--
-- Host: localhost    Database: browsy_aplk
-- ------------------------------------------------------


--
-- Table structure for table `wp_cmplz_cookiebanners`
--

CREATE TABLE `wp_cmplz_cookiebanners` (
  `ID` int(11) NOT NULL AUTO_INCREMENT,
  `banner_version` int(11) NOT NULL,
  `default` int(11) NOT NULL,
  `archived` int(11) NOT NULL,
  `title` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `position` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `theme` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `checkbox_style` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `use_logo` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `logo_attachment_id` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `close_button` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `revoke` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `manage_consent_options` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `header` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `dismiss` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `save_preferences` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `view_preferences` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `category_functional` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `category_all` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `category_stats` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `category_prefs` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `accept` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `message_optin` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `use_categories` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `disable_cookiebanner` int(11) NOT NULL,
  `banner_width` int(11) NOT NULL,
  `soft_cookiewall` int(11) NOT NULL,
  `dismiss_on_scroll` int(11) NOT NULL,
  `dismiss_on_timeout` int(11) NOT NULL,
  `dismiss_timeout` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `accept_informational` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `message_optout` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `use_custom_cookie_css` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `custom_css` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `statistics` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `functional_text` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `statistics_text` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `statistics_text_anonymous` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `preferences_text` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `marketing_text` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `colorpalette_background` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `colorpalette_text` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `colorpalette_toggles` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `colorpalette_border_radius` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `border_width` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `font_size` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `colorpalette_button_accept` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `colorpalette_button_deny` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `colorpalette_button_settings` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `buttons_border_radius` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `animation` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `use_box_shadow` int(11) NOT NULL,
  `header_footer_shadow` int(11) NOT NULL,
  `hide_preview` int(11) NOT NULL,
  `disable_width_correction` int(11) NOT NULL,
  `legal_documents` int(11) NOT NULL,
  PRIMARY KEY (`ID`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_cmplz_cookiebanners`
--

INSERT INTO `wp_cmplz_cookiebanners` VALUES (1,14,1,0,'bottom-right view-preferences','bottom-right','','slider','hide','0','1','Gérer le consentement','hover-hide-mobile','a:2:{s:4:\"text\";s:34:\"Gérer le consentement aux cookies\";s:4:\"show\";i:1;}','a:2:{s:4:\"text\";s:7:\"Refuser\";s:4:\"show\";i:1;}','Enregistrer les préférences','Voir les préférences','Fonctionnel','a:2:{s:4:\"text\";s:9:\"Marketing\";s:4:\"show\";i:1;}','a:2:{s:4:\"text\";s:12:\"Statistiques\";s:4:\"show\";i:1;}','a:2:{s:4:\"text\";s:0:\"\";s:4:\"show\";b:1;}','Accepter','Pour offrir les meilleures expériences, nous utilisons des technologies telles que les cookies pour stocker et/ou accéder aux informations des appareils. Le fait de consentir à ces technologies nous permettra de traiter des données telles que le comportement de navigation ou les ID uniques sur ce site. Le fait de ne pas consentir ou de retirer son consentement peut avoir un effet négatif sur certaines caractéristiques et fonctions.','view-preferences',0,526,0,0,0,'10','a:2:{s:4:\"text\";s:0:\"\";s:4:\"show\";b:1;}','To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.','0','/* Container */\r\n.cmplz-cookiebanner{}\r\n\r\n/* Logo */\r\n.cmplz-cookiebanner .cmplz-logo{}\r\n/* Title */\r\n.cmplz-cookiebanner .cmplz-title{}\r\n/* Close icon */\r\n.cmplz-cookiebanner .cmplz-close{}\r\n\r\n/* Message */\r\n.cmplz-cookiebanner .cmplz-message{}\r\n\r\n /* All buttons */\r\n.cmplz-buttons .cmplz-btn{}\r\n/* Accept button */\r\n.cmplz-btn .cmplz-accept{} \r\n /* Deny button */\r\n.cmplz-btn .cmplz-deny{}\r\n /* Save preferences button */\r\n.cmplz-btn .cmplz-deny{}\r\n /* View preferences button */\r\n.cmplz-btn .cmplz-deny{}\r\n\r\n /* Document hyperlinks */\r\n.cmplz-links .cmplz-documents{}\r\n\r\n /* Categories */\r\n.cmplz-cookiebanner .cmplz-category{}\r\n.cmplz-cookiebanner .cmplz-category-title{} \r\n\r\n/* Manage consent tab */\r\n#cmplz-manage-consent .cmplz-manage-consent{} \r\n\r\n/* Soft cookie wall */\r\n.cmplz-soft-cookiewall{}\r\n\r\n/* Placeholder button - Per category */\r\n.cmplz-blocked-content-container .cmplz-blocked-content-notice{}\r\n\r\n/* Placeholder button & message - Per service */\r\n.cmplz-blocked-content-container .cmplz-blocked-content-notice,\r\n.cmplz-blocked-content-notice{}\r\nbutton.cmplz-accept-service{}\r\n\r\n/* Styles for the AMP notice */\r\n#cmplz-consent-ui, #cmplz-post-consent-ui {}\r\n/* Message */\r\n#cmplz-consent-ui .cmplz-consent-message {}\r\n/* Buttons */\r\n#cmplz-consent-ui button, #cmplz-post-consent-ui button {}','a:0:{}','a:2:{s:4:\"text\";s:340:\"Le stockage ou l’accès technique est strictement nécessaire dans la finalité d’intérêt légitime de permettre l’utilisation d’un service spécifique explicitement demandé par l’abonné ou l’internaute, ou dans le seul but d’effectuer la transmission d’une communication sur un réseau de communications électroniques.\";s:4:\"show\";i:1;}','a:2:{s:4:\"text\";s:92:\"Le stockage ou l’accès technique qui est utilisé exclusivement à des fins statistiques.\";s:4:\"show\";i:1;}','a:2:{s:4:\"text\";s:0:\"\";s:4:\"show\";b:1;}','a:2:{s:4:\"text\";s:0:\"\";s:4:\"show\";b:1;}','a:2:{s:4:\"text\";s:241:\"Le stockage ou l’accès technique est nécessaire pour créer des profils d’internautes afin d’envoyer des publicités, ou pour suivre l’internaute sur un site web ou sur plusieurs sites web ayant des finalités marketing similaires.\";s:4:\"show\";i:1;}','a:2:{s:5:\"color\";s:7:\"#ffffff\";s:6:\"border\";s:7:\"#f2f2f2\";}','a:2:{s:5:\"color\";s:7:\"#222222\";s:9:\"hyperlink\";s:7:\"#1E73BE\";}','a:3:{s:10:\"background\";s:7:\"#1e73be\";s:6:\"bullet\";s:7:\"#ffffff\";s:8:\"inactive\";s:7:\"#F56E28\";}','a:5:{s:3:\"top\";i:0;s:5:\"right\";i:0;s:6:\"bottom\";i:0;s:4:\"left\";i:0;s:4:\"type\";s:2:\"px\";}','a:4:{s:3:\"top\";i:0;s:5:\"right\";i:0;s:6:\"bottom\";i:0;s:4:\"left\";i:0;}','16','a:3:{s:10:\"background\";s:7:\"#1E73BE\";s:6:\"border\";s:7:\"#1E73BE\";s:4:\"text\";s:7:\"#ffffff\";}','a:3:{s:10:\"background\";s:7:\"#f9f9f9\";s:6:\"border\";s:7:\"#f2f2f2\";s:4:\"text\";s:7:\"#222222\";}','a:3:{s:10:\"background\";s:7:\"#f9f9f9\";s:6:\"border\";s:7:\"#f2f2f2\";s:4:\"text\";s:7:\"#333333\";}','a:5:{s:3:\"top\";i:0;s:5:\"right\";i:0;s:6:\"bottom\";i:0;s:4:\"left\";i:0;s:4:\"type\";s:2:\"px\";}','none',0,0,0,0,1);

--
-- Table structure for table `wp_cmplz_cookies`
--

CREATE TABLE `wp_cmplz_cookies` (
  `ID` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `slug` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `sync` int(11) NOT NULL,
  `ignored` int(11) NOT NULL,
  `retention` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `type` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `serviceID` int(11) NOT NULL,
  `cookieFunction` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `collectedPersonalData` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `purpose` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `language` varchar(6) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `isTranslationFrom` int(11) NOT NULL,
  `isPersonalData` int(11) NOT NULL,
  `isOwnDomainCookie` int(11) NOT NULL,
  `domain` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `deleted` int(11) NOT NULL,
  `isMembersOnly` int(11) NOT NULL,
  `showOnPolicy` int(11) NOT NULL,
  `lastUpdatedDate` int(11) NOT NULL,
  `lastAddDate` int(11) NOT NULL,
  `firstAddDate` int(11) NOT NULL,
  PRIMARY KEY (`ID`)
) ENGINE=InnoDB AUTO_INCREMENT=213 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_cmplz_cookies`
--

INSERT INTO `wp_cmplz_cookies` VALUES (1,'exp*','exp10032188',1,0,'','localstorage',15,'provide functions across pages','none','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(2,'exp*','exp10032188',1,0,'','',16,'Fournir des fonctions sur toutes les pages','aucune','Fonctionnel','fr',1,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(3,'wc_cart_hash_*','wc_cart_hash_',1,0,'session','localstorage',17,'store items in shopping cart','none','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(4,'wc_cart_hash_*','wc_cart_hash_',1,0,'session','',18,'Stocker les éléments dans le panier de la boutique','aucune','Fonctionnel','fr',3,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(7,'*_expiresAt','_expiresat',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(8,'*_expiresAt','_expiresat',1,0,'','',0,'','','','fr',7,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(9,'fav_units','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363283),(10,'fav_units','',1,0,'','',0,'','','','fr',9,0,0,'self',0,0,1,0,1704483176,1701363283),(11,'kirby$content$pages/home/galerie/fr','',1,1,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,1701363786,1701363632,1701363283),(12,'kirby$content$pages/home/galerie/fr','',1,1,'','',0,'','','','fr',11,0,0,'self',0,0,1,1701363786,1701363632,1701363283),(13,'twk_*','twk_',1,0,'session','localstorage',19,'','','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(14,'twk_*','twk_',1,0,'session','',20,'','','Fonctionnel','fr',13,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(25,'algoliasearch-client-js','algoliasearch-client-js',1,1,'session','localstorage',21,'','','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(26,'algoliasearch-client-js','algoliasearch-client-js',1,1,'session','',22,'','','Fonctionnel','fr',25,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(27,'_DxHCKSjkLwYEO3O6Pgp,4188000101','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363283),(28,'_DxHCKSjkLwYEO3O6Pgp,4188000101','',1,0,'','',0,'','','','fr',27,0,0,'self',0,0,1,0,1704483176,1701363283),(31,'kirby$language','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363283),(32,'kirby$language','',1,0,'','',0,'','','','fr',31,0,0,'self',0,0,1,0,1704483176,1701363283),(33,'loglevel','',1,1,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(34,'loglevel','',1,1,'','',0,'','','','fr',33,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(37,'qm-container-height','qm-container-height',1,1,'various','localstorage',23,'provide functions across pages','No data from visitors','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(38,'qm-container-height','qm-container-height',1,1,'divers','',24,'Fournir des fonctions sur toutes les pages','Aucune donnée provenant des visiteurs','Fonctionnel','fr',37,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(41,'acf','acf',1,1,'expires immediately','localstorage',25,'provide functions across pages','none','','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(42,'acf','acf',1,1,'aucune','',26,'Fournir des fonctions sur toutes les pages','aucune','','fr',41,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(43,'39d3CLiVv6YYELDWwd0p,4188000101','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363283),(44,'39d3CLiVv6YYELDWwd0p,4188000101','',1,0,'','',0,'','','','fr',43,0,0,'self',0,0,1,0,1704483176,1701363283),(49,'WP_DATA_USER_9','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363283),(50,'WP_DATA_USER_9','',1,0,'','',0,'','','','fr',49,0,0,'self',0,0,1,0,1704483176,1701363283),(51,'undefined','undefined',1,1,'1 year','localstorage',0,'provide a responsive website','none','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(52,'undefined','undefined',1,1,'1 an','',0,'Fournir un site web responsive','aucune','Fonctionnel','fr',51,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(53,'__mp_opt_in_out_*','__mp_opt_in_out_',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(54,'__mp_opt_in_out_*','__mp_opt_in_out_',1,0,'','',0,'','','','fr',53,0,0,'self',0,0,1,1701363786,1704483176,1701363283),(55,'wpEmojiSettingsSupports','wpemojisettingssupports',1,0,'session','Cookie',27,'store browser details','none','Functional','en',0,0,0,'self',0,0,1,1701363786,1701363632,1701363283),(56,'wpEmojiSettingsSupports','wpemojisettingssupports',1,0,'session','',28,'Stocker les informations du navigateur','aucune','Fonctionnel','fr',55,0,0,'self',0,0,1,1701363786,1701363632,1701363283),(57,'wordpress_test_cookie','wordpress_test_cookie',1,0,'session','cookie',27,'read if cookies can be placed','','Functional','en',0,0,0,'self',0,1,1,1701363786,1704483177,1701363283),(58,'wordpress_test_cookie','wordpress_test_cookie',1,0,'session','',28,'Vérifier si des cookies peuvent être déposés','','Fonctionnel','fr',57,0,0,'self',0,1,1,1701363786,1704483177,1701363283),(59,'wp_lang','wp_lang',1,0,'session','Cookie',27,'store language settings','','Functional','en',0,0,0,'self',0,1,1,1701363786,1701363632,1701363283),(60,'wp_lang','wp_lang',1,0,'session','',28,'Stocker les réglages de langue','','Fonctionnel','fr',59,0,0,'self',0,1,1,1701363786,1701363632,1701363283),(61,'_ga','_ga',1,0,'2 years','cookie',29,'store and count pageviews','','Statistics','en',0,0,0,'self',0,0,1,1701363786,1704483177,1701363283),(62,'_ga','_ga',1,0,'2 ans','',30,'Compter et suivre les pages visitées','','Statistiques','fr',61,0,0,'self',0,0,1,1701363786,1704483177,1701363283),(63,'_ga_*','_ga_',1,0,'1 year','cookie',29,'store and count pageviews','','Statistics','en',0,0,0,'self',0,0,1,1701363786,1704483177,1701363283),(64,'_ga_*','_ga_',1,0,'1 an','',30,'Compter et suivre les pages visitées','','Statistiques','fr',63,0,0,'self',0,0,1,1701363786,1704483177,1701363283),(71,'initialTrafficSource','',1,0,'','cookie',0,'','','','en',0,0,0,'self',0,0,1,0,1701363632,1701363283),(72,'initialTrafficSource','',1,0,'','',0,'','','','fr',71,0,0,'self',0,0,1,0,1701363632,1701363283),(73,'_ldstut','',1,0,'','cookie',0,'','','','en',0,0,0,'self',0,0,1,0,1701363632,1701363283),(74,'_ldstut','',1,0,'','',0,'','','','fr',73,0,0,'self',0,0,1,0,1701363632,1701363283),(75,'_ldstud','',1,0,'','cookie',0,'','','','en',0,0,0,'self',0,0,1,0,1701363632,1701363283),(76,'_ldstud','',1,0,'','',0,'','','','fr',75,0,0,'self',0,0,1,0,1701363632,1701363283),(77,'_ldstuw','',1,0,'','cookie',0,'','','','en',0,0,0,'self',0,0,1,0,1701363632,1701363283),(78,'_ldstuw','',1,0,'','',0,'','','','fr',77,0,0,'self',0,0,1,0,1701363632,1701363283),(79,'_ldstum','',1,0,'','cookie',0,'','','','en',0,0,0,'self',0,0,1,0,1701363632,1701363283),(80,'_ldstum','',1,0,'','',0,'','','','fr',79,0,0,'self',0,0,1,0,1701363632,1701363283),(81,'constrobourg-_zldp','',1,0,'','cookie',0,'','','','en',0,0,0,'self',0,0,1,0,1701363632,1701363283),(82,'constrobourg-_zldp','',1,0,'','',0,'','','','fr',81,0,0,'self',0,0,1,0,1701363632,1701363283),(85,'__stripe_mid','__stripe_mid',1,0,'1 year','cookie',31,'provide fraud prevention','','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483177,1701363283),(86,'__stripe_mid','__stripe_mid',1,0,'1 an','',32,'Empêcher la fraude','','Fonctionnel','fr',85,0,0,'self',0,0,1,1701363787,1704483177,1701363283),(87,'_gcl_au','_gcl_au',1,0,'persistent','cookie',33,'store and track conversions','browsing behaviour','Marketing','en',0,0,0,'self',0,0,1,1701363786,1704483177,1701363283),(88,'_gcl_au','_gcl_au',1,0,'persistante','',34,'Stocker et suivre les conversions','comportement de navigation','Marketing','fr',87,0,0,'self',0,0,1,1701363787,1704483177,1701363283),(89,'_wpfuuid','_wpfuuid',1,0,'11 years','cookie',35,'store a unique user ID','','Preferences','en',0,0,0,'self',0,0,1,1701363786,1704483177,1701363283),(90,'_wpfuuid','_wpfuuid',1,0,'11 ans','',36,'Stocker un ID utilisateur unique','','Préférences','fr',89,0,0,'self',0,0,1,1701363787,1704483177,1701363283),(103,'mailchimp_landing_site','mailchimp_landing_site',1,0,'1 month','',37,'store which page was visited first','','Statistics','en',0,0,0,'self',0,0,1,1701363786,1701363632,1701363283),(104,'mailchimp_landing_site','mailchimp_landing_site',1,0,'1 mois','',38,'Stocker la page visitée en premier','','Statistiques','fr',103,0,0,'self',0,0,1,1701363787,1701363632,1701363283),(105,'PHPSESSID','phpsessid',1,1,'session','cookie',15,'provide functions across pages','none','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483177,1701363283),(106,'PHPSESSID','phpsessid',1,1,'session','',16,'Fournir des fonctions sur toutes les pages','aucune','Fonctionnel','fr',105,0,0,'self',0,0,1,1701363787,1704483177,1701363283),(107,'wordpress_logged_in_*','wordpress_logged_in_',1,0,'persistent','cookie',27,'Store logged in users','','Functional','en',0,0,0,'self',0,1,1,1701363786,1704483177,1701363283),(108,'wordpress_logged_in_*','wordpress_logged_in_',1,0,'persistante','',28,'Garder les utilisateurs connectés','','Fonctionnel','fr',107,0,0,'self',0,1,1,1701363787,1704483177,1701363283),(109,'io','',1,0,'','cookie',0,'','','','en',0,0,0,'self',0,0,1,0,1704483177,1701363283),(110,'io','',1,0,'','',0,'','','','fr',109,0,0,'self',0,0,1,0,1704483177,1701363283),(111,'Console/Mode','',1,1,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363292),(112,'Console/Mode','',1,1,'','',0,'','','','fr',111,0,0,'self',0,0,1,1701363787,1704483176,1701363292),(113,'instawp_admin_current','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(114,'instawp_admin_current','',1,0,'','',0,'','','','fr',113,0,0,'self',0,0,1,0,1704483176,1701363292),(115,'continueReview','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(116,'continueReview','',1,0,'','',0,'','','','fr',115,0,0,'self',0,0,1,0,1704483176,1701363292),(119,'wpformsChallengeStep','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(120,'wpformsChallengeStep','',1,0,'','',0,'','','','fr',119,0,0,'self',0,0,1,0,1704483176,1701363292),(121,'wpformsChallengeTimerId','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(122,'wpformsChallengeTimerId','',1,0,'','',0,'','','','fr',121,0,0,'self',0,0,1,0,1704483176,1701363292),(123,'wpformsChallengeSecondsLeft','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(124,'wpformsChallengeSecondsLeft','',1,0,'','',0,'','','','fr',123,0,0,'self',0,0,1,0,1704483176,1701363292),(125,'wistia','wistia',1,0,'persistent','localstorage',43,'store performed actions on the website','browsing device information','Marketing','en',0,0,0,'self',0,0,1,1701363793,1704483176,1701363292),(126,'wistia','wistia',1,0,'persistante','',44,'Stocker les actions effectuées par les utilisateurs sur le site web','informations sur l’appareil de navigation','Marketing','fr',125,0,0,'self',0,0,1,1701363793,1704483176,1701363292),(127,'_uetvid_exp','_uetvid_exp',1,0,'persistent','localstorage',39,'','','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363292),(128,'_uetvid_exp','_uetvid_exp',1,0,'persistante','',40,'','','Fonctionnel','fr',127,0,0,'self',0,0,1,1701363787,1704483176,1701363292),(129,'affwp-notice-affwp-license-upgrade-seen-1','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(130,'affwp-notice-affwp-license-upgrade-seen-1','',1,0,'','',0,'','','','fr',129,0,0,'self',0,0,1,0,1704483176,1701363292),(131,'_uetsid_exp','_uetsid_exp',1,0,'persistent','localstorage',39,'','','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363292),(132,'_uetsid_exp','_uetsid_exp',1,0,'persistante','',40,'','','Fonctionnel','fr',131,0,0,'self',0,0,1,1701363787,1704483176,1701363292),(133,'Drupal.*','drupal',1,1,'','localstorage',41,'','','','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363292),(134,'Drupal.*','drupal',1,1,'','',42,'','','','fr',133,0,0,'self',0,0,1,1701363787,1704483176,1701363292),(135,'_uetsid','_uetsid',1,0,'1 day','localstorage',39,'store and track visits across websites','','Marketing','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363292),(136,'_uetsid','_uetsid',1,0,'1 jour','',40,'Stocker et suivre les visites à travers les sites web','','Marketing','fr',135,0,0,'self',0,0,1,1701363787,1704483176,1701363292),(137,'Console','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(138,'Console','',1,0,'','',0,'','','','fr',137,0,0,'self',0,0,1,0,1704483176,1701363292),(139,'showThisQuery','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(140,'showThisQuery','',1,0,'','',0,'','','','fr',139,0,0,'self',0,0,1,0,1704483176,1701363292),(141,'siqlsdb','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(142,'siqlsdb','',1,0,'','',0,'','','','fr',141,0,0,'self',0,0,1,0,1704483176,1701363292),(143,'utsdb','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(144,'utsdb','',1,0,'','',0,'','','','fr',143,0,0,'self',0,0,1,0,1704483176,1701363292),(145,'storeApiNonce','storeapinonce',1,1,'session','localstorage',17,'provide functions across pages','','Functional','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363292),(146,'storeApiNonce','storeapinonce',1,1,'session','',18,'Fournir des fonctions sur toutes les pages','','Fonctionnel','fr',145,0,0,'self',0,0,1,1701363787,1704483176,1701363292),(147,'wistia-video-progress-*','wistia-video-progress',1,0,'persistent','localstorage',43,'store if the user has seen embedded content','','Statistics','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363292),(148,'wistia-video-progress-*','wistia-video-progress',1,0,'persistante','',44,'Stocker si l&#039;utilisateur a vu du contenu intégré','','Statistiques','fr',147,0,0,'self',0,0,1,1701363787,1704483176,1701363292),(149,'WP_DATA_USER_7','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(150,'WP_DATA_USER_7','',1,0,'','',0,'','','','fr',149,0,0,'self',0,0,1,0,1704483176,1701363292),(151,'WP_PREFERENCES_USER_*','wp_preferences_user_',1,0,'persistent','localstorage',27,'store user preferences','none','Functional','en',0,0,0,'self',0,1,1,1701363786,1704483176,1701363292),(152,'WP_PREFERENCES_USER_*','wp_preferences_user_',1,0,'persistante','',28,'Stocker les préférences des utilisateurs','aucune','Fonctionnel','fr',151,0,0,'self',0,1,1,1701363787,1704483176,1701363292),(153,'NavigationWidth','',1,0,'','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1701363292),(154,'NavigationWidth','',1,0,'','',0,'','','','fr',153,0,0,'self',0,0,1,0,1704483176,1701363292),(155,'_uetvid','_uetvid',1,0,'13 months','localstorage',39,'store and track visits across websites','','Marketing','en',0,0,0,'self',0,0,1,1701363786,1704483176,1701363292),(156,'_uetvid','_uetvid',1,0,'13 mois','',40,'Stocker et suivre les visites à travers les sites web','','Marketing','fr',155,0,0,'self',0,0,1,1701363787,1704483177,1701363292),(157,'Adobe Fonts API','adobefonts',1,0,'expires immediately','API',3,'read user IP address','IP address','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(158,'Adobe Fonts API','adobefonts',1,0,'aucune','',4,'Demander l’adresse IP de l’utilisateur','adresse IP','Marketing','fr',157,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(159,'Google Fonts API','tcb_google_fonts',1,0,'expires immediately','API',5,'read user IP address','IP address','Marketing','en',0,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(160,'Google Fonts API','tcb_google_fonts',1,0,'aucune','',6,'Demander l’adresse IP de l’utilisateur','adresse IP','Marketing','fr',159,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(161,'rc::c','rcc',1,0,'session','',7,'read and filter requests from bots','','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(162,'rc::c','rcc',1,0,'session','',8,'Filtrer les requêtes des robots','','Marketing','fr',161,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(163,'rc::b','rcb',1,0,'session','',7,'read and filter requests from bots','','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(164,'rc::b','rcb',1,0,'session','',8,'Filtrer les requêtes des robots','','Marketing','fr',163,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(165,'rc::a','rca',1,0,'persistent','',7,'read and filter requests from bots','','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(166,'rc::a','rca',1,0,'persistante','',8,'Filtrer les requêtes des robots','','Marketing','fr',165,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(167,'Google Maps API','google-maps-api',1,0,'expires immediately','API',9,'read user IP address','IP address','Marketing','en',0,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(168,'Google Maps API','google-maps-api',1,0,'aucune','',10,'Demander l’adresse IP de l’utilisateur','adresse IP','Marketing','fr',167,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(169,'GPS','gps',1,0,'session','',11,'store location data','location data','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(170,'GPS','gps',1,0,'session','',12,'Stocker les données de localisation','données de localisation','Marketing','fr',169,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(171,'VISITOR_INFO1_LIVE','visitor_info1_live',1,0,'6 months','Cookie',11,'provide ad delivery or retargeting','browsing behaviour','Marketing','en',0,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(172,'VISITOR_INFO1_LIVE','visitor_info1_live',1,0,'6 mois','',12,'Activer la diffusion ou le reciblage des publicités','comportement de navigation','Marketing','fr',171,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(173,'YSC','ysc',1,0,'session','Cookie',11,'Store and track interaction','user ID','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(174,'YSC','ysc',1,0,'session','',12,'Stocker et suivre les interactions','ID utilisateur','Marketing','fr',173,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(175,'PREF','pref',1,0,'8 months','Cookie',11,'store user preferences','browsing behaviour','Marketing','en',0,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(176,'PREF','pref',1,0,'8 mois','',12,'Stocker les préférences des utilisateurs','comportement de navigation','Marketing','fr',175,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(177,'_js_datr','_js_datr',1,1,'2 years','',13,'store user preferences','','Preferences','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(178,'_js_datr','_js_datr',1,1,'2 ans','',14,'Stocker les préférences des utilisateurs','','Préférences','fr',177,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(179,'_fbc','_fbc',1,0,'2 years','',13,'store last visit','browsing device information','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(180,'_fbc','_fbc',1,0,'2 ans','',14,'Stocker la dernière visite','informations sur l’appareil de navigation','Marketing','fr',179,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(181,'fbm*','fbm_',1,0,'1 year','',13,'store account details','social media account details','Marketing','en',0,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(182,'fbm*','fbm_',1,0,'1 an','',14,'Stocker les informations des comptes','coordonnées des comptes de réseaux sociaux','Marketing','fr',181,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(183,'xs','xs',1,0,'3 months','',13,'store a unique session ID','','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(184,'xs','xs',1,0,'3 mois','',14,'Stocker un ID de session unique','','Marketing','fr',183,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(185,'wd','wd',1,0,'1 week','',13,'read screen resolution','','Functional','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(186,'wd','wd',1,0,'1 semaine','',14,'Déterminer la résolution d’écran','','Fonctionnel','fr',185,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(187,'fr','fr',1,0,'3 months','',13,'provide ad delivery or retargeting','social media account details','Marketing','en',0,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(188,'fr','fr',1,0,'3 mois','',14,'Activer la diffusion ou le reciblage des publicités','coordonnées des comptes de réseaux sociaux','Marketing','fr',187,1,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(189,'act','act',1,0,'90 days','',13,'Store logged in users','','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(190,'act','act',1,0,'90 jours','',14,'Garder les utilisateurs connectés','','Marketing','fr',189,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(191,'_fbp','_fbp',1,0,'3 months','',13,'store and track visits across websites','','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(192,'_fbp','_fbp',1,0,'3 mois','',14,'Stocker et suivre les visites à travers les sites web','','Marketing','fr',191,0,0,'thirdparty',0,0,1,1701363794,1701363789,1701363789),(193,'datr','datr',1,0,'2 years','',13,'provide fraud prevention','browsing device information','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(194,'datr','datr',1,0,'2 ans','',14,'Empêcher la fraude','informations sur l’appareil de navigation','Marketing','fr',193,0,0,'thirdparty',0,0,1,1701363794,1701363789,1701363789),(195,'c_user','c_user',1,0,'30 days','',13,'store a unique user ID','user ID','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(196,'c_user','c_user',1,0,'30 jours','',14,'Stocker un ID utilisateur unique','ID utilisateur','Marketing','fr',195,0,0,'thirdparty',0,0,1,1701363794,1701363789,1701363789),(197,'csm','csm',1,0,'90 days','',13,'provide fraud prevention','','Functional','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363789,1701363789),(198,'csm','csm',1,0,'90 jours','',14,'Empêcher la fraude','','Fonctionnel','fr',197,0,0,'thirdparty',0,0,1,1701363794,1701363790,1701363790),(199,'sb','sb',1,0,'2 years','',13,'store browser details','browsing device information','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363790,1701363790),(200,'sb','sb',1,0,'2 ans','',14,'Stocker les informations du navigateur','informations sur l’appareil de navigation','Marketing','fr',199,0,0,'thirdparty',0,0,1,1701363794,1701363790,1701363790),(201,'actppresence','actppresence',1,0,'session','Cookie',13,'store and track if the browser tab is active','','Functional','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363790,1701363790),(202,'actppresence','actppresence',1,0,'session','',14,'Stocker et suivre si l&#039;onglet du navigateur est actif','','Fonctionnel','fr',201,0,0,'thirdparty',0,0,1,1701363794,1701363790,1701363790),(203,'*_fbm_','_fbm_',1,0,'1 year','',13,'store account details','social media account details','Marketing','en',0,1,0,'thirdparty',0,0,1,1701363793,1701363790,1701363790),(204,'*_fbm_','_fbm_',1,0,'1 an','',14,'Stocker les informations des comptes','coordonnées des comptes de réseaux sociaux','Marketing','fr',203,1,0,'thirdparty',0,0,1,1701363794,1701363790,1701363790),(205,'google_adsense_settings','google_adsense_settings',1,0,'persistent','',33,'provide ad delivery or retargeting','','Marketing','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363790,1701363790),(206,'google_adsense_settings','google_adsense_settings',1,0,'persistante','',34,'Activer la diffusion ou le reciblage des publicités','','Marketing','fr',205,0,0,'thirdparty',0,0,1,1701363794,1701363790,1701363790),(207,'mailchimp.cart.*','mailchimp-cart',1,0,'','',37,'','','','en',0,0,0,'thirdparty',0,0,1,1701363793,1701363790,1701363790),(208,'mailchimp.cart.*','mailchimp-cart',1,0,'','',38,'','','','fr',207,0,0,'thirdparty',0,0,1,1701363794,1701363790,1701363790),(209,'cmplz_consenttype','',1,0,'365 days','localstorage',0,'','','','en',0,0,0,'self',0,0,1,0,1704483176,1704483161),(210,'cmplz_consenttype','',1,0,'365 days','',0,'','','','fr',209,0,0,'self',0,0,1,0,1704483176,1704483161),(211,'cmplz_banner-status','',1,0,'365 days','cookie',0,'','','','en',0,0,0,'self',0,0,1,0,1704483177,1704483161),(212,'cmplz_banner-status','',1,0,'365 days','',0,'','','','fr',211,0,0,'self',0,0,1,0,1704483177,1704483161);

--
-- Table structure for table `wp_cmplz_services`
--

CREATE TABLE `wp_cmplz_services` (
  `ID` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `slug` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `serviceType` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `category` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `thirdParty` int(11) NOT NULL,
  `sharesData` int(11) NOT NULL,
  `secondParty` int(11) NOT NULL,
  `privacyStatementURL` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `language` varchar(6) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `isTranslationFrom` int(11) NOT NULL,
  `sync` int(11) NOT NULL,
  `lastUpdatedDate` int(11) NOT NULL,
  PRIMARY KEY (`ID`)
) ENGINE=InnoDB AUTO_INCREMENT=45 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_cmplz_services`
--

INSERT INTO `wp_cmplz_services` VALUES (1,'Google Tag Manager','google-tag-manager','website statistics','',1,1,1,'https://policies.google.com/privacy','en',0,1,1701363789),(2,'Google Tag Manager','google-tag-manager','les statistiques du site web','',1,1,1,'https://policies.google.com/privacy','fr',1,1,1701363789),(3,'Adobe Fonts','adobefonts','display of webfonts','service',1,1,0,'https://www.adobe.com/privacy/policies/adobe-fonts.html','en',0,1,1701363789),(4,'Adobe Fonts','adobefonts','l’affichage des polices web','service',1,1,0,'https://www.adobe.com/privacy/policies/adobe-fonts.html','fr',3,1,1701363789),(5,'Google Fonts','google-fonts','display of webfonts','service',1,1,0,'https://policies.google.com/privacy','en',0,1,1701363789),(6,'Google Fonts','google-fonts','l’affichage des polices web','service',1,1,0,'https://policies.google.com/privacy','fr',5,1,1701363789),(7,'Google reCAPTCHA','google-recaptcha','spam prevention','service',1,1,0,'https://policies.google.com/privacy','en',0,1,1701363789),(8,'Google reCAPTCHA','google-recaptcha','le blocage des indésirables','service',1,1,0,'https://policies.google.com/privacy','fr',7,1,1701363789),(9,'Google Maps','google-maps','maps display','service',1,1,0,'https://policies.google.com/privacy','en',0,1,1701363789),(10,'Google Maps','google-maps','l’affichage de cartes','service',1,1,0,'https://policies.google.com/privacy','fr',9,1,1701363789),(11,'YouTube','youtube','video display','service',1,1,0,'https://policies.google.com/privacy','en',0,1,1701363789),(12,'YouTube','youtube','l’affichage de vidéos','service',1,1,0,'https://policies.google.com/privacy','fr',11,1,1701363789),(13,'Facebook','facebook','display of recent social posts and/or social share buttons','social',1,1,0,'https://www.facebook.com/policy/cookies','en',0,1,1701363789),(14,'Facebook','facebook','l’affichage de publications sociales récentes et/ou des boutons de partage de réseaux sociaux','social',1,1,0,'https://www.facebook.com/policy/cookies','fr',13,1,1701363789),(15,'PHP','php','website development','',0,0,0,'','en',0,1,1701363790),(16,'PHP','php','le développement du site web','',0,0,0,'','fr',15,1,1701363790),(17,'WooCommerce','woocommerce','webshop management','',0,0,0,'','en',0,1,1701363790),(18,'WooCommerce','woocommerce','la gestion de boutique en ligne','',0,0,0,'','fr',17,1,1701363790),(19,'Tawk','tawk','chat support','',1,1,1,'https://www.tawk.to/privacy-policy/','en',0,1,1701363790),(20,'Tawk','tawk','l’assistance par discussion instantanée','',1,1,1,'https://www.tawk.to/privacy-policy/','fr',19,1,1701363790),(21,'Algolia','algolia','search functions','',0,0,0,'','en',0,1,1701363790),(22,'Algolia','algolia','les fonctions de recherche','',0,0,0,'','fr',21,1,1701363790),(23,'Query Monitor','query-monitor','website development','',0,0,0,'','en',0,1,1701363790),(24,'Query Monitor','query-monitor','le développement du site web','',0,0,0,'','fr',23,1,1701363790),(25,'Advanced Custom Fields','advanced-custom-fields','content creation','',0,0,0,'','en',0,1,1701363790),(26,'Advanced Custom Fields','advanced-custom-fields','la création de contenu','',0,0,0,'','fr',25,1,1701363790),(27,'WordPress','wordpress','website development','',0,0,0,'','en',0,1,1701363790),(28,'WordPress','wordpress','le développement du site web','',0,0,0,'','fr',27,1,1701363790),(29,'Google Analytics','google-analytics','website statistics','',1,1,1,'https://policies.google.com/privacy','en',0,1,1701363790),(30,'Google Analytics','google-analytics','les statistiques du site web','',1,1,1,'https://policies.google.com/privacy','fr',29,1,1701363790),(31,'Stripe','stripe','payment processing','',1,1,1,'https://stripe.com/privacy/','en',0,1,1701363790),(32,'Stripe','stripe','le traitement de paiement','',1,1,1,'https://stripe.com/privacy/','fr',31,1,1701363790),(33,'Google Adsense','google-adsense','showing advertisements','',1,1,0,'https://policies.google.com/privacy','en',0,1,1701363790),(34,'Google Adsense','google-adsense','l’affichage de publicités','',1,1,0,'https://policies.google.com/privacy','fr',33,1,1701363790),(35,'WPForms','wpforms','webforms','',0,0,0,'','en',0,1,1701363790),(36,'WPForms','wpforms','les formulaires web','',0,0,0,'','fr',35,1,1701363790),(37,'MailChimp','mailchimp','mailing list subscriptions','',1,1,0,'https://mailchimp.com/legal/privacy/','en',0,1,1701363790),(38,'MailChimp','mailchimp','les abonnements aux listes de diffusion','',1,1,0,'https://mailchimp.com/legal/privacy/','fr',37,1,1701363790),(39,'Bing Ads','bing-ads','advertising','',1,1,1,'https://privacy.microsoft.com/privacystatement','en',0,1,1701363790),(40,'Bing Ads','bing-ads','la publicité','',1,1,1,'https://privacy.microsoft.com/privacystatement','fr',39,1,1701363790),(41,'Admin','admin','website development','',0,0,0,'','en',0,1,1701363790),(42,'Admin','admin','le développement du site web','',0,0,0,'','fr',41,1,1701363790),(43,'Wistia','wistia','video display','',1,1,0,'https://wistia.com/privacy','en',0,1,1701363790),(44,'Wistia','wistia','l’affichage de vidéos','',1,1,0,'https://wistia.com/privacy','fr',43,1,1701363790);

--
-- 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 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

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


--
-- Table structure for table `wp_icl_content_status`
--

CREATE TABLE `wp_icl_content_status` (
  `rid` bigint(20) NOT NULL,
  `nid` bigint(20) NOT NULL,
  `timestamp` datetime NOT NULL,
  `md5` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  PRIMARY KEY (`rid`),
  KEY `nid` (`nid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_content_status`
--


--
-- Table structure for table `wp_icl_core_status`
--

CREATE TABLE `wp_icl_core_status` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `rid` bigint(20) NOT NULL,
  `module` varchar(16) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `origin` varchar(64) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `target` varchar(64) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `status` smallint(6) NOT NULL,
  `tp_revision` int(11) NOT NULL DEFAULT '1',
  `ts_status` text COLLATE utf8mb4_unicode_520_ci,
  PRIMARY KEY (`id`),
  KEY `rid` (`rid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_core_status`
--


--
-- Table structure for table `wp_icl_flags`
--

CREATE TABLE `wp_icl_flags` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `lang_code` varchar(10) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `flag` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `from_template` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `lang_code` (`lang_code`)
) ENGINE=InnoDB AUTO_INCREMENT=65 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_flags`
--

INSERT INTO `wp_icl_flags` VALUES (1,'ar','ar.png',0),(2,'bg','bg.png',0),(3,'bn','bn.png',0),(4,'bs','bs.png',0),(5,'ca','ca.png',0),(6,'cs','cs.png',0),(7,'cy','cy.png',0),(8,'da','da.png',0),(9,'de','de.png',0),(10,'el','el.png',0),(11,'en','en.png',0),(12,'eo','eo.png',0),(13,'es','es.png',0),(14,'et','et.png',0),(15,'eu','eu.png',0),(16,'fa','fa.png',0),(17,'fi','fi.png',0),(18,'fr','fr.png',0),(19,'ga','ga.png',0),(20,'gl','gl.png',0),(21,'he','he.png',0),(22,'hi','hi.png',0),(23,'hr','hr.png',0),(24,'hu','hu.png',0),(25,'hy','hy.png',0),(26,'id','id.png',0),(27,'is','is.png',0),(28,'it','it.png',0),(29,'ja','ja.png',0),(30,'ko','ko.png',0),(31,'ku','ku.png',0),(32,'lt','lt.png',0),(33,'lv','lv.png',0),(34,'mk','mk.png',0),(35,'mn','mn.png',0),(36,'ms','ms.png',0),(37,'mt','mt.png',0),(38,'ne','ne.png',0),(39,'nl','nl.png',0),(40,'no','no.png',0),(41,'pa','pa.png',0),(42,'pl','pl.png',0),(43,'pt-br','pt-br.png',0),(44,'pt-pt','pt-pt.png',0),(45,'qu','qu.png',0),(46,'ro','ro.png',0),(47,'ru','ru.png',0),(48,'sk','sk.png',0),(49,'sl','sl.png',0),(50,'so','so.png',0),(51,'sq','sq.png',0),(52,'sr','sr.png',0),(53,'sv','sv.png',0),(54,'ta','ta.png',0),(55,'th','th.png',0),(56,'tr','tr.png',0),(57,'uk','uk.png',0),(58,'ur','ur.png',0),(59,'uz','uz.png',0),(60,'vi','vi.png',0),(61,'yi','yi.png',0),(62,'zh-hans','zh.png',0),(63,'zh-hant','zh.png',0),(64,'zu','zu.png',0);

--
-- Table structure for table `wp_icl_languages`
--

CREATE TABLE `wp_icl_languages` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `code` varchar(7) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `english_name` varchar(128) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `major` tinyint(4) NOT NULL DEFAULT '0',
  `active` tinyint(4) NOT NULL,
  `default_locale` varchar(35) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  `tag` varchar(35) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  `encode_url` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `code` (`code`),
  UNIQUE KEY `english_name` (`english_name`)
) ENGINE=InnoDB AUTO_INCREMENT=65 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_languages`
--

INSERT INTO `wp_icl_languages` VALUES (1,'en','English',1,0,'en_US','en',0),(2,'es','Spanish',1,0,'es_ES','es',0),(3,'de','German',1,0,'de_DE','de',0),(4,'fr','French',1,0,'fr_FR','fr',0),(5,'ar','Arabic',0,0,'ar','ar',0),(6,'bs','Bosnian',0,0,'bs_BA','bs',0),(7,'bg','Bulgarian',0,0,'bg_BG','bg',0),(8,'ca','Catalan',0,0,'ca','ca',0),(9,'cs','Czech',0,0,'cs_CZ','cs',0),(10,'sk','Slovak',0,0,'sk_SK','sk',0),(11,'cy','Welsh',0,0,'cy_GB','cy',0),(12,'da','Danish',1,0,'da_DK','da',0),(13,'el','Greek',0,0,'el','el',0),(14,'eo','Esperanto',0,0,'eo_UY','eo',0),(15,'et','Estonian',0,0,'et','et',0),(16,'eu','Basque',0,0,'eu_ES','eu',0),(17,'fa','Persian',0,0,'fa_IR','fa',0),(18,'fi','Finnish',0,0,'fi','fi',0),(19,'ga','Irish',0,0,'ga_IE','ga',0),(20,'he','Hebrew',0,0,'he_IL','he',0),(21,'hi','Hindi',0,0,'hi_IN','hi',0),(22,'hr','Croatian',0,0,'hr','hr',0),(23,'hu','Hungarian',0,0,'hu_HU','hu',0),(24,'hy','Armenian',0,0,'hy_AM','hy',0),(25,'id','Indonesian',0,0,'id_ID','id',0),(26,'is','Icelandic',0,0,'is_IS','is',0),(27,'it','Italian',1,0,'it_IT','it',0),(28,'ja','Japanese',1,0,'ja','ja',0),(29,'ko','Korean',0,0,'ko_KR','ko',0),(30,'ku','Kurdish',0,0,'ckb','ku',0),(31,'lv','Latvian',0,0,'lv_LV','lv',0),(32,'lt','Lithuanian',0,0,'lt_LT','lt',0),(33,'mk','Macedonian',0,0,'mk_MK','mk',0),(34,'mt','Maltese',0,0,'mt_MT','mt',0),(35,'mn','Mongolian',0,0,'mn_MN','mn',0),(36,'ne','Nepali',0,0,'ne','ne',0),(37,'nl','Dutch',1,0,'nl_NL','nl',0),(38,'no','Norwegian Bokmål',0,0,'nb_NO','no',0),(39,'pa','Punjabi',0,0,'','pa',0),(40,'pl','Polish',0,0,'pl_PL','pl',0),(41,'pt-pt','Portuguese, Portugal',0,0,'pt_PT','pt-pt',0),(42,'pt-br','Portuguese, Brazil',0,0,'pt_BR','pt-br',0),(43,'qu','Quechua',0,0,'quz_PE','qu',0),(44,'ro','Romanian',0,0,'ro_RO','ro',0),(45,'ru','Russian',1,0,'ru_RU','ru',0),(46,'sl','Slovenian',0,0,'sl_SI','sl',0),(47,'so','Somali',0,0,'so_SO','so',0),(48,'sq','Albanian',0,0,'sq_AL','sq',0),(49,'sr','Serbian',0,0,'sr_RS','sr',0),(50,'sv','Swedish',0,0,'sv_SE','sv',0),(51,'ta','Tamil',0,0,'ta_IN','ta',0),(52,'th','Thai',0,0,'th','th',0),(53,'tr','Turkish',0,0,'tr_TR','tr',0),(54,'uk','Ukrainian',0,0,'uk','uk',0),(55,'ur','Urdu',0,0,'uz_UZ','ur',0),(56,'uz','Uzbek',0,0,'uz_UZ','uz',0),(57,'vi','Vietnamese',0,0,'vi_VN','vi',0),(58,'yi','Yiddish',0,0,'','yi',0),(59,'zh-hans','Chinese (Simplified)',1,0,'zh_CN','zh-hans',0),(60,'zu','Zulu',0,0,'','zu',0),(61,'zh-hant','Chinese (Traditional)',1,0,'zh_TW','zh-hant',0),(62,'ms','Malay',0,0,'ms_MY','ms',0),(63,'gl','Galician',0,0,'gl_ES','gl',0),(64,'bn','Bengali',0,0,'bn_BD','bn',0);

--
-- Table structure for table `wp_icl_languages_translations`
--

CREATE TABLE `wp_icl_languages_translations` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `language_code` varchar(7) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `display_language_code` varchar(7) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `name` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `language_code` (`language_code`,`display_language_code`)
) ENGINE=InnoDB AUTO_INCREMENT=4097 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_languages_translations`
--

INSERT INTO `wp_icl_languages_translations` VALUES (1,'en','en','English'),(2,'en','es','Inglés'),(3,'en','de','Englisch'),(4,'en','fr','Anglais'),(5,'en','ar','الإنجليزية'),(6,'en','bs','English'),(7,'en','bg','Английски'),(8,'en','ca','English'),(9,'en','cs','Angličtina'),(10,'en','sk','Angličtina'),(11,'en','cy','English'),(12,'en','da','English'),(13,'en','el','Αγγλικα'),(14,'en','eo','English'),(15,'en','et','English'),(16,'en','eu','English'),(17,'en','fa','English'),(18,'en','fi','englanti'),(19,'en','ga','English'),(20,'en','he','אנגלית'),(21,'en','hi','English'),(22,'en','hr','Engleski'),(23,'en','hu','angol'),(24,'en','hy','English'),(25,'en','id','English'),(26,'en','is','English'),(27,'en','it','Inglese'),(28,'en','ja','英語'),(29,'en','ko','영어'),(30,'en','ku','English'),(31,'en','lv','English'),(32,'en','lt','English'),(33,'en','mk','English'),(34,'en','mt','English'),(35,'en','mn','English'),(36,'en','ne','English'),(37,'en','nl','Engels'),(38,'en','no','Engelsk'),(39,'en','pa','English'),(40,'en','pl','angielski'),(41,'en','pt-pt','Inglês'),(42,'en','pt-br','Inglês'),(43,'en','qu','English'),(44,'en','ro','Engleză'),(45,'en','ru','Английский'),(46,'en','sl','Angleščina'),(47,'en','so','English'),(48,'en','sq','English'),(49,'en','sr','енглески'),(50,'en','sv','Engelska'),(51,'en','ta','English'),(52,'en','th','อังกฤษ'),(53,'en','tr','İngilizce'),(54,'en','uk','English'),(55,'en','ur','English'),(56,'en','uz','English'),(57,'en','vi','English'),(58,'en','yi','English'),(59,'en','zh-hans','英语'),(60,'en','zu','English'),(61,'en','zh-hant','英語'),(62,'en','ms','English'),(63,'en','gl','English'),(64,'en','bn','English'),(65,'es','en','Spanish'),(66,'es','es','Español'),(67,'es','de','Spanisch'),(68,'es','fr','Espagnol'),(69,'es','ar','الأسبانية'),(70,'es','bs','Spanish'),(71,'es','bg','Испански'),(72,'es','ca','Spanish'),(73,'es','cs','Španělský'),(74,'es','sk','Španielčina'),(75,'es','cy','Spanish'),(76,'es','da','Spanish'),(77,'es','el','Ισπανικα'),(78,'es','eo','Spanish'),(79,'es','et','Spanish'),(80,'es','eu','Spanish'),(81,'es','fa','Spanish'),(82,'es','fi','espanja'),(83,'es','ga','Spanish'),(84,'es','he','ספרדית'),(85,'es','hi','Spanish'),(86,'es','hr','španjolski'),(87,'es','hu','spanyol'),(88,'es','hy','Spanish'),(89,'es','id','Spanish'),(90,'es','is','Spanish'),(91,'es','it','Spagnolo'),(92,'es','ja','スペイン語'),(93,'es','ko','스페인어'),(94,'es','ku','Spanish'),(95,'es','lv','Spanish'),(96,'es','lt','Spanish'),(97,'es','mk','Spanish'),(98,'es','mt','Spanish'),(99,'es','mn','Spanish'),(100,'es','ne','Spanish'),(101,'es','nl','Spaans'),(102,'es','no','Spansk'),(103,'es','pa','Spanish'),(104,'es','pl','hiszpański'),(105,'es','pt-pt','Espanhol'),(106,'es','pt-br','Espanhol'),(107,'es','qu','Spanish'),(108,'es','ro','Spaniolă'),(109,'es','ru','Испанский'),(110,'es','sl','Španščina'),(111,'es','so','Spanish'),(112,'es','sq','Spanish'),(113,'es','sr','шпански'),(114,'es','sv','Spanska'),(115,'es','ta','Spanish'),(116,'es','th','สเปน'),(117,'es','tr','İspanyolca'),(118,'es','uk','Spanish'),(119,'es','ur','Spanish'),(120,'es','uz','Spanish'),(121,'es','vi','Spanish'),(122,'es','yi','Spanish'),(123,'es','zh-hans','西班牙语'),(124,'es','zu','Spanish'),(125,'es','zh-hant','西班牙語'),(126,'es','ms','Spanish'),(127,'es','gl','Spanish'),(128,'es','bn','Spanish'),(129,'de','en','German'),(130,'de','es','Alemán'),(131,'de','de','Deutsch'),(132,'de','fr','Allemand'),(133,'de','ar','الألمانية'),(134,'de','bs','German'),(135,'de','bg','Немски'),(136,'de','ca','German'),(137,'de','cs','Němec'),(138,'de','sk','Nemčina'),(139,'de','cy','German'),(140,'de','da','German'),(141,'de','el','Γερμανικα'),(142,'de','eo','German'),(143,'de','et','German'),(144,'de','eu','German'),(145,'de','fa','German'),(146,'de','fi','saksa'),(147,'de','ga','German'),(148,'de','he','גרמנית'),(149,'de','hi','German'),(150,'de','hr','Njemački'),(151,'de','hu','német'),(152,'de','hy','German'),(153,'de','id','German'),(154,'de','is','German'),(155,'de','it','Tedesco'),(156,'de','ja','ドイツ語'),(157,'de','ko','독어'),(158,'de','ku','German'),(159,'de','lv','German'),(160,'de','lt','German'),(161,'de','mk','German'),(162,'de','mt','German'),(163,'de','mn','German'),(164,'de','ne','German'),(165,'de','nl','Duits'),(166,'de','no','Tysk'),(167,'de','pa','German'),(168,'de','pl','niemiecki'),(169,'de','pt-pt','Alemão'),(170,'de','pt-br','Alemão'),(171,'de','qu','German'),(172,'de','ro','Germană'),(173,'de','ru','Немецкий'),(174,'de','sl','Nemščina'),(175,'de','so','German'),(176,'de','sq','German'),(177,'de','sr','немачки'),(178,'de','sv','Tyska'),(179,'de','ta','German'),(180,'de','th','เยอรมัน'),(181,'de','tr','Almanca'),(182,'de','uk','German'),(183,'de','ur','German'),(184,'de','uz','German'),(185,'de','vi','German'),(186,'de','yi','German'),(187,'de','zh-hans','德语'),(188,'de','zu','German'),(189,'de','zh-hant','德語'),(190,'de','ms','German'),(191,'de','gl','German'),(192,'de','bn','German'),(193,'fr','en','French'),(194,'fr','es','Francés'),(195,'fr','de','Französisch'),(196,'fr','fr','Français'),(197,'fr','ar','الفرنسية'),(198,'fr','bs','French'),(199,'fr','bg','Френски'),(200,'fr','ca','French'),(201,'fr','cs','Francouzština'),(202,'fr','sk','Francúzština'),(203,'fr','cy','French'),(204,'fr','da','French'),(205,'fr','el','Γαλλικα'),(206,'fr','eo','French'),(207,'fr','et','French'),(208,'fr','eu','French'),(209,'fr','fa','French'),(210,'fr','fi','ranska'),(211,'fr','ga','French'),(212,'fr','he','צרפתית'),(213,'fr','hi','French'),(214,'fr','hr','Francuzi'),(215,'fr','hu','francia'),(216,'fr','hy','French'),(217,'fr','id','French'),(218,'fr','is','French'),(219,'fr','it','Francese'),(220,'fr','ja','フランス語'),(221,'fr','ko','불어'),(222,'fr','ku','French'),(223,'fr','lv','French'),(224,'fr','lt','French'),(225,'fr','mk','French'),(226,'fr','mt','French'),(227,'fr','mn','French'),(228,'fr','ne','French'),(229,'fr','nl','Frans'),(230,'fr','no','Fransk'),(231,'fr','pa','French'),(232,'fr','pl','francuski'),(233,'fr','pt-pt','Francês'),(234,'fr','pt-br','Francês'),(235,'fr','qu','French'),(236,'fr','ro','Franceză'),(237,'fr','ru','Французский'),(238,'fr','sl','Francoščina'),(239,'fr','so','French'),(240,'fr','sq','French'),(241,'fr','sr','француски'),(242,'fr','sv','Franska'),(243,'fr','ta','French'),(244,'fr','th','ฝรั่งเศส'),(245,'fr','tr','Fransızca'),(246,'fr','uk','French'),(247,'fr','ur','French'),(248,'fr','uz','French'),(249,'fr','vi','French'),(250,'fr','yi','French'),(251,'fr','zh-hans','法语'),(252,'fr','zu','French'),(253,'fr','zh-hant','法語'),(254,'fr','ms','French'),(255,'fr','gl','French'),(256,'fr','bn','French'),(257,'ar','en','Arabic'),(258,'ar','es','Árabe'),(259,'ar','de','Arabisch'),(260,'ar','fr','Arabe'),(261,'ar','ar','العربية'),(262,'ar','bs','Arabic'),(263,'ar','bg','Арабски'),(264,'ar','ca','Arabic'),(265,'ar','cs','Arabština'),(266,'ar','sk','Arabčina'),(267,'ar','cy','Arabic'),(268,'ar','da','Arabic'),(269,'ar','el','Αραβικα'),(270,'ar','eo','Arabic'),(271,'ar','et','Arabic'),(272,'ar','eu','Arabic'),(273,'ar','fa','Arabic'),(274,'ar','fi','arabia'),(275,'ar','ga','Arabic'),(276,'ar','he','ערבית'),(277,'ar','hi','Arabic'),(278,'ar','hr','Arapski'),(279,'ar','hu','arab'),(280,'ar','hy','Arabic'),(281,'ar','id','Arabic'),(282,'ar','is','Arabic'),(283,'ar','it','Arabo'),(284,'ar','ja','アラビア語'),(285,'ar','ko','아랍어'),(286,'ar','ku','Arabic'),(287,'ar','lv','Arabic'),(288,'ar','lt','Arabic'),(289,'ar','mk','Arabic'),(290,'ar','mt','Arabic'),(291,'ar','mn','Arabic'),(292,'ar','ne','Arabic'),(293,'ar','nl','Arabisch'),(294,'ar','no','Arabisk'),(295,'ar','pa','Arabic'),(296,'ar','pl','arabski'),(297,'ar','pt-pt','Árabe'),(298,'ar','pt-br','Árabe'),(299,'ar','qu','Arabic'),(300,'ar','ro','Arabică'),(301,'ar','ru','Арабский'),(302,'ar','sl','Arabščina'),(303,'ar','so','Arabic'),(304,'ar','sq','Arabic'),(305,'ar','sr','арапски'),(306,'ar','sv','Arabiska'),(307,'ar','ta','Arabic'),(308,'ar','th','อารบิก'),(309,'ar','tr','Arapça'),(310,'ar','uk','Arabic'),(311,'ar','ur','Arabic'),(312,'ar','uz','Arabic'),(313,'ar','vi','Arabic'),(314,'ar','yi','Arabic'),(315,'ar','zh-hans','阿拉伯语'),(316,'ar','zu','Arabic'),(317,'ar','zh-hant','阿拉伯語'),(318,'ar','ms','Arabic'),(319,'ar','gl','Arabic'),(320,'ar','bn','Arabic'),(321,'bs','en','Bosnian'),(322,'bs','es','Bosnio'),(323,'bs','de','Bosnisch'),(324,'bs','fr','Bosnien'),(325,'bs','ar','البوسنية'),(326,'bs','bs','Bosnian'),(327,'bs','bg','Босненски'),(328,'bs','ca','Bosnian'),(329,'bs','cs','Bosenština'),(330,'bs','sk','Bosniačtina'),(331,'bs','cy','Bosnian'),(332,'bs','da','Bosnian'),(333,'bs','el','Βοσνιακα'),(334,'bs','eo','Bosnian'),(335,'bs','et','Bosnian'),(336,'bs','eu','Bosnian'),(337,'bs','fa','Bosnian'),(338,'bs','fi','bosnia'),(339,'bs','ga','Bosnian'),(340,'bs','he','בוסנית'),(341,'bs','hi','Bosnian'),(342,'bs','hr','Bosanski'),(343,'bs','hu','bosnyák'),(344,'bs','hy','Bosnian'),(345,'bs','id','Bosnian'),(346,'bs','is','Bosnian'),(347,'bs','it','Bosniaco'),(348,'bs','ja','ボスニア語'),(349,'bs','ko','보즈니아어'),(350,'bs','ku','Bosnian'),(351,'bs','lv','Bosnian'),(352,'bs','lt','Bosnian'),(353,'bs','mk','Bosnian'),(354,'bs','mt','Bosnian'),(355,'bs','mn','Bosnian'),(356,'bs','ne','Bosnian'),(357,'bs','nl','Bosnisch'),(358,'bs','no','Bosnisk'),(359,'bs','pa','Bosnian'),(360,'bs','pl','bośniacki'),(361,'bs','pt-pt','Bósnio'),(362,'bs','pt-br','Bósnio'),(363,'bs','qu','Bosnian'),(364,'bs','ro','Bosniacă'),(365,'bs','ru','Боснийский'),(366,'bs','sl','Bosanski'),(367,'bs','so','Bosnian'),(368,'bs','sq','Bosnian'),(369,'bs','sr','босански'),(370,'bs','sv','Bosniska'),(371,'bs','ta','Bosnian'),(372,'bs','th','บอสเนียน'),(373,'bs','tr','Boşnakça'),(374,'bs','uk','Bosnian'),(375,'bs','ur','Bosnian'),(376,'bs','uz','Bosnian'),(377,'bs','vi','Bosnian'),(378,'bs','yi','Bosnian'),(379,'bs','zh-hans','波斯尼亚语'),(380,'bs','zu','Bosnian'),(381,'bs','zh-hant','波士尼亞語'),(382,'bs','ms','Bosnian'),(383,'bs','gl','Bosnian'),(384,'bs','bn','Bosnian'),(385,'bg','en','Bulgarian'),(386,'bg','es','Búlgaro'),(387,'bg','de','Bulgarisch'),(388,'bg','fr','Bulgare'),(389,'bg','ar','البلغارية'),(390,'bg','bs','Bulgarian'),(391,'bg','bg','Български'),(392,'bg','ca','Bulgarian'),(393,'bg','cs','Bulharština'),(394,'bg','sk','Bulharčina'),(395,'bg','cy','Bulgarian'),(396,'bg','da','Bulgarian'),(397,'bg','el','Βουλγαρικα'),(398,'bg','eo','Bulgarian'),(399,'bg','et','Bulgarian'),(400,'bg','eu','Bulgarian'),(401,'bg','fa','Bulgarian'),(402,'bg','fi','bulgaria'),(403,'bg','ga','Bulgarian'),(404,'bg','he','בולגרית'),(405,'bg','hi','Bulgarian'),(406,'bg','hr','Bugarski'),(407,'bg','hu','bolgár'),(408,'bg','hy','Bulgarian'),(409,'bg','id','Bulgarian'),(410,'bg','is','Bulgarian'),(411,'bg','it','Bulgaro'),(412,'bg','ja','ブルガリア語'),(413,'bg','ko','불가리아어'),(414,'bg','ku','Bulgarian'),(415,'bg','lv','Bulgarian'),(416,'bg','lt','Bulgarian'),(417,'bg','mk','Bulgarian'),(418,'bg','mt','Bulgarian'),(419,'bg','mn','Bulgarian'),(420,'bg','ne','Bulgarian'),(421,'bg','nl','Bulgaars'),(422,'bg','no','Bulgarian'),(423,'bg','pa','Bulgarian'),(424,'bg','pl','bułgarski'),(425,'bg','pt-pt','Búlgaro'),(426,'bg','pt-br','Búlgaro'),(427,'bg','qu','Bulgarian'),(428,'bg','ro','Bulgară'),(429,'bg','ru','Болгарский'),(430,'bg','sl','Bolgarščina'),(431,'bg','so','Bulgarian'),(432,'bg','sq','Bulgarian'),(433,'bg','sr','бугарски'),(434,'bg','sv','Bulgariska'),(435,'bg','ta','Bulgarian'),(436,'bg','th','บัลแกเรียน'),(437,'bg','tr','Bulgarca'),(438,'bg','uk','Bulgarian'),(439,'bg','ur','Bulgarian'),(440,'bg','uz','Bulgarian'),(441,'bg','vi','Bulgarian'),(442,'bg','yi','Bulgarian'),(443,'bg','zh-hans','保加利亚语'),(444,'bg','zu','Bulgarian'),(445,'bg','zh-hant','保加利亞語'),(446,'bg','ms','Bulgarian'),(447,'bg','gl','Bulgarian'),(448,'bg','bn','Bulgarian'),(449,'ca','en','Catalan'),(450,'ca','es','Catalán'),(451,'ca','de','Katalanisch'),(452,'ca','fr','Catalan'),(453,'ca','ar','الكاتالوينية'),(454,'ca','bs','Catalan'),(455,'ca','bg','Каталонски'),(456,'ca','ca','Català'),(457,'ca','cs','Katalánština'),(458,'ca','sk','Katalánčina'),(459,'ca','cy','Catalan'),(460,'ca','da','Catalan'),(461,'ca','el','Καταλανικα'),(462,'ca','eo','Catalan'),(463,'ca','et','Catalan'),(464,'ca','eu','Catalan'),(465,'ca','fa','Catalan'),(466,'ca','fi','katalaani'),(467,'ca','ga','Catalan'),(468,'ca','he','קטלאנית'),(469,'ca','hi','Catalan'),(470,'ca','hr','Katalonski'),(471,'ca','hu','katalán'),(472,'ca','hy','Catalan'),(473,'ca','id','Catalan'),(474,'ca','is','Catalan'),(475,'ca','it','Catalano'),(476,'ca','ja','カタルーニャ語'),(477,'ca','ko','카탈로니아어'),(478,'ca','ku','Catalan'),(479,'ca','lv','Catalan'),(480,'ca','lt','Catalan'),(481,'ca','mk','Catalan'),(482,'ca','mt','Catalan'),(483,'ca','mn','Catalan'),(484,'ca','ne','Catalan'),(485,'ca','nl','Catalaans'),(486,'ca','no','catalan'),(487,'ca','pa','Catalan'),(488,'ca','pl','kataloński'),(489,'ca','pt-pt','Catalão'),(490,'ca','pt-br','Catalão'),(491,'ca','qu','Catalan'),(492,'ca','ro','Catalană'),(493,'ca','ru','Каталанский'),(494,'ca','sl','Katalonščina'),(495,'ca','so','Catalan'),(496,'ca','sq','Catalan'),(497,'ca','sr','каталонски'),(498,'ca','sv','Katalanska'),(499,'ca','ta','Catalan'),(500,'ca','th','คะตะลาน'),(501,'ca','tr','Katalan dili'),(502,'ca','uk','Catalan'),(503,'ca','ur','Catalan'),(504,'ca','uz','Catalan'),(505,'ca','vi','Catalan'),(506,'ca','yi','Catalan'),(507,'ca','zh-hans','加泰罗尼亚语'),(508,'ca','zu','Catalan'),(509,'ca','zh-hant','加泰羅尼亞語'),(510,'ca','ms','Catalan'),(511,'ca','gl','Catalan'),(512,'ca','bn','Catalan'),(513,'cs','en','Czech'),(514,'cs','es','Checo'),(515,'cs','de','Tschechisch'),(516,'cs','fr','Tchèque'),(517,'cs','ar','التشيكية'),(518,'cs','bs','Czech'),(519,'cs','bg','Чешки'),(520,'cs','ca','Czech'),(521,'cs','cs','Čeština'),(522,'cs','sk','Čeština'),(523,'cs','cy','Czech'),(524,'cs','da','Czech'),(525,'cs','el','Τσεχικη'),(526,'cs','eo','Czech'),(527,'cs','et','Czech'),(528,'cs','eu','Czech'),(529,'cs','fa','Czech'),(530,'cs','fi','tsekki'),(531,'cs','ga','Czech'),(532,'cs','he','צ\'כית'),(533,'cs','hi','Czech'),(534,'cs','hr','češki'),(535,'cs','hu','cseh'),(536,'cs','hy','Czech'),(537,'cs','id','Czech'),(538,'cs','is','Czech'),(539,'cs','it','Ceco'),(540,'cs','ja','チェコ語'),(541,'cs','ko','체코슬로바키아어'),(542,'cs','ku','Czech'),(543,'cs','lv','Czech'),(544,'cs','lt','Czech'),(545,'cs','mk','Czech'),(546,'cs','mt','Czech'),(547,'cs','mn','Czech'),(548,'cs','ne','Czech'),(549,'cs','nl','Tsjechisch'),(550,'cs','no','Czech'),(551,'cs','pa','Czech'),(552,'cs','pl','czeski'),(553,'cs','pt-pt','Tcheco'),(554,'cs','pt-br','Tcheco'),(555,'cs','qu','Czech'),(556,'cs','ro','Cehă'),(557,'cs','ru','Чешский'),(558,'cs','sl','Češčina'),(559,'cs','so','Czech'),(560,'cs','sq','Czech'),(561,'cs','sr','чешки'),(562,'cs','sv','Tjeckiska'),(563,'cs','ta','Czech'),(564,'cs','th','เช็ก'),(565,'cs','tr','Çekçe'),(566,'cs','uk','Czech'),(567,'cs','ur','Czech'),(568,'cs','uz','Czech'),(569,'cs','vi','Czech'),(570,'cs','yi','Czech'),(571,'cs','zh-hans','捷克语'),(572,'cs','zu','Czech'),(573,'cs','zh-hant','捷克語'),(574,'cs','ms','Czech'),(575,'cs','gl','Czech'),(576,'cs','bn','Czech'),(577,'sk','en','Slovak'),(578,'sk','es','Eslavo'),(579,'sk','de','Slowakisch'),(580,'sk','fr','Slave'),(581,'sk','ar','السلافية'),(582,'sk','bs','Slovak'),(583,'sk','bg','Словашки'),(584,'sk','ca','Slovak'),(585,'sk','cs','Slovenština'),(586,'sk','sk','Slovenčina'),(587,'sk','cy','Slovak'),(588,'sk','da','Slovak'),(589,'sk','el','Σλαβικη'),(590,'sk','eo','Slovak'),(591,'sk','et','Slovak'),(592,'sk','eu','Slovak'),(593,'sk','fa','Slovak'),(594,'sk','fi','slaavi'),(595,'sk','ga','Slovak'),(596,'sk','he','סלאבית'),(597,'sk','hi','Slovak'),(598,'sk','hr','Slovak'),(599,'sk','hu','szláv'),(600,'sk','hy','Slovak'),(601,'sk','id','Slovak'),(602,'sk','is','Slovak'),(603,'sk','it','Slavo'),(604,'sk','ja','スラヴ語派'),(605,'sk','ko','슬라브어'),(606,'sk','ku','Slovak'),(607,'sk','lv','Slovak'),(608,'sk','lt','Slovak'),(609,'sk','mk','Slovak'),(610,'sk','mt','Slovak'),(611,'sk','mn','Slovak'),(612,'sk','ne','Slovak'),(613,'sk','nl','Slavisch'),(614,'sk','no','Slovak'),(615,'sk','pa','Slovak'),(616,'sk','pl','słowacki'),(617,'sk','pt-pt','Eslavo'),(618,'sk','pt-br','Eslavo'),(619,'sk','qu','Slovak'),(620,'sk','ro','Slavă'),(621,'sk','ru','Славянский'),(622,'sk','sl','Slovaščina'),(623,'sk','so','Slovak'),(624,'sk','sq','Slovak'),(625,'sk','sr','словачки'),(626,'sk','sv','Slavisk'),(627,'sk','ta','Slovak'),(628,'sk','th','สลาวิก'),(629,'sk','tr','Slav dili'),(630,'sk','uk','Slovak'),(631,'sk','ur','Slovak'),(632,'sk','uz','Slovak'),(633,'sk','vi','Slovak'),(634,'sk','yi','Slovak'),(635,'sk','zh-hans','斯拉夫语'),(636,'sk','zu','Slovak'),(637,'sk','zh-hant','斯拉夫語'),(638,'sk','ms','Slovak'),(639,'sk','gl','Slovak'),(640,'sk','bn','Slovak'),(641,'cy','en','Welsh'),(642,'cy','es','Galés'),(643,'cy','de','Walisisch'),(644,'cy','fr','Gallois'),(645,'cy','ar','الولزية'),(646,'cy','bs','Welsh'),(647,'cy','bg','Уелски'),(648,'cy','ca','Welsh'),(649,'cy','cs','Velšský'),(650,'cy','sk','Welština'),(651,'cy','cy','Cymraeg'),(652,'cy','da','Welsh'),(653,'cy','el','Welsh'),(654,'cy','eo','Welsh'),(655,'cy','et','Welsh'),(656,'cy','eu','Welsh'),(657,'cy','fa','Welsh'),(658,'cy','fi','kymri'),(659,'cy','ga','Welsh'),(660,'cy','he','וולשית'),(661,'cy','hi','Welsh'),(662,'cy','hr','Velški'),(663,'cy','hu','vels'),(664,'cy','hy','Welsh'),(665,'cy','id','Welsh'),(666,'cy','is','Welsh'),(667,'cy','it','Gallese'),(668,'cy','ja','ウェールズ語'),(669,'cy','ko','웨일즈어'),(670,'cy','ku','Welsh'),(671,'cy','lv','Welsh'),(672,'cy','lt','Welsh'),(673,'cy','mk','Welsh'),(674,'cy','mt','Welsh'),(675,'cy','mn','Welsh'),(676,'cy','ne','Welsh'),(677,'cy','nl','Welsh'),(678,'cy','no','Welsh'),(679,'cy','pa','Welsh'),(680,'cy','pl','walijski'),(681,'cy','pt-pt','Galês'),(682,'cy','pt-br','Galês'),(683,'cy','qu','Welsh'),(684,'cy','ro','Galeză'),(685,'cy','ru','Валлийский'),(686,'cy','sl','Welsh'),(687,'cy','so','Welsh'),(688,'cy','sq','Welsh'),(689,'cy','sr','велшки'),(690,'cy','sv','Walesiska'),(691,'cy','ta','Welsh'),(692,'cy','th','เวลช์'),(693,'cy','tr','Galce'),(694,'cy','uk','Welsh'),(695,'cy','ur','Welsh'),(696,'cy','uz','Welsh'),(697,'cy','vi','Welsh'),(698,'cy','yi','Welsh'),(699,'cy','zh-hans','威尔士语'),(700,'cy','zu','Welsh'),(701,'cy','zh-hant','威爾士語'),(702,'cy','ms','Welsh'),(703,'cy','gl','Welsh'),(704,'cy','bn','Welsh'),(705,'da','en','Danish'),(706,'da','es','Danés'),(707,'da','de','Dänisch'),(708,'da','fr','Danois'),(709,'da','ar','الدانماركية'),(710,'da','bs','Danish'),(711,'da','bg','Датски'),(712,'da','ca','Danish'),(713,'da','cs','Dánský'),(714,'da','sk','Dánčina'),(715,'da','cy','Danish'),(716,'da','da','Dansk'),(717,'da','el','Δανεζικα'),(718,'da','eo','Danish'),(719,'da','et','Danish'),(720,'da','eu','Danish'),(721,'da','fa','Danish'),(722,'da','fi','tanska'),(723,'da','ga','Danish'),(724,'da','he','דנית'),(725,'da','hi','Danish'),(726,'da','hr','Danski'),(727,'da','hu','dán'),(728,'da','hy','Danish'),(729,'da','id','Danish'),(730,'da','is','Danish'),(731,'da','it','Danese'),(732,'da','ja','デンマーク語'),(733,'da','ko','덴마크어'),(734,'da','ku','Danish'),(735,'da','lv','Danish'),(736,'da','lt','Danish'),(737,'da','mk','Danish'),(738,'da','mt','Danish'),(739,'da','mn','Danish'),(740,'da','ne','Danish'),(741,'da','nl','Deens'),(742,'da','no','Danish'),(743,'da','pa','Danish'),(744,'da','pl','duński'),(745,'da','pt-pt','Dinamarquês'),(746,'da','pt-br','Dinamarquês'),(747,'da','qu','Danish'),(748,'da','ro','Daneză'),(749,'da','ru','Датский'),(750,'da','sl','Danščina'),(751,'da','so','Danish'),(752,'da','sq','Danish'),(753,'da','sr','дански'),(754,'da','sv','Danska'),(755,'da','ta','Danish'),(756,'da','th','เดนมาร์ก'),(757,'da','tr','Danca'),(758,'da','uk','Danish'),(759,'da','ur','Danish'),(760,'da','uz','Danish'),(761,'da','vi','Danish'),(762,'da','yi','Danish'),(763,'da','zh-hans','丹麦语'),(764,'da','zu','Danish'),(765,'da','zh-hant','丹麥語'),(766,'da','ms','Danish'),(767,'da','gl','Danish'),(768,'da','bn','Danish'),(769,'el','en','Greek'),(770,'el','es','Griego'),(771,'el','de','Griechisch'),(772,'el','fr','Grec moderne'),(773,'el','ar','اليونانية'),(774,'el','bs','Greek'),(775,'el','bg','Гръцки'),(776,'el','ca','Greek'),(777,'el','cs','Řečtina'),(778,'el','sk','Gréčtina'),(779,'el','cy','Greek'),(780,'el','da','Greek'),(781,'el','el','Ελληνικα'),(782,'el','eo','Greek'),(783,'el','et','Greek'),(784,'el','eu','Greek'),(785,'el','fa','Greek'),(786,'el','fi','kreikka'),(787,'el','ga','Greek'),(788,'el','he','יוונית'),(789,'el','hi','Greek'),(790,'el','hr','Grčki'),(791,'el','hu','görög'),(792,'el','hy','Greek'),(793,'el','id','Greek'),(794,'el','is','Greek'),(795,'el','it','Greco'),(796,'el','ja','ギリシア語'),(797,'el','ko','그리스어'),(798,'el','ku','Greek'),(799,'el','lv','Greek'),(800,'el','lt','Greek'),(801,'el','mk','Greek'),(802,'el','mt','Greek'),(803,'el','mn','Greek'),(804,'el','ne','Greek'),(805,'el','nl','Grieks'),(806,'el','no','Gresk'),(807,'el','pa','Greek'),(808,'el','pl','grecki'),(809,'el','pt-pt','Grego'),(810,'el','pt-br','Grego'),(811,'el','qu','Greek'),(812,'el','ro','Greacă'),(813,'el','ru','Греческий'),(814,'el','sl','Greek'),(815,'el','so','Greek'),(816,'el','sq','Greek'),(817,'el','sr','грчки'),(818,'el','sv','Grekiska'),(819,'el','ta','Greek'),(820,'el','th','กรีก'),(821,'el','tr','Yunanca'),(822,'el','uk','Greek'),(823,'el','ur','Greek'),(824,'el','uz','Greek'),(825,'el','vi','Greek'),(826,'el','yi','Greek'),(827,'el','zh-hans','希腊语'),(828,'el','zu','Greek'),(829,'el','zh-hant','希臘語'),(830,'el','ms','Greek'),(831,'el','gl','Greek'),(832,'el','bn','Greek'),(833,'eo','en','Esperanto'),(834,'eo','es','Esperanto'),(835,'eo','de','Esperanto'),(836,'eo','fr','Espéranto'),(837,'eo','ar','الاسبرانتو'),(838,'eo','bs','Esperanto'),(839,'eo','bg','Есперанто'),(840,'eo','ca','Esperanto'),(841,'eo','cs','Esperanto'),(842,'eo','sk','Esperanto'),(843,'eo','cy','Esperanto'),(844,'eo','da','Esperanto'),(845,'eo','el','Εσπεραντο'),(846,'eo','eo','Esperanta'),(847,'eo','et','Esperanto'),(848,'eo','eu','Esperanto'),(849,'eo','fa','Esperanto'),(850,'eo','fi','esperanto'),(851,'eo','ga','Esperanto'),(852,'eo','he','אספרנטו'),(853,'eo','hi','Esperanto'),(854,'eo','hr','Esperanto'),(855,'eo','hu','eszperantó'),(856,'eo','hy','Esperanto'),(857,'eo','id','Esperanto'),(858,'eo','is','Esperanto'),(859,'eo','it','Esperanto'),(860,'eo','ja','エスペラント語'),(861,'eo','ko','에스페란토어'),(862,'eo','ku','Esperanto'),(863,'eo','lv','Esperanto'),(864,'eo','lt','Esperanto'),(865,'eo','mk','Esperanto'),(866,'eo','mt','Esperanto'),(867,'eo','mn','Esperanto'),(868,'eo','ne','Esperanto'),(869,'eo','nl','Esperanto'),(870,'eo','no','Esperanto'),(871,'eo','pa','Esperanto'),(872,'eo','pl','esperanto'),(873,'eo','pt-pt','Esperanto'),(874,'eo','pt-br','Esperanto'),(875,'eo','qu','Esperanto'),(876,'eo','ro','Esperanto'),(877,'eo','ru','Эсперанто'),(878,'eo','sl','Esperanto'),(879,'eo','so','Esperanto'),(880,'eo','sq','Esperanto'),(881,'eo','sr','есперанто'),(882,'eo','sv','Esperanto'),(883,'eo','ta','Esperanto'),(884,'eo','th','เอสเปอรันโต'),(885,'eo','tr','Esperanto'),(886,'eo','uk','Esperanto'),(887,'eo','ur','Esperanto'),(888,'eo','uz','Esperanto'),(889,'eo','vi','Esperanto'),(890,'eo','yi','Esperanto'),(891,'eo','zh-hans','世界语'),(892,'eo','zu','Esperanto'),(893,'eo','zh-hant','世界語'),(894,'eo','ms','Esperanto'),(895,'eo','gl','Esperanto'),(896,'eo','bn','Esperanto'),(897,'et','en','Estonian'),(898,'et','es','Estonio'),(899,'et','de','Estnisch'),(900,'et','fr','Estonien'),(901,'et','ar','الأستونية'),(902,'et','bs','Estonian'),(903,'et','bg','Естонски'),(904,'et','ca','Estonian'),(905,'et','cs','Estonština'),(906,'et','sk','Estónčina'),(907,'et','cy','Estonian'),(908,'et','da','Estonian'),(909,'et','el','Εσθονικα'),(910,'et','eo','Estonian'),(911,'et','et','Eesti'),(912,'et','eu','Estonian'),(913,'et','fa','Estonian'),(914,'et','fi','eesti'),(915,'et','ga','Estonian'),(916,'et','he','אסטונית'),(917,'et','hi','Estonian'),(918,'et','hr','Estonski'),(919,'et','hu','észt'),(920,'et','hy','Estonian'),(921,'et','id','Estonian'),(922,'et','is','Estonian'),(923,'et','it','Estone'),(924,'et','ja','エストニア語'),(925,'et','ko','에스토니아어'),(926,'et','ku','Estonian'),(927,'et','lv','Estonian'),(928,'et','lt','Estonian'),(929,'et','mk','Estonian'),(930,'et','mt','Estonian'),(931,'et','mn','Estonian'),(932,'et','ne','Estonian'),(933,'et','nl','Ests'),(934,'et','no','Estonian'),(935,'et','pa','Estonian'),(936,'et','pl','estoński'),(937,'et','pt-pt','Estoniano'),(938,'et','pt-br','Estoniano'),(939,'et','qu','Estonian'),(940,'et','ro','Estoniană'),(941,'et','ru','Эстонский'),(942,'et','sl','Estonščina'),(943,'et','so','Estonian'),(944,'et','sq','Estonian'),(945,'et','sr','естонски'),(946,'et','sv','Estniska'),(947,'et','ta','Estonian'),(948,'et','th','เอสโตเนียน'),(949,'et','tr','Estonya dili'),(950,'et','uk','Estonian'),(951,'et','ur','Estonian'),(952,'et','uz','Estonian'),(953,'et','vi','Estonian'),(954,'et','yi','Estonian'),(955,'et','zh-hans','爱沙尼亚语'),(956,'et','zu','Estonian'),(957,'et','zh-hant','愛沙尼亞語'),(958,'et','ms','Estonian'),(959,'et','gl','Estonian'),(960,'et','bn','Estonian'),(961,'eu','en','Basque'),(962,'eu','es','Euskera'),(963,'eu','de','Baskisch'),(964,'eu','fr','Basque'),(965,'eu','ar','لغة الباسك'),(966,'eu','bs','Basque'),(967,'eu','bg','Баски'),(968,'eu','ca','Basque'),(969,'eu','cs','Basque'),(970,'eu','sk','Baskičtina'),(971,'eu','cy','Basque'),(972,'eu','da','Basque'),(973,'eu','el','Βασκικα'),(974,'eu','eo','Basque'),(975,'eu','et','Basque'),(976,'eu','eu','Euskara'),(977,'eu','fa','Basque'),(978,'eu','fi','baski'),(979,'eu','ga','Basque'),(980,'eu','he','בסקית'),(981,'eu','hi','Basque'),(982,'eu','hr','Baskijski'),(983,'eu','hu','baszk'),(984,'eu','hy','Basque'),(985,'eu','id','Basque'),(986,'eu','is','Basque'),(987,'eu','it','Basco'),(988,'eu','ja','バスク語'),(989,'eu','ko','바스크어'),(990,'eu','ku','Basque'),(991,'eu','lv','Basque'),(992,'eu','lt','Basque'),(993,'eu','mk','Basque'),(994,'eu','mt','Basque'),(995,'eu','mn','Basque'),(996,'eu','ne','Basque'),(997,'eu','nl','Baskisch'),(998,'eu','no','Basque'),(999,'eu','pa','Basque'),(1000,'eu','pl','baskijski'),(1001,'eu','pt-pt','Basco'),(1002,'eu','pt-br','Basco'),(1003,'eu','qu','Basque'),(1004,'eu','ro','Bască'),(1005,'eu','ru','Баскский'),(1006,'eu','sl','Baskovščina'),(1007,'eu','so','Basque'),(1008,'eu','sq','Basque'),(1009,'eu','sr','баскијски'),(1010,'eu','sv','Baskiska'),(1011,'eu','ta','Basque'),(1012,'eu','th','บาสค์'),(1013,'eu','tr','Bask dili'),(1014,'eu','uk','Basque'),(1015,'eu','ur','Basque'),(1016,'eu','uz','Basque'),(1017,'eu','vi','Basque'),(1018,'eu','yi','Basque'),(1019,'eu','zh-hans','巴斯克语'),(1020,'eu','zu','Basque'),(1021,'eu','zh-hant','巴斯克語'),(1022,'eu','ms','Basque'),(1023,'eu','gl','Basque'),(1024,'eu','bn','Basque'),(1025,'fa','en','Persian'),(1026,'fa','es','Persa'),(1027,'fa','de','Persisch'),(1028,'fa','fr','Perse'),(1029,'fa','ar','الفارسية'),(1030,'fa','bs','Persian'),(1031,'fa','bg','Персийски'),(1032,'fa','ca','Persian'),(1033,'fa','cs','Perský'),(1034,'fa','sk','Perzština'),(1035,'fa','cy','Persian'),(1036,'fa','da','Persian'),(1037,'fa','el','Περσικος'),(1038,'fa','eo','Persian'),(1039,'fa','et','Persian'),(1040,'fa','eu','Persian'),(1041,'fa','fa','فارسی'),(1042,'fa','fi','persia'),(1043,'fa','ga','Persian'),(1044,'fa','he','פרסית'),(1045,'fa','hi','Persian'),(1046,'fa','hr','Perzijski'),(1047,'fa','hu','perzsa'),(1048,'fa','hy','Persian'),(1049,'fa','id','Persian'),(1050,'fa','is','Persian'),(1051,'fa','it','Persiano'),(1052,'fa','ja','ペルシア語'),(1053,'fa','ko','페르시아어'),(1054,'fa','ku','Persian'),(1055,'fa','lv','Persian'),(1056,'fa','lt','Persian'),(1057,'fa','mk','Persian'),(1058,'fa','mt','Persian'),(1059,'fa','mn','Persian'),(1060,'fa','ne','Persian'),(1061,'fa','nl','Perzisch'),(1062,'fa','no','Persisk'),(1063,'fa','pa','Persian'),(1064,'fa','pl','perski'),(1065,'fa','pt-pt','Persa'),(1066,'fa','pt-br','Persa'),(1067,'fa','qu','Persian'),(1068,'fa','ro','Persană'),(1069,'fa','ru','Персидский'),(1070,'fa','sl','Perzijski'),(1071,'fa','so','Persian'),(1072,'fa','sq','Persian'),(1073,'fa','sr','персијски'),(1074,'fa','sv','Persiska'),(1075,'fa','ta','Persian'),(1076,'fa','th','เปอร์เซียน'),(1077,'fa','tr','Farsça'),(1078,'fa','uk','Persian'),(1079,'fa','ur','Persian'),(1080,'fa','uz','Persian'),(1081,'fa','vi','Persian'),(1082,'fa','yi','Persian'),(1083,'fa','zh-hans','波斯语'),(1084,'fa','zu','Persian'),(1085,'fa','zh-hant','波斯語'),(1086,'fa','ms','Persian'),(1087,'fa','gl','Persian'),(1088,'fa','bn','Persian'),(1089,'fi','en','Finnish'),(1090,'fi','es','Finlandés'),(1091,'fi','de','Finnisch'),(1092,'fi','fr','Finnois'),(1093,'fi','ar','الفنلندية'),(1094,'fi','bs','Finnish'),(1095,'fi','bg','Фински'),(1096,'fi','ca','Finnish'),(1097,'fi','cs','Finský'),(1098,'fi','sk','Fínština'),(1099,'fi','cy','Finnish'),(1100,'fi','da','Finnish'),(1101,'fi','el','Φινλανδικη'),(1102,'fi','eo','Finnish'),(1103,'fi','et','Finnish'),(1104,'fi','eu','Finnish'),(1105,'fi','fa','Finnish'),(1106,'fi','fi','Suomi'),(1107,'fi','ga','Finnish'),(1108,'fi','he','פינית'),(1109,'fi','hi','Finnish'),(1110,'fi','hr','Finski'),(1111,'fi','hu','finn'),(1112,'fi','hy','Finnish'),(1113,'fi','id','Finnish'),(1114,'fi','is','Finnish'),(1115,'fi','it','Finlandese'),(1116,'fi','ja','フィンランド語'),(1117,'fi','ko','핀란드어'),(1118,'fi','ku','Finnish'),(1119,'fi','lv','Finnish'),(1120,'fi','lt','Finnish'),(1121,'fi','mk','Finnish'),(1122,'fi','mt','Finnish'),(1123,'fi','mn','Finnish'),(1124,'fi','ne','Finnish'),(1125,'fi','nl','Fins'),(1126,'fi','no','Finsk'),(1127,'fi','pa','Finnish'),(1128,'fi','pl','fiński'),(1129,'fi','pt-pt','Finlandês'),(1130,'fi','pt-br','Finlandês'),(1131,'fi','qu','Finnish'),(1132,'fi','ro','Finlandeză'),(1133,'fi','ru','Финский'),(1134,'fi','sl','Finski'),(1135,'fi','so','Finnish'),(1136,'fi','sq','Finnish'),(1137,'fi','sr','фински'),(1138,'fi','sv','Finska'),(1139,'fi','ta','Finnish'),(1140,'fi','th','ฟินนิช'),(1141,'fi','tr','Fince'),(1142,'fi','uk','Finnish'),(1143,'fi','ur','Finnish'),(1144,'fi','uz','Finnish'),(1145,'fi','vi','Finnish'),(1146,'fi','yi','Finnish'),(1147,'fi','zh-hans','芬兰语'),(1148,'fi','zu','Finnish'),(1149,'fi','zh-hant','芬蘭語'),(1150,'fi','ms','Finnish'),(1151,'fi','gl','Finnish'),(1152,'fi','bn','Finnish'),(1153,'ga','en','Irish'),(1154,'ga','es','Irlandés'),(1155,'ga','de','Irisch'),(1156,'ga','fr','Irlandais'),(1157,'ga','ar','الأيرلندية'),(1158,'ga','bs','Irish'),(1159,'ga','bg','Ирландски'),(1160,'ga','ca','Irish'),(1161,'ga','cs','Irský'),(1162,'ga','sk','Írština'),(1163,'ga','cy','Irish'),(1164,'ga','da','Irish'),(1165,'ga','el','Ιρλανδικα'),(1166,'ga','eo','Irish'),(1167,'ga','et','Irish'),(1168,'ga','eu','Irish'),(1169,'ga','fa','Irish'),(1170,'ga','fi','iiri'),(1171,'ga','ga','Gaeilge'),(1172,'ga','he','אירית'),(1173,'ga','hi','Irish'),(1174,'ga','hr','Irci'),(1175,'ga','hu','ír'),(1176,'ga','hy','Irish'),(1177,'ga','id','Irish'),(1178,'ga','is','Irish'),(1179,'ga','it','Irlandese'),(1180,'ga','ja','アイルランド語'),(1181,'ga','ko','아일랜드어'),(1182,'ga','ku','Irish'),(1183,'ga','lv','Irish'),(1184,'ga','lt','Irish'),(1185,'ga','mk','Irish'),(1186,'ga','mt','Irish'),(1187,'ga','mn','Irish'),(1188,'ga','ne','Irish'),(1189,'ga','nl','Iers'),(1190,'ga','no','Irish'),(1191,'ga','pa','Irish'),(1192,'ga','pl','irlandzki'),(1193,'ga','pt-pt','Irlandês'),(1194,'ga','pt-br','Irlandês'),(1195,'ga','qu','Irish'),(1196,'ga','ro','Irlandeză'),(1197,'ga','ru','Ирландский'),(1198,'ga','sl','Irski'),(1199,'ga','so','Irish'),(1200,'ga','sq','Irish'),(1201,'ga','sr','ирски'),(1202,'ga','sv','Irländska'),(1203,'ga','ta','Irish'),(1204,'ga','th','ไอริช'),(1205,'ga','tr','İrlanda dili'),(1206,'ga','uk','Irish'),(1207,'ga','ur','Irish'),(1208,'ga','uz','Irish'),(1209,'ga','vi','Irish'),(1210,'ga','yi','Irish'),(1211,'ga','zh-hans','爱尔兰语'),(1212,'ga','zu','Irish'),(1213,'ga','zh-hant','愛爾蘭語'),(1214,'ga','ms','Irish'),(1215,'ga','gl','Irish'),(1216,'ga','bn','Irish'),(1217,'he','en','Hebrew'),(1218,'he','es','Hebreo'),(1219,'he','de','Hebräisch'),(1220,'he','fr','Hébreu'),(1221,'he','ar','العبرية'),(1222,'he','bs','Hebrew'),(1223,'he','bg','Иврит'),(1224,'he','ca','Hebrew'),(1225,'he','cs','Hebrejština'),(1226,'he','sk','Hebrejčina'),(1227,'he','cy','Hebrew'),(1228,'he','da','Hebrew'),(1229,'he','el','Εβραικα'),(1230,'he','eo','Hebrew'),(1231,'he','et','Hebrew'),(1232,'he','eu','Hebrew'),(1233,'he','fa','Hebrew'),(1234,'he','fi','heprea'),(1235,'he','ga','Hebrew'),(1236,'he','he','עברית'),(1237,'he','hi','Hebrew'),(1238,'he','hr','Hebrejski'),(1239,'he','hu','héber'),(1240,'he','hy','Hebrew'),(1241,'he','id','Hebrew'),(1242,'he','is','Hebrew'),(1243,'he','it','Ebraico'),(1244,'he','ja','ヘブライ語'),(1245,'he','ko','히브리어'),(1246,'he','ku','Hebrew'),(1247,'he','lv','Hebrew'),(1248,'he','lt','Hebrew'),(1249,'he','mk','Hebrew'),(1250,'he','mt','Hebrew'),(1251,'he','mn','Hebrew'),(1252,'he','ne','Hebrew'),(1253,'he','nl','Hebreeuws'),(1254,'he','no','Hebraisk'),(1255,'he','pa','Hebrew'),(1256,'he','pl','hebrajski'),(1257,'he','pt-pt','Hebraico'),(1258,'he','pt-br','Hebraico'),(1259,'he','qu','Hebrew'),(1260,'he','ro','Ebraică'),(1261,'he','ru','Иврит'),(1262,'he','sl','Hebrejščina'),(1263,'he','so','Hebrew'),(1264,'he','sq','Hebrew'),(1265,'he','sr','Хебрејски'),(1266,'he','sv','Hebreiska'),(1267,'he','ta','Hebrew'),(1268,'he','th','ฮิบรู'),(1269,'he','tr','İbranice'),(1270,'he','uk','Hebrew'),(1271,'he','ur','Hebrew'),(1272,'he','uz','Hebrew'),(1273,'he','vi','Hebrew'),(1274,'he','yi','Hebrew'),(1275,'he','zh-hans','希伯来语'),(1276,'he','zu','Hebrew'),(1277,'he','zh-hant','希伯來語'),(1278,'he','ms','Hebrew'),(1279,'he','gl','Hebrew'),(1280,'he','bn','Hebrew'),(1281,'hi','en','Hindi'),(1282,'hi','es','Hindi'),(1283,'hi','de','Hindi'),(1284,'hi','fr','Hindi'),(1285,'hi','ar','الهندية'),(1286,'hi','bs','Hindi'),(1287,'hi','bg','Хинди'),(1288,'hi','ca','Hindi'),(1289,'hi','cs','Hindština'),(1290,'hi','sk','Hindčina'),(1291,'hi','cy','Hindi'),(1292,'hi','da','Hindi'),(1293,'hi','el','Ινδικα'),(1294,'hi','eo','Hindi'),(1295,'hi','et','Hindi'),(1296,'hi','eu','Hindi'),(1297,'hi','fa','Hindi'),(1298,'hi','fi','hindi'),(1299,'hi','ga','Hindi'),(1300,'hi','he','הודית'),(1301,'hi','hi','हिन्दी'),(1302,'hi','hr','Hindski'),(1303,'hi','hu','hindi'),(1304,'hi','hy','Hindi'),(1305,'hi','id','Hindi'),(1306,'hi','is','Hindi'),(1307,'hi','it','Hindi'),(1308,'hi','ja','ヒンディー語'),(1309,'hi','ko','힌두어'),(1310,'hi','ku','Hindi'),(1311,'hi','lv','Hindi'),(1312,'hi','lt','Hindi'),(1313,'hi','mk','Hindi'),(1314,'hi','mt','Hindi'),(1315,'hi','mn','Hindi'),(1316,'hi','ne','Hindi'),(1317,'hi','nl','Hindi'),(1318,'hi','no','Hindi'),(1319,'hi','pa','Hindi'),(1320,'hi','pl','hindi'),(1321,'hi','pt-pt','Hindi'),(1322,'hi','pt-br','Hindi'),(1323,'hi','qu','Hindi'),(1324,'hi','ro','Hindi'),(1325,'hi','ru','Хинди'),(1326,'hi','sl','Hindi'),(1327,'hi','so','Hindi'),(1328,'hi','sq','Hindi'),(1329,'hi','sr','хинди'),(1330,'hi','sv','Hindi'),(1331,'hi','ta','Hindi'),(1332,'hi','th','ฮินดิ'),(1333,'hi','tr','Hintçe'),(1334,'hi','uk','Hindi'),(1335,'hi','ur','Hindi'),(1336,'hi','uz','Hindi'),(1337,'hi','vi','Hindi'),(1338,'hi','yi','Hindi'),(1339,'hi','zh-hans','印地语'),(1340,'hi','zu','Hindi'),(1341,'hi','zh-hant','印地語'),(1342,'hi','ms','Hindi'),(1343,'hi','gl','Hindi'),(1344,'hi','bn','Hindi'),(1345,'hr','en','Croatian'),(1346,'hr','es','Croata'),(1347,'hr','de','Kroatisch'),(1348,'hr','fr','Croate'),(1349,'hr','ar','الكرواتية'),(1350,'hr','bs','Croatian'),(1351,'hr','bg','Хърватски'),(1352,'hr','ca','Croatian'),(1353,'hr','cs','Chorvatský'),(1354,'hr','sk','Chorvátština'),(1355,'hr','cy','Croatian'),(1356,'hr','da','Croatian'),(1357,'hr','el','Κροατικα'),(1358,'hr','eo','Croatian'),(1359,'hr','et','Croatian'),(1360,'hr','eu','Croatian'),(1361,'hr','fa','Croatian'),(1362,'hr','fi','kroatia'),(1363,'hr','ga','Croatian'),(1364,'hr','he','קרוטאית'),(1365,'hr','hi','Croatian'),(1366,'hr','hr','Hrvatski'),(1367,'hr','hu','horvát'),(1368,'hr','hy','Croatian'),(1369,'hr','id','Croatian'),(1370,'hr','is','Croatian'),(1371,'hr','it','Croato'),(1372,'hr','ja','クロアチア語'),(1373,'hr','ko','크로아시아어'),(1374,'hr','ku','Croatian'),(1375,'hr','lv','Croatian'),(1376,'hr','lt','Croatian'),(1377,'hr','mk','Croatian'),(1378,'hr','mt','Croatian'),(1379,'hr','mn','Croatian'),(1380,'hr','ne','Croatian'),(1381,'hr','nl','Kroatisch'),(1382,'hr','no','Kroatisk'),(1383,'hr','pa','Croatian'),(1384,'hr','pl','chorwacki'),(1385,'hr','pt-pt','Croata'),(1386,'hr','pt-br','Croata'),(1387,'hr','qu','Croatian'),(1388,'hr','ro','Croată'),(1389,'hr','ru','Хорватский'),(1390,'hr','sl','Hrvaški'),(1391,'hr','so','Croatian'),(1392,'hr','sq','Croatian'),(1393,'hr','sr','хрватски'),(1394,'hr','sv','Kroatiska'),(1395,'hr','ta','Croatian'),(1396,'hr','th','โครเอเชีย'),(1397,'hr','tr','Hırvatça'),(1398,'hr','uk','Croatian'),(1399,'hr','ur','Croatian'),(1400,'hr','uz','Croatian'),(1401,'hr','vi','Croatian'),(1402,'hr','yi','Croatian'),(1403,'hr','zh-hans','克罗地亚语'),(1404,'hr','zu','Croatian'),(1405,'hr','zh-hant','克羅地亞語'),(1406,'hr','ms','Croatian'),(1407,'hr','gl','Croatian'),(1408,'hr','bn','Croatian'),(1409,'hu','en','Hungarian'),(1410,'hu','es','Húngaro'),(1411,'hu','de','Ungarisch'),(1412,'hu','fr','Hongrois'),(1413,'hu','ar','الهنغارية'),(1414,'hu','bs','Hungarian'),(1415,'hu','bg','Унгарски'),(1416,'hu','ca','Hungarian'),(1417,'hu','cs','Maďarština'),(1418,'hu','sk','Maďarčina'),(1419,'hu','cy','Hungarian'),(1420,'hu','da','Hungarian'),(1421,'hu','el','Ουγγρικα'),(1422,'hu','eo','Hungarian'),(1423,'hu','et','Hungarian'),(1424,'hu','eu','Hungarian'),(1425,'hu','fa','Hungarian'),(1426,'hu','fi','unkari'),(1427,'hu','ga','Hungarian'),(1428,'hu','he','הונגרית'),(1429,'hu','hi','Hungarian'),(1430,'hu','hr','Mađarski'),(1431,'hu','hu','Magyar'),(1432,'hu','hy','Hungarian'),(1433,'hu','id','Hungarian'),(1434,'hu','is','Hungarian'),(1435,'hu','it','Ungherese'),(1436,'hu','ja','ハンガリー語'),(1437,'hu','ko','헝가리어'),(1438,'hu','ku','Hungarian'),(1439,'hu','lv','Hungarian'),(1440,'hu','lt','Hungarian'),(1441,'hu','mk','Hungarian'),(1442,'hu','mt','Hungarian'),(1443,'hu','mn','Hungarian'),(1444,'hu','ne','Hungarian'),(1445,'hu','nl','Hongaars'),(1446,'hu','no','Ungarsk'),(1447,'hu','pa','Hungarian'),(1448,'hu','pl','węgierski'),(1449,'hu','pt-pt','Húngaro'),(1450,'hu','pt-br','Húngaro'),(1451,'hu','qu','Hungarian'),(1452,'hu','ro','Ungară'),(1453,'hu','ru','Венгерский'),(1454,'hu','sl','Madžarski'),(1455,'hu','so','Hungarian'),(1456,'hu','sq','Hungarian'),(1457,'hu','sr','мађарски'),(1458,'hu','sv','Ungerska'),(1459,'hu','ta','Hungarian'),(1460,'hu','th','ฮังการี'),(1461,'hu','tr','Macarca'),(1462,'hu','uk','Hungarian'),(1463,'hu','ur','Hungarian'),(1464,'hu','uz','Hungarian'),(1465,'hu','vi','Hungarian'),(1466,'hu','yi','Hungarian'),(1467,'hu','zh-hans','匈牙利语'),(1468,'hu','zu','Hungarian'),(1469,'hu','zh-hant','匈牙利語'),(1470,'hu','ms','Hungarian'),(1471,'hu','gl','Hungarian'),(1472,'hu','bn','Hungarian'),(1473,'hy','en','Armenian'),(1474,'hy','es','Armenio'),(1475,'hy','de','Armenisch'),(1476,'hy','fr','Arménien'),(1477,'hy','ar','الأرمينية'),(1478,'hy','bs','Armenian'),(1479,'hy','bg','Арменски'),(1480,'hy','ca','Armenian'),(1481,'hy','cs','Arménský'),(1482,'hy','sk','Arménčina'),(1483,'hy','cy','Armenian'),(1484,'hy','da','Armenian'),(1485,'hy','el','Αρμενικα'),(1486,'hy','eo','Armenian'),(1487,'hy','et','Armenian'),(1488,'hy','eu','Armenian'),(1489,'hy','fa','Armenian'),(1490,'hy','fi','armenia'),(1491,'hy','ga','Armenian'),(1492,'hy','he','ארמנית'),(1493,'hy','hi','Armenian'),(1494,'hy','hr','Armenac'),(1495,'hy','hu','örmény'),(1496,'hy','hy','Հայերեն'),(1497,'hy','id','Armenian'),(1498,'hy','is','Armenian'),(1499,'hy','it','Armeno'),(1500,'hy','ja','アルメニア語'),(1501,'hy','ko','아르메니아어'),(1502,'hy','ku','Armenian'),(1503,'hy','lv','Armenian'),(1504,'hy','lt','Armenian'),(1505,'hy','mk','Armenian'),(1506,'hy','mt','Armenian'),(1507,'hy','mn','Armenian'),(1508,'hy','ne','Armenian'),(1509,'hy','nl','Armeens'),(1510,'hy','no','Armensk'),(1511,'hy','pa','Armenian'),(1512,'hy','pl','ormiański'),(1513,'hy','pt-pt','Arménio'),(1514,'hy','pt-br','Arménio'),(1515,'hy','qu','Armenian'),(1516,'hy','ro','Armeană'),(1517,'hy','ru','Армянский'),(1518,'hy','sl','Armenski'),(1519,'hy','so','Armenian'),(1520,'hy','sq','Armenian'),(1521,'hy','sr','јерменски'),(1522,'hy','sv','Armeniska'),(1523,'hy','ta','Armenian'),(1524,'hy','th','อาร์เมเนีย'),(1525,'hy','tr','Ermenice'),(1526,'hy','uk','Armenian'),(1527,'hy','ur','Armenian'),(1528,'hy','uz','Armenian'),(1529,'hy','vi','Armenian'),(1530,'hy','yi','Armenian'),(1531,'hy','zh-hans','亚美尼亚语'),(1532,'hy','zu','Armenian'),(1533,'hy','zh-hant','亞美尼亞語'),(1534,'hy','ms','Armenian'),(1535,'hy','gl','Armenian'),(1536,'hy','bn','Armenian'),(1537,'id','en','Indonesian'),(1538,'id','es','Indonesio'),(1539,'id','de','Indonesisch'),(1540,'id','fr','Indonésien'),(1541,'id','ar','الأندونيسية'),(1542,'id','bs','Indonesian'),(1543,'id','bg','Индонезийски'),(1544,'id','ca','Indonesian'),(1545,'id','cs','Indonéský'),(1546,'id','sk','Indonézčina'),(1547,'id','cy','Indonesian'),(1548,'id','da','Indonesian'),(1549,'id','el','Ινδονησιακα'),(1550,'id','eo','Indonesian'),(1551,'id','et','Indonesian'),(1552,'id','eu','Indonesian'),(1553,'id','fa','Indonesian'),(1554,'id','fi','indonesia'),(1555,'id','ga','Indonesian'),(1556,'id','he','אינדונזית'),(1557,'id','hi','Indonesian'),(1558,'id','hr','Indonezijski'),(1559,'id','hu','indonéz'),(1560,'id','hy','Indonesian'),(1561,'id','id','Indonesia'),(1562,'id','is','Indonesian'),(1563,'id','it','Indonesiano'),(1564,'id','ja','インドネシア語'),(1565,'id','ko','인도네시아어'),(1566,'id','ku','Indonesian'),(1567,'id','lv','Indonesian'),(1568,'id','lt','Indonesian'),(1569,'id','mk','Indonesian'),(1570,'id','mt','Indonesian'),(1571,'id','mn','Indonesian'),(1572,'id','ne','Indonesian'),(1573,'id','nl','Indonesisch'),(1574,'id','no','Indonesian'),(1575,'id','pa','Indonesian'),(1576,'id','pl','indonezyjski'),(1577,'id','pt-pt','Indonésio'),(1578,'id','pt-br','Indonésio'),(1579,'id','qu','Indonesian'),(1580,'id','ro','Indoneziană'),(1581,'id','ru','Индонезийский'),(1582,'id','sl','Indonezijski'),(1583,'id','so','Indonesian'),(1584,'id','sq','Indonesian'),(1585,'id','sr','индонезијски'),(1586,'id','sv','Indonesiska'),(1587,'id','ta','Indonesian'),(1588,'id','th','อินโดนีเซีย'),(1589,'id','tr','Endonezya dili'),(1590,'id','uk','Indonesian'),(1591,'id','ur','Indonesian'),(1592,'id','uz','Indonesian'),(1593,'id','vi','Indonesian'),(1594,'id','yi','Indonesian'),(1595,'id','zh-hans','印度尼西亚语'),(1596,'id','zu','Indonesian'),(1597,'id','zh-hant','印尼語'),(1598,'id','ms','Indonesian'),(1599,'id','gl','Indonesian'),(1600,'id','bn','Indonesian'),(1601,'is','en','Icelandic'),(1602,'is','es','Islandés'),(1603,'is','de','Isländisch'),(1604,'is','fr','Islandais'),(1605,'is','ar','الأيسلاندية'),(1606,'is','bs','Icelandic'),(1607,'is','bg','Исландски'),(1608,'is','ca','Icelandic'),(1609,'is','cs','Islandský'),(1610,'is','sk','Islančina'),(1611,'is','cy','Icelandic'),(1612,'is','da','Icelandic'),(1613,'is','el','Ισλανδικα'),(1614,'is','eo','Icelandic'),(1615,'is','et','Icelandic'),(1616,'is','eu','Icelandic'),(1617,'is','fa','Icelandic'),(1618,'is','fi','islanti'),(1619,'is','ga','Icelandic'),(1620,'is','he','איסלנדית'),(1621,'is','hi','Icelandic'),(1622,'is','hr','Islandski'),(1623,'is','hu','izlandi'),(1624,'is','hy','Icelandic'),(1625,'is','id','Icelandic'),(1626,'is','is','Íslenska'),(1627,'is','it','Islandese'),(1628,'is','ja','アイスランド語'),(1629,'is','ko','아이슬랜드어'),(1630,'is','ku','Icelandic'),(1631,'is','lv','Icelandic'),(1632,'is','lt','Icelandic'),(1633,'is','mk','Icelandic'),(1634,'is','mt','Icelandic'),(1635,'is','mn','Icelandic'),(1636,'is','ne','Icelandic'),(1637,'is','nl','Ijslands'),(1638,'is','no','Islandsk'),(1639,'is','pa','Icelandic'),(1640,'is','pl','islandzki'),(1641,'is','pt-pt','Islandês'),(1642,'is','pt-br','Islandês'),(1643,'is','qu','Icelandic'),(1644,'is','ro','Islandeză'),(1645,'is','ru','Исландский'),(1646,'is','sl','Islandski'),(1647,'is','so','Icelandic'),(1648,'is','sq','Icelandic'),(1649,'is','sr','исландски'),(1650,'is','sv','Isländska'),(1651,'is','ta','Icelandic'),(1652,'is','th','ไอซ์แลนด์'),(1653,'is','tr','İzlandaca'),(1654,'is','uk','Icelandic'),(1655,'is','ur','Icelandic'),(1656,'is','uz','Icelandic'),(1657,'is','vi','Icelandic'),(1658,'is','yi','Icelandic'),(1659,'is','zh-hans','冰岛语'),(1660,'is','zu','Icelandic'),(1661,'is','zh-hant','冰島語'),(1662,'is','ms','Icelandic'),(1663,'is','gl','Icelandic'),(1664,'is','bn','Icelandic'),(1665,'it','en','Italian'),(1666,'it','es','Italiano'),(1667,'it','de','Italienisch'),(1668,'it','fr','Italien'),(1669,'it','ar','الإيطالية'),(1670,'it','bs','Italian'),(1671,'it','bg','Италиански'),(1672,'it','ca','Italian'),(1673,'it','cs','Ital'),(1674,'it','sk','Taliančina'),(1675,'it','cy','Italian'),(1676,'it','da','Italian'),(1677,'it','el','Ιταλικα'),(1678,'it','eo','Italian'),(1679,'it','et','Italian'),(1680,'it','eu','Italian'),(1681,'it','fa','Italian'),(1682,'it','fi','italia'),(1683,'it','ga','Italian'),(1684,'it','he','איטלקית'),(1685,'it','hi','Italian'),(1686,'it','hr','Talijanski'),(1687,'it','hu','olasz'),(1688,'it','hy','Italian'),(1689,'it','id','Italian'),(1690,'it','is','Italian'),(1691,'it','it','Italiano'),(1692,'it','ja','イタリア語'),(1693,'it','ko','이태리어'),(1694,'it','ku','Italian'),(1695,'it','lv','Italian'),(1696,'it','lt','Italian'),(1697,'it','mk','Italian'),(1698,'it','mt','Italian'),(1699,'it','mn','Italian'),(1700,'it','ne','Italian'),(1701,'it','nl','Italiaans'),(1702,'it','no','Italiensk'),(1703,'it','pa','Italian'),(1704,'it','pl','włoski'),(1705,'it','pt-pt','Italiano'),(1706,'it','pt-br','Italiano'),(1707,'it','qu','Italian'),(1708,'it','ro','Italiană'),(1709,'it','ru','Итальянский'),(1710,'it','sl','Italijanski'),(1711,'it','so','Italian'),(1712,'it','sq','Italian'),(1713,'it','sr','италијански'),(1714,'it','sv','Italienska'),(1715,'it','ta','Italian'),(1716,'it','th','อิตาลี'),(1717,'it','tr','İtalyanca'),(1718,'it','uk','Italian'),(1719,'it','ur','Italian'),(1720,'it','uz','Italian'),(1721,'it','vi','Italian'),(1722,'it','yi','Italian'),(1723,'it','zh-hans','意大利语'),(1724,'it','zu','Italian'),(1725,'it','zh-hant','義大利語'),(1726,'it','ms','Italian'),(1727,'it','gl','Italian'),(1728,'it','bn','Italian'),(1729,'ja','en','Japanese'),(1730,'ja','es','Japonés'),(1731,'ja','de','Japanisch'),(1732,'ja','fr','Japonais'),(1733,'ja','ar','اليابانية'),(1734,'ja','bs','Japanese'),(1735,'ja','bg','Японски'),(1736,'ja','ca','Japanese'),(1737,'ja','cs','Japonský'),(1738,'ja','sk','Japonština'),(1739,'ja','cy','Japanese'),(1740,'ja','da','Japanese'),(1741,'ja','el','Ιαπωνικα'),(1742,'ja','eo','Japanese'),(1743,'ja','et','Japanese'),(1744,'ja','eu','Japanese'),(1745,'ja','fa','Japanese'),(1746,'ja','fi','japani'),(1747,'ja','ga','Japanese'),(1748,'ja','he','יפנית'),(1749,'ja','hi','Japanese'),(1750,'ja','hr','Japanski'),(1751,'ja','hu','japán'),(1752,'ja','hy','Japanese'),(1753,'ja','id','Japanese'),(1754,'ja','is','Japanese'),(1755,'ja','it','Giapponese'),(1756,'ja','ja','日本語'),(1757,'ja','ko','일어'),(1758,'ja','ku','Japanese'),(1759,'ja','lv','Japanese'),(1760,'ja','lt','Japanese'),(1761,'ja','mk','Japanese'),(1762,'ja','mt','Japanese'),(1763,'ja','mn','Japanese'),(1764,'ja','ne','Japanese'),(1765,'ja','nl','Japans'),(1766,'ja','no','Japansk'),(1767,'ja','pa','Japanese'),(1768,'ja','pl','japoński'),(1769,'ja','pt-pt','Japonês'),(1770,'ja','pt-br','Japonês'),(1771,'ja','qu','Japanese'),(1772,'ja','ro','Japoneză'),(1773,'ja','ru','Японский'),(1774,'ja','sl','Japonski'),(1775,'ja','so','Japanese'),(1776,'ja','sq','Japanese'),(1777,'ja','sr','јапански'),(1778,'ja','sv','Japanska'),(1779,'ja','ta','Japanese'),(1780,'ja','th','ญี่ปุ่น'),(1781,'ja','tr','Japonca'),(1782,'ja','uk','Japanese'),(1783,'ja','ur','Japanese'),(1784,'ja','uz','Japanese'),(1785,'ja','vi','Japanese'),(1786,'ja','yi','Japanese'),(1787,'ja','zh-hans','日语'),(1788,'ja','zu','Japanese'),(1789,'ja','zh-hant','日語'),(1790,'ja','ms','Japanese'),(1791,'ja','gl','Japanese'),(1792,'ja','bn','Japanese'),(1793,'ko','en','Korean'),(1794,'ko','es','Coreano'),(1795,'ko','de','Koreanisch'),(1796,'ko','fr','Coréen'),(1797,'ko','ar','الكورية'),(1798,'ko','bs','Korean'),(1799,'ko','bg','Корейски'),(1800,'ko','ca','Korean'),(1801,'ko','cs','Korejský'),(1802,'ko','sk','Kórejčina'),(1803,'ko','cy','Korean'),(1804,'ko','da','Korean'),(1805,'ko','el','Κορεατικα'),(1806,'ko','eo','Korean'),(1807,'ko','et','Korean'),(1808,'ko','eu','Korean'),(1809,'ko','fa','Korean'),(1810,'ko','fi','korea'),(1811,'ko','ga','Korean'),(1812,'ko','he','קוראנית'),(1813,'ko','hi','Korean'),(1814,'ko','hr','Korejski'),(1815,'ko','hu','koreai'),(1816,'ko','hy','Korean'),(1817,'ko','id','Korean'),(1818,'ko','is','Korean'),(1819,'ko','it','Coreano'),(1820,'ko','ja','韓国語'),(1821,'ko','ko','한국어'),(1822,'ko','ku','Korean'),(1823,'ko','lv','Korean'),(1824,'ko','lt','Korean'),(1825,'ko','mk','Korean'),(1826,'ko','mt','Korean'),(1827,'ko','mn','Korean'),(1828,'ko','ne','Korean'),(1829,'ko','nl','Koreaans'),(1830,'ko','no','Koreanske'),(1831,'ko','pa','Korean'),(1832,'ko','pl','koreański'),(1833,'ko','pt-pt','Coreano'),(1834,'ko','pt-br','Coreano'),(1835,'ko','qu','Korean'),(1836,'ko','ro','Coreană'),(1837,'ko','ru','Корейский'),(1838,'ko','sl','Korejski'),(1839,'ko','so','Korean'),(1840,'ko','sq','Korean'),(1841,'ko','sr','корејски'),(1842,'ko','sv','Koreanska'),(1843,'ko','ta','Korean'),(1844,'ko','th','เกาหลี'),(1845,'ko','tr','Kore dili'),(1846,'ko','uk','Korean'),(1847,'ko','ur','Korean'),(1848,'ko','uz','Korean'),(1849,'ko','vi','Korean'),(1850,'ko','yi','Korean'),(1851,'ko','zh-hans','韩语'),(1852,'ko','zu','Korean'),(1853,'ko','zh-hant','韓語'),(1854,'ko','ms','Korean'),(1855,'ko','gl','Korean'),(1856,'ko','bn','Korean'),(1857,'ku','en','Kurdish'),(1858,'ku','es','Kurdo'),(1859,'ku','de','Kurdisch'),(1860,'ku','fr','Kurde'),(1861,'ku','ar','الكردية'),(1862,'ku','bs','Kurdish'),(1863,'ku','bg','Кюрдски'),(1864,'ku','ca','Kurdish'),(1865,'ku','cs','Kurdský'),(1866,'ku','sk','Kurdština'),(1867,'ku','cy','Kurdish'),(1868,'ku','da','Kurdish'),(1869,'ku','el','Κουρδικα'),(1870,'ku','eo','Kurdish'),(1871,'ku','et','Kurdish'),(1872,'ku','eu','Kurdish'),(1873,'ku','fa','Kurdish'),(1874,'ku','fi','kurdi'),(1875,'ku','ga','Kurdish'),(1876,'ku','he','כורדית'),(1877,'ku','hi','Kurdish'),(1878,'ku','hr','Kurdski'),(1879,'ku','hu','kurd'),(1880,'ku','hy','Kurdish'),(1881,'ku','id','Kurdish'),(1882,'ku','is','Kurdish'),(1883,'ku','it','Curdo'),(1884,'ku','ja','クルド語'),(1885,'ku','ko','쿠르드어'),(1886,'ku','ku','Kurdish'),(1887,'ku','lv','Kurdish'),(1888,'ku','lt','Kurdish'),(1889,'ku','mk','Kurdish'),(1890,'ku','mt','Kurdish'),(1891,'ku','mn','Kurdish'),(1892,'ku','ne','Kurdish'),(1893,'ku','nl','Koerdish'),(1894,'ku','no','Kurdisk'),(1895,'ku','pa','Kurdish'),(1896,'ku','pl','kurdyjski'),(1897,'ku','pt-pt','Curdo'),(1898,'ku','pt-br','Curdo'),(1899,'ku','qu','Kurdish'),(1900,'ku','ro','Kurdă'),(1901,'ku','ru','Курдский'),(1902,'ku','sl','Kurdščina'),(1903,'ku','so','Kurdish'),(1904,'ku','sq','Kurdish'),(1905,'ku','sr','курдски'),(1906,'ku','sv','Kurdiska'),(1907,'ku','ta','Kurdish'),(1908,'ku','th','เคอร์ดิช'),(1909,'ku','tr','Kürtçe'),(1910,'ku','uk','Kurdish'),(1911,'ku','ur','Kurdish'),(1912,'ku','uz','Kurdish'),(1913,'ku','vi','Kurdish'),(1914,'ku','yi','Kurdish'),(1915,'ku','zh-hans','库尔德语'),(1916,'ku','zu','Kurdish'),(1917,'ku','zh-hant','庫爾德語'),(1918,'ku','ms','Kurdish'),(1919,'ku','gl','Kurdish'),(1920,'ku','bn','Kurdish'),(1921,'lv','en','Latvian'),(1922,'lv','es','Letón'),(1923,'lv','de','Lettisch'),(1924,'lv','fr','Letton'),(1925,'lv','ar','اللاتفية'),(1926,'lv','bs','Latvian'),(1927,'lv','bg','Латвийски'),(1928,'lv','ca','Latvian'),(1929,'lv','cs','Lotyština'),(1930,'lv','sk','Lotyština'),(1931,'lv','cy','Latvian'),(1932,'lv','da','Latvian'),(1933,'lv','el','Λετονικα'),(1934,'lv','eo','Latvian'),(1935,'lv','et','Latvian'),(1936,'lv','eu','Latvian'),(1937,'lv','fa','Latvian'),(1938,'lv','fi','latvia'),(1939,'lv','ga','Latvian'),(1940,'lv','he','לטבית'),(1941,'lv','hi','Latvian'),(1942,'lv','hr','Letonski'),(1943,'lv','hu','lett'),(1944,'lv','hy','Latvian'),(1945,'lv','id','Latvian'),(1946,'lv','is','Latvian'),(1947,'lv','it','Lettone'),(1948,'lv','ja','ラトビア語'),(1949,'lv','ko','라트비아어'),(1950,'lv','ku','Latvian'),(1951,'lv','lv','Latviešu'),(1952,'lv','lt','Latvian'),(1953,'lv','mk','Latvian'),(1954,'lv','mt','Latvian'),(1955,'lv','mn','Latvian'),(1956,'lv','ne','Latvian'),(1957,'lv','nl','Lets'),(1958,'lv','no','Latvisk'),(1959,'lv','pa','Latvian'),(1960,'lv','pl','łotewski'),(1961,'lv','pt-pt','Letão'),(1962,'lv','pt-br','Letão'),(1963,'lv','qu','Latvian'),(1964,'lv','ro','Letoniană'),(1965,'lv','ru','латышский'),(1966,'lv','sl','Latvijščina'),(1967,'lv','so','Latvian'),(1968,'lv','sq','Latvian'),(1969,'lv','sr','летонски'),(1970,'lv','sv','Lettiska'),(1971,'lv','ta','Latvian'),(1972,'lv','th','ลัตเวีย'),(1973,'lv','tr','Letonca'),(1974,'lv','uk','Latvian'),(1975,'lv','ur','Latvian'),(1976,'lv','uz','Latvian'),(1977,'lv','vi','Latvian'),(1978,'lv','yi','Latvian'),(1979,'lv','zh-hans','拉脱维亚语'),(1980,'lv','zu','Latvian'),(1981,'lv','zh-hant','拉脫維亞語'),(1982,'lv','ms','Latvian'),(1983,'lv','gl','Latvian'),(1984,'lv','bn','Latvian'),(1985,'lt','en','Lithuanian'),(1986,'lt','es','Lituano'),(1987,'lt','de','Litauisch'),(1988,'lt','fr','Lituanien'),(1989,'lt','ar','اللتوانية'),(1990,'lt','bs','Lithuanian'),(1991,'lt','bg','Литовски'),(1992,'lt','ca','Lithuanian'),(1993,'lt','cs','litevský'),(1994,'lt','sk','Litovčina'),(1995,'lt','cy','Lithuanian'),(1996,'lt','da','Lithuanian'),(1997,'lt','el','Λιθουανικα'),(1998,'lt','eo','Lithuanian'),(1999,'lt','et','Lithuanian'),(2000,'lt','eu','Lithuanian'),(2001,'lt','fa','Lithuanian'),(2002,'lt','fi','liettua'),(2003,'lt','ga','Lithuanian'),(2004,'lt','he','ליטאית'),(2005,'lt','hi','Lithuanian'),(2006,'lt','hr','Litvanski'),(2007,'lt','hu','litván'),(2008,'lt','hy','Lithuanian'),(2009,'lt','id','Lithuanian'),(2010,'lt','is','Lithuanian'),(2011,'lt','it','Lituano'),(2012,'lt','ja','リトアニア語'),(2013,'lt','ko','리투아니아어'),(2014,'lt','ku','Lithuanian'),(2015,'lt','lv','Lithuanian'),(2016,'lt','lt','Lietuvos'),(2017,'lt','mk','Lithuanian'),(2018,'lt','mt','Lithuanian'),(2019,'lt','mn','Lithuanian'),(2020,'lt','ne','Lithuanian'),(2021,'lt','nl','Litouws'),(2022,'lt','no','Litauisk'),(2023,'lt','pa','Lithuanian'),(2024,'lt','pl','litewski'),(2025,'lt','pt-pt','Lituano'),(2026,'lt','pt-br','Lituano'),(2027,'lt','qu','Lithuanian'),(2028,'lt','ro','Lituaniană'),(2029,'lt','ru','Литовский'),(2030,'lt','sl','Litovščina'),(2031,'lt','so','Lithuanian'),(2032,'lt','sq','Lithuanian'),(2033,'lt','sr','литвански'),(2034,'lt','sv','Litauiska'),(2035,'lt','ta','Lithuanian'),(2036,'lt','th','ลิธัวเนีย'),(2037,'lt','tr','Litvanyaca'),(2038,'lt','uk','Lithuanian'),(2039,'lt','ur','Lithuanian'),(2040,'lt','uz','Lithuanian'),(2041,'lt','vi','Lithuanian'),(2042,'lt','yi','Lithuanian'),(2043,'lt','zh-hans','立陶宛语'),(2044,'lt','zu','Lithuanian'),(2045,'lt','zh-hant','立陶宛語'),(2046,'lt','ms','Lithuanian'),(2047,'lt','gl','Lithuanian'),(2048,'lt','bn','Lithuanian'),(2049,'mk','en','Macedonian'),(2050,'mk','es','Macedonio'),(2051,'mk','de','Mazedonisch'),(2052,'mk','fr','Macédonien'),(2053,'mk','ar','المقدونية'),(2054,'mk','bs','Macedonian'),(2055,'mk','bg','Македонски'),(2056,'mk','ca','Macedonian'),(2057,'mk','cs','Makedonský'),(2058,'mk','sk','Macedónština'),(2059,'mk','cy','Macedonian'),(2060,'mk','da','Macedonian'),(2061,'mk','el','Μακεδονικο'),(2062,'mk','eo','Macedonian'),(2063,'mk','et','Macedonian'),(2064,'mk','eu','Macedonian'),(2065,'mk','fa','Macedonian'),(2066,'mk','fi','makedonia'),(2067,'mk','ga','Macedonian'),(2068,'mk','he','מקדונית'),(2069,'mk','hi','Macedonian'),(2070,'mk','hr','Makedonski'),(2071,'mk','hu','macedón'),(2072,'mk','hy','Macedonian'),(2073,'mk','id','Macedonian'),(2074,'mk','is','Macedonian'),(2075,'mk','it','Macedone'),(2076,'mk','ja','マケドニア語'),(2077,'mk','ko','마케도니아어'),(2078,'mk','ku','Macedonian'),(2079,'mk','lv','Macedonian'),(2080,'mk','lt','Macedonian'),(2081,'mk','mk','македонски'),(2082,'mk','mt','Macedonian'),(2083,'mk','mn','Macedonian'),(2084,'mk','ne','Macedonian'),(2085,'mk','nl','Macedonisch'),(2086,'mk','no','Makedonsk'),(2087,'mk','pa','Macedonian'),(2088,'mk','pl','macedoński'),(2089,'mk','pt-pt','Macedônio'),(2090,'mk','pt-br','Macedônio'),(2091,'mk','qu','Macedonian'),(2092,'mk','ro','Macedoniană'),(2093,'mk','ru','Македонский'),(2094,'mk','sl','Makedonski'),(2095,'mk','so','Macedonian'),(2096,'mk','sq','Macedonian'),(2097,'mk','sr','македонски'),(2098,'mk','sv','Makedonska'),(2099,'mk','ta','Macedonian'),(2100,'mk','th','มาซิโดเนีย'),(2101,'mk','tr','Makedonyaca'),(2102,'mk','uk','Macedonian'),(2103,'mk','ur','Macedonian'),(2104,'mk','uz','Macedonian'),(2105,'mk','vi','Macedonian'),(2106,'mk','yi','Macedonian'),(2107,'mk','zh-hans','马其顿语'),(2108,'mk','zu','Macedonian'),(2109,'mk','zh-hant','馬其頓語'),(2110,'mk','ms','Macedonian'),(2111,'mk','gl','Macedonian'),(2112,'mk','bn','Macedonian'),(2113,'mt','en','Maltese'),(2114,'mt','es','Maltés'),(2115,'mt','de','Maltesisch'),(2116,'mt','fr','Maltais'),(2117,'mt','ar','المالطية'),(2118,'mt','bs','Maltese'),(2119,'mt','bg','Малтийски'),(2120,'mt','ca','Maltese'),(2121,'mt','cs','Maltština'),(2122,'mt','sk','Maltézština'),(2123,'mt','cy','Maltese'),(2124,'mt','da','Maltese'),(2125,'mt','el','Μαλτεζικα'),(2126,'mt','eo','Maltese'),(2127,'mt','et','Maltese'),(2128,'mt','eu','Maltese'),(2129,'mt','fa','Maltese'),(2130,'mt','fi','malta'),(2131,'mt','ga','Maltese'),(2132,'mt','he','מלטזית'),(2133,'mt','hi','Maltese'),(2134,'mt','hr','Malteški'),(2135,'mt','hu','máltai'),(2136,'mt','hy','Maltese'),(2137,'mt','id','Maltese'),(2138,'mt','is','Maltese'),(2139,'mt','it','Maltese'),(2140,'mt','ja','マルタ語'),(2141,'mt','ko','몰타어'),(2142,'mt','ku','Maltese'),(2143,'mt','lv','Maltese'),(2144,'mt','lt','Maltese'),(2145,'mt','mk','Maltese'),(2146,'mt','mt','Malti'),(2147,'mt','mn','Maltese'),(2148,'mt','ne','Maltese'),(2149,'mt','nl','Maltees'),(2150,'mt','no','Maltese'),(2151,'mt','pa','Maltese'),(2152,'mt','pl','maltański'),(2153,'mt','pt-pt','Maltês'),(2154,'mt','pt-br','Maltês'),(2155,'mt','qu','Maltese'),(2156,'mt','ro','Malteză'),(2157,'mt','ru','Мальтийский'),(2158,'mt','sl','Malteški'),(2159,'mt','so','Maltese'),(2160,'mt','sq','Maltese'),(2161,'mt','sr','малтешки'),(2162,'mt','sv','Maltesiska'),(2163,'mt','ta','Maltese'),(2164,'mt','th','มอลทีส'),(2165,'mt','tr','Malta dili'),(2166,'mt','uk','Maltese'),(2167,'mt','ur','Maltese'),(2168,'mt','uz','Maltese'),(2169,'mt','vi','Maltese'),(2170,'mt','yi','Maltese'),(2171,'mt','zh-hans','马耳他语'),(2172,'mt','zu','Maltese'),(2173,'mt','zh-hant','馬爾他語'),(2174,'mt','ms','Maltese'),(2175,'mt','gl','Maltese'),(2176,'mt','bn','Maltese'),(2177,'mn','en','Mongolian'),(2178,'mn','es','Mongol'),(2179,'mn','de','Mongolisch'),(2180,'mn','fr','Mongol'),(2181,'mn','ar','المنغولية'),(2182,'mn','bs','Mongolian'),(2183,'mn','bg','Монголски'),(2184,'mn','ca','Mongolian'),(2185,'mn','cs','Mongolský'),(2186,'mn','sk','Mongolština'),(2187,'mn','cy','Mongolian'),(2188,'mn','da','Mongolian'),(2189,'mn','el','Μογγολικα'),(2190,'mn','eo','Mongolian'),(2191,'mn','et','Mongolian'),(2192,'mn','eu','Mongolian'),(2193,'mn','fa','Mongolian'),(2194,'mn','fi','mongoli'),(2195,'mn','ga','Mongolian'),(2196,'mn','he','מונגולית'),(2197,'mn','hi','Mongolian'),(2198,'mn','hr','Mongolski'),(2199,'mn','hu','mongol'),(2200,'mn','hy','Mongolian'),(2201,'mn','id','Mongolian'),(2202,'mn','is','Mongolian'),(2203,'mn','it','Mongolo'),(2204,'mn','ja','モンゴル語'),(2205,'mn','ko','몽골어'),(2206,'mn','ku','Mongolian'),(2207,'mn','lv','Mongolian'),(2208,'mn','lt','Mongolian'),(2209,'mn','mk','Mongolian'),(2210,'mn','mt','Mongolian'),(2211,'mn','mn','Mongolian'),(2212,'mn','ne','Mongolian'),(2213,'mn','nl','Mongools'),(2214,'mn','no','Mongolsk'),(2215,'mn','pa','Mongolian'),(2216,'mn','pl','mongolski'),(2217,'mn','pt-pt','Mongolian'),(2218,'mn','pt-br','Mongolian'),(2219,'mn','qu','Mongolian'),(2220,'mn','ro','Mongoleză'),(2221,'mn','ru','Монгольский'),(2222,'mn','sl','Mongolski'),(2223,'mn','so','Mongolian'),(2224,'mn','sq','Mongolian'),(2225,'mn','sr','монголски'),(2226,'mn','sv','Mongoliska'),(2227,'mn','ta','Mongolian'),(2228,'mn','th','มองโกเลีย'),(2229,'mn','tr','Mongolca'),(2230,'mn','uk','Mongolian'),(2231,'mn','ur','Mongolian'),(2232,'mn','uz','Mongolian'),(2233,'mn','vi','Mongolian'),(2234,'mn','yi','Mongolian'),(2235,'mn','zh-hans','蒙古语'),(2236,'mn','zu','Mongolian'),(2237,'mn','zh-hant','蒙古語'),(2238,'mn','ms','Mongolian'),(2239,'mn','gl','Mongolian'),(2240,'mn','bn','Mongolian'),(2241,'ne','en','Nepali'),(2242,'ne','es','Nepalí'),(2243,'ne','de','Nepali'),(2244,'ne','fr','Népalais'),(2245,'ne','ar','النيبالية'),(2246,'ne','bs','Nepali'),(2247,'ne','bg','Непалски'),(2248,'ne','ca','Nepali'),(2249,'ne','cs','Nepálský'),(2250,'ne','sk','Nepálčina'),(2251,'ne','cy','Nepali'),(2252,'ne','da','Nepali'),(2253,'ne','el','Νεπαλι'),(2254,'ne','eo','Nepali'),(2255,'ne','et','Nepali'),(2256,'ne','eu','Nepali'),(2257,'ne','fa','Nepali'),(2258,'ne','fi','nepali'),(2259,'ne','ga','Nepali'),(2260,'ne','he','נפאלית'),(2261,'ne','hi','Nepali'),(2262,'ne','hr','Nepalski'),(2263,'ne','hu','nepáli'),(2264,'ne','hy','Nepali'),(2265,'ne','id','Nepali'),(2266,'ne','is','Nepali'),(2267,'ne','it','Nepalese'),(2268,'ne','ja','ネパール語'),(2269,'ne','ko','네팔어'),(2270,'ne','ku','Nepali'),(2271,'ne','lv','Nepali'),(2272,'ne','lt','Nepali'),(2273,'ne','mk','Nepali'),(2274,'ne','mt','Nepali'),(2275,'ne','mn','Nepali'),(2276,'ne','ne','Nepali'),(2277,'ne','nl','Nepalees'),(2278,'ne','no','Nepali'),(2279,'ne','pa','Nepali'),(2280,'ne','pl','nepalski'),(2281,'ne','pt-pt','Nepali'),(2282,'ne','pt-br','Nepali'),(2283,'ne','qu','Nepali'),(2284,'ne','ro','Nepaleză'),(2285,'ne','ru','Непальский'),(2286,'ne','sl','Nepalščina'),(2287,'ne','so','Nepali'),(2288,'ne','sq','Nepali'),(2289,'ne','sr','непалски'),(2290,'ne','sv','Nepalesiska'),(2291,'ne','ta','Nepali'),(2292,'ne','th','เนปาล'),(2293,'ne','tr','Nepal dili'),(2294,'ne','uk','Nepali'),(2295,'ne','ur','Nepali'),(2296,'ne','uz','Nepali'),(2297,'ne','vi','Nepali'),(2298,'ne','yi','Nepali'),(2299,'ne','zh-hans','尼泊尔语'),(2300,'ne','zu','Nepali'),(2301,'ne','zh-hant','尼泊爾語'),(2302,'ne','ms','Nepali'),(2303,'ne','gl','Nepali'),(2304,'ne','bn','Nepali'),(2305,'nl','en','Dutch'),(2306,'nl','es','Holandés'),(2307,'nl','de','Niederländisch'),(2308,'nl','fr','Néerlandais'),(2309,'nl','ar','الهولندية'),(2310,'nl','bs','Dutch'),(2311,'nl','bg','Холандски'),(2312,'nl','ca','Dutch'),(2313,'nl','cs','Holandský'),(2314,'nl','sk','Holandčina'),(2315,'nl','cy','Dutch'),(2316,'nl','da','Dutch'),(2317,'nl','el','Ολλανδικα'),(2318,'nl','eo','Dutch'),(2319,'nl','et','Dutch'),(2320,'nl','eu','Dutch'),(2321,'nl','fa','Dutch'),(2322,'nl','fi','hollanti'),(2323,'nl','ga','Dutch'),(2324,'nl','he','הולנדית'),(2325,'nl','hi','Dutch'),(2326,'nl','hr','Holandski'),(2327,'nl','hu','holland'),(2328,'nl','hy','Dutch'),(2329,'nl','id','Dutch'),(2330,'nl','is','Dutch'),(2331,'nl','it','Olandese'),(2332,'nl','ja','オランダ語'),(2333,'nl','ko','화란어'),(2334,'nl','ku','Dutch'),(2335,'nl','lv','Dutch'),(2336,'nl','lt','Dutch'),(2337,'nl','mk','Dutch'),(2338,'nl','mt','Dutch'),(2339,'nl','mn','Dutch'),(2340,'nl','ne','Dutch'),(2341,'nl','nl','Nederlands'),(2342,'nl','no','Nederlandsk'),(2343,'nl','pa','Dutch'),(2344,'nl','pl','holenderski'),(2345,'nl','pt-pt','Holandês'),(2346,'nl','pt-br','Holandês'),(2347,'nl','qu','Dutch'),(2348,'nl','ro','Olaneză'),(2349,'nl','ru','Голландский'),(2350,'nl','sl','Nizozemščina'),(2351,'nl','so','Dutch'),(2352,'nl','sq','Dutch'),(2353,'nl','sr','холандски'),(2354,'nl','sv','Nederländska'),(2355,'nl','ta','Dutch'),(2356,'nl','th','ดัตช์'),(2357,'nl','tr','Hollandaca'),(2358,'nl','uk','Dutch'),(2359,'nl','ur','Dutch'),(2360,'nl','uz','Dutch'),(2361,'nl','vi','Dutch'),(2362,'nl','yi','Dutch'),(2363,'nl','zh-hans','荷兰语'),(2364,'nl','zu','Dutch'),(2365,'nl','zh-hant','荷蘭語'),(2366,'nl','ms','Dutch'),(2367,'nl','gl','Dutch'),(2368,'nl','bn','Dutch'),(2369,'no','en','Norwegian Bokmål'),(2370,'no','es','Bokmål'),(2371,'no','de','Norwegisch (Buchsprache)'),(2372,'no','fr','Norvégien Bokmål'),(2373,'no','ar','البوكمالية النرويجية'),(2374,'no','bs','Norwegian Bokmål'),(2375,'no','bg','Норвежки книжовен'),(2376,'no','ca','Norwegian Bokmål'),(2377,'no','cs','Norwegian bokmål'),(2378,'no','sk','Nórsky jazyk Bokmål'),(2379,'no','cy','Norwegian Bokmål'),(2380,'no','da','Norwegian Bokmål'),(2381,'no','el','Νορβηγικα'),(2382,'no','eo','Norwegian Bokmål'),(2383,'no','et','Norwegian Bokmål'),(2384,'no','eu','Norwegian Bokmål'),(2385,'no','fa','Norwegian Bokmål'),(2386,'no','fi','kirjanorja'),(2387,'no','ga','Norwegian Bokmål'),(2388,'no','he','נורווגית'),(2389,'no','hi','Norwegian Bokmål'),(2390,'no','hr','Književni norveški'),(2391,'no','hu','norvég bokmål'),(2392,'no','hy','Norwegian Bokmål'),(2393,'no','id','Norwegian Bokmål'),(2394,'no','is','Norwegian Bokmål'),(2395,'no','it','Norvegese Bokmål'),(2396,'no','ja','ノルウェー・ブークモール'),(2397,'no','ko','노르웨이 보크말어'),(2398,'no','ku','Norwegian Bokmål'),(2399,'no','lv','Norwegian Bokmål'),(2400,'no','lt','Norwegian Bokmål'),(2401,'no','mk','Norwegian Bokmål'),(2402,'no','mt','Norwegian Bokmål'),(2403,'no','mn','Norwegian Bokmål'),(2404,'no','ne','Norwegian Bokmål'),(2405,'no','nl','Noors Bokmål'),(2406,'no','no','Norsk bokmål'),(2407,'no','pa','Norwegian Bokmål'),(2408,'no','pl','norweski bokmål'),(2409,'no','pt-pt','Norueguês'),(2410,'no','pt-br','Norueguês'),(2411,'no','qu','Norwegian Bokmål'),(2412,'no','ro','Bokmål (norvegiană)'),(2413,'no','ru','Норвежский букмол'),(2414,'no','sl','Knjižna norveščina'),(2415,'no','so','Norwegian Bokmål'),(2416,'no','sq','Norwegian Bokmål'),(2417,'no','sr','Норвешки бокмал'),(2418,'no','sv','Norskt Bokmål'),(2419,'no','ta','Norwegian Bokmål'),(2420,'no','th','นอร์วิเจียนบอกมาล'),(2421,'no','tr','Bokmal Norveç dili'),(2422,'no','uk','Norwegian Bokmål'),(2423,'no','ur','Norwegian Bokmål'),(2424,'no','uz','Norwegian Bokmål'),(2425,'no','vi','Norwegian Bokmål'),(2426,'no','yi','Norwegian Bokmål'),(2427,'no','zh-hans','挪威布克莫尔语'),(2428,'no','zu','Norwegian Bokmål'),(2429,'no','zh-hant','挪威布克莫爾語'),(2430,'no','ms','Norwegian Bokmål'),(2431,'no','gl','Norwegian Bokmål'),(2432,'no','bn','Norwegian Bokmål'),(2433,'pa','en','Punjabi'),(2434,'pa','es','Panyabí'),(2435,'pa','de','Pandschabi'),(2436,'pa','fr','Panjabi'),(2437,'pa','ar','البنجابية'),(2438,'pa','bs','Punjabi'),(2439,'pa','bg','Панджабски'),(2440,'pa','ca','Punjabi'),(2441,'pa','cs','Punjabi'),(2442,'pa','sk','Pandžábčina'),(2443,'pa','cy','Punjabi'),(2444,'pa','da','Punjabi'),(2445,'pa','el','Panjabi'),(2446,'pa','eo','Punjabi'),(2447,'pa','et','Punjabi'),(2448,'pa','eu','Punjabi'),(2449,'pa','fa','Punjabi'),(2450,'pa','fi','pandzabi'),(2451,'pa','ga','Punjabi'),(2452,'pa','he','פנג\'אבית'),(2453,'pa','hi','Punjabi'),(2454,'pa','hr','Pendžabljanin'),(2455,'pa','hu','pandzsábi'),(2456,'pa','hy','Punjabi'),(2457,'pa','id','Punjabi'),(2458,'pa','is','Punjabi'),(2459,'pa','it','Panjabi'),(2460,'pa','ja','パンジャーブ語'),(2461,'pa','ko','펀자브어'),(2462,'pa','ku','Punjabi'),(2463,'pa','lv','Punjabi'),(2464,'pa','lt','Punjabi'),(2465,'pa','mk','Punjabi'),(2466,'pa','mt','Punjabi'),(2467,'pa','mn','Punjabi'),(2468,'pa','ne','Punjabi'),(2469,'pa','nl','Punjabi'),(2470,'pa','no','Punjabi'),(2471,'pa','pa','Punjabi'),(2472,'pa','pl','pendżabi'),(2473,'pa','pt-pt','Panjabi'),(2474,'pa','pt-br','Panjabi'),(2475,'pa','qu','Punjabi'),(2476,'pa','ro','Punjabi'),(2477,'pa','ru','Панджаби'),(2478,'pa','sl','Pandžabščina'),(2479,'pa','so','Punjabi'),(2480,'pa','sq','Punjabi'),(2481,'pa','sr','панџаби'),(2482,'pa','sv','Punjabi'),(2483,'pa','ta','Punjabi'),(2484,'pa','th','ปัญจาบ'),(2485,'pa','tr','Pencapça'),(2486,'pa','uk','Punjabi'),(2487,'pa','ur','Punjabi'),(2488,'pa','uz','Punjabi'),(2489,'pa','vi','Punjabi'),(2490,'pa','yi','Punjabi'),(2491,'pa','zh-hans','旁遮普语'),(2492,'pa','zu','Punjabi'),(2493,'pa','zh-hant','旁遮普語'),(2494,'pa','ms','Punjabi'),(2495,'pa','gl','Punjabi'),(2496,'pa','bn','Punjabi'),(2497,'pl','en','Polish'),(2498,'pl','es','Polaco'),(2499,'pl','de','Polnisch'),(2500,'pl','fr','Polonais'),(2501,'pl','ar','البولندية'),(2502,'pl','bs','Polish'),(2503,'pl','bg','Полски'),(2504,'pl','ca','Polish'),(2505,'pl','cs','Polský'),(2506,'pl','sk','Polština'),(2507,'pl','cy','Polish'),(2508,'pl','da','Polish'),(2509,'pl','el','Πολωνικα'),(2510,'pl','eo','Polish'),(2511,'pl','et','Polish'),(2512,'pl','eu','Polish'),(2513,'pl','fa','Polish'),(2514,'pl','fi','puola'),(2515,'pl','ga','Polish'),(2516,'pl','he','פולנית'),(2517,'pl','hi','Polish'),(2518,'pl','hr','Poljski'),(2519,'pl','hu','lengyel'),(2520,'pl','hy','Polish'),(2521,'pl','id','Polish'),(2522,'pl','is','Polish'),(2523,'pl','it','Polacco'),(2524,'pl','ja','ポーランド語'),(2525,'pl','ko','폴란드어'),(2526,'pl','ku','Polish'),(2527,'pl','lv','Polish'),(2528,'pl','lt','Polish'),(2529,'pl','mk','Polish'),(2530,'pl','mt','Polish'),(2531,'pl','mn','Polish'),(2532,'pl','ne','Polish'),(2533,'pl','nl','Pools'),(2534,'pl','no','Polsk'),(2535,'pl','pa','Polish'),(2536,'pl','pl','polski'),(2537,'pl','pt-pt','Polonês'),(2538,'pl','pt-br','Polonês'),(2539,'pl','qu','Polish'),(2540,'pl','ro','Poloneză'),(2541,'pl','ru','Польский'),(2542,'pl','sl','Poljski'),(2543,'pl','so','Polish'),(2544,'pl','sq','Polish'),(2545,'pl','sr','пољски'),(2546,'pl','sv','Polska'),(2547,'pl','ta','Polish'),(2548,'pl','th','โปแลนด์'),(2549,'pl','tr','Polonyaca'),(2550,'pl','uk','Polish'),(2551,'pl','ur','Polish'),(2552,'pl','uz','Polish'),(2553,'pl','vi','Polish'),(2554,'pl','yi','Polish'),(2555,'pl','zh-hans','波兰语'),(2556,'pl','zu','Polish'),(2557,'pl','zh-hant','波蘭語'),(2558,'pl','ms','Polish'),(2559,'pl','gl','Polish'),(2560,'pl','bn','Polish'),(2561,'pt-pt','en','Portuguese (Portugal)'),(2562,'pt-pt','es','Portugués, Portugal'),(2563,'pt-pt','de','Portugiesisch, Portugal'),(2564,'pt-pt','fr','Portugais - du Portugal'),(2565,'pt-pt','ar','البرتغالية ، البرتغال'),(2566,'pt-pt','bs','Portuguese, Portugal'),(2567,'pt-pt','bg','Португалски (Португалия)'),(2568,'pt-pt','ca','Portuguese, Portugal'),(2569,'pt-pt','cs','Portugalština ( Portugalsko)'),(2570,'pt-pt','sk','Portugalština'),(2571,'pt-pt','cy','Portuguese, Portugal'),(2572,'pt-pt','da','Portuguese, Portugal'),(2573,'pt-pt','el','Πορτογαλικα'),(2574,'pt-pt','eo','Portuguese, Portugal'),(2575,'pt-pt','et','Portuguese, Portugal'),(2576,'pt-pt','eu','Portuguese, Portugal'),(2577,'pt-pt','fa','Portuguese, Portugal'),(2578,'pt-pt','fi','portugali'),(2579,'pt-pt','ga','Portuguese, Portugal'),(2580,'pt-pt','he','פורטוגזית'),(2581,'pt-pt','hi','Portuguese, Portugal'),(2582,'pt-pt','hr','Portugalski (Portugal)'),(2583,'pt-pt','hu','portugál'),(2584,'pt-pt','hy','Portuguese, Portugal'),(2585,'pt-pt','id','Portuguese, Portugal'),(2586,'pt-pt','is','Portuguese, Portugal'),(2587,'pt-pt','it','Portoghese, Portogallo'),(2588,'pt-pt','ja','ポルトガル語'),(2589,'pt-pt','ko','포르투갈 포르투갈어'),(2590,'pt-pt','ku','Portuguese, Portugal'),(2591,'pt-pt','lv','Portuguese, Portugal'),(2592,'pt-pt','lt','Portuguese, Portugal'),(2593,'pt-pt','mk','Portuguese, Portugal'),(2594,'pt-pt','mt','Portuguese, Portugal'),(2595,'pt-pt','mn','Portuguese, Portugal'),(2596,'pt-pt','ne','Portuguese, Portugal'),(2597,'pt-pt','nl','Portugees, Portugal'),(2598,'pt-pt','no','Portugisisk (Portugal)'),(2599,'pt-pt','pa','Portuguese, Portugal'),(2600,'pt-pt','pl','portugalski, Portugalia'),(2601,'pt-pt','pt-pt','Português'),(2602,'pt-pt','pt-br','Português'),(2603,'pt-pt','qu','Portuguese, Portugal'),(2604,'pt-pt','ro','Portugheză (Portugalia)'),(2605,'pt-pt','ru','Португальский, Португалия'),(2606,'pt-pt','sl','Portugalščina ( Portugalska )'),(2607,'pt-pt','so','Portuguese, Portugal'),(2608,'pt-pt','sq','Portuguese, Portugal'),(2609,'pt-pt','sr','Португалски (Португалија)'),(2610,'pt-pt','sv','Portugisiska, Portugal'),(2611,'pt-pt','ta','Portuguese, Portugal'),(2612,'pt-pt','th','โปรตุเกส'),(2613,'pt-pt','tr','Portekizce, Portekiz'),(2614,'pt-pt','uk','Portuguese, Portugal'),(2615,'pt-pt','ur','Portuguese, Portugal'),(2616,'pt-pt','uz','Portuguese, Portugal'),(2617,'pt-pt','vi','Portuguese, Portugal'),(2618,'pt-pt','yi','Portuguese, Portugal'),(2619,'pt-pt','zh-hans','葡萄牙语（葡萄牙）'),(2620,'pt-pt','zu','Portuguese, Portugal'),(2621,'pt-pt','zh-hant','葡萄牙語（葡萄牙）'),(2622,'pt-pt','ms','Portuguese, Portugal'),(2623,'pt-pt','gl','Portuguese, Portugal'),(2624,'pt-pt','bn','Portuguese, Portugal'),(2625,'pt-br','en','Portuguese (Brazil)'),(2626,'pt-br','es','Portugués, Brasil'),(2627,'pt-br','de','Portugiesisch, Brasilien'),(2628,'pt-br','fr','Portugais - du Brésil'),(2629,'pt-br','ar','البرتغالية ،البرازيل'),(2630,'pt-br','bs','Portuguese, Brazil'),(2631,'pt-br','bg','Португалски (Бразилия)'),(2632,'pt-br','ca','Portuguese, Brazil'),(2633,'pt-br','cs','Portugalština ( Brazílie)'),(2634,'pt-br','sk','Brazílska Portugalština'),(2635,'pt-br','cy','Portuguese, Brazil'),(2636,'pt-br','da','Portuguese, Brazil'),(2637,'pt-br','el','Πορτογαλικα'),(2638,'pt-br','eo','Portuguese, Brazil'),(2639,'pt-br','et','Portuguese, Brazil'),(2640,'pt-br','eu','Portuguese, Brazil'),(2641,'pt-br','fa','Portuguese, Brazil'),(2642,'pt-br','fi','Brasilian portugali'),(2643,'pt-br','ga','Portuguese, Brazil'),(2644,'pt-br','he','פורטוגזית - ברזיל'),(2645,'pt-br','hi','Portuguese, Brazil'),(2646,'pt-br','hr','Portugalski (Brazil)'),(2647,'pt-br','hu','brazil'),(2648,'pt-br','hy','Portuguese, Brazil'),(2649,'pt-br','id','Portuguese, Brazil'),(2650,'pt-br','is','Portuguese, Brazil'),(2651,'pt-br','it','Portoghese, Brasile'),(2652,'pt-br','ja','ポルトガル語（ブラジル）'),(2653,'pt-br','ko','브라질 포르투갈어'),(2654,'pt-br','ku','Portuguese, Brazil'),(2655,'pt-br','lv','Portuguese, Brazil'),(2656,'pt-br','lt','Portuguese, Brazil'),(2657,'pt-br','mk','Portuguese, Brazil'),(2658,'pt-br','mt','Portuguese, Brazil'),(2659,'pt-br','mn','Portuguese, Brazil'),(2660,'pt-br','ne','Portuguese, Brazil'),(2661,'pt-br','nl','Portugees, Brazilië'),(2662,'pt-br','no','Portugisisk (Brasil)'),(2663,'pt-br','pa','Portuguese, Brazil'),(2664,'pt-br','pl','portugalski, Brazylia'),(2665,'pt-br','pt-pt','Português'),(2666,'pt-br','pt-br','Português'),(2667,'pt-br','qu','Portuguese, Brazil'),(2668,'pt-br','ro','Portugheză (Brazilia)'),(2669,'pt-br','ru','Португальский, Бразилия'),(2670,'pt-br','sl','Portugalščina ( Brazilija )'),(2671,'pt-br','so','Portuguese, Brazil'),(2672,'pt-br','sq','Portuguese, Brazil'),(2673,'pt-br','sr','Португалски (Бразил)'),(2674,'pt-br','sv','Portugisiska, Brasilien'),(2675,'pt-br','ta','Portuguese, Brazil'),(2676,'pt-br','th','โปรตุเกสบราซิล'),(2677,'pt-br','tr','Portekizce, Brezilya'),(2678,'pt-br','uk','Portuguese, Brazil'),(2679,'pt-br','ur','Portuguese, Brazil'),(2680,'pt-br','uz','Portuguese, Brazil'),(2681,'pt-br','vi','Portuguese, Brazil'),(2682,'pt-br','yi','Portuguese, Brazil'),(2683,'pt-br','zh-hans','葡萄牙语（巴西）'),(2684,'pt-br','zu','Portuguese, Brazil'),(2685,'pt-br','zh-hant','葡萄牙語（巴西）'),(2686,'pt-br','ms','Portuguese, Brazil'),(2687,'pt-br','gl','Portuguese, Brazil'),(2688,'pt-br','bn','Portuguese, Brazil'),(2689,'qu','en','Quechua'),(2690,'qu','es','Quechua'),(2691,'qu','de','Quechua'),(2692,'qu','fr','Quechua'),(2693,'qu','ar','الكويتشوا'),(2694,'qu','bs','Quechua'),(2695,'qu','bg','Кечуа'),(2696,'qu','ca','Quechua'),(2697,'qu','cs','Quechua'),(2698,'qu','sk','Jazyk Quechua'),(2699,'qu','cy','Quechua'),(2700,'qu','da','Quechua'),(2701,'qu','el','Κετσουα'),(2702,'qu','eo','Quechua'),(2703,'qu','et','Quechua'),(2704,'qu','eu','Quechua'),(2705,'qu','fa','Quechua'),(2706,'qu','fi','ketsua'),(2707,'qu','ga','Quechua'),(2708,'qu','he','קצ\'ואה'),(2709,'qu','hi','Quechua'),(2710,'qu','hr','Quechua'),(2711,'qu','hu','quechua'),(2712,'qu','hy','Quechua'),(2713,'qu','id','Quechua'),(2714,'qu','is','Quechua'),(2715,'qu','it','Quechua'),(2716,'qu','ja','ケチュア語'),(2717,'qu','ko','케추아어'),(2718,'qu','ku','Quechua'),(2719,'qu','lv','Quechua'),(2720,'qu','lt','Quechua'),(2721,'qu','mk','Quechua'),(2722,'qu','mt','Quechua'),(2723,'qu','mn','Quechua'),(2724,'qu','ne','Quechua'),(2725,'qu','nl','Quechua'),(2726,'qu','no','Quechua'),(2727,'qu','pa','Quechua'),(2728,'qu','pl','keczua'),(2729,'qu','pt-pt','Quechua'),(2730,'qu','pt-br','Quechua'),(2731,'qu','qu','Quechua'),(2732,'qu','ro','Quechuană'),(2733,'qu','ru','Кечуа'),(2734,'qu','sl','Quechua'),(2735,'qu','so','Quechua'),(2736,'qu','sq','Quechua'),(2737,'qu','sr','Кечуа'),(2738,'qu','sv','Quechua'),(2739,'qu','ta','Quechua'),(2740,'qu','th','คิวชัว'),(2741,'qu','tr','Quechua dili'),(2742,'qu','uk','Quechua'),(2743,'qu','ur','Quechua'),(2744,'qu','uz','Quechua'),(2745,'qu','vi','Quechua'),(2746,'qu','yi','Quechua'),(2747,'qu','zh-hans','盖丘亚语'),(2748,'qu','zu','Quechua'),(2749,'qu','zh-hant','蓋丘亞語'),(2750,'qu','ms','Quechua'),(2751,'qu','gl','Quechua'),(2752,'qu','bn','Quechua'),(2753,'ro','en','Romanian'),(2754,'ro','es','Rumano'),(2755,'ro','de','Rumänisch'),(2756,'ro','fr','Roumain'),(2757,'ro','ar','الرومانية'),(2758,'ro','bs','Romanian'),(2759,'ro','bg','Румънски'),(2760,'ro','ca','Romanian'),(2761,'ro','cs','Rumunština'),(2762,'ro','sk','Rumunčina'),(2763,'ro','cy','Romanian'),(2764,'ro','da','Romanian'),(2765,'ro','el','Ρουμανικα'),(2766,'ro','eo','Romanian'),(2767,'ro','et','Romanian'),(2768,'ro','eu','Romanian'),(2769,'ro','fa','Romanian'),(2770,'ro','fi','romania'),(2771,'ro','ga','Romanian'),(2772,'ro','he','רומנית'),(2773,'ro','hi','Romanian'),(2774,'ro','hr','Rumunjski'),(2775,'ro','hu','román'),(2776,'ro','hy','Romanian'),(2777,'ro','id','Romanian'),(2778,'ro','is','Romanian'),(2779,'ro','it','Rumeno'),(2780,'ro','ja','ルーマニア語'),(2781,'ro','ko','로마니아어'),(2782,'ro','ku','Romanian'),(2783,'ro','lv','Romanian'),(2784,'ro','lt','Romanian'),(2785,'ro','mk','Romanian'),(2786,'ro','mt','Romanian'),(2787,'ro','mn','Romanian'),(2788,'ro','ne','Romanian'),(2789,'ro','nl','Roemeens'),(2790,'ro','no','Rumensk'),(2791,'ro','pa','Romanian'),(2792,'ro','pl','rumuński'),(2793,'ro','pt-pt','Romeno'),(2794,'ro','pt-br','Romeno'),(2795,'ro','qu','Romanian'),(2796,'ro','ro','Română'),(2797,'ro','ru','Румынский'),(2798,'ro','sl','Romunščina'),(2799,'ro','so','Romanian'),(2800,'ro','sq','Romanian'),(2801,'ro','sr','румунски'),(2802,'ro','sv','Rumänska'),(2803,'ro','ta','Romanian'),(2804,'ro','th','โรมาเนีย'),(2805,'ro','tr','Rumence'),(2806,'ro','uk','Romanian'),(2807,'ro','ur','Romanian'),(2808,'ro','uz','Romanian'),(2809,'ro','vi','Romanian'),(2810,'ro','yi','Romanian'),(2811,'ro','zh-hans','罗马尼亚语'),(2812,'ro','zu','Romanian'),(2813,'ro','zh-hant','羅馬尼亞語'),(2814,'ro','ms','Romanian'),(2815,'ro','gl','Romanian'),(2816,'ro','bn','Romanian'),(2817,'ru','en','Russian'),(2818,'ru','es','Ruso'),(2819,'ru','de','Russisch'),(2820,'ru','fr','Russe'),(2821,'ru','ar','الروسية'),(2822,'ru','bs','Russian'),(2823,'ru','bg','Руски'),(2824,'ru','ca','Russian'),(2825,'ru','cs','Ruský'),(2826,'ru','sk','Ruština'),(2827,'ru','cy','Russian'),(2828,'ru','da','Russian'),(2829,'ru','el','Ρωσικα'),(2830,'ru','eo','Russian'),(2831,'ru','et','Russian'),(2832,'ru','eu','Russian'),(2833,'ru','fa','Russian'),(2834,'ru','fi','venäjä'),(2835,'ru','ga','Russian'),(2836,'ru','he','רוסית'),(2837,'ru','hi','Russian'),(2838,'ru','hr','Ruski'),(2839,'ru','hu','orosz'),(2840,'ru','hy','Russian'),(2841,'ru','id','Russian'),(2842,'ru','is','Russian'),(2843,'ru','it','Russo'),(2844,'ru','ja','ロシア語'),(2845,'ru','ko','러시아어'),(2846,'ru','ku','Russian'),(2847,'ru','lv','Russian'),(2848,'ru','lt','Russian'),(2849,'ru','mk','Russian'),(2850,'ru','mt','Russian'),(2851,'ru','mn','Russian'),(2852,'ru','ne','Russian'),(2853,'ru','nl','Russisch'),(2854,'ru','no','Russisk'),(2855,'ru','pa','Russian'),(2856,'ru','pl','rosyjski'),(2857,'ru','pt-pt','Russo'),(2858,'ru','pt-br','Russo'),(2859,'ru','qu','Russian'),(2860,'ru','ro','Rusă'),(2861,'ru','ru','Русский'),(2862,'ru','sl','Ruščina'),(2863,'ru','so','Russian'),(2864,'ru','sq','Russian'),(2865,'ru','sr','руски'),(2866,'ru','sv','Ryska'),(2867,'ru','ta','Russian'),(2868,'ru','th','รัสเซีย'),(2869,'ru','tr','Rusça'),(2870,'ru','uk','Russian'),(2871,'ru','ur','Russian'),(2872,'ru','uz','Russian'),(2873,'ru','vi','Russian'),(2874,'ru','yi','Russian'),(2875,'ru','zh-hans','俄语'),(2876,'ru','zu','Russian'),(2877,'ru','zh-hant','俄語'),(2878,'ru','ms','Russian'),(2879,'ru','gl','Russian'),(2880,'ru','bn','Russian'),(2881,'sl','en','Slovenian'),(2882,'sl','es','Esloveno'),(2883,'sl','de','Slowenisch'),(2884,'sl','fr','Slovène'),(2885,'sl','ar','السلوفانية'),(2886,'sl','bs','Slovenian'),(2887,'sl','bg','Словенски'),(2888,'sl','ca','Slovenian'),(2889,'sl','cs','Slovinština'),(2890,'sl','sk','Slovinčina'),(2891,'sl','cy','Slovenian'),(2892,'sl','da','Slovenian'),(2893,'sl','el','Σλοβενικα'),(2894,'sl','eo','Slovenian'),(2895,'sl','et','Slovenian'),(2896,'sl','eu','Slovenian'),(2897,'sl','fa','Slovenian'),(2898,'sl','fi','sloveeni'),(2899,'sl','ga','Slovenian'),(2900,'sl','he','סלובנית'),(2901,'sl','hi','Slovenian'),(2902,'sl','hr','Slovenac'),(2903,'sl','hu','szlovén'),(2904,'sl','hy','Slovenian'),(2905,'sl','id','Slovenian'),(2906,'sl','is','Slovenian'),(2907,'sl','it','Sloveno'),(2908,'sl','ja','スロベニア語'),(2909,'sl','ko','슬로베니아어'),(2910,'sl','ku','Slovenian'),(2911,'sl','lv','Slovenian'),(2912,'sl','lt','Slovenian'),(2913,'sl','mk','Slovenian'),(2914,'sl','mt','Slovenian'),(2915,'sl','mn','Slovenian'),(2916,'sl','ne','Slovenian'),(2917,'sl','nl','Sloveens'),(2918,'sl','no','Slovensk'),(2919,'sl','pa','Slovenian'),(2920,'sl','pl','słoweński'),(2921,'sl','pt-pt','Esloveno'),(2922,'sl','pt-br','Esloveno'),(2923,'sl','qu','Slovenian'),(2924,'sl','ro','Slovenă'),(2925,'sl','ru','Словенский'),(2926,'sl','sl','Slovenščina'),(2927,'sl','so','Slovenian'),(2928,'sl','sq','Slovenian'),(2929,'sl','sr','словеначки'),(2930,'sl','sv','Slovenska'),(2931,'sl','ta','Slovenian'),(2932,'sl','th','สโลวีเนียน'),(2933,'sl','tr','Sloven dili'),(2934,'sl','uk','Slovenian'),(2935,'sl','ur','Slovenian'),(2936,'sl','uz','Slovenian'),(2937,'sl','vi','Slovenian'),(2938,'sl','yi','Slovenian'),(2939,'sl','zh-hans','斯洛文尼亚语'),(2940,'sl','zu','Slovenian'),(2941,'sl','zh-hant','斯洛文尼亞語'),(2942,'sl','ms','Slovenian'),(2943,'sl','gl','Slovenian'),(2944,'sl','bn','Slovenian'),(2945,'so','en','Somali'),(2946,'so','es','Somalí'),(2947,'so','de','Somali'),(2948,'so','fr','Somali'),(2949,'so','ar','الصومالية'),(2950,'so','bs','Somali'),(2951,'so','bg','Сомалийски'),(2952,'so','ca','Somali'),(2953,'so','cs','Somali'),(2954,'so','sk','Somálčina'),(2955,'so','cy','Somali'),(2956,'so','da','Somali'),(2957,'so','el','Somali'),(2958,'so','eo','Somali'),(2959,'so','et','Somali'),(2960,'so','eu','Somali'),(2961,'so','fa','Somali'),(2962,'so','fi','somali'),(2963,'so','ga','Somali'),(2964,'so','he','סומלית'),(2965,'so','hi','Somali'),(2966,'so','hr','Somalijski'),(2967,'so','hu','szomáli'),(2968,'so','hy','Somali'),(2969,'so','id','Somali'),(2970,'so','is','Somali'),(2971,'so','it','Somalo'),(2972,'so','ja','ソマリ語'),(2973,'so','ko','소말리아어'),(2974,'so','ku','Somali'),(2975,'so','lv','Somali'),(2976,'so','lt','Somali'),(2977,'so','mk','Somali'),(2978,'so','mt','Somali'),(2979,'so','mn','Somali'),(2980,'so','ne','Somali'),(2981,'so','nl','Somalisch'),(2982,'so','no','Somali'),(2983,'so','pa','Somali'),(2984,'so','pl','somalijski'),(2985,'so','pt-pt','Somali'),(2986,'so','pt-br','Somali'),(2987,'so','qu','Somali'),(2988,'so','ro','Somaleză'),(2989,'so','ru','Сомалийский'),(2990,'so','sl','Somalski'),(2991,'so','so','Somali'),(2992,'so','sq','Somali'),(2993,'so','sr','Сомалијски'),(2994,'so','sv','Somaliska'),(2995,'so','ta','Somali'),(2996,'so','th','โซมาลี'),(2997,'so','tr','Somalice'),(2998,'so','uk','Somali'),(2999,'so','ur','Somali'),(3000,'so','uz','Somali'),(3001,'so','vi','Somali'),(3002,'so','yi','Somali'),(3003,'so','zh-hans','索马里语'),(3004,'so','zu','Somali'),(3005,'so','zh-hant','索馬里語'),(3006,'so','ms','Somali'),(3007,'so','gl','Somali'),(3008,'so','bn','Somali'),(3009,'sq','en','Albanian'),(3010,'sq','es','Albanés'),(3011,'sq','de','Albanisch'),(3012,'sq','fr','Albanais'),(3013,'sq','ar','الألبانية'),(3014,'sq','bs','Albanian'),(3015,'sq','bg','Албански'),(3016,'sq','ca','Albanian'),(3017,'sq','cs','Albánský'),(3018,'sq','sk','Albánčina'),(3019,'sq','cy','Albanian'),(3020,'sq','da','Albanian'),(3021,'sq','el','Αλβανικα'),(3022,'sq','eo','Albanian'),(3023,'sq','et','Albanian'),(3024,'sq','eu','Albanian'),(3025,'sq','fa','Albanian'),(3026,'sq','fi','albania'),(3027,'sq','ga','Albanian'),(3028,'sq','he','אלבנית'),(3029,'sq','hi','Albanian'),(3030,'sq','hr','Albanac'),(3031,'sq','hu','albán'),(3032,'sq','hy','Albanian'),(3033,'sq','id','Albanian'),(3034,'sq','is','Albanian'),(3035,'sq','it','Albanese'),(3036,'sq','ja','アルバニア語'),(3037,'sq','ko','알바니아어'),(3038,'sq','ku','Albanian'),(3039,'sq','lv','Albanian'),(3040,'sq','lt','Albanian'),(3041,'sq','mk','Albanian'),(3042,'sq','mt','Albanian'),(3043,'sq','mn','Albanian'),(3044,'sq','ne','Albanian'),(3045,'sq','nl','Albaans'),(3046,'sq','no','Albansk'),(3047,'sq','pa','Albanian'),(3048,'sq','pl','albański'),(3049,'sq','pt-pt','Albanês'),(3050,'sq','pt-br','Albanês'),(3051,'sq','qu','Albanian'),(3052,'sq','ro','Albaneză'),(3053,'sq','ru','Албанский'),(3054,'sq','sl','Albanski'),(3055,'sq','so','Albanian'),(3056,'sq','sq','Albanian'),(3057,'sq','sr','албански'),(3058,'sq','sv','Albanska'),(3059,'sq','ta','Albanian'),(3060,'sq','th','อัลเบเนีย'),(3061,'sq','tr','Arnavutça'),(3062,'sq','uk','Albanian'),(3063,'sq','ur','Albanian'),(3064,'sq','uz','Albanian'),(3065,'sq','vi','Albanian'),(3066,'sq','yi','Albanian'),(3067,'sq','zh-hans','阿尔巴尼亚语'),(3068,'sq','zu','Albanian'),(3069,'sq','zh-hant','阿爾巴尼亞語'),(3070,'sq','ms','Albanian'),(3071,'sq','gl','Albanian'),(3072,'sq','bn','Albanian'),(3073,'sr','en','Serbian'),(3074,'sr','es','Serbio'),(3075,'sr','de','Serbisch'),(3076,'sr','fr','Serbe'),(3077,'sr','ar','الصربية'),(3078,'sr','bs','Serbian'),(3079,'sr','bg','Сръбски'),(3080,'sr','ca','Serbian'),(3081,'sr','cs','Srbský'),(3082,'sr','sk','Srbština'),(3083,'sr','cy','Serbian'),(3084,'sr','da','Serbian'),(3085,'sr','el','Σερβικα'),(3086,'sr','eo','Serbian'),(3087,'sr','et','Serbian'),(3088,'sr','eu','Serbian'),(3089,'sr','fa','Serbian'),(3090,'sr','fi','serbia'),(3091,'sr','ga','Serbian'),(3092,'sr','he','סרבית'),(3093,'sr','hi','Serbian'),(3094,'sr','hr','Srpski'),(3095,'sr','hu','szerb'),(3096,'sr','hy','Serbian'),(3097,'sr','id','Serbian'),(3098,'sr','is','Serbian'),(3099,'sr','it','Serbo'),(3100,'sr','ja','セルビア語'),(3101,'sr','ko','세르비아어'),(3102,'sr','ku','Serbian'),(3103,'sr','lv','Serbian'),(3104,'sr','lt','Serbian'),(3105,'sr','mk','Serbian'),(3106,'sr','mt','Serbian'),(3107,'sr','mn','Serbian'),(3108,'sr','ne','Serbian'),(3109,'sr','nl','Servisch'),(3110,'sr','no','Serbisk'),(3111,'sr','pa','Serbian'),(3112,'sr','pl','serbski'),(3113,'sr','pt-pt','Sérvio'),(3114,'sr','pt-br','Sérvio'),(3115,'sr','qu','Serbian'),(3116,'sr','ro','Sârbă'),(3117,'sr','ru','Сербский'),(3118,'sr','sl','Srbski'),(3119,'sr','so','Serbian'),(3120,'sr','sq','Serbian'),(3121,'sr','sr','српски'),(3122,'sr','sv','Serbiska'),(3123,'sr','ta','Serbian'),(3124,'sr','th','เซอร์เบีย'),(3125,'sr','tr','Sırpça'),(3126,'sr','uk','Serbian'),(3127,'sr','ur','Serbian'),(3128,'sr','uz','Serbian'),(3129,'sr','vi','Serbian'),(3130,'sr','yi','Serbian'),(3131,'sr','zh-hans','赛尔维亚语'),(3132,'sr','zu','Serbian'),(3133,'sr','zh-hant','賽爾維亞語'),(3134,'sr','ms','Serbian'),(3135,'sr','gl','Serbian'),(3136,'sr','bn','Serbian'),(3137,'sv','en','Swedish'),(3138,'sv','es','Sueco'),(3139,'sv','de','Schwedisch'),(3140,'sv','fr','Suédois'),(3141,'sv','ar','السويدية'),(3142,'sv','bs','Swedish'),(3143,'sv','bg','Шведски'),(3144,'sv','ca','Swedish'),(3145,'sv','cs','Švédský'),(3146,'sv','sk','Švédština'),(3147,'sv','cy','Swedish'),(3148,'sv','da','Swedish'),(3149,'sv','el','Σουηδικη'),(3150,'sv','eo','Swedish'),(3151,'sv','et','Swedish'),(3152,'sv','eu','Swedish'),(3153,'sv','fa','Swedish'),(3154,'sv','fi','ruotsi'),(3155,'sv','ga','Swedish'),(3156,'sv','he','שוודית'),(3157,'sv','hi','Swedish'),(3158,'sv','hr','švedski'),(3159,'sv','hu','svéd'),(3160,'sv','hy','Swedish'),(3161,'sv','id','Swedish'),(3162,'sv','is','Swedish'),(3163,'sv','it','Svedese'),(3164,'sv','ja','スウェーデン語'),(3165,'sv','ko','스웨덴어'),(3166,'sv','ku','Swedish'),(3167,'sv','lv','Swedish'),(3168,'sv','lt','Swedish'),(3169,'sv','mk','Swedish'),(3170,'sv','mt','Swedish'),(3171,'sv','mn','Swedish'),(3172,'sv','ne','Swedish'),(3173,'sv','nl','Zweeds'),(3174,'sv','no','Swedish'),(3175,'sv','pa','Swedish'),(3176,'sv','pl','szwedzki'),(3177,'sv','pt-pt','Sueco'),(3178,'sv','pt-br','Sueco'),(3179,'sv','qu','Swedish'),(3180,'sv','ro','Suedeză'),(3181,'sv','ru','Шведский'),(3182,'sv','sl','Švedščina'),(3183,'sv','so','Swedish'),(3184,'sv','sq','Swedish'),(3185,'sv','sr','шведски'),(3186,'sv','sv','Svenska'),(3187,'sv','ta','Swedish'),(3188,'sv','th','สวีเดน'),(3189,'sv','tr','İsveççe'),(3190,'sv','uk','Swedish'),(3191,'sv','ur','Swedish'),(3192,'sv','uz','Swedish'),(3193,'sv','vi','Swedish'),(3194,'sv','yi','Swedish'),(3195,'sv','zh-hans','瑞典语'),(3196,'sv','zu','Swedish'),(3197,'sv','zh-hant','瑞典語'),(3198,'sv','ms','Swedish'),(3199,'sv','gl','Swedish'),(3200,'sv','bn','Swedish'),(3201,'ta','en','Tamil'),(3202,'ta','es','Tamil'),(3203,'ta','de','Tamil'),(3204,'ta','fr','Tamoul'),(3205,'ta','ar','التاميلية'),(3206,'ta','bs','Tamil'),(3207,'ta','bg','Тамилски'),(3208,'ta','ca','Tamil'),(3209,'ta','cs','Tamil'),(3210,'ta','sk','Tamilčina'),(3211,'ta','cy','Tamil'),(3212,'ta','da','Tamil'),(3213,'ta','el','Ταμιλ'),(3214,'ta','eo','Tamil'),(3215,'ta','et','Tamil'),(3216,'ta','eu','Tamil'),(3217,'ta','fa','Tamil'),(3218,'ta','fi','tamili'),(3219,'ta','ga','Tamil'),(3220,'ta','he','טמילית'),(3221,'ta','hi','Tamil'),(3222,'ta','hr','Tamil'),(3223,'ta','hu','tamil'),(3224,'ta','hy','Tamil'),(3225,'ta','id','Tamil'),(3226,'ta','is','Tamil'),(3227,'ta','it','Tamil'),(3228,'ta','ja','タミル語'),(3229,'ta','ko','타밀어'),(3230,'ta','ku','Tamil'),(3231,'ta','lv','Tamil'),(3232,'ta','lt','Tamil'),(3233,'ta','mk','Tamil'),(3234,'ta','mt','Tamil'),(3235,'ta','mn','Tamil'),(3236,'ta','ne','Tamil'),(3237,'ta','nl','Tamil'),(3238,'ta','no','Tamil'),(3239,'ta','pa','Tamil'),(3240,'ta','pl','tamilski'),(3241,'ta','pt-pt','Tamil'),(3242,'ta','pt-br','Tamil'),(3243,'ta','qu','Tamil'),(3244,'ta','ro','Tamilă'),(3245,'ta','ru','Тамильский'),(3246,'ta','sl','Tamilščina'),(3247,'ta','so','Tamil'),(3248,'ta','sq','Tamil'),(3249,'ta','sr','тамилски'),(3250,'ta','sv','Tamil'),(3251,'ta','ta','Tamil'),(3252,'ta','th','ทมิฬ'),(3253,'ta','tr','Tamil dili'),(3254,'ta','uk','Tamil'),(3255,'ta','ur','Tamil'),(3256,'ta','uz','Tamil'),(3257,'ta','vi','Tamil'),(3258,'ta','yi','Tamil'),(3259,'ta','zh-hans','泰米尔语'),(3260,'ta','zu','Tamil'),(3261,'ta','zh-hant','泰米爾語'),(3262,'ta','ms','Tamil'),(3263,'ta','gl','Tamil'),(3264,'ta','bn','Tamil'),(3265,'th','en','Thai'),(3266,'th','es','Tailandés'),(3267,'th','de','Thai'),(3268,'th','fr','Thaï'),(3269,'th','ar','التايلندية'),(3270,'th','bs','Thai'),(3271,'th','bg','Тайски'),(3272,'th','ca','Thai'),(3273,'th','cs','Thai'),(3274,'th','sk','Thajština'),(3275,'th','cy','Thai'),(3276,'th','da','Thai'),(3277,'th','el','Thai'),(3278,'th','eo','Thai'),(3279,'th','et','Thai'),(3280,'th','eu','Thai'),(3281,'th','fa','Thai'),(3282,'th','fi','thai'),(3283,'th','ga','Thai'),(3284,'th','he','תאילנדית'),(3285,'th','hi','Thai'),(3286,'th','hr','Thai'),(3287,'th','hu','tájföldi'),(3288,'th','hy','Thai'),(3289,'th','id','Thai'),(3290,'th','is','Thai'),(3291,'th','it','Thai'),(3292,'th','ja','タイ語'),(3293,'th','ko','태국어'),(3294,'th','ku','Thai'),(3295,'th','lv','Thai'),(3296,'th','lt','Thai'),(3297,'th','mk','Thai'),(3298,'th','mt','Thai'),(3299,'th','mn','Thai'),(3300,'th','ne','Thai'),(3301,'th','nl','Thai'),(3302,'th','no','Thai'),(3303,'th','pa','Thai'),(3304,'th','pl','tajski'),(3305,'th','pt-pt','Tailandês'),(3306,'th','pt-br','Tailandês'),(3307,'th','qu','Thai'),(3308,'th','ro','Tailandeză'),(3309,'th','ru','Тайский'),(3310,'th','sl','Tajski'),(3311,'th','so','Thai'),(3312,'th','sq','Thai'),(3313,'th','sr','Тајландски'),(3314,'th','sv','Thailändska'),(3315,'th','ta','Thai'),(3316,'th','th','ไทย'),(3317,'th','tr','Tayca'),(3318,'th','uk','Thai'),(3319,'th','ur','Thai'),(3320,'th','uz','Thai'),(3321,'th','vi','Thai'),(3322,'th','yi','Thai'),(3323,'th','zh-hans','泰语'),(3324,'th','zu','Thai'),(3325,'th','zh-hant','泰語'),(3326,'th','ms','Thai'),(3327,'th','gl','Thai'),(3328,'th','bn','Thai'),(3329,'tr','en','Turkish'),(3330,'tr','es','Turco'),(3331,'tr','de','Türkisch'),(3332,'tr','fr','Turc'),(3333,'tr','ar','التركية'),(3334,'tr','bs','Turkish'),(3335,'tr','bg','Турски'),(3336,'tr','ca','Turkish'),(3337,'tr','cs','Turečtina'),(3338,'tr','sk','Turečtina'),(3339,'tr','cy','Turkish'),(3340,'tr','da','Turkish'),(3341,'tr','el','Τουρκικα'),(3342,'tr','eo','Turkish'),(3343,'tr','et','Turkish'),(3344,'tr','eu','Turkish'),(3345,'tr','fa','Turkish'),(3346,'tr','fi','turkki'),(3347,'tr','ga','Turkish'),(3348,'tr','he','תורכית'),(3349,'tr','hi','Turkish'),(3350,'tr','hr','Turski'),(3351,'tr','hu','török'),(3352,'tr','hy','Turkish'),(3353,'tr','id','Turkish'),(3354,'tr','is','Turkish'),(3355,'tr','it','Turco'),(3356,'tr','ja','トルコ語'),(3357,'tr','ko','터어키어'),(3358,'tr','ku','Turkish'),(3359,'tr','lv','Turkish'),(3360,'tr','lt','Turkish'),(3361,'tr','mk','Turkish'),(3362,'tr','mt','Turkish'),(3363,'tr','mn','Turkish'),(3364,'tr','ne','Turkish'),(3365,'tr','nl','Turks'),(3366,'tr','no','Turkish'),(3367,'tr','pa','Turkish'),(3368,'tr','pl','turecki'),(3369,'tr','pt-pt','Turco'),(3370,'tr','pt-br','Turco'),(3371,'tr','qu','Turkish'),(3372,'tr','ro','Turcă'),(3373,'tr','ru','Турецкий'),(3374,'tr','sl','Turščina'),(3375,'tr','so','Turkish'),(3376,'tr','sq','Turkish'),(3377,'tr','sr','турски'),(3378,'tr','sv','Turkiska'),(3379,'tr','ta','Turkish'),(3380,'tr','th','ตุรกี'),(3381,'tr','tr','Türkçe'),(3382,'tr','uk','Turkish'),(3383,'tr','ur','Turkish'),(3384,'tr','uz','Turkish'),(3385,'tr','vi','Turkish'),(3386,'tr','yi','Turkish'),(3387,'tr','zh-hans','土耳其语'),(3388,'tr','zu','Turkish'),(3389,'tr','zh-hant','土耳其語'),(3390,'tr','ms','Turkish'),(3391,'tr','gl','Turkish'),(3392,'tr','bn','Turkish'),(3393,'uk','en','Ukrainian'),(3394,'uk','es','Ucraniano'),(3395,'uk','de','Ukrainisch'),(3396,'uk','fr','Ukrainien'),(3397,'uk','ar','الأوكرانية'),(3398,'uk','bs','Ukrainian'),(3399,'uk','bg','Украински'),(3400,'uk','ca','Ukrainian'),(3401,'uk','cs','Ukrajinský'),(3402,'uk','sk','Ukrajinčina'),(3403,'uk','cy','Ukrainian'),(3404,'uk','da','Ukrainian'),(3405,'uk','el','Ουκρανικα'),(3406,'uk','eo','Ukrainian'),(3407,'uk','et','Ukrainian'),(3408,'uk','eu','Ukrainian'),(3409,'uk','fa','Ukrainian'),(3410,'uk','fi','ukraina'),(3411,'uk','ga','Ukrainian'),(3412,'uk','he','אוקראינית'),(3413,'uk','hi','Ukrainian'),(3414,'uk','hr','Ukrajinski'),(3415,'uk','hu','ukrán'),(3416,'uk','hy','Ukrainian'),(3417,'uk','id','Ukrainian'),(3418,'uk','is','Ukrainian'),(3419,'uk','it','Ucraino'),(3420,'uk','ja','ウクライナ語'),(3421,'uk','ko','우크라이나어'),(3422,'uk','ku','Ukrainian'),(3423,'uk','lv','Ukrainian'),(3424,'uk','lt','Ukrainian'),(3425,'uk','mk','Ukrainian'),(3426,'uk','mt','Ukrainian'),(3427,'uk','mn','Ukrainian'),(3428,'uk','ne','Ukrainian'),(3429,'uk','nl','Oekraïens'),(3430,'uk','no','Ukrainsk'),(3431,'uk','pa','Ukrainian'),(3432,'uk','pl','ukraiński'),(3433,'uk','pt-pt','Ucraniano'),(3434,'uk','pt-br','Ucraniano'),(3435,'uk','qu','Ukrainian'),(3436,'uk','ro','Ucrainiană'),(3437,'uk','ru','Украинский'),(3438,'uk','sl','Ukrajinski'),(3439,'uk','so','Ukrainian'),(3440,'uk','sq','Ukrainian'),(3441,'uk','sr','украјински'),(3442,'uk','sv','Ukrainska'),(3443,'uk','ta','Ukrainian'),(3444,'uk','th','ยูเครน'),(3445,'uk','tr','Ukraynaca'),(3446,'uk','uk','Українська'),(3447,'uk','ur','Ukrainian'),(3448,'uk','uz','Ukrainian'),(3449,'uk','vi','Ukrainian'),(3450,'uk','yi','Ukrainian'),(3451,'uk','zh-hans','乌克兰语'),(3452,'uk','zu','Ukrainian'),(3453,'uk','zh-hant','烏克蘭語'),(3454,'uk','ms','Ukrainian'),(3455,'uk','gl','Ukrainian'),(3456,'uk','bn','Ukrainian'),(3457,'ur','en','Urdu'),(3458,'ur','es','Urdu'),(3459,'ur','de','Urdu'),(3460,'ur','fr','Ourdu'),(3461,'ur','ar','الأردية'),(3462,'ur','bs','Urdu'),(3463,'ur','bg','Урду'),(3464,'ur','ca','Urdu'),(3465,'ur','cs','Urdu'),(3466,'ur','sk','Urdština'),(3467,'ur','cy','Urdu'),(3468,'ur','da','Urdu'),(3469,'ur','el','Ουρντου'),(3470,'ur','eo','Urdu'),(3471,'ur','et','Urdu'),(3472,'ur','eu','Urdu'),(3473,'ur','fa','Urdu'),(3474,'ur','fi','urdu'),(3475,'ur','ga','Urdu'),(3476,'ur','he','אורדו'),(3477,'ur','hi','Urdu'),(3478,'ur','hr','Urdu'),(3479,'ur','hu','urdu'),(3480,'ur','hy','Urdu'),(3481,'ur','id','Urdu'),(3482,'ur','is','Urdu'),(3483,'ur','it','Urdu'),(3484,'ur','ja','ウルドゥー語'),(3485,'ur','ko','우르두어'),(3486,'ur','ku','Urdu'),(3487,'ur','lv','Urdu'),(3488,'ur','lt','Urdu'),(3489,'ur','mk','Urdu'),(3490,'ur','mt','Urdu'),(3491,'ur','mn','Urdu'),(3492,'ur','ne','Urdu'),(3493,'ur','nl','Urdu'),(3494,'ur','no','Urdu'),(3495,'ur','pa','Urdu'),(3496,'ur','pl','urdu'),(3497,'ur','pt-pt','Urdu'),(3498,'ur','pt-br','Urdu'),(3499,'ur','qu','Urdu'),(3500,'ur','ro','Urdu'),(3501,'ur','ru','Урду'),(3502,'ur','sl','Urdujščina'),(3503,'ur','so','Urdu'),(3504,'ur','sq','Urdu'),(3505,'ur','sr','урду'),(3506,'ur','sv','Urdu'),(3507,'ur','ta','Urdu'),(3508,'ur','th','อุรดู'),(3509,'ur','tr','Urduca'),(3510,'ur','uk','Urdu'),(3511,'ur','ur','اردو '),(3512,'ur','uz','Urdu'),(3513,'ur','vi','Urdu'),(3514,'ur','yi','Urdu'),(3515,'ur','zh-hans','乌尔都语'),(3516,'ur','zu','Urdu'),(3517,'ur','zh-hant','烏爾都語'),(3518,'ur','ms','Urdu'),(3519,'ur','gl','Urdu'),(3520,'ur','bn','Urdu'),(3521,'uz','en','Uzbek'),(3522,'uz','es','Uzbeko'),(3523,'uz','de','Usbekisch'),(3524,'uz','fr','Ouzbek'),(3525,'uz','ar','الاوزباكية'),(3526,'uz','bs','Uzbek'),(3527,'uz','bg','Узбекски'),(3528,'uz','ca','Uzbek'),(3529,'uz','cs','Uzbek'),(3530,'uz','sk','Uzbekčina'),(3531,'uz','cy','Uzbek'),(3532,'uz','da','Uzbek'),(3533,'uz','el','Ουζμπεκικα'),(3534,'uz','eo','Uzbek'),(3535,'uz','et','Uzbek'),(3536,'uz','eu','Uzbek'),(3537,'uz','fa','Uzbek'),(3538,'uz','fi','uzbekki'),(3539,'uz','ga','Uzbek'),(3540,'uz','he','אוזבקית'),(3541,'uz','hi','Uzbek'),(3542,'uz','hr','Uzbečki'),(3543,'uz','hu','üzbég'),(3544,'uz','hy','Uzbek'),(3545,'uz','id','Uzbek'),(3546,'uz','is','Uzbek'),(3547,'uz','it','Uzbeco'),(3548,'uz','ja','ウズベク語'),(3549,'uz','ko','우즈베크어'),(3550,'uz','ku','Uzbek'),(3551,'uz','lv','Uzbek'),(3552,'uz','lt','Uzbek'),(3553,'uz','mk','Uzbek'),(3554,'uz','mt','Uzbek'),(3555,'uz','mn','Uzbek'),(3556,'uz','ne','Uzbek'),(3557,'uz','nl','Oezbeeks'),(3558,'uz','no','Usbekisk'),(3559,'uz','pa','Uzbek'),(3560,'uz','pl','uzbecki'),(3561,'uz','pt-pt','Uzbeque'),(3562,'uz','pt-br','Uzbeque'),(3563,'uz','qu','Uzbek'),(3564,'uz','ro','Uzbecă'),(3565,'uz','ru','Узбекский'),(3566,'uz','sl','Uzbek'),(3567,'uz','so','Uzbek'),(3568,'uz','sq','Uzbek'),(3569,'uz','sr','Узбек'),(3570,'uz','sv','Uzbekiska'),(3571,'uz','ta','Uzbek'),(3572,'uz','th','อุซเบก'),(3573,'uz','tr','Özbekçe'),(3574,'uz','uk','Uzbek'),(3575,'uz','ur','Uzbek'),(3576,'uz','uz','Uzbek'),(3577,'uz','vi','Uzbek'),(3578,'uz','yi','Uzbek'),(3579,'uz','zh-hans','乌兹别克语'),(3580,'uz','zu','Uzbek'),(3581,'uz','zh-hant','烏茲別克語'),(3582,'uz','ms','Uzbek'),(3583,'uz','gl','Uzbek'),(3584,'uz','bn','Uzbek'),(3585,'vi','en','Vietnamese'),(3586,'vi','es','Vietnamita'),(3587,'vi','de','Vietnamesisch'),(3588,'vi','fr','Vietnamien'),(3589,'vi','ar','الفيتنامية'),(3590,'vi','bs','Vietnamese'),(3591,'vi','bg','Виетнамски'),(3592,'vi','ca','Vietnamese'),(3593,'vi','cs','Vietnamský'),(3594,'vi','sk','Vietnamčina'),(3595,'vi','cy','Vietnamese'),(3596,'vi','da','Vietnamese'),(3597,'vi','el','Βιετναμεζικα'),(3598,'vi','eo','Vietnamese'),(3599,'vi','et','Vietnamese'),(3600,'vi','eu','Vietnamese'),(3601,'vi','fa','Vietnamese'),(3602,'vi','fi','vietnam'),(3603,'vi','ga','Vietnamese'),(3604,'vi','he','וייטנאמית'),(3605,'vi','hi','Vietnamese'),(3606,'vi','hr','Vijetnamski'),(3607,'vi','hu','vietnámi'),(3608,'vi','hy','Vietnamese'),(3609,'vi','id','Vietnamese'),(3610,'vi','is','Vietnamese'),(3611,'vi','it','Vietnamita'),(3612,'vi','ja','ベトナム語'),(3613,'vi','ko','베트남어'),(3614,'vi','ku','Vietnamese'),(3615,'vi','lv','Vietnamese'),(3616,'vi','lt','Vietnamese'),(3617,'vi','mk','Vietnamese'),(3618,'vi','mt','Vietnamese'),(3619,'vi','mn','Vietnamese'),(3620,'vi','ne','Vietnamese'),(3621,'vi','nl','Vietnamees'),(3622,'vi','no','Vietnamesisk'),(3623,'vi','pa','Vietnamese'),(3624,'vi','pl','wietnamski'),(3625,'vi','pt-pt','Vietnamita'),(3626,'vi','pt-br','Vietnamita'),(3627,'vi','qu','Vietnamese'),(3628,'vi','ro','Vietnameză'),(3629,'vi','ru','Вьетнамский'),(3630,'vi','sl','Vietnamščina'),(3631,'vi','so','Vietnamese'),(3632,'vi','sq','Vietnamese'),(3633,'vi','sr','вијетнамски'),(3634,'vi','sv','Vietnamesiska'),(3635,'vi','ta','Vietnamese'),(3636,'vi','th','เวียดนาม'),(3637,'vi','tr','Vietnamca'),(3638,'vi','uk','Vietnamese'),(3639,'vi','ur','Vietnamese'),(3640,'vi','uz','Vietnamese'),(3641,'vi','vi','Tiếng Việt'),(3642,'vi','yi','Vietnamese'),(3643,'vi','zh-hans','越南语'),(3644,'vi','zu','Vietnamese'),(3645,'vi','zh-hant','越南語'),(3646,'vi','ms','Vietnamese'),(3647,'vi','gl','Vietnamese'),(3648,'vi','bn','Vietnamese'),(3649,'yi','en','Yiddish'),(3650,'yi','es','Yidis'),(3651,'yi','de','Jiddisch'),(3652,'yi','fr','Yiddish'),(3653,'yi','ar','اليديشية'),(3654,'yi','bs','Yiddish'),(3655,'yi','bg','Идиш'),(3656,'yi','ca','Yiddish'),(3657,'yi','cs','Jidiš'),(3658,'yi','sk','Jidiš'),(3659,'yi','cy','Yiddish'),(3660,'yi','da','Yiddish'),(3661,'yi','el','Γιντις'),(3662,'yi','eo','Yiddish'),(3663,'yi','et','Yiddish'),(3664,'yi','eu','Yiddish'),(3665,'yi','fa','Yiddish'),(3666,'yi','fi','jiddi'),(3667,'yi','ga','Yiddish'),(3668,'yi','he','יידיש'),(3669,'yi','hi','Yiddish'),(3670,'yi','hr','Jidiš'),(3671,'yi','hu','jiddis'),(3672,'yi','hy','Yiddish'),(3673,'yi','id','Yiddish'),(3674,'yi','is','Yiddish'),(3675,'yi','it','Yiddish'),(3676,'yi','ja','イディッシュ語'),(3677,'yi','ko','이디시어'),(3678,'yi','ku','Yiddish'),(3679,'yi','lv','Yiddish'),(3680,'yi','lt','Yiddish'),(3681,'yi','mk','Yiddish'),(3682,'yi','mt','Yiddish'),(3683,'yi','mn','Yiddish'),(3684,'yi','ne','Yiddish'),(3685,'yi','nl','Jiddisch'),(3686,'yi','no','Yiddish'),(3687,'yi','pa','Yiddish'),(3688,'yi','pl','jidysz'),(3689,'yi','pt-pt','Yiddish'),(3690,'yi','pt-br','Yiddish'),(3691,'yi','qu','Yiddish'),(3692,'yi','ro','Idiş'),(3693,'yi','ru','Идиш'),(3694,'yi','sl','Jidiš'),(3695,'yi','so','Yiddish'),(3696,'yi','sq','Yiddish'),(3697,'yi','sr','јидиш'),(3698,'yi','sv','Jiddisch'),(3699,'yi','ta','Yiddish'),(3700,'yi','th','ยิชดิช'),(3701,'yi','tr','Eski İbranice'),(3702,'yi','uk','Yiddish'),(3703,'yi','ur','Yiddish'),(3704,'yi','uz','Yiddish'),(3705,'yi','vi','Yiddish'),(3706,'yi','yi','Yiddish'),(3707,'yi','zh-hans','依地语'),(3708,'yi','zu','Yiddish'),(3709,'yi','zh-hant','依地語'),(3710,'yi','ms','Yiddish'),(3711,'yi','gl','Yiddish'),(3712,'yi','bn','Yiddish'),(3713,'zh-hans','en','Chinese (Simplified)'),(3714,'zh-hans','es','Chino simplificado'),(3715,'zh-hans','de','Vereinfachtes Chinesisch'),(3716,'zh-hans','fr','Chinois simplifié'),(3717,'zh-hans','ar','الصينية المبسطة'),(3718,'zh-hans','bs','Chinese (Simplified)'),(3719,'zh-hans','bg','Китайски  (опростен)'),(3720,'zh-hans','ca','Chinese (Simplified)'),(3721,'zh-hans','cs','Čínština ( Zjednodušený )'),(3722,'zh-hans','sk','Zjednodušená Čínština'),(3723,'zh-hans','cy','Chinese (Simplified)'),(3724,'zh-hans','da','Chinese (Simplified)'),(3725,'zh-hans','el','Κινεζικα (Απλοποιημένα)'),(3726,'zh-hans','eo','Chinese (Simplified)'),(3727,'zh-hans','et','Chinese (Simplified)'),(3728,'zh-hans','eu','Chinese (Simplified)'),(3729,'zh-hans','fa','Chinese (Simplified)'),(3730,'zh-hans','fi','kiina'),(3731,'zh-hans','ga','Chinese (Simplified)'),(3732,'zh-hans','he','סינית'),(3733,'zh-hans','hi','Chinese (Simplified)'),(3734,'zh-hans','hr','Kineski (pojednostavljeni)'),(3735,'zh-hans','hu','egyszerűsített kínai'),(3736,'zh-hans','hy','Chinese (Simplified)'),(3737,'zh-hans','id','Chinese (Simplified)'),(3738,'zh-hans','is','Chinese (Simplified)'),(3739,'zh-hans','it','Cinese semplificato'),(3740,'zh-hans','ja','簡体中国語'),(3741,'zh-hans','ko','중국어 간체'),(3742,'zh-hans','ku','Chinese (Simplified)'),(3743,'zh-hans','lv','Chinese (Simplified)'),(3744,'zh-hans','lt','Chinese (Simplified)'),(3745,'zh-hans','mk','Chinese (Simplified)'),(3746,'zh-hans','mt','Chinese (Simplified)'),(3747,'zh-hans','mn','Chinese (Simplified)'),(3748,'zh-hans','ne','Chinese (Simplified)'),(3749,'zh-hans','nl','Vereenvoudigd Chinees'),(3750,'zh-hans','no','Kinesisk (forenklet)'),(3751,'zh-hans','pa','Chinese (Simplified)'),(3752,'zh-hans','pl','chiński uproszczony'),(3753,'zh-hans','pt-pt','Chinês (Simplificado)'),(3754,'zh-hans','pt-br','Chinês (Simplificado)'),(3755,'zh-hans','qu','Chinese (Simplified)'),(3756,'zh-hans','ro','Chineza simplificată'),(3757,'zh-hans','ru','Китайский (упрощенный)'),(3758,'zh-hans','sl','Kitajščina (poenostavljena )'),(3759,'zh-hans','so','Chinese (Simplified)'),(3760,'zh-hans','sq','Chinese (Simplified)'),(3761,'zh-hans','sr','Кинески (поједностављени)'),(3762,'zh-hans','sv','Förenklad kinesiska'),(3763,'zh-hans','ta','Chinese (Simplified)'),(3764,'zh-hans','th','จีนประยุกต์'),(3765,'zh-hans','tr','Modern Çince'),(3766,'zh-hans','uk','Chinese (Simplified)'),(3767,'zh-hans','ur','Chinese (Simplified)'),(3768,'zh-hans','uz','Chinese (Simplified)'),(3769,'zh-hans','vi','Chinese (Simplified)'),(3770,'zh-hans','yi','Chinese (Simplified)'),(3771,'zh-hans','zh-hans','简体中文'),(3772,'zh-hans','zu','Chinese (Simplified)'),(3773,'zh-hans','zh-hant','簡體中文'),(3774,'zh-hans','ms','Chinese (Simplified)'),(3775,'zh-hans','gl','Chinese (Simplified)'),(3776,'zh-hans','bn','Chinese (Simplified)'),(3777,'zu','en','Zulu'),(3778,'zu','es','Zulú'),(3779,'zu','de','Zulu'),(3780,'zu','fr','Zoulou'),(3781,'zu','ar','الزولو'),(3782,'zu','bs','Zulu'),(3783,'zu','bg','Зулу'),(3784,'zu','ca','Zulu'),(3785,'zu','cs','Zulu'),(3786,'zu','sk','Jazyk Zulu'),(3787,'zu','cy','Zulu'),(3788,'zu','da','Zulu'),(3789,'zu','el','Ζουλου'),(3790,'zu','eo','Zulu'),(3791,'zu','et','Zulu'),(3792,'zu','eu','Zulu'),(3793,'zu','fa','Zulu'),(3794,'zu','fi','zulu'),(3795,'zu','ga','Zulu'),(3796,'zu','he','זולו '),(3797,'zu','hi','Zulu'),(3798,'zu','hr','Zulu'),(3799,'zu','hu','zulu'),(3800,'zu','hy','Zulu'),(3801,'zu','id','Zulu'),(3802,'zu','is','Zulu'),(3803,'zu','it','Zulu'),(3804,'zu','ja','ズールー語'),(3805,'zu','ko','줄루어'),(3806,'zu','ku','Zulu'),(3807,'zu','lv','Zulu'),(3808,'zu','lt','Zulu'),(3809,'zu','mk','Zulu'),(3810,'zu','mt','Zulu'),(3811,'zu','mn','Zulu'),(3812,'zu','ne','Zulu'),(3813,'zu','nl','Zulu'),(3814,'zu','no','Zulu'),(3815,'zu','pa','Zulu'),(3816,'zu','pl','zuluski'),(3817,'zu','pt-pt','Zulu'),(3818,'zu','pt-br','Zulu'),(3819,'zu','qu','Zulu'),(3820,'zu','ro','Zulu'),(3821,'zu','ru','Зулу'),(3822,'zu','sl','Zulu'),(3823,'zu','so','Zulu'),(3824,'zu','sq','Zulu'),(3825,'zu','sr','зулу'),(3826,'zu','sv','Zulu'),(3827,'zu','ta','Zulu'),(3828,'zu','th','ซูลู'),(3829,'zu','tr','Zulu dili'),(3830,'zu','uk','Zulu'),(3831,'zu','ur','Zulu'),(3832,'zu','uz','Zulu'),(3833,'zu','vi','Zulu'),(3834,'zu','yi','Zulu'),(3835,'zu','zh-hans','祖鲁语'),(3836,'zu','zu','Zulu'),(3837,'zu','zh-hant','祖魯語'),(3838,'zu','ms','Zulu'),(3839,'zu','gl','Zulu'),(3840,'zu','bn','Zulu'),(3841,'zh-hant','en','Chinese (Traditional)'),(3842,'zh-hant','es','Chino tradicional'),(3843,'zh-hant','de','Traditionelles Chinesisch'),(3844,'zh-hant','fr','Chinois traditionnel'),(3845,'zh-hant','ar','الصينية التقليدية'),(3846,'zh-hant','bs','Chinese (Traditional)'),(3847,'zh-hant','bg','Китайски (традиционен)'),(3848,'zh-hant','ca','Chinese (Traditional)'),(3849,'zh-hant','cs','Čínština (tradiční )'),(3850,'zh-hant','sk','Tradičná Čínština'),(3851,'zh-hant','cy','Chinese (Traditional)'),(3852,'zh-hant','da','Chinese (Traditional)'),(3853,'zh-hant','el','Κινεζικα (Παραδοσιακά)'),(3854,'zh-hant','eo','Chinese (Traditional)'),(3855,'zh-hant','et','Chinese (Traditional)'),(3856,'zh-hant','eu','Chinese (Traditional)'),(3857,'zh-hant','fa','Chinese (Traditional)'),(3858,'zh-hant','fi','perinteinen kiina'),(3859,'zh-hant','ga','Chinese (Traditional)'),(3860,'zh-hant','he','סינית מסורתית'),(3861,'zh-hant','hi','Chinese (Traditional)'),(3862,'zh-hant','hr','Kineski (tradicionalni)'),(3863,'zh-hant','hu','hagyományos kínai'),(3864,'zh-hant','hy','Chinese (Traditional)'),(3865,'zh-hant','id','Chinese (Traditional)'),(3866,'zh-hant','is','Chinese (Traditional)'),(3867,'zh-hant','it','Cinese tradizionale'),(3868,'zh-hant','ja','繁体中国語'),(3869,'zh-hant','ko','중국어 번체'),(3870,'zh-hant','ku','Chinese (Traditional)'),(3871,'zh-hant','lv','Chinese (Traditional)'),(3872,'zh-hant','lt','Chinese (Traditional)'),(3873,'zh-hant','mk','Chinese (Traditional)'),(3874,'zh-hant','mt','Chinese (Traditional)'),(3875,'zh-hant','mn','Chinese (Traditional)'),(3876,'zh-hant','ne','Chinese (Traditional)'),(3877,'zh-hant','nl','Traditioneel Chinees'),(3878,'zh-hant','no','Kinesisk (tradisjonell)'),(3879,'zh-hant','pa','Chinese (Traditional)'),(3880,'zh-hant','pl','chiński tradycyjny'),(3881,'zh-hant','pt-pt','Chinês (Tradicional)'),(3882,'zh-hant','pt-br','Chinês (Tradicional)'),(3883,'zh-hant','qu','Chinese (Traditional)'),(3884,'zh-hant','ro','Chineza tradiţională'),(3885,'zh-hant','ru','Китайский (традиционный)'),(3886,'zh-hant','sl','Kitajščina (tradicionalna)'),(3887,'zh-hant','so','Chinese (Traditional)'),(3888,'zh-hant','sq','Chinese (Traditional)'),(3889,'zh-hant','sr','Кинески (традиционални)'),(3890,'zh-hant','sv','Traditionell kinesiska'),(3891,'zh-hant','ta','Chinese (Traditional)'),(3892,'zh-hant','th','จีนดั้งเดิม'),(3893,'zh-hant','tr','Klasik Çince'),(3894,'zh-hant','uk','Chinese (Traditional)'),(3895,'zh-hant','ur','Chinese (Traditional)'),(3896,'zh-hant','uz','Chinese (Traditional)'),(3897,'zh-hant','vi','Chinese (Traditional)'),(3898,'zh-hant','yi','Chinese (Traditional)'),(3899,'zh-hant','zh-hans','繁体中文'),(3900,'zh-hant','zu','Chinese (Traditional)'),(3901,'zh-hant','zh-hant','繁體中文'),(3902,'zh-hant','ms','Chinese (Traditional)'),(3903,'zh-hant','gl','Chinese (Traditional)'),(3904,'zh-hant','bn','Chinese (Traditional)'),(3905,'ms','en','Malay'),(3906,'ms','es','Malayo'),(3907,'ms','de','Malaiisch'),(3908,'ms','fr','Malay'),(3909,'ms','ar','لغة الملايو'),(3910,'ms','bs','Malay'),(3911,'ms','bg','Малайски'),(3912,'ms','ca','Malay'),(3913,'ms','cs','Malajský'),(3914,'ms','sk','Malay'),(3915,'ms','cy','Malay'),(3916,'ms','da','Malay'),(3917,'ms','el','Malay'),(3918,'ms','eo','Malay'),(3919,'ms','et','Malay'),(3920,'ms','eu','Malay'),(3921,'ms','fa','Malay'),(3922,'ms','fi','Malay'),(3923,'ms','ga','Malay'),(3924,'ms','he','מלאית'),(3925,'ms','hi','Malay'),(3926,'ms','hr','Malajski'),(3927,'ms','hu','Malay'),(3928,'ms','hy','Malay'),(3929,'ms','id','Malay'),(3930,'ms','is','Malay'),(3931,'ms','it','Malay'),(3932,'ms','ja','Malay'),(3933,'ms','ko','Malay'),(3934,'ms','ku','Malay'),(3935,'ms','lv','Malay'),(3936,'ms','lt','Malay'),(3937,'ms','mk','Malay'),(3938,'ms','mt','Malay'),(3939,'ms','mn','Malay'),(3940,'ms','ne','Malay'),(3941,'ms','nl','Malay'),(3942,'ms','no','Malay'),(3943,'ms','pa','Malay'),(3944,'ms','pl','Malay'),(3945,'ms','pt-pt','Malaio'),(3946,'ms','pt-br','Malaio'),(3947,'ms','qu','Malay'),(3948,'ms','ro','Malay'),(3949,'ms','ru','Малайский'),(3950,'ms','sl','Malajščina'),(3951,'ms','so','Malay'),(3952,'ms','sq','Malay'),(3953,'ms','sr','малајски'),(3954,'ms','sv','Malay'),(3955,'ms','ta','Malay'),(3956,'ms','th','Malay'),(3957,'ms','tr','Malay'),(3958,'ms','uk','Malay'),(3959,'ms','ur','Malay'),(3960,'ms','uz','Malay'),(3961,'ms','vi','Malay'),(3962,'ms','yi','Malay'),(3963,'ms','zh-hans','Malay'),(3964,'ms','zu','Malay'),(3965,'ms','zh-hant','Malay'),(3966,'ms','ms','Melayu'),(3967,'ms','gl','Malay'),(3968,'ms','bn','Malay'),(3969,'gl','en','Galician'),(3970,'gl','es','Gallego'),(3971,'gl','de','Galicisch'),(3972,'gl','fr','Galicien'),(3973,'gl','ar','Galician'),(3974,'gl','bs','Galician'),(3975,'gl','bg','Galician'),(3976,'gl','ca','Galician'),(3977,'gl','cs','Galician'),(3978,'gl','sk','Galician'),(3979,'gl','cy','Galician'),(3980,'gl','da','Galician'),(3981,'gl','el','Galician'),(3982,'gl','eo','Galician'),(3983,'gl','et','Galician'),(3984,'gl','eu','Galician'),(3985,'gl','fa','Galician'),(3986,'gl','fi','Galician'),(3987,'gl','ga','Galician'),(3988,'gl','he','Galician'),(3989,'gl','hi','Galician'),(3990,'gl','hr','Galician'),(3991,'gl','hu','Galician'),(3992,'gl','hy','Galician'),(3993,'gl','id','Galician'),(3994,'gl','is','Galician'),(3995,'gl','it','Gallego'),(3996,'gl','ja','Galician'),(3997,'gl','ko','Galician'),(3998,'gl','ku','Galician'),(3999,'gl','lv','Galician'),(4000,'gl','lt','Galician'),(4001,'gl','mk','Galician'),(4002,'gl','mt','Galician'),(4003,'gl','mn','Galician'),(4004,'gl','ne','Galician'),(4005,'gl','nl','Galician'),(4006,'gl','no','Galician'),(4007,'gl','pa','Galician'),(4008,'gl','pl','Galician'),(4009,'gl','pt-pt','Galego'),(4010,'gl','pt-br','Galego'),(4011,'gl','qu','Galician'),(4012,'gl','ro','Galician'),(4013,'gl','ru','Галисийский'),(4014,'gl','sl','Galician'),(4015,'gl','so','Galician'),(4016,'gl','sq','Galician'),(4017,'gl','sr','Galician'),(4018,'gl','sv','Galician'),(4019,'gl','ta','Galician'),(4020,'gl','th','Galician'),(4021,'gl','tr','Galician'),(4022,'gl','uk','Galician'),(4023,'gl','ur','Galician'),(4024,'gl','uz','Galician'),(4025,'gl','vi','Galician'),(4026,'gl','yi','Galician'),(4027,'gl','zh-hans','Galician'),(4028,'gl','zu','Galician'),(4029,'gl','zh-hant','Galician'),(4030,'gl','ms','Galician'),(4031,'gl','gl','Galego'),(4032,'gl','bn','Galician'),(4033,'bn','en','Bengali'),(4034,'bn','es','Bengalí'),(4035,'bn','de','Bengalisch'),(4036,'bn','fr','Bengali'),(4037,'bn','ar','Bengali'),(4038,'bn','bs','Bengali'),(4039,'bn','bg','Bengali'),(4040,'bn','ca','Bengali'),(4041,'bn','cs','Bengali'),(4042,'bn','sk','Bengali'),(4043,'bn','cy','Bengali'),(4044,'bn','da','Bengali'),(4045,'bn','el','Bengali'),(4046,'bn','eo','Bengali'),(4047,'bn','et','Bengali'),(4048,'bn','eu','Bengali'),(4049,'bn','fa','Bengali'),(4050,'bn','fi','Bengali'),(4051,'bn','ga','Bengali'),(4052,'bn','he','Bengali'),(4053,'bn','hi','Bengali'),(4054,'bn','hr','Bengali'),(4055,'bn','hu','Bengali'),(4056,'bn','hy','Bengali'),(4057,'bn','id','Bengali'),(4058,'bn','is','Bengali'),(4059,'bn','it','Bengalese'),(4060,'bn','ja','Bengali'),(4061,'bn','ko','Bengali'),(4062,'bn','ku','Bengali'),(4063,'bn','lv','Bengali'),(4064,'bn','lt','Bengali'),(4065,'bn','mk','Bengali'),(4066,'bn','mt','Bengali'),(4067,'bn','mn','Bengali'),(4068,'bn','ne','Bengali'),(4069,'bn','nl','Bengali'),(4070,'bn','no','Bengali'),(4071,'bn','pa','Bengali'),(4072,'bn','pl','Bengali'),(4073,'bn','pt-pt','Bengalês'),(4074,'bn','pt-br','Bengalês'),(4075,'bn','qu','Bengali'),(4076,'bn','ro','Bengali'),(4077,'bn','ru','Бенгальский'),(4078,'bn','sl','Bengali'),(4079,'bn','so','Bengali'),(4080,'bn','sq','Bengali'),(4081,'bn','sr','Bengali'),(4082,'bn','sv','Bengali'),(4083,'bn','ta','Bengali'),(4084,'bn','th','Bengali'),(4085,'bn','tr','Bengali'),(4086,'bn','uk','Bengali'),(4087,'bn','ur','Bengali'),(4088,'bn','uz','Bengali'),(4089,'bn','vi','Bengali'),(4090,'bn','yi','Bengali'),(4091,'bn','zh-hans','Bengali'),(4092,'bn','zu','Bengali'),(4093,'bn','zh-hant','Bengali'),(4094,'bn','ms','Bengali'),(4095,'bn','gl','Bengali'),(4096,'bn','bn','हिन्दी');

--
-- Table structure for table `wp_icl_locale_map`
--

CREATE TABLE `wp_icl_locale_map` (
  `code` varchar(7) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `locale` varchar(35) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  UNIQUE KEY `code` (`code`,`locale`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_locale_map`
--


--
-- Table structure for table `wp_icl_message_status`
--

CREATE TABLE `wp_icl_message_status` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `rid` bigint(20) unsigned NOT NULL,
  `object_id` bigint(20) unsigned NOT NULL,
  `from_language` varchar(10) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `to_language` varchar(10) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `md5` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `object_type` varchar(64) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `status` smallint(6) NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `rid` (`rid`),
  KEY `object_id` (`object_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_message_status`
--


--
-- Table structure for table `wp_icl_node`
--

CREATE TABLE `wp_icl_node` (
  `nid` bigint(20) NOT NULL,
  `md5` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `links_fixed` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`nid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_node`
--


--
-- Table structure for table `wp_icl_reminders`
--

CREATE TABLE `wp_icl_reminders` (
  `id` bigint(20) NOT NULL,
  `message` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `url` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `can_delete` tinyint(4) NOT NULL,
  `show` tinyint(4) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_reminders`
--


--
-- Table structure for table `wp_icl_string_positions`
--

CREATE TABLE `wp_icl_string_positions` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `string_id` bigint(20) NOT NULL,
  `kind` tinyint(4) DEFAULT NULL,
  `position_in_page` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  PRIMARY KEY (`id`),
  KEY `string_id` (`string_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_string_positions`
--


--
-- Table structure for table `wp_icl_string_status`
--

CREATE TABLE `wp_icl_string_status` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `rid` bigint(20) NOT NULL,
  `string_translation_id` bigint(20) NOT NULL,
  `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `md5` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  PRIMARY KEY (`id`),
  KEY `string_translation_id` (`string_translation_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_string_status`
--


--
-- Table structure for table `wp_icl_string_translations`
--

CREATE TABLE `wp_icl_string_translations` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `string_id` bigint(20) unsigned NOT NULL,
  `language` varchar(10) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `status` tinyint(4) NOT NULL,
  `value` longtext COLLATE utf8mb4_unicode_520_ci,
  `mo_string` longtext COLLATE utf8mb4_unicode_520_ci,
  `translator_id` bigint(20) unsigned DEFAULT NULL,
  `translation_service` varchar(16) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `batch_id` int(11) NOT NULL DEFAULT '0',
  `translation_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  UNIQUE KEY `string_language` (`string_id`,`language`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_string_translations`
--


--
-- Table structure for table `wp_icl_strings`
--

CREATE TABLE `wp_icl_strings` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `language` varchar(7) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `context` varchar(160) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `name` varchar(160) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `value` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `string_package_id` bigint(20) unsigned DEFAULT NULL,
  `location` bigint(20) unsigned DEFAULT NULL,
  `wrap_tag` varchar(16) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `type` varchar(40) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'LINE',
  `title` varchar(160) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  `status` tinyint(4) NOT NULL,
  `gettext_context` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `domain_name_context_md5` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `translation_priority` varchar(160) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `word_count` int(10) unsigned DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `uc_domain_name_context_md5` (`domain_name_context_md5`),
  KEY `language_context` (`language`,`context`),
  KEY `icl_strings_name` (`name`),
  KEY `icl_strings_translation_priority` (`translation_priority`),
  KEY `context` (`context`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_strings`
--


--
-- Table structure for table `wp_icl_translate`
--

CREATE TABLE `wp_icl_translate` (
  `tid` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `job_id` bigint(20) unsigned NOT NULL,
  `content_id` bigint(20) unsigned NOT NULL,
  `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `field_type` varchar(160) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `field_wrap_tag` varchar(16) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `field_format` varchar(16) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `field_translate` tinyint(4) NOT NULL,
  `field_data` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `field_data_translated` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `field_finished` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`tid`),
  KEY `job_id` (`job_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_translate`
--


--
-- Table structure for table `wp_icl_translate_job`
--

CREATE TABLE `wp_icl_translate_job` (
  `job_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `rid` bigint(20) unsigned NOT NULL,
  `translator_id` int(10) unsigned NOT NULL,
  `translated` tinyint(3) unsigned NOT NULL DEFAULT '0',
  `manager_id` int(10) unsigned NOT NULL,
  `revision` int(10) unsigned DEFAULT NULL,
  `title` varchar(160) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  `deadline_date` datetime DEFAULT NULL,
  `completed_date` datetime DEFAULT NULL,
  `editor` varchar(16) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  `editor_job_id` bigint(20) unsigned DEFAULT NULL,
  `edit_timestamp` int(11) unsigned DEFAULT NULL,
  PRIMARY KEY (`job_id`),
  KEY `rid` (`rid`,`translator_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_translate_job`
--


--
-- Table structure for table `wp_icl_translation_batches`
--

CREATE TABLE `wp_icl_translation_batches` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `batch_name` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `tp_id` int(11) DEFAULT NULL,
  `ts_url` text COLLATE utf8mb4_unicode_520_ci,
  `last_update` datetime DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_translation_batches`
--


--
-- Table structure for table `wp_icl_translation_status`
--

CREATE TABLE `wp_icl_translation_status` (
  `rid` bigint(20) NOT NULL AUTO_INCREMENT,
  `translation_id` bigint(20) NOT NULL,
  `status` tinyint(4) NOT NULL,
  `translator_id` bigint(20) NOT NULL,
  `needs_update` tinyint(4) NOT NULL,
  `md5` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `translation_service` varchar(16) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `batch_id` int(11) NOT NULL DEFAULT '0',
  `translation_package` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `links_fixed` tinyint(4) NOT NULL DEFAULT '0',
  `_prevstate` longtext COLLATE utf8mb4_unicode_520_ci,
  `uuid` varchar(36) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  `tp_id` int(11) DEFAULT NULL,
  `tp_revision` int(11) NOT NULL DEFAULT '1',
  `ts_status` text COLLATE utf8mb4_unicode_520_ci,
  PRIMARY KEY (`rid`),
  UNIQUE KEY `translation_id` (`translation_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_translation_status`
--


--
-- Table structure for table `wp_icl_translations`
--

CREATE TABLE `wp_icl_translations` (
  `translation_id` bigint(20) NOT NULL AUTO_INCREMENT,
  `element_type` varchar(36) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post_post',
  `element_id` bigint(20) DEFAULT NULL,
  `trid` bigint(20) NOT NULL,
  `language_code` varchar(7) COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `source_language_code` varchar(7) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
  PRIMARY KEY (`translation_id`),
  UNIQUE KEY `trid_lang` (`trid`,`language_code`),
  UNIQUE KEY `el_type_id` (`element_type`,`element_id`),
  KEY `trid` (`trid`),
  KEY `id_type_language` (`element_id`,`element_type`,`language_code`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_icl_translations`
--


--
-- 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=21564 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

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


INSERT INTO `wp_options` VALUES (21459,'_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:73:\"Do The Woo Community: Future Investments from WooCommerce: What to Expect\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://dothewoo.io/?post_type=blog&p=86201\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://dothewoo.io/blog/future-investments-from-woocommerce-what-to-expect/\";s: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:366:\"As WooCommerce continues to grow as a leading platform for online commerce, here are several key areas that Beau Lebens mentioned in a recent podcast episode about where the company is focusing its future investments. These developments are aimed at enhancing both the merchant experience and the overall ecosystem for developers and businesses alike. Here [&#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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Oct 2024 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s: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:94:\"WPTavern: WP Fusion Lite Plugin Removed From WordPress.com Following a Cease and Desist Letter\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=175800\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"https://wptavern.com/wp-fusion-lite-plugin-removed-from-wordpress-com-following-a-cease-and-desist-letter\";s: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:4846:\"<p>Automattic has agreed to <a href=\"https://wpfusion.com/business/regarding-our-cease-and-desist-letter-to-automattic/\">remove the WP Fusion Lite Plugin</a> from WordPress.com following a Cease and Desist letter filed by the plugin&#8217;s creator Jack Arturo on October 12, 2024. The letter accused Automattic and WordPress.com of unauthorized trademark usage by displaying the plugin on WordPress.com.</p>\n\n\n\n<p><a href=\"https://wordpress.org/plugins/wp-fusion-lite/\">WP Fusion Lite</a> is a WordPress plugin that connects WordPress websites to popular CRM systems and marketing automation tools. It has over 5,000 Active Installs in the WordPress.org Repository.&nbsp;</p>\n\n\n\n<p>Jack Arturo, founder of Very Good Plugins LLC and creator of WP Fusion plugin, <a href=\"https://x.com/verygoodplugins/status/1845246925886353795\">filed the Cease and Desist letter</a> stating: “As the owner of the federally registered trademark WP FUSION (U.S. Registration No. 6,052,437), which was registered on May 12, 2020, and is associated with software services including website integration with customer relationship management (CRM) and marketing automation systems, I believe that your continued use and distribution of the plugin under the WP Fusion name is a clear infringement of my exclusive trademark rights under U.S. law.</p>\n\n\n\n<p>The plugin you are hosting creates a likelihood of confusion, mistake, or deception regarding the source, sponsorship, or affiliation of the WP Fusion brand, which could damage the reputation and goodwill associated with my brand. Please be advised that I will vigorously defend my trademark rights to the fullest extent of the law.”</p>\n\n\n\n<p>The letter included three key demands:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Immediately remove the &#8220;WP Fusion Lite&#8221; plugin from WordPress.com.</li>\n\n\n\n<li>Cease any use of trademarks, logos, or names confusingly similar to WP Fusion.</li>\n\n\n\n<li>Provide written confirmation within ten business days that these actions have been taken.</li>\n</ul>\n\n\n\n<p>He also warned that if the above requests are not met, he would “pursue all available legal remedies, including but not limited to seeking injunctive relief, damages, and attorney&#8217;s fees for trademark infringement.”&nbsp;</p>\n\n\n\n<h3 class=\"wp-block-heading\">Automattic&#8217;s Response on October 18, 2024 </h3>\n\n\n\n<p>Automattic responded, saying they “would like to resolve this matter swiftly and amicably, and to that end WP Fusion Lite is no longer listed on WordPress.com and we have disabled its landing page. It is no longer available to WordPress.com customers nor will it appear in search results. We trust this resolves your concerns.”</p>\n\n\n\n<p>However, Automattic disagreed with the trademark infringement claim, stating: “Automattic disagrees with your assertions that it has infringed the intellectual property rights of Very Good Plugins, LLC. The listing uses the WPFUSION trademark solely and only to the extent necessary to identify the genuine WPFUSION plugin, which constitutes nominative fair use under applicable law.”</p>\n\n\n\n<p>Since last year, WordPress.com has displayed all WP.org plugins in a private directory for its hosting customers, a practice that has raised <a href=\"https://wptavern.com/developers-raise-concerns-about-wordpress-com-plugin-listings-outranking-wordpress-org-on-google\">concerns among developers</a>. They worry that WordPress.com plugin listings are outranking WordPress.org on Google, causing confusion for users. Many users, unaware of the distinction between WP.com and WP.org, click the WP.com link, which prompts them to create an account and sign up for premium hosting. Jack mentioned that this confusion was affecting his customers, who had already purchased the pro version of the plugin.</p>\n\n\n\n<p>Automattic has maintained that featuring plugins on WP.com benefits authors by increasing exposure. They responded to Jack’s complaints on <a href=\"https://x.com/automattic/status/1845252369174364554\">X</a>, asking, “So, to clarify, you&#8217;d like us to hide your plugin from the ~248M registered users on @wordpressdotcom?” Matt had also <a href=\"https://x.com/photomatt/status/1701973661110915205\">tweeted</a> last year, “It&#8217;s providing distribution to the plugin authors, literally millions and millions of installs.”</p>\n\n\n\n<p>Jack <a href=\"https://x.com/verygoodplugins/status/1845266438539382989\">clarified</a> that he has no objection to others mirroring his plugins, except for Automattic. Also, WP Fusion Pro does not require the free version to function, and they have been delivering updates to pro customers via their own servers for many years.</p>\n\n\n\n<p>The issue has been resolved, but it remains to be seen whether more plugin authors will choose to remove their plugins from WP.com.</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 Oct 2024 03:19: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:7:\"Jyolsna\";s: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:26:\"Matt: My Freedom of Speech\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=128329\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"https://ma.tt/2024/10/first-amendment/\";s: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:2208:\"<p><a href=\"https://wpengine.com/\">WP Engine</a> has <a href=\"https://www.theverge.com/2024/10/18/24273448/wp-engine-injunction-matt-mullenweg-wordpress-resources\">filed hundreds pages of legal documents seeking an injunction against me and Automattic</a>. They say this is about community or some nonsense, but if you look at the core, what they&#8217;re trying to do is ask a judge to curtail my First Amendment rights.</p>\n\n\n\n<p>The First Amendment is the basis of our democracy. It is <em>inconvenient</em> and <em>important</em>. It&#8217;s also short, so I&#8217;m going to quote the First Amendment in its entirety:</p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances.</p>\n</blockquote>\n\n\n\n<p>This means that, <a href=\"https://en.wikipedia.org/wiki/United_States_free_speech_exceptions\">with rare exceptions</a>, the government cannot tell you not to say something.</p>\n\n\n\n<h2 class=\"wp-block-heading\">Freedom of Speech is not Freedom of Reach</h2>\n\n\n\n<p>The First Amendment says I should be able to state facts and my opinions about WP Engine. However, the <a href=\"https://www.nytimes.com/\">New York Times</a> is not required or compelled to publish them in their newspaper and distribute them to their subscribers.</p>\n\n\n\n<p>WP Engine is free to publish whatever <a href=\"https://en.wikipedia.org/wiki/GNU_General_Public_License\">GPL code</a> they want to the world. <a href=\"https://wordpress.org/\">WordPress.org</a> should not be compelled to distribute it or provide it free hosting.</p>\n\n\n\n<h2 class=\"wp-block-heading\">Quiet For A While</h2>\n\n\n\n<p>After this post, I will refrain from personally commenting on the WP Engine case until a judge rules on the injunction. I will continue to exercise my First Amendment rights to promote others&#8217; speech. However, <strong>I hope others speak up on our battle with WP Engine, and I will boost their speech wherever I can</strong>.</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, 20 Oct 2024 21:53: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:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"Matt: Cloudflare Stories\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=128322\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://ma.tt/2024/10/cloudflare-stories/\";s: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:1102:\"<p>There are two great Cloudflare-related stories published this weekend.</p>\n\n\n\n<p><a href=\"https://www.wired.com/story/plaintext-you-can-now-see-the-code-that-ended-apartheid/\">The first is Steven Levy&#8217;s incredible story about Tim Jenkin</a>, who created a secure communication protocol for the African National Congress to overthrow the apartheid regime in South Africa. Cloudflare&#8217;s CTO, <a href=\"https://jgc.org/\">John Graham-Cumming</a>, later helped break past the cryptography system&#8217;s lost password, which he <a href=\"https://blog.jgc.org/2024/09/cracking-old-zip-file-to-help-open.html\">blogged about with some technical detail here</a>.</p>\n\n\n\n<p>Second, my dear friend Om Malik <a href=\"https://crazystupidtech.com/archive/future-of-internet-in-the-age-of-ai/\">published a great conversation with Cloudflare CEO Matthew Prince in his new newsletter Crazy Stupid Tech</a>. <a href=\"https://x.com/eastdakota\">Matthew</a> and Om are influential thinkers to listen to, and their discussion contains a lot of interesting nuance about networks, censorship, and sovereignty. </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, 20 Oct 2024 04:57:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"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: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:120:\"Gutenberg Times: Source of Truth WordPress 6.7, Mastering Theme.json, Dev Notes Galore and more — Weekend Edition #308\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=30448\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:124:\"https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/\";s: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:17131:\"<p>Hi there, </p>\n\n\n\n<p>WordPress 6.7 RC1 is scheduled for October 22, 2024. That&#8217;s also the occasion to publish the Fieldguide listing the big and small changes coming with the new version. Below I listed the Devnotes that are already available. <strong>Anne McCarthy</strong> published the 6,450-words <a href=\"https://gutenbergtimes.com/6-7-source-of-truth/\"><strong>Source of Truth</strong></a> on this site as well. </p>\n\n\n\n<p>It&#8217;s going to be a busy three weeks until the final release on November 12, 2024. </p>\n\n\n\n<p>Enjoy exploring the new features and update in WordPress and have a great weekend! </p>\n\n\n\n<p>Yours, 💕<br /><em>Birgit</em></p>\n\n\n\n<div class=\"wp-block-group has-light-background-background-color has-background\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n<p><strong>Table of Contents</strong></p>\n\n\n\n<ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/#0-word-press-release-information\">Developing Gutenberg and WordPress</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/#0-p\">Plugins, Themes, and Tools for #nocode site builders and owners</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/#2-word-press-6-0-1-and-6-1-scheduled\">Theme Development for Full Site Editing and Blocks</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/source-of-truth-wordpress-6-7-mastering-theme-json-dev-notes-galore-and-more-weekend-edition-308/#3-building-themes-for-fse-and-word-press\">Building Blocks and Tools for the Block editor</a></li></ol>\n</div></div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"0-word-press-release-information\">Developing Gutenberg and WordPress</h2>\n\n\n\n<p><a href=\"https://wordpress.org/news/2024/10/wordpress-6-7-beta-3/\">WordPress 6.7 Beta 3</a> has been released and the first <strong>Dev Notes</strong> are being published: </p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https://make.wordpress.org/core/2024/10/15/subscribe-to-changes-in-the-interactivity-api-state-and-context-on-client-side-navigation-in-6-7/\">Subscribe to changes in the Interactivity API state and context on client-side navigation in 6.7</a>  </li>\n\n\n\n<li><a href=\"https://make.wordpress.org/core/2024/10/14/updates-to-script-modules-in-6-7/\">Updates to Script Modules in 6.7</a> </li>\n\n\n\n<li><a href=\"https://make.wordpress.org/core/2024/10/17/roster-of-design-tools-per-block-wordpress-6-6-edition-2/\">Roster of design tools per block (WordPress 6.7 edition)</a></li>\n\n\n\n<li><a href=\"https://make.wordpress.org/core/2024/10/17/updates-to-the-html-api-in-6-7/\">Updates to the HTML API in 6.7</a></li>\n\n\n\n<li> <a href=\"https://make.wordpress.org/core/2024/10/17/new-block-type-registration-apis-to-improve-performance-in-wordpress-6-7/\">New block type registration APIs to improve performance in WordPress 6.7</a></li>\n\n\n\n<li><a href=\"https://make.wordpress.org/core/2024/10/18/auto-sizes-for-lazy-loaded-images-in-wordpress-6-7/\">Auto Sizes for Lazy Loaded Images in WordPress 6.7</a></li>\n\n\n\n<li><a href=\"https://make.wordpress.org/core/2024/10/18/post-editor-iframing-with-meta-boxes-in-wordpress-6-7/\">Post Editor iframing with meta boxes&nbsp;in WordPress 6.7</a></li>\n</ul>\n\n\n\n<img width=\"652\" height=\"374\" tabindex=\"0\" src=\"https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/376215782-1f8a8a02-f3fd-464d-a543-00f7a90dd1eb.png?resize=652%2C374&ssl=1\" alt=\"Highlights Grid WordPress 6.7\" class=\"wp-image-30498\" />\n\n\n\n<p><strong>Anne McCarthy</strong> found a <a href=\"https://nomad.blog/2024/10/18/new-location-for-the-6-7-source-of-truth/\">new location for the 6.7 Source of&nbsp;Truth</a> on the Gutenberg Times.  The <strong><a href=\"https://gutenbergtimes.com/6-7-source-of-truth/\">Source of Truth</a></strong> is a tool for others who educate WordPress users on the new updates. &#8220;It’s a foundational resource but, it’s so long and detailed, it needs to be repackaged to be useful in each space.&#8221; McCarthy wrote. </p>\n\n\n\n<a href=\"https://gutenbergtimes.com/6-7-source-of-truth/\"><img width=\"652\" height=\"365\" tabindex=\"0\" src=\"https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/6.7-Source-of-Truth-Featured-Image.png?resize=652%2C365&ssl=1\" alt=\"White text on blue background with a paintbrush mark saying WordPress 6.7 Source of Truth\" class=\"wp-image-30499\" /></a>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<div class=\"wp-block-group has-light-background-background-color has-background\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p>🎙️ Latest episode: <a href=\"https://gutenbergtimes.com/podcast/gutenberg-changelog-109-a-responsive-navigation-block/\">Gutenberg Changelog #109 – Gutenberg 19.4, Creating a Block Theme, Responsive Navigation Block Plugin</a> with special guest Anne Katzeff</p>\n\n\n\n<img width=\"652\" height=\"184\" tabindex=\"0\" src=\"https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/Screenshot-2024-10-12-at-15.51.00.png?resize=652%2C184&ssl=1\" alt=\"Gutenberg Changelog with Anne Katzeff and Birgit Pauli-Haack\" class=\"wp-image-30397\" />\n</div></div>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<p><strong>Joen Asmussen</strong> shared a list of work done by the WordPress design team: <a href=\"https://make.wordpress.org/design/2024/10/18/design-share-66-oct-7-oct18/\"><strong>Design Share #66 (Oct 7-Oct18)</strong></a>. He highlights: </p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Admin bar evolution</li>\n\n\n\n<li>Unseen icon update</li>\n\n\n\n<li>Navigation: Provide fallback when menu was deleted</li>\n\n\n\n<li>Admin themes</li>\n\n\n\n<li>Update component: Combobox</li>\n\n\n\n<li>Storybook: Color</li>\n\n\n\n<li>WordPress Photo Directory</li>\n\n\n\n<li>5FTF. Sponsorship</li>\n</ul>\n\n\n\n<a href=\"https://make.wordpress.org/design/2024/10/18/design-share-66-oct-7-oct18/\"><img width=\"652\" height=\"278\" tabindex=\"0\" src=\"https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/5FTF-Sponsorship.webp?resize=652%2C278&ssl=1\" alt=\"\" class=\"wp-image-30490\" /></a>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"0-p\">Plugins, Themes, and Tools for #nocode site builders and owners</h2>\n\n\n\n<p>In his video, <a href=\"https://www.youtube.com/watch?v=v5drhUktS_0\"><strong>WordPress, How to build Complex Layouts in the Block Editor </strong></a><strong>Elliot Richmond</strong> showed how easy it is now to build websites with WordPress, even if the layout seems a bit more challenging. I liked how you get to hear about the reasoning of design choices and also how Richmond decides on the tools to use. In the methods of the Speed building challenge, Richmond takes you along as he rebuilds the Blookup.com website.</p>\n\n\n\n<img width=\"652\" height=\"326\" tabindex=\"0\" src=\"https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/Screenshot-2024-10-16-at-15.56.32.png?resize=652%2C326&ssl=1\" alt=\"Screenshot of site building video\" class=\"wp-image-30483\" />\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<p><strong><a href=\"https://x.com/robinpietersen\">Robin Pietersen</a> </strong>announced a few more blocks for FooEvents. In his post <a href=\"https://www.fooevents.com/introducing-the-new-fooevents-calendar-and-attendee-listing-blocks/?s=09\"><strong>Introducing the New FooEvents Calendar and Attendee Listing Blocks</strong></a> you can take a look at the new FooEvents Calendar Block and FooEvents Attendee Listing Block, as well as updates to the FooEvents Express Check-ins plugin and FooEvents Ticket Importer.</p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<p><a href=\"https://x.com/ronaldhuereca\"><strong>Ronald Huereca</strong></a> t<a href=\"https://x.com/MediaRonLLC/status/1847527385823900064\">weeted he</a> &#8220;quietly released Photo Block earlier this week.&#8221;  An official announcement post is forthcoming. If you want to check out the new Photo Block, it&#8217;s available from the WordPress repository.  The <a href=\"https://docs.dlxplugins.com/photo-block\">documentation page</a> is already available, showing off the plugin&#8217;s features, that enhance the image core block: Cropping, Dimension support, Image Sizing and Object Fit, Add CSS Gram Effects, multiple caption variations and overlay support. It&#8217;s definitely worth exploring if you have a wider range of image needs. </p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"2-word-press-6-0-1-and-6-1-scheduled\">Theme Development for Full Site Editing and Blocks</h2>\n\n\n\n<p><strong>Save The date!</strong> WordPress 6.7 and the new Twenty Twenty-Five theme are just weeks away. Theme Dev Leads,<strong> <a href=\"https://x.com/carolinapoena\">Carolina Nymark</a></strong> and <a href=\"https://x.com/juanfraa\"><strong>Juan Aldasoro</strong></a> will join Developer Hours on <strong>Oct. 29 at 15:00 UTC </strong>for an in-depth look at the theme’s technical details and features. <a href=\"https://www.meetup.com/learn-wordpress-online-workshops/events/304044317/\"><strong>Developer Hours: Exploring the Twenty Twenty-Five Theme</strong></a></p>\n\n\n\n<a href=\"https://www.meetup.com/learn-wordpress-online-workshops/events/304044317/\"><img width=\"600\" height=\"338\" tabindex=\"0\" src=\"https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/DH-October-29-Carolina-Nymark-Juanfra-Aldasoro.webp?resize=600%2C338&ssl=1\" alt=\"\" class=\"wp-image-30507\" /></a>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<p>If you are starting out building a Block Theme, it can be a bit overwhelming with the number of details you might have to consider. In <a href=\"https://developer.wordpress.org/news/2024/10/17/mastering-theme-json-you-might-not-need-css/\"><strong>Mastering theme.json: You might not need CSS</strong></a>, <strong>Justin Tadlock</strong> gives you a walkthrough of many tips, tricks, and techniques for using theme.json and style variations to their full extent.</p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<p><strong>Carlos Daniele</strong> created <a href=\"https://kinsta.com/blog/twenty-twenty-five-theme/\"><strong>A developer’s overview of Twenty Twenty-Five, the next default WordPress theme</strong></a>. &#8220;Twenty Twenty-Five provides an excellent example of the philosophy of democratization of design, and this article will show you its structure in detail.&#8221; he wrote. Daniele looks at the code and explains some of the concepts that were incorporated into the new default theme, especially Section styles and Template patterns. </p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<p>In <a href=\"https://kinsta.com/blog/wordpress-typography-theme-json/\"><strong>Revolutionizing WordPress typography with full site editing and theme.json</strong></a> <strong>Jeremy Holcombe</strong> takes a comprehensive journey through the tools and features of the Site editor and block themes on working with typography on the web and how users can make their typography choices and add them to their site. </p>\n\n\n\n<p><strong>&nbsp;<a href=\"https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/\" target=\"_blank\" rel=\"noreferrer noopener\">&#8220;Keeping up with Gutenberg &#8211; Index 2024&#8221;</a>&nbsp;</strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2024 on. Updated by yours truly. The previous years are also available: <strong><strong><a href=\"https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/\">2020</a>&nbsp;|&nbsp;<a href=\"https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2021/\">2021</a></strong>&nbsp;|&nbsp;<strong><a href=\"https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2022/\">2022</a></strong></strong>&nbsp;|&nbsp;<strong><a href=\"https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/gutenberg-index-2023\">2023</a></strong></p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"3-building-themes-for-fse-and-word-press\">Building Blocks and Tools for the Block editor</h2>\n\n\n\n<p>For the first time, Developer Hours were streamed from YouTube directly, and it made a difference in the numbers of people reached. If you missed it, here is the recording: <a href=\"https://www.youtube.com/watch?v=6lBIkf3xNDw\"><strong>How to Simplify Client Editing in WordPress</strong></a> with <strong>Nick Diego</strong>, <strong>Ryan Welcher</strong> and <strong>Jamie Marsland</strong>. </p>\n\n\n<div width=\"100%\" class=\"wp-block-newsletterglue-showhide ng-block\">\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"toolbelt-video-wrapper\"></div>\n</div>\n</div>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<p><a href=\"https://www.youtube.com/watch?v=JrOpsePAX3c\">In his Live stream</a>,<strong> Ryan Welcher</strong>, explored if he could <strong>replace custom blocks with Block Bindings</strong>. It&#8217;s a continuation of the show from last week. <a href=\"https://www.youtube.com/watch?v=NIDS4PFUHBI\"><strong>Looking at the Block Bindings API coming in WordPress 6.7</strong></a></p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<p><a href=\"https://x.com/3LPU4S\"><strong>Alfredo Navas-Fernandini</strong></a> found <a href=\"https://elpuas.com/blog/you-might-not-need-a-custom-block-the-block-variations-api/\"><strong>You Might Not Need a Custom Block: The Block Variations API</strong></a> and teaches you how to create Block variations with a common examples, a Call-to-Action block, and a Team query block,  assembled from core blocks. In the same mind set, Navas posted earlier <a href=\"https://elpuas.com/blog/you-might-not-need-a-custom-block-the-block-styles-api/\">You Might Not Need a Custom Block: The Block Styles API</a>, showing ways to create more buttons styles and a custom header block. </p>\n\n\n\n<p><strong><a href=\"https://gutenbergtimes.com/need-a-zip-from-master/\">Need a plugin .zip from Gutenberg&#8217;s master branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. </p>\n\n\n\n<p>Now also available via <a href=\"https://playground.wordpress.net/?blueprint-url=https://gutenbergtimes.com/wp-content/uploads/2020/11/playnightly.json\">WordPress Playground</a>. There is no need for a test site locally or on a server. Have you been using it? <a href=\"mailto:pauli@gutenbergtimes.com\">Email me </a>with your experience</p>\n\n\n\n<p><img alt=\"GitHub all releases\" src=\"https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge\" /></p>\n\n\n\n<p class=\"has-text-align-center has-small-font-size\"><em>Questions? Suggestions? Ideas? </em><br /><em>Don&#8217;t hesitate to send <a href=\"mailto:pauli@gutenbergtimes.com\">them via email</a> or</em><br /><em> send me a message on WordPress Slack or Twitter @bph</em>.</p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" />\n\n\n\n<p class=\"has-text-align-center has-small-font-size\">For questions to be answered on the <a href=\"http://gutenbergtimes.com/podcast\">Gutenberg Changelog</a>, <br />send them to <a href=\"mailto:changelog@gutenbergtimes.com\">changelog@gutenbergtimes.com</a></p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\" />\n\n\n\n<hr class=\"wp-block-separator has-css-opacity is-style-wide\" />\n\n\n\n<p class=\"has-text-align-left\"><strong>Don&#8217;t want to miss the next Weekend Edition? </strong></p>\n\n\n<form class=\"wp-block-newsletterglue-form ngl-form ngl-portrait\" action=\"https://gutenbergtimes.com/feed/\" method=\"post\"><div class=\"ngl-form-container\"><div class=\"ngl-form-field\"><label class=\"ngl-form-label\" for=\"ngl_email\"><br />Type in your Email address to subscribe.</label><div class=\"ngl-form-input\"><input type=\"email\" class=\"ngl-form-input-text\" name=\"ngl_email\" id=\"ngl_email\" /></div></div><button type=\"submit\" class=\"ngl-form-button\">Subscribe</button><p class=\"ngl-form-text\">We hate spam, too, and won&#8217;t give your email address to anyone <br />except Mailchimp to send out our Weekend Edition</p></div><div class=\"ngl-message-overlay\"><div class=\"ngl-message-svg-wrap\"></div><div class=\"ngl-message-overlay-text\">Thanks for subscribing.</div></div><input type=\"hidden\" name=\"ngl_list_id\" id=\"ngl_list_id\" value=\"26f81bd8ae\" /><input type=\"hidden\" name=\"ngl_double_optin\" id=\"ngl_double_optin\" value=\"yes\" /></form>\n\n\n<hr class=\"wp-block-separator has-css-opacity is-style-wide\" />\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 19 Oct 2024 08:30:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:82:\"WordPress.org blog: Expanding Our Code of Conduct to Protect Private Conversations\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=17994\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://wordpress.org/news/2024/10/protect-private-conversations/\";s: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:2935:\"<p>At the heart of our community is our shared pledge to create a space that is harassment-free, welcoming, and inclusive for all. Our <a href=\"https://make.wordpress.org/handbook/community-code-of-conduct/\">Community Code of Conduct</a> already outlines a clear set of expectations, while also providing examples of unacceptable actions. Today, we are reinforcing our values by adding another element to our list of unacceptable behaviors: Publishing private messages without consent.</p>\n\n\n\n<h2 class=\"wp-block-heading\">Why This Addition Matters</h2>\n\n\n\n<p>The relationships we build within our community often involve private discussions. These conversations may involve sensitive matters, personal experiences, or simply casual exchanges. Regardless of the content, every individual should feel confident that their private communications will remain private unless they grant explicit permission to share them.</p>\n\n\n\n<p>Sharing private messages without consent is a breach of trust that can also lead to unintended harm, including emotional distress or misrepresentation. When members of our community feel they cannot trust others in their personal conversations, it undermines the collaborative spirit that is crucial to our collective success.</p>\n\n\n\n<h2 class=\"wp-block-heading\">How This Change Protects the Community</h2>\n\n\n\n<p>By explicitly addressing the publication of private messages without consent, we are reinforcing an existing unacceptable behavior in our Community Code of Conduct: Other conduct which could reasonably be considered inappropriate in a professional setting. Sharing private communications without permission is a clear violation of professional integrity.</p>\n\n\n\n<p>This new addition ensures that private messages receive the same level of protection as personal information and that sensitive communications shared in confidence will not be disclosed without prior consent. An important exception to this is when sharing private messages is necessary for reporting incidents or concerns to the <a href=\"https://make.wordpress.org/community/handbook/irt/\">Incident Response Team</a>, as part of our commitment to maintaining a safe and respectful environment.</p>\n\n\n\n<p>Ultimately, this change encourages honest, constructive engagement across all levels of participation.</p>\n\n\n\n<h2 class=\"wp-block-heading\">Moving Forward Together</h2>\n\n\n\n<p>The strength of our community lies in the trust we place in one another. By clarifying and reinforcing our expectations, we are taking another step toward maintaining an inclusive, respectful, and safe environment for everyone.This new addition will take effect immediately, and violations will be handled in accordance with our existing <a href=\"https://make.wordpress.org/handbook/community-code-of-conduct/#enforcement\">enforcement guidelines</a>. Together, we can ensure our community remains a place of collaboration, trust, and mutual respect.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 19 Oct 2024 00: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:17:\"Nicholas Garofalo\";s: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:47:\"WordPress.org blog: WordPress Thanks Salesforce\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=18012\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2024/10/thank-you-salesforce/\";s: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:2643:\"<p>In the midst of our legal battles with Silver Lake and WP Engine, I wanted to take a moment to highlight something positive.</p>\n\n\n\n<p>Because of my friendships with the co-founders of Slack, <a href=\"https://x.com/stewart\">Stewart Butterfield</a> and <a href=\"https://x.com/iamcal\">Cal Henderson</a>, WordPress.org has had a free version of the Pro version of Slack since they started in 2009. We switched from IRC to Slack, and it was like superpowers were unlocked for our team.</p>\n\n\n\n<p>Over the past 10 years, <a href=\"https://slack.com/\">Slack</a> has been our secret weapon of productivity compared to many other open source projects. Its amazing collaboration features have allowed us to scale WordPress from running just a few blogs to now powering around 43% of all websites in the world, almost 10 times the runner-up in the market.</p>\n\n\n\n<p>As we have scaled from very small to very large, Slack has scaled right alongside us, seemingly effortlessly. WordPress.org currently has 49,286 users on its <a href=\"https://slack.com/pricing\">Slack Business+ instance</a>, which would cost at least $8.8M/yr if we were paying. (And we may need to go to their enterprise grid, to support e-discovery in the lawsuit attacks from WP Engine, which would cost even more.) </p>\n\n\n\n<p>This incredible generosity was continued by the enlightened leadership of Marc Benioff at Salesforce when they bought Slack in 2020. However, it has not been widely known or recognized on our <a href=\"https://wordpress.org/five-for-the-future/\">Five for the Future page</a>, which only highlights self-reported contributor hours and doesn&#8217;t mention Salesforce at all.</p>\n\n\n\n<p>This is a grave error, and we are correcting it today. Going forward:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>I would like every business in the world to see the amazing collaboration and productivity gains Slack has enabled for our community of tens of thousands of volunteers worldwide and <a href=\"https://slack.com/\">consider adopting it for their own business</a>.</li>\n\n\n\n<li>Salesforce will have a complimentary top sponsor slot at our flagship WordCamp events in the <a href=\"https://us.wordcamp.org/\">United States</a>, <a href=\"https://europe.wordcamp.org/\">Europe</a>, and <a href=\"https://asia.wordcamp.org/\">Asia</a>, which attract thousands of people each.</li>\n\n\n\n<li>We will update our <a href=\"https://wordpress.org/five-for-the-future/\">Five for the Future program</a> to reflect contributions such as Salesforce&#8217;s going forward.</li>\n</ul>\n\n\n\n<p>We just want to repeat: Thank you. We hope to deepen our partnership with Salesforce in the future.</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 Oct 2024 20:17:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:46:\"Gutenberg Times: WordPress 6.7 Source of Truth\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=30495\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"https://gutenbergtimes.com/6-7-source-of-truth/\";s: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:81160:\"<p>After quite a few rounds of sharing the <a href=\"https://nomad.blog/tag/source-of-truth/\">Source of Truth on my personal site</a>, Birgit Pauli-Haack, the wonderful creator and curator of Gutenberg Times, offered up this space for me to share this resource. Going forward, we&#8217;re going to experiment with it continuing to be shared here in hopes of reaching more content creators, educators, and general WordPress enthusiasts who want to know every detail of the latest &amp; greatest of WordPress.</p>\n\n\n\n<p>As always, I’d recommend staying up to date on the&nbsp;dev notes&nbsp;as those are rolling out along with&nbsp;reviewing the Field Guide when it comes out.</p>\n\n\n\n<p><strong>As a reminder, this is not meant to replace dev notes or the release-specific field guides, which serve important roles and are separate efforts. </strong>I mainly see it as for folks close to the WordPress release itself and educating others than I see it as something broadly helpful for the average WordPress user. It’s a foundational resource but, it’s so long and detailed, it needs to be repackaged to be useful in each space. Feedback is welcomed for improvements for this version and for future versions as I consider how best to share this information.</p>\n\n\n\n<p>Big thank you to everyone who helped in big and small ways.</p>\n\n\n\n<img width=\"652\" height=\"374\" tabindex=\"0\" src=\"https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2024/10/376215782-1f8a8a02-f3fd-464d-a543-00f7a90dd1eb.png?resize=652%2C374&ssl=1\" alt=\"\" class=\"wp-image-30498\" />\n\n\n\n<ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#changelog\">Changelog</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#important-note-guidelines\">Important Note/Guidelines</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#overview\">Overview </a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#important-links\">Important links:</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#6-7-assets\">6.7 assets: </a></li></ol></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#tags\">Tags</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#priority-items-for-6-7\">Priority Items for 6.7</a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#new-default-theme-twenty-twenty-five\">New default theme: Twenty Twenty-Five</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#refining-data-views\">Refining Data Views </a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#enhancements\">Enhancements</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#expanded-extensibility\">Expanded extensibility </a></li></ol></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#consolidating-and-expanding-block-supports\">Consolidating and expanding block supports</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#block-bindings-improvements-including-ui-to-connect-blocks-and-custom-fields-developer-plugin-author-enterprise\">Block Bindings improvements, including UI to connect blocks and custom fields [developer] [plugin author] [enterprise]</a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#ui-to-connect-blocks-and-custom-fields\">UI to connect blocks and custom fields</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#new-apis-to-empower-extenders\">New APIs to empower extenders</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#ux-improvements\">UX improvements</a></li></ol></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#polishing-the-query-loop-block-with-a-focus-on-simplicity\">Polishing the Query Loop block with a focus on simplicity</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#zoom-out-to-compose-with-patterns\">Zoom out to compose with patterns</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#media-improvements\">Media improvements</a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#support-for-heic-image-uploads\">Support for HEIC image uploads</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#auto-sizes-for-lazy-loaded-images\">Auto Sizes for Lazy-loaded Images</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#expanded-and-improved-background-image-support\">Expanded and improved background image support</a></li></ol></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#view-meta-boxes-in-the-iframed-post-editor-plugin-author-enterprise\">View meta boxes in the iframed Post Editor [plugin author] [enterprise]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#font-management-updates-end-user-theme-author\">Font management updates [end user] [theme author]</a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#edit-and-apply-font-size-presets\">Edit and apply font size presets </a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#consistent-interfaces\">Consistent interfaces</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#font-library-enhancements\">Font library enhancements</a></li></ol></li></ol></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#additional-items-for-6-7\">Additional Items for 6.7</a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#template-registration-api-plugin-author-theme-author-developer\">Template Registration API [plugin author] [theme author] [developer]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#preview-options-api-developer-plugin-author-enterprise\">Preview Options API [developer] [plugin author] [enterprise]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#changes-to-heartbeat-api-to-lower-minimum-allowed-time-enterprise-plugin-author\">Changes to Heartbeat API to lower minimum allowed time [enterprise] [plugin author] </a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#customize-heading-level-curation-developer\">Customize heading level curation [developer]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#general-improvements\">General improvements</a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#updated-order-of-editor-actions-for-a-clearer-sidebar\">Updated order of editor actions for a clearer sidebar</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#opt-out-preference-for-choose-a-pattern-modal-when-adding-a-new-page\">Opt out preference for &#8216;Choose a Pattern&#8217; modal when adding a new page</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#more-robust-saving\">More robust saving</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#iterating-on-pattern-shuffling\">Iterating on pattern shuffling</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#writing-flow-improvements\">Writing flow improvements </a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#adding-block-examples-and-previews\">Adding block examples and previews</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#site-editor-focused\">Site Editor focused</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#other\">Other</a></li></ol></li></ol></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#interactivity-api-iteration-bug-fixes-internal-refactor-and-new-apis-developer-plugin-author\">Interactivity API iteration: bug fixes, internal refactor, and new APIs [developer] [plugin author]</a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#new-apis-getserver-state-getservercontext\">New APIs: getServer State &amp; getServerContext</a></li></ol></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#updates-for-the-html-api-plugin-author-developer\">Updates for the HTML API [plugin author] [developer] </a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#time-input-as-a-subcomponent-of-timepicker-developer-plugin-author\">Time input as a subcomponent of TimePicker [developer] [plugin author]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#define-block-variations-via-a-php-file-developer-plugin-author\">Define block variations via a PHP file [developer] [plugin author]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#override-styles-dynamically-plugin-author-developer\">Override styles dynamically [plugin author] [developer]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#help-text-for-radiocontrol-options-developer-plugin-author\">Help text for RadioControl options [developer] [plugin author]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#clearfix-for-the-post-content-block-theme-author-end-user\">Clearfix for the Post Content block [theme author] [end user]</a></li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https://gutenbergtimes.com/6-7-source-of-truth/#continuing-to-improve-php-8-x-support\">Continuing to improve PHP 8.x support</a></li></ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"changelog\"><strong>Changelog</strong></h2>\n\n\n\n<p>Any changes will be catalogued here as the release goes on. </p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oct 21, 2024: added links to published Dev Notes</li>\n</ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"important-note-guidelines\"><strong>Important Note/Guidelines</strong></h2>\n\n\n\n<p><em>This is a public document so please be mindful of the fact that a wider audience than you might think can participate in what’s shared here 🙂&nbsp;</em></p>\n\n\n\n<p><strong>Please do not copy and paste what is in this document </strong>since this will be shared with many people. This should be used to inspire your own content and to ensure that you have the best information about this release. If you do copy and paste, keep in mind that others might do the same, opening the door for some awkwardness around duplicated content out on the web.&nbsp;</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The document is shared publicly so be mindful of what you comment. The audience is large!</li>\n\n\n\n<li>You will have Comment access but not edit access. This is intentional – please comment if you have any questions/concerns/feedback and I’ll follow up.&nbsp;</li>\n\n\n\n<li>If there are drastic changes, this document will be updated and you will be alerted.</li>\n\n\n\n<li>Each item has been tagged using best guesses with different high level labels so that you can more readily see at a glance who is likely to be most impacted.</li>\n\n\n\n<li>Each item has a high-level description, visuals (if relevant), adoption strategy (if relevant), and key resources if you want to learn more.</li>\n</ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"overview\"><strong>Overview&nbsp;</strong></h2>\n\n\n\n<p>Along with a new default theme, there are new features, like the ability to zoom out to compose content with patterns, and new APIs, like the Template Registration API. More than anything though, this release brings refinement to how everything connects together to create a more seamless WordPress experience.</p>\n\n\n\n<p>Of note, this release includes Gutenberg 18.6 &#8211; 19.3 and, for the first time, I used AI to help offer rewrites to different sections.&nbsp;</p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"important-links\">Important links:</h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https://make.wordpress.org/core/2024/09/03/roadmap-to-6-7/\">Roadmap to 6.7</a>.</li>\n\n\n\n<li><a href=\"https://make.wordpress.org/core/6-7/\">6.7 Development Cycle information</a>.</li>\n\n\n\n<li>6.7 Field Guide (coming soon)</li>\n\n\n\n<li>What’s new for developers: <a href=\"https://developer.wordpress.org/news/2024/07/10/whats-new-for-developers-july-2024/\">July</a>, <a href=\"https://developer.wordpress.org/news/2024/08/10/whats-new-for-developers-august-2024/\">August</a>, <a href=\"https://developer.wordpress.org/news/2024/09/10/whats-new-for-developers-september-2024\">September</a>, <a href=\"https://developer.wordpress.org/news/2024/10/10/whats-new-for-developers-october-2024/\">October</a></li>\n</ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"6-7-assets\">6.7 assets:&nbsp;</h3>\n\n\n\n<p>To view all assets in this document, <a href=\"https://drive.google.com/drive/folders/1So-c8M-H45g_zyOZ8ACefZe-F-LD-8cq?usp=sharing\">please review this drive folder</a>.&nbsp;</p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"tags\"><strong>Tags</strong></h2>\n\n\n\n<p>To make this document easier to navigate based on specific audiences, the following tags are used liberally:&nbsp;</p>\n\n\n\n<p>[end user]: end user focus.&nbsp;</p>\n\n\n\n<p>[theme author]: block or classic theme author.&nbsp;</p>\n\n\n\n<p>[plugin author]: plugin author, whether block or otherwise.</p>\n\n\n\n<p>[developer]: catch-all term for more technical folks.&nbsp;</p>\n\n\n\n<p>[site admin]: this includes a “builder” type.&nbsp;</p>\n\n\n\n<p>[enterprise]: specific items that would be of interest to or particularly impact enterprise-level folks</p>\n\n\n\n<p><strong>If no tags are listed, it’s because the impact is broad enough to impact everyone equally.&nbsp;</strong></p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"priority-items-for-6-7\"><strong>Priority Items for 6.7</strong></h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"new-default-theme-twenty-twenty-five\">New default theme: Twenty Twenty-Five</h3>\n\n\n\n<p>6.7 marks the next edition of a default WordPress theme, designed to showcase the latest in WordPress and set a new standard for block themers. This year&#8217;s theme aims to cater to a wide range of bloggers. It’s designed for <strong>simple personal blogs</strong> like ma.tt, <strong>photo blogs</strong> focused on photography or portfolios, and more <strong>complex blogs</strong>, such as news sites that require a broader set of blocks and more complex content.&nbsp;</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1aZM2tL4Tt9IYMbULYJHEAUcp_CWwcb0V/view?usp=drive_link\">demo</a> walking through the theme including style variations, template layouts, and page patterns.<br /><strong>Key Make Posts/GitHub/Trac Issue(s):</strong> <em>Follow the </em><a href=\"https://github.com/WordPress/twentytwentyfive\"><em>Twenty Twenty-Five GitHub repo</em></a><em> and </em><a href=\"https://make.wordpress.org/core/2024/08/15/introducing-twenty-twenty-five/\"><em>read the announcement post</em></a><em> for more information.&nbsp;</em></p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"refining-data-views\">Refining Data Views&nbsp;</h3>\n\n\n\n<p>Following the launch of Data Views in 6.5 and advancements in 6.6, this release is focused on refining the experience with a few new features planned. The aim is to make these views more flexible for customization and more functional to use.&nbsp;</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"enhancements\">Enhancements</h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https://github.com/WordPress/gutenberg/issues/60630\">Ability to set the density of information in the grid layout</a>.</li>\n\n\n\n<li><a href=\"https://href.li/?https://github.com/WordPress/gutenberg/pull/63203\">Option to hide/show the filters in the user interface</a> to add more optionality and reduce clutter.</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/63416\">Ability to customize the column order in table views</a> with the <a href=\"https://github.com/WordPress/gutenberg/pull/64646\">move left/right controls always available</a>, including in the <a href=\"https://github.com/WordPress/gutenberg/pull/64381\">new view configuration UI to manage order across all columns</a>.&nbsp;</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/63487\">Make the Grid layout aspect ratio user configurable</a>.</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/64175#top\">Graduate data view options out of a menu to allow more design expression</a>.</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/63309\">See author’s avatar next to publication status in Pages</a>.</li>\n\n\n\n<li>Mobile responsiveness improvements, including fixes like <a href=\"https://github.com/WordPress/gutenberg/pull/63203\">moving the filtering UI into a toggle-able panel to improve experience on narrow viewports/containers</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/63118\">make SiteHub available for Pages, Patterns, and Templates in mobile viewports</a>, and <a href=\"https://github.com/WordPress/gutenberg/pull/63002\">ensure Patterns and Templates can be edited</a>.</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/64209\">De-emphasise bulk actions on Grid layout</a> after feedback that always being able to see the bulk select option proved to be confusing.</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/64268\">Move bulk actions menu to the Footer</a>, consolidate with the floating toolbar and total items display, to provide an easier to access pathway.&nbsp;</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/65223\">Show item count for each item in the sidebar</a> for access to quick information.&nbsp;</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/65295\">Improved UX of views for Pages</a> with filtered views, like Published and Drafts, that only shows additional filters and hides the “status” filter to prevent ending up in a confusing state.&nbsp;&nbsp;</li>\n</ul>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"expanded-extensibility\">Expanded extensibility&nbsp;</h4>\n\n\n\n<p>As part of enhancing Data Views extensibility and supporting the <a href=\"https://make.wordpress.org/core/2023/07/12/admin-design/\">Admin Redesign</a> efforts, an API was introduced to register and unregister dataview actions. The existing post actions were also moved to globally registered actions and typed actions (see examples in <code>packages/editor/src/dataviews/actions</code>). This enables third-party developers to manage actions as needed. This includes a way to register and unregister core actions around <a href=\"https://github.com/WordPress/gutenberg/pull/64087\">trashing</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/64088\">permanently deleting</a>, and <a href=\"https://github.com/WordPress/gutenberg/pull/64134\">restoring</a> posts. In staying with the idea, users of the component can also unregister actions to duplicate <a href=\"https://github.com/WordPress/gutenberg/pull/64441\">posts</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/64373\">patterns</a>, or <a href=\"https://github.com/WordPress/gutenberg/pull/64388\">template parts</a>.&nbsp;</p>\n\n\n\n<p>Developers can also remove the actions to view <a href=\"https://github.com/WordPress/gutenberg/pull/64467\">posts</a> and <a href=\"https://github.com/WordPress/gutenberg/pull/64464\">post revisions</a> or prevent users from <a href=\"https://github.com/WordPress/gutenberg/pull/64366\">renaming a post</a> or <a href=\"https://github.com/WordPress/gutenberg/pull/64199\">reordering pages.</a> These actions appear in both the Site Editor views and the sidebar in the Post or Site Editor.</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1q3_IyMrAtXe6s1gDc5kSr9qmt484GNNa/view?usp=drive_link\">demo</a> changing grid density, <a href=\"https://drive.google.com/file/d/1B7DeTe6eXG6LCub2dKLLwPFE47TCmXck/view?usp=drive_link\">image</a> of show/hide filters option.<br /><strong>Adoption approach:</strong> updated by default if using a block theme and opt in for extending with two guides to help <a href=\"https://developer.wordpress.org/news/2024/08/27/using-data-views-to-display-and-interact-with-data-in-plugins/\">Using Data Views to display and interact with data in plugins</a> &amp; <a href=\"https://developer.wordpress.org/news/2024/09/23/actions-from-data-views-adding-images-to-the-media-library/\">Actions from Data Views: Adding images to the Media Library</a><br /><strong>Key Make Posts/GitHub/Trac Issue(s):</strong> <em>Follow </em><a href=\"https://github.com/WordPress/gutenberg/issues/63128\"><em>this tracking issue</em></a><em> for more information.</em></p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"consolidating-and-expanding-block-supports\">Consolidating and expanding block supports</h3>\n\n\n\n<p>Several blocks now come with expanded support options, enabling even more design possibilities. Notably, the long-requested shadow support for Group blocks has been added, which is a big win for designers and theme developers:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Buttons: Add border, color, and padding block supports. (<a href=\"https://github.com/WordPress/gutenberg/pull/63538\">63538</a>)</li>\n\n\n\n<li>Categories: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/63950\">63950</a>)</li>\n\n\n\n<li>Column: Enable border-radius support. (<a href=\"https://github.com/WordPress/gutenberg/pull/63924\">63924</a>)</li>\n\n\n\n<li>Comment Author Name: add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/64550\">64550</a>)</li>\n\n\n\n<li>Comment Content: add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/64230\">64230</a>)</li>\n\n\n\n<li>Comment Date: add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/64210\">64210</a>)</li>\n\n\n\n<li>Comment Template: Add Border Block Support. (<a href=\"https://github.com/WordPress/gutenberg/pull/64238\">64238</a>)</li>\n\n\n\n<li>Comment Edit Link: Add Border Block Support. (<a href=\"https://github.com/WordPress/gutenberg/pull/64239\">64239</a>)</li>\n\n\n\n<li>Comment Reply Link: Add border support. (<a href=\"https://github.com/WordPress/gutenberg/pull/64271\">64271</a>)</li>\n\n\n\n<li>File: Add border block support (<a href=\"https://github.com/WordPress/gutenberg/pull/64509\">64509</a>).</li>\n\n\n\n<li>Gallery: Add border block support. (<a href=\"https://github.com/WordPress/gutenberg/pull/63428\">63428</a>)</li>\n\n\n\n<li>Group: Add block support for shadow. (<a href=\"https://github.com/WordPress/gutenberg/pull/63295\">63295</a>)</li>\n\n\n\n<li>Heading: Add border support. (<a href=\"https://github.com/WordPress/gutenberg/pull/63539\">63539</a>)</li>\n\n\n\n<li>Image: Adopt margin block support (<a href=\"https://github.com/WordPress/gutenberg/pull/63546\">63546</a>)</li>\n\n\n\n<li>Latest comments: Add color block support (<a href=\"https://github.com/WordPress/gutenberg/pull/63419\">63419</a>)</li>\n\n\n\n<li>List: add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/63540\">63540</a>)</li>\n\n\n\n<li>List Item: Add color support (<a href=\"https://github.com/WordPress/gutenberg/pull/59892\">59892</a>), add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/63541\">63541</a>).</li>\n\n\n\n<li>Media &amp; Text: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/63542\">63542</a>)</li>\n\n\n\n<li>Paragraph: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/63543\">63543</a>)</li>\n\n\n\n<li>Post Author Biography: Add border support&nbsp; (<a href=\"https://github.com/WordPress/gutenberg/pull/64615\">64615</a>)</li>\n\n\n\n<li>Post Author Name: Add border support&nbsp; (<a href=\"https://github.com/WordPress/gutenberg/pull/64530\">64530</a>)</li>\n\n\n\n<li>Post Author: Add border support&nbsp; (<a href=\"https://github.com/WordPress/gutenberg/pull/64599\">64599</a>)</li>\n\n\n\n<li>Post Comments Form: Add Border Block Support. (<a href=\"https://github.com/WordPress/gutenberg/pull/64233\">64233</a>)</li>\n\n\n\n<li>Post Content: Add background image and padding support (<a href=\"https://github.com/WordPress/gutenberg/pull/62499\">62499</a>)</li>\n\n\n\n<li>Post Date: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/64023\">64023</a>)</li>\n\n\n\n<li>Post Excerpt: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/64022\">64022</a>)</li>\n\n\n\n<li>Post Terms: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/64246\">64246</a>)</li>\n\n\n\n<li>Post Title: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/64024\">64024</a>)</li>\n\n\n\n<li>Preformatted: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/64302\">64302</a>)</li>\n\n\n\n<li>Query Title: Add border support&nbsp; (<a href=\"https://github.com/WordPress/gutenberg/pull/64581\">64581</a>)</li>\n\n\n\n<li>Quote: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/63544\">63544</a>), add spacing supports (<a href=\"https://github.com/WordPress/gutenberg/pull/63545\">63545</a>), add background image and minimum height support (<a href=\"https://github.com/WordPress/gutenberg/pull/62497\">62497</a>), add align support (<a href=\"https://github.com/WordPress/gutenberg/pull/64188\">64188</a>).</li>\n\n\n\n<li>Search: Add margin support. (<a href=\"https://github.com/WordPress/gutenberg/pull/63547\">63547</a>)</li>\n\n\n\n<li>Site Tagline: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/63778\">63778</a>)</li>\n\n\n\n<li>Site Title: Add border support (<a href=\"https://github.com/WordPress/gutenberg/pull/63631\">63631</a>)</li>\n\n\n\n<li>Social Links: Add border block support (<a href=\"https://github.com/WordPress/gutenberg/pull/63629\">63629</a>)</li>\n\n\n\n<li>Tag Cloud: Add border block support (<a href=\"https://github.com/WordPress/gutenberg/pull/63579\">63579</a>)</li>\n\n\n\n<li>Term Description: Add border block support (<a href=\"https://github.com/WordPress/gutenberg/pull/63630\">63630</a>)</li>\n\n\n\n<li>Verse block: Add background image and minimum height support (<a href=\"https://github.com/WordPress/gutenberg/pull/62498\">62498</a>)</li>\n\n\n\n<li>Text orientation controls have been added to more blocks (site-title, site-tagline, verse, and button block.) (<a href=\"https://github.com/WordPress/gutenberg/pull/62727\">#62727</a>)</li>\n</ul>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1Z3aZYjI7kmM2Q1Gzhvq9kiEouNWzdaMR/view?usp=drive_link\">image</a> of shadow support in the Group block.</p>\n\n\n\n<p>In <a href=\"https://make.wordpress.org/core/2024/10/17/roster-of-design-tools-per-block-wordpress-6-6-edition-2/\">Roster of design tools per block (WordPress 6.7 edition</a>, you&#8217;ll find an overview table, updated with the most recent changes. </p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"block-bindings-improvements-including-ui-to-connect-blocks-and-custom-fields-developer-plugin-author-enterprise\">Block Bindings improvements, including UI to connect blocks and custom fields [developer] [plugin author] [enterprise]</h3>\n\n\n\n<p>The Block Bindings API launched in 6.5 and iterated upon in 6.6 allows you to bind dynamic data to block attributes, solving many use cases for custom blocks and powering other features, like overrides in synced patterns. The work for this release centered mainly on polishing and opening the underlying APIs that were deemed stable, improving the overall UX, and adding a user interface (UI) that allows users to connect attributes with custom fields to their binding sources, making it possible to create bindings through the UI instead of the Code Editor.</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"ui-to-connect-blocks-and-custom-fields\">UI to connect blocks and custom fields</h4>\n\n\n\n<p><em>A quick note here, this is specific to post meta fields as the APIs to extend this UI weren’t considered stable yet. This means that other sources can’t use it yet.</em></p>\n\n\n\n<p>This release comes with a new user interface (UI) that allows users to connect attributes with custom fields, making it possible to create bindings through the UI instead of the Code Editor. This UI is controlled by a new editor setting reading a <a href=\"https://github.com/WordPress/wordpress-develop/pull/7258\"><code>new edit_block_binding</code> capability</a>, which is mapped to `edit_post` (if editing a post) or <code>edit_theme_options</code> (if editing a template). This means that by default admin and editor users can create and modify bindings, but this can be overridden with <code>block_editor_settings_all</code> or <code>map_meta_cap</code> filters.</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"new-apis-to-empower-extenders\">New APIs to empower extenders</h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/65713\">APIs to register sources in the client</a>: Allow extenders to show their source value and provide mechanisms to update it if wanted.</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/gutenberg/pull/64102\">Utils to update and remove bindings</a>: Open the door for plugin authors who might want to create their own UI.</li>\n\n\n\n<li><a href=\"https://github.com/WordPress/wordpress-develop/pull/6839\">PHP filter to customize the output of a block bindings source</a>: Provide flexibility for developers that just want to modify the output of a specific source.</li>\n</ul>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"ux-improvements\">UX improvements</h4>\n\n\n\n<p>In terms of UX improvements, this includes everything from warnings when a block is connected to an invalid attribute to changing the placeholder text when a block is bound. Additionally, a <a href=\"https://github.com/WordPress/wordpress-develop/pull/7298\">new “label” property</a> has been added to register_meta to be able to consume a human-readable text, which highly improves the UX, especially for non-developer users. When combined, these all seek to improve the experience of editing and interacting with bound blocks.</p>\n\n\n\n<p>For this release, the possibility of extending this UI hasn’t been opened because the API wasn’t considered stable, but there are plans to do so in the future.</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1V0OduoyRBnFNy2KUtjAvQiu7lUotfpfA/view?usp=drive_link\">demo</a> of UI to connect blocks and custom fields.&nbsp;<br /><strong>Adoption approach: </strong>opt-in by using block bindings UI with the ability to override which users have access to the UI with the `block_editor_settings_all` filter. To disable, you can use the same `block_editor_settings_all` filter and set <code>$editor_settings[\'canUpdateBlockBindings\']</code>as false.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>To read about every change in this release, review <a href=\"https://github.com/WordPress/gutenberg/issues/63018\">this iteration issue</a><strong>.</strong></p>\n\n\n\n<p>The Developer Note covers the details: <a href=\"https://make.wordpress.org/core/2024/10/21/block-bindings-improvements-to-the-editor-experience-in-6-7/\">Block Bindings: Improvements to the Editor Experience in 6.7</a> </p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"polishing-the-query-loop-block-with-a-focus-on-simplicity\">Polishing the Query Loop block with a focus on simplicity</h3>\n\n\n\n<p>WordPress 6.7 introduces significant improvements to the Query Loop block, focusing on simplicity and clarity. One of the most notable changes is the default settings, where the block now automatically inherits the query from the template, eliminating the need for users to enable this option manually. This ensures that posts display immediately both in the editor and on the front end, streamlining the process for most users who just want to see their content without extra configuration. This also applies when adding a Query Loop block to a single post or page, where the settings will be automatically configured to work in that context.</p>\n\n\n\n<p>The Post List variation has been removed from the Inserter due to its confusing settings, which often caused posts to not appear. This change improves the overall user experience.&nbsp;</p>\n\n\n\n<p>In terms of customization, a new toggle allows users to easily switch between default and custom queries. If opting for a custom query, another toggle lets users choose between filtering for posts, pages, or custom post types. Additionally, commonly used settings like Posts Per Page, Offset, and Max Pages to Show have been moved from the toolbar to the sidebar settings panel, consolidating all key options into one central place for easier configuration.</p>\n\n\n\n<p>The update also includes several refinements, such as a quick preview when selecting the Query Loop block in the Inserter and more intuitive help text, particularly for sticky posts, which are now clearly labeled to always appear first. Pagination controls have been enhanced and moved to the Advanced section for better organization. Another new feature is the introduction of a &#8220;format&#8221; parameter, which allows users to filter content by post format, offering more flexibility in creating tailored queries. Combined, these updates make the Query Loop block both easier to use for beginners and more powerful for advanced users.</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1OPLKlFAi3c9J0JNlQlOEuygVzD70pKrd/view?usp=drive_link\">demo</a> of some of the query loop block changes, <a href=\"https://drive.google.com/file/d/13HAuc-2EdkQ8BYCg1NViA2NyIQmy-FA3/view?usp=drive_link\">image</a> of post format support.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong><a href=\"https://make.wordpress.org/core/2024/09/23/core-editor-improvement-simplified-query-loop-block-with-smarter-defaults-intuitive-settings/\">Core Editor Improvement: Simplified Query Loop block with smarter defaults &amp; intuitive settings</a>.</p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"zoom-out-to-compose-with-patterns\">Zoom out to compose with patterns</h3>\n\n\n\n<p>The Zoom Out view aims to simplify the process of composing content at the pattern level, rather than focusing on lower-level, individual blocks. This new feature, accessible as a toggle in the toolbar, introduces a high-level, streamlined approach to site building with several key benefits:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>High-Level Overview of Content Structure: The Zoom Out View allows users to insert and manipulate patterns across a page or template, offering a clearer sense of the content structure.&nbsp;</li>\n\n\n\n<li>Efficient Pattern Manipulation: While zoomed out, users can easily move, delete, shuffle between, and edit patterns, powered by the usual block toolbar.</li>\n\n\n\n<li>Toggle On/Off: This option can be turned on and off in various ways, including clicking the option in the toolbar and double-clicking to edit patterns. All of these options provide pathways in and out of zooming as you’d like.</li>\n\n\n\n<li>Ability to style at a high level: As part of making zoom out more robust, you will still see options to style top level container blocks and any individual blocks that don’t exist within a container. This means you can stay zoomed out and still make quick changes, like changing the background color of a Group block.</li>\n\n\n\n<li>Additional Enhancements: Other refinements include closing the inserter automatically when switching to block-level editing, showing top-level sections in List View, visual vertical displacement when dragging patterns, and an “Add pattern” prompt for the quick inserter.</li>\n</ul>\n\n\n\n<p>This feature gives users a simplified, high-level interface to make design changes, ensuring more cohesive layouts with less granular block management.</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1mQFeDmNun-U_PCedpoTqWlRTYKYB2O5U/view?usp=drive_link\">demo</a> showing a template being built moving in and out of using zoom out.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Zoom out mode iteration issue for 6.7 for a full list of related changes (<a href=\"https://github.com/WordPress/gutenberg/issues/64197\">64197</a>)&nbsp;</p>\n\n\n\n<p><a href=\"https://make.wordpress.org/core/2024/10/21/developer-notes-for-zoom-out-in-wordpress-6-7/\">Developer Notes for Zoom Out in WordPress 6.7</a></p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"media-improvements\">Media improvements</h3>\n\n\n\n<p>Adding and interacting with media is taking a big leap forward in this release with HEIC support, auto sizes for lazy loaded images, and more background image support at an individual block and global level:</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"support-for-heic-image-uploads\">Support for HEIC image uploads</h4>\n\n\n\n<p>“In WordPress 6.7, <a href=\"https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format\">HEIC</a> image uploads <a href=\"https://core.trac.wordpress.org/ticket/53645\">will be automatically converted to JPEG on the server when possible</a>. This allows you to view HEIC images in WP Admin and use them in posts and pages regardless of whether a visitor’s browser supports HEIC. Automatic conversion of HEIC images to JPEG can be disabled using the <code>image_editor_output_format</code> filter.”</p>\n\n\n<pre class=\"wp-block-code has-small-font-size\"><span><code class=\"hljs language-php shcb-code-table shcb-line-numbers shcb-wrap-lines\"><span class=\"shcb-loc\"><span>add_filter( <span class=\"hljs-string\">\'image_editor_output_format\'</span>, <span class=\"hljs-function\"><span class=\"hljs-keyword\">function</span><span class=\"hljs-params\">( $output_format )</span> </span>{\n</span></span><span class=\"shcb-loc\"><span>\n</span></span><span class=\"shcb-loc\"><span>    <span class=\"hljs-keyword\">unset</span>( $output_format&#91;<span class=\"hljs-string\">\'image/heic\'</span>] );\n</span></span><span class=\"shcb-loc\"><span>\n</span></span><span class=\"shcb-loc\"><span>    <span class=\"hljs-keyword\">return</span> $output_format;\n</span></span><span class=\"shcb-loc\"><span>\n</span></span><span class=\"shcb-loc\"><span>} );\n</span></span></code></span></pre>\n\n\n<p>From the <a href=\"https://make.wordpress.org/core/2024/08/15/automatic-conversion-of-heic-images-to-jpeg-in-wordpress-6-7/\">Automatic conversion of HEIC images to JPEG in WordPress 6.7</a></p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"auto-sizes-for-lazy-loaded-images\">Auto Sizes for Lazy-loaded Images</h4>\n\n\n\n<p>“This implements the HTML spec for applying auto sizes to lazy-loaded images by prepending auto to the sizes attribute generated by WordPress if the image has a loading attribute set to lazy. For browsers that support this HTML spec, the image&#8217;s size value will be set to the concrete object size of the image. For browsers that don&#8217;t support the spec, the word &#8220;auto&#8221; will be ignored when parsing the sizesizes value.”</p>\n\n\n\n<p>From the <a href=\"https://core.trac.wordpress.org/ticket/61847\">trac ticket</a> that implemented this feature.</p>\n\n\n\n<p>Developer Note: <a href=\"https://make.wordpress.org/core/2024/10/18/auto-sizes-for-lazy-loaded-images-in-wordpress-6-7/\">Auto Sizes for Lazy Loaded Images in WordPress 6.7</a></p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"expanded-and-improved-background-image-support\">Expanded and improved background image support</h4>\n\n\n\n<p>Recent updates to background image support bring new customization options for content blocks like Quote, Verse, and Post Content. Previously, background image functionality was restricted to container blocks such as Cover and Group, but with expanded support across multiple blocks, users now have more flexibility in design. This enhancement eliminates the need for nesting blocks, making it easier to achieve the desired look by adding a background image to individual blocks.</p>\n\n\n\n<p>Another key improvement is the ability to set background images globally via Styles for block themes for all blocks with background support. For example, this means you can apply a background image across all Quote or Pull Quote blocks within a site, ensuring consistency in design. Additionally, when setting a background image globally or for an individual block, you can enable a fixed background directly from the block settings in Styles. Alternatively, you can define this setting in <code>theme.json</code> using the `background.backgroundAttachment` style property. Finally, a new popover interface has been introduced for background image controls, keeping them neatly hidden when not in use.&nbsp;</p>\n\n\n\n<p>In terms of technical updates, you can now use reference values for background images in <code>theme.json</code>, allowing for code reuse and avoiding potential bugs. For example, you can reference a background image defined via <code>styles.background.backGroundImage</code> by setting a value of <code>{ ref: \'styles.background.backgroundImage\' }</code> for another background image. Overall, these enhancements greatly improve the flexibility and user experience of adding background images across a site.</p>\n\n\n\n<p><strong>Visuals: </strong>images of <a href=\"https://drive.google.com/file/d/1mS1QUNCV4Qe13HHFE-5LWVcMhltgyUaa/view?usp=drive_link\">Quote block</a> and <a href=\"https://drive.google.com/file/d/1FEfhr1-bxFiEHfOubyNb1uFr-TZcbjo3/view?usp=drive_link\">Verse block</a> with background image support, <a href=\"https://drive.google.com/file/d/1nwVqced-a7U3QxnVsUKNVcOxOGjbvSIN/view?usp=drive_link\">demo</a> of using background image tools in Styles.</p>\n\n\n\n<p><strong>Adoption approach:&nbsp;</strong></p>\n\n\n\n<p>Opt out for HEIC support via the <code>image_editor_output_format</code> hook.</p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs language-php\">add_filter( <span class=\"hljs-string\">\'image_editor_output_format\'</span>, <span class=\"hljs-function\"><span class=\"hljs-keyword\">function</span><span class=\"hljs-params\">( $output_format )</span> </span>{\n\n    <span class=\"hljs-keyword\">unset</span>( $output_format&#91;<span class=\"hljs-string\">\'image/heic\'</span>] );\n\n    <span class=\"hljs-keyword\">return</span> $output_format;\n\n} );</code></span></pre>\n\n\n<p>See examples of adding reference values to `theme.json` <a href=\"https://github.com/WordPress/gutenberg/pull/64128\">in the PR that implemented the feature</a>.&nbsp;</p>\n\n\n\n<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>background image block support follow up tasks with a dedicated 6.7 section (<a href=\"https://github.com/WordPress/gutenberg/issues/54336\">54336</a>)</p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"view-meta-boxes-in-the-iframed-post-editor-plugin-author-enterprise\">View meta boxes in the iframed Post Editor [plugin author] [enterprise]</h3>\n\n\n\n<p>Previously, after an effort to <a href=\"https://github.com/WordPress/gutenberg/issues/33346\">iframe the post editor</a>, metaboxes prevented the editor content from loading in an iframe, causing a fair amount of disruption and workarounds. To resolve this and ensure that both metaboxes and canvas content is visible when working on content, a split view option has been added to allow you to access both while editing when the editor is iframed. This change will provide a consistent WYSIWYG experience between the Editor and frontend views.</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The editor running as an iframe will affect many plugin developers and may force you to modify your code (see <a href=\"https://github.com/WordPress/gutenberg/pull/64351#issuecomment-2326301103\">this comment</a>). Expect a dev note on this topic. Ideally, if you are building a plugin that extends the editor with custom data input, you would transition to one of the available <a href=\"https://href.li/?https://developer.wordpress.org/block-editor/reference-guides/slotfills/\">SlotFills</a> in the interface, creating a more integrated user experience.</li>\n\n\n\n<li>This work makes the post editor canvas work as an iframe when there is a meta box.</li>\n\n\n\n<li>The meta box area is resizable, and its height is saved as a user preference. If the browser height is low, the meta box switches to a toggleable details element.</li>\n</ul>\n\n\n\n<p>For enterprise folks who often use plugins that add metaboxes, this is also a change to be aware of and plan for.&nbsp;</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1Sfa0pPnlOJ8_7sxUhrctSnayHgLYfugh/view?usp=drive_link\">demo</a> showing before and after this work with the Yoast plugin as an example.&nbsp;<br /><strong>Adoption approach: </strong>Plugin developers may have to alter their code. Expect a dev note on this topic. <a href=\"https://github.com/Yoast/wordpress-seo/issues/21602\">Here’s an example</a> from Yoast around adjustments that had to be made.<br /><strong>Key Make Posts/GitHub/Trac Issue(s):&nbsp; </strong>Try split content view with open metaboxes (<a href=\"https://github.com/WordPress/gutenberg/pull/64351\">64351</a>)</p>\n\n\n\n<p>Developer Note: <a href=\"https://make.wordpress.org/core/2024/10/18/post-editor-iframing-with-meta-boxes-in-wordpress-6-7/\">Post Editor iframing with meta boxes in WordPress 6.7</a></p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"font-management-updates-end-user-theme-author\">Font management updates [end user] [theme author]</h3>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"edit-and-apply-font-size-presets\">Edit and apply font size presets&nbsp;</h4>\n\n\n\n<p>An enhanced Styles interface allows for greater flexibility when creating, editing, removing, and applying font size presets. Users can now easily modify the presets provided by a theme or create their own custom options. A key feature is the ability to toggle fluid typography, which enables responsive font scaling, with the option to set custom fluid values for finer control over responsiveness. Of note, individual font sizes may opt out of fluid typography if it is turned on globally. Individual font size presets can opt in to fluid typography if it is not turned on globally, creating more possibilities.&nbsp;</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"consistent-interfaces\">Consistent interfaces</h4>\n\n\n\n<p>In addition to these font-related enhancements, the Styles interface has been upgraded to offer more intuitive control over font size presets. These presets, along with color presets, are now available for selection from the Styles sidebar under the &#8220;Browse styles&#8221; option, aligning with the left sidebar Styles menu. This change creates a more streamlined and consistent user experience, making navigating and applying global styles across the site easier and making &nbsp; the fonts management modal dialog more discoverable. (<a href=\"https://github.com/WordPress/gutenberg/pull/62129\">62129</a>)</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"font-library-enhancements\">Font library enhancements</h4>\n\n\n\n<p>Fonts are now grouped by source (<a href=\"https://github.com/WordPress/gutenberg/pull/63211\">63211</a>) helping users understand at a glance where each font comes from. A new “Select All” option (<a href=\"https://github.com/WordPress/gutenberg/pull/63531\">63531</a>) allows for quick activation or deactivation of all fonts at once, streamlining font management. When no fonts are installed, a message now displays in the library tab (<a href=\"https://github.com/WordPress/gutenberg/pull/63740\">63740</a>), improving user awareness. Additionally, enhancements have been made to the &#8220;No fonts installed&#8221; state (<a href=\"https://github.com/WordPress/gutenberg/pull/63533\">63533</a>), clarifying situations when fonts are installed but not yet activated.</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1yOpfEc9fVustc7swG5CXTm6ivGeLBFl9/view?usp=drive_link\">demo</a> showing editing font preset, creating a font preset, and font library improvements.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong><a href=\"https://make.wordpress.org/core/2024/10/08/core-editor-improvement-new-features-and-flows-for-font-management/\">Core Editor Improvement post dedicated to these changes</a>, efforts done across a number of PRs including add font size presets UI (<a href=\"https://github.com/WordPress/gutenberg/pull/63057\">63057</a>), Font Library: group fonts by source (<a href=\"https://github.com/WordPress/gutenberg/pull/63211#top\">63211</a>), and fluid typography: allow individual preset overrides (<a href=\"https://github.com/WordPress/gutenberg/pull/64790\">64790</a>).</p>\n\n\n\n<p>Developer Notes excerpt: <a href=\"https://make.wordpress.org/core/2024/10/20/miscellaneous-block-editor-changes-in-wordpress-6-7/#new-font-size-presets-ui\">New Font Size Presets UI</a></p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"additional-items-for-6-7\"><strong>Additional Items for 6.7</strong></h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"template-registration-api-plugin-author-theme-author-developer\">Template Registration API [plugin author] [theme author] [developer]</h3>\n\n\n\n<p>A new API streamlines the process of registering templates and template parts for plugins, making it easier for developers to integrate custom templates. Previously, plugins had to rely on multiple filters to accomplish this, which created a barrier to entry and limited adoption. With this new API, developers now have a much simpler path to building block templates and aligning with the expectations of WordPress users.</p>\n\n\n\n<p>One key feature of the new API is that plugin-registered templates can be overridden by themes, with fallback options that automatically revert to the plugin&#8217;s registered title and description when necessary. The API also empowers theme builders by offering customization options for these templates. Additionally, developers can unregister existing templates or create custom category templates to suit their needs.</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1jXL79RTt3v7UN9UW_dQ5GT9myUU-juCE/view?usp=drive_link\">image</a> of code showing how to register a template.&nbsp;<br /><strong>Adoption approach:</strong> Opt in. The tutorial, <a href=\"https://developer.wordpress.org/news/2024/08/29/registering-block-templates-via-plugins-in-wordpress-6-7/\">Registering block templates via plugins in WordPress 6.7</a>, walks you through an example of how to use the new API to provide single, archive, and custom templates for a Book custom post type. Here’s an example for now:</p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs language-xml\">register_block_template( \'devblog-plugin-templates//example\', &#91;\n\n\'title\'       =&gt; __( \'Example\', \'devblog-plugin-templates\' ),\n\n\'description\' =&gt; __( \'An example block template from a plugin.\', \'devblog-plugin-templates\' ),\n\n\'content\'     =&gt; \'\n\n<span class=\"hljs-comment\">&lt;!-- wp:template-part {\"slug\":\"header\",\"area\":\"header\",\"tagName\":\"header\"} /--&gt;</span>\n\n<span class=\"hljs-comment\">&lt;!-- wp:group {\"tagName\":\"main\"} --&gt;</span>\n\n<span class=\"hljs-tag\">&lt;<span class=\"hljs-name\">main</span> <span class=\"hljs-attr\">class</span>=<span class=\"hljs-string\">\"wp-block-group\"</span>&gt;</span>\n\n<span class=\"hljs-comment\">&lt;!-- wp:group {\"layout\":{\"type\":\"constrained\"}} --&gt;</span>\n\n<span class=\"hljs-tag\">&lt;<span class=\"hljs-name\">div</span> <span class=\"hljs-attr\">class</span>=<span class=\"hljs-string\">\"wp-block-group\"</span>&gt;</span>\n\n<span class=\"hljs-comment\">&lt;!-- wp:paragraph --&gt;</span>\n\n<span class=\"hljs-tag\">&lt;<span class=\"hljs-name\">p</span>&gt;</span>This is a plugin-registered template.<span class=\"hljs-tag\">&lt;/<span class=\"hljs-name\">p</span>&gt;</span>\n\n<span class=\"hljs-comment\">&lt;!-- /wp:paragraph --&gt;</span>\n\n<span class=\"hljs-tag\">&lt;/<span class=\"hljs-name\">div</span>&gt;</span>\n\n<span class=\"hljs-comment\">&lt;!-- /wp:group --&gt;</span>\n\n<span class=\"hljs-tag\">&lt;/<span class=\"hljs-name\">main</span>&gt;</span>\n\n<span class=\"hljs-comment\">&lt;!-- /wp:group --&gt;</span>\n\n<span class=\"hljs-comment\">&lt;!-- wp:template-part {\"slug\":\"footer\",\"area\":\"footer\",\"tagName\":\"footer\"} /--&gt;</span>\'\n\n] );</code></span></pre>\n\n\n<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong><a href=\"https://developer.wordpress.org/news/2024/08/29/registering-block-templates-via-plugins-in-wordpress-6-7/\">Registering block templates via plugins in WordPress 6.7</a> developer blog post tutorial, Add plugin template registration API (<a href=\"https://github.com/WordPress/gutenberg/pull/61577\">61577</a>).</p>\n\n\n\n<p>Developer Note: <a href=\"https://make.wordpress.org/core/2024/10/20/new-plugin-template-registration-api-in-wordpress-6-7/\">New Plugin Template Registration API in WordPress 6.7</a></p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"preview-options-api-developer-plugin-author-enterprise\">Preview Options API [developer] [plugin author] [enterprise]</h3>\n\n\n\n<p>The latest WordPress release enhances the Preview Options in the block editor, making it easier for developers to customize how content is previewed. A new API allows plugins and themes to add custom items to the preview dropdown menu, enabling users to see content in different formats or environments. This flexibility improves the editing experience while maintaining the existing structure of the Preview dropdown:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Introduces <code>PreviewDropdownMenuItem</code> component for adding custom items to the Preview dropdown</li>\n\n\n\n<li>Allows plugins to add menu items with custom titles and click handlers</li>\n\n\n\n<li>Maintains the existing Preview dropdown structure while allowing for extensibility</li>\n</ul>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1Axvxz-jnDHk0E341zRWF7cPelnRoLfXo/view?usp=drive_link\">image</a> of an example of how a plugin could use this API.&nbsp;<br /><strong>Adoption approach:</strong> opt in.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Add extensibility to PreviewOptions v2 (<a href=\"https://github.com/WordPress/gutenberg/pull/64644#top\">64644</a>)</p>\n\n\n\n<p>Developer Note: <a href=\"https://make.wordpress.org/core/2024/10/18/extending-the-preview-dropdown-menu-in-wordpress-6-7/\">Extending the Preview Dropdown Menu in WordPress 6.7</a></p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"changes-to-heartbeat-api-to-lower-minimum-allowed-time-enterprise-plugin-author\">Changes to Heartbeat API to lower minimum allowed time [enterprise] [plugin author]&nbsp;</h3>\n\n\n\n<p>The WordPress Heartbeat script (used to set post locks, show logged-out warnings in wp-admin, etc.) <a href=\"https://github.com/WordPress/wordpress-develop/pull/7301\">has been updated</a> to <a href=\"https://public-api.wordpress.com/bar/?stat=groovemails-events&bin=wpcom_email_click&redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2023%2F10%2F23%2Fsummary-and-insights-of-phase-3-related-conversations%2F%23%3A%7E%3Atext%3DCollaborative%2520editing%2520%2526%2520asynchronous%2520collaboration&sr=1&signature=e67e40321ccefa55db4f6637890faf5e&user=64259130&_e=eyJlcnJvciI6bnVsbCwiYmxvZ19pZCI6MjAzNzcxODY0LCJibG9nX2xhbmciOiJlbiIsInNpdGVfaWRfbGFiZWwiOiJ3cGNvbSIsIl91aSI6NjQyNTkxMzAsImxvY2FsZSI6ImVuIiwiY3VycmVuY3kiOiJVU0QiLCJjb3VudHJ5X2NvZGVfc2lnbnVwIjoiVVMiLCJzaWdudXBfZmxvd19uYW1lIjoiIiwiZW1haWxfZG9tYWluIjpudWxsLCJwb3N0X2lkIjo3NDYwLCJ1c2VyX2VtYWlsIjoiIiwiZGF0ZV9zZW50IjoiMjAyNC0wOS0xNyIsImVtYWlsX2lkIjoiYjhkMDZiNjFhMWI0NTA2YjJhNjkyN2U1NWQ4YzFiOGYiLCJlbWFpbF9uYW1lIjoicG9zdCIsInRlbXBsYXRlIjoicG9zdCIsImFuY2hvcl90ZXh0IjoiaW1wcm92ZSB0aGUgY3Jvc3MtdXNlciBjb2xsYWJvcmF0aW9uIGV4cGVyaWVuY2UiLCJfZHIiOm51bGwsIl9kbCI6IlwvIiwiX3V0Ijoid3Bjb206dXNlcl9pZCIsIl91bCI6ImFubmV6YXp1IiwiX2VuIjoid3Bjb21fZW1haWxfY2xpY2siLCJfdHMiOjE3MjY1NTQ1NTU2NzMsImJyb3dzZXJfdHlwZSI6InBocC1hZ2VudCIsIl9hdWEiOiJ3cGNvbS10cmFja3MtY2xpZW50LXYwLjMiLCJibG9nX3R6IjowLCJ1c2VyX2xhbmciOiJlbiJ9&_z=z\">improve the cross-user collaboration experience</a>. This update speeds up the &#8220;heartbeat&#8221; a bit, from 15 to 10 seconds, which means post locked notices (when somebody edits a post) will be set and cleared faster. It also allows extenders more flexibility in setting a precise heartbeat poll interval, rather than a fixed set of values, ranging from 1 to 3600 seconds (1 hour).</p>\n\n\n\n<p><strong>Adoption approach: </strong>opt in by making changes to <code>wp.heartbeat.interval()</code> which has been modified to allow theme and plugin authors to set the heartbeat interval to any value between one second and one hour rather than limiting them to a fixed set of values.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Heartbeat API: consider changing the min allowed time (<a href=\"https://core.trac.wordpress.org/ticket/61960\">61960</a>)</p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"customize-heading-level-curation-developer\">Customize heading level curation [developer]</h3>\n\n\n\n<p>The <code>levelOptions</code> block attribute allows you to limit the available heading levels directly through block markup in patterns and templates. Additionally, you can customize the attribute using a filter for both PHP and JavaScript so the applications are broad. This attribute is now available for Core blocks that use heading elements, including <a href=\"https://github.com/WordPress/gutenberg/pull/64106\">Post Title</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/64107\">Query Title</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/64113\">Site Tagline</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/64111\">Site Title</a>, and <a href=\"https://github.com/WordPress/gutenberg/pull/64103\">Comments Title</a>.</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1NChG_4ZAkyPKtkLSyPLlhD0Vm_X4OkZl/view?usp=drive_link\">image</a> of before/after heading curation.<br /><strong>Adoption approach: </strong>Opt in via block markup or filters. For examples, <a href=\"https://github.com/WordPress/gutenberg/pull/63535\">please review the PR</a> that added this option to see both markup and filter examples.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s):</strong> Enable heading level curation. (<a href=\"https://github.com/WordPress/gutenberg/pull/63535\">63535</a>)</p>\n\n\n\n<p>Developer Note excerpt: <a href=\"https://make.wordpress.org/core/2024/10/20/miscellaneous-block-editor-changes-in-wordpress-6-7/#heading-level-curation\">Heading level curation</a></p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"general-improvements\">General improvements</h3>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"updated-order-of-editor-actions-for-a-clearer-sidebar\">Updated order of editor actions for a clearer sidebar</h4>\n\n\n\n<p>The top toolbar in the editors is an important part of the publishing and saving flow, requiring careful consideration around the placement of each item. In this release, two enhancements come together to add clarity and streamline the experience of working across the editors:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reorder the top bar actions to move Save/Publish buttons to the right of the Settings and Global Styles (pinned items) buttons.&nbsp;</li>\n\n\n\n<li>Swap the &#8220;Cancel&#8221; and &#8220;Publish&#8221; buttons in the pre-publish check panel, allowing users to publish without additional cursor movement.</li>\n</ul>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1vLC8_X2APSpX_K1QmzFZHKLN5GMCcXY7/view?usp=drive_link\">demo</a> of streamlined pre-publish flow, <a href=\"https://drive.google.com/file/d/1_UFOlzJ9cfVZ49UUZhU2nBmph8r2UF5l/view?usp=sharing\">image</a> of before/after in the site editor of editor actions, <a href=\"https://drive.google.com/file/d/1plrWkmLLV7dx7jXiGQezXHsVcAx7ROAn/view?usp=drive_link\">image</a> of before/after in the post editor of editor actions.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Editor topbar: Reorder the actions on the right (<a href=\"https://github.com/WordPress/gutenberg/pull/65163\">65163</a>), Swap position of the Pre-publish checks buttons (<a href=\"https://github.com/WordPress/gutenberg/pull/65317#top\">65317</a>).</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"opt-out-preference-for-choose-a-pattern-modal-when-adding-a-new-page\">Opt out preference for &#8216;Choose a Pattern&#8217; modal when adding a new page</h4>\n\n\n\n<p>Based on feedback, a new preference was added to toggle on and off “Show starter patterns” to provide the ability to control whether starter patterns appear when creating a new page.&nbsp;</p>\n\n\n\n<p><strong>Visuals: </strong><a href=\"https://drive.google.com/file/d/1VR5YRm9U4WbrLeknyjX5K5Wh0JihpnJ9/view?usp=drive_link\">demo</a> showing turning off this option.<br /><strong>Adoption approach: </strong>Opt in by turning preference on.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Add opt out preference to the &#8216;Choose a Pattern&#8217; modal when adding a page. (<a href=\"https://github.com/WordPress/gutenberg/pull/65026\">65026</a>)</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"more-robust-saving\">More robust saving</h4>\n\n\n\n<p>Imagine a situation where you are adding an image to your post and, before it finishes loading, you navigate away from the editor, without ever getting a warning that your image hasn’t yet been saved. In WordPress 6.7, work was done to ensure that doesn’t happen anymore with the introduction of temporary block attributes that ensure in-progress media items are eventually saved and shown:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Introduce “local” attributes and use it for the image block. (<a href=\"https://github.com/WordPress/gutenberg/pull/63076\">63076</a>)</li>\n\n\n\n<li>Video Block: Do not persist blob urls and fix undo. (<a href=\"https://github.com/WordPress/gutenberg/pull/63238\">63238</a>)</li>\n\n\n\n<li>Audio Block: Do not persist blob urls and fix undo. (<a href=\"https://github.com/WordPress/gutenberg/pull/63257\">63257</a>)</li>\n\n\n\n<li>File block: Do not persist blob urls and fix undo. (<a href=\"https://github.com/WordPress/gutenberg/pull/63282\">63282</a>)</li>\n</ul>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"iterating-on-pattern-shuffling\">Iterating on pattern shuffling</h4>\n\n\n\n<p>To ensure that pattern shuffling behaves as expected and to minimize the risk of losing customizations made to patterns, several adjustments were made to limit its scope:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Shuffling now applies only to patterns added by the theme or the user.</li>\n\n\n\n<li>Shuffling is only available in the zoomed-out view, and the option has been removed from the block toolbar.</li>\n</ul>\n\n\n\n<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>&nbsp;Remove the Shuffle block toolbar button <a href=\"https://github.com/WordPress/gutenberg/pull/64571\">(</a><a href=\"https://github.com/WordPress/gutenberg/pull/64954\">64954</a>), limit pattern shuffling to theme and user patterns only (<a href=\"https://github.com/WordPress/gutenberg/pull/62677\">62677</a>).</p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"writing-flow-improvements\">Writing flow improvements&nbsp;</h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Allow dropping multiple images to the image block. (<a href=\"https://github.com/WordPress/gutenberg/pull/65030\">65030</a>)</li>\n\n\n\n<li>Drag and Drop: When dragging a mix of video, audio, and image blocks, create individual blocks as appropriate. (<a href=\"https://github.com/WordPress/gutenberg/pull/65144\">65144</a>)</li>\n\n\n\n<li>Inserter: When opening the block inserter, it will now stay open when interacting with the editor canvas. This makes it easier to move around the document while adding blocks. (<a href=\"https://github.com/WordPress/gutenberg/pull/63059\">63059</a>)</li>\n\n\n\n<li>LinkControl: Refined the display of the link preview title and URL when both are same. (<a href=\"https://github.com/WordPress/gutenberg/pull/61819\">61819</a>)</li>\n\n\n\n<li>Link Editing: Automatically add tel to phone number when linking URL. (<a href=\"https://github.com/WordPress/gutenberg/pull/64865\">64865</a>)</li>\n\n\n\n<li>Page editor: Double-click to edit template part. (<a href=\"https://github.com/WordPress/gutenberg/pull/65024\">65024</a>)</li>\n\n\n\n<li>Post Title: Fix pasting in Safari. (<a href=\"https://github.com/WordPress/gutenberg/pull/64671\">64671</a>)</li>\n\n\n\n<li>Post Title: Move selection at the end after pasting over the text. (<a href=\"https://github.com/WordPress/gutenberg/pull/64665\">64665</a>)</li>\n\n\n\n<li>Restore: Move to trash button in Document settings. (<a href=\"https://github.com/WordPress/gutenberg/pull/65087\">65087</a>)</li>\n\n\n\n<li>Slash Inserter: Restrict block list to allowed blocks only. (<a href=\"https://github.com/WordPress/gutenberg/pull/64413\">64413</a>)</li>\n\n\n\n<li>Writing flow: Split heading into default block. (<a href=\"https://github.com/WordPress/gutenberg/pull/61891\">61891</a>)</li>\n</ul>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"adding-block-examples-and-previews\">Adding block examples and previews</h4>\n\n\n\n<p>The following adds previews and examples to blocks so that, when searching in the Inserter, you can quickly see how each might be used:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Excerpt block: Add example of the block. (<a href=\"https://github.com/WordPress/gutenberg/pull/63010\">63010</a>)</li>\n\n\n\n<li>Login/out block: Add example of the block. (<a href=\"https://github.com/WordPress/gutenberg/pull/62937\">62937</a>)</li>\n\n\n\n<li>Post author blocks: Add example and preview. (<a href=\"https://github.com/WordPress/gutenberg/pull/62978\">62978</a>)</li>\n\n\n\n<li>Post content block: Add example of the block. (<a href=\"https://github.com/WordPress/gutenberg/pull/62968\">62968</a>)</li>\n\n\n\n<li>Post title: Add example of the block. (<a href=\"https://github.com/WordPress/gutenberg/pull/62955\">62955</a>)</li>\n\n\n\n<li>Post date block: Add a block example. (<a href=\"https://github.com/WordPress/gutenberg/pull/63368\">63368</a>)</li>\n\n\n\n<li>Post featured image: Add example of the block. (<a href=\"https://github.com/WordPress/gutenberg/pull/63011\">63011</a>)</li>\n\n\n\n<li>Post terms block: Add an example. (<a href=\"https://github.com/WordPress/gutenberg/pull/63369\">63369</a>)</li>\n\n\n\n<li>Query loop block and Posts list: add example (<a href=\"https://github.com/WordPress/gutenberg/pull/63286\">63286</a>)</li>\n</ul>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"site-editor-focused\">Site Editor focused</h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Add colors and typography to the browse styles section. (<a href=\"https://github.com/WordPress/gutenberg/pull/63173\">63173</a>)</li>\n\n\n\n<li>Allow editing of description only for custom templates. (<a href=\"https://github.com/WordPress/gutenberg/pull/63664\">63664</a>)</li>\n\n\n\n<li>Add a typesets section to Typography. (<a href=\"https://github.com/WordPress/gutenberg/pull/62539\">62539</a>)</li>\n\n\n\n<li>Apply same styles to block previews on inserter and Styles. (<a href=\"https://github.com/WordPress/gutenberg/pull/63177\">63177</a>)</li>\n\n\n\n<li>Document bar is now displayed when viewing the Style book and Style revisions (<a href=\"https://github.com/WordPress/gutenberg/pull/62669\">#62669</a>)</li>\n\n\n\n<li>Move font directory into uploads to match WP 6.5. (<a href=\"https://github.com/WordPress/gutenberg/pull/60354\">60354</a>)</li>\n\n\n\n<li>Polish create template part modal. (<a href=\"https://github.com/WordPress/gutenberg/pull/63617\">63617</a>)</li>\n\n\n\n<li>Template parts now show the content panel in the editor settings. (<a href=\"https://github.com/WordPress/gutenberg/pull/62034\">#62034</a>)</li>\n\n\n\n<li>Use four color palette colors instead of five for useStylesPreviewColors. (<a href=\"https://github.com/WordPress/gutenberg/pull/64700\">64700</a>)</li>\n</ul>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"other\">Other</h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Automatically select group variation if there is only one available. (<a href=\"https://github.com/WordPress/gutenberg/pull/61871\">61871</a>)</li>\n\n\n\n<li>Categories List block: Add dropdown for taxonomies. (<a href=\"https://github.com/WordPress/gutenberg/pull/65272\">65272</a>)</li>\n\n\n\n<li>Cover Block: Move Clear Media button from Inspector Controls to Block Controls. (<a href=\"https://github.com/WordPress/gutenberg/pull/64630\">64630</a>)</li>\n\n\n\n<li>Flex dimensions: Rename “Fill” to “Grow”. (<a href=\"https://github.com/WordPress/gutenberg/pull/62779\">62779</a>)</li>\n\n\n\n<li>Format Library: Add alt edit field to inline image (<a href=\"https://github.com/WordPress/gutenberg/pull/64124#top\">64124</a>)</li>\n\n\n\n<li>Image lightbox: Remove duplicate image when lightbox is opened. (<a href=\"https://github.com/WordPress/gutenberg/pull/63381\">63381</a>)</li>\n\n\n\n<li>Image: Adds the block controls for uploading image. (<a href=\"https://github.com/WordPress/gutenberg/pull/64320\">64320</a>)</li>\n\n\n\n<li>Improve Social Icons setup and appending. (<a href=\"https://github.com/WordPress/gutenberg/pull/64877\">64877</a>)</li>\n\n\n\n<li>Make SiteLogoReplaceFlow always available in the Site Logo block toolbar. (<a href=\"https://github.com/WordPress/gutenberg/pull/63499\">63499</a>)</li>\n\n\n\n<li>Move gallery link controls to the block toolbar. (<a href=\"https://github.com/WordPress/gutenberg/pull/62762\">62762</a>)</li>\n\n\n\n<li>Post Date &amp; Comment Date: Add relative date format. (<a href=\"https://github.com/WordPress/gutenberg/pull/62298\">62298</a>) Both the Post Date and Comment Dates now let you <a href=\"https://github.com/WordPress/gutenberg/pull/62298\">set a relative date format</a> (e.g., 00 hours ago).</li>\n\n\n\n<li>Table Block: Add toolbar button to add a caption. (<a href=\"https://github.com/WordPress/gutenberg/pull/47984\">47984</a>)</li>\n\n\n\n<li>Toolbar justification controls for Group and Content blocks The justification controls for the Group and Content blocks are now exposed in the block toolbar. This makes it easier to quickly update these blocks to be left or right-aligned, using a similar interface to text and button blocks. (<a href=\"https://github.com/WordPress/gutenberg/pull/62924\">62924</a>)</li>\n</ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"interactivity-api-iteration-bug-fixes-internal-refactor-and-new-apis-developer-plugin-author\">Interactivity API iteration: bug fixes, internal refactor, and new APIs [developer] [plugin author]</h2>\n\n\n\n<p>For WordPress 6.7, internal improvements and bug fixes were done to ensure that the Interactivity API&#8217;s code is as simple and stable as possible and to make the Interactivity API resilient when used asynchronously (e.g., adding directives or stores after initialization). This paves the way for future performance improvements such as directive code splitting or lazy loading of interactive blocks.&nbsp;</p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"new-apis-getserver-state-getservercontext\">New APIs: getServer State &amp; getServerContext</h3>\n\n\n\n<p>Alongside this, two new APIs are available with <code>getServerState</code> and <code>getServerContext</code>, available from the <code>@wordpress/interactivity</code> package. These functions are required for subscribing to changes in state/context when the HTML is updated using <code>navigate()</code>. These functions return an object that is analogous to the state/context returned by <code>store()</code>/<code>getContext()</code>, with a couple of differences:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The object returned is read-only.</li>\n\n\n\n<li>The object is updated after <code>navigate()</code> calls, using the values defined in the HTML.</li>\n\n\n\n<li>Devs cannot directly use its properties in directives, but they can use callbacks to subscribe to changes in its properties and update the usual state/context.</li>\n</ul>\n\n\n\n<p><strong>Adoption approach: </strong>Opt in. For awareness, some new documentation is available for using the Interactivity API:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/core-concepts/the-reactive-and-declarative-mindset/\">The Reactive and Declarative mindset</a></li>\n\n\n\n<li><a href=\"https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state/\">Understanding global state, local context and derived state</a></li>\n\n\n\n<li><a href=\"https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/core-concepts/server-side-rendering/\">Server-side rendering: Processing directives on the server</a></li>\n</ul>\n\n\n\n<p><strong>Key Make Posts/GitHub/Trac Issue(s):</strong><em>Follow </em><a href=\"https://github.com/WordPress/gutenberg/issues/63232\"><em>this iteration issue</em></a><em> for more information.</em></p>\n\n\n\n<p>Developer Note: <a href=\"https://make.wordpress.org/core/2024/10/15/subscribe-to-changes-in-the-interactivity-api-state-and-context-on-client-side-navigation-in-6-7/\">Subscribe to changes in the Interactivity API state and context on client-side navigation in 6.7</a></p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"updates-for-the-html-api-plugin-author-developer\">Updates for the HTML API [plugin author] [developer]&nbsp;</h2>\n\n\n\n<p>The HTML Processor has a few upgrades and features:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Full HTML Support: HTML Processor can handle any HTML and in only the rarest situations will the HTML Processor now give up, and in none of these cases is it because the processor doesn&#8217;t know how to handle a given tag.</li>\n\n\n\n<li>Ability to modify most text in a document: The first of a new set of modification methods has been added to the HTML API: <code>set_modifiable_text()</code>.&nbsp;</li>\n\n\n\n<li>Full parser mode: The <code>create_full_parser()</code> mode was introduced, which allows the HTML API to process entire HTML documents from start to finish, something that wasn&#8217;t possible before.</li>\n\n\n\n<li>CSS behavior reviewed: The Tag Processor and fragment parser in the HTML Processor will assume a document is in standards mode (no-quirks mode) unless it determines otherwise. In response to this, all CSS-adjacent code has been audited and updated to ensure that the matching of things like class names behaves just as it would in a browser.</li>\n</ul>\n\n\n\n<p><strong>Adoption approach:</strong> opt in by using the HTML API<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>HTML API: Plans for 6.7 (<a href=\"https://github.com/WordPress/gutenberg/issues/60396\">60396</a>)&nbsp;</p>\n\n\n\n<p>Developer Note: <a href=\"https://make.wordpress.org/core/2024/10/17/updates-to-the-html-api-in-6-7/\">Updates to the HTML API in 6.7</a></p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"time-input-as-a-subcomponent-of-timepicker-developer-plugin-author\">Time input as a subcomponent of TimePicker [developer] [plugin author]</h2>\n\n\n\n<p>Sometimes users only need a way to enter time separate from the <a href=\"https://github.com/WordPress/gutenberg/pull/63145\">date for the TimePicker.component</a>. Developers can now offer <code>separateTimePicker.TimeInput</code> fields in their plugins and apps.&nbsp;</p>\n\n\n\n<p><strong>Adoption approach: </strong><a href=\"https://wordpress.github.io/gutenberg/?path=/docs/components-timepicker--docs\">Documentation is available</a> via Storybook.<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>TimeInput: Expose as subcomponent of TimePicker (<a href=\"https://github.com/WordPress/gutenberg/pull/63145\">63145</a>).&nbsp;</p>\n\n\n\n<p>Developer Note excerpt: <a href=\"https://make.wordpress.org/core/2024/10/18/editor-components-updates-in-wordpress-6-7/#timepicker-time-input-can-be-used-in-isolation\">TimePicker: Time input can be used in isolation</a></p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"define-block-variations-via-a-php-file-developer-plugin-author\">Define block variations via a PHP file [developer] [plugin author]</h2>\n\n\n\n<p>6.7 introduces <a href=\"https://github.com/WordPress/gutenberg/pull/62092\">support for referencing a PHP file</a> in block.json for registering block variations. To do this, you must assign the file path as a value for the variations property:</p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs language-json\">{\n\n<span class=\"hljs-attr\">\"variations\"</span>: <span class=\"hljs-string\">\"file:./variations.php\"</span>\n\n}</code></span></pre>\n\n\n<p>Previously, you could only define a variations JSON object, but this change lets you register the variations on the server-side. The PHP file must return an array of variations to register.</p>\n\n\n\n<p><strong>Adoption approach: </strong>opt in.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>block.json: Allow passing filename as variations field (<a href=\"https://github.com/WordPress/gutenberg/pull/62092\">62092</a>)&nbsp;</p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"override-styles-dynamically-plugin-author-developer\">Override styles dynamically [plugin author] [developer]</h2>\n\n\n\n<p>The <a href=\"https://github.com/WordPress/gutenberg/pull/63656\">hook `useStyleOverride` is now available for plugin developers</a> so that styles can be added to the canvas by blocks. This can be especially useful when packaging a component library with custom styles rather than instructing developers to enqueue a separate stylesheet in all the correct locations.&nbsp;</p>\n\n\n\n<p><strong>Adoption approach: </strong>opt in.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Make useStyleOverride public (<a href=\"https://github.com/WordPress/gutenberg/pull/63656\">63656</a>)&nbsp;</p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"help-text-for-radiocontrol-options-developer-plugin-author\">Help text for RadioControl options [developer] [plugin author]</h2>\n\n\n\n<p>“Developers using the Radio Control component can now add help text for each of the listed options by adding an extra `<a href=\"https://github.com/WordPress/gutenberg/pull/63751\">options[].description`</a> property. This becomes even more relevant when the component is used in the context of input forms for visitors and users via the new wp-admin.” &#8211; From <a href=\"https://developer.wordpress.org/news/2024/09/10/whats-new-for-developers-september-2024/\">What’s new for developers? (September 2024)</a></p>\n\n\n\n<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>RadioControl: add support for option help text (<a href=\"https://github.com/WordPress/gutenberg/pull/63751\">63751</a>).</p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"clearfix-for-the-post-content-block-theme-author-end-user\">Clearfix for the Post Content block [theme author] [end user]</h2>\n\n\n\n<p>“<a href=\"https://github.com/WordPress/gutenberg/pull/63690\">A “clearfix” solution</a> is now applied to the Post Content block. This is an old-school technique that ensures blocks after Post Content sit below the content itself, especially in cases where there is a right or left-aligned block at the end of the post. As this was an issue for quite a while, it’s expected that theme developers found other ways to solve this particular problem. Now that it’s solved for the core block, you might need to double-check your existing sites to make sure this doesn’t break any previous layouts. Content creators might have helped themselves by adding a spacer block after the aligned block in questions.” &#8211; From <a href=\"https://developer.wordpress.org/news/2024/09/10/whats-new-for-developers-september-2024/\">What’s new for developers? (September 2024)</a></p>\n\n\n\n<p><strong>Adoption approach:</strong> please double-check to ensure existing layouts continue to work.&nbsp;<br /><strong>Key Make Posts/GitHub/Trac Issue(s):</strong> Post content: Add clearfix (<a href=\"https://github.com/WordPress/gutenberg/pull/63690\">63690</a>)</p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"continuing-to-improve-php-8-x-support\">Continuing to improve PHP 8.x support</h2>\n\n\n\n<p>To continue improving support for PHP 8.x, code specific to prior PHP versions that are no longer supported have been removed.</p>\n\n\n\n<p><strong>Key Make Posts/GitHub/Trac Issue(s): </strong>Remove PHP &lt; 7.2 code (<a href=\"https://core.trac.wordpress.org/ticket/61574\">61574</a>)&nbsp;</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 Oct 2024 19:54:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Anne McCarthy\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:63:\"WordPress Foundation: 2024 WordPress Foundation Meeting Minutes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://wordpressfoundation.org/?p=1193851\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpressfoundation.org/news/2024/meeting-minutes/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14339:\"<h1 class=\"wp-block-heading\">October 17, 2024 &#8211; Online</h1>\n\n\n\n<p><strong>Present</strong>:&nbsp;</p>\n\n\n\n<p>WordPress Foundation Directors: Mark Ghosh, Matt Mullenweg, and Chele Chiavacci Farley</p>\n\n\n\n<p>Guests/Observers: Harmony Romo, Isotta Peira, and Sarah Glenn</p>\n\n\n\n<p>Regrets: None</p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Call to Order</strong></li>\n\n\n\n<li><strong>Financial discussion</strong>\n<ul class=\"wp-block-list\">\n<li><strong>WordPress Foundation financial overview and discussion&nbsp;</strong></li>\n</ul>\n</li>\n</ol>\n\n\n\n<p>Harmony Romo spoke to the current financial position of the WordPress Foundation as of today October 17, 2024 and reported on the current cash position, which is up $44,560 compared to the prior year. She noted that after challenges with Wells Fargo earlier in the year that the foundation has switched to J.P. Morgan.</p>\n\n\n\n<p><strong>WordPress Foundation Cash Position:</strong></p>\n\n\n\n<table class=\"has-fixed-layout\"><tbody><tr><td>J.P. Morgan Commercial Operating Account</td><td>$264,680</td></tr><tr><td>PayPal</td><td>$0</td></tr><tr><td>Stripe</td><td>$0</td></tr></tbody></table>\n\n\n\n<p>She shared that, to date, in 2024 the foundation has received $41,417 in donations, up $12,952 compared to last year. It was noted that since WordCamp US in September 2024 there has been an increase in donations with 48 new recurring donations created and a total of $12,535 donated. <br /><br />Matt Mullenweg inquired about the sources of the increased donations to WPF. Harmony Romo shared that there are currently 174 active recurring donations, an increase of 40 over the prior year. Donations received were from a wide variety of foundation supporters, with no single donor contributing more than $5,000. This ensures that the foundation will meet the required 33.33% public support percentage.</p>\n\n\n\n<p>The board, alongside a recommendation from Harmony Romo, identified that the foundation should maintain a balance of $150,000. There was further discussion as to how the current excess should be directed. It was suggested that donations could be made to non-profit organizations with similar missions (Foundation for Public Code, Black Girls Code, and Internet Archive) as has been done in the past. Matt Mullenweg requested that an agenda item be added to direct $100,000 to the Internet Archive as they are currently in need.</p>\n\n\n\n<ul start=\"2\" class=\"wp-block-list\">\n<li><strong>Motion by Matt Mullenweg to approve a $100,000 donation to the Internet Archive&nbsp;</strong>: Seconded by Chele Chiavacci Farley and Mark Ghosh and carried&nbsp;</li>\n</ul>\n\n\n\n<ul start=\"3\" class=\"wp-block-list\">\n<li><strong>WordPress Community Support, PBC financial overview and discussion</strong></li>\n</ul>\n\n\n\n<p>Harmony Romo spoke to the current financial position of WordPress Community Support, PBC as of today October 17, 2024 and reported on the cash position which is up $667,076 compared to this time in 2023.</p>\n\n\n\n<p><strong>WordPress Community Support Cash Position:<br /></strong></p>\n\n\n\n<table class=\"has-fixed-layout\"><tbody><tr><td>J.P. Morgan Commercial Operating Account</td><td> $2,181,836</td></tr><tr><td>J.P. Morgan Commercial Deposit-Only Account&nbsp; </td><td>$0</td></tr><tr><td>PayPal</td><td>$0</td></tr><tr><td>Stripe</td><td>$0</td></tr></tbody></table>\n\n\n\n<p>Harmony Romo noted that ~$120,000 of our current balance does represent income received for 2025 events and that we still have significant expenses from WordCamp US, held in September 2024, that have yet to be reconciled. </p>\n\n\n\n<p>Matt Mullenweg inquired as to why the cash position is so much higher this year than in the past, and Harmony shared that both WordCamp US and WordCamp Europe ended up with significant surpluses. He requested that the programming team look to address this and suggested that we invest in local marketing for WordCamp US next year, and that the programming team works to reduce ticket prices if possible.</p>\n\n\n\n<ul start=\"4\" class=\"wp-block-list\">\n<li><strong>Discussion of Meetup.com fees and bank strategy </strong></li>\n</ul>\n\n\n\n<p>Harmony Romo shared that the largest overhead expense is $221,529 for Meetup.com fees per year. She shared that there has been some progress and testing of GatherPress, which if successful could reduce overhead expenses by more than 50%.&nbsp;</p>\n\n\n\n<p>Harmony Romo shared that the foundation moved their operating account to J.P. Morgan after challenges with Wells Fargo earlier in the year.</p>\n\n\n\n<p>The board discussed whether or not the WordPress Foundation or WordPress Community Support, PBC should alter their banking strategy. It was decided that there is low financial risk with J.P. Morgan, and opening additional accounts with different banks is not necessary at this time. The board did identify that opening money market accounts would be beneficial for WordPress Community Support, PBC and potentially for the WordPress Foundation.<br /><br />Chele Chiavacci Farley noted that interest income returns on both accounts should be 4-5% on the balances. Mark Ghosh recommended that balances be transferred to money market accounts with an option to automatically fund the operating account as needed to cover expenses. Harmony Romo will discuss this with the J.P. Morgan representatives and follow up with options and details via email.</p>\n\n\n\n<ul start=\"5\" class=\"wp-block-list\">\n<li><strong>Discussion of tax returns</strong></li>\n</ul>\n\n\n\n<p>Harmony Romo shared that in the filing of the 2023 WordPress Foundations Form 990 the foundation highlighted do_action and learn.wordpress.org programs. The main difference in the 2023 filing, over 2022, was an increase in donation income from $23,744 to $36,388.&nbsp;</p>\n\n\n\n<p>As for WordPress Community Support, PBC, the 2023 filing reflected a loss of ($159,983). The loss was due to a large increase in total WordCamps, 71 in 2023 compared to 26 in 2022, and rising inflation that heavily impacted venue as well as food and beverage costs. It was noted that the majority of 2023 losses were related to the flagship events (WordCamp Europe, WordCamp US).  Some of the income for WC Asia that was received in 2020 was reported as income for that year versus being carried forward to offset the 2023 expenses, which also contributed to the loss. This 2023 tax loss will roll forward to offset future years income.&nbsp;</p>\n\n\n\n<p>Chele Chiavacci Farley requested that moving forward all financials shared with the board include the prior years financials, and that we ensure a board meeting is held prior to when taxes are due.&nbsp;</p>\n\n\n\n<ol start=\"3\" class=\"wp-block-list\">\n<li><strong>Programming discussion</strong></li>\n</ol>\n\n\n\n<p>Isotta Peira shared updates on the various WordPress Foundation and WordPress Community Support, PBC programs.&nbsp;</p>\n\n\n\n<p><strong>do_action:</strong></p>\n\n\n\n<p>By the end of 2024, the foundation will have supported 8 do_action charity hackathons that combined produced over 21 charity websites for deserving non-profits. The do_action events are close to revenue neutral and only $1,066 was paid in grants in 2024. Mark Ghosh inquired as to how this compares to last year, and it was shared that there were twice as many do_action events as in 2023, when the Foundation only supported 4. In an effort to promote do_actions, they are now displayed on events.WordPress.org alongside other events, like WordCamps.&nbsp;</p>\n\n\n\n<p><strong>Open source education:</strong><br /><br />So far in 2024, the WordPress training team organized one online Intro to Open Source workshop called <a href=\"https://www.meetup.com/learn-wordpress-online-workshops/events/301830181/\">“Shape the Future: Your Role in WordPress Open Source Contribution</a> that received 40 RSVPs. There were also 108 participants who completed the ‘<a href=\"https://learn.wordpress.org/course/open-source-basics-and-wordpress/\">Open Source Basics and WordPress’</a> Learn WordPress asynchronous course, and six meetup groups that held open source-focused workshops with a combined total of 200 participants that RSVP’d. There were no direct costs associated with any of these programs as they used the Meetup.com infrastructure paid for by WordPress Community Support.</p>\n\n\n\n<p><strong>Learn WordPress</strong><br /></p>\n\n\n\n<p>Learn WordPress, launched in December 2020, continues to grow. There are currently 502 lessons and 24 courses with 38,000 people that have registered. So far, 8,600 learners have completed courses this year, which is an average course completion rate of 21%. There have also been 107 online workshops in 2024 with an average of 33 participants.<br /><br />Matt Mullenweg expressed some concern around the low number of learners (8,600) that completed courses, given that there are two full-time sponsored employees focusing on the program. He requested that the programming team work to increase the number of individuals that complete courses as that is much more valuable than the number of people that register.&nbsp;</p>\n\n\n\n<p>It was also noted that Learning Pathways was launched in August 2024 as a new approach to educational content, and so far, the average learner satisfaction rate is 93%, and the video retention rate for Learning Pathway courses is 59% (this aligns with technology video benchmarks that see a 40-70% retention rate).&nbsp;</p>\n\n\n\n<p><strong>Mentorship Program</strong></p>\n\n\n\n<p>An update was shared on the new WordPress Contributor Working Group that aims to bring in new contributors to WordPress through active mentorship over a six-week period. In 2024 there were two cohorts, the first with 28 mentors supporting 52 mentees and the current cohort with 25 mentors supporting 100 mentees. Mentees in the Spring 2024 cohort had an 89% program satisfaction rate.&nbsp;</p>\n\n\n\n<p>Matt Mullenweg shared that RTCamp has 10 developers prepared to contribute to core, but they need mentorship. He will create a WordPress.org Slack channel with a representative from RT Camp and Hari Shanker.</p>\n\n\n\n<p><strong>Meetups<br /><br /></strong>It was shared that as of today, there are 633 WordPress chapter Meetups in 92 countries, with over 510,000 Meetup members globally, an increase of 10,000 members since last year.&nbsp;</p>\n\n\n\n<p><strong>WordPress Events</strong><strong><br /></strong><strong><br /></strong>So far in 2024, there have been 56 WordCamps and WordPress Events held in 51 countries with 6 events held in the US, with another 22 events scheduled over the next two months for a total of 78 events in 2024 compared to 71 events in 2023. In total the events sold more than 18,500 tickets, which is an increase of 4,500 over the previous year.&nbsp;</p>\n\n\n\n<p>The board discussed the progress here and Matt Mullenweg shared that he thinks we can do much better and would like to see a larger increase in ticket sales for next year.</p>\n\n\n\n<p><strong>Kim Parsell Memorial Scholarship:</strong></p>\n\n\n\n<p>In 2024 the Kim Parsnell Memorial Scholarship recipient was Cynthia Norman of Ontario, Canada who was awarded $3,000. Cynthia was a member for the 2023 mentorship pilot and has since contributed to the WordPress Training Team, and created more than two dozen lessons for Learn WordPress.&nbsp;</p>\n\n\n\n<p>The board was impressed with the impact the scholarship has had and decided to expand the program to offer scholarships for WordCamp Europe and WordCamp Asia in addition to WordCamp US.&nbsp;</p>\n\n\n\n<p>Mark Ghosh suggested that the recipient receives approximately 5 minutes of stage-time to discuss how they became involved, and Matt Mullenweg suggested that this could be built into his keynote at flagship events. Matt Mullenweg also recommended that we write blog posts about recipients and try to encourage more people to apply.&nbsp;</p>\n\n\n\n<ol start=\"4\" class=\"wp-block-list\">\n<li><strong>Updates and new business</strong></li>\n</ol>\n\n\n\n<ul class=\"wp-block-list\">\n<li>New Executive Director</li>\n</ul>\n\n\n\n<p>It was noted that Mary Hubbard will be starting as the new Executive Director of WordPress.org next week. She will also oversee educational programs in 2025 with support from teams focused on community, education, and contribution.&nbsp;</p>\n\n\n\n<ul start=\"2\" class=\"wp-block-list\">\n<li><strong>New business</strong></li>\n</ul>\n\n\n\n<p>Mark Ghosh suggested that WordPress Community Supports look into offering developer badges or certification as a type of learning offering.&nbsp;</p>\n\n\n\n<p>Mark Ghosh suggested that in order to move forward more quickly with GatherPress the foundation may want to consider a hackathon type event focused on building this plugin, as the rapid iteration available at a hackathon may help move this along quicker, since a new solution would directly reduce expenses.&nbsp;</p>\n\n\n\n<ol start=\"5\" class=\"wp-block-list\">\n<li><strong>Next Meeting</strong></li>\n</ol>\n\n\n\n<p>Matt Mullenweg suggested that the foundation move from one annual meeting to two meetings annually. Mark Ghosh, and Chele Chiavacci Farley agreed this would be beneficial as it would allow the new Executive Director to provide an update and opportunities to review financials prior to tax filings being due. </p>\n\n\n\n<p>The board decided the next meeting will be in March, with the following one in August or September.</p>\n\n\n\n<ol start=\"6\" class=\"wp-block-list\">\n<li><strong>In-Camera Session</strong>\n<ul class=\"wp-block-list\">\n<li>Matt Mullenweg called an in-camera session for the board at 9:35 AM PST, and the guests/observers departed. </li>\n</ul>\n</li>\n</ol>\n\n\n\n<p>The In-Camera session was adjourned at 9:55 AM PST.</p>\n\n\n\n<ol start=\"7\" class=\"wp-block-list\">\n<li><strong>Close</strong></li>\n</ol>\n\n\n\n<p>Matt Mullenweg called the meeting to close at 9:57 AM PST.&nbsp;</p>\n\n\n\n<p><strong>ADDENDUM</strong></p>\n\n\n\n<p>After the meeting was adjourned, it was discovered that some courses on Learn.WordPress.org were deprecated during the fiscal year reported on in the board meeting, and thus the total completed number of courses was understated by 4,087. Total completed courses was actually 12,687.</p>\n\n\n\n<p>In addition, it was suggested there be an annual blog post announcing the winner of the Kim Parsell scholarship. This is, in fact, already being done.</p>\n\n\n\n<p>WC Asia 2024 also ended with a surplus, which has increased the cash position of WPCS.</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 Oct 2024 16:09: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:\"Harmony Romo\";s: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:115:\"Do The Woo Community: WooCommerce Caching, Scaling, Plugin Optimization, Security, Headless, and AI with Andre Faca\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=86155\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:109:\"https://dothewoo.io/woocommerce-caching-scaling-plugin-optimization-security-headless-and-ai-with-andre-faca/\";s: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:176:\"In this episode of Woo DevChat, Marcel and Mike discuss optimizing WooCommerce sites with guest Andre Faca, covering caching, performance, scaling, and security best practices.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Oct 2024 08:25: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:5:\"BobWP\";s: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:79:\"WordPress Foundation: WordPress Foundation Donates $100,000 to Internet Archive\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://wordpressfoundation.org/?p=1193835\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wordpressfoundation.org/news/2024/wordpress-foundation-donation/\";s: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:768:\"<p>On October 17th, 2024, the WordPress Foundation Board of Directors made the unanimous decision to make a contribution of $100,000 to the <a href=\"http://Archive.org\">Internet Archive</a>. The WordPress Foundation has long supported the work of the Internet Archive. </p>\n\n\n\n<p>The work this organization does to <a href=\"https://blog.archive.org/2016/10/23/defining-web-pages-web-sites-and-web-captures/\">preserve the Internet</a>, ensures that students, researchers, journalists, librarians, and curious citizens around the globe have access to our digital cultural heritage for many years to come. </p>\n\n\n\n<p>The Board of Directors is hopeful that this donation will make a significant impact, given the recent challenges faced by the organization.</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:\"Thu, 17 Oct 2024 19:54:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Harmony Romo\";s: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:87:\"WPTavern: Developers Remove Plugins From WordPress.org Repository After ACF Controversy\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=175491\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"https://wptavern.com/developers-remove-plugins-from-wordpress-org-repository-after-acf-controversy\";s: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:4525:\"<p>Following the recent ban and <a href=\"https://wptavern.com/acf-plugin-forked-to-secure-custom-fields-plugin\">ACF to Secure Custom Fields fork/takeover</a> incident, some plugin authors have announced their decision to remove their plugins from the WordPress.org repository.</p>\n\n\n\n<h3 class=\"wp-block-heading\">Gravity PDF Plugin</h3>\n\n\n\n<p>The <a href=\"https://wordpress.org/plugins/gravity-forms-pdf-extended/\">Gravity PDF plugin</a> with over 50k active installations and a 4.9 rating is leaving the plugin repository. Its founder Jake Jackson <a href=\"https://gravitypdf.com/news/installing-and-upgrading-to-the-canonical-version-of-gravity-pdf/\">stated</a> that “WordPress co-founder Matt Mullenweg has weaponized WordPress.org and appropriated the popular Advanced Custom Fields plugin from its creators. This action sets a dangerous precedent, and violates the integrity and security of the platform. To minimize the risks to ourselves and our users, the canonical (primary) version of the free and open-source Gravity PDF plugin is now being distributed directly from GravityPDF.com.”</p>\n\n\n\n<p>The team reassured users that all existing PDF settings, custom templates, and fonts will be preserved when transitioning to the new release. Future reviews will be hosted on <a href=\"https://www.g2.com/products/gravity-pdf/reviews\">G2.com</a>. The canonical plugin will use “gravity-pdf” for the slug and text domain, replacing the “gravity-forms-pdf-extended” used on WordPress.org. Updates for the premium version and its extensions will continue directly from GravityPDF.com.</p>\n\n\n\n<a href=\"https://x.com/takisbig/status/1846542405706649856\"><img src=\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXeBCgibxR6Q2OJ7hjcnbnSHUnt0mZul_fiN5UHGXRlnnrG9N_-wKG5tgAE1aTgOKwO7js8IsPnhs3ktfcY0GWU-aQYD8WPiC96FAkml9d58dhZIGWKz3xCQnKaW-hiC0bE_TOgtVV3WIgUg4uFongcFSfvb?key=sYM_dbehUUr6zg7NnQ_agg\" alt=\"\" /></a>\n\n\n\n<a href=\"https://x.com/ajaydsouza/status/1846519982030483735\"><img src=\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXdy92EbP5Jkcj_u3OOrDU7vxQasl9fbRrqJSOLELKPkpSIjUAUe0UnYCP4Hh5mJEfLkN2hPS3KIVfr9DZnlgDJ2M9IEJ0315cClyqVOcZZpJSbZatAhkm9Y7I6rPDC9uzPUSSKDvQW0LlosKhaq0d9ugcKq?key=sYM_dbehUUr6zg7NnQ_agg\" alt=\"\" /></a>\n\n\n\n<h3 class=\"wp-block-heading\">BE Media from Production &amp; Display Posts Plugins&nbsp;</h3>\n\n\n\n<p>Bill Erickson, author of <a href=\"https://en-gb.wordpress.org/plugins/be-media-from-production/\">BE Media from Production</a> and <a href=\"https://wordpress.org/plugins/display-posts-shortcode/\">Display Posts</a>, also expressed concerns, <a href=\"https://displayposts.com/install/\">stating</a>, “I am no longer comfortable hosting my code on WordPress.org given recent actions by Matt Mullenweg.”</p>\n\n\n\n<p><a href=\"https://en-gb.wordpress.org/plugins/be-media-from-production/\">BE Media from Production</a> plugin has been closed and <a href=\"https://wordpress.org/support/topic/plugin-has-moved-to-github/\">Future updates</a> to this plugin will only come from the official GitHub repo.</p>\n\n\n\n<p>He also <a href=\"https://x.com/BillErickson/status/1845872464296808724\">tweeted</a>: “If you use my plugin BE Media from Production, it&#8217;s now hosted only on GitHub.”</p>\n\n\n\n<h3 class=\"wp-block-heading\">Paid Memberships Pro Plugin</h3>\n\n\n\n<p>The Paid Memberships Pro team released version 3.3 and their CEO Jason Coleman <a href=\"https://www.paidmembershipspro.com/pmpro-update-3-3/\">explained</a>, “This is the first update of the core Paid Memberships Pro plugin that will be served off our own license server instead of the wordpress.org repository. We have been serving our premium plugins and several of our free plugins from our own license server for many years. We will now be serving downloads and updates of our core plugin ourselves.”</p>\n\n\n\n<p>He continued, “We plan to follow suit for all of our plugins that are hosted at wordpress.org, excepting a few that are co-maintained with other folks there. The core plugin is still free and users will always be able to update it for free.”</p>\n\n\n\n<p>Version 3.2.2 will be available in the repository for a day or so and then closed. Jason said on <a href=\"https://x.com/jason_coleman/status/1846957738624274560\">X</a> that &#8220;We&#8217;ve had this planned for over a year. Recent events motivated us to expedite things.&#8221;</p>\n\n\n\n<p>Given the current situation, it doesn&#8217;t seem like things will settle down anytime soon. It remains to be seen if other developers too will follow suit. </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 Oct 2024 19:43:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Jyolsna\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"WordPress.org blog: WP Engine Promotions &amp; Coupons\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=17996\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2024/10/wp-engine-promotions/\";s: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:2081:\"<p>Given the egregious legal attacks by WP Engine against WordPress co-founder Matt Mullenweg, a number of their customers have been looking for alternative hosting, and in return a number of hosts have created specials and promotions for WP Engine customers looking to migrate to a host that has great relations with WordPress.org. Here they are, in alphabetical order.</p>\n\n\n\n<p>We&#8217;ll update this post if any new offers come online, get in touch and we&#8217;ll link it.</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https://www.bluehost.com/migrate-wordpress-website?channelid=P61C46097236S625N0B2A151D0E0000V107\">Bluehost will cover migration costs, and credit back your existing contract</a>. They offer 24/7 phone support, you can call them at 844-699-3907. Their wp.cloud-powered Cloud hosting starts at $29.99/mo.</li>\n\n\n\n<li><a href=\"https://www.dreamhost.com/switch-to-dreamhost/\">DreamHost is offering free migrations</a>, with plans starting at $16.95/mo.</li>\n\n\n\n<li><a href=\"https://hostinger.com/migrate\">Hostinger offers free migration for an unlimited number of websites with a 24/7 dedicated customer success team</a>. Their relevant cloud plans start at $7.99/mo. </li>\n\n\n\n<li><a href=\"https://www.nexcess.net/wp-engine-vs-nexcess/\">Nexcess has plans starting at $21/mo</a>.</li>\n\n\n\n<li><a href=\"https://pressable.com/wpe-contract-buyout/\">Pressable will credit back your current WP Engine contract and match their pricing</a>, so if you&#8217;re in the middle of a long contract with WP Engine, you don&#8217;t need to wait until your renewal time.</li>\n\n\n\n<li><a href=\"https://wordpress.com/migrate-from-wp-engine/\">WordPress.com will give you a free year of any plan they offer</a>, and donate 5% of your purchase price to the <a href=\"https://wordpressfoundation.org/\">WordPress Foundation</a>. Their relevant plans start at $25/mo.</li>\n\n\n\n<li>For large-scale enterprise customers, <a href=\"https://wpvip.com/wordpress-vip-vs-wp-engine/\">WordPress VIP will cover the cost of migration</a>. Their plans generally start at $2k/mo.</li>\n</ul>\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:\"Thu, 17 Oct 2024 15:19:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"Gary: HOWTO: Fork 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:25:\"https://pento.net/?p=5587\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://pento.net/2024/10/17/howto-fork-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:9215:\"<p>Congratulations on your decision to fork WordPress! You&#8217;ve taken on a mammoth task, I&#8217;m impressed with your willingness step up to the challenge of a lifetime. I&#8217;m here to give some advice on the things you might not have thought about yet, and what you&#8217;ll need to help the long term success of your fork.</p>\n\n\n\n<p>Forking, I&#8217;m please to share, <a href=\"https://wordpress.org/news/2024/10/spoon/\">is beautiful</a>. It continues to be an important feature of the Open Source ethos, even if it has become more involved as projects have matured. Forking is a valuable tool for Open Source communities to demonstrate that they believe a project should move in a different direction.</p>\n\n\n\n<p>Before we get into the details, however, I do have to offer a few disclaimers. This post is <strong>not</strong>:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An active call for people to fork WordPress. In the spirit of Open Source, I think it&#8217;s important that we publicly talk about what this process looks like, even if it can be an uncomfortable discussion.</li>\n\n\n\n<li>An announcement that I&#8217;m forking WordPress. I don&#8217;t have the free time for that.</li>\n\n\n\n<li>An offer to wrangle your fork of WordPress. I am happy to discuss your plans and offer advice, though.</li>\n</ul>\n\n\n\n<p>Disclaimers out of the way, let&#8217;s begin!</p>\n\n\n\n<h2 class=\"wp-block-heading\">Before you Announce</h2>\n\n\n\n<p>First of all, let&#8217;s talk about that big old elephant in the room: the current level of instability in the WordPress world. I wouldn&#8217;t be surprised to learn that this the major factor in motivating your fork. Unfortunately, this approach won&#8217;t get you very far, so the first thing you need to do is take any feelings you have about it, and set them aside. You need to decide what you&#8217;re in favour of, instead. What are are the positive motivational factors that will make you jump out of bed, and push this project forward for the next decade or more? What will motivate others to join you for the long haul?</p>\n\n\n\n<blockquote><p>Build a community, not an angry mob.</p></blockquote>\n\n\n\n<p>Think carefully about what your fork is going to be named. I&#8217;m willing to bet that you first jumped to calling it <em>{Adjective}</em>Press, or perhaps something with &#8220;WP&#8221; in the name. That&#8217;s a great idea if you&#8217;re planning on your project being forever defined as a protest against WordPress, but you need to think beyond that. How will you define your brand to keep it relevant for decades to come?</p>\n\n\n\n<p>Oh, and make sure you can get the domains and social media handles for your name. Having to try and get them later is just expensive and frustrating.</p>\n\n\n\n<p>Talk to people. Not just your circle of friends and colleagues who agree with you, find people who can offer different perspectives, and decide how your fork is going to help them. Talk to WordPress core contributors (not just committers!), and learn their take on it. Can you present an argument that would convince long term contributors to switch to working on your fork?</p>\n\n\n\n<p>Figure out funding, at least enough to bootstrap your project. As much as I&#8217;d love to be, most of us are not post-economic. You can only get so far as a volunteer project, you&#8217;re going to need at least some people to be paid to work on it. There are big, complex problems that crop up along the way, it&#8217;s hard to solve them if everyone has to context switch between their day job, and their volunteer work.</p>\n\n\n\n<h2 class=\"wp-block-heading\">The Meta Project</h2>\n\n\n\n<p>If you&#8217;ve made it this far into starting your fork, give yourself a pat on the back. You&#8217;ve made it much further than many others do. Your next challenge is deciding the process of building it. You could stick with the <a href=\"https://en.wikipedia.org/wiki/Benevolent_dictator_for_life\">BDFL</a> approach, which certainly has benefits, particularly when first starting out. It might be hard to sell what many folks see as a key weakness in WordPress, though. Perhaps you might like to explore a democratic governance model, or some sort of hybrid approach. Everything has a set of benefits and trade-offs, you&#8217;ll need to decide what works for you.</p>\n\n\n\n<p>You&#8217;re going to have a bunch of technical dirty work to figure out. Where will the code be hosted? How will you track issues? Provide support? Discuss plans? Build community? Track data? Host themes, and plugins? What will you do about mobile apps?</p>\n\n\n\n<p>At first glance, each of these are fairly straightforward to answer, but it&#8217;s very easy to get lost in the possibilities. My advice here is simple: pick something, use it until it stops being valuable. You can always switch to something different later. Switching governance models might be hard, but switching server-side tools is relatively easy.</p>\n\n\n\n<blockquote><p>Do the dirty work, but don&#8217;t get stuck in the weeds.</p></blockquote>\n\n\n\n<p>Start thinking about how you&#8217;ll build your in-person community. Meetups, conferences, hack days, helping people move to your project, there are countless opportunities here to build your community.</p>\n\n\n\n<h2 class=\"wp-block-heading\">The Moat</h2>\n\n\n\n<p>WordPress has three substantial factors that have made it largely unassailable for many years.</p>\n\n\n\n<p>First, there&#8217;s the massive community that&#8217;s built up around WordPress over the years. Regular meetups and conferences are an integral part of building a popular Open Source project. You can&#8217;t really piggy back off the work that WordPress has done over the years here, either. The only way forward is to put in the work to build and maintain a community that you&#8217;re proud to be a part of.</p>\n\n\n\n<p>Second, there&#8217;s the vast selection of plugins and themes that are available to download for free. The quality between options vary wildly, of course, but that&#8217;s largely irrelevant. The fact that so many options exist means there really is something for everyone. You&#8217;re going to need to figure out how to either maintain long term compatibility with existing WordPress plugins and themes, or you&#8217;re going to find yourself reproducing them all.</p>\n\n\n\n<p>Finally, you&#8217;ll need to deal with inertia. The vast majority of WordPress site owners have no need or motivation to change, so you need to make it easy (ideally, your fork would be a drop-in replacement), and beneficial. What will your fork do better to solve real problems?</p>\n\n\n\n<h2 class=\"wp-block-heading\">Tell Your Friends!</h2>\n\n\n\n<p>It&#8217;s around about this point that you&#8217;re probably getting ready to talk about your fork publicly. Go ahead, you&#8217;ve earned it!</p>\n\n\n\n<p>Launch day is inevitably a mix of strong emotions. Elation if you get a huge positive response from the public, maybe discouragement if the public response is a bit more muted. Relief at having made it this far. Optimism about the future. Maybe even some doubt could creep in that you&#8217;re the right person to be wrangling such a huge endeavour. Whatever you end up experiencing, try not to stress about it too much. It&#8217;s a big day, but what really defines your project is what you do with it tomorrow. Next week. Next year.</p>\n\n\n\n<p>Go right back to the start, and remind yourself of the positive reasons that you&#8217;re choosing to build this project. Tell the world those positive reasons, and welcome anyone who wants to join you on the journey.</p>\n\n\n\n<h2 class=\"wp-block-heading\">The Long Haul</h2>\n\n\n\n<p>Not every day is launch day, however. Most of your days will be&#8230; kinda boring, to be honest. That&#8217;s a good thing! Too much excitement will inevitably burn out you and your community. Sustainable effort, day after day, is how you build something to last.</p>\n\n\n\n<blockquote><p>It&#8217;s a marathon, not a sprint.</p></blockquote>\n\n\n\n<p>Of course, there&#8217;ll be ups and downs. It&#8217;s always okay to go back to the start, and reminder yourself (and your community!) of the positive reasons that you&#8217;re all working together on this.</p>\n\n\n\n<p>Oh, and please try to remember that one day, you&#8217;re probably not going to be the right person to lead your project any more. This isn&#8217;t something to fear, or to look forward to, really: projects, communities, and individuals all grow and change. It&#8217;s probably going to be a weird time when you get to this point, but it doesn&#8217;t have to be a time of upheaval and uncertainty. If you&#8217;ve run the project well, you should hopefully have a deep pool of talented folks who can step in to continue what you began.</p>\n\n\n\n<h2 class=\"wp-block-heading\">Have Fun!</h2>\n\n\n\n<p>Finally, it would be remiss of me not to remind you to have fun! It&#8217;s easy to get lost in conflict at times, but it&#8217;s important to remember that&#8230; it&#8217;s just a CMS. It&#8217;s not going to be the end of the world if you take time away from the project, it&#8217;s actively beneficial for you to have a life outside of the internet. Friends, family, pets, hobbies: make time for the things that matter in your life.</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 Oct 2024 01:20:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:14;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"WPTavern: #141 – Christy Nyiri and Mike Straw on Automattic’s Special Projects Team\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=175292\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"https://wptavern.com/podcast/141-christy-nyiri-and-mike-straw-on-automattics-special-projects-team\";s: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:46359:\"Transcript<div>\n<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.</p>\n\n\n\n<p>Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, learning about the work of the Automattic Special Projects Team.</p>\n\n\n\n<p>If you&#8217;d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast, player of choice. Or by going to wptavern.com/feed/podcast. And you can copy that URL into most podcasts players.</p>\n\n\n\n<p>If you have a topic that you&#8217;d like us to feature on the podcast, I&#8217;m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.</p>\n\n\n\n<p>So on the podcast today we have Christy Nyiri and Mike Straw.</p>\n\n\n\n<p>Christy leads the design arm of Automattic&#8217;s Special Projects Team. She taught herself to design and code 17 years ago, and has since worked with a wide range of clients, many of whom you&#8217;ll hear about later.</p>\n\n\n\n<p>Mike is an engineer with the Special Projects Team. He&#8217;s been writing code for over four decades and has been deeply into WordPress for the last seven years.</p>\n\n\n\n<p>Today we&#8217;re pulling back the curtain on the work done at Automattic&#8217;s Special Projects Team, a somewhat mysterious entity within Automattic. Because of its low visibility and its detachment from regular product output, many have never heard of the team or what they produce, but that is about to change.</p>\n\n\n\n<p>Mike and Christy, tell us all about the team, what they do and who they work with and for. They clarify the unique operational model of the team, which resembles an internal agency focusing exclusively on WordPress and open source projects. Their mission isn&#8217;t driven purely by profit. They often support nonprofits and contribute back to the WordPress community.</p>\n\n\n\n<p>We get into the team&#8217;s philosophy of learning from mistakes while striving for excellence. From there work with prominent websites, to assisting household names to more philanthropic work, Mike and Christy illustrates how their work showcases the power and versatility of WordPress. In short, they strive to show the very best that WordPress can produce.</p>\n\n\n\n<p>This episode highlights the technical and design prowess of the Special Projects Team, but also captures the passion and dedication of its members.</p>\n\n\n\n<p>Whether you&#8217;re a WordPress developer, a web design, enthusiastic, or someone interested in the operational intricacies of high caliber web projects, this episode is for you.</p>\n\n\n\n<p>If you&#8217;d like to find out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you&#8217;ll find all the other episodes as well.</p>\n\n\n\n<p>And so without further delay, I bring you Christy Nyiri and Mike Straw.</p>\n\n\n\n<p>I am joined on the podcast by Christy Nyiri and Mike Straw. Hello both.</p>\n\n\n\n<p>[00:03:28] <strong>Christy Nyiri:</strong> Hello.</p>\n\n\n\n<p>[00:03:29] <strong>Mike Straw:</strong> Hello.</p>\n\n\n\n<p>[00:03:31] <strong>Nathan Wrigley:</strong> We&#8217;re going to have a conversation today from WordCamp US. We are in one of the meeting rooms in Portland, Oregon. Christy and Mike have joined me today because they work on a really interesting team, which I don&#8217;t know much about. So they&#8217;re going to school me in how this all hangs together, and how it works.</p>\n\n\n\n<p>Before we begin that though, Christy first, and then Mike afterwards, would you mind just giving us a little potted bio about yourselves. Maybe a minute, or something like that.</p>\n\n\n\n<p>[00:03:55] <strong>Christy Nyiri:</strong> Yeah. Hey, I&#8217;m Christy Nyiri. I&#8217;m Canadian, but I live in Brooklyn now. I&#8217;ve been with Automattic for a little over four years, and it&#8217;s the longest job I&#8217;ve ever held. So that says something about Automattic as a company.</p>\n\n\n\n<p>[00:04:08] <strong>Nathan Wrigley:</strong> Thank you very much Christy. And Mike, give us your little potted bio.</p>\n\n\n\n<p>[00:04:12] <strong>Mike Straw:</strong> I&#8217;m Mike. I&#8217;m currently from Ohio, but I&#8217;m from everywhere. I traveled around a lot as a kid, and then in my adult life. But I joined Automattic about seven years ago, and I just joined the Special Projects Team two years ago. I kind of can&#8217;t hold down a job, so I keep changing places I work. I did that my whole life, changing jobs between company, or between organisations. And then in Automattic, I&#8217;ve kind of bounced around a little bit, and I&#8217;ve settled on the special projects team and I am pretty happy here.</p>\n\n\n\n<p>[00:04:42] <strong>Nathan Wrigley:</strong> Okay, so you&#8217;ve alluded to what we&#8217;re going to talk about today, Mike. You mentioned the Special Projects Team. It&#8217;s kind of an interesting name. It sort of feels a little bit shrouded in mystery. I don&#8217;t know, it almost feels like special forces in in the army, or something like that. You know, this is the team that we deploy when things get a little bit tricky, when things are complicated.</p>\n\n\n\n<p>I don&#8217;t know if that&#8217;s the feeling that you guys get, but it does feel as if what you are working on is, let&#8217;s say, at a higher level than any of the websites I ever built. Put it that way.</p>\n\n\n\n<p>So the first question, and either of you can tackle this. What is the Special Projects Team, and which kind of clients do you work with?</p>\n\n\n\n<p>[00:05:18] <strong>Christy Nyiri:</strong> So the Automattic Special Projects Team, I&#8217;ll read our little mission statement. We just help interesting people, projects, and organisations have a great experience with WordPress.</p>\n\n\n\n<p>[00:05:27] <strong>Nathan Wrigley:</strong> Okay, perfect. Can you name drop? Are you allowed to name drop any of the kind of projects that you&#8217;ve worked on before?</p>\n\n\n\n<p>[00:05:32] <strong>Christy Nyiri:</strong> For sure. You can see a bunch of the projects on our website, which is specialprojects.automattic.com. The biggest one that I worked with personally was Print Magazine, which is like a publication that has been around since the 1940s, and it has a big history in the design community.</p>\n\n\n\n<p>[00:05:48] <strong>Mike Straw:</strong> Some of the ones I really were proud of is End The Backlog. Which was about backlogs of sexual assault in the country, because they won a Webby for their work. The website won a Webby, and the work they&#8217;re doing has actually had real impact, like the numbers and the charts since they started has actually stopped this backlog that&#8217;s going on. So it was like a real social life impact. And I have some background in that field, so I&#8217;m really passionate about it. So seeing that happen was really cool.</p>\n\n\n\n<p>Also, the site we talked about, one of the sites we talked about yesterday was Johan Ernst the explorer, his website, and just the amazing experience of the site itself. The work is pretty amazing.</p>\n\n\n\n<p>Post Secret is another really cool one that we&#8217;ve worked on. There&#8217;s a list, we have, what is it, over 450 production sites running now that we&#8217;ve built over the years. And it&#8217;s actually a fun experience having only been here for two years to periodically go on a website and say, hey, wait a minute, that&#8217;s one of our websites. Because I still don&#8217;t know the list completely.</p>\n\n\n\n<p>[00:06:51] <strong>Nathan Wrigley:</strong> Okay, thank you for that. That&#8217;s great. So we know that some of the websites that you&#8217;re building have impact. Sounds like some of them, especially meaningful to you in particular there, Mike. That&#8217;s really nice.</p>\n\n\n\n<p>What&#8217;s the purpose of the team though? So, as an example, if I rocked up to the special projects team, and just said, I have a brochure website for a local veterinary practice in the town where I live. I&#8217;m guessing that, at some point, you&#8217;re going to filter me out, maybe I don&#8217;t qualify as special.</p>\n\n\n\n<p>And I just wonder, is there a criteria? Is it, I don&#8217;t know, is there a criteria based upon the depth of your pockets, or the type of projects, or the industry you are in, or is it maybe just more, well, there&#8217;s a notorious company? Everybody&#8217;s heard of those, so they qualify as special. What is the criteria that gets you in?</p>\n\n\n\n<p>[00:07:35] <strong>Christy Nyiri:</strong> Well, we&#8217;ve done projects for a huge range of people, like from very high profile projects to, honestly, there is, not a vet, but we have a site for an animal adoption agency that I think is actually just a girl. A young girl, a teenager, and we built her a website.</p>\n\n\n\n<p>So the project has come to us through referrals from other partners that have already existed, and from other Automatticians as well. So if anyone at the company has a project they think would fit with our mission, we can work on that too.</p>\n\n\n\n<p>[00:08:07] <strong>Nathan Wrigley:</strong> Okay. So yeah, there&#8217;s definitely some sort of criteria there. But it seems, I was probably missing the target a little bit. So it really isn&#8217;t necessarily to do with the depth of the pockets, or the fact that you are notorious, it really could be anything.</p>\n\n\n\n<p>[00:08:17] <strong>Christy Nyiri:</strong> It really can, yeah.</p>\n\n\n\n<p>[00:08:19] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;s fascinating. In the presentation blurb that went along with the presentation that you gave yesterday, one of the phrases that you used was, well, you said, connecting partners with the best that the WordPress community has to offer. And as soon as I hear the word WordPress community, I kind of imagine the crowd that we&#8217;re amongst here. Everybody shows up, everybody has their turn, you know, anybody can speak here, anybody can attend here.</p>\n\n\n\n<p>But the sort of slightly exclusive nature of the word special, and the kind of projects that you deal with, how is that connection made? Do you feed back things to the WordPress community? So I&#8217;m just wondering if you could unpack that sentence for me.</p>\n\n\n\n<p>[00:08:54] <strong>Mike Straw:</strong> There&#8217;s a lot there, because we really are, we&#8217;re part of the WordPress community. We are not primarily about making money, but the way I like to word it is, we are here to make WordPress look good.</p>\n\n\n\n<p>We bring things to our partners, we give them the best experience, with the best website we can build for them, and give them the best experience we can for using WordPress.</p>\n\n\n\n<p>So we choose tools, we&#8217;re really big on, like right now using block editor, and all that technology. We&#8217;ve been doing a lot of even no code builds, or low code builds, only building like specific functionality that has to be coded up, but using the block editor, and using the tools so that it&#8217;s just there. And then when they&#8217;re working on their website later, they just go in the editor, and click, and it&#8217;s done. So very simple. So it&#8217;s making the WordPress experience a good experience.</p>\n\n\n\n<p>And then we also, on the other side of it, we try to give back to the community as much as we can. If we do use a plugin, as an example, I was recently on a project where I found a bug in a plugin that we had installed on a site that was a wordpress.org plugin. I went in, I was like, this is the problem, here&#8217;s the bug. And I fixed it inside, so we could get the site going. And then I went on to their forum and said, hey, we found a bug, here&#8217;s the bug, here&#8217;s how I fixed it. And then they&#8217;re like, cool, thank you, and the next release had the fix.</p>\n\n\n\n<p>And we do that with community plugins. We do that with our own products. You know, we&#8217;ll obviously, we&#8217;ll promote Automattic products for them to use. And if there&#8217;s a problem with the product, we&#8217;ll go to the product team and say, we found this. The dog fooding experience, that we dog food pretty much everything that Automattic has to offer. And we find a problem, and we say, we&#8217;ll go to the product team and say, here&#8217;s the bug we found. And sometimes we&#8217;ll also say, here&#8217;s the PR to fix the code.</p>\n\n\n\n<p>[00:10:43] <strong>Nathan Wrigley:</strong> So it&#8217;s kind of like a double pronged thing, in that you are creating things, but then contributing back, maybe improvements to existing things, but also perhaps creating your own functionality and allowing the WordPress repository to get a hold of that. But also, I suppose the community piece there is that you are creating exceptional websites, exceptional experiences, which then are a kind of advert, if you like, for WordPress as a tool, like a showcase almost. You know, the things that you produce, I&#8217;m guessing are of, without blowing your own trumpets, you would probably regard them as of high quality, and good examples of what WordPress itself can do.</p>\n\n\n\n<p>And I do feel at this moment in time, we&#8217;re recording this in 2024, that we do have, not a credibility problem, but we are competing in a marketplace where the tools that are out there, which you can pay, I don&#8217;t know, $20 a month for, we know what we&#8217;re talking about, these SaaS-based tools. They are beginning to be popular. They&#8217;ve got television adverts, they have giant marketing budgets. So one of the ways that I guess WordPress can promote itself is with exceptional websites that people can look at. So, I don&#8217;t know if you&#8217;ve got anything you want to add to that.</p>\n\n\n\n<p>[00:11:48] <strong>Mike Straw:</strong> Yeah. I think, internally, because you know we have our own internal team names. Our team is called Team 51, which sounds as mysterious and strange, and secretive as Special Projects. But really the 51 is for 51%. And that is, we want WordPress to have 51% of the internet. And we&#8217;re doing that by doing things like this because, and this is me personally editorialising a little of, before I came to WordPress, WordPress does kind of have a reputation issue sometimes, because the average external person hears of these suss hosting sites, or because anybody can extend it, anybody can write a plugin.</p>\n\n\n\n<p>And you get a plugin in there that&#8217;s junk, and then the WordPress experience is junk, and then they&#8217;re saying WordPress is junk. And so we&#8217;re trying to highlight, no, WordPress itself is a solid tool, a solid platform, and if you develop well on it, you will have a solid site. And so we do a lot of that just to kind of build the reputation.</p>\n\n\n\n<p>[00:12:46] <strong>Christy Nyiri:</strong> I&#8217;d like to add that, on the design side of things, someone came up to me after the talk yesterday and said, how does WordPress compete with the other platforms out there that are really design focused? And I think that is what we&#8217;re trying to do on our team, is show that you can build really well designed websites with WordPress, and using the block editor.</p>\n\n\n\n<p>It is a more recent thing, I will admit, the block editor only really came to maturity maybe in the last year. And up until then, like I was even very anti-block theme. As a developer I&#8217;m like, I can build it better in PHP, like I know what I&#8217;m doing. But like now that you can adjust padding, and negative margins, and all those things, it&#8217;s an actual tool that you can use to build nice looking things.</p>\n\n\n\n<p>There is some work that needs to be done, but it&#8217;s getting there. And we&#8217;re confident that the more that we show sites that we build, that are full, non headless builds, like straight block themes, that it&#8217;ll inspire other people to do the same.</p>\n\n\n\n<p>[00:13:39] <strong>Mike Straw:</strong> One of the things I will often tell people is, I think I&#8217;m a pretty good engineer, I am a terrible designer. So you tell me what to make a website look like and do, and I will make it do it. If you look at my websites that I have put together, they are disgustingly ugly because a designer has not looked at them.</p>\n\n\n\n<p>With the block editor, I&#8217;ve gotten better. I&#8217;m able to actually make it look pretty decent because it does a lot of that for me. But it&#8217;s that thing of, if you have something that&#8217;s only going to be built by engineers, it&#8217;s going to look like something an engineer built. If you build it like anybody would build a website on any other platform, where you have designers that design, and make the look, and the branding, and you get the marketing in there, whatever team you have, and then the engineers are building what they have said make it look like, you end up with something that&#8217;s nice and pretty.</p>\n\n\n\n<p>And WordPress, I think, has always had that capability, although it required a lot more engineering work historically. But now, I think it&#8217;s amazing now that we now have project builds that, I think we&#8217;ve had some that just had no engineer involvement now.</p>\n\n\n\n<p>[00:14:37] <strong>Nathan Wrigley:</strong> Oh wow. Because the blocks are good enough.</p>\n\n\n\n<p>[00:14:39] <strong>Mike Straw:</strong> Our designers design it, our account managers build it in the block editor, and then they&#8217;re done.</p>\n\n\n\n<p>[00:14:44] <strong>Nathan Wrigley:</strong> It feels a bit like Team 51 is a website building agency, buried within Automattic then. So again, just to let me understand it a little bit more, we&#8217;ve got designers, Christy&#8217;s a designer. We&#8217;ve got developers, Mike is a developer. And it sounded like you mentioned marketing as well. There&#8217;s marketing people as well? What I&#8217;m trying to get to with that question, is it almost like an agency buried inside of Automattic?</p>\n\n\n\n<p>[00:15:09] <strong>Christy Nyiri:</strong> Yeah, you&#8217;re hitting the nail right on the head. Our team does operate on an agency model. There&#8217;s a couple of other teams at Automattic that do as well. One being VIP, and now the other one is lost on me. Oh, The Design Core, they&#8217;re kind of like do all our internal brand stuff.</p>\n\n\n\n<p>So Team 51, we are composed of designers, engineers, and project managers, which we call TAMS, AKA Technical Account Managers. And we also have an operations team. All of us like work together to build sites, as any traditional agency would.</p>\n\n\n\n<p>[00:15:40] <strong>Mike Straw:</strong> The marketing was an example of how a company would build a website. But yeah, for us internally, some of the partners we bring in have a marketing branch, and we will work with them to do the designing. But yeah, we don&#8217;t do marketing ourselves within the team.</p>\n\n\n\n<p>[00:15:56] <strong>Nathan Wrigley:</strong> Okay. And I think I&#8217;m right in saying that the WP Tavern website, and if you are listening to this, there&#8217;s a high chance that either you&#8217;re on an RSS reader, and you&#8217;re listening to this on a podcast player, or you&#8217;re on the WP Tavern website. I think the Tavern website is one of your projects.</p>\n\n\n\n<p>[00:16:10] <strong>Mike Straw:</strong> I believe so.</p>\n\n\n\n<p>[00:16:10] <strong>Christy Nyiri:</strong> Yeah. Yeah, I remember working on that, or working with other people who were working on it. But yeah, we did that a few years ago, but it was before block themes. I think it&#8217;s actually probably due for a revamp to create a block theme version of it.</p>\n\n\n\n<p>[00:16:24] <strong>Nathan Wrigley:</strong> I&#8217;m going to be in your inbox.</p>\n\n\n\n<p>Okay, let&#8217;s go in this direction. If we&#8217;re going to categorise your team as special, which is obviously the name. What is special? What do you bring to the table that any other agency out there might not? I am not trying to put you up against, or make you give me a competitive analysis statement of how you&#8217;re different. But what are some of the things that you&#8217;ve noticed in your time there, which really does separate it out as a special thing?</p>\n\n\n\n<p>[00:16:47] <strong>Christy Nyiri:</strong> Yeah, I think the biggest thing with our team is that we&#8217;re just like really WordPress focused, and involved in the community, and the open source nature of WordPress, which a lot of like other larger agencies, building larger sites, aren&#8217;t. They&#8217;re doing headless builds using whatever sort of build processes they are, and we&#8217;re like hardcore, a hundred percent block themes. So that&#8217;s one special thing about us.</p>\n\n\n\n<p>[00:17:08] <strong>Mike Straw:</strong> And, while we use the agency model, we don&#8217;t directly operate like an agency. An agency is a company trying to make money by building websites. So they&#8217;re going to try to do the things that are going to help them bring in good income, and that&#8217;s kind of what they&#8217;re thinking about.</p>\n\n\n\n<p>We are more, even though we operate on that model, that&#8217;s how we interact with partners that we&#8217;re working on with websites and things like that. The things we&#8217;re doing is not to extract funding from them. Again, it&#8217;s about us making a project that shines, and does good things, and makes a site that they will be proud of and brag to their friends about. And so we don&#8217;t operate in that.</p>\n\n\n\n<p>And we&#8217;re also just, the entire team is people that are just really, really passionate about WordPress. We want to make it look good. We want to give the best that we have to our partners, to the community. It&#8217;s not unusual, when we discover a bug or a glitch, there&#8217;s somebody within minutes saying, okay, who do we need to talk to, to make sure this works right for everybody else that&#8217;s running into this.</p>\n\n\n\n<p>[00:18:09] <strong>Nathan Wrigley:</strong> Do you end up doing sort of some philanthropic work as well? Because this is something buried within Automattic, and Automattic as we know, the three of us at least do, and dear listener, if you don&#8217;t, you can go and explore what Automattic do. They&#8217;ve got multiple revenue streams, and so a traditional agency, I&#8217;m imagining their revenue stream is client work. And the fact that Automattic has other revenue streams, does that make it possible for you to do website builds that aren&#8217;t necessarily going to be, air quotes, profitable? That perhaps you could describe as, I don&#8217;t know, philanthropic?</p>\n\n\n\n<p>A good example may be The Tavern actually because, as far as I&#8217;m aware, it doesn&#8217;t, there&#8217;s no revenue stream coming out of The Tavern. The decision has been made to keep a news organisation for WordPress going, and it&#8217;s being kept alive by your team, but there&#8217;s no revenue stream there. So I&#8217;m wondering, do you have that? Is it possible for you to do things on a more philanthropic nature because of the funding system that you&#8217;ve got?</p>\n\n\n\n<p>[00:19:03] <strong>Christy Nyiri:</strong> Yeah, I think exactly what you&#8217;re saying. We are not like a profits based team. We work on just trying to showcase the best of what WordPress can do. And so we definitely have done sites for partners that are nonprofits, and we help them build their web presence online.</p>\n\n\n\n<p>[00:19:22] <strong>Mike Straw:</strong> I think End The Backlog is a great example of that. There&#8217;s a lot of ones that are just, they&#8217;re not profit making entities. They&#8217;re just groups that are trying to do better things in the world, and we&#8217;re providing some service to that. We&#8217;re not necessarily we&#8217;re not like, this is a good, although that comes into the equation, it&#8217;s not a, we&#8217;re doing this because it&#8217;s a good social justice thing or something, but it&#8217;s a good place we can work. But the outcome is definitely there of enabling these organisations to be able to do things that they might not otherwise be able to do because of financial considerations.</p>\n\n\n\n<p>[00:19:55] <strong>Nathan Wrigley:</strong> But it does sound then as if the overall purpose of the special projects team then, and we did allude to this a little bit ago, but we probably could go a little bit further, is to act like a bit of a showcase for WordPress, and just to sort of exemplify the very best of what it can do.</p>\n\n\n\n<p>And I don&#8217;t know if you&#8217;ve got like one place, one domain where we can go, and look at the work that you&#8217;ve done, or if it&#8217;s more of, no, you&#8217;ll have to be a bit inventive, and Google, and contact us, and we&#8217;ll tell you what we&#8217;ve built.</p>\n\n\n\n<p>But it does feel like that&#8217;s the point. Here&#8217;s a big property. Here&#8217;s an important thing, whether it&#8217;s philanthropic or not, and we&#8217;re going to churn out the best that WordPress can do, and thereby, sort of vicariously let the community know, here&#8217;s WordPress. Here&#8217;s how credible it is. Here&#8217;s the kind of people with the stature that they&#8217;ve got who are using it.</p>\n\n\n\n<p>[00:20:41] <strong>Mike Straw:</strong> As of this week, you can go to specialprojects.automattic.com, which has a list of websites, showcases. It actually has some of the tools we&#8217;ve built, and some of the blocks that we&#8217;ve got out there.</p>\n\n\n\n<p>Going back to contributing to the WordPress community, there&#8217;s a pull request to put our Accordion Block into Gutenberg Core.</p>\n\n\n\n<p>But actually, going back to that whole showcasing idea, the actual way back origins of this team go back to when Matt was working for CNET and building WordPress. And he would build WordPress sites for his friends and say, here&#8217;s a site I made in WordPress, isn&#8217;t WordPress cool? I&#8217;m not quoting him. I don&#8217;t know what he actually said exactly, but that&#8217;s the gist of what was happening.</p>\n\n\n\n<p>But that was kind of how, when we were starting as a team back in the day, a lot of times it was a, we&#8217;d see a site hosted on, I don&#8217;t know if it was around back then, but a Wix or a Squarespace kind of environment, and we&#8217;d be like, we could make that in WordPress.</p>\n\n\n\n<p>The team would build a WordPress site mirroring that site, and then go to that person and say, look, we made a WordPress site, this is probably going to be a lot easier for you to work with than wherever you are. And that&#8217;s kind of the origins of, literally, let&#8217;s make WordPress look good by building good WordPress sites.</p>\n\n\n\n<p>[00:21:53] <strong>Nathan Wrigley:</strong> Forgive me for sort of making this assumption, but it seems like you&#8217;re both quite happy with the work that you are doing. It&#8217;s got value, there&#8217;s some credibility to the work that you&#8217;re doing. I mean, that kind of stuff going on a CV looks nice, right?</p>\n\n\n\n<p>And I&#8217;m just wondering if somebody listening to this has the thought that, I think I&#8217;m doing good work, I think I have that caliber in me.</p>\n\n\n\n<p>How did you end up dropping into this team? Was it that you were Automatticians already? You may have touched on this in your bio at the beginning, I can&#8217;t remember. Is there a way that you can find yourself into this team? Do you hire externally? There&#8217;s a lot in there, but just tell us what you can.</p>\n\n\n\n<p>[00:22:27] <strong>Mike Straw:</strong> Can I say yes?</p>\n\n\n\n<p>[00:22:28] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;ll do it.</p>\n\n\n\n<p>[00:22:30] <strong>Mike Straw:</strong> Because I think we have very different experiences. You got hired into 51. So we&#8217;d had very different experiences on this, and I think from both ways of, I came in, I got hired by Automattic about seven years ago. Basically rediscovered WordPress, went to a conference, became a happiness engineer doing wordpress.com support.</p>\n\n\n\n<p>And then, I think I said earlier, I kind of can&#8217;t hold down a job. I switched from wordpress.com support to doing WooCommerce support. And then I went through, we had an internal developer apprenticeship program that I went through, back to engineering, and worked as an engineer on the woocommerce.com website.</p>\n\n\n\n<p>But back when I was a wordpress.com happiness engineer, one of the sites came in for support, who happens to be one of my favorite authors. So I saw her site, and actually it was a, she made a post on her blog of, I&#8217;m having a problem with my like button or something. I&#8217;m like, oh, well I have the access, I&#8217;m doing support, I can go check on it. And I went in, and I start reading, and it had this little flag on it saying, this is a Team 51 site.</p>\n\n\n\n<p>So I went and looked. It&#8217;s like, you contact these people. I was like, okay, what is this Team 51? Are they alien secret people? I don&#8217;t know because I hadn&#8217;t, I was new enough, I didn&#8217;t know who they were. And so I messaged someone, I was like, here&#8217;s the thing. And then we got chatting, and he started talking about what they&#8217;re doing. I&#8217;m like, oh my gosh, I want to, this just sounds really cool.</p>\n\n\n\n<p>And once an opportunity came in, after I was an engineer for a while, and then they just happened to have an internal thing saying, we&#8217;re looking for some engineers. And I was like, hello, please, yes, and contacted them and then got in. So we do some of that internal hiring kind of thing. But also, and I think Christy can talk more about getting from the outside.</p>\n\n\n\n<p>[00:24:09] <strong>Nathan Wrigley:</strong> Okay. So there is internal, there&#8217;s mechanisms internally within Automattic to make your way toward the team. But Christy&#8217;s got a different story.</p>\n\n\n\n<p>[00:24:15] <strong>Christy Nyiri:</strong> I guess I didn&#8217;t say this earlier, but I lead the design arm of Special Projects. When I got involved with Automattic I was, like I&#8217;ve been designing and developing websites, self-taught for like, I don&#8217;t know, 17, 18 years now. And I started with WordPress about 17 years ago, when it was so young.</p>\n\n\n\n<p>And it was like February, 2020, and I was looking for a full-time role somewhere, and I had a friend who was on the Tumblr engineering team at the time. And he&#8217;s like, why don&#8217;t you just apply at Automattic? And I was like, oh, okay.</p>\n\n\n\n<p>And then I applied, and went through the whole trial, and the interview. And the interview was for a product designer. And I don&#8217;t really do product design. I&#8217;m a web, UI person. But I went through the trial expecting eventually like, to get an offer, it would be as the product designer. And they were like, oh, actually we have this team for you, we think you&#8217;d be good on, it&#8217;s called Team 51. And like I had the same reaction as Mike, Team 51, what is that? It sounds mysterious.</p>\n\n\n\n<p>And I kind of like looked on the website that they had, and looked at who was on the team, and Jeffrey Zeldman was on the team at the time. Oh my God, if I get to work with Jeffrey Zeldman, like, amazing. And so I was thrilled to get hired at that time.</p>\n\n\n\n<p>But I was the first internal designer on the team at that point. They didn&#8217;t really have anyone else. They were working with some contractors who&#8217;s, a lot of them are still with us. We&#8217;ve now grown from just me, to like three other internal designers on our team. So the benefit for my design side of the team is that having internal designers means they can work on internal projects, and they&#8217;re more closely associated with the brand. So they can do like Automattic brand things as well. Because like, in addition to the websites, sometimes we do other projects. I am involved in kind of a rebrand for Automattic. There will be something coming hopefully in the next year or so in that end.</p>\n\n\n\n<p>[00:25:58] <strong>Nathan Wrigley:</strong> Would it be fair to say then, if I find a website and the logo of Automattic is at the bottom of the footer, would that be something that is likely to have been done by your team?</p>\n\n\n\n<p>[00:26:07] <strong>Christy Nyiri:</strong> Some of them, yeah. Not all of them. We do some internal builds, but there&#8217;s definitely ones we haven&#8217;t done.</p>\n\n\n\n<p>[00:26:13] <strong>Nathan Wrigley:</strong> Okay. Yeah, so it&#8217;s not guaranteed, but it&#8217;s a probable. Do you find yourself involved in Automattic properties that have got nothing to do with WordPress as well? So, I don&#8217;t know, things like Pocket Casts and, dare I say it, Tumblr, things like that.</p>\n\n\n\n<p>[00:26:25] <strong>Mike Straw:</strong> We&#8217;ve built Tumblr sites as part of it. We&#8217;ve had a couple people just kind of get directly involved on building Tumblr themes. One of the ones, the first time I heard that we were doing that was actually the Jonas Brothers were going on tour, and one of the leads I&#8217;ve had, it was actually built that theme.</p>\n\n\n\n<p>And I think that might&#8217;ve been the, was that the first one we did? I know they came back. But we built the theme for the Jonas Brothers when they went on tour. And I think there were some others that we&#8217;ve built. We&#8217;ve built Tumblrs for partners, like along with the sites, or things like that. So yeah, we&#8217;ve worked with Tumblr. I don&#8217;t know that we&#8217;ve done anything with Pocket Casts. That&#8217;s what I listen to your podcast on.</p>\n\n\n\n<p>[00:27:01] <strong>Nathan Wrigley:</strong> Okay, yeah. That&#8217;s my podcast player of choice as well.</p>\n\n\n\n<p>[00:27:05] <strong>Mike Straw:</strong> Oh, we built, that&#8217;s right, we did. We built the Pocket Cast Blog. We just recently moved that over.</p>\n\n\n\n<p>[00:27:09] <strong>Nathan Wrigley:</strong> Automattic seems like it&#8217;s on a clip of purchasing things. So in the more recent past, I can think of Beeper and Texts, and maybe they&#8217;re the kind of things that in the future will come under your purview as well. I don&#8217;t know.</p>\n\n\n\n<p>[00:27:18] <strong>Mike Straw:</strong> If there&#8217;s a website, if it&#8217;s an Automattic branded site that belongs to it, we tend to be involved in building those sites, and getting them up and running, or doing a redesign and migration of the site into the Automattic platform.</p>\n\n\n\n<p>I&#8217;ve worked, personally spent some time on akismet.com, jetpack.com, automattic.com, I think I&#8217;ve done a little bit of work there. So like those internal sites, we do work with those. And yeah, I had forgotten, we migrated the Pocket Cast Blog.</p>\n\n\n\n<p>[00:27:45] <strong>Nathan Wrigley:</strong> Nice. Now, I&#8217;m guessing the fact that you&#8217;ve got, both of you, this incredible heritage, and you&#8217;re obviously surrounded by people of an equal caliber. I&#8217;m guessing that the kind of work that you put out means that it has to be of the highest quality. And if somebody was to be thinking, I&#8217;d like to work with that team, you have to have really high expectations here. Nothing can go out the door that isn&#8217;t as good as it possibly can be.</p>\n\n\n\n<p>I don&#8217;t really have a question in there, but I&#8217;m just sort of asking, is that the case? Do you feel that you are doing the best work that you can do with everything that you put out? No corners cut, go the extra mile, do the extra work, that kind of thing. I&#8217;m getting some smiles.</p>\n\n\n\n<p>[00:28:22] <strong>Mike Straw:</strong> That sounds really high stress.</p>\n\n\n\n<p>[00:28:23] <strong>Nathan Wrigley:</strong> Yeah, and I wondered if it was.</p>\n\n\n\n<p>[00:28:25] <strong>Mike Straw:</strong> So there&#8217;s a kind of a philosophy within Automattic of, you&#8217;re allowed to make mistakes. As a matter of fact, I said earlier, I went through an apprenticeship program to become an engineer again, because I&#8217;ve been doing some sort of coding for decades. But it was always smaller projects, and I knew when I came to Automattic, there was no way I could operate at the scale and the level that Automattic operates at.</p>\n\n\n\n<p>So I came in as a support person, and then when they had the opportunity for me to go learn this, and when I started my apprenticeship, I actually, I was going to work on the woocommerce.com website. And as part of my apprenticeship, no pressure there, far as I know, the largest WooCommerce site on the internet, and I said something to my lead. Something about, as long as I don&#8217;t crash the site. And he says, oh no, it&#8217;s not a matter of if you&#8217;re going to crash the site, it&#8217;s when. And I fulfilled that. I only crashed it once, so that was good.</p>\n\n\n\n<p>Yeah, and I&#8217;ve made mistakes on Team 51. I&#8217;ve made some that had some impact. I wish I hadn&#8217;t, but I did. And I learned from it, and will never do that again, and had learned things as I went. It&#8217;s definitely not a, we&#8217;re cavalier, work fast, break things, as some companies operate in. It&#8217;s, we are very careful, but we also acknowledge the fact that we are human beings that are going to make mistakes, especially because we&#8217;re operating at the cutting edge of things.</p>\n\n\n\n<p>A new thing comes in WordPress, or is coming in WordPress, a lot of times we&#8217;ll start implementing it, and using it, and sometimes things don&#8217;t go perfectly. And we have an internal system to make sure that if something does go wrong, we&#8217;re quick to get it fixed, quick to get everything back to working well. But yeah, we do want to give the best. We do all absolutely always give the very best we have to what we&#8217;re doing. We don&#8217;t have an expectation of perfection in that. We have an expectation of, I would say an expectation of excellence, but not of perfection, if that makes sense.</p>\n\n\n\n<p>[00:30:19] <strong>Christy Nyiri:</strong> Well, I have an expectation of perfection in design. I&#8217;d say it&#8217;s like really hard in design to get things to the level that I really want them to be. That mostly comes down to just like the really little, this finessing at the end of the build, the CSS details. That&#8217;s what I love. Like I&#8217;m a huge CSS nerd, and because I&#8217;ve built most sites, like up until working in Automattic, my background is that I would do it myself, and do those afterwards, and it&#8217;s hard for me to kind of like translate that to a developer a lot of the time.</p>\n\n\n\n<p>But other people on my team that are younger, and have better, I guess like development handoff practices, are really good at like translating to a dev. Like, here&#8217;s the animation I want to see, here&#8217;s the details that I want on the site. And the site that Mike mentioned earlier, johanernst.com, so that&#8217;s. J-O-H-A-N-E-R-N-S-T, and I want everyone to see the site because it is, I think, the most perfect example of what we&#8217;ve built. It&#8217;s like a super high caliber, and all the little details on it. And they&#8217;re still even adding more. Like they&#8217;re going to add, on the site there&#8217;s this globe, and then we&#8217;re going to add a connector of the expeditions around the globe, so you can see the kind of like route that he&#8217;s taken. It&#8217;s such a good site, check it out.</p>\n\n\n\n<p>[00:31:34] <strong>Mike Straw:</strong> Going back to the perfection idea, I&#8217;m going to amend a little bit, or with what Christy said, the perfection of the design, and the way the sites look, that is a thing. We try to give them the absolute best site. And I learned that on one website we worked on, that we got the initial site delivered, and then the QA went on for the design QA, and I was one of the people that worked on the couple of hundred issues that they found with the design.</p>\n\n\n\n<p>A lot of it was, this is shaded a little different, this is just a couple of pixels out of alignment when you&#8217;re with this particular, like it was very, very detailed design. Making the site look perfect. Making things absolutely the best it can be. So there is that standard of the site we deliver. I was looking more from an engineering perspective of perfect code is not a thing, and sometimes there is a belief that you have to just do everything perfect, and if you make something go wrong, that&#8217;s just the end of everything. And we don&#8217;t have that mindset. We work very, very, very hard to make sure that doesn&#8217;t happen.</p>\n\n\n\n<p>The presentation I gave yesterday about the safety net plugin we have, comes from that mindset of, we want to never risk doing something that&#8217;s going to impact our partners, or any of our websites in a negative way. WordPress is a very large code base, it&#8217;s not perfect. But our standards for what we deliver very much are very, very detailed.</p>\n\n\n\n<p>[00:33:04] <strong>Nathan Wrigley:</strong> In preparation for this podcast, I actually asked a few Automatticians if they had any idea what your team does.</p>\n\n\n\n<p>[00:33:10] <strong>Christy Nyiri:</strong> Nobody does.</p>\n\n\n\n<p>[00:33:11] <strong>Nathan Wrigley:</strong> Yeah, and not only did they not know, many of them didn&#8217;t know that it was a thing, the Special Projects Team. So I think the cabal like nature of it, it is interesting. There is this perception that, okay, they live in a different warehouse over there, and they&#8217;ve got chemicals boiling in test tubes, and things like that. But it&#8217;s kind of interesting, this podcast, peeling it back a little bit, and just realising sort of more human nature of it.</p>\n\n\n\n<p>[00:33:34] <strong>Mike Straw:</strong> It is kind of that way, but not by design. It just kind of happened that way, because we are so small, and we have such a small thing. So it&#8217;s just not really visible necessarily every day to things that are going on, because we&#8217;re not necessarily putting out product, and things like that.</p>\n\n\n\n<p>So I could see where people, well, again, both of us kind of had that perception before we actually came to the team of this big, mysterious thing. And, no, it&#8217;s just really people that really love doing cool stuff.</p>\n\n\n\n<p>[00:34:01] <strong>Nathan Wrigley:</strong> It sounds like the caliber of work that you&#8217;re doing is of great interest to you both. You seem to enjoy the space that you&#8217;re in. And obviously, the difficulty that comes with that is understood. I will into the show notes put any of the links that we mentioned today, including the, and I&#8217;m going to call it showcase, I don&#8217;t know if that was the right word, of the kind of sites that the team have been building.</p>\n\n\n\n<p>But really fascinating just pulling back the curtain a little bit, and hopefully, off the back of this episode, some people will reach out to wherever they need to reach out to, to see how they can become involved. You never know, you might find some job applications coming through.</p>\n\n\n\n<p>Thank you so much for talking to me today. Honestly, really interesting just pulling back the curtain a little bit on the team that you are involved in, and hopefully making it feel a bit less cabal like, in the process. So, Christy and Mike, thank you so much for chatting to me today. I really appreciate it.</p>\n\n\n\n<p>[00:34:48] <strong>Mike Straw:</strong> Absolutely. Thank you, this has been fun.</p>\n\n\n\n<p>[00:34:49] <strong>Christy Nyiri:</strong> Yeah, thanks so much.</p>\n</div>\n\n\n\n<p>On the podcast today we have <a href=\"https://profiles.wordpress.org/nyiriland/\">Christy Nyiri</a> and <a href=\"https://profiles.wordpress.org/mikestraw/\">Mike Straw</a>.</p>\n\n\n\n<p>Christy leads the design arm of Automattic’s Special Projects Team. She taught herself to design and code 17 years ago and has since worked with a wide range of clients, many of whom you’ll hear about later.</p>\n\n\n\n<p>Mike is an engineer with the Special Projects Team. He’s been writing code for over four decades, and has been deeply into WordPress for the last seven years.</p>\n\n\n\n<p>Today, we&#8217;re pulling back the curtain on the work done at <a href=\"https://specialprojects.automattic.com/\">Automattic’s Special Projects Team</a>, a somewhat mysterious entity within Automattic. Because of its low visibility and its detachment from regular product output, many have never heard of the team or what they produce, but that’s about to change.</p>\n\n\n\n<p>Mike and Christy tell us all about the team. What they do, and who they work with and for. They clarify the unique operational model of the team, which resembles an internal agency, focusing exclusively on WordPress and open-source projects. Their mission isn&#8217;t driven purely by profit; they often support nonprofits and contribute back to the WordPress community.</p>\n\n\n\n<p>We get into the team’s philosophy of learning from mistakes while striving for excellence. From their work with prominent websites, to assisting household names, to more philanthropic work, Mike and Christy illustrate how their work showcases the power and versatility of WordPress. In short, they strive to show the very best that WordPress can produce</p>\n\n\n\n<p>This episode highlights the technical and design prowess of the Special Projects Team, but also captures the passion and dedication of its members.</p>\n\n\n\n<p>Whether you&#8217;re a WordPress developer, a web design enthusiast, or someone interested in the operational intricacies of high-calibre web projects, this episode is for you.</p>\n\n\n\n<h2 class=\"wp-block-heading\">Useful links</h2>\n\n\n\n<p><a href=\"https://specialprojects.automattic.com/\">Automattic Special Projects Team</a></p>\n\n\n\n<p><a href=\"https://www.printmag.com/\">PRINT magazine</a></p>\n\n\n\n<p><a href=\"https://www.endthebacklog.org/\">End The Backlog</a></p>\n\n\n\n<p><a href=\"https://johanernst.com/\">Johan Ernst</a></p>\n\n\n\n<p><a href=\"https://postsecret.com/\">Post Secret</a></p>\n\n\n\n<p><a href=\"https://pocketcasts.com/\">Pocket Casts</a></p>\n\n\n\n<p><a href=\"https://blog.pocketcasts.com/\">Pocket Casts Blog</a></p>\n\n\n\n<p><a href=\"https://www.tumblr.com/\">Tumblr</a></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 16 Oct 2024 14:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:61:\"Do The Woo Community: It’s WooSesh 2024 with Brian Richards\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=86126\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://dothewoo.io/its-woosesh-2024-with-brian-richards/\";s: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:160:\"WooSesh 2024 is a free virtual conference on October 29-30, focusing on exceptional customer experience in WooCommerce, featuring keynotes and community awards.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 16 Oct 2024 12:39:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s: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:26:\"Matt: Those Other Lawsuits\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=128223\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"https://ma.tt/2024/10/other-lawsuits/\";s: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:2707:\"<p>It&#8217;s a heavy day, and I&#8217;m sad to write this. Not sure where to start.</p>\n\n\n\n<p>In 2022, a lawyer recruited two people who took care of my Mom—an assistant and one of her dozen nurses—to resign and demand a million dollars each, or they would publish horrible things about her in a lawsuit. I refused. The lawsuits were filed. Luckily, the accusations are so sick, twisted, and outrageous that they refute themselves. There&#8217;s some weird sex stuff, and also claims that my Mom is racist. I am sad for whatever mind could even imagine such things. </p>\n\n\n\n<p>I won&#8217;t link or quote them because they don&#8217;t deserve that, but the lawsuits have been part of the public record and available to anyone with a web browser since 2022. The lawyer sent them to every major media publication and gossip rag.  You&#8217;re just hearing about them now because any journalist who spent five minutes calling around easily saw how spurious the claims are and didn&#8217;t run with the story. They&#8217;ve been dredged up as part of the smear campaign against me in my battle with Silver Lake and WP Engine.</p>\n\n\n\n<p>My advice for any other founder: As you gain wealth this may happen to you with household staff as well. Never settle. It just creates an incentive for more people to make stuff up. Even if it&#8217;s messy, fight the claims in court as I am doing. It&#8217;s the only way to deter people trying to make a quick buck. These cases are common, and the media is used to them.</p>\n\n\n\n<p>Now for some good news! I&#8217;m happy to report that since these two people left, my Mom has had no errors in her medication (previously, she had to be hospitalized twice and almost died because of medication errors). She&#8217;s back to the weight she was in her 30s and isn&#8217;t in a wheelchair all the time anymore. She&#8217;s just moved into a new home we&#8217;ve been remodeling together for the past 5 years.  She still has 24/7 RNs, but the new nurses have been fantastic and feel like an extension of our family. We&#8217;re looking forward to celebrating the holidays together with my sister, lifelong family friends like the Ornelas family, Mom&#8217;s four dogs, and some of my fifteen godchildren who live in the area.</p>\n\n\n\n<p>I may be wrong or dumb about many other things, but I sincerely believe in the sanctity and beauty of every human life, regardless of any background. We are all God&#8217;s creation. My Mother taught me these values, and I have done my best to uphold them in my life&#8217;s work building open source, WordPress, and Automattic. <a href=\"https://ma.tt/2024/09/charitable-contributions/\">It&#8217;s part of why I give so much back</a>. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Oct 2024 10:30: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: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: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:21:\"Matt: Response to DHH\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"https://ma.tt/?p=128140\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://ma.tt/2024/10/on-dhh/\";s: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:2388:\"<p>I&#8217;ve taken this post down. I&#8217;ve been attacked so much the past few days; the most <a href=\"https://ma.tt/2024/10/other-lawsuits/\">vicious</a>, personal, hateful words poisoned my brain, and the original version of this post was mean. I am so sorry. I shouldn&#8217;t let this stuff get to me, but it clearly did, and I took it out on DHH, who, while I disagree with him on several points, isn&#8217;t the actual villain in this story: <strong>it&#8217;s WP Engine and Silver Lake</strong>.</p>\n\n\n\n<p>A few bullets to his core points:</p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The headline &#8220;Automattic is doing open source dirty&#8221; is not fair.</li>\n\n\n\n<li>Automattic did not work on a deal with WP Engine for 18+ months because of the GPL, or them using &#8220;WP&#8221; in their name, it was because of their abuse of the WordPress and WooCommerce trademarks. Trademarks must be protected, as evidenced by <a href=\"https://rubyonrails.org/trademarks\">Rails trademark policy</a>.</li>\n\n\n\n<li><a href=\"https://automattic.com/2024/09/25/open-source-trademarks-wp-engine/\">Our C&amp;D</a> is about public trademark abuse; <a href=\"https://wpengine.com/wp-content/uploads/2024/09/Cease-and-Desist-Letter-to-Automattic-and-Request-to-Preserve-Documents-Sent.pdf\">theirs</a> is about censorship, and doxxes private messages. They have since filed a <a href=\"https://wpengine.com/wp-content/uploads/2024/10/Complaint-WP-Engine-v-Automattic-et-al.pdf\">kitchen sink lawsuit</a> that embroils all of WordPress.org.</li>\n\n\n\n<li>Updating ACF to <a href=\"https://wordpress.org/support/plugin/advanced-custom-fields/\">Secure Custom Fields in our directory</a> was to provide users of our plugin directory the best, safest, most secure code. It included a security update that still has not been merged by the ACF team.</li>\n\n\n\n<li>We will merge any improvements ACF makes to their GPL code going forward and will also include enhanced functionality in the coming days to provide a secure and free drop-in replacement for ACF. If WP Engine didn&#8217;t want this to happen, they should not have published their code under the GPL or distributed it through WordPress.org&#8217;s directory.</li>\n\n\n\n<li>I think it&#8217;s fantastic when businesses are built on open source, the WordPress ecosystem is at least 10B+ a year; Automattic and WP Engine are less than 5% of that.</li>\n</ul>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Oct 2024 09:30: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: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: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:85:\"Do The Woo Community: A Conversation with Beau Lebens, WooCommerce in 2024 and Beyond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=86017\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://dothewoo.io/a-conversation-with-beau-lebens-woocommerce-in-2024-and-beyond/\";s: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:55954:\"Episode Transcript\n<p><strong>Jonathan:</strong><br />Welcome to another episode of <em>Inside Woo</em>. I&#8217;m your host, Jonathan Wold, and with me today is Beau Lebens, the head of engineering at WooCommerce. How are you, Beau?</p>\n\n\n\n<p><strong>Beau:</strong><br />I&#8217;m doing well, Jonathan. Thanks for having me on.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />It&#8217;s good to have you, and we have a lot to cover inside of WooCommerce. Before we get to that, though, for those who don&#8217;t know, would you mind giving us just a bit of background on yourself? You&#8217;ve been at Automattic for, if I&#8217;m counting right, 15 years now?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, a little like that. Yep. A little over 15 years.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />And WooCommerce, you&#8217;ve been focused on WooCommerce for over five years now at this point, and you&#8217;ve worn a lot of different hats. Can you just give us some context for your work broadly at Automattic and what you&#8217;ve been focused on at Woo for the past five-plus years?</p>\n\n\n\n<p><strong>Beau:</strong><br />Sure thing. Yeah, so as you mentioned, it’s been a little over 15 years with Automattic now. I came on originally as an engineer, just the one engineer person, and worked on a bunch of different parts of Automattic. I originally actually came on working, ironically, not directly on WordPress. The first few things I actually worked on were IntenseDebate and then Gravatar, but then I got deep into WordPress.com. I worked on Jetpack for a number of years and then came over to the Woo team, I guess it was five and a half years ago, and joined originally on what was then the core engineering team, with an eye towards being in this sort of engineering leadership role, helping to steer the future of WooCommerce in the WordPress space as someone who had actually worked in the WordPress world before joining Automattic as well. So, really early on in the WordPress space, and so that&#8217;s sort of always been my forte. And since coming onto Woo, I have really helped, I guess, steer Woo alongside WordPress, which is something I believe we’ll talk about. There’s something we’re still doing, which is having Woo be kind of in lockstep with the evolution of WordPress itself, but then also steering it towards this whole green space as far as the commerce world goes, and what it looks like and what it means to be not just the de facto commerce solution for WordPress, but being a real commerce ecosystem of its own.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />So, you&#8217;ve worn a lot of different hats, and with Automattic broadly—myself as a former Automattician—there&#8217;s a lot of flexibility and freedom that you have to pursue interests. So, you have a lot of autonomy in what you do. I’m a big fan of a wide-ranging experience. I think it makes you better at the work that you do. Are there any particular experiences that stand out to you from your 15 years that have especially helped shape the work, I guess the experience and the approach, that you take to the work that you do now in WooCommerce?</p>\n\n\n\n<p><strong>Beau:</strong><br />Definitely, yeah. So as I mentioned, I sort of was working with WordPress before I even started at Automattic. Originally, I got involved with WordPress—I guess very originally—just because it was an interesting new platform. I was in the web space already and was building websites and doing all sorts of things that WordPress looked interesting for. But then what really got me deep into it was actually attempting a startup with a friend of mine, which, as many startups do, failed miserably. But the premise there was actually leveraging what was, at the time, WordPress MU (which is now a multisite feature that is baked into core), and integrating with bbPress, which is sort of a bulletin board or forum system based on WordPress. So, it was taking those, mashing them together, and then completely changing the front-end experience, so the user didn’t actually know they were using WordPress or bbPress for that matter. So, it was this really customized WordPress-based system.</p>\n\n\n\n<p>And when I look back, that’s actually something that has been a little bit of a thread and feels relevant now, the way that we look at WooCommerce, which is: Yes, this thing is based on WordPress. Yes, it is WordPress-powered. Yes, it brings WordPress’s ability to manipulate and manage content to the forefront, but it’s also something else. And it’s leaning into that—leveraging this operating system, if you like, and customizing it towards a specific experience, in our case commerce, and then doing everything that’s possible with that power that comes under the hood. And so, that’s still something that we’re doing today. We are leveraging all of the power of WordPress’s posts and users and settings management, all of this stuff that comes under the hood, all of that portability and flexibility that allows it to run on any web host, but we’re applying that same approach to commerce.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />I think that’s part of what I’ve always found interesting about WooCommerce in particular, is it’s such a great example of an ecosystem within WordPress. And I think it’s especially so because, for most folks who are using WooCommerce, they have this clear business intention, this clear commercial intention, but the way that they got there can vary quite a bit. They could have started out in WordPress with a blog and suddenly, like, add commerce, and then that sort of takes off. And now you have this commerce business. There are people who came in just for WooCommerce—that was something that we began to see early on in WooCommerce is people coming into the ecosystem for Woo. So, it’s always sat at this unique intersection.</p>\n\n\n\n<p>And I think what I’m interested in hearing first is, you have this evolution of WooCommerce starting out as a plugin that gave you a lot out of the box from the outset and introduced this whole new range of capabilities to WordPress. And already, from your perspective, when did ecosystem thinking first come into WooCommerce? Was that driven by how people began to use it and what they demanded of it? What’s your perspective as an observer first, and then coming into where that thinking about WooCommerce as a plugin evolved into an ecosystem?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, that’s a great question. I want to actually just really quickly touch on that mention of these overlapping ecosystems or communities between WordPress and WooCommerce, because I think that’s the really fascinating one. There’s a couple of different ways you can look at it, and I often look at it—there are two specific ways I tend to look at it. One is, if you try and Venn diagram those worlds, right? WooCommerce has huge overlap with WordPress, obviously, as a product and as a community and an ecosystem, but it’s not 100%. So, to your point, there’s a certain slice of people, whether they’re developers or the merchants themselves, who really aren’t thinking about WordPress much at all. It’s just there, it’s the foundation of WooCommerce, but they’re thinking of it through a sort of WooCommerce-first lens. And so, that may be a merchant who just wants to set up a store…</p>\n\n\n\n<p><strong>Jonathan:</strong><br />…which I think is worth pointing out that that’s pretty unique. In WordPress, oftentimes there’s a lot of ecosystems, sub-ecosystems—forms are good examples—but with WooCommerce, I think you’ll have people who really aren’t thinking about the WordPress part, which is something a lot of people in WordPress, it may not be obvious unless you point it out.</p>\n\n\n\n<p><strong>Beau:</strong><br />Absolutely. Yeah, absolutely. It’s something that, especially if you’re sort of steeped in this WordPress background (which, I’ll be the first to say, I am myself), it’s actually kind of hard to wrap your head around that reality and accept that, no, some of these people, they just heard about WooCommerce, and they heard WooCommerce is how you put a store on the internet. And so, they go looking for that, and that’s what they want. And then, as they unpeel the onion, if you like, they see, oh, there’s this WordPress thing under here as well, and I have access to this whole other, what they think of as a whole other ecosystem of WordPress solutions and flexibility and everything else that comes.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Like, &#8220;Oh, I can have a blog as well, that’s cool.&#8221;</p>\n\n\n\n<p><strong>Beau:</strong><br />Right. &#8220;And I can add complicated forms to it, and I can optimize my SEO,&#8221; all these other things that come along with that WordPress world. They maybe didn’t appreciate that they were getting that out of the box with WooCommerce.</p>\n\n\n\n<p>The other lens that I look at it—so first, you’ve got that Venn diagram world. The other one is this sort of stacked platforms, if you like, where WordPress is very much a platform, it’s a whole ecosystem—it’s WordPress the solution, and then all of the plugins and themes and everything that come with it. WooCommerce is kind of like, oh, add another core platform on top of that, and then another whole ecosystem of WooCommerce-specific solutions. So we refer to them as extensions, but at a code level, they’re really just WordPress plugins that rely on WooCommerce specifically. And there’s a whole other world of them, which is sort of this next layer on this commerce solution, if you like.</p>\n\n\n\n<p>And so, when you think about it as slices rather than a Venn diagram, we have basically everything that you have at</p>\n\n\n\n<p>the WooCommerce level, whether that’s communities or meetups or plugins or any of the solutions that exist for WordPress. We have all of that at the WooCommerce layer as well. And so then, that’s a really interesting way of slicing it out. And then you can look at just what’s happening at the WooCommerce level, but then also how does that interact with the layer below it? So you end up in a pretty complex environment, but it’s a really interesting one to work in.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />So, if you start to take its origins as a plugin, from your perspective, how did we get there? I like the layers idea. What are the things that stand out to you?</p>\n\n\n\n<p><strong>Beau:</strong><br />I actually think early on in WooCommerce’s trajectory, if you like, there was kind of this acknowledgment that you can’t build everything that you need for a commerce solution in a single plugin for WordPress. It’s hard enough to do as a complete standalone, entirely controlled SaaS service. Even in that environment, you can’t build everything that you need to cater to every commerce solution all in one native package. You have to have something of an ecosystem to provide all of the unique solutions that all of these different commerce scenarios require.</p>\n\n\n\n<p>So from day one, I think whether it was fully acknowledged or not, WooCommerce has sort of embraced this idea that it takes an ecosystem to provide all of these solutions. And what we’ve done over the years is really lean into that. And we’ve really said, yeah, that’s core to how WooCommerce works. No matter how much we may or may not build into that core experience, you’re always going to need the flexibility that WordPress and, by extension, WooCommerce provide. You’re always going to need some extra workflow modification, or maybe you need, I don’t know, a specific shipping carrier in a region that’s not very big, whatever it may be. And so the way that we can provide that is that we as Woo—that distinction is there, the company rather than WooCommerce the product—something that’s really important to us is figuring out how to build an excellent experience but retain this flexibility and extensibility so that developers and builders can customize and tailor it.</p>\n\n\n\n<p>And then, I think one of the other big challenges for us is making sure that interoperability is there so that once you start putting together a solution, it still feels like a meaningful, singular commerce experience. And that exists both at that WooCommerce layer and that WordPress layer. And that’s where it gets really interesting, frankly, and challenging. And where I think the direction that WordPress is going (which we can talk about if that’s interesting) is really sort of enabling a level of integration and flexibility that actually is not great at the moment in WordPress. WordPress has some, I think, almost a lack of opinion that has been great for flexibility but has resulted in some experiences that feel a bit disjointed and that aren’t as deeply integrated as they could be.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />I started writing about this concept of ecosystem plugins a number of years back, and WooCommerce was the one that really stood out to me. And when I think about this concept of an ecosystem within WordPress, there were three characteristics that stood out. First, you have to introduce a suite of functionality, which WooCommerce clearly does—a whole new category. You also have to provide an integration layer that can be extended. But the third thing—and I’ve felt from the beginning that WooCommerce, whether inadvertently or not, has done this better than most—is you also need to influence and shape that ecosystem, like taking an active role. Because I think a lot of the ecosystems we have in WordPress, up until more recently, it’s been fairly hands-off. And I think in WooCommerce, there’s a degree, at least from my perspective, to which just the demands of the growing business required active curation. The partnerships team did a lot of work to help shape and influence what came into WooCommerce.</p>\n\n\n\n<p>But from your perspective, through your lens and the roles that you’ve played, and from an engineering perspective, how do you think about the responsibility of WooCommerce the business to shape the ecosystem, especially when it’s so large? There are people who use WooCommerce in so many different ways, and you’re already beginning to allude to the importance of opinions there. But how do you think about that responsibility?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, it’s a tricky one. It can be, as you said, it’s really broad, and so people are doing all sorts of things with WooCommerce, some of which we would never imagine. And so, it’s very difficult to plan for that. We do take backwards compatibility really seriously. Similar to one of the things that is actually sort of fundamental to WordPress’s success over the 20 years that it’s existed, is this commitment to backwards compatibility. What does that look like? What does that mean? And frankly, it’s something that, as engineers and developers, it’s easy to get really annoyed with and wish that we didn’t have to do and just wish that we could move forward, change things, build the new shiny thing, build a new system, whatever. But I think that’s fundamental to WordPress’s success and WooCommerce’s success.</p>\n\n\n\n<p>We do need to break it sometimes—there are some unavoidable situations where maybe it’s a security fix or a specification change, or whatever it might be where we just can’t figure out how to maintain backwards compatibility or, frankly, staying backwards compatible is not in everyone’s best interest, and so we have to move things forward.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Let’s talk about that specifically because I think it’s a really good example of where the tension, especially from an engineering perspective, lies because, at least from my perspective, having worked with many engineers, you can kind of move on. You see better ways to do something. You see, okay, there’s this new set of practices that we want to bring in. This makes a lot of sense. And from an end user’s perspective, oftentimes it just doesn’t matter. And if you look at it, I feel similarly that WordPress’s and WooCommerce’s success is in large part due to the confidence and stability that comes from that. People don’t have to think about it often; it’s just not breaking. Is there an example that stands out to you of where you did the harder work—usually the much harder work—to maintain the backwards compatibility? I think for builders listening to me, this is an important part of success in the WordPress ecosystem, is internalizing why this compatibility, why the work matters. Is there any example that stands out to you?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, I have a huge one, which is very relevant. We can talk about the past version and the future version of it, and that’s HPOS—so high-performance order storage. For anyone who’s not familiar, this is a pretty fundamental change where, historically, WooCommerce had stored all of its order information, so someone places an order on your website, you make a sale, that information was stored in the WP post table, because that was the sort of most flexible place to store that data in a WordPress install, where historically it was somewhat frowned upon to introduce your own custom tables. And so back in the day, WooCommerce was built as a plugin. It was intended to be installed on WordPress, spun up pretty quickly, and you could just go about your way, start taking orders.</p>\n\n\n\n<p>So HPOS was this project to shift all of that data to a custom set of tables, which were optimized for storing large volumes of order data and for processing at high capacity. And the actual engineering work to just do that, if we were just changing WooCommerce core, was done in about two months max. And that’s with even sort of trying to allow for the fact that the way that we did it, the planning process, everything was very different because we were catering to an entire ecosystem. So we did this work, and then it took almost two years before that was actually the default on new WooCommerce installs.</p>\n\n\n\n<p>And that’s because all of the work was really around the ecosystem and adoption and educating other developers and introducing systems to allow different plugins to declare compatibility or incompatibility and how we handle all of those different combinations of things that are or are not compatible. That’s where all the complexity came in. And that, frankly, is all about backwards compatibility, whether that’s at the sort of user level or the code level, it’s handling all of these different scenarios that exist in the WordPress world because you’ve got these different versions of things out there running, and you can’t just update them all at once. We can’t just go tell people, you have to update WordPress, WooCommerce, and every plugin that you’re running to X version and they’re all compatible and then you’re good. And so since we can’t do that, we have to deal with this complexity.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />That’s a great example because I think instinctively it feels to me like it was the right approach to focus on the lowest common denominator of experience, which is the merchant, and also the most important in this case. So, it takes that time, yet if you can make it available to your builders, to the agency ecosystem sooner, then there&#8217;s more winning that can happen. They&#8217;re able to successfully roll this out for their merchants, their clients, your merchants, and you can probably get a productive feedback loop that also gives confidence that makes what you ultimately roll out to everyone more effective. And if I contrast this to other ecosystems, part of the problem is that they don&#8217;t have that first focus. I don&#8217;t remember the details of it, but my sense of what happened with Magento, for instance, was this sort of big cut from one to the next. And from what I recall, there were developers who were</p>\n\n\n\n<p>quite happy about the changes, and probably also the work that they&#8217;d have to be paid for to make the migration successful. But a lot of merchants ended up being disenfranchised and just lost in the process. So, you’ve done a good job, from my perspective, to remain merchant-centric in those decisions. And it sounds like you&#8217;ve recognized the role that your ecosystem can play in supporting that, and you can create a win for them as well in the process.</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, that’s definitely a learning for us. And I think also a challenge and just something that we&#8217;re still getting better at is how to really engage with this developer ecosystem. You mentioned earlier that there are people out there building WooCommerce solutions, and we frankly just don’t even know who most of them are. That’s both the beauty and the struggle of, I think, WordPress itself, but also WooCommerce is that they&#8217;re out there in the world. The code base is available, people can go build them and deploy them anywhere, and they may not interact with us in any way. And so, it can be very difficult for us to communicate with that ecosystem of builders and developers. And it&#8217;s something that actually, I think we haven&#8217;t done as good of a job as we should have in the last few years, but I guess a few years ago, the last year plus, you may have seen we&#8217;re much more active out there in public now. That&#8217;s a really conscious and intentional shift. We really want to engage with developers through GitHub, through our Slack community, through our developer blog. We&#8217;ve been putting a ton of work into tightening up and aggregating all of the, what was disparate documentation for our platform, bringing that all into a single developer hub, and then also leaning into tooling—do we have CLI commands and all of the stuff that we know developers actually prefer to work with. They shouldn’t have to dig through the code to find out how to do something. We should have better documentation for that.</p>\n\n\n\n<p>So that&#8217;s really a foundational thing for us that we&#8217;re investing a lot in. And we really want that feedback loop with community developers who are building on top of WooCommerce or they&#8217;re building solutions for WooCommerce. Frankly, a lot of that has happened without us hearing about it. And so sometimes we get these blowups of feedback where people get frustrated and they say, &#8220;Why aren’t you doing X?&#8221; And we say, &#8220;Oh, we actually hadn&#8217;t heard that that was such a big deal to you.&#8221;</p>\n\n\n\n<p><strong>Jonathan:</strong><br />So, this is one of the things that’s standing out to me in this—some of these problems, these challenges, we&#8217;ll call them challenges—that you&#8217;re experiencing are quite unique to open source. If we contrast this to proprietary platforms, in a proprietary platform, you wouldn&#8217;t have that. Typically, you wouldn’t have that two-year period.</p>\n\n\n\n<p><strong>Beau:</strong><br />You’d just do it.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />You just do it. &#8220;This approach is deprecated as of this year. We&#8217;ve upgraded everything.&#8221;</p>\n\n\n\n<p><strong>Beau:</strong><br />Exactly.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />You take care of it for them. And you also know your constraints, who’s working in your platform more often than not. And if you don’t, you can solve that a lot more readily. I’m curious from your perspective, I guess I&#8217;m not asking about just the benefits of it in this open-source ecosystem. And I think that’s a big part of why it’s grown to where it is. It’s a key factor in all of this. But I guess, how do you think about—you grew up in the WordPress space—how do you think about the impact that the open-source nature has, the benefits, and the trade-offs to WooCommerce? Because you started from a plugin, now you have an entire ecosystem that happens to be open source. It’s quite unique and very commercial in its nature, and there are all these dynamics at play. And yeah, I think it’s worth touching on that because that&#8217;s a single characteristic that has a lot of impact on what you&#8217;re trying to work on.</p>\n\n\n\n<p><strong>Beau:</strong><br />Definitely. Yeah, it’s an interesting and very difficult question to answer because, as you said, it seems like a relatively narrow question…</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Right? &#8220;Oh, it’s just open source.&#8221;</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, it has so many implications. So I do think it is fundamental both to our previous success—I think it is what got us here—and it poses some unique challenges in going forward. There are certain things that, especially in a commerce space, would be much, much easier to do if we controlled the full stack, if all of WooCommerce was hosted in a single environment and we could just deploy updates, or we could optimize certain things. Performance is a favorite topic, which is actually an area that we are investing in more this year. We mentioned HPOS, but there are a ton of different performance characteristics that, when you control the whole system, you can just optimize for the way that system works. Whether it’s, I don’t know, adding an index in a database or optimizing a specific query or whatever it might be—adding a specific caching layer—we don’t even know what people do with most WooCommerce stores. And so, it makes it very, very difficult to optimize the performance profile of something that you don’t know what it is.</p>\n\n\n\n<p>So that sort of thing can be really challenging. But I think what we&#8217;re seeing is, over the years, there’s a certain number of pretty consistent profiles that we see. For example, people use WooCommerce in certain ways, and it’s actually one of the beauties of being housed within Automattic, which has multiple hosting environments, is that we can just go look at real stores and see how they’re going, what they’re doing, what software they’re running, what performance bottlenecks do they ever run into, and then just working directly with them and improving it and then bringing those improvements back to the rest of the platform.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />It’s such a unique challenge. I remember when I worked at WooCommerce, one of the debates at the time was this: how does WooCommerce relate to the hosting ecosystem? And this is such a good example because someone can have really low-cost hosting on WordPress, which is great, and then wake up one day and decide to install WooCommerce and run WooCommerce and start to take orders. All of this can be happening in an environment that was not designed, intended for that, right? And that’s not necessarily going to be apparent to the user.</p>\n\n\n\n<p><strong>Beau:</strong><br />They have a bad experience potentially, and they think, &#8220;Oh, it’s WooCommerce’s fault.&#8221; And I think commerce and content are really interesting when married together, but they’re also almost opposed from a performance perspective, right?</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Caching versus not caching.</p>\n\n\n\n<p><strong>Beau:</strong><br />Exactly.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Right out of the gate.</p>\n\n\n\n<p><strong>Beau:</strong><br />Right out of the gate. The fundamental strategy for content performance is just cache everything, and basically, it’s a static website, and to the moon. And it’s the opposite with commerce—you basically have to not cache everything, or there are definitely caching strategies that you can go down, but you probably can’t just static cache everything. You probably have a very different profile of users coming back to your website. And so, there are just fundamental differences there that really do require us to think about the way that we approach WooCommerce as: it’s on WordPress, but it’s also quite different from WordPress.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />So then, here comes the tension, right? Because from an engineering perspective, and especially if you didn’t come up in the WordPress space—which is part of why I think you’re in such a unique position—if you came from a proprietary ecosystem, the answer would be clear: &#8220;Well, we need to control this.&#8221; &#8220;Let&#8217;s not deal with all these hosts out here. We need to control as much of this as possible.&#8221; And you could argue, I think successfully, that from what’s best for the merchant’s perspective, that’s a fair line of reasoning. Let’s give them a great experience. And hosting is a good example of an open-source variable that can have a big impact. But yet, that’s also a big part of why WooCommerce has grown as much as it has. You have this vast ecosystem. And while it’s much harder, I’ve been really happy to see WooCommerce take an approach over the past couple of years of working with the hosts and figuring out, okay, how do we support that? So how do you think about that? And I think for the merchant in particular, ideally, they wouldn’t even have to care about this, but yet there is real-world impact to that. There’s a lot there, but how do you think about that?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, so I think it’s really interesting that you&#8217;re sort of bringing it from the merchant&#8217;s perspective because we try and do that a lot. Ultimately, even though we know that builders and developers are involved with many WooCommerce deployments, ultimately, it’s a merchant who has to use the product. And so, however we get there, we need to get to a good merchant experience. And frankly, something that we’ve seen over the years is that if you look back originally to the sort of WooCommerce early days, WooThemes days, and then all the way through—frankly, until now—the model for WooCommerce is you get WooCommerce, and then you will definitely add all of these other solutions. You’ll add a payment gateway, a shipping carrier, a tax solution probably, who knows—all sorts of things. Actually, fun fact, I think the number I’ve seen recently is an average Woo store has something like 44 plugins. So you’re talking about a lot of extra stuff.</p>\n\n\n\n<p>And so that was intentional. That was the approach—</p>\n\n\n\n<p>give builders and merchants the flexibility to get this core and then plug in any solution that they need and mix and match to get exactly what they want. And what we’ve seen over the years is, I guess, two things. One, that introduces a level of decision fatigue, discoverability, and complexity that people don’t actually love. No one really wants to manage a bunch of software. So there’s this level of complexity that it introduces. And then, the other one is frankly that the expectations of people on the internet have changed. WooCommerce has been around for over a decade. Things have changed in that time.</p>\n\n\n\n<p>And so, what we are seeing is we actually need, as the platform, as WooCommerce, we actually need to have a little bit stronger of an opinion on what good looks like. And so, you will see us start to shift a little bit more towards, hey, if you don’t have a preference or you don’t have a specific need, you should just use this solution.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Stronger defaults.</p>\n\n\n\n<p><strong>Beau:</strong><br />Right, stronger defaults, which is theoretically something that WordPress has always had—decisions, not options. This has been a mantra forever, and we&#8217;ve usually tried to do that at the technical level, but we haven’t always done it at the sort of product experience level. And you’ll see us do that a little bit more going forward, and that’s directly based on feedback where we’ve just heard, &#8220;Look, there are too many things to manage. There are too many choices to make. I actually don’t want to do this. I just want to be told which ones work together. I want them to work really well. I want them to be integrated. If I’m using a specific payment solution, I want to get comprehensive payment reports, and I want it to perfectly handle my taxes,&#8221; whatever the combination may be.</p>\n\n\n\n<p>And when you&#8217;re mixing and matching from the ground up, that level of interoperability can be pretty tricky to get right. So, you’ll see us do a little bit more of that—saying, &#8220;Hey, these solutions work together.&#8221; We still want to maintain the option—if you don’t want to use that, you’ve still got the flexibility. That’s the beauty of everything being open source and extensible. But if you go that route, then obviously, you&#8217;re taking all of that into your own hands, and now you need to figure out, do they work together as well as they could, which is frankly how things are right now. And that&#8217;s part of the value that builders provide in the equation—putting together a package of solutions and then making sure that they work well together.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />So, you guys just recently launched the business services category, and to me, that was good. I was happy to see that. It was a good example of, at least from an outside perspective, this continued evolution to take in a more holistic view of the things that merchants need. If you&#8217;re a merchant and you&#8217;re having any kind of success, there’s a whole series of additional things you are going to need at some point, right? And yeah, I think I&#8217;d love to hear more from you on anything that stands out to you in that evolution—the impact of thinking more holistically, of thinking about better decisions, not options, of thinking about that end-user experience. How is that affecting what you prioritize in terms of developing new features and introducing new things like the business services category?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, that&#8217;s a great one. So, I guess just to touch on that briefly, for anyone who’s not familiar with it, I guess a few months ago now we introduced the business services tab within our marketplace. And this is basically where you go as a merchant to find sort of WooCommerce-adjacent services. So, the idea is they don’t necessarily need a technology integration; they may not be part of your website or part of your baked-in business workflow, but you need them to run a business. And I think this sort of breaking out of the idea of WooCommerce as just a plugin to, no, for a lot of people, WooCommerce represents their business. It is the hub, how they run their livelihood. And so, what can we do to help them do that? What are all the other pieces that are relevant when running a business, and how do we connect people to those solutions? I think previously, we just relied on, I guess, developers to either do that or for a business owner to engage with a developer and a tax professional or an accountant or whoever, and for them to just figure it out themselves. And if we’re in a world where we’re trying to enable merchants to get up and running and get going, then the more we can do to help them, the better. So, that’s really where that’s coming from.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />I like that a lot. One thing I want to touch on—so I think WooCommerce and WordPress, especially being in Automattic, there’s always been a unique interplay between what’s happening in core WordPress and what’s happening in WooCommerce. I remember WooCommerce was doing early work on blocks, and there was an alignment of interest there, I think because it was at Automattic, that might not have been there otherwise. It was a lot of work to try and figure out how do we do this. And I remember some of the early—at least from my perspective—there was a lot of pioneering work that was done in Woo on improving user interfaces and experiences that also had a positive impact on the work that was happening in core. So, how do you think about the interplay? WooCommerce, to me, is the largest and most impactful sub-ecosystem of WordPress, and that can be something that can be lost at times. How do you think about the relationship between what&#8217;s happening in WooCommerce versus what’s happening in WordPress? How does WooCommerce, from an engineering perspective, think about what&#8217;s happening in the project and where WordPress itself is evolving?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, I think you&#8217;re spot on with the reality that if WooCommerce wasn’t within Automattic, things might be a little different here, and that would impact both WooCommerce and WordPress. The work that you’re referring to, investing early in blocks and thinking about what’s happening in WordPress core, is very much still happening. Actually, a perfect example of that—a couple of examples, actually—the product editor that you&#8217;ve seen us working on, if you&#8217;re watching the sort of things that are feature-flagged and available, if you jump into the right spot, that’s undergone a couple of really major changes, and there’s probably still another one coming, which is part of why we haven’t pushed that out as any sort of default experience for the majority of users. And that’s because it’s evolving alongside what’s happening in WordPress. And frankly, WordPress itself is still figuring out a lot of things related to full-site editing, to data views, to all these new components and new UX patterns and things. And so, we&#8217;re right there with them. We&#8217;re actually working alongside core Gutenberg teams and really bringing to them, &#8220;Hey, we have this complex experience that’s critical for commerce that you haven&#8217;t considered yet. Let’s work together and solve for that.&#8221;</p>\n\n\n\n<p>Actually, a kind of random good example—we’re having a conversation at the moment around, should data views—so these are effectively the replacement for a WP list table—should they support drag-and-drop? On the surface, you&#8217;d say, yeah, absolutely. But there are a lot of scenarios where it breaks. If you&#8217;ve got a sort or a filter applied and you change the order, what happens now? So, there’s a bunch of things like that where the fact that we represent commerce, we represent a lot of really complex user interactions and a certain way of interacting with what is technically WordPress (which WordPress focused purely on content may not be taking into account). And so, what I like to think is that WooCommerce is basically one of the most complex applications of anything that WordPress could come up with. And so, if the WordPress platform can support that, it can support almost anything.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />I like that example a lot, and I think one of the strengths—it’s a double-edged sword—one of the strengths is that interplay of content and commerce that merchants see, right? They love the idea of being able to create content, which is often key to the marketing, the sales side of a commerce business. And it’s easy to take for granted—that&#8217;s not just trivial in these other platforms. They tend to be, &#8220;Okay, this is commerce, and maybe there’s some light content layer.&#8221; So, there&#8217;s a lot of complexity that comes with that because they’re not the same, yet they can have a clear relationship with each other. But the needs in commerce—it’s a different workflow, different expectations, different problem set, the caching versus non-caching. So, it seems like it’s a lot more work to do that and to stay with that.</p>\n\n\n\n<p>As we’re nearing the end, what I&#8217;d love to touch on is—you see that work firsthand, and I think that’s increasingly appreciated for those who&#8217;ve been in the space for a while and been following. It could be frustrating that things don’t happen quickly. At the same time, I think people who are paying attention can also see that care and consideration and thinking long-term is also part of what you&#8217;d want in a steward of the ecosystem. So, for the builders who are listening and they’re looking to the future of WooCommerce, what are some of the things that you would be encouraging builders to be thinking about? Where should they be focusing some of their energy and efforts? Let’s start with the agency folks first. For folks who are building for merchants, they have clients, whether freelancers or agencies, what are some of the things that</p>\n\n\n\n<p>you recommend that they be thinking about in the context of where you see the platform going?</p>\n\n\n\n<p><strong>Beau:</strong><br />Great question. Yeah, so I think we&#8217;ve talked about blocks and the future of WordPress and where WordPress is going. So, I&#8217;d say part of it would be to understand that as much as you can, especially for bigger agencies—I think they tend to be better connected to what is happening with WordPress. So, understand that and be looking at what does this mean for the sites that I&#8217;m building, especially on the backend. So, in the admin experience, things are shifting towards blocks, towards this new WP admin design that is sort of coming slowly down the pike—the full-site editor. So, think about how that all applies to the type of work that you do and look at which solutions you&#8217;re picking. So, which extensions or plugins are you choosing to build new sites on? Especially, are they compatible with this future? I would frankly be really thinking about that at this point. If they’re not and you are not the developer of that solution, start working with that developer to understand how they can make it compatible with that future. Start engaging with us. Like I said before, we really are out there trying to engage more directly with developers and agencies because we want to hear what is happening out there. I think people actually forget that agencies are often—agencies and solo developers—they&#8217;re actually often the front line that’s really understanding the reality of applying software like WordPress or WooCommerce in a way that we frankly may not understand because we are building the software and they&#8217;re applying it in certain scenarios. So, getting that real-world feedback loop of, hey, how are you using it? What problems are you running into? Are there limitations we can remove? Are there things that we&#8217;re not doing that we should be doing, or whatever?</p>\n\n\n\n<p>Really closing that feedback loop with us is the biggest thing. I mentioned earlier, I think we have a community Slack channel—that’s a great spot to start. We have a developer blog, which is at developer.woocommerce.com. There’s a developer-specific newsletter on there now, which I would strongly recommend anyone building for WooCommerce to be on. And then, we&#8217;ve started using GitHub discussions pretty actively as well. So, I&#8217;d suggest jumping in there. You&#8217;ll see RFCs for major changes that we&#8217;re looking at doing—things like that. We need real feedback from people who are frankly outside of that cycle of Gutenberg development (and I use Gutenberg there loosely just to refer to the whole roadmap). But yeah, real-world uses of WooCommerce—we want to hear about them.</p>\n\n\n\n<p>And I guess I would say—this sounds a little &#8220;Matrix-y&#8221;—but open your mind a little bit. We&#8217;ve heard feedback from builders specifically or developers who don’t necessarily want change. They know how to build for the current system, and they want it to stay the same. We need to change to stay up with WordPress. WooCommerce and WordPress are inextricably tied together. That’s not going to change. So, we are going to stay deeply integrated with WordPress. We believe that’s actually the thing that makes us unique in the market and which gives us the strength and flexibility and the reach of WordPress itself. So, we fully intend to stay integrated with WordPress, and that means that the future is going in a certain direction. So, I would encourage everyone to understand that direction and come along with us.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />I like that a lot. The business services category launch, I think, is a good illustration of what I&#8217;m observing in the market, which is a growing interest from products to play in the WooCommerce space. More product companies are coming in, they’re seeing the opportunity, they’re seeing the size of the ecosystem, and that&#8217;s been an important part for a long time now—people building extensions. And you&#8217;re seeing bigger and bigger companies come in. There&#8217;s a full partnerships team at WooCommerce. For the people listening who are building products for the WooCommerce ecosystem, what guidance do you have to offer them? How would you encourage them to be thinking about the evolution of WooCommerce as a platform, as an ecosystem, and what should they be paying attention to?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, that&#8217;s a good one. So, I think, as you said, there are a lot of people trying to enter the WooCommerce market, if you like. And for us, we&#8217;re in this weird spot. We&#8217;ve talked a lot about ecosystem thinking and the community and working with developers and builders, and that is the strength of what we&#8217;re doing. But frankly, if we&#8217;re to remain running as a business, we also need to commercialize certain parts of it. We need to be part of the money that&#8217;s flowing through this ecosystem so that we can continue funding the development of what we&#8217;re doing.</p>\n\n\n\n<p>So, I mentioned there&#8217;s a few sort of central commerce experiences that we&#8217;re investing heavily in. I&#8217;d say off the top-line list of that is payments, shipping, taxes. These are areas that you&#8217;re going to see us invest in heavily, and you&#8217;ve already seen us probably building WooPayments. We also recently relaunched WooCommerce Shipping. So, these are areas that we know that it&#8217;s critical for merchants to have a great experience, and we believe that the best experience is one that’s going to be deeply integrated with WooCommerce. So, there are plenty of other solutions for payments and shipping in particular where it&#8217;s a plugin and then you go use some other dashboard to manage that part of your business. And we fundamentally believe that there is at least a certain audience who want that all in WP admin. They want an integrated experience, they want to be able to bounce between different parts. I mentioned earlier like payments and taxes, let&#8217;s say. You can imagine that actually extending to all three—so, if you&#8217;re taking a payment that includes taxes, that covers shipping, you want to be able to understand all of that in the performance of your business. And if that&#8217;s spread out across multiple systems, that can be really difficult. So, I&#8217;d say we&#8217;ll be investing more heavily in those areas, which is not to say that other people shouldn&#8217;t, but I guess know that we will be playing in those spaces a lot.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />For someone who is coming into the space—you just made that point about the importance of the integrated experience. If they&#8217;re new, how would you encourage them to be thinking about that? For instance, in the business services category, you introduced banking, for instance. And unless your intention is to get into banking (which, who knows?), but it’s—for someone who&#8217;s in the banking space and coming in, how would you be encouraging them to be thinking about things like that? Should it be integrated? There&#8217;s not existing precedent, right? It could be outside the space; they could go to a separate dashboard. How would you think about that example?</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, banking is an interesting one. Obviously, that&#8217;s a really complicated space.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />But also fundamental to commerce.</p>\n\n\n\n<p><strong>Beau:</strong><br />Fundamental to commerce, pretty connected to payments, interestingly. So, it is an area that we&#8217;re sort of touching on. But I would say in general, what we would love to see more of is people who are really thinking about WooCommerce as a whole complex system and how can they build something that&#8217;s part of that complex system rather than, &#8220;I represent banking; I want to just make my banking visible.&#8221; That’s the first step. But actually building it in some sort of integrated way is really where we see things succeed more.</p>\n\n\n\n<p>So, I mentioned that the business services tab is largely for things that really probably won&#8217;t integrate deeply or are somewhat separate or somewhat adjacent to the website itself. There may be some crossover—so actually, banking is maybe a good one. We probably could, and probably will, have more flows and better seamless handoff between your WooCommerce store and whatever that banking solution is. But we&#8217;re probably not going to, for example, replicate your entire banking website and banking experience all within WooCommerce. In business services, just as a specific example, I think is also really interesting for connecting things like developers. And this is an interesting sort of crossover—one of the services you may need as a business is a developer to customize your business website.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Right.</p>\n\n\n\n<p><strong>Beau:</strong><br />So, I think there&#8217;s an interesting crossover there, which we’ve just started exploring—opening up the ability for merchants to get access to various forms of technical support, to use a loose term there, as part of running their business.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Well, I’m excited. There&#8217;s a lot to the ecosystem, and I think this is why you coming on episodes like this is especially helpful from my perspective, to give a broader sense of what&#8217;s going on behind the scenes. And I really appreciate you taking the time to share. We&#8217;ve given folks a lot of things to think about and work with. If someone wants to reach out to you, Beau, what&#8217;s the best way to get in contact?</p>\n\n\n\n<p><strong>Beau:</strong><br />The best way is probably to tweet at me, or I guess &#8220;X&#8221; at me, however you say that now. Yeah, you can get me on there. It’s just @BeauLeins, which I’m sure we can put in the show notes or something for the spelling. Or frankly, you can also just email me: beau@automattic.com.</p>\n\n\n\n<p><strong>Jonathan:</strong><br />Excellent. Beau, thank you for the time. Thank you for the work that you and the team have been doing, and talk to you soon.</p>\n\n\n\n<p><strong>Beau:</strong><br />Yeah, thanks, Jonathan. Appreciate it. Been fun.</p>\n\n\n\n<div class=\"wp-block-group has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\"></div>\n\n\n\n\n<p>In this episode of <strong><em>Inside Woo</em></strong>, host <strong>Jonathan Wold</strong> welcomes <strong>Beau Lebens</strong>, head of engineering at WooCommerce, to discuss the development and future of WooCommerce within the WordPress ecosystem which grew out of his post on Woo, <em><strong>WooCommerce in 2024 and beyond: Roadmap update</strong></em>.</p>\n\n\n\n<p>Beau shares his extensive experience within Automattic and provides insights into the uniqueness of WooCommerce as it evolves from a WordPress plugin to a complete commerce solution with its ecosystem. The conversation covers topics such as the challenges and responsibilities of maintaining backward compatibility, the role of WooCommerce in the broader WordPress evolution, and the strategic alignment with new WordPress technologies like blocks and full site editing. </p>\n\n\n\n<p>Beau highlights ongoing efforts to improve the integration of merchant and agency experiences, focusing on performance optimization and ecosystem collaboration. They also chat about  new additions like the Business Services tab and emphasizes the importance of providing integrated, merchant-centric solutions.</p>\n\n\n\n<p><strong>Takeaways</strong></p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>WooCommerce’s Growth</strong>: WooCommerce started as a simple plugin but has evolved into a robust ecosystem, tightly integrated with WordPress, providing flexibility for both developers and merchants.</li>\n\n\n\n<li><strong>Stronger Defaults for Merchants</strong>: To reduce complexity and decision fatigue for merchants, WooCommerce is focusing on providing stronger defaults, particularly in payments, shipping, and taxes, while still maintaining flexibility for developers.</li>\n\n\n\n<li><strong>Backward Compatibility</strong>: WooCommerce is deeply committed to backward compatibility, even when implementing complex changes like the High-Performance Order Storage (HPOS) project, to ensure stability for merchants and developers.</li>\n\n\n\n<li><strong>Developer Engagement</strong>: WooCommerce is increasingly engaging with its developer community through GitHub, Slack, and blogs, seeking feedback to shape future updates and features.</li>\n\n\n\n<li><strong>Ecosystem Thinking</strong>: WooCommerce embraces ecosystem thinking, encouraging third-party developers to build integrated solutions that work seamlessly within the WooCommerce platform rather than as standalone products.</li>\n\n\n\n<li><strong>Commerce and Content Performance</strong>: One of WooCommerce’s unique challenges is balancing the performance needs of real-time commerce with content-focused caching, requiring continuous optimization.</li>\n\n\n\n<li><strong>Future Investment</strong>: WooCommerce is investing heavily in key areas such as payments, shipping, taxes, and technologies like blocks and full-site editing, aligning with WordPress’s long-term roadmap.</li>\n</ul>\n\n\n\n<p><strong>Links</strong></p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https://x.com/beaulebens\">Beau Lebens on X (Twitter)</a></li>\n\n\n\n<li><a href=\"https://developer.woocommerce.com\">WooCommerce Developer Resources</a></li>\n\n\n\n<li><a href=\"https://github.com/woocommerce/woocommerce/discussions\">WooCommerce on GitHub</a></li>\n\n\n\n<li><a href=\"https://developer.woocommerce.com/2024/07/23/woocommerce-in-2024-and-beyond-roadmap-update/\">WooCommerce in 2024 and beyond: Roadmap update</a></li>\n\n\n\n<li><a href=\"https://developer.woocommerce.com/category/roadmap-insights/\">Roadmap Insights</a></li>\n</ul>\n\n\n\n<p><strong>Chapter Titles with Timestamps</strong></p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>00:00&nbsp;Introduction and Welcome</li>\n\n\n\n<li>00:38&nbsp;Beau Lebens&#8217; Journey at Automattic</li>\n\n\n\n<li>02:38&nbsp;The Evolution of WooCommerce</li>\n\n\n\n<li>05:14&nbsp;WooCommerce as an Ecosystem</li>\n\n\n\n<li>10:18&nbsp;Challenges and Responsibilities in WooCommerce Development</li>\n\n\n\n<li>16:49&nbsp;High Performance Order Storage (HPOS)</li>\n\n\n\n<li>25:00&nbsp;Open Source Dynamics in WooCommerce</li>\n\n\n\n<li>28:16&nbsp;Understanding Performance Bottlenecks</li>\n\n\n\n<li>28:28&nbsp;WooCommerce and Hosting Ecosystem</li>\n\n\n\n<li>29:03&nbsp;Commerce and Content: A Performance Perspective</li>\n\n\n\n<li>30:01&nbsp;Engineering Challenges and Merchant Experience</li>\n\n\n\n<li>31:12&nbsp;WooCommerce&#8217;s Evolution and Stronger Defaults</li>\n\n\n\n<li>34:49&nbsp;Business Services and Holistic Merchant Support</li>\n\n\n\n<li>36:59&nbsp;Interplay Between WooCommerce and WordPress</li>\n\n\n\n<li>41:41&nbsp;Future Directions for WooCommerce Builders</li>\n\n\n\n<li>46:27&nbsp;Guidance for WooCommerce Product Companies</li>\n</ul>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Oct 2024 09:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s: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:57:\"WPTavern: Jetpack 13.9.1 Patches a Critical Security Flaw\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=175212\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/jetpack-13-9-1-patches-a-critical-security-flaw\";s: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:2144:\"<p><a href=\"https://jetpack.com/blog/jetpack-13-9-1-critical-security-update/\">Jetpack 13.9.1</a>, a critical security update, was released yesterday to fix a vulnerability in the Contact Form feature that had been present since 2016. This flaw allowed logged-in users of a site to access forms submitted by visitors.</p>\n\n\n\n<p>The vulnerability was discovered during an internal security audit, prompting the Jetpack team to collaborate with the WordPress.org Security Team to release patches for all versions of Jetpack dating back to 3.9.9.</p>\n\n\n\n<img width=\"2158\" height=\"744\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-33.png\" alt=\"Full list of the 101 different versions of Jetpack released yesterday.\" class=\"wp-image-175217\" />\n\n\n\n<p>The Jetpack team also warned: “We have no evidence that this vulnerability has been exploited in the wild. However, now that the update has been released, it is possible that someone will try to take advantage of this vulnerability.”</p>\n\n\n\n<p>Wordfence team <a href=\"https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/jetpack/jetpack-1391-missing-authorization-to-authenticated-subscriber-sensitive-information-disclosure\">shared</a> that the plugin is “vulnerable to unauthorized access of data due to missing capability checks in the Contact_Form_Endpoint class in various versions version up to, but not including, 13.9.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to read all Jetpack form submissions on the site.”&nbsp;</p>\n\n\n\n<p>The vulnerability has been given a CVSS score of 4.3, and users are advised to update to Jetpack 13.9.1 to secure their websites.&nbsp;</p>\n\n\n\n<p>The Jetpack team reassured users, stating, “We will continue to regularly audit all aspects of our codebase to ensure that your Jetpack site remains safe.”&nbsp;</p>\n\n\n\n<p><strong>Update</strong>: <a href=\"https://wpscan.com/plugin/jetpack/\">WPScan</a> will share the Proof of Concept on November 11, 2024, to give users time to update. The vulnerability was reported by their researcher Marc Montpas. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Oct 2024 04:02: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:7:\"Jyolsna\";s: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:29:\"WPTavern: HeroPress Turns Ten\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=175202\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wptavern.com/heropress-turns-ten\";s: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:2520:\"<p><a href=\"https://heropress.com/\">HeroPress</a>, launched by Topher DeRosia, has <a href=\"https://heropress.com/ten-years-of-heropress/\">turned ten</a>. Born from the idea of amplifying the voices of those who have overcome significant challenges, HeroPress has spent the last decade celebrating the diverse and inspiring journeys of people who have found strength, opportunity, and success through their connection with WordPress.</p>\n\n\n\n<p>At its core, HeroPress is about storytelling. It showcases the personal and professional journeys of individuals from all walks of life, connected by their use of WordPress.</p>\n\n\n\n<p>Back in 2015, HeroPress had hit a snag following failure to<a href=\"https://wptavern.com/heropress-fails-to-attract-backers-cancels-kickstarter-campaign-ahead-of-deadline\"> attract backers</a> but this didn&#8217;t stop Topher. So rather than releasing videos with translations as originally planned, he opted for text-based essays, which are easier and more cost-effective to create, translate, and download over low bandwidth.</p>\n\n\n\n<p><a href=\"https://heropress.com/essays/finding-your-place/\">Andrey “Rarst” Savchenko</a> wrote the first essay for HeroPress, and over time, it has become a beacon of hope for those seeking inspiration.</p>\n\n\n\n<a href=\"https://x.com/hellofromTonya/status/1844835198283743394\"><img width=\"2412\" height=\"1064\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-34.png\" alt=\"\" class=\"wp-image-175222\" /></a>\n\n\n\n<p>The global reach of HeroPress is reflected in the incredible diversity of its contributors: 278 essays have been published in 29 languages from 66 countries, featuring 136 women, 134 men, and 3 non-binary individuals.</p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>HeroPress has been a blessing in my life for ten years now. It has been a deep deep privilege to share the stories of WordPress with the world.&nbsp;</p>\n\n\n\n<p>Topher DeRosia</p>\n</blockquote>\n\n\n\n<p>As HeroPress turns 10, it’s also looking for <a href=\"https://heropress.com/donate/\">financial support</a>. “HeroPress isn’t just a website — it’s a platform that brings hope and connection to the global WordPress community. Your financial support ensures that we can keep sharing these stories, helping to inspire more people through the power of WordPress,” said Topher DeRosia.</p>\n\n\n\n<p>You can also <a href=\"https://heropress.com/contribute/\">share your WordPress story </a>with HeroPress.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Oct 2024 03:55: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:7:\"Jyolsna\";s: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:40:\"WordPress.org blog: WordPress 6.7 Beta 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=17984\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2024/10/wordpress-6-7-beta-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8279:\"<p id=\"block-3cf2f536-f167-464f-a4ba-07f45105e476\">WordPress 6.7 Beta 3 is now ready for testing!</p>\n\n\n\n<p id=\"block-b65e3bf0-0494-4039-a701-f21e505600ad\"><strong>This beta version of the WordPress software is under development</strong>. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it is recommended you evaluate Beta 3 on a test server and site.</p>\n\n\n\n<p id=\"block-e904322b-c488-4166-8312-0b769067b943\">You can test WordPress 6.7 Beta 3 in four ways:</p>\n\n\n\n<table class=\"has-fixed-layout\"><tbody><tr><th>Plugin</th><td>Install and activate the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).</td></tr><tr><th>Direct Download</th><td>Download the <a href=\"https://wordpress.org/wordpress-6.7-beta3.zip\">Beta 3 version (zip)</a> and install it on a WordPress website.</td></tr><tr><th>Command Line</th><td>Use the following <a href=\"https://make.wordpress.org/cli/\">WP-CLI</a> command:<br /><code>wp core update --version=6.7-beta3</code></td></tr><tr><th>WordPress Playground</th><td>Use the <a href=\"https://playground.wordpress.net/#%7B%20%22preferredVersions%22:%20%7B%20%22php%22:%20%228.0%22,%20%22wp%22:%20%22https://playground.wordpress.net/plugin-proxy.php?build-ref=11b364fbffbab28d9127be91ee2d48f6645a6509%22%20%7D,%20%22features%22:%20%7B%20%22networking%22:%20true%20%7D,%20%22steps%22:%20%5B%20%7B%20%22step%22:%20%22login%22,%20%22username%22:%20%22admin%22,%20%22password%22:%20%22password%22%20%7D,%20%7B%20%22step%22:%20%22importFile%22,%20%22file%22:%20%7B%20%22resource%22:%20%22url%22,%20%22url%22:%20%22https://raw.githubusercontent.com/wpaccessibility/a11y-theme-unit-test/master/a11y-theme-unit-test-data.xml%22%20%7D%20%7D,%20%7B%20%22step%22:%20%22importFile%22,%20%22file%22:%20%7B%20%22resource%22:%20%22url%22,%20%22url%22:%20%22https://raw.githubusercontent.com/WordPress/theme-test-data/master/themeunittestdata.wordpress.xml%22%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22query-monitor%22%20%7D,%20%22options%22:%20%7B%20%22activate%22:%20false%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22create-block-theme%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22debug-bar%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22health-check%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22test-reports%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D,%20%7B%20%22step%22:%20%22installPlugin%22,%20%22pluginZipFile%22:%20%7B%20%22resource%22:%20%22wordpress.org/plugins%22,%20%22slug%22:%20%22user-switching%22%20%7D,%20%22progress%22:%20%7B%20%22weight%22:%202%20%7D%20%7D%20%5D%20%7D\">6.7 Beta 3 WordPress Playground instance</a> to test the software directly in your browser without the need for a separate site or setup.&nbsp;</td></tr></tbody></table>\n\n\n\n<p id=\"block-93b754f0-e211-47b7-ac89-349d85c2f02f\">The current target date for the final release of WordPress 6.7 is <strong>November 12, 2024</strong>. Get an overview of the <a href=\"https://make.wordpress.org/core/6-7/\">6.7 release cycle</a>, and check the <a href=\"https://make.wordpress.org/core/\">Make WordPress Core blog</a> for <a href=\"https://make.wordpress.org/core/tag/6-7/\">6.7-related posts</a> in the coming weeks for more information.</p>\n\n\n\n<p id=\"block-7b5d791d-225a-4623-83ee-19a586c7094b\"><strong>Catch up on what&#8217;s new in WordPress 6.7</strong>: Read the <a href=\"https://wordpress.org/news/2024/10/wordpress-6-7-beta-1/\">Beta 1</a> and <a href=\"https://wordpress.org/news/2024/10/wordpress-6-7-beta-2/\">Beta 2</a> announcements for details and highlights.</p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"block-f1abd396-a019-4c9a-bcb8-9ac381a61ca1\">How to test this release</h2>\n\n\n\n<p id=\"block-92dfcab6-d2a8-4753-84ce-8ef7b6dd1e90\">Your help testing the WordPress 6.7 Beta 3 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. <a href=\"https://make.wordpress.org/test/2024/10/01/help-test-wordpress-6-7/\">This detailed guide</a> will walk you through testing features in WordPress 6.7.</p>\n\n\n\n<p id=\"block-6519fad7-59ea-45f1-9b8f-ca14c09c865d\">If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to <a href=\"https://core.trac.wordpress.org/newticket\">WordPress Trac</a> if you are comfortable writing a reproducible bug report. You can also check your issue against a list of <a href=\"https://core.trac.wordpress.org/tickets/major\">known bugs</a>.</p>\n\n\n\n<p id=\"block-4bd66b13-6784-4a4f-bb7a-b4dab8e5fc12\">Curious about testing releases in general? Follow along with the <a href=\"https://make.wordpress.org/test/\">testing initiatives in Make Core</a> and join the <a href=\"https://wordpress.slack.com/messages/core-test/\">#core-test channel</a> on <a href=\"https://wordpress.slack.com/\">Making WordPress Slack</a>.</p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"block-67b6a6c7-a95e-4b27-8946-a66d15105cb7\">Vulnerability bounty doubles during Beta/RC</h2>\n\n\n\n<p id=\"block-16175da3-84c9-45d0-b735-08a9d4453a14\">Between Beta 1, released on October 1, 2024, and the final Release Candidate (RC) scheduled for November 5, 2024, the <a href=\"https://make.wordpress.org/security/2024/02/12/welcoming-2024-with-wordpress-6-5-beta-1/\">monetary reward for reporting new, unreleased security vulnerabilities</a> is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the <a href=\"https://hackerone.com/wordpress\">HackerOne page</a> and in the <a href=\"https://wordpress.org/about/security/\">security white paper</a>.</p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"block-14306771-b240-4e15-948f-7504757bbb61\">Beta 3 updates and highlights</h2>\n\n\n\n<p id=\"block-93917d31-4478-45b5-b71c-1c8a1f49cc65\">WordPress 6.7 Beta 3 contains more than 26 Editor updates and fixes since the Beta 2 release, including 18 tickets for WordPress core.</p>\n\n\n\n<p id=\"block-ffdc1220-c2f5-4c23-982b-60c366c629d1\">Each beta cycle focuses on bug fixes; more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 3 using these links:</p>\n\n\n\n<ul id=\"block-3fcf78c7-bebc-42e1-96f6-8b605ea23aae\" class=\"wp-block-list\">\n<li><a href=\"https://github.com/WordPress/gutenberg/commits/wp/6.7?since=2024-10-09&until=2024-10-14\">GitHub commits for 6.7</a> since October 9, 2024</li>\n\n\n\n<li><a href=\"https://core.trac.wordpress.org/query?status=closed&changetime=10%2F09%2F2024..10%2F14%2F2024&milestone=6.7&col=id&col=milestone&col=owner&col=type&col=priority&order=id\">Closed Trac tickets</a> since October 9, 2024</li>\n</ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"block-c414b25e-802f-4f29-a31c-9e13394a4947\">A Beta 3 haiku</h2>\n\n\n\n<p id=\"block-a0f155a2-19b3-4645-a516-c7ae56541e5f\">Code in motion hums,<br />New features bloom, bugs retreat,<br />6.7 calls.</p>\n\n\n\n<p id=\"block-014ab749-322b-44bd-bf4f-bf5817d90bfd\"><em>Props to <a href=\"https://profiles.wordpress.org/joedolson/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>joedolson</a> and </em><a href=\"https://profiles.wordpress.org/jeffpaul/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>jeffpaul</a><em> for proofreading and review, and haiku from&nbsp;<a href=\"https://wordpress.slack.com/team/U030RHV73\" target=\"_blank\" rel=\"noreferrer noopener\">@colorful-tones</a></em>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Oct 2024 00:30:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"David Baumwald\";s: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:71:\"WordCamp Central: Beyond the Savannah: Join Us at WordCamp Nairobi 2024\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://central.wordcamp.org/?p=8222797\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"https://central.wordcamp.org/news/2024/10/beyond-the-savannah-join-us-at-wordcamp-nairobi-2024/\";s: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:8394:\"<h1 class=\"wp-block-heading\">Introduction</h1>\n\n\n\n<p>Kenya, a land of breathtaking contrasts, is renowned for its abundant wildlife, vibrant cultures, and welcoming smiles. In the heart of this diverse landscape lies Nairobi City, famously known as the Silicon Savannah—home to one of Africa’s most dynamic and engaging WordPress communities. In the midst of all this, WordCamp Nairobi 2024 will be held, marking the 8th annual gathering of WordPress enthusiasts, developers, and innovators in Kenya.</p>\n\n\n\n<p>This November, the Kenyan WordPress community invites you to join us in ‘The City Under the Sun’ as we come together for two days of learning, collaboration, and connection. WordCamp Nairobi 2024 promises to be a celebration of creativity, innovation, and the limitless possibilities of WordPress in Africa and beyond.</p>\n\n\n\n<h1 class=\"wp-block-heading\">The 2024 Theme:</h1>\n\n\n\n<a href=\"https://central.wordcamp.org/files/2024/10/Blog-Image-3.jpg\"><img width=\"1024\" height=\"640\" tabindex=\"0\" src=\"https://central.wordcamp.org/files/2024/10/Blog-Image-3-1024x640.jpg\" alt=\"\" class=\"wp-image-8223263\" /></a>\n\n\n\n<p><strong><em>&#8216;Beyond the Savannah: Connecting the Kenyan WordPress Community to the World&#8217;</em></strong></p>\n\n\n\n<p>Our theme this year, “Beyond the Savannah”, symbolizes our commitment to expanding horizons and exploring WordPress&#8217;s limitless possibilities. We aim to bridge the gap between the Kenyan WordPress community and the international stage, fostering collaboration, knowledge sharing, and growth.</p>\n\n\n\n<p>Just as the Kenyan savanna is a vast and diverse landscape, so too is the world of WordPress. Our theme encourages us to venture beyond our comfort zones and discover new opportunities for growth and innovation.</p>\n\n\n\n<h1 class=\"wp-block-heading\">When Will it Happen and Where?</h1>\n\n\n\n<p>WordCamp Nairobi 2024 will take place on <strong>November 1st and 2nd, 2024</strong> at the <strong>Daystar University, Nairobi Campus Towers</strong>, located in the heart of Nairobi. This venue offers modern facilities and stunning views of the city skyline, providing an inspiring backdrop for two days of learning and networking.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><img src=\"https://s.w.org/images/core/emoji/15.0.3/72x72/1f3db.png\" alt=\"🏛\" class=\"wp-smiley\" /> Exciting News! WordCamp Nairobi 2024 will be at Daystar University, Nairobi Campus! This innovative venue is perfect for networking and learning.<br /><img src=\"https://s.w.org/images/core/emoji/15.0.3/72x72/23f3.png\" alt=\"⏳\" class=\"wp-smiley\" /> Don’t wait! Limited tickets available—secure yours now! <img src=\"https://s.w.org/images/core/emoji/15.0.3/72x72/1f39f.png\" alt=\"🎟\" class=\"wp-smiley\" /><img src=\"https://s.w.org/images/core/emoji/15.0.3/72x72/1f449.png\" alt=\"👉\" class=\"wp-smiley\" /> <a href=\"https://t.co/uCHLG4QqdB\">https://t.co/uCHLG4QqdB</a><a href=\"https://twitter.com/hashtag/WCNBO24?src=hash&ref_src=twsrc%5Etfw\">#WCNBO24</a> <a href=\"https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw\">#WordPress</a>  <a href=\"https://twitter.com/hashtag/DaystarUniversity?src=hash&ref_src=twsrc%5Etfw\">#DaystarUniversity</a> <a href=\"https://t.co/ZxGgTcCagg\">pic.twitter.com/ZxGgTcCagg</a></p>&mdash; WordPress Kenya (@WordPress_Kenya) <a href=\"https://twitter.com/WordPress_Kenya/status/1844730970311631037?ref_src=twsrc%5Etfw\">October 11, 2024</a></blockquote>\n</div>\n\n\n\n<h1 class=\"wp-block-heading\">What to Expect: Speakers and Sessions</h1>\n\n\n\n<p>WordCamp Nairobi 2024 will feature a diverse lineup of local and international speakers, each bringing unique insights and expertise to the event. From experienced developers to creative designers, content creators, and entrepreneurs, our speakers will cover a wide range of topics relevant to the WordPress community.</p>\n\n\n\n<p>You can expect sessions on beginner workshops, advanced development, design and UX talks, business and marketing strategies, case studies, and much more.</p>\n\n\n\n<h1 class=\"wp-block-heading\">Sponsorship Opportunities</h1>\n\n\n\n<p>WordCamp Nairobi 2024 is made possible thanks to the generous support of sponsors. We offer a range of sponsorship opportunities that allow your brand to be part of the event while supporting the local WordPress community. <strong><a href=\"https://nairobi.wordcamp.org/2024/sponsors/call-for-sponsors/\">Become a sponsor today</a></strong> and help us make this event accessible to everyone.</p>\n\n\n\n<h1 class=\"wp-block-heading\">Nairobi Vibes and Accommodation</h1>\n\n\n\n<p>Nairobi, often called the “Green City in the Sun,” is a vibrant fusion of cultures, energy, and modernity. From its rich cultural heritage and diverse people to local cuisines, buzzing nightlife, dynamic art and music scenes, lush nature parks, and bustling shopping hubs, Nairobi offers a unique blend of experiences. As a hub of <strong>tech and innovation</strong>, and with its pleasant year-round weather, Nairobi has something for everyone.</p>\n\n\n\n<p>If you&#8217;re traveling from outside Nairobi, there are several accommodation options near the venue, ranging from budget-friendly hotels to more luxurious stays. We recommend booking early to secure the best rates and proximity to Daystar University. <a href=\"https://nairobi.wordcamp.org/2024/travel/accomodation/\"><strong>Click here for detailed accommodation information</strong></a></p>\n\n\n\n<h1 class=\"wp-block-heading\">Tickets</h1>\n\n\n\n<p>Tickets for WordCamp Nairobi 2024 are now available! We offer <strong>General Admission</strong>, <strong>Microsponsor Support, </strong>and<strong> Student Admission</strong> tickets, ensuring that there’s a suitable option for everyone. All tickets include 2-day access to sessions, workshops, food, drinks, swag, and more. <strong><a href=\"https://nairobi.wordcamp.org/2024/tickets/\">Get your tickets now</a></strong> and join us for an unforgettable experience!</p>\n\n\n\n<h1 class=\"wp-block-heading\">Join Us at WordCamp Nairobi 2024!</h1>\n\n\n\n<p>WordCamp Nairobi 2024 is shaping up to be an unforgettable event filled with learning, collaboration, and exciting opportunities to connect with the WordPress community. Whether you&#8217;re new to WordPress or a seasoned professional, there’s something for everyone. From insightful sessions to hands-on workshops, networking with peers, and celebrating the unique energy of Nairobi, this event promises to be a highlight of the year.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">WordPress lovers, it\'s time! Grab your tickets for <a href=\"https://twitter.com/hashtag/WordCampNairobi2024?src=hash&ref_src=twsrc%5Etfw\">#WordCampNairobi2024</a> NOW! <img src=\"https://s.w.org/images/core/emoji/15.0.3/72x72/1f39f.png\" alt=\"🎟\" class=\"wp-smiley\" /> Don’t miss out on this incredible opportunity!<br />Click to book <img src=\"https://s.w.org/images/core/emoji/15.0.3/72x72/1f449.png\" alt=\"👉\" class=\"wp-smiley\" /><a href=\"https://t.co/O3tFfLDcU2\">https://t.co/O3tFfLDcU2</a><a href=\"https://twitter.com/hashtag/WNBO24?src=hash&ref_src=twsrc%5Etfw\">#WNBO24</a> <a href=\"https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw\">#WordPress</a> <a href=\"https://twitter.com/hashtag/TechEvents?src=hash&ref_src=twsrc%5Etfw\">#TechEvents</a> <a href=\"https://twitter.com/hashtag/NairobiTech?src=hash&ref_src=twsrc%5Etfw\">#NairobiTech</a> <a href=\"https://twitter.com/hashtag/WebDevelopment?src=hash&ref_src=twsrc%5Etfw\">#WebDevelopment</a> <a href=\"https://t.co/GsE5aQFHvl\">pic.twitter.com/GsE5aQFHvl</a></p>&mdash; WordPress Kenya (@WordPress_Kenya) <a href=\"https://twitter.com/WordPress_Kenya/status/1835704120864276554?ref_src=twsrc%5Etfw\">September 16, 2024</a></blockquote>\n</div>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Contact Us: nairobi@wordcamp.org</li>\n\n\n\n<li>Our Website: <a href=\"https://nairobi.wordcamp.org/2024/\">https://nairobi.wordcamp.org/2024/</a></li>\n\n\n\n<li>Tickets Info: <a href=\"https://nairobi.wordcamp.org/2024/tickets/\">https://nairobi.wordcamp.org/2024/tickets/</a>&nbsp;</li>\n\n\n\n<li>Sponsorship Opportunities: <a href=\"https://nairobi.wordcamp.org/2024/sponsors/call-for-sponsors/\">https://nairobi.wordcamp.org/2024/sponsors/call-for-sponsors/</a>&nbsp;</li>\n\n\n\n<li>Join the Talks: #WCN24 #WordCampNairobi #WordPressKenya</li>\n</ul>\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:\"Mon, 14 Oct 2024 19:08:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeremy Kabaya\";s: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:67:\"Do The Woo Community: Team Members Video, During a Call, Off or On?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://dothewoo.io/?post_type=blog&p=86083\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://dothewoo.io/blog/team-members-video-during-a-call-off-or-on/\";s: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:7945:\"<p>As an agency or a service, you are on Zoom, Google Meets, etc. having those calls with your team. Small and large.</p>\n\n\n\n<p>The question is. </p>\n\n\n\n<p>Should there be a rule for video on or off?</p>\n\n\n\n<p>There were a couple of things that prompted this thought with me. One was a podcast episode from <strong>Woo AgencyChat</strong> and another from a post our host Katie Keith shared on X.</p>\n\n\n\n<img width=\"1024\" height=\"526\" tabindex=\"0\" src=\"https://i0.wp.com/dothewoo.io/wp-content/uploads/2024/10/2024-10-13-1.32.45%E2%80%AFPM.png?resize=1024%2C526&ssl=1\" alt=\"\" class=\"wp-image-86086\" />\n\n\n\n<p><a href=\"https://x.com/KatieKeithBarn2/status/1844018227736625500\">You can see all the replies and the conversation here. </a></p>\n\n\n\n<p>Here is a summary of those responses.</p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Mixed rules depending on context:</strong> Some companies have expectations for cameras to be on during scheduled meetings but allow flexibility for unscheduled or informal calls. For example, some prefer cameras on for important discussions, but may allow them off in situations like unscheduled meetings or when someone is not prepared.</li>\n\n\n\n<li><strong>Cultural expectations:</strong> Many teams don&#8217;t have strict rules but generally encourage cameras to be on. Some teams naturally default to cameras on because it&#8217;s become part of the company culture, while others leave it to individual preference.</li>\n\n\n\n<li><strong>Flexibility is key:</strong> Several respondents suggest a &#8220;soft rule&#8221; where cameras are encouraged but exceptions are understood (e.g., someone is unwell, internet issues, or self-consciousness). Some also suggested having cameras on at the start to ensure attention but allowing them off later.</li>\n\n\n\n<li><strong>Cameras for communication:</strong> Many argue that having the camera on improves communication, trust, and engagement by allowing facial cues to be seen, though some disagree and suggest that it’s not always necessary for effective communication.</li>\n\n\n\n<li><strong>Empathy and personal boundaries:</strong> Some responses highlight the importance of understanding personal preferences and comfort levels. Leaders are advised to meet people where they are and not force cameras on, which could create pressure or anxiety.</li>\n\n\n\n<li><strong>Job context matters:</strong> For specific situations like interviews or client-facing calls, many agree that cameras should be on. However, for internal team meetings, it&#8217;s seen as less critical unless it helps foster better engagement.</li>\n\n\n\n<li><strong>Respect and engagement:</strong> There’s a sentiment that having the camera on is a way of showing respect to the team and being fully present in meetings, as it helps with connection and understanding.</li>\n\n\n\n<li><strong>Other considerations:</strong> Some suggested improving audio quality or offering a compromise like sharing a headshot if the camera is off. Others mentioned that if cameras are optional, it can create misunderstandings, and there should be clarity on expectations.</li>\n</ol>\n\n\n\n<div class=\"wp-block-group has-border-color has-light-gray-background-color has-background has-small-font-size has-global-padding is-layout-constrained wp-container-core-group-is-layout-5 wp-block-group-is-layout-constrained\">\n<p class=\"has-secondary-color has-text-color has-link-color wp-elements-f0a1ab971f9dce87252b162a11a595d4\">Thanks to our sponsor&#8230;</p>\n\n\n\n<div class=\"wp-block-group is-vertical is-layout-flex wp-container-core-group-is-layout-4 wp-block-group-is-layout-flex\">\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-1 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<div class=\"wp-block-group is-nowrap is-layout-flex wp-container-core-group-is-layout-3 wp-block-group-is-layout-flex\">\n<div class=\"wp-block-group has-base-background-color has-background wp-container-content-1 has-global-padding is-content-justification-left is-layout-constrained wp-container-core-group-is-layout-2 wp-block-group-is-layout-constrained\">\n<img width=\"600\" height=\"600\" tabindex=\"0\" src=\"https://i0.wp.com/dothewoo.io/wp-content/uploads/2022/10/GoDaddy-square.png?resize=600%2C600&ssl=1\" alt=\"GoDaddy\" class=\"wp-image-75131\" />\n</div>\n</div>\n</div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<p class=\"wp-container-content-2\"> <strong><a href=\"https://godaddy.com\">GoDaddy</a></strong>: Build your clients sites using the flexibility of a <strong>Managed WooCommerce Store from GoDaddy</strong>. If you clients are looking to expand their store, you can deliver them a fully-customized WooCommerce site.</p>\n</div>\n</div>\n</div>\n</div>\n\n\n\n<h3 class=\"wp-block-heading\">And then there are cases like this. </h3>\n\n\n\n<p>He had&nbsp;<strong>Joe Riviello, founder of Zen Agency</strong> on Woo AgencyChat. He is also a cardiovascular perfusionist while running his agency.</p>\n\n\n\n<p>Joe talked about a very interesting situation around the case of, video off or on.</p>\n\n\n\n<p>&#8220;The majority of my staff, our leadership, is very experienced. I try to vet everyone who comes through the door, all of our staff, and I try to hire people who have many years of experience&#8230;. About two weeks ago, we hired a gentleman—I won’t say any names—who was really an experienced SEO. He wasn’t really in the whole e-commerce realm but was an experienced SEO. That’s a portion that we’re really trying to build out in our agency. We see good opportunities there, especially utilizing AI in that space. </p>\n\n\n\n<p>So anyway, we hired this guy. I vetted him, I hired him, and he started last week. Everything seemed to be going great. I was on vacation last week, so I didn’t really get any face-to-face time with him, but this week I did. I had face-to-face time with him yesterday, along with the rest of my marketing team. We had a group meeting, and his face wasn’t on the Google Meet, though it normally was when I was interviewing him and discussing the role. Anyway, I could tell something was not right; I could just tell. As we were in the meeting, I went into my G Suite, and I looked up his IP address and saw an IP address from the Philippines.</p>\n\n\n\n<p>So that raised a red flag. I asked him to show his face, and he wouldn’t show his face. He said he had to restart his computer. So I said, “Well, you know what? Instead of showing your face, just tell me your birthday,” because I knew his birthday from a background check that we ran on him. He couldn’t say his birthday. He just dropped off. </p>\n\n\n\n<p>So immediately at that moment, I picked up my phone and called this guy, and he answered the phone while he was in the meeting with me. “Hey Joe, how’s it going?” So I knew something was up, and I would not stop, man. I just kept grinding, trying to get it out of him. It turns out he was working a couple of different jobs in the same role, but who knows if it was even him doing the work or not. </p>\n\n\n\n<p>I know one of his previous employers— it definitely was not him doing the work because I phoned them, and now apparently he no longer has a job there either.&#8221; So again, I’m not going to mention any names, but that was an interesting day yesterday and part of my morning today.&#8221;</p>\n\n\n\n<h3 class=\"wp-block-heading\">A unique case but&#8230;</h3>\n\n\n\n<p>Now I admit this is not typical, and also this was a recent hire. But still, one can have definitive ideas of video camera etiquette, and you still need to be prepared for those unusual moments. Also, a great lesson learning in hiring remotely.</p>\n\n\n\n<p>You can read the transcript or listen to the full episode, <strong><a href=\"https://dothewoo.io/balancing-careers-and-agency-evolution-with-joe-riviello/\">Balancing Careers and Agency Evolution with Joe Riviello</a></strong></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 14 Oct 2024 11:52:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s: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:63:\"WPTavern: State of Enterprise WordPress 2024 Survey is Now Open\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=175111\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/state-of-enterprise-wordpress-2024-survey-is-now-open\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2103:\"<p>The 2024 <a href=\"https://soewp.com/\">State of Enterprise WordPress Survey</a> is now open. This marks the second year Big Bite, a UK-based enterprise WordPress agency, is conducting this survey.</p>\n\n\n\n<p>Last year, over 100 prominent organizations using WordPress, including Macy’s, New Statesman Media Group, and The Times, participated. The <a href=\"https://soewp.com/2023-report/\">2023 report</a> highlighted how enterprises monetize their websites, with 9 out of 10 respondents planning to continue using WordPress due to high satisfaction. Additionally, nearly three-quarters of the brands surveyed rated the return on investment from their WordPress sites as good or excellent.</p>\n\n\n\n<p>This year’s survey aims to build on these insights by gathering more data on usage patterns, customization trends, budget allocations, and the challenges enterprise brands face with WordPress. The survey takes about 6 minutes to complete and covers topics such as enterprise profiles, WordPress usage and selection, costs, maintenance, and future plans of enterprises.</p>\n\n\n\n<p>Iain McPherson, CEO of Big Bite, commented: “The findings from the 2023 survey paint a very positive picture of enterprise WordPress, with almost three quarters of respondents stating that they’d be very likely to recommend the platform to other large-scale organizations. This signals that we’ll see even more major brands adopting WordPress in the coming months and years, however it’s crucial that we don’t rest on our laurels.&#8221;</p>\n\n\n\n<p>He continued, &#8221; By releasing State of Enterprise WordPress as an annual report, we want to create an ongoing dialogue with as many enterprise users as possible, ensuring that the wider WordPress ecosystem can continue to evolve and meet the needs of large-scale brands.”</p>\n\n\n\n<p>Enterprise organizations using WordPress or those with an enterprise-level solution are invited to <a href=\"https://bigbitesurveys.typeform.com/soewp2024\">take the survey</a> and share their experiences through the end of October. All responses will remain confidential.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 14 Oct 2024 04:35:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Jyolsna\";s: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:64:\"WPTavern: ACF Plugin Forked to ‘Secure Custom Fields’ 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=175027\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wptavern.com/acf-plugin-forked-to-secure-custom-fields-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:13647:\"<p>Yesterday, WordPress co-founder Matt Mullenweg <a href=\"https://wordpress.org/news/2024/10/secure-custom-fields/\">announced</a> the forking of the Advanced Custom Fields (ACF) plugin into a new plugin called <a href=\"https://wordpress.org/plugins/advanced-custom-fields/\">Secure Custom Fields</a>.</p>\n\n\n\n<p>In the announcement, he stated: “On behalf of the <a href=\"https://wordpress.org/about/security/\">WordPress security team</a>, I am announcing that we are invoking <a href=\"https://github.com/wordpress/wporg-plugin-guidelines/blob/trunk/guideline-18.md\">point 18 of the plugin directory guidelines</a> and are forking Advanced Custom Fields (ACF) into a new plugin, Secure Custom Fields. <strong>SCF has been updated to remove commercial upsells and fix a security problem</strong>.”</p>\n\n\n\n<a href=\"https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#18-we-reserve-the-right-to-maintain-the-plugin-directory-to-the-best-of-our-ability\"><img width=\"2104\" height=\"1526\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-30.png\" alt=\"Point 18 of Plugin Directory Guidelines \" class=\"wp-image-175066\" /></a>Point 18 of Plugin Directory Guidelines \n\n\n\n<p>The post went on to explain, “<strong>This update is as minimal as possible to fix the security issue. </strong>Going forward, Secure Custom Fields is now a <strong>non-commercial plugin</strong>, and if any developers want to get involved in maintaining and improving it, please get in touch. Similar situations have happened before, but not at this scale. This is a rare and unusual situation brought on by WP Engine’s legal attacks, we do not anticipate this happening for other plugins.”</p>\n\n\n\n<img width=\"2110\" height=\"1448\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-25.png\" alt=\"SCF Plugin Changelog\" class=\"wp-image-175053\" />SCF Plugin Changelog\n\n\n\n<a href=\"https://x.com/WordPress/status/1845180875798884632\"><img width=\"2110\" height=\"798\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-29.png\" alt=\"\" class=\"wp-image-175060\" /></a>\n\n\n\n<p>The ACF plugin is popular among web developers for its capabilities in customizing edit screens and managing custom field data. However, it has become <a href=\"https://wptavern.com/impact-of-wpengines-ban-on-acf-plugin\">embroiled in a dispute between Automattic and WP Engine</a>, its owner. Following <a href=\"https://wptavern.com/wp-engine-banned-from-using-wordpress-org-resources\">WP Engine&#8217;s ban</a>, the ACF team was <a href=\"https://x.com/wp_acf/status/1841843084700598355\">blocked</a> from accessing WordPress dot org on October 03, 2024.</p>\n\n\n\n<p>Next, Automattic tweeted about a vulnerability in the plugin. The tweet was later deleted. In response, the ACF team released <a href=\"https://www.advancedcustomfields.com/blog/acf-6-3-8-security-release/\">ACF 6.3.8</a>, a routine security release stating, “WP Engine remains blocked from accessing our plugins on the .org plugin repository and therefore this update has been shipped to WP Engine’s repository and to the ACF website.”, they said.</p>\n\n\n\n<p>The ACF team also provided a copy of this update to the WordPress.org Security team, which posted it to the plugin repository.</p>\n\n\n\n<p>On October 9, a <a href=\"https://wptavern.com/wordpress-org-login-gets-mandatory-affiliation-checkbox-following-wp-engine-dispute\">mandatory affiliation checkbox</a> was added to the WordPress.org login. Users could access their accounts only after confirming, “I am not affiliated with WP Engine in any way, financially or otherwise.”</p>\n\n\n\n<h3 class=\"wp-block-heading\">WP Engine Reacts</h3>\n\n\n\n<p>WP Engine <a href=\"https://x.com/wp_acf/status/1845169499064107049\">tweeted</a>: “We have been made aware that the Advanced Custom Fields plugin on the WordPress directory has been taken over by WordPress dot org. A plugin under active development has never been unilaterally and forcibly taken away from its creator without consent in the 21 year history of WordPress&#8230; This essential community promise has been violated, and we ask everyone to consider the ethics of such an action, and the new precedent that has been set.”  </p>\n\n\n\n<p>They <a href=\"https://x.com/wp_acf/status/1845247349276148208\">added</a>: “We were saddened and appalled by Matt Mullenweg’s actions this morning appropriating the Advanced Custom Fields plugin that our ACF team has been actively developing for the WordPress community since 2011.”</p>\n\n\n\n<p>In response, WordPress.org <a href=\"https://x.com/WordPress/status/1845179941727690824\">noted</a> that this is not the first occurrence of such an incident: ”This has happened several times before, and in line with the <a href=\"https://github.com/wordpress/wporg-plugin-guidelines/blob/trunk/guideline-18.md\">guidelines you agreed to by being in the directory</a>. Best of luck with your version. We&#8217;re looking forward to making ours amazing for our users, using the best GPL code available.” </p>\n\n\n\n<p>In a <a href=\"https://www.advancedcustomfields.com/blog/acf-plugin-no-longer-available-on-wordpress-org/\">blog post</a> on the ACF website, the team shared, “The change to our published distribution, and under our ‘slug’ which uniquely identifies the ACF plugin and code that our users trust in the WordPress.org plugin repository, is inconsistent with open source values and principles.&nbsp; The change made by Mullenweg is maliciously being used to update millions of existing installations of ACF with code that is unapproved and untrusted by the Advanced Custom Fields team.”</p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>Advanced Custom Fields is a sophisticated plugin with over 200,000 lines of code, which we continually develop, enhance, support and invest in to meet the needs of our users across WordPress.  We’ve made 15+ releases over the past two years, since joining WP Engine, and added significant new functionality to the free plugin as well as continually improving performance and our security and testing practices to meet the ‘enterprise grade’ that our users deserve.”</p>\n\n\n\n<p>Iain Poulson</p>\n</blockquote>\n\n\n\n<p>The post concludes, “Mullenweg’s actions are extraordinarily concerning and pose the grave risk of upending and irreparably harming the entire WordPress ecosystem.&nbsp; His attempt to unilaterally take control of this open platform that we and so many other plugin developers and contributors have relied on, in the spirit of sharing plugins for all, provides further evidence of his serious abuse of trust, manifold conflicts of interest, and breach of the promises of openness and integrity in the community.”</p>\n\n\n\n<h3 class=\"wp-block-heading\">Impact of the Fork&nbsp;</h3>\n\n\n\n<p>This development does not affect WP Engine, Flywheel hosting, or ACF PRO customers. Free plugin users can choose to install <a href=\"https://wordpress.org/plugins/advanced-custom-fields/\">Secure Custom Fields from the plugin directory</a> or the ACF 6.3.8 version from <a href=\"https://www.advancedcustomfields.com/blog/installing-and-upgrading-to-the-latest-version-of-acf/\">advancedcustomfields.com</a>. For sites with auto-updates enabled through WordPress.org, the update will automatically transition them from Advanced Custom Fields to Secure Custom Fields.</p>\n\n\n\n<p>The WordPress community is no stranger to forking; for instance, WordPress itself was forked from the b2/cafelog project, and ClassicPress was forked in response to the introduction of Gutenberg. However, the forking of the ACF plugin has sent shockwaves through the community, raising ethical questions about the decision.</p>\n\n\n\n<p>Interestingly, the Securecustomfields.com domain currently redirects to the ACF website, as highlighted by <a href=\"https://x.com/kellie/status/1845232004750770636\">Kellie Peterson</a> on X.</p>\n\n\n\n<p>The community has expressed their support and criticisms about this forking.  The previous reviews of the ACF plugin are still visible under the <a href=\"https://wordpress.org/plugins/advanced-custom-fields/\">Secure Custom Fields</a> plugin. Following the announcement, several members posted both positive and negative reviews about the plugin in the repository while others took to X.</p>\n\n\n\n<a href=\"https://wordpress.org/plugins/advanced-custom-fields/#reviews\"><img width=\"500\" height=\"369\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-20-500x369.png\" alt=\"\" class=\"wp-image-175044\" /></a>SCF Reviews from Plugin Repository\n\n\n\n<p>Colin Stewart <a href=\"https://x.com/cost_dev/status/1845213012954591601\">tweeted</a>: “In light of today&#8217;s news, since I mentioned in my previous post that I&#8217;m a member of the WordPress Security Team before anyone asks me: No, I was not aware.” Justin Sainton also <a href=\"https://x.com/JS_Zao/status/1845245386862268521\">tweeted </a>along the same lines: “I do not love it. (Speaking independently, as a member of the Plugin Review Team)”</p>\n\n\n\n<p>Several people also pointed out that ACF&#8217;s logos are still there in the new plugin, while WP Engine logos are still in the assets folder, while others referred to the post published by the Plugin Review Team <a href=\"https://make.wordpress.org/plugins/2021/02/16/reminder-forked-premium-plugins-are-not-permitted/\">Forked Premium Plugins Are Not Permitted</a>.</p>\n\n\n\n<a href=\"https://x.com/richardhyland/status/1845216757352468777\"><img width=\"2890\" height=\"978\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-21.png\" alt=\"\" class=\"wp-image-175046\" /></a>\n\n\n\n<a href=\"https://x.com/BFTrick/status/1845172736785850698\"><img width=\"2888\" height=\"1028\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-22.png\" alt=\"\" class=\"wp-image-175049\" /></a>\n\n\n\n<a href=\"https://x.com/techandtrading/status/1845467669727736099\"><img width=\"1816\" height=\"586\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-31.png\" alt=\"\" class=\"wp-image-175071\" /></a>\n\n\n\n<a href=\"https://x.com/DanielW_Kiwi/status/1845299674665865524\"><img width=\"2926\" height=\"1082\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-24.png\" alt=\"\" class=\"wp-image-175051\" /></a>\n\n\n\n<a href=\"https://x.com/interesting_op/status/1845187104516489466\"><img width=\"2114\" height=\"770\" tabindex=\"0\" src=\"https://wptavern.com/wp-content/uploads/2024/10/image-28.png\" alt=\"\" class=\"wp-image-175058\" /></a>\n\n\n\n<p>The creator of Ruby on Rails, David Heinemeier Hansson, published <a href=\"https://world.hey.com/dhh/open-source-royalty-and-mad-kings-a8f79d16\">Open source royalty and mad kings</a>. WP And Legal Stuff published <a href=\"https://wpandlegalstuff.com/the-acfscf-fork-and-legal-risk/\">ACF>SCF ‘fork’ and legal risk</a>. </p>\n\n\n\n<p>Tim Nash, a WordPress security consultant, has published an <a href=\"https://timnash.co.uk/advisory-advanced-custom-fields-changes/\">advisory about the ACF changes</a>, while James Giroux published <a href=\"https://jamesgiroux.ca/acf-gets-a-fork-by-wordpress-org/\">ACF Gets A Fork By WordPress.org</a> where he says “While emotions are high, this move highlights the importance of maintaining the security and integrity of WordPress’s ecosystem. Forking under the GPL is not unprecedented, and this action reinforces the need for WP Engine/Silver Lake to negotiate in good faith.”</p>\n\n\n\n<h3 class=\"wp-block-heading\">Other Forks</h3>\n\n\n\n<p>In a blog post titled <a href=\"https://wordpress.org/news/2024/10/spoon/\">Forking is Beautiful</a>, Matt mentioned two recent WordPress fork attempts &#8211; <strong>FreeWP &amp; AspirePress</strong>. </p>\n\n\n\n<p>About Vinny Green&#8217;s <a href=\"https://freewp.com/\">FreeWP</a>, Matt said: &#8220;We strongly encourage anyone who disagrees with the direction WordPress is headed in to join up with Vinny and create an amazing fork of WordPress. Viva FreeWP!&#8221;</p>\n\n\n\n<p>In response, Vinny took to <a href=\"https://x.com/vinnysgreen/status/1844488053060141233\">X to clarify</a>: &#8220;I love how I never said I was going to fork the project and only wanted to support those who did. Matt is incredible at only hearing the things he wants to hear. Thanks for the free promotion, I guess. We in the biz called that earned media.&#8221;</p>\n\n\n\n<p>The <a href=\"https://freewp.com/faq/\">FAQ section</a> in the FreeWP website has more details about the project: &#8220;To the best of our knowledge, it is a website that starts with “freewp” and ends with “.com”. Any further details are at the discretion of the individual who manages it.&#8221; </p>\n\n\n\n<p>&#8220;What’s FreeWP then? Besides a more pleasant depiction of the domain? Its burgeoning project that is dedicated to the following mission: Coming soon. And not a fork.&#8221; </p>\n\n\n\n<p>So you guessed its status! But you can sign up now to get updates. </p>\n\n\n\n<p><a href=\"https://aspirepress.org/\">AspirePress</a>, on the other hand, is a loosely collected group of volunteers that offer their support to the WordPress platform and it &#8220;exists to be a community of individuals focused on helping WordPress become the platform we all aspire for it to be.&#8221;</p>\n\n\n\n<p>They are building a <a href=\"https://aspirepress.org/a-vision-for-aspirepress-and-a-community-run-org-mirror/\">mirror of WP .org</a> and <a href=\"https://x.com/AspirePressOrg/status/1845280032228331818\">tweeted</a>: &#8220;In case we have&#8217;t been crystal clear, we <strong>have not</strong> forked WordPress. Rumors to the contrary are exaggerations.&#8221;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0