diff --git a/composer.json b/composer.json index ae181279..3fba9507 100644 --- a/composer.json +++ b/composer.json @@ -22,7 +22,10 @@ } ], "config": { - "preferred-install": "dist" + "preferred-install": "dist", + "allow-plugins": { + "dealerdirect/phpcodesniffer-composer-installer": true + } }, "autoload": { "psr-4": { diff --git a/composer.lock b/composer.lock index be7489f6..60a30f37 100644 --- a/composer.lock +++ b/composer.lock @@ -115,16 +115,16 @@ }, { "name": "publishpress/wordpress-banners", - "version": "v1.2.7", + "version": "v1.2.8", "source": { "type": "git", "url": "https://github.com/publishpress/wordpress-banners.git", - "reference": "fbc31f612468db297f57f38f20f3e8749b1894f9" + "reference": "79a02716f89b93daec5b2dc0e8c1bc4d1cf9967c" }, "dist": { "type": "zip", - "url": "https://api.github.com/repos/publishpress/wordpress-banners/zipball/fbc31f612468db297f57f38f20f3e8749b1894f9", - "reference": "fbc31f612468db297f57f38f20f3e8749b1894f9", + "url": "https://api.github.com/repos/publishpress/wordpress-banners/zipball/79a02716f89b93daec5b2dc0e8c1bc4d1cf9967c", + "reference": "79a02716f89b93daec5b2dc0e8c1bc4d1cf9967c", "shasum": "" }, "require": { @@ -150,9 +150,9 @@ "homepage": "http://publishpress.com/", "support": { "issues": "https://github.com/publishpress/wordpress-banners/issues", - "source": "https://github.com/publishpress/wordpress-banners/tree/v1.2.7" + "source": "https://github.com/publishpress/wordpress-banners/tree/v1.2.8" }, - "time": "2022-03-17T00:55:57+00:00" + "time": "2022-03-18T14:49:29+00:00" }, { "name": "publishpress/wordpress-reviews", @@ -4092,9 +4092,6 @@ "illuminate/support": ">=4.0.0", "php": ">=5.3.0" }, - "replace": { - "mikemclin/laravel-wp-password": "self.version" - }, "require-dev": { "mockery/mockery": "~0.9", "phpunit/phpunit": "~4.0", @@ -9562,5 +9559,5 @@ "php": ">=5.6.20" }, "platform-dev": [], - "plugin-api-version": "2.1.0" + "plugin-api-version": "2.2.0" } diff --git a/defines.php b/defines.php index 8d1bcba2..2b9574a2 100644 --- a/defines.php +++ b/defines.php @@ -12,7 +12,7 @@ defined('ABSPATH') or die('No direct script access allowed.'); if (!defined('PP_AUTHORS_VERSION')) { - define('PP_AUTHORS_VERSION', '3.15.1'); + define('PP_AUTHORS_VERSION', '3.16.0'); define('PP_AUTHORS_FILE', 'publishpress-authors/publishpress-authors.php'); define('PP_AUTHORS_BASE_PATH', plugin_dir_path(__DIR__ . '/publishpress-authors.php')); define('PP_AUTHORS_MODULES_PATH', PP_AUTHORS_BASE_PATH . 'src/modules/'); diff --git a/languages/publishpress-authors-it_IT.mo b/languages/publishpress-authors-it_IT.mo index d91aaa18..8026ffa4 100644 Binary files a/languages/publishpress-authors-it_IT.mo and b/languages/publishpress-authors-it_IT.mo differ diff --git a/languages/publishpress-authors-it_IT.po b/languages/publishpress-authors-it_IT.po index a3febeef..7704095b 100644 --- a/languages/publishpress-authors-it_IT.po +++ b/languages/publishpress-authors-it_IT.po @@ -1,750 +1,774 @@ -# Translation of Plugins - PublishPress Authors: Show Multiple Authors and Guest Authors in an Author Box - Stable (latest release) in Italian -# This file is distributed under the same license as the Plugins - PublishPress Authors: Show Multiple Authors and Guest Authors in an Author Box - Stable (latest release) package. +# Translation of Plugins - Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors - Stable (latest release) in Italian +# This file is distributed under the same license as the Plugins - Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors - Stable (latest release) package. msgid "" msgstr "" -"Project-Id-Version: Plugins - PublishPress Authors: Show Multiple Authors " -"and Guest Authors in an Author Box - Stable (latest release)\n" -"POT-Creation-Date: 2021-11-04 15:04-0300\n" -"PO-Revision-Date: 2021-11-04 15:07-0300\n" +"Project-Id-Version: Plugins - Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors - Stable (latest release)\n" +"POT-Creation-Date: \n" +"PO-Revision-Date: 2022-02-10 16:50+0100\n" "Last-Translator: \n" -"Language-Team: \n" +"Language-Team: Angelo Giammarresi - info@wocmultimedia.com\n" "Language: it\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" -"X-Generator: Poedit 3.0\n" +"X-Generator: Poedit 3.0.1\n" -#: publishpress-authors.php:110 -#, php-format -msgid "New comment on your post \"%s\"" -msgstr "Nuovo commento al tuo articolo \"%s\"" +#: src/modules/default-layouts/default-layouts.php:129 +msgid "View all posts" +msgstr "Visualizza tutti gli articoli" -#: publishpress-authors.php:113 -#, php-format -msgid "Author : %1$s (IP: %2$s , %3$s)" -msgstr "Autore : %1$s (IP: %2$s , %3$s)" +#: src/modules/reviews/reviews.php:74 +msgid "Reviews" +msgstr "Recensioni" -#: publishpress-authors.php:118 -#, php-format -msgid "E-mail : %s" -msgstr "Email : %s" +#: src/modules/multiple-authors/multiple-authors.php:845 +msgid "Click here for more details." +msgstr "Fai clic qui per maggiori dettagli." -#: publishpress-authors.php:119 publishpress-authors.php:137 -#: publishpress-authors.php:151 -#, php-format -msgid "URL : %s" -msgstr "URL : %s" +#: src/modules/multiple-authors/multiple-authors.php:843 +msgid "This setting may be disabled for users who can not edit others posts." +msgstr "Questa impostazione può essere disabilitata per gli utenti che non possono modificare gli articoli degli altri." -#: publishpress-authors.php:121 -#, php-format -msgid "Whois : http://whois.arin.net/rest/ip/%s" -msgstr "Whois : http://whois.arin.net/rest/ip/%s" +#: src/core/Classes/Post_Editor.php:164 +msgid "\"post_author\" is empty" +msgstr "\"post_author\" è vuoto" -#: publishpress-authors.php:124 -msgid "Comment: " -msgstr "Commento: " +#: src/core/Classes/Post_Editor.php:156 +msgid "No author term" +msgstr "Nessun termine autore" -#: publishpress-authors.php:125 -msgid "You can see all comments on this post here: " -msgstr "Puoi vedere qui tutti i commenti su questo articolo: " +#: src/modules/polylang-integration/polylang-integration.php:55 +#: src/modules/polylang-integration/polylang-integration.php:56 +#: src/modules/polylang-integration/polylang-integration.php:57 +msgid "Polylang Integration" +msgstr "Integrazione con Polylang" -#. translators: 1: blog name, 2: post title -#: publishpress-authors.php:127 -#, php-format -msgid "[%1$s] Comment: \"%2$s\"" -msgstr "[%1$s] Commento: \"%2$s\"" +#: src/modules/multiple-authors/assets/js/sync-post-author.jsx:21 +msgid "Updated %d of %d posts..." +msgstr "Aggiornato %d di %d articoli…" + +#: src/modules/multiple-authors/assets/js/sync-post-author.jsx:20 +msgid "Updating author field on posts..." +msgstr "Aggiornamento dei campi autore negli articoli…" + +#: src/modules/multiple-authors/assets/js/sync-post-author.jsx:18 +msgid "Done! %d posts were updated." +msgstr "Fatto! %d articoli sono stati aggiornati." + +#: src/modules/multiple-authors/assets/js/sync-author-slug.jsx:21 +msgid "Updated %d of %d authors..." +msgstr "Aggiornato %d di %d autori…" + +#: src/modules/multiple-authors/assets/js/sync-author-slug.jsx:20 +msgid "Updating authors slug..." +msgstr "Aggiornamento dello slug dell'autore…" + +#: src/modules/multiple-authors/assets/js/sync-author-slug.jsx:18 +msgid "Done! %d authors were updated." +msgstr "Fatto! %d autori sono stati aggiornati." + +#: src/modules/multiple-authors/assets/js/sync-author-slug.jsx:17 +#: src/modules/multiple-authors/assets/js/sync-post-author.jsx:17 +msgid "Finishing the process..." +msgstr "Ultimando il processo…" + +#: src/modules/multiple-authors/assets/js/sync-author-slug.jsx:16 +#: src/modules/multiple-authors/assets/js/sync-post-author.jsx:16 +msgid "Collecting data..." +msgstr "Raccogliendo i dati…" + +#: src/modules/multiple-authors/assets/js/sync-author-slug.jsx:15 +msgid "Sync Author slugs to User logins" +msgstr "Sincronizzare gli slug degli autori con gli accessi degli utenti" + +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:255 +msgid "Copy Co-Authors Plus data" +msgstr "Copiare i dati di Co-Authors Plus" + +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:218 +msgid "Deactivate Co-Authors Plus" +msgstr "Disattivare Co-Authors Plus" + +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:204 +msgid "Done! Co-Authors Plus is deactivated." +msgstr "Fatto! Co-Authors Plus è stato disattivato." + +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:189 +msgid "Deactivating Co-uthors Plus..." +msgstr "Disattivando Co-Authors Plus…" + +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:134 +msgid "Done! Co-Authors Plus data was copied." +msgstr "Fatto! I dati di Co-Authors Plus sono stati copiati." + +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:76 +msgid "Creating missed post authors..." +msgstr "Creazione degli autori degli articoli mancanti…" + +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:207 +msgid "Deactivate Bylines" +msgstr "Disattivare Bylines" + +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:193 +msgid "Done! Bylines is deactivated." +msgstr "Fatto! Bylines è stato disattivato." + +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:178 +msgid "Deactivating Bylines..." +msgstr "Disattivando Bylines…" + +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:120 +msgid "Done! Bylines data was copied and you can deactivate the plugin." +msgstr "Fatto! I dati di Bylines sono stati copiati e puoi disattivare il plugin." + +#: src/modules/byline-migration/assets/js/byline-migration.jsx:185 +msgid "Deactivate Byline" +msgstr "Disattivare Byline" + +#: src/modules/byline-migration/assets/js/byline-migration.jsx:171 +msgid "Done! Byline is deactivated." +msgstr "Fatto! Byline è stato disattivato." + +#: src/modules/byline-migration/assets/js/byline-migration.jsx:156 +msgid "Deactivating Byline..." +msgstr "Disattivando Byline…" + +#: src/modules/byline-migration/assets/js/byline-migration.jsx:141 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:163 +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:174 +msgid "Copying authors' data..." +msgstr "Copiando i dati degli autori…" + +#: src/modules/byline-migration/assets/js/byline-migration.jsx:98 +msgid "Done! Byline data was copied and you can deactivate the plugin." +msgstr "Fatto! I dati di Byline sono stati copiati e puoi disattivare il plugin." + +#: src/modules/byline-migration/assets/js/byline-migration.jsx:63 +#: src/modules/byline-migration/assets/js/byline-migration.jsx:117 +#: src/modules/byline-migration/assets/js/byline-migration.jsx:178 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:57 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:74 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:99 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:139 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:200 +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:63 +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:96 +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:150 +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:211 +#: src/modules/multiple-authors/assets/js/Components/DataMigrationBox.jsx:54 +#: src/modules/multiple-authors/assets/js/Components/DataMigrationBox.jsx:136 +#: src/modules/multiple-authors/assets/js/Components/DataMigrationBox.jsx:167 +msgid "Error: " +msgstr "Errore: " + +#: src/modules/byline-migration/assets/js/byline-migration.jsx:39 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:39 +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:39 +msgid "Collecting data for the migration..." +msgstr "Raccogliendo i dati per la migrazione…" + +#: src/core/Classes/Author_Editor.php:167 +msgid "Create Author Profile" +msgstr "Crea il profilo autore" -#: publishpress-authors.php:129 -#, php-format -msgid "New trackback on your post \"%s\"" -msgstr "Nuovo trackback al tuo articolo \"%s\"" +#: src/modules/multiple-authors/multiple-authors.php:472 +msgid "Post types to display on the author's profile page:" +msgstr "Tipi di contenuto da mostrare nella pagina del profilo autore:" -#: publishpress-authors.php:132 publishpress-authors.php:146 -#, php-format -msgid "Website: %1$s (IP: %2$s , %3$s)" -msgstr "Sito web: %1$s (IP: %2$s , %3$s)" +#: src/core/Classes/Installer.php:318 +msgid "All is set. No posts need to be updated" +msgstr "Tutto è a posto. Nessun articolo deve essere aggiornato" -#: publishpress-authors.php:138 publishpress-authors.php:152 -msgid "Excerpt: " -msgstr "Riassunto: " +#: src/core/Classes/Installer.php:299 +msgid "Adding the author term %d to the post %d" +msgstr "Aggiungendo il termine autore %d all'articolo %d" -#: publishpress-authors.php:139 -msgid "You can see all trackbacks on this post here: " -msgstr "Puoi vedere qui tutti i trackback a questo articolo: " +#: src/core/Classes/Installer.php:286 +msgid "Creating author term for the user %d" +msgstr "Creando il termine autore per l'utente %d" -#. translators: 1: blog name, 2: post title -#: publishpress-authors.php:141 -#, php-format -msgid "[%1$s] Trackback: \"%2$s\"" -msgstr "[%1$s] Trackback: \"%2$s\"" +#: src/core/Classes/Installer.php:272 +msgid "%d/%d: Inspecting the post %d" +msgstr "%d/%d: Ispezionando l'articolo %d" -#: publishpress-authors.php:143 -#, php-format -msgid "New pingback on your post \"%s\"" -msgstr "Nuovo pingback al tuo articolo \"%s\"" +#: src/core/Classes/Installer.php:260 +msgid "Now inspecting or updating %d total posts" +msgstr "Ora ispezionando o aggiornando %d messaggi totali" -#: publishpress-authors.php:156 -msgid "You can see all pingbacks on this post here: " -msgstr "Puoi vedere qui tutti i pingback a questo articolo: " +#: src/core/Classes/Installer.php:179 +msgid "All is set. No author need to be updated" +msgstr "Tutto è a posto. Nessun autore deve essere aggiornato" -#. translators: 1: blog name, 2: post title -#: publishpress-authors.php:158 -#, php-format -msgid "[%1$s] Pingback: \"%2$s\"" -msgstr "[%1$s] Pingback: \"%2$s\"" +#: src/core/Classes/Installer.php:167 +msgid "%d/%d: Inspecting the user %d" +msgstr "%d/%d: Ispezionando l'utente %d" -#: publishpress-authors.php:162 -#, php-format -msgid "Permalink: %s" -msgstr "Permalink: %s" +#: src/core/Classes/Installer.php:153 +msgid "Now inspecting or updating %d total authors" +msgstr "Ora ispezionando o aggiornando %d autori totali" -#: publishpress-authors.php:167 -#, php-format -msgid "Trash it: %s" -msgstr "Cestinare: %s" +#: src/core/Classes/Post_Editor.php:298 +msgid "Search for an user" +msgstr "Cerca l'utente" -#: publishpress-authors.php:172 -#, php-format -msgid "Delete it: %s" -msgstr "Eliminalo: %s" +#: src/core/Classes/Post_Editor.php:290 +msgid "This option is showing because you do not have a WordPress user selected as an author. For some tasks, it can be helpful to have a user selected here. This user will not be visible on the front of your site." +msgstr "Questa opzione viene visualizzata perché non hai un utente WordPress impostato come autore. Per alcune operazioni potrebbe essere utile avere un utente selezionato qui. Questo utente non sarà comunque visibile sul lato pubblico del sito." -#: publishpress-authors.php:177 -#, php-format -msgid "Spam it: %s" -msgstr "Spammalo: %s" +#: src/core/WP_Cli.php:71 +msgid "%d posts were found without author terms" +msgstr "%d articoli sono stati trovati senza termini autore" -#: src/core/Authors_Widget.php:22 -msgid "Authors List" -msgstr "Lista autori" +#: src/core/WP_Cli.php:56 +msgid "No posts without author terms were found" +msgstr "Non sono stati trovati articoli senza termini autore" -#: src/core/Authors_Widget.php:29 -msgid "Display authors list." -msgstr "Visualizza lista autori." +#: src/modules/pro-placeholders/views/layouts-placeholder.php:11 +msgid "With PublishPress Authors Pro you can build new layouts for authors. You can use author information, custom fields, and much more." +msgstr "Con PublishPress Authors Pro puoi costruire nuovi layout per gli autori. Puoi aggiungere informazioni sull'autore, campi personalizzati e molto altro." -#: src/core/Authors_Widget.php:107 -msgid "Title" -msgstr "Titolo" +#: src/modules/pro-placeholders/views/layouts-placeholder.php:2 +msgid "New Author Layout" +msgstr "Nuovo layout autore" -#: src/core/Authors_Widget.php:108 src/core/Widget.php:123 -msgid "Layout" -msgstr "Layout" +#: src/modules/pro-placeholders/views/layouts-placeholder.php:2 +msgid "Author Layouts" +msgstr "Layout autore" -#: src/core/Authors_Widget.php:110 -msgid "Display All Authors (including those who have not written any posts)" -msgstr "" -"Visualizza tutti gli autori (incluso anche quelli che non hanno ancora " -"scritto alcun articolo)" +#: src/modules/pro-placeholders/views/fields-placeholder.php:15 +#: src/modules/pro-placeholders/views/layouts-placeholder.php:15 +msgid "Upgrade to Pro" +msgstr "Aggiorna a Pro" -#: src/core/Classes/Author_Editor.php:43 -msgid "Name" -msgstr "Nome" +#: src/modules/pro-placeholders/views/fields-placeholder.php:11 +msgid "With PublishPress Authors Pro you can create custom fields for your author profiles. You can add Text, WYSIWYG, Link, email fields and more." +msgstr "Con PublishPress Authors Pro puoi creare campi personalizzati per i profili degli autori. Puoi aggiungere campi testo, WYSIWYG, link, email e altro." -#: src/core/Classes/Author_Editor.php:44 src/core/Classes/Author_Editor.php:281 -msgid "Email" -msgstr "Email" +#: src/modules/pro-placeholders/views/fields-placeholder.php:2 +msgid "New Author Field" +msgstr "Nuovo campo autore" -#: src/core/Classes/Author_Editor.php:53 src/core/Plugin.php:683 -#: src/modules/multiple-authors/multiple-authors.php:124 -#: src/modules/multiple-authors/multiple-authors.php:623 -#: src/modules/settings/settings.php:289 -msgid "Posts" -msgstr "Articoli" +#: src/modules/pro-placeholders/views/fields-placeholder.php:2 +msgid "Author Fields" +msgstr "Campi autore" -#: src/core/Classes/Author_Editor.php:55 src/core/Plugin.php:685 -#, php-format -msgid "Published posts of the following post types: %s" -msgstr "Articoli pubblicati per i seguenti tipi di articoli: %s" +#: src/modules/pro-placeholders/pro-placeholders.php:105 +#: src/modules/pro-placeholders/pro-placeholders.php:106 +msgid "Layouts" +msgstr "Layout" -#: src/core/Classes/Author_Editor.php:93 -msgid "User" -msgstr "Utente" +#: src/modules/pro-placeholders/pro-placeholders.php:95 +#: src/modules/pro-placeholders/pro-placeholders.php:96 +msgid "Fields" +msgstr "Campi" -#: src/core/Classes/Author_Editor.php:96 -msgid "Guest Author" -msgstr "Autore ospite" +#: src/modules/pro-placeholders/pro-placeholders.php:56 +#: src/modules/pro-placeholders/pro-placeholders.php:57 +#: src/modules/pro-placeholders/pro-placeholders.php:58 +msgid "Pro Placeholders" +msgstr "Segnaposti Pro" -#: src/core/Classes/Author_Editor.php:139 -#: src/core/Classes/Author_Editor.php:217 -msgid "Edit User" -msgstr "Modifica utente" +#: src/modules/multiple-authors/multiple-authors.php:550 +msgid "Color scheme:" +msgstr "Schema dei colori:" -#: src/core/Classes/Author_Editor.php:154 -#: src/core/Classes/Author_Editor.php:201 -msgid "Edit Author Profile" -msgstr "Modifica profilo autore" +#: src/modules/wpengine-integration/wpengine-integration.php:52 +msgid "Add compatibility with the WPEngine object cache." +msgstr "Aggiungere la compatibilità con la cache degli oggetti di WPEngine." -#: src/core/Classes/Author_Editor.php:168 -#, fuzzy -#| msgid "Edit Author Profile" -msgid "Create Author Profile" -msgstr "Modifica profilo autore" +#: src/modules/wpengine-integration/wpengine-integration.php:51 +msgid "WPEngine Integration" +msgstr "Integrazione WPEngine" -#: src/core/Classes/Author_Editor.php:268 -msgid "Mapped User" -msgstr "Utente mappato" +#: src/modules/seoframework-integration/seoframework-integration.php:59 +msgid "Add compatibility with The SEO Framework plugin." +msgstr "Aggiunta compatibilità con il plugin The SEO Framework." -#: src/core/Classes/Author_Editor.php:273 -msgid "First Name" -msgstr "Nome" +#: src/modules/seoframework-integration/seoframework-integration.php:58 +msgid "The SEO Framework Integration" +msgstr "Integrazione The SEO Framework" -#: src/core/Classes/Author_Editor.php:277 -msgid "Last Name" -msgstr "Cognome" +#: src/core/Widget.php:122 +msgid "Plural Title" +msgstr "Titolo plurale" -#: src/core/Classes/Author_Editor.php:284 -msgid "" -"To show the avatar from the Mapped User, enter the same email address as the " -"Mapped User.
To show the avatar for a Guest Author, enter the email for " -"their Gravatar account." -msgstr "" -"Per mostrare l'avatar dell'utente mappato, immettere lo stesso indirizzo " -"email dell'utente mappato.
Per mostrare l'avatar di un autore ospite, " -"inserisci l'email del suo account Gravatar." +#: src/core/Widget.php:121 +msgid "Single Title" +msgstr "Titolo singolare" -#: src/core/Classes/Author_Editor.php:289 -msgid "Custom Avatar" -msgstr "Avatar personalizzato" +#: src/modules/multiple-authors/multiple-authors.php:716 +msgid "Plural" +msgstr "Plurale" -#: src/core/Classes/Author_Editor.php:294 -msgid "Website" -msgstr "Sito web" +#: src/modules/multiple-authors/multiple-authors.php:709 +msgid "Single" +msgstr "Singolare" -#: src/core/Classes/Author_Editor.php:299 -msgid "Biographical Info" -msgstr "Informazioni biografiche" +#: src/modules/rest-api/rest-api.php:96 +msgid "Authors." +msgstr "Autori." -#: src/core/Classes/Author_Editor.php:352 -msgid "Select image" -msgstr "Seleziona immagine" +#: src/modules/rest-api/rest-api.php:58 src/modules/rest-api/rest-api.php:59 +msgid "Rest API support" +msgstr "Supporto Rest API" -#: src/core/Classes/Author_Editor.php:356 -msgid "Remove this image" -msgstr "Rimuovi questa immagine" +#: src/modules/rest-api/rest-api.php:57 +msgid "Rest API" +msgstr "Rest API" -#: src/core/Classes/Author_Editor.php:370 -msgid "Select a user" -msgstr "Seleziona un utente" +#: src/modules/editflow-integration/editflow-integration.php:52 +msgid "Add compatibility with the Edit Flow plugin" +msgstr "Aggiungi compatibilità con il plugin Edit Flow" -#: src/core/Classes/Author_Editor.php:481 -msgid "Mapped User (optional)" -msgstr "Utente mappato (opzionale)" +#: src/modules/editflow-integration/editflow-integration.php:51 +msgid "Edit Flow Integration" +msgstr "Integrazione con Edit Flow" -#: src/core/Classes/Author_Editor.php:489 -msgid "" -"You don’t have to choose a Mapped User. Leave this choice blank and you can " -"create a Guest Author with no WordPress account." -msgstr "" -"Non devi scegliere un utente mappato. Lascia questa scelta vuota e puoi " -"creare un autore ospite senza che abbia un account WordPress collegato." +#: src/modules/multiple-authors/multiple-authors.php:2541 +msgid "Click to run the update now" +msgstr "Fai clic per avviare adesso l'aggiornamento" -#: src/core/Classes/Author_Editor.php:548 -msgid "Update data from mapped user" -msgstr "Aggiorna i dati da utente mappato" +#: src/modules/multiple-authors/multiple-authors.php:2540 +msgid "PublishPress Authors needs a database update for Permissions integration." +msgstr "PublishPress Authors deve aggiornare il database per l'integrazione con il plugin Permissions." -#: src/core/Classes/Author_Editor.php:552 -msgid "Convert into guest author" -msgstr "Converti in autore ospite" +#: src/modules/multiple-authors/multiple-authors.php:922 +msgid "Synchronize Author slugs to User logins" +msgstr "Sincronizza gli slug dell'autore con gli accessi dell'utente" -#: src/core/Classes/Author_Editor.php:556 -msgid "Update post count" -msgstr "Aggiorna conteggio articoli" +#: src/modules/debug/debug.php:97 +msgid "Authors Debug" +msgstr "Debug PublishPress Authors" -#: src/core/Classes/Author_Editor.php:620 -msgid "No authors were updated" -msgstr "Nessun autore è stato aggiornato" +#: src/modules/debug/debug.php:54 +msgid "Add debug information for the plugin" +msgstr "Aggiungi le informazioni di debug per il plugin" -#: src/core/Classes/Author_Editor.php:622 -#, php-format -msgid "Updated %d authors" -msgstr "Aggiorna %d autori" +#: src/modules/debug/debug.php:53 +msgid "Debug" +msgstr "Debug" -#: src/core/Classes/Authors_Iterator.php:33 -msgid "" -"No post ID provided for Authors_Iterator constructor. Are you not in a loop " -"or is $post not set?" -msgstr "" -"Nessun ID articolo fornito per il costruttore Authors_Iterator. Non sei in " -"loop o $post non è impostato?" - -#: src/core/Classes/Installer.php:153 -#, php-format -msgid "Now inspecting or updating %d total authors" -msgstr "" - -#: src/core/Classes/Installer.php:167 -#, php-format -msgid "%d/%d: Inspecting the user %d" -msgstr "" - -#: src/core/Classes/Installer.php:179 -#, fuzzy -#| msgid "No authors were updated" -msgid "All is set. No author need to be updated" -msgstr "Nessun autore è stato aggiornato" - -#: src/core/Classes/Installer.php:260 -#, php-format -msgid "Now inspecting or updating %d total posts" -msgstr "" +#: src/core/Plugin.php:1367 +msgid "Are you sure you want to update the author slug for all the users?" +msgstr "Vuoi davvero aggiornare lo slug autore di tutti gli utenti?" -#: src/core/Classes/Installer.php:272 -#, php-format -msgid "%d/%d: Inspecting the post %d" -msgstr "" +#. translators: %s: Number of posts. +#: src/core/Plugin.php:714 +msgid "%s post by this author" +msgid_plural "%s posts by this author" +msgstr[0] "%s articolo di questo autore" +msgstr[1] "%s articoli di questo autore" -#: src/core/Classes/Installer.php:286 -#, php-format -msgid "Creating author term for the user %d" -msgstr "" +#: src/core/Classes/Author_Editor.php:55 src/core/Plugin.php:685 +msgid "Published posts of the following post types: %s" +msgstr "Articoli pubblicati per i seguenti tipi di articoli: %s" -#: src/core/Classes/Installer.php:299 -#, php-format -msgid "Adding the author term %d to the post %d" -msgstr "" +#: src/core/Classes/Author_Editor.php:555 +msgid "Update post count" +msgstr "Aggiorna conteggio articoli" -#: src/core/Classes/Installer.php:318 -msgid "All is set. No posts need to be updated" -msgstr "" +#: src/core/Plugin.php:1363 +msgid "Are you sure you want to update the author column for all the posts?" +msgstr "Sei sicuro di voler aggiornare la colonna autore di tutti gli articoli?" -#: src/core/Classes/Integrations/Theme.php:40 -#, php-format -msgid "Author: %s" -msgstr "Autore: %s" +#: src/modules/ultimatemember-integration/ultimatemember-integration.php:54 +msgid "Add compatibility with the Ultimate Member plugin" +msgstr "Aggiungi compatibilità con il plugin Ultimate Member" -#: src/core/Classes/Legacy/LegacyPlugin.php:253 -msgid "Configure" -msgstr "Configura" +#: src/modules/ultimatemember-integration/ultimatemember-integration.php:53 +msgid "Ultimate Member Integration" +msgstr "Integrazione Ultimate Member" -#: src/core/Classes/Legacy/LegacyPlugin.php:257 -msgid "Please correct your form errors below and try again." -msgstr "Correggi gli errori nel modulo sottostante e riprova." +#: src/modules/multiple-authors/multiple-authors.php:915 +#: src/modules/multiple-authors/assets/js/sync-post-author.jsx:15 +msgid "Update author field on posts" +msgstr "Aggiorna il campo autore negli articoli" -#: src/core/Classes/Legacy/LegacyPlugin.php:260 -#: src/modules/settings/settings.php:336 -msgid "Cheatin’ uh?" -msgstr "Stai cercando di barare, vero?" +#: src/modules/multiple-authors/multiple-authors.php:502 +msgid "Default author for new posts:" +msgstr "Autore predefinito per i nuovi articoli:" -#: src/core/Classes/Legacy/LegacyPlugin.php:262 -msgid "You do not have necessary permissions to complete this action." -msgstr "Non hai le autorizzazioni necessarie per completare questa azione." +#: src/modules/multiple-authors/multiple-authors.php:2473 +#: src/modules/multiple-authors/multiple-authors.php:2547 +msgid "Dismiss" +msgstr "Ignora" -#: src/core/Classes/Legacy/LegacyPlugin.php:265 -msgid "Post does not exist" -msgstr "L'articolo non esiste" +#: src/modules/multiple-authors/multiple-authors.php:2468 +msgid "Please click here and read this guide!" +msgstr "Fai clic qui e leggi questa guida!" -#: src/core/Classes/Legacy/Module.php:102 -msgid "Post" -msgstr "Articolo" +#: src/modules/multiple-authors/multiple-authors.php:2467 +msgid "It looks like you have Co-Authors Plus installed." +msgstr "Sembra che tu hai installato anche Co-Authors Plus." -#: src/core/Classes/Legacy/Module.php:103 -msgid "Page" -msgstr "Pagina" +#. Description of the plugin +#: src/modules/multiple-authors/multiple-authors.php:76 +#: src/modules/multiple-authors/multiple-authors.php:80 +msgid "PublishPress Authors allows you to add multiple authors and guest authors to WordPress posts" +msgstr "PublishPress Authors ti permette di aggiungere autori multipli e autori ospiti agli articoli di WordPress" -#: src/core/Classes/Post_Editor.php:89 src/core/Classes/Post_Editor.php:192 -#: src/core/Plugin.php:762 src/core/Traits/Author_box.php:150 -#: src/modules/editflow-integration/editflow-integration.php:113 -#: src/modules/multiple-authors/multiple-authors.php:264 -#: src/modules/multiple-authors/multiple-authors.php:265 -#: src/modules/multiple-authors/multiple-authors.php:296 -#: src/modules/multiple-authors/multiple-authors.php:297 -#: src/modules/multiple-authors/multiple-authors.php:704 -msgid "Authors" -msgstr "Autori" +#: src/modules/multiple-authors/multiple-authors.php:805 +msgid "If the Author is mapped to a WordPress user, this will display the authors' \"Display name\" and their \"Username\". The default is to show only the \"Display name\". Showing the \"Username\" is useful if you have several authors with similar names." +msgstr "Se l'autore è mappato a un utente WordPress, questo mostrerà il «Nome visualizzato» degli autori e il loro «Nome utente». L'impostazione predefinita è mostrare solo il «Nome visualizzato». La visualizzazione del «Nome utente» è utile se hai più autori con nomi simili." -#: src/core/Classes/Post_Editor.php:156 -#, fuzzy -#| msgid "No author" -msgid "No author term" -msgstr "Nessun autore" +#: src/modules/multiple-authors/multiple-authors.php:491 +msgid "Show username in the search field:" +msgstr "Mostra il nome utente nel campo di ricerca:" -#: src/core/Classes/Post_Editor.php:164 -msgid "\"post_author\" is empty" -msgstr "" +#: src/core/Authors_Widget.php:109 +msgid "Display All Authors (including those who have not written any posts)" +msgstr "Visualizza tutti gli autori (incluso anche quelli che non hanno ancora scritto alcun articolo)" -#: src/core/Classes/Post_Editor.php:264 src/core/Plugin.php:1346 -#: src/modules/multiple-authors/multiple-authors.php:830 -msgid "Search for an author" -msgstr "Cerca un autore" +#: src/core/Authors_Widget.php:28 +msgid "Display authors list." +msgstr "Visualizza lista autori." -#: src/core/Classes/Post_Editor.php:286 -msgid "" -"This option is showing because you do not have a WordPress user selected as " -"an author. For some tasks, it can be helpful to have a user selected here. " -"This user will not be visible on the front of your site." -msgstr "" +#: src/core/Authors_Widget.php:22 +msgid "Authors List" +msgstr "Lista autori" -#: src/core/Classes/Post_Editor.php:293 -#, fuzzy -#| msgid "Search for an author" -msgid "Search for an user" -msgstr "Cerca un autore" +#: src/core/Widget.php:42 +msgid "Post Author" +msgstr "Autore articolo" -#: src/core/Classes/Term_Editor.php:56 -#: src/modules/multiple-authors/multiple-authors.php:1172 -msgid "Author URL" -msgstr "URL autore" +#. Plugin URI of the plugin +msgid "https://wordpress.org/plugins/publishpress-authors/" +msgstr "https://wordpress.org/plugins/publishpress-authors/" -#: src/core/Classes/Utils.php:73 -msgid "Co-Authors Plus must be installed and active." -msgstr "Co-Authors Plus deve essere installato e attivato." +#: src/modules/divi-integration/divi-integration.php:53 +msgid "Add compatibility with the Divi Theme Builder" +msgstr "Aggiungi compatibilità con il Divi Theme Builder" -#: src/core/Plugin.php:474 -msgctxt "taxonomy general name" -msgid "Authors" -msgstr "Autori" +#: src/modules/divi-integration/divi-integration.php:52 +msgid "Divi Integration" +msgstr "Integrazione Divi" -#: src/core/Plugin.php:479 -msgctxt "taxonomy singular name" -msgid "Author" -msgstr "Autore" +#: src/modules/elementor-integration/Modules/Posts/Skins/PostsSkinCards.php:40 +msgid "Cards - PublishPress Authors" +msgstr "Carte - PublishPress Authors" -#: src/core/Plugin.php:483 -msgid "Search authors" -msgstr "Cerca autori" +#: src/modules/elementor-integration/Modules/Posts/Skins/PostsSkinFullContent.php:36 +msgid "Full Content - PublishPress Authors" +msgstr "Contenuto completo" -#: src/core/Plugin.php:484 -msgid "Popular authors" -msgstr "Autori popolari" +#: src/modules/elementor-integration/Modules/Posts/Skins/PostsSkinClassic.php:38 +msgid "Classic - PublishPress Authors" +msgstr "Classico - PublishPress Authors" -#: src/core/Plugin.php:485 -msgid "All authors" -msgstr "Tutti gli autori" +#: src/modules/elementor-integration/elementor-integration.php:58 +msgid "Add compatibility with the Elementor and Elementor Pro page builder" +msgstr "Aggiungi compatibilità con Elementor ed Elementor Pro page builder" -#: src/core/Plugin.php:486 -msgid "Parent author" -msgstr "Autore genitore" +#: src/modules/elementor-integration/elementor-integration.php:57 +msgid "Elementor Integration" +msgstr "Integrazione Elementor" -#: src/core/Plugin.php:487 -msgid "Parent author:" -msgstr "Autore genitore:" +#: src/modules/genesis-integration/genesis-integration.php:53 +msgid "Add compatibility with the Genesis framework" +msgstr "Aggiungi compatibilità con Genesis framework" -#: src/core/Plugin.php:488 -msgid "Edit author" -msgstr "Modifica autore" +#: src/modules/genesis-integration/genesis-integration.php:52 +msgid "Genesis Integration" +msgstr "Integrazione Genesis" -#: src/core/Plugin.php:489 -msgid "View author" -msgstr "Visualizza autore" +#: src/modules/yoast-seo-integration/yoast-seo-integration.php:52 +msgid "Yoast SEO Integration" +msgstr "Integrazione Yoast SEO" -#: src/core/Plugin.php:490 -msgid "Update author" -msgstr "Aggiorna autore" +#: src/modules/byline-migration/byline-migration.php:157 +#: src/modules/byline-migration/assets/js/byline-migration.jsx:222 +msgid "Copy Byline Data" +msgstr "Copia dati info autore" -#: src/core/Plugin.php:491 src/core/Plugin.php:492 -msgid "New author" -msgstr "Nuovo autore" +#: src/modules/byline-migration/byline-migration.php:72 +#: src/modules/byline-migration/byline-migration.php:73 +msgid "Add migration option for Byline" +msgstr "Aggiungi opzione migrazione per info autori" -#: src/core/Plugin.php:494 -msgid "Separate authors with commas" -msgstr "Separare gli autori con virgole" +#: src/modules/byline-migration/byline-migration.php:71 +msgid "Migrate Byline Data" +msgstr "Migrare i dati info autore" -#: src/core/Plugin.php:497 -msgid "Add or remove authors" -msgstr "Aggiungi o rimuovi autori" +#: src/modules/bylines-migration/bylines-migration.php:159 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:244 +msgid "Copy Bylines Data" +msgstr "Copiare i dati info autori" -#: src/core/Plugin.php:499 -msgid "Choose from the most used authors" -msgstr "Scegli tra gli autori più utilizzati" +#: src/modules/bylines-migration/bylines-migration.php:75 +#: src/modules/bylines-migration/bylines-migration.php:76 +msgid "Add migration option for Bylines" +msgstr "Aggiungi opzione migrazione per info autori" -#: src/core/Plugin.php:502 -msgid "No authors found." -msgstr "Nessun autore trovato." +#: src/modules/bylines-migration/bylines-migration.php:74 +msgid "Migrate Bylines Data" +msgstr "Migrare i dati info autori" -#: src/core/Plugin.php:503 src/core/Traits/Author_box.php:144 -#: src/modules/multiple-authors/multiple-authors.php:698 -msgid "Author" -msgstr "Autore" +#: src/modules/yoast-seo-integration/yoast-seo-integration.php:53 +msgid "Add compatibility with the Yoast SEO plugin" +msgstr "Aggiungi compatibilità con il plugin Yoast SEO" -#: src/core/Plugin.php:504 -msgid "Back to Authors" -msgstr "Torna ad autori" +#: src/functions/template-tags.php:918 +msgid ", and " +msgstr ", e " -#. Plugin Name of the plugin/theme -#: src/core/Plugin.php:622 src/modules/settings/settings.php:59 -msgid "PublishPress Authors" -msgstr "PublishPress Authors" +#. translators: Posts by a given author. +#: src/functions/template-tags.php:832 +msgid "Posts by %1$s" +msgstr "Articoli da %1$s" -#: src/core/Plugin.php:626 -#, php-format -msgid "If you like %s please leave us a %s rating. Thank you!" -msgstr "Se sei soddisfatto di %s, lasciaci una valutazione di %s." +#. Translators: refers to the author's website. +#: src/functions/template-tags.php:629 src/functions/template-tags.php:887 +msgid "Visit %s’s website" +msgstr "Visita il sito web di %s" -#. translators: %s: Number of posts. -#: src/core/Plugin.php:714 -#, php-format -msgid "%s post by this author" -msgid_plural "%s posts by this author" -msgstr[0] "%s articolo di questo autore" -msgstr[1] "%s articoli di questo autore" +#: src/functions/template-tags.php:445 +msgid "Posts by %s" +msgstr "Articoli da %s" -#: src/core/Plugin.php:766 -msgid "Click on an author to change them. Drag to change their order." -msgstr "" -"Fai click su ogni autore per modificarli. Trascinali per cambiarne l'ordine." +#: src/functions/template-tags.php:294 src/functions/template-tags.php:917 +msgid " and " +msgstr " e " -#: src/core/Plugin.php:803 -msgid "No co-author exists for that term" -msgstr "Nessun coautore esiste per quel termine" +#: publishpress-authors.php:177 +msgid "Spam it: %s" +msgstr "Spammalo: %s" -#: src/core/Plugin.php:1337 -msgid "Edit" -msgstr "Modifica" +#: publishpress-authors.php:172 +msgid "Delete it: %s" +msgstr "Eliminalo: %s" -#: src/core/Plugin.php:1339 -msgid "Are you sure you want to remove this author?" -msgstr "Sei sicuro di voler rimuovere questo autore?" +#: publishpress-authors.php:167 +msgid "Trash it: %s" +msgstr "Cestinare: %s" -#: src/core/Plugin.php:1343 -msgid "Click to change this author, or drag to change their position" -msgstr "" -"Fai click per modificare questo autore li, oppure puoi anche trascinarlo per " -"cambiarne la posizione" +#: publishpress-authors.php:162 +msgid "Permalink: %s" +msgstr "Permalink: %s" -#: src/core/Plugin.php:1348 -msgid "" -"Click on an author to change them. Drag to change their order. Click on " -"Remove to remove them." -msgstr "" -"Fai click su ogni autore per modificarli, puoi anche trascinarli per " -"cambiarne l'ordine oppure fai clic su Rimuovi per " -"rimuoverli." +#. translators: 1: blog name, 2: post title +#: publishpress-authors.php:158 +msgid "[%1$s] Pingback: \"%2$s\"" +msgstr "[%1$s] Pingback: \"%2$s\"" -#: src/core/Plugin.php:1352 -msgid "" -"Are you sure you want to delete the authors profiles mapped to users? This " -"action can't be undone." -msgstr "" -"Sei sicuro di voler eliminare i profili degli autori mappati agli utenti? " -"Questa azione non può essere annullata." +#: publishpress-authors.php:156 +msgid "You can see all pingbacks on this post here: " +msgstr "Puoi vedere qui tutti i pingback a questo articolo: " -#: src/core/Plugin.php:1356 -msgid "" -"Are you sure you want to delete the guest authors profiles? This action " -"can't be undone." -msgstr "" -"Sei sicuro di voler eliminare i profili degli autori ospiti? Questa azione " -"non può essere annullata." +#: publishpress-authors.php:143 +msgid "New pingback on your post \"%s\"" +msgstr "Nuovo pingback al tuo articolo \"%s\"" -#: src/core/Plugin.php:1360 -msgid "" -"Are you sure you want to create author profiles for the missed post authors?" -msgstr "" -"Sei sicuro di voler creare dei profili autore per gli autori di articoli " -"persi?" +#. translators: 1: blog name, 2: post title +#: publishpress-authors.php:141 +msgid "[%1$s] Trackback: \"%2$s\"" +msgstr "[%1$s] Trackback: \"%2$s\"" -#: src/core/Plugin.php:1364 -msgid "Are you sure you want to update the author column for all the posts?" -msgstr "" -"Sei sicuro di voler aggiornare la colonna autore di tutti gli articoli?" +#: publishpress-authors.php:139 +msgid "You can see all trackbacks on this post here: " +msgstr "Puoi vedere qui tutti i trackback a questo articolo: " -#: src/core/Plugin.php:1368 -msgid "Are you sure you want to update the author slug for all the users?" -msgstr "Vuoi davvero aggiornare lo slug autore di tutti gli utenti?" +#: publishpress-authors.php:138 publishpress-authors.php:152 +msgid "Excerpt: " +msgstr "Riassunto: " -#: src/core/Plugin.php:1372 -msgid "Are you sure you want to create authors for the selected roles?" -msgstr "Sei sicuro di voler creare degli autori per i ruoli selezionati?" +#: publishpress-authors.php:132 publishpress-authors.php:146 +msgid "Website: %1$s (IP: %2$s , %3$s)" +msgstr "Sito web: %1$s (IP: %2$s , %3$s)" -#: src/core/Plugin.php:1377 -msgid "Please, wait..." -msgstr "Attendere prego…" +#: publishpress-authors.php:129 +msgid "New trackback on your post \"%s\"" +msgstr "Nuovo trackback al tuo articolo \"%s\"" -#: src/core/Plugin.php:1379 -msgid "Sorry, the request returned an error." -msgstr "Spiacenti, la richiesta ha restituito un errore." +#. translators: 1: blog name, 2: post title +#: publishpress-authors.php:127 +msgid "[%1$s] Comment: \"%2$s\"" +msgstr "[%1$s] Commento: \"%2$s\"" -#: src/core/Plugin.php:1443 -msgid "Mine" -msgstr "Miei" +#: publishpress-authors.php:125 +msgid "You can see all comments on this post here: " +msgstr "Puoi vedere qui tutti i commenti su questo articolo: " -#: src/core/WP_Cli.php:56 -msgid "No posts without author terms were found" -msgstr "" +#: publishpress-authors.php:124 +msgid "Comment: " +msgstr "Commento: " -#: src/core/WP_Cli.php:71 -#, php-format -msgid "%d posts were found without author terms" -msgstr "" +#: publishpress-authors.php:121 +msgid "Whois : http://whois.arin.net/rest/ip/%s" +msgstr "Whois : http://whois.arin.net/rest/ip/%s" -#: src/core/Widget.php:42 -msgid "Post Author" -msgstr "Autore articolo" +#: publishpress-authors.php:119 publishpress-authors.php:137 +#: publishpress-authors.php:151 +msgid "URL : %s" +msgstr "URL : %s" -#: src/core/Widget.php:49 -msgid "Display a list of authors for the current post." -msgstr "Visualizza un elenco degli autori per l'articolo corrente." +#: publishpress-authors.php:118 +msgid "E-mail : %s" +msgstr "Email : %s" -#: src/core/Widget.php:121 -msgid "Single Title" -msgstr "" +#: publishpress-authors.php:113 +msgid "Author : %1$s (IP: %2$s , %3$s)" +msgstr "Autore : %1$s (IP: %2$s , %3$s)" -#: src/core/Widget.php:122 -msgid "Plural Title" -msgstr "" +#: publishpress-authors.php:110 +msgid "New comment on your post \"%s\"" +msgstr "Nuovo commento al tuo articolo \"%s\"" -#: src/functions/template-tags.php:295 src/functions/template-tags.php:917 -msgid " and " -msgstr " e " +#: src/modules/default-layouts/default-layouts.php:153 +msgid "Simple list" +msgstr "Elenco semplice" -#: src/functions/template-tags.php:445 -#, php-format -msgid "Posts by %s" -msgstr "Articoli da %s" +#: src/modules/default-layouts/default-layouts.php:152 +msgid "Inline with avatar" +msgstr "In linea con avatar" -#: src/functions/template-tags.php:629 src/functions/template-tags.php:887 -#, php-format -msgid "Visit %s’s website" -msgstr "Visita il sito web di %s" +#: src/modules/default-layouts/default-layouts.php:151 +msgid "Inline" +msgstr "In linea" -#: src/functions/template-tags.php:832 -#, php-format -msgid "Posts by %1$s" -msgstr "Articoli da %1$s" +#: src/modules/default-layouts/default-layouts.php:150 +msgid "Centered" +msgstr "Centrato" -#: src/functions/template-tags.php:918 -msgid ", and " -msgstr ", e " +#: src/modules/default-layouts/default-layouts.php:149 +msgid "Boxed" +msgstr "Riquadrato" -#: src/modules/byline-migration/byline-migration.php:71 -msgid "Migrate Byline Data" -msgstr "Migrare i dati info autore" +#: src/modules/default-layouts/default-layouts.php:54 +msgid "Default Layouts" +msgstr "Layout predefiniti" -#: src/modules/byline-migration/byline-migration.php:72 -#: src/modules/byline-migration/byline-migration.php:73 -msgid "Add migration option for Byline" -msgstr "Aggiungi opzione migrazione per info autori" +#: src/modules/modules-settings/modules-settings.php:235 +msgid "Enabled features" +msgstr "Funzionalità abilitate" -#: src/modules/byline-migration/byline-migration.php:157 -msgid "Copy Byline Data" -msgstr "Copia dati info autore" +#: src/modules/modules-settings/modules-settings.php:227 +msgid "Feel free to select only the features you need." +msgstr "Puoi decidere di selezionare soltanto le funzionalità desiderate." -#: src/modules/bylines-migration/bylines-migration.php:74 -msgid "Migrate Bylines Data" -msgstr "Migrare i dati info autori" +#: src/modules/modules-settings/modules-settings.php:226 +msgid "Features" +msgstr "Funzionalità" -#: src/modules/bylines-migration/bylines-migration.php:75 -#: src/modules/bylines-migration/bylines-migration.php:76 -msgid "Add migration option for Bylines" -msgstr "Aggiungi opzione migrazione per info autori" +#: src/modules/modules-settings/modules-settings.php:52 +msgid "Authors Settings" +msgstr "Impostazioni autori" -#: src/modules/bylines-migration/bylines-migration.php:159 -msgid "Copy Bylines Data" -msgstr "Copiare i dati info autori" +#: src/modules/multiple-authors/multiple-authors.php:1859 +msgid "Maintenance completed successfully." +msgstr "La manutenzione è stata completata con successo." -#: src/modules/debug/debug.php:53 -msgid "Debug" -msgstr "Debug" +#: src/modules/multiple-authors/multiple-authors.php:1848 +msgid "Error. Author terms could not be reseted." +msgstr "Errore. Impossibile reimpostare i termini dell'autore." -#: src/modules/debug/debug.php:54 -msgid "Add debug information for the plugin" -msgstr "Aggiungi le informazioni di debug per il plugin" +#: src/modules/multiple-authors/multiple-authors.php:1176 +msgid "This forms part of the URL for the author’s profile page. If you choose a Mapped User, this URL is taken from the user’s account and can not be changed." +msgstr "Questo fa parte dell'URL della pagina del profilo dell'autore. Se scegli un utente mappato, questo URL viene preso dall'account dell'utente e non può essere modificato." -#: src/modules/debug/debug.php:97 -msgid "Authors Debug" -msgstr "Debug PublishPress Authors" +#: src/core/Classes/Term_Editor.php:56 +#: src/modules/multiple-authors/multiple-authors.php:1172 +msgid "Author URL" +msgstr "URL autore" -#: src/modules/default-layouts/default-layouts.php:54 -msgid "Default Layouts" -msgstr "Layout predefiniti" +#: src/modules/multiple-authors/multiple-authors.php:1162 +msgid "This is how the author’s name will appears on your site." +msgstr "Ecco come apparirà il nome dell'autore sul tuo sito." -#: src/modules/default-layouts/default-layouts.php:129 -msgid "View all posts" -msgstr "" +#: src/modules/multiple-authors/multiple-authors.php:1074 +msgid "Maintenance" +msgstr "Manutenzione" -#: src/modules/default-layouts/default-layouts.php:149 -msgid "Boxed" -msgstr "Riquadrato" +#: src/modules/multiple-authors/multiple-authors.php:1073 +msgid "Display" +msgstr "Visualizza" -#: src/modules/default-layouts/default-layouts.php:150 -msgid "Centered" -msgstr "Centrato" +#: src/modules/multiple-authors/multiple-authors.php:1072 +msgid "General" +msgstr "Generale" -#: src/modules/default-layouts/default-layouts.php:151 -msgid "Inline" -msgstr "In linea" +#: src/modules/multiple-authors/multiple-authors.php:959 +msgid "Please be careful clicking these buttons. Before clicking, we recommend taking a site backup in case anything goes wrong." +msgstr "Fai attenzione a fare clic su questi pulsanti. Prima di fare clic, ti consigliamo di eseguire un backup del sito nel caso in cui qualcosa possa andare storto." -#: src/modules/default-layouts/default-layouts.php:152 -msgid "Inline with avatar" -msgstr "In linea con avatar" +#: src/modules/multiple-authors/multiple-authors.php:953 +msgid "Delete all guest authors" +msgstr "Elimina tutti gli autori ospiti" -#: src/modules/default-layouts/default-layouts.php:153 -msgid "Simple list" -msgstr "Elenco semplice" +#: src/modules/multiple-authors/multiple-authors.php:951 +msgid "Delete Guest Authors" +msgstr "Elimina gli autori ospiti" -#: src/modules/divi-integration/divi-integration.php:52 -msgid "Divi Integration" -msgstr "Integrazione Divi" +#: src/modules/multiple-authors/multiple-authors.php:946 +msgid "Delete all authors mapped to users" +msgstr "Elimina tutti gli autori mappati come utenti" -#: src/modules/divi-integration/divi-integration.php:53 -msgid "Add compatibility with the Divi Theme Builder" -msgstr "Aggiungi compatibilità con il Divi Theme Builder" +#: src/modules/multiple-authors/multiple-authors.php:944 +msgid "Delete Mapped Authors" +msgstr "Elimina tutti gli autori mappati" -#: src/modules/editflow-integration/editflow-integration.php:51 -msgid "Edit Flow Integration" -msgstr "Integrazione con Edit Flow" +#: src/modules/multiple-authors/multiple-authors.php:936 +msgid "Copy Co-Authors Plus Data" +msgstr "Copia i dati Co-Authors Plus" -#: src/modules/editflow-integration/editflow-integration.php:53 -msgid "Add compatibility with the Edit Flow plugin" -msgstr "Aggiungi compatibilità con il plugin Edit Flow" +#: src/modules/multiple-authors/multiple-authors.php:909 +#: src/modules/multiple-authors/multiple-authors.php:911 +msgid "Create missed authors from role" +msgstr "Crea autori persi dal ruolo" -#: src/modules/elementor-integration/Modules/Posts/Skins/PostsSkinCards.php:38 -msgid "Cards - PublishPress Authors" -msgstr "Carte - PublishPress Authors" +#: src/modules/multiple-authors/multiple-authors.php:903 +#: src/modules/multiple-authors/multiple-authors.php:905 +msgid "Create missed post authors" +msgstr "Crea autori di articoli persi" -#: src/modules/elementor-integration/Modules/Posts/Skins/PostsSkinClassic.php:38 -msgid "Classic - PublishPress Authors" -msgstr "Classico - PublishPress Authors" +#: src/modules/multiple-authors/multiple-authors.php:884 +msgid "This will display the authors site in the author box." +msgstr "Questo visualizzerà il sito degli autori nel riquadro dell'autore." -#: src/modules/elementor-integration/Modules/Posts/Skins/PostsSkinFullContent.php:36 -msgid "Full Content - PublishPress Authors" -msgstr "Contenuto completo" +#: src/modules/multiple-authors/multiple-authors.php:864 +msgid "This will display the authors email in the author box." +msgstr "Questo visualizzerà l'indirizzo email degli autori nel riquadro dell'autore." -#: src/modules/elementor-integration/elementor-integration.php:57 -msgid "Elementor Integration" -msgstr "Integrazione Elementor" +#: src/modules/multiple-authors/multiple-authors.php:784 +msgid "Author profiles can be mapped to WordPress user accounts. This option allows you to automatically create author profiles when users are created in these roles. You can also do this for existing users by clicking the \"Create missed authors from role\" button in the Maintenance tab." +msgstr "I profili degli autori possono essere mappati agli account utente di WordPress. Questa opzione consente di creare automaticamente i profili dell'autore quando gli utenti vengono creati in questi ruoli. Puoi farlo anche per gli utenti esistenti facendo clic sul pulsante \"Crea autori mancanti dal ruolo\" nella scheda Manutenzione." -#: src/modules/elementor-integration/elementor-integration.php:59 -msgid "Add compatibility with the Elementor and Elementor Pro page builder" -msgstr "Aggiungi compatibilità con Elementor ed Elementor Pro page builder" +#: src/modules/multiple-authors/multiple-authors.php:681 +msgid "This will display the authors box at the end of the content." +msgstr "Questo visualizzerà il riquadro degli autori alla fine del contenuto." -#: src/modules/genesis-integration/genesis-integration.php:52 -msgid "Genesis Integration" -msgstr "Integrazione Genesis" +#: src/modules/multiple-authors/multiple-authors.php:567 +msgid "Show site link:" +msgstr "Mostra link del sito:" -#: src/modules/genesis-integration/genesis-integration.php:53 -msgid "Add compatibility with the Genesis framework" -msgstr "Aggiungi compatibilità con Genesis framework" +#: src/modules/multiple-authors/multiple-authors.php:559 +msgid "Show email link:" +msgstr "Mostra link email:" -#: src/modules/modules-settings/modules-settings.php:52 -msgid "Authors Settings" -msgstr "Impostazioni autori" +#: src/modules/multiple-authors/multiple-authors.php:542 +msgid "Layout:" +msgstr "Layout:" -#: src/modules/modules-settings/modules-settings.php:226 -msgid "Features" -msgstr "Funzionalità" +#: src/modules/multiple-authors/multiple-authors.php:534 +msgid "Title for the author box:" +msgstr "Titolo del riquadro autore:" -#: src/modules/modules-settings/modules-settings.php:228 -msgid "Feel free to select only the features you need." -msgstr "Puoi decidere di selezionare soltanto le funzionalità desiderate." +#: src/modules/multiple-authors/multiple-authors.php:526 +msgid "Show below the content:" +msgstr "Mostra sotto al contenuto:" -#: src/modules/modules-settings/modules-settings.php:236 -msgid "Enabled features" -msgstr "Funzionalità abilitate" +#: src/modules/multiple-authors/multiple-authors.php:480 +msgid "Automatically create author profiles:" +msgstr "Crea automaticamente i profili degli autori:" -#: src/modules/multiple-authors/multiple-authors.php:75 -msgid "Multiple Authors" -msgstr "Autori multipli" +#: src/modules/multiple-authors/multiple-authors.php:464 +msgid "Add to these post types:" +msgstr "Aggiungi questi tipi di articoli:" -#. Description of the plugin/theme -#: src/modules/multiple-authors/multiple-authors.php:77 -#: src/modules/multiple-authors/multiple-authors.php:81 -msgid "" -"PublishPress Authors allows you to add multiple authors and guest authors to " -"WordPress posts" -msgstr "" -"PublishPress Authors ti permette di aggiungere autori multipli e autori " -"ospiti agli articoli di WordPress" +#: src/modules/multiple-authors/multiple-authors.php:661 +#: src/modules/settings/settings.php:312 +msgid "Disabled because add_post_type_support('%1$s', '%2$s') is included in a loaded file." +msgstr "Disabilitato perché add_post_type_support('%1$s', '%2$s') è incluso in un file già caricato." #: src/modules/multiple-authors/multiple-authors.php:125 #: src/modules/multiple-authors/multiple-authors.php:624 @@ -752,388 +776,329 @@ msgstr "" msgid "Pages" msgstr "Pagine" -#: src/modules/multiple-authors/multiple-authors.php:464 -msgid "Add to these post types:" -msgstr "Aggiungi questi tipi di articoli:" - -#: src/modules/multiple-authors/multiple-authors.php:472 -msgid "Post types to display on the author's profile page:" -msgstr "" - -#: src/modules/multiple-authors/multiple-authors.php:481 -msgid "Automatically create author profiles:" -msgstr "Crea automaticamente i profili degli autori:" - -#: src/modules/multiple-authors/multiple-authors.php:492 -msgid "Show username in the search field:" -msgstr "Mostra il nome utente nel campo di ricerca:" - -#: src/modules/multiple-authors/multiple-authors.php:503 -msgid "Default author for new posts:" -msgstr "Autore predefinito per i nuovi articoli:" +#: src/core/Classes/Author_Editor.php:53 src/core/Plugin.php:683 +#: src/modules/multiple-authors/multiple-authors.php:124 +#: src/modules/multiple-authors/multiple-authors.php:623 +#: src/modules/settings/settings.php:289 +msgid "Posts" +msgstr "Articoli" -#: src/modules/multiple-authors/multiple-authors.php:526 -msgid "Show below the content:" -msgstr "Mostra sotto al contenuto:" +#: src/modules/settings/settings.php:222 +msgid "There are no PublishPress modules registered" +msgstr "Non ci sono moduli di PublishPress registrati" -#: src/modules/multiple-authors/multiple-authors.php:534 -msgid "Title for the author box:" -msgstr "Titolo del riquadro autore:" +#: src/modules/settings/settings.php:103 +msgid "Settings" +msgstr "Impostazioni" -#: src/modules/multiple-authors/multiple-authors.php:542 -msgid "Layout:" -msgstr "Layout:" +#: src/modules/settings/settings.php:102 +msgid "Multiple Authors Settings" +msgstr "Impostazioni autori multipli" -#: src/modules/multiple-authors/multiple-authors.php:550 -msgid "Color scheme:" -msgstr "" +#: src/core/Plugin.php:1442 +msgid "Mine" +msgstr "Miei" -#: src/modules/multiple-authors/multiple-authors.php:559 -msgid "Show email link:" -msgstr "Mostra link email:" +#: src/core/Plugin.php:1378 +msgid "Sorry, the request returned an error." +msgstr "Spiacenti, la richiesta ha restituito un errore." -#: src/modules/multiple-authors/multiple-authors.php:567 -msgid "Show site link:" -msgstr "Mostra link del sito:" +#: src/core/Plugin.php:1377 +#: src/modules/byline-migration/assets/js/byline-migration.jsx:131 +#: src/modules/bylines-migration/assets/js/bylines-migration.jsx:153 +#: src/modules/multiple-authors/assets/js/coauthors-migration.jsx:164 +#: src/modules/multiple-authors/assets/js/sync-author-slug.jsx:19 +#: src/modules/multiple-authors/assets/js/sync-post-author.jsx:19 +msgid "Please, wait..." +msgstr "Attendere prego…" -#: src/modules/multiple-authors/multiple-authors.php:661 -#: src/modules/settings/settings.php:312 -#, php-format -msgid "" -"Disabled because add_post_type_support('%1$s', '%2$s') is included in a " -"loaded file." -msgstr "" -"Disabilitato perché add_post_type_support('%1$s', '%2$s') è incluso in un " -"file già caricato." +#: src/core/Plugin.php:1371 +msgid "Are you sure you want to create authors for the selected roles?" +msgstr "Sei sicuro di voler creare degli autori per i ruoli selezionati?" -#: src/modules/multiple-authors/multiple-authors.php:682 -msgid "This will display the authors box at the end of the content." -msgstr "Questo visualizzerà il riquadro degli autori alla fine del contenuto." +#: src/core/Plugin.php:1359 +msgid "Are you sure you want to create author profiles for the missed post authors?" +msgstr "Sei sicuro di voler creare dei profili autore per gli autori di articoli persi?" -#: src/modules/multiple-authors/multiple-authors.php:709 -msgid "Single" -msgstr "" +#: src/core/Plugin.php:1355 +msgid "Are you sure you want to delete the guest authors profiles? This action can't be undone." +msgstr "Sei sicuro di voler eliminare i profili degli autori ospiti? Questa azione non può essere annullata." -#: src/modules/multiple-authors/multiple-authors.php:716 -msgid "Plural" -msgstr "" +#: src/core/Plugin.php:1351 +msgid "Are you sure you want to delete the authors profiles mapped to users? This action can't be undone." +msgstr "Sei sicuro di voler eliminare i profili degli autori mappati agli utenti? Questa azione non può essere annullata." -#: src/modules/multiple-authors/multiple-authors.php:785 -msgid "" -"Author profiles can be mapped to WordPress user accounts. This option allows " -"you to automatically create author profiles when users are created in these " -"roles. You can also do this for existing users by clicking the \"Create " -"missed authors from role\" button in the Maintenance tab." -msgstr "" -"I profili degli autori possono essere mappati agli account utente di " -"WordPress. Questa opzione consente di creare automaticamente i profili " -"dell'autore quando gli utenti vengono creati in questi ruoli. Puoi farlo " -"anche per gli utenti esistenti facendo clic sul pulsante \"Crea autori " -"mancanti dal ruolo\" nella scheda Manutenzione." +#: src/core/Plugin.php:1347 +msgid "Click on an author to change them. Drag to change their order. Click on Remove to remove them." +msgstr "Fai click su ogni autore per modificarli, puoi anche trascinarli per cambiarne l'ordine oppure fai clic su Rimuovi per rimuoverli." -#: src/modules/multiple-authors/multiple-authors.php:806 -msgid "" -"If the Author is mapped to a WordPress user, this will display the authors' " -"\"Display name\" and their \"Username\". The default is to show only the " -"\"Display name\". Showing the \"Username\" is useful if you have several " -"authors with similar names." -msgstr "" -"Se l'autore è mappato a un utente WordPress, questo mostrerà il «Nome " -"visualizzato» degli autori e il loro «Nome utente». L'impostazione " -"predefinita è mostrare solo il «Nome visualizzato». La visualizzazione del " -"«Nome utente» è utile se hai più autori con nomi simili." +#: src/core/Plugin.php:1342 +msgid "Click to change this author, or drag to change their position" +msgstr "Fai click per modificare questo autore li, oppure puoi anche trascinarlo per cambiarne la posizione" -#: src/modules/multiple-authors/multiple-authors.php:843 -msgid "This setting may be disabled for users who can not edit others posts." -msgstr "" +#: src/core/Plugin.php:1338 +msgid "Are you sure you want to remove this author?" +msgstr "Sei sicuro di voler rimuovere questo autore?" -#: src/modules/multiple-authors/multiple-authors.php:845 -msgid "Click here for more details." -msgstr "" +#: src/core/Plugin.php:1337 +msgid "Edit" +msgstr "Modifica" -#: src/modules/multiple-authors/multiple-authors.php:865 -msgid "This will display the authors email in the author box." -msgstr "" -"Questo visualizzerà l'indirizzo email degli autori nel riquadro dell'autore." +#: src/core/Plugin.php:803 +msgid "No co-author exists for that term" +msgstr "Nessun coautore esiste per quel termine" -#: src/modules/multiple-authors/multiple-authors.php:885 -msgid "This will display the authors site in the author box." -msgstr "Questo visualizzerà il sito degli autori nel riquadro dell'autore." +#: src/core/Plugin.php:765 +msgid "Click on an author to change them. Drag to change their order." +msgstr "Fai click su ogni autore per modificarli. Trascinali per cambiarne l'ordine." -#: src/modules/multiple-authors/multiple-authors.php:903 -#: src/modules/multiple-authors/multiple-authors.php:905 -msgid "Create missed post authors" -msgstr "Crea autori di articoli persi" +#: src/core/Plugin.php:625 +msgid "If you like %s please leave us a %s rating. Thank you!" +msgstr "Se sei soddisfatto di %s, lasciaci una valutazione di %s!" -#: src/modules/multiple-authors/multiple-authors.php:909 -#: src/modules/multiple-authors/multiple-authors.php:911 -msgid "Create missed authors from role" -msgstr "Crea autori persi dal ruolo" +#: src/core/Plugin.php:504 +msgid "Back to Authors" +msgstr "Torna ad autori" -#: src/modules/multiple-authors/multiple-authors.php:915 -msgid "Update author field on posts" -msgstr "Aggiorna il campo autore negli articoli" +#: src/core/Plugin.php:503 src/core/Traits/Author_box.php:143 +#: src/modules/multiple-authors/multiple-authors.php:697 +msgid "Author" +msgstr "Autore" -#: src/modules/multiple-authors/multiple-authors.php:922 -msgid "Synchronize Author slugs to User logins" -msgstr "Sincronizza gli slug dell'autore con gli accessi dell'utente" +#: src/core/Plugin.php:502 +msgid "No authors found." +msgstr "Nessun autore trovato." -#: src/modules/multiple-authors/multiple-authors.php:936 -msgid "Copy Co-Authors Plus Data" -msgstr "Copia i dati Co-Authors Plus" +#: src/core/Plugin.php:498 +msgid "Choose from the most used authors" +msgstr "Scegli tra gli autori più utilizzati" -#: src/modules/multiple-authors/multiple-authors.php:944 -msgid "Delete Mapped Authors" -msgstr "Elimina tutti gli autori mappati" +#: src/core/Plugin.php:497 +msgid "Add or remove authors" +msgstr "Aggiungi o rimuovi autori" -#: src/modules/multiple-authors/multiple-authors.php:946 -msgid "Delete all authors mapped to users" -msgstr "Elimina tutti gli autori mappati come utenti" +#: src/core/Plugin.php:493 +msgid "Separate authors with commas" +msgstr "Separare gli autori con virgole" -#: src/modules/multiple-authors/multiple-authors.php:951 -msgid "Delete Guest Authors" -msgstr "Elimina gli autori ospiti" +#: src/core/Plugin.php:491 src/core/Plugin.php:492 +msgid "New author" +msgstr "Nuovo autore" -#: src/modules/multiple-authors/multiple-authors.php:953 -msgid "Delete all guest authors" -msgstr "Elimina tutti gli autori ospiti" +#: src/core/Plugin.php:490 +msgid "Update author" +msgstr "Aggiorna autore" -#: src/modules/multiple-authors/multiple-authors.php:960 -msgid "" -"Please be careful clicking these buttons. Before clicking, we recommend " -"taking a site backup in case anything goes wrong." -msgstr "" -"Fai attenzione a fare clic su questi pulsanti. Prima di fare clic, ti " -"consigliamo di eseguire un backup del sito nel caso in cui qualcosa possa " -"andare storto." +#: src/core/Plugin.php:489 +msgid "View author" +msgstr "Visualizza autore" -#: src/modules/multiple-authors/multiple-authors.php:1072 -msgid "General" -msgstr "Generale" +#: src/core/Plugin.php:488 +msgid "Edit author" +msgstr "Modifica autore" -#: src/modules/multiple-authors/multiple-authors.php:1073 -msgid "Display" -msgstr "Visualizza" +#: src/core/Plugin.php:487 +msgid "Parent author:" +msgstr "Autore genitore:" -#: src/modules/multiple-authors/multiple-authors.php:1074 -msgid "Maintenance" -msgstr "Manutenzione" +#: src/core/Plugin.php:486 +msgid "Parent author" +msgstr "Autore genitore" -#: src/modules/multiple-authors/multiple-authors.php:1163 -msgid "This is how the author’s name will appears on your site." -msgstr "Ecco come apparirà il nome dell'autore sul tuo sito." +#: src/core/Plugin.php:485 +msgid "All authors" +msgstr "Tutti gli autori" -#: src/modules/multiple-authors/multiple-authors.php:1177 -msgid "" -"This forms part of the URL for the author’s profile page. If you choose a " -"Mapped User, this URL is taken from the user’s account and can not be " -"changed." -msgstr "" -"Questo fa parte dell'URL della pagina del profilo dell'autore. Se scegli un " -"utente mappato, questo URL viene preso dall'account dell'utente e non può " -"essere modificato." +#: src/core/Plugin.php:484 +msgid "Popular authors" +msgstr "Autori popolari" -#: src/modules/multiple-authors/multiple-authors.php:1849 -msgid "Error. Author terms could not be reseted." -msgstr "Errore. Impossibile reimpostare i termini dell'autore." +#: src/core/Plugin.php:483 +msgid "Search authors" +msgstr "Cerca autori" -#: src/modules/multiple-authors/multiple-authors.php:1859 -msgid "Maintenance completed successfully." -msgstr "La manutenzione è stata completata con successo." +#: src/core/Plugin.php:478 +msgctxt "taxonomy singular name" +msgid "Author" +msgstr "Autore" -#: src/modules/multiple-authors/multiple-authors.php:2467 -msgid "It looks like you have Co-Authors Plus installed." -msgstr "Sembra che tu hai installato anche Co-Authors Plus." +#: src/core/Plugin.php:473 +msgctxt "taxonomy general name" +msgid "Authors" +msgstr "Autori" -#: src/modules/multiple-authors/multiple-authors.php:2469 -msgid "Please click here and read this guide!" -msgstr "Fai clic qui e leggi questa guida!" +#: src/core/Classes/Legacy/Module.php:103 +msgid "Page" +msgstr "Pagina" -#: src/modules/multiple-authors/multiple-authors.php:2474 -#: src/modules/multiple-authors/multiple-authors.php:2548 -msgid "Dismiss" -msgstr "Ignora" +#: src/core/Classes/Legacy/Module.php:102 +msgid "Post" +msgstr "Articolo" -#: src/modules/multiple-authors/multiple-authors.php:2540 -msgid "" -"PublishPress Authors needs a database update for Permissions integration." -msgstr "" -"PublishPress Authors deve aggiornare il database per l'integrazione con il " -"plugin Permissions." +#: src/core/Classes/Legacy/LegacyPlugin.php:265 +msgid "Post does not exist" +msgstr "L'articolo non esiste" -#: src/modules/multiple-authors/multiple-authors.php:2542 -msgid "Click to run the update now" -msgstr "Fai clic per avviare adesso l'aggiornamento" +#: src/core/Classes/Legacy/LegacyPlugin.php:261 +msgid "You do not have necessary permissions to complete this action." +msgstr "Non hai le autorizzazioni necessarie per completare questa azione." -#: src/modules/polylang-integration/polylang-integration.php:55 -#: src/modules/polylang-integration/polylang-integration.php:56 -#: src/modules/polylang-integration/polylang-integration.php:57 -#, fuzzy -#| msgid "Elementor Integration" -msgid "Polylang Integration" -msgstr "Integrazione Elementor" +#: src/core/Classes/Legacy/LegacyPlugin.php:260 +#: src/modules/settings/settings.php:336 +msgid "Cheatin’ uh?" +msgstr "Vuoi barare, eh?" -#: src/modules/pro-placeholders/pro-placeholders.php:56 -#: src/modules/pro-placeholders/pro-placeholders.php:57 -#: src/modules/pro-placeholders/pro-placeholders.php:58 -msgid "Pro Placeholders" -msgstr "" +#: src/core/Classes/Legacy/LegacyPlugin.php:256 +msgid "Please correct your form errors below and try again." +msgstr "Correggi gli errori nel modulo sottostante e riprova." -#: src/modules/pro-placeholders/pro-placeholders.php:95 -#: src/modules/pro-placeholders/pro-placeholders.php:96 -msgid "Fields" -msgstr "" +#: src/core/Classes/Legacy/LegacyPlugin.php:253 +msgid "Configure" +msgstr "Configura" -#: src/modules/pro-placeholders/pro-placeholders.php:105 -#: src/modules/pro-placeholders/pro-placeholders.php:106 -#, fuzzy -#| msgid "Layout" -msgid "Layouts" -msgstr "Layout" +#: src/core/Classes/Author_Editor.php:622 +msgid "Updated %d authors" +msgstr "Aggiorna %d autori" -#: src/modules/pro-placeholders/views/fields-placeholder.php:2 -#, fuzzy -#| msgid "Authors List" -msgid "Author Fields" -msgstr "Lista autori" +#: src/core/Classes/Author_Editor.php:620 +msgid "No authors were updated" +msgstr "Nessun autore è stato aggiornato" -#: src/modules/pro-placeholders/views/fields-placeholder.php:2 -#, fuzzy -#| msgid "New author" -msgid "New Author Field" -msgstr "Nuovo autore" +#: src/core/Classes/Author_Editor.php:551 +msgid "Convert into guest author" +msgstr "Converti in autore ospite" -#: src/modules/pro-placeholders/views/fields-placeholder.php:11 -msgid "" -"With PublishPress Authors Pro you can create custom fields for your author " -"profiles. You can add Text, WYSIWYG, Link, email fields and more." -msgstr "" +#: src/core/Classes/Author_Editor.php:547 +msgid "Update data from mapped user" +msgstr "Aggiorna i dati da utente mappato" -#: src/modules/pro-placeholders/views/fields-placeholder.php:15 -#: src/modules/pro-placeholders/views/layouts-placeholder.php:15 -msgid "Upgrade to Pro" -msgstr "" +#: src/core/Classes/Author_Editor.php:488 +msgid "You don’t have to choose a Mapped User. Leave this choice blank and you can create a Guest Author with no WordPress account." +msgstr "Non devi scegliere un utente mappato. Lascia questa scelta vuota e puoi creare un autore ospite senza che abbia un account WordPress collegato." -#: src/modules/pro-placeholders/views/layouts-placeholder.php:2 -#, fuzzy -#| msgid "Authors List" -msgid "Author Layouts" -msgstr "Lista autori" +#: src/core/Classes/Author_Editor.php:481 +msgid "Mapped User (optional)" +msgstr "Utente mappato (opzionale)" -#: src/modules/pro-placeholders/views/layouts-placeholder.php:2 -#, fuzzy -#| msgid "New author" -msgid "New Author Layout" -msgstr "Nuovo autore" +#: src/core/Classes/Author_Editor.php:370 +msgid "Select a user" +msgstr "Seleziona un utente" -#: src/modules/pro-placeholders/views/layouts-placeholder.php:11 -msgid "" -"With PublishPress Authors Pro you can build new layouts for authors. You can " -"use author information, custom fields, and much more." -msgstr "" +#: src/core/Classes/Author_Editor.php:356 +msgid "Remove this image" +msgstr "Rimuovi questa immagine" -#: src/modules/rest-api/rest-api.php:56 -msgid "Rest API" -msgstr "" +#: src/core/Classes/Author_Editor.php:352 +msgid "Select image" +msgstr "Seleziona immagine" -#: src/modules/rest-api/rest-api.php:57 src/modules/rest-api/rest-api.php:58 -msgid "Rest API support" -msgstr "" +#: src/core/Classes/Author_Editor.php:299 +msgid "Biographical Info" +msgstr "Informazioni biografiche" -#: src/modules/rest-api/rest-api.php:95 -#, fuzzy -#| msgid "Authors" -msgid "Authors." -msgstr "Autori" +#: src/core/Classes/Author_Editor.php:294 +msgid "Website" +msgstr "Sito web" -#: src/modules/reviews/reviews.php:74 -msgid "Reviews" -msgstr "" +#: src/core/Classes/Author_Editor.php:289 +msgid "Custom Avatar" +msgstr "Avatar personalizzato" -#: src/modules/seoframework-integration/seoframework-integration.php:58 -#, fuzzy -#| msgid "Elementor Integration" -msgid "The SEO Framework Integration" -msgstr "Integrazione Elementor" +#: src/core/Classes/Author_Editor.php:283 +msgid "To show the avatar from the Mapped User, enter the same email address as the Mapped User.
To show the avatar for a Guest Author, enter the email for their Gravatar account." +msgstr "Per mostrare l'avatar dell'utente mappato, immettere lo stesso indirizzo email dell'utente mappato.
Per mostrare l'avatar di un autore ospite, inserisci l'email del suo account Gravatar." -#: src/modules/seoframework-integration/seoframework-integration.php:60 -#, fuzzy -#| msgid "Add compatibility with the Edit Flow plugin" -msgid "Add compatibility with The SEO Framework plugin." -msgstr "Aggiungi compatibilità con il plugin Edit Flow" +#: src/core/Classes/Author_Editor.php:277 +msgid "Last Name" +msgstr "Cognome" -#: src/modules/settings/settings.php:102 -msgid "Multiple Authors Settings" -msgstr "Impostazioni autori multipli" +#: src/core/Classes/Author_Editor.php:273 +msgid "First Name" +msgstr "Nome" -#: src/modules/settings/settings.php:103 -msgid "Settings" -msgstr "Impostazioni" +#: src/core/Classes/Author_Editor.php:268 +msgid "Mapped User" +msgstr "Utente mappato" -#: src/modules/settings/settings.php:222 -msgid "There are no PublishPress modules registered" -msgstr "Non ci sono moduli di PublishPress registrati" +#: src/core/Classes/Author_Editor.php:153 +#: src/core/Classes/Author_Editor.php:201 +msgid "Edit Author Profile" +msgstr "Modifica profilo autore" -#: src/modules/ultimatemember-integration/ultimatemember-integration.php:53 -msgid "Ultimate Member Integration" -msgstr "Integrazione Ultimate Member" +#: src/core/Classes/Author_Editor.php:139 +#: src/core/Classes/Author_Editor.php:216 +msgid "Edit User" +msgstr "Modifica utente" -#: src/modules/ultimatemember-integration/ultimatemember-integration.php:54 -msgid "Add compatibility with the Ultimate Member plugin" -msgstr "Aggiungi compatibilità con il plugin Ultimate Member" +#: src/core/Classes/Author_Editor.php:95 +msgid "Guest Author" +msgstr "Autore ospite" -#: src/modules/wpengine-integration/wpengine-integration.php:51 -#, fuzzy -#| msgid "Divi Integration" -msgid "WPEngine Integration" -msgstr "Integrazione Divi" +#: src/core/Classes/Author_Editor.php:93 +msgid "User" +msgstr "Utente" -#: src/modules/wpengine-integration/wpengine-integration.php:53 -#, fuzzy -#| msgid "Add compatibility with the Edit Flow plugin" -msgid "Add compatibility with the WPEngine object cache." -msgstr "Aggiungi compatibilità con il plugin Edit Flow" +#: src/core/Classes/Author_Editor.php:44 src/core/Classes/Author_Editor.php:281 +msgid "Email" +msgstr "Email" -#: src/modules/yoast-seo-integration/yoast-seo-integration.php:52 -msgid "Yoast SEO Integration" -msgstr "Integrazione Yoast SEO" +#: src/core/Classes/Author_Editor.php:43 +msgid "Name" +msgstr "Nome" -#: src/modules/yoast-seo-integration/yoast-seo-integration.php:53 -msgid "Add compatibility with the Yoast SEO plugin" -msgstr "Aggiungi compatibilità con il plugin Yoast SEO" +#: src/core/Classes/Authors_Iterator.php:55 +msgid "No post ID provided for Authors_Iterator constructor. Are you not in a loop or is $post not set?" +msgstr "Nessun ID articolo fornito per il costruttore Authors_Iterator. Non sei in loop o $post non è impostato?" -#. Plugin URI of the plugin/theme -msgid "https://wordpress.org/plugins/publishpress-authors/" -msgstr "https://wordpress.org/plugins/publishpress-authors/" +#: src/core/Classes/Integrations/Theme.php:40 +msgid "Author: %s" +msgstr "Autore: %s" -#. Author of the plugin/theme -msgid "PublishPress" -msgstr "PublishPress" +#: src/core/Classes/Post_Editor.php:269 src/core/Plugin.php:1346 +#: src/modules/multiple-authors/multiple-authors.php:830 +msgid "Search for an author" +msgstr "Cerca un autore" -#. Author URI of the plugin/theme -msgid "https://publishpress.com" -msgstr "https://publishpress.com" +#: src/core/Classes/Utils.php:73 +msgid "Co-Authors Plus must be installed and active." +msgstr "Co-Authors Plus deve essere installato e attivato." -#~ msgid "Uncategorized" -#~ msgstr "Senza categoria" +#: src/core/Authors_Widget.php:108 src/core/Widget.php:123 +msgid "Layout" +msgstr "Layout" -#~ msgid "Create Author" -#~ msgstr "Crea autore" +#: src/core/Authors_Widget.php:107 +msgid "Title" +msgstr "Titolo" -#~ msgid "Edit Author" -#~ msgstr "Modifica autore" +#: src/modules/multiple-authors/multiple-authors.php:75 +msgid "Multiple Authors" +msgstr "Autori multipli" -#~ msgid "All done! %d posts were affected." -#~ msgstr "Tutto fatto! %d articoli sono stati interessati." +#: src/core/Widget.php:48 +msgid "Display a list of authors for the current post." +msgstr "Visualizza un elenco degli autori per l'articolo corrente." -#~ msgid "Updating - Adding %s's byline to post #%d" -#~ msgstr "Aggiornando - Aggiungendo info autore di %s all'articolo #%d" +#: src/core/Classes/Post_Editor.php:89 src/core/Classes/Post_Editor.php:192 +#: src/core/Plugin.php:762 src/core/Traits/Author_box.php:149 +#: src/modules/editflow-integration/editflow-integration.php:113 +#: src/modules/multiple-authors/multiple-authors.php:264 +#: src/modules/multiple-authors/multiple-authors.php:265 +#: src/modules/multiple-authors/multiple-authors.php:296 +#: src/modules/multiple-authors/multiple-authors.php:297 +#: src/modules/multiple-authors/multiple-authors.php:703 +msgid "Authors" +msgstr "Autori" -#~ msgid "Skipping - Post #%d already has co-authors assigned: %s" -#~ msgstr "Saltando - L'articolo #%d ha già coautori assegnati: %s" +#. Author URI of the plugin +msgid "https://publishpress.com" +msgstr "https://publishpress.com" -#~ msgid "Please specify a valid co-author login" -#~ msgstr "Specifica un accesso coautore valido" +#. Author of the plugin +msgid "PublishPress" +msgstr "PublishPress" -#~ msgid "Please specify a valid user_login" -#~ msgstr "Specifica un valido user_login" +#. Plugin Name of the plugin +#: src/core/Plugin.php:622 src/modules/settings/settings.php:59 +msgid "PublishPress Authors" +msgstr "PublishPress Authors" diff --git a/languages/publishpress-authors.pot b/languages/publishpress-authors.pot index b1f9eed7..2fd69215 100644 --- a/languages/publishpress-authors.pot +++ b/languages/publishpress-authors.pot @@ -1,16 +1,16 @@ #, fuzzy msgid "" msgstr "" -"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" "Project-Id-Version: PublishPress Authors\n" -"POT-Creation-Date: 2021-11-04 15:04-0300\n" +"POT-Creation-Date: 2022-03-22 18:17-0300\n" "PO-Revision-Date: 2019-11-07 12:27-0300\n" "Last-Translator: Anderson Grudtner Martins \n" "Language-Team: Anderson Grudtner Martins \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"X-Generator: Poedit 3.0\n" +"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n" +"X-Generator: Poedit 3.0.1\n" "X-Poedit-Basepath: ..\n" "X-Poedit-Flags-xgettext: --add-comments=translators:\n" "X-Poedit-WPHeader: publishpress-authors.php\n" @@ -25,101 +25,101 @@ msgstr "" "X-Poedit-SearchPathExcluded-5: *.min.js\n" "X-Poedit-SearchPathExcluded-6: src/assets/lib\n" -#: publishpress-authors.php:110 +#: publishpress-authors.php:113 #, php-format msgid "New comment on your post \"%s\"" msgstr "" -#: publishpress-authors.php:113 +#: publishpress-authors.php:116 #, php-format msgid "Author : %1$s (IP: %2$s , %3$s)" msgstr "" -#: publishpress-authors.php:118 +#: publishpress-authors.php:121 #, php-format msgid "E-mail : %s" msgstr "" -#: publishpress-authors.php:119 publishpress-authors.php:137 -#: publishpress-authors.php:151 +#: publishpress-authors.php:122 publishpress-authors.php:140 +#: publishpress-authors.php:154 #, php-format msgid "URL : %s" msgstr "" -#: publishpress-authors.php:121 +#: publishpress-authors.php:124 #, php-format msgid "Whois : http://whois.arin.net/rest/ip/%s" msgstr "" -#: publishpress-authors.php:124 +#: publishpress-authors.php:127 msgid "Comment: " msgstr "" -#: publishpress-authors.php:125 +#: publishpress-authors.php:128 msgid "You can see all comments on this post here: " msgstr "" #. translators: 1: blog name, 2: post title -#: publishpress-authors.php:127 +#: publishpress-authors.php:130 #, php-format msgid "[%1$s] Comment: \"%2$s\"" msgstr "" -#: publishpress-authors.php:129 +#: publishpress-authors.php:132 #, php-format msgid "New trackback on your post \"%s\"" msgstr "" -#: publishpress-authors.php:132 publishpress-authors.php:146 +#: publishpress-authors.php:135 publishpress-authors.php:149 #, php-format msgid "Website: %1$s (IP: %2$s , %3$s)" msgstr "" -#: publishpress-authors.php:138 publishpress-authors.php:152 +#: publishpress-authors.php:141 publishpress-authors.php:155 msgid "Excerpt: " msgstr "" -#: publishpress-authors.php:139 +#: publishpress-authors.php:142 msgid "You can see all trackbacks on this post here: " msgstr "" #. translators: 1: blog name, 2: post title -#: publishpress-authors.php:141 +#: publishpress-authors.php:144 #, php-format msgid "[%1$s] Trackback: \"%2$s\"" msgstr "" -#: publishpress-authors.php:143 +#: publishpress-authors.php:146 #, php-format msgid "New pingback on your post \"%s\"" msgstr "" -#: publishpress-authors.php:156 +#: publishpress-authors.php:159 msgid "You can see all pingbacks on this post here: " msgstr "" #. translators: 1: blog name, 2: post title -#: publishpress-authors.php:158 +#: publishpress-authors.php:161 #, php-format msgid "[%1$s] Pingback: \"%2$s\"" msgstr "" -#: publishpress-authors.php:162 +#: publishpress-authors.php:165 #, php-format msgid "Permalink: %s" msgstr "" -#: publishpress-authors.php:167 +#: publishpress-authors.php:170 #, php-format msgid "Trash it: %s" msgstr "" -#: publishpress-authors.php:172 +#: publishpress-authors.php:175 #, php-format msgid "Delete it: %s" msgstr "" -#: publishpress-authors.php:177 +#: publishpress-authors.php:180 #, php-format msgid "Spam it: %s" msgstr "" @@ -144,156 +144,204 @@ msgstr "" msgid "Display All Authors (including those who have not written any posts)" msgstr "" -#: src/core/Classes/Author_Editor.php:43 +#: src/core/Classes/Admin_Ajax.php:236 +msgid "Request status." +msgstr "" + +#: src/core/Classes/Admin_Ajax.php:244 +msgid "Security error. Kindly reload this page and try again" +msgstr "" + +#: src/core/Classes/Admin_Ajax.php:258 src/core/Classes/Author_Editor.php:807 +msgid "This user is already mapped to another author." +msgstr "" + +#: src/core/Classes/Admin_Ajax.php:267 +msgid "Author URL cannot be empty." +msgstr "" + +#: src/core/Classes/Admin_Ajax.php:281 +msgid "Another user with Author URL already exists." +msgstr "" + +#: src/core/Classes/Author_Editor.php:47 msgid "Name" msgstr "" -#: src/core/Classes/Author_Editor.php:44 src/core/Classes/Author_Editor.php:281 +#: src/core/Classes/Author_Editor.php:48 src/core/Classes/Author_Editor.php:352 msgid "Email" msgstr "" -#: src/core/Classes/Author_Editor.php:53 src/core/Plugin.php:683 -#: src/modules/multiple-authors/multiple-authors.php:124 -#: src/modules/multiple-authors/multiple-authors.php:623 -#: src/modules/settings/settings.php:289 +#: src/core/Classes/Author_Editor.php:57 src/core/Plugin.php:720 +#: src/modules/multiple-authors/multiple-authors.php:122 +#: src/modules/multiple-authors/multiple-authors.php:665 +#: src/modules/settings/settings.php:248 msgid "Posts" msgstr "" -#: src/core/Classes/Author_Editor.php:55 src/core/Plugin.php:685 +#: src/core/Classes/Author_Editor.php:59 src/core/Plugin.php:722 #, php-format msgid "Published posts of the following post types: %s" msgstr "" -#: src/core/Classes/Author_Editor.php:93 +#: src/core/Classes/Author_Editor.php:97 msgid "User" msgstr "" -#: src/core/Classes/Author_Editor.php:96 +#: src/core/Classes/Author_Editor.php:100 msgid "Guest Author" msgstr "" -#: src/core/Classes/Author_Editor.php:139 -#: src/core/Classes/Author_Editor.php:217 +#: src/core/Classes/Author_Editor.php:143 +#: src/core/Classes/Author_Editor.php:221 msgid "Edit User" msgstr "" -#: src/core/Classes/Author_Editor.php:154 -#: src/core/Classes/Author_Editor.php:201 +#: src/core/Classes/Author_Editor.php:158 +#: src/core/Classes/Author_Editor.php:205 msgid "Edit Author Profile" msgstr "" -#: src/core/Classes/Author_Editor.php:168 +#: src/core/Classes/Author_Editor.php:172 msgid "Create Author Profile" msgstr "" -#: src/core/Classes/Author_Editor.php:268 +#: src/core/Classes/Author_Editor.php:258 +msgid "tab-link nav-tab" +msgstr "" + +#: src/core/Classes/Author_Editor.php:307 +#: src/modules/multiple-authors/multiple-authors.php:1115 +msgid "General" +msgstr "" + +#: src/core/Classes/Author_Editor.php:310 +msgid "Image" +msgstr "" + +#: src/core/Classes/Author_Editor.php:336 msgid "Mapped User" msgstr "" -#: src/core/Classes/Author_Editor.php:273 +#: src/core/Classes/Author_Editor.php:342 msgid "First Name" msgstr "" -#: src/core/Classes/Author_Editor.php:277 +#: src/core/Classes/Author_Editor.php:347 msgid "Last Name" msgstr "" -#: src/core/Classes/Author_Editor.php:284 -msgid "To show the avatar from the Mapped User, enter the same email address as the Mapped User.
To show the avatar for a Guest Author, enter the email for their Gravatar account." +#: src/core/Classes/Author_Editor.php:357 +msgid "Avatar Source" +msgstr "" + +#: src/core/Classes/Author_Editor.php:363 +msgid "Gravatar" +msgstr "" + +#: src/core/Classes/Author_Editor.php:366 +#, php-format +msgid "(Uses the %sauthor e-mail%s as Gravatar account)" msgstr "" -#: src/core/Classes/Author_Editor.php:289 -msgid "Custom Avatar" +#: src/core/Classes/Author_Editor.php:373 +msgid "Custom image" msgstr "" -#: src/core/Classes/Author_Editor.php:294 +#: src/core/Classes/Author_Editor.php:378 msgid "Website" msgstr "" -#: src/core/Classes/Author_Editor.php:299 +#: src/core/Classes/Author_Editor.php:384 msgid "Biographical Info" msgstr "" -#: src/core/Classes/Author_Editor.php:352 +#: src/core/Classes/Author_Editor.php:446 +#: src/core/Classes/Author_Editor.php:495 msgid "Select image" msgstr "" -#: src/core/Classes/Author_Editor.php:356 +#: src/core/Classes/Author_Editor.php:450 +#: src/core/Classes/Author_Editor.php:499 msgid "Remove this image" msgstr "" -#: src/core/Classes/Author_Editor.php:370 +#: src/core/Classes/Author_Editor.php:513 msgid "Select a user" msgstr "" -#: src/core/Classes/Author_Editor.php:481 +#: src/core/Classes/Author_Editor.php:627 msgid "Mapped User (optional)" msgstr "" -#: src/core/Classes/Author_Editor.php:489 +#: src/core/Classes/Author_Editor.php:635 msgid "You don’t have to choose a Mapped User. Leave this choice blank and you can create a Guest Author with no WordPress account." msgstr "" -#: src/core/Classes/Author_Editor.php:548 +#: src/core/Classes/Author_Editor.php:694 msgid "Update data from mapped user" msgstr "" -#: src/core/Classes/Author_Editor.php:552 +#: src/core/Classes/Author_Editor.php:698 msgid "Convert into guest author" msgstr "" -#: src/core/Classes/Author_Editor.php:556 +#: src/core/Classes/Author_Editor.php:702 msgid "Update post count" msgstr "" -#: src/core/Classes/Author_Editor.php:620 +#: src/core/Classes/Author_Editor.php:766 msgid "No authors were updated" msgstr "" -#: src/core/Classes/Author_Editor.php:622 +#: src/core/Classes/Author_Editor.php:769 #, php-format msgid "Updated %d authors" msgstr "" -#: src/core/Classes/Authors_Iterator.php:33 +#: src/core/Classes/Author_Editor.php:836 +msgid "An author with the name provided already exists." +msgstr "" + +#: src/core/Classes/Authors_Iterator.php:56 msgid "No post ID provided for Authors_Iterator constructor. Are you not in a loop or is $post not set?" msgstr "" -#: src/core/Classes/Installer.php:153 +#: src/core/Classes/Installer.php:154 #, php-format msgid "Now inspecting or updating %d total authors" msgstr "" -#: src/core/Classes/Installer.php:167 +#: src/core/Classes/Installer.php:168 #, php-format msgid "%d/%d: Inspecting the user %d" msgstr "" -#: src/core/Classes/Installer.php:179 +#: src/core/Classes/Installer.php:180 msgid "All is set. No author need to be updated" msgstr "" -#: src/core/Classes/Installer.php:260 +#: src/core/Classes/Installer.php:261 #, php-format msgid "Now inspecting or updating %d total posts" msgstr "" -#: src/core/Classes/Installer.php:272 +#: src/core/Classes/Installer.php:273 #, php-format msgid "%d/%d: Inspecting the post %d" msgstr "" -#: src/core/Classes/Installer.php:286 +#: src/core/Classes/Installer.php:287 #, php-format msgid "Creating author term for the user %d" msgstr "" -#: src/core/Classes/Installer.php:299 +#: src/core/Classes/Installer.php:300 #, php-format msgid "Adding the author term %d to the post %d" msgstr "" -#: src/core/Classes/Installer.php:318 +#: src/core/Classes/Installer.php:319 msgid "All is set. No posts need to be updated" msgstr "" @@ -302,24 +350,24 @@ msgstr "" msgid "Author: %s" msgstr "" -#: src/core/Classes/Legacy/LegacyPlugin.php:253 +#: src/core/Classes/Legacy/LegacyPlugin.php:260 msgid "Configure" msgstr "" -#: src/core/Classes/Legacy/LegacyPlugin.php:257 +#: src/core/Classes/Legacy/LegacyPlugin.php:264 msgid "Please correct your form errors below and try again." msgstr "" -#: src/core/Classes/Legacy/LegacyPlugin.php:260 -#: src/modules/settings/settings.php:336 +#: src/core/Classes/Legacy/LegacyPlugin.php:267 +#: src/modules/settings/settings.php:296 msgid "Cheatin’ uh?" msgstr "" -#: src/core/Classes/Legacy/LegacyPlugin.php:262 +#: src/core/Classes/Legacy/LegacyPlugin.php:269 msgid "You do not have necessary permissions to complete this action." msgstr "" -#: src/core/Classes/Legacy/LegacyPlugin.php:265 +#: src/core/Classes/Legacy/LegacyPlugin.php:272 msgid "Post does not exist" msgstr "" @@ -332,13 +380,13 @@ msgid "Page" msgstr "" #: src/core/Classes/Post_Editor.php:89 src/core/Classes/Post_Editor.php:192 -#: src/core/Plugin.php:762 src/core/Traits/Author_box.php:150 +#: src/core/Plugin.php:800 src/core/Traits/Author_box.php:154 #: src/modules/editflow-integration/editflow-integration.php:113 -#: src/modules/multiple-authors/multiple-authors.php:264 -#: src/modules/multiple-authors/multiple-authors.php:265 -#: src/modules/multiple-authors/multiple-authors.php:296 -#: src/modules/multiple-authors/multiple-authors.php:297 -#: src/modules/multiple-authors/multiple-authors.php:704 +#: src/modules/multiple-authors/multiple-authors.php:269 +#: src/modules/multiple-authors/multiple-authors.php:270 +#: src/modules/multiple-authors/multiple-authors.php:320 +#: src/modules/multiple-authors/multiple-authors.php:321 +#: src/modules/multiple-authors/multiple-authors.php:746 msgid "Authors" msgstr "" @@ -350,21 +398,21 @@ msgstr "" msgid "\"post_author\" is empty" msgstr "" -#: src/core/Classes/Post_Editor.php:264 src/core/Plugin.php:1346 -#: src/modules/multiple-authors/multiple-authors.php:830 +#: src/core/Classes/Post_Editor.php:268 src/core/Plugin.php:1395 +#: src/modules/multiple-authors/multiple-authors.php:873 msgid "Search for an author" msgstr "" -#: src/core/Classes/Post_Editor.php:286 +#: src/core/Classes/Post_Editor.php:290 msgid "This option is showing because you do not have a WordPress user selected as an author. For some tasks, it can be helpful to have a user selected here. This user will not be visible on the front of your site." msgstr "" -#: src/core/Classes/Post_Editor.php:293 +#: src/core/Classes/Post_Editor.php:297 msgid "Search for an user" msgstr "" #: src/core/Classes/Term_Editor.php:56 -#: src/modules/multiple-authors/multiple-authors.php:1172 +#: src/modules/multiple-authors/multiple-authors.php:1205 msgid "Author URL" msgstr "" @@ -372,152 +420,164 @@ msgstr "" msgid "Co-Authors Plus must be installed and active." msgstr "" -#: src/core/Plugin.php:474 +#: src/core/Plugin.php:481 +msgid "Edit My Author Profile" +msgstr "" + +#: src/core/Plugin.php:486 +msgid "This is the name that will show on the site." +msgstr "" + +#: src/core/Plugin.php:491 +msgid "This forms part of the URL for the author’s profile page. If you choose a Mapped User, this URL is taken from the user’s account and can not be changed." +msgstr "" + +#: src/core/Plugin.php:507 msgctxt "taxonomy general name" msgid "Authors" msgstr "" -#: src/core/Plugin.php:479 +#: src/core/Plugin.php:512 msgctxt "taxonomy singular name" msgid "Author" msgstr "" -#: src/core/Plugin.php:483 -msgid "Search authors" +#: src/core/Plugin.php:516 +msgid "Search Authors" msgstr "" -#: src/core/Plugin.php:484 -msgid "Popular authors" +#: src/core/Plugin.php:517 +msgid "Popular Authors" msgstr "" -#: src/core/Plugin.php:485 -msgid "All authors" +#: src/core/Plugin.php:518 +msgid "All Authors" msgstr "" -#: src/core/Plugin.php:486 -msgid "Parent author" +#: src/core/Plugin.php:519 +msgid "Parent Author" msgstr "" -#: src/core/Plugin.php:487 -msgid "Parent author:" +#: src/core/Plugin.php:520 +msgid "Parent Author:" msgstr "" -#: src/core/Plugin.php:488 -msgid "Edit author" +#: src/core/Plugin.php:521 +msgid "Edit Author" msgstr "" -#: src/core/Plugin.php:489 -msgid "View author" +#: src/core/Plugin.php:522 +msgid "View Author" msgstr "" -#: src/core/Plugin.php:490 -msgid "Update author" +#: src/core/Plugin.php:523 +msgid "Update Author" msgstr "" -#: src/core/Plugin.php:491 src/core/Plugin.php:492 -msgid "New author" +#: src/core/Plugin.php:524 src/core/Plugin.php:525 +msgid "New Author" msgstr "" -#: src/core/Plugin.php:494 +#: src/core/Plugin.php:527 msgid "Separate authors with commas" msgstr "" -#: src/core/Plugin.php:497 +#: src/core/Plugin.php:530 msgid "Add or remove authors" msgstr "" -#: src/core/Plugin.php:499 -msgid "Choose from the most used authors" +#: src/core/Plugin.php:532 +msgid "Choose from the most used Authors" msgstr "" -#: src/core/Plugin.php:502 +#: src/core/Plugin.php:535 msgid "No authors found." msgstr "" -#: src/core/Plugin.php:503 src/core/Traits/Author_box.php:144 -#: src/modules/multiple-authors/multiple-authors.php:698 +#: src/core/Plugin.php:536 src/core/Traits/Author_box.php:148 +#: src/modules/multiple-authors/multiple-authors.php:740 msgid "Author" msgstr "" -#: src/core/Plugin.php:504 +#: src/core/Plugin.php:537 msgid "Back to Authors" msgstr "" #. Plugin Name of the plugin/theme -#: src/core/Plugin.php:622 src/modules/settings/settings.php:59 +#: src/core/Plugin.php:655 src/modules/settings/settings.php:61 msgid "PublishPress Authors" msgstr "" -#: src/core/Plugin.php:626 +#: src/core/Plugin.php:659 #, php-format msgid "If you like %s please leave us a %s rating. Thank you!" msgstr "" #. translators: %s: Number of posts. -#: src/core/Plugin.php:714 +#: src/core/Plugin.php:750 #, php-format msgid "%s post by this author" msgid_plural "%s posts by this author" msgstr[0] "" msgstr[1] "" -#: src/core/Plugin.php:766 +#: src/core/Plugin.php:804 msgid "Click on an author to change them. Drag to change their order." msgstr "" -#: src/core/Plugin.php:803 +#: src/core/Plugin.php:842 msgid "No co-author exists for that term" msgstr "" -#: src/core/Plugin.php:1337 +#: src/core/Plugin.php:1386 msgid "Edit" msgstr "" -#: src/core/Plugin.php:1339 +#: src/core/Plugin.php:1388 msgid "Are you sure you want to remove this author?" msgstr "" -#: src/core/Plugin.php:1343 +#: src/core/Plugin.php:1392 msgid "Click to change this author, or drag to change their position" msgstr "" -#: src/core/Plugin.php:1348 +#: src/core/Plugin.php:1397 msgid "Click on an author to change them. Drag to change their order. Click on Remove to remove them." msgstr "" -#: src/core/Plugin.php:1352 +#: src/core/Plugin.php:1401 msgid "Are you sure you want to delete the authors profiles mapped to users? This action can't be undone." msgstr "" -#: src/core/Plugin.php:1356 +#: src/core/Plugin.php:1405 msgid "Are you sure you want to delete the guest authors profiles? This action can't be undone." msgstr "" -#: src/core/Plugin.php:1360 +#: src/core/Plugin.php:1409 msgid "Are you sure you want to create author profiles for the missed post authors?" msgstr "" -#: src/core/Plugin.php:1364 +#: src/core/Plugin.php:1413 msgid "Are you sure you want to update the author column for all the posts?" msgstr "" -#: src/core/Plugin.php:1368 +#: src/core/Plugin.php:1417 msgid "Are you sure you want to update the author slug for all the users?" msgstr "" -#: src/core/Plugin.php:1372 +#: src/core/Plugin.php:1421 msgid "Are you sure you want to create authors for the selected roles?" msgstr "" -#: src/core/Plugin.php:1377 +#: src/core/Plugin.php:1426 msgid "Please, wait..." msgstr "" -#: src/core/Plugin.php:1379 +#: src/core/Plugin.php:1428 msgid "Sorry, the request returned an error." msgstr "" -#: src/core/Plugin.php:1443 +#: src/core/Plugin.php:1498 msgid "Mine" msgstr "" @@ -546,52 +606,53 @@ msgstr "" msgid "Plural Title" msgstr "" -#: src/functions/template-tags.php:295 src/functions/template-tags.php:917 +#: src/functions/template-tags.php:320 src/functions/template-tags.php:940 msgid " and " msgstr "" -#: src/functions/template-tags.php:445 +#: src/functions/template-tags.php:470 +#: src/modules/multiple-authors/multiple-authors.php:1135 #, php-format msgid "Posts by %s" msgstr "" -#: src/functions/template-tags.php:629 src/functions/template-tags.php:887 +#: src/functions/template-tags.php:654 src/functions/template-tags.php:910 #, php-format msgid "Visit %s’s website" msgstr "" -#: src/functions/template-tags.php:832 +#: src/functions/template-tags.php:855 #, php-format msgid "Posts by %1$s" msgstr "" -#: src/functions/template-tags.php:918 +#: src/functions/template-tags.php:941 msgid ", and " msgstr "" -#: src/modules/byline-migration/byline-migration.php:71 +#: src/modules/byline-migration/byline-migration.php:72 msgid "Migrate Byline Data" msgstr "" -#: src/modules/byline-migration/byline-migration.php:72 #: src/modules/byline-migration/byline-migration.php:73 +#: src/modules/byline-migration/byline-migration.php:74 msgid "Add migration option for Byline" msgstr "" -#: src/modules/byline-migration/byline-migration.php:157 +#: src/modules/byline-migration/byline-migration.php:158 msgid "Copy Byline Data" msgstr "" -#: src/modules/bylines-migration/bylines-migration.php:74 +#: src/modules/bylines-migration/bylines-migration.php:75 msgid "Migrate Bylines Data" msgstr "" -#: src/modules/bylines-migration/bylines-migration.php:75 #: src/modules/bylines-migration/bylines-migration.php:76 +#: src/modules/bylines-migration/bylines-migration.php:77 msgid "Add migration option for Bylines" msgstr "" -#: src/modules/bylines-migration/bylines-migration.php:159 +#: src/modules/bylines-migration/bylines-migration.php:160 msgid "Copy Bylines Data" msgstr "" @@ -611,27 +672,27 @@ msgstr "" msgid "Default Layouts" msgstr "" -#: src/modules/default-layouts/default-layouts.php:129 +#: src/modules/default-layouts/default-layouts.php:133 msgid "View all posts" msgstr "" -#: src/modules/default-layouts/default-layouts.php:149 +#: src/modules/default-layouts/default-layouts.php:153 msgid "Boxed" msgstr "" -#: src/modules/default-layouts/default-layouts.php:150 +#: src/modules/default-layouts/default-layouts.php:154 msgid "Centered" msgstr "" -#: src/modules/default-layouts/default-layouts.php:151 +#: src/modules/default-layouts/default-layouts.php:155 msgid "Inline" msgstr "" -#: src/modules/default-layouts/default-layouts.php:152 +#: src/modules/default-layouts/default-layouts.php:156 msgid "Inline with avatar" msgstr "" -#: src/modules/default-layouts/default-layouts.php:153 +#: src/modules/default-layouts/default-layouts.php:157 msgid "Simple list" msgstr "" @@ -651,7 +712,7 @@ msgstr "" msgid "Add compatibility with the Edit Flow plugin" msgstr "" -#: src/modules/elementor-integration/Modules/Posts/Skins/PostsSkinCards.php:38 +#: src/modules/elementor-integration/Modules/Posts/Skins/PostsSkinCards.php:40 msgid "Cards - PublishPress Authors" msgstr "" @@ -679,212 +740,237 @@ msgstr "" msgid "Add compatibility with the Genesis framework" msgstr "" -#: src/modules/modules-settings/modules-settings.php:52 +#: src/modules/modules-settings/modules-settings.php:54 msgid "Authors Settings" msgstr "" -#: src/modules/modules-settings/modules-settings.php:226 +#: src/modules/modules-settings/modules-settings.php:231 msgid "Features" msgstr "" -#: src/modules/modules-settings/modules-settings.php:228 +#: src/modules/modules-settings/modules-settings.php:233 msgid "Feel free to select only the features you need." msgstr "" -#: src/modules/modules-settings/modules-settings.php:236 +#: src/modules/modules-settings/modules-settings.php:241 msgid "Enabled features" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:75 +#: src/modules/modules-settings/modules-settings.php:282 +msgid "Recommendations for you" +msgstr "" + +#: src/modules/modules-settings/modules-settings.php:283 +msgid "Showcase your Authors with PublishPress Blocks" +msgstr "" + +#: src/modules/modules-settings/modules-settings.php:285 +msgid "PublishPress Blocks is a free plugin with full support for PublishPress Authors." +msgstr "" + +#: src/modules/modules-settings/modules-settings.php:286 +msgid "Install this plugin to showcase content by your Authors." +msgstr "" + +#: src/modules/modules-settings/modules-settings.php:287 +msgid "Use the Content Display block to show your posts in many beautiful layouts." +msgstr "" + +#: src/modules/modules-settings/modules-settings.php:288 +msgid "PublishPress Blocks has over 20 extra Gutenberg blocks including accordions, galleries, tables, and more." +msgstr "" + +#: src/modules/modules-settings/modules-settings.php:291 +msgid "Click here to install PublishPress Blocks" +msgstr "" + +#: src/modules/multiple-authors/multiple-authors.php:73 msgid "Multiple Authors" msgstr "" #. Description of the plugin/theme -#: src/modules/multiple-authors/multiple-authors.php:77 -#: src/modules/multiple-authors/multiple-authors.php:81 +#: src/modules/multiple-authors/multiple-authors.php:75 +#: src/modules/multiple-authors/multiple-authors.php:79 msgid "PublishPress Authors allows you to add multiple authors and guest authors to WordPress posts" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:125 -#: src/modules/multiple-authors/multiple-authors.php:624 -#: src/modules/settings/settings.php:290 +#: src/modules/multiple-authors/multiple-authors.php:123 +#: src/modules/multiple-authors/multiple-authors.php:666 +#: src/modules/settings/settings.php:249 msgid "Pages" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:464 +#: src/modules/multiple-authors/multiple-authors.php:286 +#: src/modules/multiple-authors/multiple-authors.php:287 +msgid "Author Profile" +msgstr "" + +#: src/modules/multiple-authors/multiple-authors.php:506 msgid "Add to these post types:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:472 +#: src/modules/multiple-authors/multiple-authors.php:514 msgid "Post types to display on the author's profile page:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:481 +#: src/modules/multiple-authors/multiple-authors.php:523 msgid "Automatically create author profiles:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:492 +#: src/modules/multiple-authors/multiple-authors.php:534 msgid "Show username in the search field:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:503 +#: src/modules/multiple-authors/multiple-authors.php:545 msgid "Default author for new posts:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:526 +#: src/modules/multiple-authors/multiple-authors.php:568 msgid "Show below the content:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:534 +#: src/modules/multiple-authors/multiple-authors.php:576 msgid "Title for the author box:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:542 +#: src/modules/multiple-authors/multiple-authors.php:584 msgid "Layout:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:550 +#: src/modules/multiple-authors/multiple-authors.php:592 msgid "Color scheme:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:559 +#: src/modules/multiple-authors/multiple-authors.php:601 msgid "Show email link:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:567 +#: src/modules/multiple-authors/multiple-authors.php:609 msgid "Show site link:" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:661 -#: src/modules/settings/settings.php:312 +#: src/modules/multiple-authors/multiple-authors.php:703 +#: src/modules/settings/settings.php:271 #, php-format msgid "Disabled because add_post_type_support('%1$s', '%2$s') is included in a loaded file." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:682 +#: src/modules/multiple-authors/multiple-authors.php:724 msgid "This will display the authors box at the end of the content." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:709 +#: src/modules/multiple-authors/multiple-authors.php:751 msgid "Single" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:716 +#: src/modules/multiple-authors/multiple-authors.php:758 msgid "Plural" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:785 +#: src/modules/multiple-authors/multiple-authors.php:828 msgid "Author profiles can be mapped to WordPress user accounts. This option allows you to automatically create author profiles when users are created in these roles. You can also do this for existing users by clicking the \"Create missed authors from role\" button in the Maintenance tab." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:806 +#: src/modules/multiple-authors/multiple-authors.php:849 msgid "If the Author is mapped to a WordPress user, this will display the authors' \"Display name\" and their \"Username\". The default is to show only the \"Display name\". Showing the \"Username\" is useful if you have several authors with similar names." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:843 +#: src/modules/multiple-authors/multiple-authors.php:886 msgid "This setting may be disabled for users who can not edit others posts." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:845 -msgid "Click here for more details." -msgstr "" - -#: src/modules/multiple-authors/multiple-authors.php:865 +#: src/modules/multiple-authors/multiple-authors.php:908 msgid "This will display the authors email in the author box." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:885 +#: src/modules/multiple-authors/multiple-authors.php:928 msgid "This will display the authors site in the author box." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:903 -#: src/modules/multiple-authors/multiple-authors.php:905 +#: src/modules/multiple-authors/multiple-authors.php:946 +#: src/modules/multiple-authors/multiple-authors.php:948 msgid "Create missed post authors" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:909 -#: src/modules/multiple-authors/multiple-authors.php:911 +#: src/modules/multiple-authors/multiple-authors.php:952 +#: src/modules/multiple-authors/multiple-authors.php:954 msgid "Create missed authors from role" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:915 +#: src/modules/multiple-authors/multiple-authors.php:958 msgid "Update author field on posts" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:922 +#: src/modules/multiple-authors/multiple-authors.php:965 msgid "Synchronize Author slugs to User logins" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:936 +#: src/modules/multiple-authors/multiple-authors.php:979 msgid "Copy Co-Authors Plus Data" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:944 +#: src/modules/multiple-authors/multiple-authors.php:987 msgid "Delete Mapped Authors" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:946 +#: src/modules/multiple-authors/multiple-authors.php:989 msgid "Delete all authors mapped to users" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:951 +#: src/modules/multiple-authors/multiple-authors.php:994 msgid "Delete Guest Authors" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:953 +#: src/modules/multiple-authors/multiple-authors.php:996 msgid "Delete all guest authors" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:960 +#: src/modules/multiple-authors/multiple-authors.php:1003 msgid "Please be careful clicking these buttons. Before clicking, we recommend taking a site backup in case anything goes wrong." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:1072 -msgid "General" -msgstr "" - -#: src/modules/multiple-authors/multiple-authors.php:1073 +#: src/modules/multiple-authors/multiple-authors.php:1116 msgid "Display" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:1074 +#: src/modules/multiple-authors/multiple-authors.php:1117 msgid "Maintenance" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:1163 -msgid "This is how the author’s name will appears on your site." +#: src/modules/multiple-authors/multiple-authors.php:1702 +msgid "Invalid nonce" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:1177 -msgid "This forms part of the URL for the author’s profile page. If you choose a Mapped User, this URL is taken from the user’s account and can not be changed." +#: src/modules/multiple-authors/multiple-authors.php:1706 +msgid "Access denied" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:1849 +#: src/modules/multiple-authors/multiple-authors.php:1872 msgid "Error. Author terms could not be reseted." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:1859 +#: src/modules/multiple-authors/multiple-authors.php:1882 msgid "Maintenance completed successfully." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:2467 +#: src/modules/multiple-authors/multiple-authors.php:2541 msgid "It looks like you have Co-Authors Plus installed." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:2469 +#: src/modules/multiple-authors/multiple-authors.php:2543 msgid "Please click here and read this guide!" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:2474 #: src/modules/multiple-authors/multiple-authors.php:2548 +#: src/modules/multiple-authors/multiple-authors.php:2622 msgid "Dismiss" msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:2540 +#: src/modules/multiple-authors/multiple-authors.php:2614 msgid "PublishPress Authors needs a database update for Permissions integration." msgstr "" -#: src/modules/multiple-authors/multiple-authors.php:2542 +#: src/modules/multiple-authors/multiple-authors.php:2616 msgid "Click to run the update now" msgstr "" @@ -939,15 +1025,15 @@ msgstr "" msgid "With PublishPress Authors Pro you can build new layouts for authors. You can use author information, custom fields, and much more." msgstr "" -#: src/modules/rest-api/rest-api.php:56 +#: src/modules/rest-api/rest-api.php:57 msgid "Rest API" msgstr "" -#: src/modules/rest-api/rest-api.php:57 src/modules/rest-api/rest-api.php:58 +#: src/modules/rest-api/rest-api.php:58 src/modules/rest-api/rest-api.php:59 msgid "Rest API support" msgstr "" -#: src/modules/rest-api/rest-api.php:95 +#: src/modules/rest-api/rest-api.php:96 msgid "Authors." msgstr "" @@ -963,15 +1049,15 @@ msgstr "" msgid "Add compatibility with The SEO Framework plugin." msgstr "" -#: src/modules/settings/settings.php:102 +#: src/modules/settings/settings.php:101 msgid "Multiple Authors Settings" msgstr "" -#: src/modules/settings/settings.php:103 +#: src/modules/settings/settings.php:102 msgid "Settings" msgstr "" -#: src/modules/settings/settings.php:222 +#: src/modules/settings/settings.php:201 msgid "There are no PublishPress modules registered" msgstr "" diff --git a/publishpress-authors.php b/publishpress-authors.php index cbd3436f..ecfac056 100644 --- a/publishpress-authors.php +++ b/publishpress-authors.php @@ -5,7 +5,7 @@ * Description: PublishPress Authors allows you to add multiple authors and guest authors to WordPress posts * Author: PublishPress * Author URI: https://publishpress.com - * Version: 3.15.1 + * Version: 3.16.0 * Text Domain: publishpress-authors * * ------------------------------------------------------------------------------ diff --git a/readme.txt b/readme.txt index a54a0d61..750630cd 100644 --- a/readme.txt +++ b/readme.txt @@ -7,7 +7,7 @@ Tags: multiple authors, authors, guest authors, author fields, author layouts Requires at least: 4.7 Requires PHP: 5.6 Tested up to: 5.9 -Stable tag: 3.15.1 +Stable tag: 3.16.0 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html @@ -224,6 +224,16 @@ There are two ways to install the PublishPress Authors plugin: == Changelog == += [3.16.0] - 23 Mar 2022 = + +* Added: Add option to authors update their own profile, #24; +* Fixed: Fix new author form not allowing to map a user to multiple authors, #64; +* Fixed: Fix PHP notice Constant PP_WP_BANNERS_VERSION already defined, #603; +* Fixed: Improve the selection of avatar for authors, making it clear if is using gravatar or custom image, #564; +* Fixed: Updated Italian translation files; +* Fixed: Fix description field that were displayed in the author profile after navigating throw the tabs, #605; +* Fixed: Fix small extra spacing in image link, #607; + = [3.15.1] - 17 Mar 2022 = * Fixed: Fix fatal error: Cannot declare class PublishPress\WordPressBanners\BannersMain; diff --git a/src/assets/css/multiple-authors.css b/src/assets/css/multiple-authors.css index 267941dc..bae513b8 100644 --- a/src/assets/css/multiple-authors.css +++ b/src/assets/css/multiple-authors.css @@ -318,3 +318,17 @@ body.block-editor-page select[id^="post-author-selector-"] { display: block; font-style: italic; } + +/* Set tab active class if user is on their author profile edit page */ +body.own-profile-edit li[class*=' toplevel_page_term?taxonomy=author&tag_ID'] { + border: 0 none; +} +body.own-profile-edit li[class*=' toplevel_page_term?taxonomy=author&tag_ID'] a.menu-top { + background: #2271b1; + color: #fff; +} + +body.own-profile-edit .term-authors-user_id-wrap, +body.own-profile-edit .edit-tag-actions span#delete-link { + display: none !important; +} \ No newline at end of file diff --git a/src/assets/css/pressshack-admin.css b/src/assets/css/pressshack-admin.css index 56729e59..f941bd86 100644 --- a/src/assets/css/pressshack-admin.css +++ b/src/assets/css/pressshack-admin.css @@ -339,3 +339,7 @@ div.pp-authors-menus-wrapper-promo select.ppc-nav-menu-role { height: 450px; } } + +body.term-php .term-slug-wrap .description { + display: none; +} diff --git a/src/assets/js/multiple-authors.js b/src/assets/js/multiple-authors.js index 607141c1..fe2b4da0 100644 --- a/src/assets/js/multiple-authors.js +++ b/src/assets/js/multiple-authors.js @@ -113,8 +113,7 @@ jQuery(document).ready(function ($) { }); } - function hasSelectedOnlyGuests(parent) - { + function hasSelectedOnlyGuests(parent) { if (typeof parent === 'undefined' || parent.length == 0) { parent = $('.authors-list'); } @@ -131,8 +130,7 @@ jQuery(document).ready(function ($) { return guestAuthorsCount === selectedAuthors.length; } - function handleUsersAuthorField(parent) - { + function handleUsersAuthorField(parent) { let $authorsUserField = $('#publishpress-authors-user-author-wrapper'); if (hasSelectedOnlyGuests(parent)) { $authorsUserField.show(); @@ -141,8 +139,7 @@ jQuery(document).ready(function ($) { } } - function authorsUserSelect2(selector) - { + function authorsUserSelect2(selector) { selector.each(function () { var authorsSearch = $(this).ppma_select2({ placeholder: $(this).data("placeholder"), @@ -259,7 +256,7 @@ jQuery(document).ready(function ($) { selectedAuthors.push(parseInt($(this).val())); }); - var selectedFallbackUser= $('#publishpress-authors-user-author-select').val(); + var selectedFallbackUser = $('#publishpress-authors-user-author-select').val(); // save the data $.ajax({ @@ -488,6 +485,108 @@ jQuery(document).ready(function ($) { return false; }); }); + + /** + * Add tab class to author editor's tr without tab + * + * This will add general tab class to 'Name' and Author URL + * or any tab that's rendered by default or third party + * without tab attribute + */ + if ($('body').hasClass('taxonomy-author')) { + $('form#edittag tr.form-field:not(.ppma-tab-content)') + .addClass('ppma-tab-content ppma-general-tab') + .attr('data-tab', 'general'); + } + + /** + * Author editor tab switch + */ + $(document).on('click', '.ppma-editor-tabs a', function (event) { + + event.preventDefault(); + + var clicked_tab = $(this).attr('data-tab'); + + //remove active class from all tabs + $('.ppma-editor-tabs a').removeClass('nav-tab-active'); + //add active class to current tab + $(this).addClass('nav-tab-active'); + + //hide all tabs contents + $('.ppma-tab-content').hide(); + //show this current tab contents + $('.ppma-' + clicked_tab + '-tab').show(); + + // Make sure the description field is hidden. It was being displayed after navigating throw tabs. + $('.form-field.term-description-wrap').hide(); + }); + + /** + * Author image avatar source option toggle + */ + $(document).on('click', 'input[name="authors-avatar-options"]', function () { + var clicked_element = $(this); + + if (clicked_element.val() === 'custom_image') { + clicked_element.closest('tr').find('.author-image-field-wrapper').show(); + } else { + //trigger image remove action + clicked_element.closest('tr').find('.delete-author-image-field').trigger('click'); + //hide image field wrapper + clicked_element.closest('tr').find('.author-image-field-wrapper').hide(); + } + }); + + /** + * Switch focus to general email from image tab handler + */ + $(document).on('click', '.ppma-image-general-author-focus', function (event) { + event.preventDefault(); + //triger click on general tab + $('.ppma-editor-tabs a[data-tab="general"]').trigger('click'); + //set focus on email field + $('input[name="authors-user_email"]').focus(); + }); + + //process a request to validate author mapped user. + $('body.taxonomy-author form#edittag').submit(function (event) { + + var $mappedUser = $('select[name="authors-user_id"]').val(); + var $authorSlug = $('input[name="slug"]').val(); + var $termId = $('input[name="tag_ID"]').val(); + var $form = $(this); + + $('.author-response-notice').remove(); + + event.preventDefault(); + + //prepare ajax data + var data = { + action: "mapped_author_validation", + author_id: $mappedUser, + author_slug: $authorSlug, + term_id: $termId, + nonce: MultipleAuthorsStrings.mapped_author_nonce, + }; + + if ($('.author-loading-spinner').length === 0) { + $('.edit-tag-actions input[type="submit"]').after(''); + } + + $('.author-loading-spinner').addClass('is-active'); + + $.post(ajaxurl, data, function (response) { + if (response.status === 'error') { + $('.edit-tag-actions').after('

' + response.content + '

'); + $('.author-loading-spinner').removeClass('is-active'); + } else { + $form.unbind('submit').submit(); + } + }); + + }); + }); if (typeof console === "undefined") { diff --git a/src/core/Classes/Admin_Ajax.php b/src/core/Classes/Admin_Ajax.php index f19e0644..fa2eefc2 100644 --- a/src/core/Classes/Admin_Ajax.php +++ b/src/core/Classes/Admin_Ajax.php @@ -225,4 +225,68 @@ public static function handle_author_get_user_data() echo wp_json_encode($response); exit; } + + /** + * Handle a request to validate mapped author. + */ + public static function handle_mapped_author_validation() + { + + $response['status'] = 'success'; + $response['content'] = esc_html__('Request status.', 'publishpress-authors'); + + //do not process request if nonce validation failed + if (empty($_POST['nonce']) + || !wp_verify_nonce(sanitize_key($_POST['nonce']), 'mapped_author_nonce') + ) { + $response['status'] = 'error'; + $response['content'] = esc_html__( + 'Security error. Kindly reload this page and try again', + 'publishpress-authors' + ); + } else { + $author_slug = !empty($_POST['author_slug']) ? sanitize_title($_POST['author_slug']) : ''; + $author_id = !empty($_POST['author_id']) ? (int)($_POST['author_id']) : 0; + $term_id = !empty($_POST['term_id']) ? (int)($_POST['term_id']) : 0; + + if ($author_id > 0) { + $author = Author::get_by_user_id($author_id); + if ($author && is_object($author) && isset($author->term_id)) { + if ((int)$author->term_id !== (int)$term_id) { + $response['status'] = 'error'; + $response['content'] = esc_html__( + 'This user is already mapped to another author.', + 'publishpress-authors' + ); + } + } + } + + if (empty($author_slug)) { + $response['status'] = 'error'; + $response['content'] = esc_html__('Author URL cannot be empty.', 'publishpress-authors'); + } else { + $author_slug_user = get_user_by('slug', $author_slug); + if ($author_slug_user && is_object($author_slug_user) && isset($author_slug_user->ID)) { + if (($author_id === 0) + || ($author_id > 0 + && (int)$author_slug_user->ID != (int)$author_id) + ) { + /** + * Return error if author is not linked or + * linked author ID is not equal return ID + */ + $response['status'] = 'error'; + $response['content'] = esc_html__( + 'Another user with Author URL already exists.', + 'publishpress-authors' + ); + } + } + } + } + + wp_send_json($response); + exit; + } } diff --git a/src/core/Classes/Author_Editor.php b/src/core/Classes/Author_Editor.php index d251968b..893b5581 100644 --- a/src/core/Classes/Author_Editor.php +++ b/src/core/Classes/Author_Editor.php @@ -12,6 +12,7 @@ use MultipleAuthors\Classes\Legacy\Util; use MultipleAuthors\Classes\Objects\Author; use MultipleAuthors\Factory; +use WP_Error; /** * Class Author_Editor @@ -22,6 +23,9 @@ */ class Author_Editor { + + const AUTHOR_EDITOR_DEFAULT_TAB = 'general'; + /** * Customize the term table to look more like the users table. * @@ -226,6 +230,41 @@ public static function filter_author_row_actions($actions, $author_term) return $actions; } + /** + * Render fields tabs for the author profile editor + * + * @param WP_Term $term Author term being edited. + */ + public static function action_author_edit_form_fields_tab($term) + { + $author = Author::get_by_term_id($term->term_id); + + /** + * Filter the fields tabs on the Author's profile. + * + * @param array $tabs + * @param Author $author + * + * @return array + */ + $fields_tabs = apply_filters('multiple_authors_author_fields_tabs', self::get_fields_tabs($author), $author); + + echo '

'; + + foreach ($fields_tabs as $key => $args) { + $active_tab = ($key === self::AUTHOR_EDITOR_DEFAULT_TAB) ? ' nav-tab-active' : ''; + ?> + + + + '; + } + /** * Render fields for the author profile editor * @@ -254,6 +293,35 @@ public static function action_author_edit_form_fields($term) wp_nonce_field('author-edit', 'author-edit-nonce'); } + /** + * Get the fields tabs to be rendered in the author editor + * + * @param Author $author Author to be rendered. + * + * @return array + */ + public static function get_fields_tabs($author) + { + $fields_tabs = [ + 'general' => [ + 'label' => __('General', 'publishpress-authors'), + ], + 'image' => [ + 'label' => __('Image', 'publishpress-authors'), + ], + ]; + + /** + * Customize fields tabs presented in the author editor. + * + * @param array $fields_tabs Existing fields tabs to display. + * @param Author $author Author to be rendered. + */ + $fields_tabs = apply_filters('authors_editor_fields_tabs', $fields_tabs, $author); + + return $fields_tabs; + } + /** * Get the fields to be rendered in the author editor * @@ -265,40 +333,58 @@ public static function get_fields($author) { $fields = [ 'user_id' => [ - 'label' => __('Mapped User', 'publishpress-authors'), + 'label' => esc_html__('Mapped User', 'publishpress-authors'), 'type' => 'ajax_user_select', 'sanitize' => 'intval', + 'tab' => 'general', ], 'first_name' => [ - 'label' => __('First Name', 'publishpress-authors'), + 'label' => esc_html__('First Name', 'publishpress-authors'), 'type' => 'text', + 'tab' => 'general', ], 'last_name' => [ - 'label' => __('Last Name', 'publishpress-authors'), + 'label' => esc_html__('Last Name', 'publishpress-authors'), 'type' => 'text', + 'tab' => 'general', ], 'user_email' => [ - 'label' => __('Email', 'publishpress-authors'), + 'label' => esc_html__('Email', 'publishpress-authors'), 'type' => 'email', - 'description' => __( - 'To show the avatar from the Mapped User, enter the same email address as the Mapped User.
To show the avatar for a Guest Author, enter the email for their Gravatar account.', - 'publishpress-authors' - ), + 'tab' => 'general', ], 'avatar' => [ - 'label' => __('Custom Avatar', 'publishpress-authors'), - 'type' => 'image', - 'sanitize' => 'intval', + 'label' => __('Avatar Source', 'publishpress-authors'), + 'type' => 'avatar', + 'sanitize' => 'intval', + 'tab' => 'image', + 'options' => [ + 'gravatar' => [ + 'label' => __('Gravatar', 'publishpress-authors'), + 'description' => sprintf( + esc_html__( + '(Uses the %sauthor e-mail%s as Gravatar account)', + 'publishpress-authors' + ), + '', '' + ) + ], + 'custom_image' => [ + 'label' => __('Custom image', 'publishpress-authors'), + ], + ], ], 'user_url' => [ - 'label' => __('Website', 'publishpress-authors'), + 'label' => esc_html__('Website', 'publishpress-authors'), 'type' => 'url', 'sanitize' => 'esc_url_raw', + 'tab' => 'general', ], 'description' => [ - 'label' => __('Biographical Info', 'publishpress-authors'), + 'label' => esc_html__('Biographical Info', 'publishpress-authors'), 'type' => 'textarea', 'sanitize' => 'sanitize_textarea_field', + 'tab' => 'general', ], ]; @@ -322,15 +408,23 @@ private static function get_rendered_author_partial($args) { $defaults = [ 'type' => 'text', + 'tab' => self::AUTHOR_EDITOR_DEFAULT_TAB, + 'options' => [], 'value' => '', 'label' => '', 'description' => '', ]; - $args = array_merge($defaults, $args); - $key = 'authors-' . $args['key']; + $args = array_merge($defaults, $args); + $key = 'authors-' . $args['key']; + $tab_class = 'ppma-tab-content ppma-' . $args['tab'] . '-tab'; + $tab_style = ($args['tab'] === self::AUTHOR_EDITOR_DEFAULT_TAB) ? '' : 'display:none;'; ob_start(); ?> - + @@ -359,6 +453,55 @@ private static function get_rendered_author_partial($args) + + + $avatar_option_data) { ?> +

+ /> + + +

+ + +
+
+ + + +
+

+ + + + + + +

+ +
@@ -631,4 +774,73 @@ public static function admin_notices() echo ''; } } + + /** + * Author term mapped limit validation + * + * @param string|WP_Error $term The term name to add, or a WP_Error object if there's an error. + * @param string $taxonomy Taxonomy slug. + * + * @return array|WP_Error + */ + public static function filter_pre_insert_term($term, $taxonomy) + { + if ($taxonomy === 'author') { + /** + * Check if term with this user exist + */ + if ( + isset($_POST['authors-new']) + && $author_id = (int)$_POST['authors-new'] > 0 + ) { + $author = Author::get_by_user_id($author_id); + + if ( + $author + && is_object($author) + && isset($author->term_id) + && (int)$author->term_id > 0 + ) { + return new WP_Error( + 'publishpress_authors_duplicate_mapped_user', + esc_html__( + 'This user is already mapped to another author.', + 'publishpress-authors' + ) + ); + } + } + + /** + * Check if user with term slug already exists + */ + if (empty($_POST['slug'])) { + $slug = sanitize_title($_POST['tag-name']); + } else { + $slug = sanitize_title($_POST['slug']); + } + + $author_slug_user = get_user_by('slug', $slug); + if ( + $author_slug_user + && is_object($author_slug_user) + && isset($author_slug_user->ID) + ) { + if ( + (! isset($_POST['authors-new'])) + || ((int)$author_slug_user->ID != (int)$_POST['authors-new']) + ) { + return new WP_Error( + 'publishpress_authors_slug_exists', + esc_html__( + 'An author with the name provided already exists.', + 'publishpress-authors' + ) + ); + } + } + } + + return $term; + } } diff --git a/src/core/Plugin.php b/src/core/Plugin.php index dc38b00b..2e2ee2b8 100644 --- a/src/core/Plugin.php +++ b/src/core/Plugin.php @@ -216,6 +216,10 @@ public function __construct() 10, 2 ); + add_action( + 'author_term_edit_form_top', + ['MultipleAuthors\\Classes\\Author_Editor', 'action_author_edit_form_fields_tab'] + ); add_action( 'author_edit_form_fields', ['MultipleAuthors\\Classes\\Author_Editor', 'action_author_edit_form_fields'] @@ -255,6 +259,16 @@ public function __construct() 'admin_notices', ['MultipleAuthors\\Classes\\Author_Editor', 'admin_notices'] ); + add_filter( + 'pre_insert_term', + ['MultipleAuthors\\Classes\\Author_Editor', 'filter_pre_insert_term'], + 10, + 2 + ); + add_action( + 'wp_ajax_mapped_author_validation', + ['MultipleAuthors\\Classes\\Admin_Ajax', 'handle_mapped_author_validation'] + ); add_filter('admin_footer_text', [$this, 'update_footer_admin']); } @@ -447,6 +461,38 @@ public function action_init() null, plugin_basename(PP_AUTHORS_BASE_PATH) . '/languages/' ); + + add_filter('taxonomy_labels_author', [$this, 'filter_author_taxonomy_labels']); + } + + public function filter_author_taxonomy_labels($labels) + { + global $pagenow; + + if ( + is_admin() + && $pagenow === 'term.php' + && isset($_GET['taxonomy']) && $_GET['taxonomy'] === 'author' + && isset($_GET['tag_ID']) + ) { + $author = Author::get_by_term_id((int)$_GET['tag_ID']); + + if (is_object($author) && !is_wp_error($author) && (int)$author->user_id === get_current_user_id()) { + $labels->edit_item = __('Edit My Author Profile', 'publishpress-authors'); + } + } + + $labels->name_field_description = esc_html__( + 'This is the name that will show on the site.', + 'publishpress-authors' + ); + + $labels->slug_field_description = esc_html__( + 'This forms part of the URL for the author’s profile page. If you choose a Mapped User, this URL is taken from the user’s account and can not be changed.', + 'publishpress-authors' + ); + + return $labels; } /** @@ -467,23 +513,23 @@ public function action_init_late() 'taxonomy singular name', 'publishpress-authors' ), - 'search_items' => __('Search authors', 'publishpress-authors'), - 'popular_items' => __('Popular authors', 'publishpress-authors'), - 'all_items' => __('All authors', 'publishpress-authors'), - 'parent_item' => __('Parent author', 'publishpress-authors'), - 'parent_item_colon' => __('Parent author:', 'publishpress-authors'), - 'edit_item' => __('Edit author', 'publishpress-authors'), - 'view_item' => __('View author', 'publishpress-authors'), - 'update_item' => __('Update author', 'publishpress-authors'), - 'add_new_item' => __('New author', 'publishpress-authors'), - 'new_item_name' => __('New author', 'publishpress-authors'), + 'search_items' => __('Search Authors', 'publishpress-authors'), + 'popular_items' => __('Popular Authors', 'publishpress-authors'), + 'all_items' => __('All Authors', 'publishpress-authors'), + 'parent_item' => __('Parent Author', 'publishpress-authors'), + 'parent_item_colon' => __('Parent Author:', 'publishpress-authors'), + 'edit_item' => __('Edit Author', 'publishpress-authors'), + 'view_item' => __('View Author', 'publishpress-authors'), + 'update_item' => __('Update Author', 'publishpress-authors'), + 'add_new_item' => __('New Author', 'publishpress-authors'), + 'new_item_name' => __('New Author', 'publishpress-authors'), 'separate_items_with_commas' => __( 'Separate authors with commas', 'publishpress-authors' ), 'add_or_remove_items' => __('Add or remove authors', 'publishpress-authors'), 'choose_from_most_used' => __( - 'Choose from the most used authors', + 'Choose from the most used Authors', 'publishpress-authors' ), 'not_found' => __('No authors found.', 'publishpress-authors'), @@ -1382,6 +1428,7 @@ public function enqueue_scripts($hook_suffix) 'Sorry, the request returned an error.', 'publishpress-authors' ), + 'mapped_author_nonce' => wp_create_nonce("mapped_author_nonce"), ]; wp_localize_script( @@ -1705,6 +1752,7 @@ public function filterCMECapabilities($capabilities) [ 'ppma_manage_authors', 'ppma_edit_post_authors', + 'ppma_edit_own_profile', ] ); diff --git a/src/modules/modules-settings/modules-settings.php b/src/modules/modules-settings/modules-settings.php index e59f9ffb..321dd9dd 100644 --- a/src/modules/modules-settings/modules-settings.php +++ b/src/modules/modules-settings/modules-settings.php @@ -31,6 +31,7 @@ use MultipleAuthors\Classes\Legacy\Module; use MultipleAuthors\Classes\Utils; use MultipleAuthors\Factory; +use PublishPress\WordPressBanners\BannersMain; if (!class_exists('MA_Modules_Settings')) { /** @@ -273,10 +274,10 @@ public function print_configure_view() submit_button(null, 'primary', 'submit', false); ?> - +
pp_display_banner( esc_html__( 'Recommendations for you', 'publishpress-authors' ), esc_html__( 'Showcase your Authors with PublishPress Blocks', 'publishpress-authors' ), diff --git a/src/modules/multiple-authors/multiple-authors.php b/src/modules/multiple-authors/multiple-authors.php index 4f4e6b93..03d7071a 100644 --- a/src/modules/multiple-authors/multiple-authors.php +++ b/src/modules/multiple-authors/multiple-authors.php @@ -183,6 +183,9 @@ public function init() if (!is_admin()) { add_filter('body_class', [$this, 'filter_body_class']); add_filter('comment_class', [$this, 'filterCommentClass'], 10, 5); + }else{ + //author profile edit body class + add_filter('admin_body_class', [$this, 'filter_admin_body_class']); } // Fix upload permissions for multiple authors. @@ -252,6 +255,9 @@ public function init() add_action('profile_update', [$this, 'userProfileUpdate'], 10, 2); add_filter('pre_comment_approved', [$this, 'preCommentApproved'], 10, 2); + + // Allow author to edit own author profile. + add_filter('map_meta_cap', [$this, 'filter_term_map_meta_cap'], 10, 4); } /** @@ -268,6 +274,25 @@ public function action_admin_menu_page() 'dashicons-groups', 26 ); + + $current_author = Author::get_by_user_id(get_current_user_id()); + if ( + !current_user_can(apply_filters('pp_multiple_authors_manage_authors_cap', 'ppma_manage_authors')) && + $current_author && + is_object($current_author) && + isset($current_author->term_id) + ) { + add_menu_page( + esc_html__('Author Profile', 'publishpress-authors'), + esc_html__('Author Profile', 'publishpress-authors'), + apply_filters('pp_multiple_authors_edit_own_profile_cap', 'ppma_edit_own_profile'), + 'term.php?taxonomy=author&tag_ID='.$current_author->term_id, + __return_empty_string(), + 'dashicons-groups', + 26 + ); + } + } /** @@ -1170,32 +1195,14 @@ public function filter_get_text($translation, $text, $domain) } $taxonomy = isset($_GET['taxonomy']) ? sanitize_key($_GET['taxonomy']) : null; - if ('author' !== $taxonomy) { return $translation; } - // The description of the field Name - if ('default' === $domain && 'The name is how it appears on your site.' === $translation) { - $translation = esc_html__( - 'This is how the author’s name will appears on your site.', - 'publishpress-authors' - ); - } - // The name of field Slug, convert to Author URL - if (isset($_GET['taxonomy']) && 'author' === $_GET['taxonomy']) { - if ('default' === $domain) { - if ('Slug' === $translation) { - $translation = esc_html__('Author URL', 'publishpress-authors'); - } - - if ('The “slug” is the URL-friendly version of the name. It is usually all lowercase and contains only letters, numbers, and hyphens.' === $translation) { - $translation = esc_html__( - 'This forms part of the URL for the author’s profile page. If you choose a Mapped User, this URL is taken from the user’s account and can not be changed.', - 'publishpress-authors' - ); - } + if ('default' === $domain) { + if ('Slug' === $translation) { + $translation = esc_html__('Author URL', 'publishpress-authors'); } } @@ -2065,16 +2072,27 @@ public function admin_enqueue_scripts() */ public function migrate_legacy_settings() { - if (get_option('publishpress_multiple_authors_settings_migrated_3_0_0')) { - return false; - } + if (!get_option('publishpress_multiple_authors_settings_migrated_3_0_0')) { + $legacyOptions = get_option('publishpress_multiple_authors_options'); + if (!empty($legacyOptions)) { + update_option('multiple_authors_multiple_authors_options', $legacyOptions); + } - $legacyOptions = get_option('publishpress_multiple_authors_options'); - if (!empty($legacyOptions)) { - update_option('multiple_authors_multiple_authors_options', $legacyOptions); + update_option('publishpress_multiple_authors_settings_migrated_3_0_0', 1); + } + + if (!get_option('publishpress_multiple_authors_settings_migrated_3_15_0')) { + if (function_exists('get_role')) { + $capability_roles = ['administrator', 'editor', 'author']; + foreach ($capability_roles as $capability_role) { + $role = get_role($capability_role); + if (is_object($role) && !is_wp_error($role)) { + $role->add_cap('ppma_edit_own_profile'); + } + } + update_option('publishpress_multiple_authors_settings_migrated_3_15_0', 1); + } } - - update_option('publishpress_multiple_authors_settings_migrated_3_0_0', 1); } /** @@ -2798,5 +2816,70 @@ public function preCommentApproved($approved, $commentData) return $approved; } + + /** + * Allow author to edit own author profile. + * + * @param $caps + * @param $cap + * @param $user_id + * @param $args + * + * @return mixed + */ + public function filter_term_map_meta_cap($caps, $cap, $user_id, $args) + { + if (in_array($cap, ['edit_term', 'ppma_manage_authors']) && in_array('ppma_manage_authors', $caps, true)) { + + $term_id = 0; + if (isset($args[0])) { + $term_id = (int)$args[0]; + }else if (isset($_POST['action']) && $_POST['action'] === 'editedtag' && isset($_POST['tag_ID']) && (int)$_POST['tag_ID'] > 0) { + //this is needed for when saving the profile as it run through edit-tags.php which user doesn't have permission + $term_id = (int)$_POST['tag_ID']; + } + $current_author = Author::get_by_user_id(get_current_user_id()); + + //allow user to edit own profile. + if ( + $term_id > 0 && + $current_author && + is_object($current_author) && + isset($current_author->term_id) && + (int)$current_author->term_id === $term_id + ) { + foreach ($caps as &$item) { + if ($item === 'ppma_manage_authors') { + $item = 'ppma_edit_own_profile'; + } + } + $caps = apply_filters('pp_authors_filter_term_map_meta_cap', $caps, $cap, $user_id, $term_id); + } + } + + return $caps; + } + + /** + * Author profile edit body class + * + * @param string $class + * + * @return string + */ + public function filter_admin_body_class($classes) { + + if (!function_exists('get_current_screen')) { + return $classes; + } + + $screen = get_current_screen(); + + if ($screen && is_object($screen) && isset($screen->id) && $screen->id === 'edit-author') { + $classes .= (current_user_can(apply_filters('pp_multiple_authors_manage_authors_cap', 'ppma_manage_authors'))) ? ' authorised-profile-edit ' : ' own-profile-edit '; + } + + return $classes; + } } } diff --git a/tests/codeception/_data/dump.sql b/tests/codeception/_data/dump.sql index 509de42c..4b3f9568 100644 --- a/tests/codeception/_data/dump.sql +++ b/tests/codeception/_data/dump.sql @@ -8,421 +8,502 @@ SET sql_mode = 'NO_AUTO_VALUE_ON_ZERO'; SET NAMES utf8mb4; DROP TABLE IF EXISTS `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 DEFAULT NULL, - 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; +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 DEFAULT NULL, + 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; DROP TABLE IF EXISTS `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; +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; -INSERT INTO `wp_comments` (`comment_ID`, `comment_post_ID`, `comment_author`, `comment_author_email`, `comment_author_url`, `comment_author_IP`, `comment_date`, `comment_date_gmt`, `comment_content`, `comment_karma`, `comment_approved`, `comment_agent`, `comment_type`, `comment_parent`, `user_id`) VALUES -(1, 1, 'A WordPress Commenter', 'wapuu@wordpress.example', 'https://wordpress.org/', '', '2020-04-20 19:10:05', '2020-04-20 19:10:05', 'Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from Gravatar.', 0, '1', '', '', 0, 0); +INSERT INTO `wp_comments` (`comment_ID`, `comment_post_ID`, `comment_author`, `comment_author_email`, + `comment_author_url`, `comment_author_IP`, `comment_date`, `comment_date_gmt`, + `comment_content`, `comment_karma`, `comment_approved`, `comment_agent`, `comment_type`, + `comment_parent`, `user_id`) +VALUES (1, 1, 'A WordPress Commenter', 'wapuu@wordpress.example', 'https://wordpress.org/', '', '2020-04-20 19:10:05', + '2020-04-20 19:10:05', + 'Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from Gravatar.', + 0, '1', '', '', 0, 0); DROP TABLE IF EXISTS `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; +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; DROP TABLE IF EXISTS `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 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +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 + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES -(1, 'siteurl', 'https://tests.local', 'yes'), -(2, 'home', 'https://tests.local', 'yes'), -(3, 'blogname', 'Sandbox', 'yes'), -(4, 'blogdescription', 'Just another WordPress site', 'yes'), -(5, 'users_can_register', '0', 'yes'), -(6, 'admin_email', 'publishpress-dev@example.com', 'yes'), -(7, 'start_of_week', '1', 'yes'), -(8, 'use_balanceTags', '0', 'yes'), -(9, 'use_smilies', '1', 'yes'), -(10, 'require_name_email', '1', 'yes'), -(11, 'comments_notify', '1', 'yes'), -(12, 'posts_per_rss', '10', 'yes'), -(13, 'rss_use_excerpt', '0', 'yes'), -(14, 'mailserver_url', 'mail.example.com', 'yes'), -(15, 'mailserver_login', 'login@example.com', 'yes'), -(16, 'mailserver_pass', 'password', 'yes'), -(17, 'mailserver_port', '110', 'yes'), -(18, 'default_category', '1', 'yes'), -(19, 'default_comment_status', 'open', 'yes'), -(20, 'default_ping_status', 'open', 'yes'), -(21, 'default_pingback_flag', '1', 'yes'), -(22, 'posts_per_page', '10', 'yes'), -(23, 'date_format', 'F j, Y', 'yes'), -(24, 'time_format', 'g:i a', 'yes'), -(25, 'links_updated_date_format', 'F j, Y g:i a', 'yes'), -(26, 'comment_moderation', '0', 'yes'), -(27, 'moderation_notify', '1', 'yes'), -(28, 'permalink_structure', '', 'yes'), -(29, 'rewrite_rules', '', 'yes'), -(30, 'hack_file', '0', 'yes'), -(31, 'blog_charset', 'UTF-8', 'yes'), -(32, 'moderation_keys', '', 'no'), -(33, 'active_plugins', 'a:2:{i:0;s:37:\"custom-post-type/custom-post-type.php\";i:1;s:45:\"publishpress-authors/publishpress-authors.php\";}', 'yes'), -(34, 'category_base', '', 'yes'), -(35, 'ping_sites', 'http://rpc.pingomatic.com/', 'yes'), -(36, 'comment_max_links', '2', 'yes'), -(37, 'gmt_offset', '0', 'yes'), -(38, 'default_email_category', '1', 'yes'), -(39, 'recently_edited', '', 'no'), -(40, 'template', 'twentytwenty', 'yes'), -(41, 'stylesheet', 'twentytwenty', 'yes'), -(44, 'comment_registration', '0', 'yes'), -(45, 'html_type', 'text/html', 'yes'), -(46, 'use_trackback', '0', 'yes'), -(47, 'default_role', 'subscriber', 'yes'), -(48, 'db_version', '49752', 'yes'), -(49, 'uploads_use_yearmonth_folders', '1', 'yes'), -(50, 'upload_path', '', 'yes'), -(51, 'blog_public', '1', 'yes'), -(52, 'default_link_category', '2', 'yes'), -(53, 'show_on_front', 'posts', 'yes'), -(54, 'tag_base', '', 'yes'), -(55, 'show_avatars', '1', 'yes'), -(56, 'avatar_rating', 'G', 'yes'), -(57, 'upload_url_path', '', 'yes'), -(58, 'thumbnail_size_w', '150', 'yes'), -(59, 'thumbnail_size_h', '150', 'yes'), -(60, 'thumbnail_crop', '1', 'yes'), -(61, 'medium_size_w', '300', 'yes'), -(62, 'medium_size_h', '300', 'yes'), -(63, 'avatar_default', 'mystery', 'yes'), -(64, 'large_size_w', '1024', 'yes'), -(65, 'large_size_h', '1024', 'yes'), -(66, 'image_default_link_type', 'none', 'yes'), -(67, 'image_default_size', '', 'yes'), -(68, 'image_default_align', '', 'yes'), -(69, 'close_comments_for_old_posts', '0', 'yes'), -(70, 'close_comments_days_old', '14', 'yes'), -(71, 'thread_comments', '1', 'yes'), -(72, 'thread_comments_depth', '5', 'yes'), -(73, 'page_comments', '0', 'yes'), -(74, 'comments_per_page', '50', 'yes'), -(75, 'default_comments_page', 'newest', 'yes'), -(76, 'comment_order', 'asc', 'yes'), -(77, 'sticky_posts', 'a:0:{}', 'yes'), -(78, 'widget_categories', 'a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}', 'yes'), -(79, 'widget_text', 'a:0:{}', 'yes'), -(80, 'widget_rss', 'a:0:{}', 'yes'), -(81, 'uninstall_plugins', 'a:0:{}', 'no'), -(82, 'timezone_string', '', 'yes'), -(83, 'page_for_posts', '0', 'yes'), -(84, 'page_on_front', '0', 'yes'), -(85, 'default_post_format', '0', 'yes'), -(86, 'link_manager_enabled', '0', 'yes'), -(87, 'finished_splitting_shared_terms', '1', 'yes'), -(88, 'site_icon', '0', 'yes'), -(89, 'medium_large_size_w', '768', 'yes'), -(90, 'medium_large_size_h', '0', 'yes'), -(91, 'wp_page_for_privacy_policy', '3', 'yes'), -(92, 'show_comments_cookies_opt_in', '1', 'yes'), -(94, 'initial_db_version', '45805', 'yes'), -(95, 'wp_user_roles', 'a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:63:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;s:19:\"ppma_manage_authors\";b:1;s:22:\"ppma_edit_post_authors\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:35:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:22:\"ppma_edit_post_authors\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:11:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:22:\"ppma_edit_post_authors\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:6:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"ppma_edit_post_authors\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}', 'yes'), -(96, 'fresh_site', '0', 'yes'), -(97, 'widget_search', 'a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}', 'yes'), -(98, 'widget_recent-posts', 'a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}', 'yes'), -(99, 'widget_recent-comments', 'a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}', 'yes'), -(100, 'widget_archives', 'a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}', 'yes'), -(101, 'widget_meta', 'a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}', 'yes'), -(102, 'sidebars_widgets', 'a:4:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:3:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";}s:9:\"sidebar-2\";a:3:{i:0;s:10:\"archives-2\";i:1;s:12:\"categories-2\";i:2;s:6:\"meta-2\";}s:13:\"array_version\";i:3;}', 'yes'), -(103, 'cron', 'a:6:{i:1641243686;a:6:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:18:\"wp_https_detection\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1641243688;a:1:{s:8:\"do_pings\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}}i:1641243772;a:1:{s:28:\"wp_update_comment_type_batch\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}}i:1641244170;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1641330086;a:1:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}s:7:\"version\";i:2;}', 'yes'), -(104, 'widget_pages', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(105, 'widget_calendar', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(106, 'widget_media_audio', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(107, 'widget_media_image', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(108, 'widget_media_gallery', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(109, 'widget_media_video', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(110, 'widget_tag_cloud', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(111, 'widget_nav_menu', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(112, 'widget_custom_html', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(139, 'db_upgraded', '', 'yes'), -(142, 'recently_activated', 'a:0:{}', 'yes'), -(143, '_site_transient_update_plugins', 'O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1641248344;s:8:\"response\";a:2:{s:45:\"publishpress-authors/publishpress-authors.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:34:\"w.org/plugins/publishpress-authors\";s:4:\"slug\";s:20:\"publishpress-authors\";s:6:\"plugin\";s:45:\"publishpress-authors/publishpress-authors.php\";s:11:\"new_version\";s:6:\"3.14.9\";s:3:\"url\";s:51:\"https://wordpress.org/plugins/publishpress-authors/\";s:7:\"package\";s:70:\"https://downloads.wordpress.org/plugin/publishpress-authors.3.14.9.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:73:\"https://ps.w.org/publishpress-authors/assets/icon-256x256.png?rev=2472504\";s:2:\"1x\";s:73:\"https://ps.w.org/publishpress-authors/assets/icon-128x128.png?rev=2472504\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:76:\"https://ps.w.org/publishpress-authors/assets/banner-1544x500.jpg?rev=2472504\";s:2:\"1x\";s:75:\"https://ps.w.org/publishpress-authors/assets/banner-772x250.jpg?rev=2472504\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.7\";s:6:\"tested\";s:5:\"5.8.2\";s:12:\"requires_php\";s:3:\"5.6\";}s:37:\"custom-post-type/custom-post-type.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:30:\"w.org/plugins/custom-post-type\";s:4:\"slug\";s:16:\"custom-post-type\";s:6:\"plugin\";s:37:\"custom-post-type/custom-post-type.php\";s:11:\"new_version\";s:3:\"1.0\";s:3:\"url\";s:47:\"https://wordpress.org/plugins/custom-post-type/\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/plugin/custom-post-type.zip\";s:5:\"icons\";a:1:{s:7:\"default\";s:60:\"https://s.w.org/plugins/geopattern-icon/custom-post-type.svg\";}s:7:\"banners\";a:0:{}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.0\";s:6:\"tested\";s:6:\"4.6.21\";s:12:\"requires_php\";b:0;}}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:2:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:5:\"4.2.1\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.2.1.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:59:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272\";s:2:\"1x\";s:59:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:61:\"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.0\";}s:9:\"hello.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:5:\"1.7.2\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855\";s:2:\"1x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/hello-dolly/assets/banner-1544x500.jpg?rev=2645582\";s:2:\"1x\";s:66:\"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.6\";}}s:7:\"checked\";a:4:{s:19:\"akismet/akismet.php\";s:5:\"4.2.1\";s:9:\"hello.php\";s:5:\"1.7.2\";s:45:\"publishpress-authors/publishpress-authors.php\";s:19:\"3.14.9-hotfix-552.1\";s:37:\"custom-post-type/custom-post-type.php\";s:5:\"0.1.0\";}}', 'no'), -(144, '_site_transient_update_themes', 'O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1641244202;s:7:\"checked\";a:2:{s:14:\"twentynineteen\";s:3:\"2.1\";s:15:\"twentytwentyone\";s:3:\"1.4\";}s:8:\"response\";a:0:{}s:9:\"no_update\";a:2:{s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"2.1\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.2.1.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentytwentyone\";a:6:{s:5:\"theme\";s:15:\"twentytwentyone\";s:11:\"new_version\";s:3:\"1.4\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentytwentyone/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentytwentyone.1.4.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"5.6\";}}s:12:\"translations\";a:0:{}}', 'no'), -(147, 'widget_block', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(148, 'theme_mods_twentytwenty', 'a:1:{s:18:\"custom_css_post_id\";i:-1;}', 'yes'), -(149, '_transient_doing_cron', '1641248406.0403409004211425781250', 'yes'), -(150, 'admin_email_lifespan', '3338761010', 'yes'), -(151, 'disallowed_keys', '', 'no'), -(152, 'comment_previously_approved', '1', 'yes'), -(153, 'auto_plugin_theme_update_emails', 'a:0:{}', 'no'), -(154, 'auto_update_core_dev', 'enabled', 'yes'), -(155, 'auto_update_core_minor', 'enabled', 'yes'), -(156, 'auto_update_core_major', 'unset', 'yes'), -(157, 'wp_force_deactivated_plugins', 'a:0:{}', 'yes'), -(158, 'finished_updating_comment_type', '0', 'yes'), -(160, '_site_transient_timeout_theme_roots', '1641245971', 'no'), -(161, '_site_transient_theme_roots', 'a:2:{s:14:\"twentynineteen\";s:7:\"/themes\";s:15:\"twentytwentyone\";s:7:\"/themes\";}', 'no'), -(162, '_site_transient_timeout_wp_remote_block_patterns_81e61ac1547ff34fec7bd771bd25e786', '1641247773', 'no'), -(163, '_site_transient_wp_remote_block_patterns_81e61ac1547ff34fec7bd771bd25e786', 'a:13:{i:0;O:8:\"stdClass\":7:{s:2:\"id\";i:184;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:7:\"Heading\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:290:\"\n

We’re a studio in Berlin with an international practice in architecture, urban planning and interior design. We believe in sharing knowledge and promoting dialogue to increase the creative potential of collaboration.

\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:12:\"Heading text\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:1:{i:0;s:12:\"core/heading\";}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:2:{i:0;s:8:\"featured\";i:1;s:4:\"text\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:402:\"\n

We\'re a studio in Berlin with an international practice in architecture, urban planning and interior design. We believe in sharing knowledge and promoting dialogue to increase the creative potential of collaboration.

\n\";}i:1;O:8:\"stdClass\":7:{s:2:\"id\";i:185;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:35:\"Large header with left-aligned text\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:1019:\"\n
\"\"
\n

Forest.

\n\n\n\n
\n
\n
\n\n\n\n

Even a child knows how valuable the forest is. The fresh, breathtaking smell of trees. Echoing birds flying above that dense magnitude. A stable climate, a sustainable diverse life and a source of culture. Yet, forests and other ecosystems hang in the balance, threatened to become croplands, pasture, and plantations.

\n
\n\n\n\n
\n
\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:29:\"Cover image with quote on top\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:2:{i:0;s:8:\"featured\";i:1;s:6:\"header\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1610:\"\n
\"\"
\n

Forest.

\n\n\n\n
\n
\n
\n\n\n\n

Even a child knows how valuable the forest is. The fresh, breathtaking smell of trees. Echoing birds flying above that dense magnitude. A stable climate, a sustainable diverse life and a source of culture. Yet, forests and other ecosystems hang in the balance, threatened to become croplands, pasture, and plantations.

\n
\n\n\n\n
\n
\n
\n\";}i:2;O:8:\"stdClass\":7:{s:2:\"id\";i:186;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:35:\"Large header with text and a button\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:1082:\"\n
\n

Overseas:
1500 — 1960

\n\n\n\n
\n
\n

An exhibition about the different representations of the ocean throughout time, between the sixteenth and the twentieth century. Taking place in our Open Room in Floor 2.

\n\n\n\n
\n
Visit
\n
\n
\n\n\n\n
\n
\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:62:\"Large header with background image and text and button on top.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:1:{i:0;s:6:\"header\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1865:\"\n
\n

Overseas:
1500 — 1960

\n\n\n\n
\n
\n

An exhibition about the different representations of the ocean throughout time, between the sixteenth and the twentieth century. Taking place in our Open Room in Floor 2.

\n\n\n\n
\n
Visit
\n
\n
\n\n\n\n
\n
\n
\n\";}i:3;O:8:\"stdClass\":7:{s:2:\"id\";i:196;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:41:\"Media and text in a full height container\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:1221:\"\n
\n
\"Close-up
\n

What’s the problem?

\n\n\n\n

Trees are more important today than ever before. More than 10,000 products are reportedly made from trees. Through chemistry, the humble woodpile is yielding chemicals, plastics and fabrics that were beyond comprehension when an axe first felled a Texas tree.

\n\n\n\n
\n
Learn more
\n
\n
\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:77:\"Media and text block with image to the left and text and button to the right.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:1:{i:0;s:6:\"header\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1858:\"\n
\n
\"Close-up
\n

What\'s the problem?

\n\n\n\n

Trees are more important today than ever before. More than 10,000 products are reportedly made from trees. Through chemistry, the humble woodpile is yielding chemicals, plastics and fabrics that were beyond comprehension when an axe first felled a Texas tree.

\n\n\n\n
\n
Learn more
\n
\n
\n
\n\";}i:4;O:8:\"stdClass\":7:{s:2:\"id\";i:192;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:37:\"Media and text with image on the left\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:520:\"\n
\"Close-up,
\n

Open Spaces

\n\n\n\n

See case study ↗

\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:66:\"Media and text block with image to the left and text to the right.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:2:{i:0;s:8:\"featured\";i:1;s:6:\"header\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:827:\"\n
\"Close-up,
\n

Open Spaces

\n\n\n\n

See case study ↗

\n
\n\";}i:5;O:8:\"stdClass\":7:{s:2:\"id\";i:195;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:38:\"Media and text with image on the right\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:685:\"\n
\"A
\n

Shore with Blue Sea

\n\n\n\n

Eleanor Harris (American, 1901-1942)

\n
\n\n\n\n

\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:66:\"Media and text block with image to the right and text to the left.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:1:{i:0;s:6:\"header\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1138:\"\n
\"A
\n

Shore with Blue Sea

\n\n\n\n

Eleanor Harris (American, 1901-1942)

\n
\n\n\n\n

\n\";}i:6;O:8:\"stdClass\":7:{s:2:\"id\";i:27;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:5:\"Quote\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:656:\"\n
\n\n\n\n
\"A
\n\n\n\n

“Contributing makes me feel like I’m being useful to the planet.”

— Anna Wong, Volunteer
\n\n\n\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:0:\"\";s:19:\"wpop_viewport_width\";i:800;s:16:\"wpop_block_types\";a:1:{i:0;s:10:\"core/quote\";}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:1:{i:0;s:4:\"text\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1012:\"\n
\n\n\n\n
\"A
\n\n\n\n

\"Contributing makes me feel like I\'m being useful to the planet.\"

— Anna Wong, Volunteer
\n\n\n\n
\n\";}i:7;O:8:\"stdClass\":7:{s:2:\"id\";i:200;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:21:\"Three columns of text\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:801:\"\n
\n
\n

Virtual Tour ↗

\n\n\n\n

Get a virtual tour of the museum. Ideal for schools and events.

\n
\n\n\n\n
\n

Current Shows ↗

\n\n\n\n

Stay updated and see our current exhibitions here.

\n
\n\n\n\n
\n

Useful Info ↗

\n\n\n\n

Get to know our opening times, ticket prices and discounts.

\n
\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:22:\"Three columns of text.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:3:{i:0;s:7:\"columns\";i:1;s:8:\"featured\";i:2;s:4:\"text\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1496:\"\n
\n
\n

Virtual Tour ↗

\n\n\n\n

Get a virtual tour of the museum. Ideal for schools and events.

\n
\n\n\n\n
\n

Current Shows ↗

\n\n\n\n

Stay updated and see our current exhibitions here.

\n
\n\n\n\n
\n

Useful Info ↗

\n\n\n\n

Get to know our opening times, ticket prices and discounts.

\n
\n
\n\";}i:8;O:8:\"stdClass\":7:{s:2:\"id\";i:199;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:34:\"Three columns with images and text\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:2646:\"\n
\n
\n
\n
\n\n\n\n
ECOSYSTEM
\n\n\n\n

Positive growth.

\n\n\n\n
\n
\n
\n\n\n\n
\n
\n

Nature, in the common sense, refers to essences unchanged by man; space, the air, the river, the leaf. Art is applied to the mixture of his will with the same things, as in a house, a canal, a statue, a picture. But his operations taken together are so insignificant, a little chipping, baking, patching, and washing, that in an impression so grand as that of the world on the human mind, they do not vary the result.

\n
\n\n\n\n
\n
\n\n\n\n
\"The
\n
\n\n\n\n
\n
\"Wind
\n
\n
\n\n\n\n
\n
\n
\"The
\n
\n\n\n\n
\n

Undoubtedly we have no questions to ask which are unanswerable. We must trust the perfection of the creation so far, as to believe that whatever curiosity the order of things has awakened in our minds, the order of things can satisfy. Every man’s condition is a solution in hieroglyphic to those inquiries he would put.

\n
\n
\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:77:\"Three columns with images and text, with vertical spacing for an offset look.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:2:{i:0;s:7:\"columns\";i:1;s:8:\"featured\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:3980:\"\n
\n
\n
\n
\n\n\n\n
ECOSYSTEM
\n\n\n\n

Positive growth.

\n\n\n\n
\n
\n
\n\n\n\n
\n
\n

Nature, in the common sense, refers to essences unchanged by man; space, the air, the river, the leaf. Art is applied to the mixture of his will with the same things, as in a house, a canal, a statue, a picture. But his operations taken together are so insignificant, a little chipping, baking, patching, and washing, that in an impression so grand as that of the world on the human mind, they do not vary the result.

\n
\n\n\n\n
\n
\n\n\n\n
\"The
\n
\n\n\n\n
\n
\"Wind
\n
\n
\n\n\n\n
\n
\n
\"The
\n
\n\n\n\n
\n

Undoubtedly we have no questions to ask which are unanswerable. We must trust the perfection of the creation so far, as to believe that whatever curiosity the order of things has awakened in our minds, the order of things can satisfy. Every man\'s condition is a solution in hieroglyphic to those inquiries he would put.

\n
\n
\n
\n\";}i:9;O:8:\"stdClass\":7:{s:2:\"id\";i:201;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:32:\"Three columns with offset images\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:1077:\"\n
\n
\n
\"Close-up,
\n
\n\n\n\n
\n
\n\n\n\n
\n\n\n\n
\"Close-up,
\n
\n\n\n\n
\n
\"Close-up
\n\n\n\n
\n
\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:33:\"Three columns with offset images.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:2:{i:0;s:7:\"gallery\";i:1;s:6:\"images\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1753:\"\n
\n
\n
\"Close-up,
\n
\n\n\n\n
\n
\n\n\n\n
\n\n\n\n
\"Close-up,
\n
\n\n\n\n
\n
\"Close-up
\n\n\n\n
\n
\n
\n\";}i:10;O:8:\"stdClass\":7:{s:2:\"id\";i:29;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:29:\"Two columns of text and title\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:1337:\"\n

The voyage had begun, and had begun happily with a soft blue sky, and a calm sea.

\n\n\n\n
\n
\n

They followed her on to the deck. All the smoke and the houses had disappeared, and the ship was out in a wide space of sea very fresh and clear though pale in the early light. They had left London sitting on its mud. A very thin line of shadow tapered on the horizon, scarcely thick enough to stand the burden of Paris, which nevertheless rested upon it. They were free of roads, free of mankind, and the same exhilaration at their freedom ran through them all.

\n
\n\n\n\n
\n

The ship was making her way steadily through small waves which slapped her and then fizzled like effervescing water, leaving a little border of bubbles and foam on either side. The colourless October sky above was thinly clouded as if by the trail of wood-fire smoke, and the air was wonderfully salt and brisk. Indeed it was too cold to stand still. Mrs. Ambrose drew her arm within her husband’s, and as they moved off it could be seen from the way in which her sloping cheek turned up to his that she had something private to communicate.

\n
\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:47:\"Two columns of text preceded by a long heading.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:2:{i:0;s:7:\"columns\";i:1;s:4:\"text\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1711:\"\n

The voyage had begun, and had begun happily with a soft blue sky, and a calm sea.

\n\n\n\n
\n
\n

They followed her on to the deck. All the smoke and the houses had disappeared, and the ship was out in a wide space of sea very fresh and clear though pale in the early light. They had left London sitting on its mud. A very thin line of shadow tapered on the horizon, scarcely thick enough to stand the burden of Paris, which nevertheless rested upon it. They were free of roads, free of mankind, and the same exhilaration at their freedom ran through them all.

\n
\n\n\n\n
\n

The ship was making her way steadily through small waves which slapped her and then fizzled like effervescing water, leaving a little border of bubbles and foam on either side. The colourless October sky above was thinly clouded as if by the trail of wood-fire smoke, and the air was wonderfully salt and brisk. Indeed it was too cold to stand still. Mrs. Ambrose drew her arm within her husband\'s, and as they moved off it could be seen from the way in which her sloping cheek turned up to his that she had something private to communicate.

\n
\n
\n\";}i:11;O:8:\"stdClass\":7:{s:2:\"id\";i:197;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:39:\"Two columns of text with offset heading\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:1915:\"\n
\n
\n\n\n\n
\n
\n

Oceanic Inspiration

\n
\n\n\n\n
\n
\n
\n
\n\n\n\n
\n
\n\n\n\n
\n

Winding veils round their heads, the women walked on deck. They were now moving steadily down the river, passing the dark shapes of ships at anchor, and London was a swarm of lights with a pale yellow canopy drooping above it. There were the lights of the great theatres, the lights of the long streets, lights that indicated huge squares of domestic comfort, lights that hung high in air.

\n
\n\n\n\n
\n

No darkness would ever settle upon those lamps, as no darkness had settled upon them for hundreds of years. It seemed dreadful that the town should blaze for ever in the same spot; dreadful at least to people going away to adventure upon the sea, and beholding it as a circumscribed mound, eternally burnt, eternally scarred. From the deck of the ship the great city appeared a crouched and cowardly figure, a sedentary miser.

\n
\n
\n\n\n\n
\n
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:43:\"Two columns of text with an offset heading.\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:2:{i:0;s:7:\"columns\";i:1;s:4:\"text\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:2837:\"\n
\n
\n\n\n\n
\n
\n

Oceanic Inspiration

\n
\n\n\n\n
\n
\n
\n
\n\n\n\n
\n
\n\n\n\n
\n

Winding veils round their heads, the women walked on deck. They were now moving steadily down the river, passing the dark shapes of ships at anchor, and London was a swarm of lights with a pale yellow canopy drooping above it. There were the lights of the great theatres, the lights of the long streets, lights that indicated huge squares of domestic comfort, lights that hung high in air.

\n
\n\n\n\n
\n

No darkness would ever settle upon those lamps, as no darkness had settled upon them for hundreds of years. It seemed dreadful that the town should blaze for ever in the same spot; dreadful at least to people going away to adventure upon the sea, and beholding it as a circumscribed mound, eternally burnt, eternally scarred. From the deck of the ship the great city appeared a crouched and cowardly figure, a sedentary miser.

\n
\n
\n\n\n\n
\n
\n\";}i:12;O:8:\"stdClass\":7:{s:2:\"id\";i:19;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:23:\"Two images side by side\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:647:\"\n
  • \"An
  • \"An
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":7:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:41:\"An image gallery with two example images.\";s:19:\"wpop_viewport_width\";i:800;s:16:\"wpop_block_types\";a:0:{}s:11:\"wpop_locale\";s:5:\"en_US\";s:20:\"wpop_unlisted_reason\";s:0:\"\";}s:14:\"category_slugs\";a:1:{i:0;s:7:\"gallery\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:737:\"\n
  • \"An
  • \"An
\n\";}}', 'no'), -(164, '_site_transient_timeout_browser_f2dcfae9f86a6bb04bcd228267797cd3', '1641848978', 'no'), -(165, '_site_transient_browser_f2dcfae9f86a6bb04bcd228267797cd3', 'a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:13:\"96.0.4664.110\";s:8:\"platform\";s:5:\"Linux\";s:10:\"update_url\";s:29:\"https://www.google.com/chrome\";s:7:\"img_src\";s:43:\"http://s.w.org/images/browsers/chrome.png?1\";s:11:\"img_src_ssl\";s:44:\"https://s.w.org/images/browsers/chrome.png?1\";s:15:\"current_version\";s:2:\"18\";s:7:\"upgrade\";b:0;s:8:\"insecure\";b:0;s:6:\"mobile\";b:0;}', 'no'), -(166, '_site_transient_timeout_php_check_0bf95b5f09d09e56bf994b7894d9087c', '1641848979', 'no'), -(167, '_site_transient_php_check_0bf95b5f09d09e56bf994b7894d9087c', 'a:5:{s:19:\"recommended_version\";s:3:\"7.4\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:1;s:9:\"is_secure\";b:1;s:13:\"is_acceptable\";b:1;}', 'no'), -(168, 'can_compress_scripts', '1', 'no'), -(169, '_site_transient_timeout_community-events-6718ef04d3f46d7f6ff6aabe77f33591', '1641287380', 'no'), -(170, '_site_transient_community-events-6718ef04d3f46d7f6ff6aabe77f33591', 'a:4:{s:9:\"sandboxed\";b:0;s:5:\"error\";N;s:8:\"location\";a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}s:6:\"events\";a:0:{}}', 'no'), -(171, '_transient_timeout_feed_9bbd59226dc36b9b26cd43f15694c5c3', '1641287381', 'no'), -(172, '_transient_feed_9bbd59226dc36b9b26cd43f15694c5c3', 'a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:79:\"\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:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"News – – WordPress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"https://wordpress.org/news\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"The latest news about WordPress and the WordPress community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 31 Dec 2021 00:04:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"en-US\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/?v=5.9-beta4-52429\";s:7:\"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:20:{i:0;a:6:{s:4:\"data\";s:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"People of WordPress: Collins Agbonghama\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wordpress.org/news/2021/12/people-of-wordpress-collins-agbonghama/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 Dec 2021 22:45:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:17:\"Contributor Story\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11923\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:130:\"Collins Agbonghama, a web developer from Nigeria, Africa, shares how WordPress gives him a sustainable income and a better future.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"webcommsat AbhaNonStopNewsUK\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:8695:\"\n

In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a website builder from Nigeria, who uses the open source WordPress platform to support his family and to share learning with others in his home country and beyond.

\n\n\n\n
\"Collins
\n\n\n\n

Creating a life in the WordPress Ecosystem

\n\n\n\n

Collins Agbonghama started his journey to becoming a web developer by reading the football news headlines on a friend’s mobile phone. His fascination with development and learning continued to grow, and he now makes a living using WordPress and the web.

\n\n\n\n

Read on to discover his story, which shows with creativity and determination you can create products and make a living using WordPress. 

\n\n\n\n

Starting web building on a phone

\n\n\n\n
\"Collins
\n\n\n\n

Collins began his exploration of the internet while attending Secondary School in Nigeria, or High School as it is known in some other countries. 

\n\n\n\n

A friend at the school had a simple mobile phone which could browse the internet. Collins had his first introduction to the World Wide Web through access to this device. He became hooked by reading headlines on a sports site about a famous English Premier League Football Club, Chelsea, a soccer team which he has long supported.

\n\n\n\n

“Being a very inquisitive person, I wanted to learn how the web works as well as have my own website. I was able to buy a classic mobile phone through the menial jobs I did after school,” he said. 

\n\n\n\n

His first website was a wapsite or Wireless Application Protocol site optimized for mobile devices. 

\n\n\n\n

He took to Google to learn how to actually build a site. He discovered he needed something called an ‘email address’ to sign-up for site builders. Google Search came to the rescue again, and he created the first email account for his first website.

\n\n\n\n

A desire for a website was the catalyst for further learning, starting with HTML and CSS from an online provider. His interest in building sites with more advanced tools grew, and then he came across WordPress. 

\n\n\n\n

Using his savings, he bought the cheapest hosting plan from a local Nigerian web host. He installed WordPress and started writing tutorials for a mobile device platform. He built the site, created the lessons, and started his entry into WordPress all on a mobile phone. 

\n\n\n\n

This led to him having the confidence to start building sites for others, and he was able to earn a small income from that. 

\n\n\n\n

Collins said: “I couldn’t go to the university because of my precarious financial situation. I continued to do menial jobs during the day and started learning PHP in the evenings and at night using my mobile phone via online learning platforms.”

\n\n\n\n

He was later able to get an old laptop, which helped him access ebooks to learn more and practice his coding. 

\n\n\n\n

Keen to share this learning, he started blogging about what he was learning on his website.  

\n\n\n\n

Collins said: “I later took up a job teaching children at a school primarily because I got tired of the menial jobs and wanted to earn enough to take care of my internet data plan. After a while, I became fairly proficient in PHP and even took up a job to build a school management system.”

\n\n\n\n

Using WordPress to make a living

\n\n\n\n

Collins’ blog wasn’t making money through advertisements, but he discovered opportunities to write tutorials for other platforms. 

\n\n\n\n

“I started writing PHP and WordPress development tutorials and got paid a few hundred dollars per article. In Nigeria, that’s quite a lot of money. I was able to improve the life and wellbeing of my family and myself,” he said.

\n\n\n\n

After getting into a higher education program to study computer science, his life dramatically changed. He decided to stop writing and began to focus on building and selling WordPress plugins. His first one was a user and profile plugin for WordPress sites.

\n\n\n\n

“Thankfully, after a year, it started making enough revenue for me to live pretty comfortably here in Nigeria because the cost of living here is relatively low,” he said

\n\n\n\n

Today, Collins has several plugins which have given him a sustainable source of income. He’s also a Core and Translation volunteer contributor to the WordPress.org Open Source project.

\n\n\n\n

I am thankful for WordPress because without it, I’m really not sure I would have been able to live a decent quality life.
Who knows what would have become of me?

Collins Agbonghama
\n\n\n\n

“I am also thankful for the community. I have made lots of friends that have been very supportive and helpful in my journey.”

\n\n\n\n

He added: “I tell people, life won’t give you what you want. You demand from life what you want. You make these demands by being determined and never giving up on your dreams and aspirations.

\n\n\n\n

“If you are poor, perhaps because you came from a humble and poor background, it is not your fault. You can’t go back in time to change things. I implore you to be strong, determined, and work hard.”

\n\n\n\n

\n\n\n\n

Meet more WordPress community members in our People of WordPress series.

\n\n\n\n

Contributors

\n\n\n\n

Thanks to Michael Geheren (@geheren), Abha Thakor (@webcommsat), for writing this feature, to @MeherBala (@meher) for follow-ups and photo-editing, and to Chloe Bringmann (@cbringmann) and Nalini Thakor (@nalininonstopnewsuk) for the final proofing. Thank you to Collins Agbonghama (@collizo4sky) for sharing his Contributor Story.

\n\n\n\n

Thanks to Josepha Haden Chomphosy (@chanthaboune), Topher DeRosia (@topher1kenobe) and others for their support of this initiative.

\n\n\n\n

The People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia, which highlights people in the WordPress community who have overcome barriers. 

\n\n\n\n

#HeroPress #ContributorStory

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11923\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:66:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.9 Beta 4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2021/12/wordpress-5-9-beta-4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 Dec 2021 21:17:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:4:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:4:\"beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11876\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"WordPress 5.9 Beta 4 released on 21 December 2021 and is available for testing. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5158:\"\n

WordPress 5.9 Beta 4 is now available for testing!

\n\n\n\n

This software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.

\n\n\n\n

You can test the WordPress 5.9 Beta 4 in three ways:

\n\n\n\n

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

\n\n\n\n

Option 2: Direct download the beta version here (zip).

\n\n\n\n

Option 3: When using WP-CLI to upgrade from Beta 1, 2, or 3 to Beta 4 on a case-insensitive filesystem, please use the following command sequence:

\n\n\n\n

Command One:

\n\n\n\n
wp core update --version=5.9-beta4
\n\n\n\n

Command Two:

\n\n\n\n
wp core update --version=5.9-beta4 --force
\n\n\n\n

The current target for the final release of 5.9 is January 25, 2022, which is only five weeks away. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

\n\n\n\n

Some Highlights

\n\n\n\n

Since Beta 3, 20 bugs have been fixed. Here are a few of the changes you will find in Beta 4:

\n\n\n\n
  • Bundled Theme: Fixed duplicate CSS rules in Twenty Twenty-One theme (#53605).
  • Customizer: It’s possible to switch to a block theme from within Customizer (#54549).
  • Themes: Provide guidance to users seeking to preview block themes on WordPress versions below 5.9 (#54575).
  • REST API: The get_theme_item method should respect fields param (#54595).
  • Editor: Block Patterns: “Featured” category & patterns missing from inserter (#54623).
  • Login and registration: Add a filter to allow to disable the Login screen language dropdown – (#54675).
\n\n\n\n

How You Can Help

\n\n\n\n

Do some testing!

\n\n\n\n

Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute. 

\n\n\n\n

Please post to the Alpha/Beta area in the support forums if you find a bug. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

\n\n\n\n

Got questions? Here are some answers

\n\n\n\n

In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that will cover these items in detail.

\n\n\n\n

So far, contributors have fixed 326 tickets and 108 new features and enhancements in WordPress 5.9. More bug fixes are on the way with your help through testing.

\n\n\n\n

Props to @cbringmann, @psykro, @hellofromtonya, @marybaum, @webcommsat, @audrasjb, @cbringmann, @costdev and @meher for contributions to this post.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11876\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:58:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"WP Briefing: Episode 22: A Carol of Thanks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://wordpress.org/news/2021/12/episode-22-a-carol-of-thanks/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 20 Dec 2021 19:22:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11880\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:404:\"In this last episode of 2021, Josepha Haden Chomphosy takes the time to appreciate those who make the WordPress project a success and offers a carol of thanks. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho Production: Chloé Bringmann Song: […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/12/WP-Briefing-022.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5720:\"\n

In this last episode of 2021, Josepha Haden Chomphosy takes the time to appreciate those who make the WordPress project a success and offers a carol of thanks.

\n\n\n\n

Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.

\n\n\n\n

Credits

\n\n\n\n\n\n\n\n

References

\n\n\n\n

Have yourself A Merry Little Christmas

\n\n\n\n

Transcript

\n\n\n\n\n\n\n\n

Josepha Haden Chomphosy  00:10

\n\n\n\n

Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project. Some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!

\n\n\n\n

Josepha Haden Chomphosy  00:39

\n\n\n\n

So, ages and ages ago, when I first started this podcast, someone basically requested that Matt and I do a duet for the last podcast of the year. A Christmas carol duet; him on the saxophone and me on voice. I obviously did not get that coordinated I don’t even know why I said obviously. I’ll tell you right now I did not get that coordinated. I was a very busy lady this year. So I don’t have a Matt on saxophone. Still, I did think that maybe it might be nice just for me to sing a teensy little Christmas carol for you all just because it seems especially poignant the words this year, especially after the 2020, 2021 COVID, all the things and trying to get back in person. So I’m going to sing you all one little verse from Have Yourself a Merry Little Christmas.

\n\n\n\n

Josepha Haden Chomphosy 01:35 Singing  

\n\n\n\n

Have yourself a merry little Christmas

\n\n\n\n

Let your heart be light

\n\n\n\n

From now on our troubles

\n\n\n\n

Will be out of sight

\n\n\n\n

Have yourself a merry little Christmas

\n\n\n\n

Make the Yuletide gay

\n\n\n\n

From now on our troubles

\n\n\n\n

Will be miles away

\n\n\n\n

Here we are as in olden days

\n\n\n\n

Happy golden days of yore

\n\n\n\n

Faithful friends who are dear to us

\n\n\n\n

Gather near to us, once more

\n\n\n\n

Through the years we all will be together

\n\n\n\n

If the fates allow

\n\n\n\n

Hang a shining star upon the highest bough

\n\n\n\n

And have yourself a merry little Christmas now

\n\n\n\n

Here we are as in olden days

\n\n\n\n

Happy golden days of yore

\n\n\n\n

Faithful friends who are dear to us

\n\n\n\n

Gather near to us, once more

\n\n\n\n

Through the years we all will be together

\n\n\n\n

If the fates allow

\n\n\n\n

Hang a shining star upon the highest bough

\n\n\n\n

And have yourself a merry little Christmas now

\n\n\n\n

Josepha Haden Chomphosy  03:34

\n\n\n\n

Alright, my friends, that was from my heart to yours if you happened to listen. If you skipped a few seconds to get through it, which I would totally understand, that is also fine. But I did want to just kind of wrap up the year to let you all know that I am so incredibly grateful for all of the people who show up for the WordPress project to make it a success. I have made so many friends and wonderful acquaintances throughout my time here with the WordPress project. And especially in my three years as the project’s Executive Director. You all have put a lot of trust in me and a lot of faith. And I know that we have gotten so much done together in the last few years. And I am equally sure that we’re going to get so much done in the years to come. And so thank you all so much for your continued work with WordPress and the way that you just bring your best at all times. 

\n\n\n\n

Josepha Haden Chomphosy  04:32

\n\n\n\n

One other little thanks I want to give. Over the course of this year, I’ve had an excellent team that works with me on this podcast. I have editing and design folks and people who’ve joined me here and there, folks who helped me with my production. So big thank you to Dustin, Bea, I realize your name is Beatriz in the actual credits, but I call you Bea, and so thank you. Also, a huge thank you to Chloé, who does all of our production and wrangling every couple of weeks. A big round of applause and kudos to that tiny but tough team that helps me get this all done.

\n\n\n\n

Josepha Haden Chomphosy  05:10

\n\n\n\n

That’s to go on top of the general thanks to the WordPress project. And if you all are celebrators, I hope you have a wonderful holiday season. If you are not celebrators, I hope that you have a wonderful end to your year and that everything you wanted to get done, you did get done, and that you can start 2022 with a fresh slate. Again, this is the WP Briefing. Thank you so much for listening. I’m your host Josepha Haden Chomphosy, and I’ll see you again in 2022.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11880\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"Highlights from State of the Word 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wordpress.org/news/2021/12/highlights-from-state-of-the-word-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Dec 2021 01:04:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:6:\"WrapUp\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11869\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"Highlights and the official video for State of the Word 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Anjana Vasan\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3651:\"\n
\n\n
\n\n\n\n

State of the Word 2021, the annual keynote from WordPress co-founder Matt Mullenweg, happened on December 14. The hybrid event took place in New York City with a small audience (proof of vaccination required). As Matt said, “we had people join by plane, train, and automobile.” Those who didn’t make the trek to the live event watched the livestream from wherever they call home, all around the world. 

\n\n\n\n

It was an exciting moment for the WordPress community which also celebrated its first in-person WordCamp in Sevilla, Spain, after a lengthy hiatus for in-person events.

\n\n\n\n

You can view the full recording, complete with captions and transcripts on WordPress.tv.

\n\n\n\n

It was thrilling to see so many meetup organizers host watch parties worldwide. Twenty-six watch parties were held across eleven countries, with more than 300 RSVPs.  

\n\n\n\n

Similar to past State of the Word events, Matt covered a broad range of topics. This year was no different. WordPress’ past, present, and future were in the spotlight, with highlights on the growth of the contributors, language translations, recent release milestones, and educational initiatives, to name a few.

\n\n\n\n

Audience members and livestreamers alike viewed product demos showcasing upcoming features that will be the hallmark of WordPress 5.9, such as full site editing, block patterns, global styling options, and enhanced image controls.

\n\n\n\n

Matt took the opportunity to remind everyone of the WordPress roadmap which includes native multi-lingual support and real-time collaborative site editing. He also pointed out that anyone can contribute to WordPress’ progress through a number of different initiatives ranging from creating new features and testing to helping spread the word and educate others.

\n\n\n\n

Matt emphasized the way that open source software gets better by reminding everyone that “The more people that use a program like WordPress, the better it gets.”

\n\n\n\n

Broader topics covering the tech landscape including web3, merger and acquisition activity, as well as the growth and support of open source software, rounded out the energetic presentation. 

\n\n\n\n

The one-hour multimedia presentation was followed by an interactive question and answer session where Matt fielded questions that were submitted ahead of the event, as well as questions from the livestream and studio audience.

\n\n\n\n

Discover everything that was covered by watching the official event recording and join the ongoing #ILoveWP conversation on Twitter!

\n\n\n\n

Special thanks to @dansoschin for review and edits!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11869\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.9 Beta 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2021/12/wordpress-5-9-beta-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Dec 2021 20:19:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:4:\"beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:11:\"development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11835\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:102:\"WordPress 5.9 Beta 3 is now available for testing. Help test to make the release as good as it can be.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6087:\"\n

WordPress 5.9 Beta 3 is now available for testing!

\n\n\n\n

This software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.

\n\n\n\n

You can test the WordPress 5.9 Beta 3 in three ways:

\n\n\n\n

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

\n\n\n\n

Option 2: Direct download the beta version.

\n\n\n\n

Option 3: If you use WP-CLI to upgrade from Beta 1 or Beta 2 to Beta 3 on a case-insensitive filesystem, please use the following command sequence:

\n\n\n\n

Command One:

\n\n\n\n
wp core update --version=5.9-beta2
\n\n\n\n

Command Two:

\n\n\n\n
wp core update --version=5.9-beta3 --force
\n\n\n\n

The current target for the final release of 5.9 is January 25, 2022, which gets closer every minute. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

\n\n\n\n

Some Highlights

\n\n\n\n

Since Beta 2, 14 bugs have been fixed. Here are a few of the changes you will find in Beta 3:

\n\n\n\n
  • Editor: Add FSE infrastructure from Gutenberg plugin into Core (#54335).
  • Formatting: Allow PDFs to embedded as objects (#54261)
  • Language switcher on the login screen (#43700)
  • REST API: Add navigation areas REST API endpoint from Gutenberg plugin (#54393)
  • Themes: Live Preview button bug (#54578)
\n\n\n\n

How You Can Help

\n\n\n\n

Do some testing!

\n\n\n\n

Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute. 

\n\n\n\n

If you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.

\n\n\n\n

For even more ways to test, you can also refer to this official Full Site Editing post from @annezazu.

\n\n\n\n

Got questions? Here are some answers

\n\n\n\n

In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that cover these items in detail. So far, contributors have fixed 316 tickets in WordPress 5.9, including 100 new features and enhancements. More bug fixes are on the way with your help through testing.

\n\n\n\n

Props to @psykro, @estelaris, @hellofromtonya, @marybaum, @webcommsat, @cbringmann, @costdev, and @audrasjb for contributions to this post.

\n\n\n\n

Filed under #release, #5.9, #beta

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11835\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:75:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.9 Beta 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2021/12/wordpress-5-9-beta-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 07 Dec 2021 22:02:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:7:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:4:\"beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:6:\"Beta 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:12:\"block editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:6;a:5:{s:4:\"data\";s:11:\"WP releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11794\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"Can you help test the latest software version of WordPress? 5.9 Beta 2 was published on 7 December 2021, help find any bugs. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6225:\"\n

WordPress 5.9 Beta 2 is now available for testing!

\n\n\n\n

This software version is still under development. Please do not run this software on a production site. Instead, install it on a test site, where you can try out the newest features to get a feel for how they will work on your site.

\n\n\n\n

You can test the WordPress 5.9 Beta 2 in three ways:

\n\n\n\n

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

\n\n\n\n

Option 2: Direct download the beta version here (zip).

\n\n\n\n

Option 3: When using WP-CLI to upgrade from Beta 1 to Beta 2 on a case-insensitive filesystem, please use the following command sequence:

\n\n\n\n

Command One:

\n\n\n\n
wp core update --version=5.9-beta1
\n\n\n\n

Command Two:

\n\n\n\n
 wp core update --version=5.9-beta2 --force
\n\n\n\n

The current target for the final release of 5.9 is January 25, 2022, which is just seven weeks away. Your help testing this version is a vital part of making this release as good as it can be.

\n\n\n\n

Some Highlights

\n\n\n\n

Since Beta 1, 24 bugs have been fixed. Here are a few of the changes you will find in Beta 2:

\n\n\n\n
  • Block Editor: Remove navigation areas (#54506)
  • Block Editor: Navigation block view JavaScript error (#54456)
  • Block Editor: Block template theme error related to child themes (#54515)
  • General: Fixing existing links to Customizer when the Site Editor is enabled (#54460)
  • Media: Media library showing only the selected image (#53765)
  • Media: Fatal error uploading media on PHP8 (#54385)
  • REST API: Add Global Styles REST API endpoints from Gutenberg into Core (#54336)
\n\n\n\n

Also, note that some users testing 5.9 Beta 1 faced some fatal errors upon upgrade. In turn, these errors revealed the need for some extra work on the filesystem and upgrader. Those fatal errors are no longer a problem, and the enhancements will be part of version 6.0.

\n\n\n\n

How You Can Help

\n\n\n\n

Do some testing!

\n\n\n\n

Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute. 

\n\n\n\n

If you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.

\n\n\n\n

Where can I get more information?

\n\n\n\n

In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that cover these items in detail.

\n\n\n\n

So far, contributors have fixed 305 tickets in WordPress 5.9, including 110 new features and enhancements. More bug fixes are on the way with your help through testing.

\n\n\n\n

Props to @psykro, @estelaris, @hellofromtonya, @marybaum, @webcommsat, @cbringmann, @davidb, @audrasjb, and @pbiron for contributions to this post.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11794\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"The Month in WordPress – November 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2021/12/month-in-wordpress-november-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 02 Dec 2021 11:30:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:22:\"the month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11763\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:337:\"Despite the holiday season being around the corner, the WordPress project didn’t slow down. In a recent episode of WP Briefing, Executive Director Josepha Haden shares the first thing she wants people to notice about WordPress, which is also the heart of this open source project: “Now, the first thing I want people to see […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Anjana Vasan\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:18201:\"\n

Despite the holiday season being around the corner, the WordPress project didn’t slow down. In a recent episode of WP Briefing, Executive Director Josepha Haden shares the first thing she wants people to notice about WordPress, which is also the heart of this open source project:

\n\n\n\n

“Now, the first thing I want people to see on that site is that WordPress has not only 18 years of learned knowledge that every single new user benefits from, but that it also has thousands of really smart people making sure it works and gets better every day.”

\n\n\n\n

As always, contributors across various teams are working hard to ensure the upcoming release of WordPress 5.9 doesn’t disappoint. With State of the Word 2021 coming up soon, there are many exciting things in the works. Read the November 2021 edition of the Month in WordPress to learn more about what’s happening.

\n\n\n\n
\n\n\n\n

WordPress 5.9: Expected to release on January 25, 2022

\n\n\n\n
\n\n\n\n
\"\"
\n\n\n\n
\n\n\n\n
  • The Core Team announced the WordPress 5.9 Revised Release Schedule, and the release is now planned for January 25, 2022.
  • WordPress 5.9 Beta 1 was recently released and is available for testing. This version of the WordPress software is under development. Check out the release post to learn more about what’s new in version 5.9 and how you can help testing. 
  • Check out “A Look at WordPress 5.9” for a first peek into the exciting features included in this major release.
  • WordPress 5.8.2, a security and maintenance release, was out on November 10, 2021. This release includes two bug fixes and one security fix.
\n\n\n\n
\n\n\n\n

Are you interested in contributing to WordPress core? Join the #core channel, follow the Core Team blog, and check out the team handbook. Also, don’t miss the Core Team’s weekly developer chat on Wednesdays at 8 PM UTC.

\n\n\n\n
\n\n\n\n

Gutenberg releases: 11.9 and 12.0 are out

\n\n\n\n

Two new Gutenberg versions have been released!

\n\n\n\n
  • Version 11.9.0 brings new Gutenberg blocks for working with post comments, a fullscreen pattern explorer modal, further iterations on the Navigation block, and many other improvements.
  • Gutenberg 12.0.0, released on November 24, improves the Block Styles preview and includes featured image block visual enhancements, a site Editor welcome guide, official JSON schema updates, and much more.
\n\n\n\n
\n\n\n\n

Want to get involved in developing Gutenberg? Follow the Core Team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Make WordPress Slack. Follow #gutenberg-new for details on the latest updates.

\n\n\n\n
\n\n\n\n

State of the Word 2021: Join a watch party in your local community

\n\n\n\n
\n\n\n\n
\"State
\n\n\n\n
\n\n\n\n\n\n\n\n
\n\n\n\n

Add the event to your calendar so you don’t miss State of the Word 2021! Want to ask Matt a question during State of the Word? Please send your questions ahead of time to ask-matt@wordcamp.org or ask them live during the event via YouTube chat.

\n\n\n\n
\n\n\n\n

Team updates: Nominations for some team representatives are still underway

\n\n\n\n\n\n\n\n
\n\n\n\n

We want to hear from you! Suggest your 2022 goals for the Global Community Team by December 6, 2021.

\n\n\n\n
\n\n\n\n

Feedback/Testing requests: Test WordPress 5.9 Beta 1; Take the 2021 Annual WordPress Survey to share your experience

\n\n\n\n
  • WordPress 5.9 Beta 1 is now available for testing and we’d like to hear from you! Testing is vital to ensure the release is as good as it can be—it’s also a great way to contribute. Read the comprehensive guide, “Help test WordPress 5.9 Features,” to learn how to test WordPress 5.9 Beta 1 and report any bugs.
  • There’s an open call for testing for WordPress iOS 18.7 and Android 18.7.
\n\n\n\n
\n\n\n\n

The 2021 WordPress Annual Survey is out! Please respond to the survey, so your WordPress experience is reflected in the results.

\n\n\n\n
\n\n\n\n

Keep an eye out for WordCamp Taiwan and Sevilla, along with several WordPress workshops in December 2021

\n\n\n\n\n\n\n\n
\n\n\n\n

Give back to open source. Please donate to the WordPress Foundation’s mission this holiday season.

\n\n\n\n
\n\n\n\n

Have a story that we could include in the next ‘Month in WordPress’ post? Let us know  by filling out this form. 

\n\n\n\n

The following folks contributed to November 2021’s Month in WordPress: @anjanavasan, @harishanker, @rmartinezduque, @callye, @jrf, @webcommsat, and @nalininonstopnewsuk

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11763\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.9 Beta 1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2021/11/wordpress-5-9-beta-1/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 30 Nov 2021 23:35:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11584\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:307:\"WordPress 5.9 Beta 1 is now available for testing! This version of the WordPress software is under development. You don’t want to run this version on a production site. Instead, it is recommended that you run this on a test site. This will allow you to test out the new version. You can test the […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:10992:\"\n

WordPress 5.9 Beta 1 is now available for testing!

\n\n\n\n

This version of the WordPress software is under development. You don’t want to run this version on a production site. Instead, it is recommended that you run this on a test site. This will allow you to test out the new version.

\n\n\n\n

You can test the WordPress 5.9 Beta 1 in three ways:

\n\n\n\n
  • Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
  • Option 2: Direct download the beta version here (zip).
  • Option 3: Use WP-CLI to test: wp core update --version=5.9-beta1. Do not use this option if your filesystem is case-insensitive.
\n\n\n\n

The current target for the final release is January 25, 2022, which is just eight weeks away. Your help testing this version is vital to make sure the release is as good as it can be.

\n\n\n\n

Check the Make WordPress Core blog for 5.9-related developer notes in the coming weeks which will break down all upcoming changes in greater detail.

\n\n\n\n

How You Can Help – Testing!

\n\n\n\n

Testing for bugs is a critical part of polishing the release in the beta stage. It is also a great way to contribute. If you’ve never tested a beta release before, this detailed guide will help walk you through what and how to test.

\n\n\n\n

If you think you’ve found a bug, please report it to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.

\n\n\n\n

To see every feature in the Gutenberg releases since WordPress 5.8, check out the What’s New In Gutenberg posts for 10.8, 10.9, 11.0, 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 11.7, 11.8, and 11.9. 

\n\n\n\n

Beyond the noted changes, which include 580 enhancements and nearly 450 bug fixes, contributors have fixed 297 tickets for WordPress 5.9, including 110 new features and enhancements. More fixes are on the way.

\n\n\n\n

Happy testing!

\n\n\n\n

Want to know what’s new in version 5.9? Read on for some highlights.

\n\n\n\n
\n\n\n\n

Full Site Editing

\n\n\n\n

The Styles Interface

\n\n\n\n

Combine all the features that went live in 5.8 with those making their entrance in 5.9, and you get Full Site Editing.

\n\n\n\n

Formerly known as Global Styles, the Styles Interface lets you interact directly with your blocks and elements right in the WordPress Admin. From typography to color palettes, this cohesive design interface means a design change—even a dramatic one—can happen without a theme switch. No code needed.

\n\n\n\n

Theme.json

\n\n\n\n

Introduced in WordPress 5.8, theme.json has been improved to enable features and default styles for your site and its blocks. With 5.9, theme.json can support child themes and the duotone treatment. Coordinate layers of style with theme.json, taking the weight off of your theme’s required CSS.

\n\n\n\n

Other features supported by theme.json include:

\n\n\n\n
  • Border: color, style, and width augment the border-radius property that landed in 5.8.
  • Flex layouts: Block Gap support, courtesy of spacing.blockGap.
  • Typography: font families, font style, font weight, text decoration, and text transform.
  • Images: Duotones.
\n\n\n\n

A New Navigation Block

\n\n\n\n

Welcome to the most intuitive way to build navigation: the Navigation Block. 

\n\n\n\n

Here are the features that need testing the most:

\n\n\n\n
  • Responsive menu options you can turn off, have always on, or opt to use only for small screens.
  • Built-in keyboard accessibility.  For accessibility, for speed, or both.
  • Add extra blocks like Search and Site Icon blocks (and customize them to your liking).
  • Submenu items with styling options.
  • Horizontal or vertical alignment.
  • Reusable navigation? Even across themes? Yes. Because the Navigation Block you build gets saved as a custom post type.
\n\n\n\n\n\n\n\n

What if you could treat single images in your Gallery Block the same way you treat the Image Block? Now you can.

\n\n\n\n

Make every image in your gallery different from the next, with inline cropping or a duotone and change layouts with the ease of drag and drop. With the improved gallery block, every image is its own Image block.

\n\n\n\n

One thing to note: Have you built a plugin or theme on the Gallery Block functionality? Be sure to review this Dev Note, which details what you need to do for compatibility.

\n\n\n\n

Focused Template Part Mode

\n\n\n\n

Building template parts can take a level of focus all its own because you’re making decisions for the entire site. So WordPress 5.9 adds a focus mode that shows you only the part you’re working on right now (and you can get back to the regular view with a keystroke). 

\n\n\n\n

Block Pattern Directory

\n\n\n\n

The Pattern Directory offers a range of prebuilt block patterns, from a couple of blocks that show an image and text, to an entire page layout with columns and sections. Since the 5.8 release, the directory has become a hub for exploratory UI and patterns, taking submissions and offering them to the community. So now, your creation can help other people build out their perfect site.

\n\n\n\n

Twenty Twenty-Two Default Theme

\n\n\n\n

A whole new way of building WordPress themes.

\n\n\n\n

WordPress 5.9 introduces features that make Full Site Editing possible, including the first default block theme.

\n\n\n\n

Using minimal CSS, theme styles reside in theme.json so that you can configure them in the Styles interface of the WordPress Admin. Make this theme take on its own personality site-wide, with a wide array of color schemes, type combinations, page templates, premade components (forms), and image treatments to choose from.

\n\n\n\n

More Improvements and Updates

\n\n\n\n
  • Do you love to blog? New tweaks to the publishing flow let you add new posts just seconds after hitting Publish on your latest post.
  • List View lets you drag and drop content as easily as you could always cruise through it – and collapse entire sections – so you can concentrate on a task or get the bigger picture.
  • The Buttons and Social icons blocks now absorb and display their parent block’s toolbar controls.  
  • Choose your language on the login screen.
  • More performance improvements (i.e., speed).
\n\n\n\n

Props to @chanthaboune, @priethor, @psykro, @annezazu, @webcommsat, @marybaum, @hellofromtonya, @davidbaumwald, and @rmartinezduque for their research and copy.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11584\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:72:\"\n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"People of WordPress: Devin Maeztri\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2021/11/people-of-wordpress-devin-maeztri/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 30 Nov 2021 22:21:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:6:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:17:\"Contributor Story\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:9:\"Indonesia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:20:\"Polyglot Contributor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11678\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:111:\"Devin Maeztri, a campaigner from Indonesia talks about the difference WordPress makes in her life and her work.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"webcommsat AbhaNonStopNewsUK\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:16562:\"\n

In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a translator and campaigner who uses WordPress to highlight good causes and helps people in her area benefit from the open source platform.

\n\n\n\n
\"Devin
\n\n\n\n

Going to a WordCamp can be a life-changing experience, as Devin Maeztri discovered. Every event she attends is a further step on a journey of discovering the WordPress community and its many opportunities.

\n\n\n\n

“It is not that hard to fall for WordPress if you have a chance to experience WordPress. For me, it took a WordCamp.”

Devin Maeztri
\n\n\n\n

Devin’s first experience with camps came when she volunteered impromptu at an Indonesian event, WordCamp Denpasar, Bali in 2016. 

\n\n\n\n

Here, she made a profound discovery: “WordCamps can bring people who will give back to the community, even if they don’t get anything from WordPress directly.”

\n\n\n\n

With every WordCamp after that first experience, she became more interested in WordPress and the community. 

\n\n\n\n

Over time, Devin found she wanted to be part of WordPress events more often. She became a regular at Meetups in Ubud and Jakarta, joining as a co-organizer at WordCamp Jakarta in 2017 and 2019. Later, she took on the role of co-organizer for Meetups in Jakarta and Ubud. 

\n\n\n\n

Smitten by what WordCamps can offer and how they can bring people together across national borders, she joined the organizing team for WordCamp Asia 2020. Sadly, this event was to become the first major WordPress event to be cancelled in the COVID-19 pandemic. 

\n\n\n\n

Naturally, Devin hopes WordCamp Asia will happen someday very soon. Beyond the expected WordPress learning and sharing that event will promote, she believes its very scale will showcase how WordCamps add international tourism and cultural understanding everywhere they take place.

\n\n\n\n
\"Devin
WordCamp Asia 2020 Organizers at WordCamp Europe 2019. Devin is pictured in the front row, second from left. Photo Credit: Abha Thakor
\n\n\n\n

Showing how WordPress can be used locally

\n\n\n\n

After experiencing several events, Devin had questions: “At WordCamps and Meetups, you hear stories about how WordPress powers the web. How it changes the lives of so many people, how it helps dreams come true. It made me think, considering WordPress is that powerful, why are there not even more people in Indonesia using websites, and more using WordPress? Why aren’t more talented Indonesian WordPress users, developers, designers, and business owners taking part in WordPress.org projects? Language, for me, was the main answer.”

\n\n\n\n

The solution Devin felt was to make WordPress available in the main local language. She said: “I believe, the more content translated into Indonesian, the more Indonesian WordPress users see WordPress as more than just a blogging platform or a content management system. They will realize it’s a huge open source community that works together to make the web a better place. The more plugins and themes translated, the easier the work of the developer and designer will be. The more people see how WordPress can enhance their life, the better the ecosystem for business owners becomes.”

\n\n\n\n

Encouraging others to translate WordPress

\n\n\n\n

After talking with others about how WordPress could be even more useful in Indonesia, Devin felt she had to make a personal commitment to reviving the polyglot project in Indonesia. With another volunteer contributor and through promotion, the local polyglot team got bigger and the interest in translation grew. She also took on the responsibility of a General Translation Editor for the language.

\n\n\n\n
\"Polyglot
\n\n\n\n

Through the efforts of Devin and the other translation editors, Indonesia took part in WordPress Translation Day in 2020, and in 2021 held sprints and learning sessions spanning the whole 30 days of the event.

\n\n\n\n

Her enthusiasm and dedication to helping others translate WordPress locally and promoting the global community were recognized in the Polyglot Appreciation Nominations for 2021.

\n\n\n\n

Helping to give access to more diverse audiences

\n\n\n\n

Through her involvement in translation, Devin noticed there were not many women involved in the WordPress community in Indonesia. Often, she found herself the only woman at an event.

\n\n\n\n

So, along with a couple of community members, she started Perempuan WordPress, a local initiative. This group is open for everyone to join, but prioritizes women as event speakers.

\n\n\n\n

Devin has gone on to support the work of the Diversity Speaker Training group in the Community Team, translating materials and promoting initiatives in Indonesia. She is keen to encourage others to get involved with this initiative which helps increase the diversity of presenters at Meetups and WordCamps.

\n\n\n\n
\"\"
Organizing at WordCamp Jakarta 2019
\n\n\n\n

In her professional roles, Devin is an advocate for WordPress as a tool for people with a wide variety of skill sets. She does not code, but uses the platform extensively for her projects. In 2014, she signed up for a free account on WordPress.com to keep and share notes about what she saw or was thinking about as she commuted on public transport to work. This site did not turn into a blog, but instead introduced her to other opportunities and the vast capabilities of the platform.

\n\n\n\n

WordPress can support your skills and passions

\n\n\n\n

With a background in environmental activism, Devin has worked for international development organizations on everything from policymaking to campaigning. 

\n\n\n\n

Behind the desk, she worked with policymakers and organized conferences and meetings. That meant doing a lot of writing and translating and working with people on the ground who were impacted by the policies. “My work on the ground usually involved researching, movement building and community empowerment,” she noted.

\n\n\n\n

Her work with events inspired Devin to get involved in WordCamps and Meetups and share her energy for making things happen. As in her professional work, she felt WordPress was an opportunity to work and share with people about something that can make a positive impact on someone else’s life.

\n\n\n\n

“For me, everything comes from the heart. I do things that I feel so strongly about. Things that call me, and things that I am good at but still giving me room to learn and become better at. WordPress can be the perfect place for this.”

\n\n\n\n

While she was between jobs, Devin was encouraged to volunteer at WordCamp Denpasar 2016. With some help, she created an online CV. She also learned to manage a WordPress site, navigate the wp-admin, and make the content appeal to potential employers. 

\n\n\n\n

She eventually got a job as a campaigner to build a movement online and offline. The brainchild of many university friends in America, who used digital campaigns to go global, the campaign used WordPress. 

\n\n\n\n

Devin worked alongside a digital campaigner and helped shape the content, the call to action, and the user experience. She also had to use the wp-admin to make some amendments. As a global movement, it developed its resources in English, so she also reviewed the work of the translators she worked with.

\n\n\n\n
\"One
Devin’s cat became a regular on social media posts about #WPTranslationDay 2021
\n\n\n\n

She left her job as a campaigner at the end of 2018 to concentrate on freelancing – and to spend more of her free time contributing to the WordPress community. She also took up the initiative to help street cats in Jakarta. 

\n\n\n\n

Devin said: “So, I am busy helping these cats but also learning how to fundraise using a website. I’m learning to use online forms, set up a payment service provider, work on SEO, and do other new things I need to learn to grow my initiative. I do have the privilege to learn directly from a personal guru. The same person who convinced me to volunteer at WordCamp Denpasar, and who I married in 2018.”

\n\n\n\n

WordPress gives everyone a chance to learn

\n\n\n\n

Devin was so enthused by being a contributor for WordPress, she took part in the video shorts following the Translation Day events.

\n\n\n\n
\n\n
Devin talks about translating in this short video (opens in a new tab on YouTube)
\n\n\n\n

She is also active in other Contributor Teams and decided to become a Community Team Deputy to support meetups in new cities across Indonesia and perhaps future WordCamps. 

\n\n\n\n

She said: “One of the things that I like about WordPress is that it is very welcoming and open to people like me, who don’t code at all. At the same time, it shows me a different way of looking at the world.”

\n\n\n\n

Devin believes in the power of WordPress to give ‘everyone a chance to learn new things’ and allows her to contribute and share her knowledge and experience. “By contributing, I hope to make a difference in someone’s life. I hope they feel the benefit of using WordPress and want to give back to create a healthier WordPress community.”

\n\n\n\n

Contributors

\n\n\n\n

Thank you to Abha Thakor (@webcommsat) and Mary Baum (@marybaum) for the interviews and writing this feature, and to Devin Maeztri (@devinmaeztri) for sharing her story. Thanks to Meher Bala (@meher) for work on the images, and to Chloé Bringmann (@cbringmann) and Collieth Clarke (@callye) for proofing.

\n\n\n\n

Thanks to Josepha Haden Chomphosy (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support for the series.

\n\n\n\n

This People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress #ContributorStory

\n\n\n\n

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11678\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:55:\"\n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"WP Briefing: Episode 21: All Things Block Themes!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://wordpress.org/news/2021/11/episode-21-all-things-block-themes/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 29 Nov 2021 12:07:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11636\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:436:\"In episode 21 of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy, talks all things block themes with developers and theme specialists Maggie Cabrera and Jeff Ong. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho Production: Chloé Bringmann Song: Fearless […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/11/WP-Briefing-021.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:26887:\"\n

In episode 21 of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy, talks all things block themes with developers and theme specialists Maggie Cabrera and Jeff Ong.

\n\n\n\n

Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.

\n\n\n\n

Credits

\n\n\n\n\n\n\n\n

References

\n\n\n\n\n\n\n\n

Transcript

\n\n\n\n\n\n\n\n

Josepha Haden Chomphosy  00:11

\n\n\n\n

Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. See, here we go!

\n\n\n\n

Josepha Haden Chomphosy  00:40

\n\n\n\n

Well, today, folks, in our podcast, I am joined by a couple of special guests. I know it’s been a bit since I’ve had a guest, so I’m very excited to introduce you to who I have with me today. Today, I have Maggie Cabrera and Jeff Ong. They both are working on themes, and especially the future of themes as we move into this low code, no code block based experience of editing things in WordPress. And there have been so many questions lately about what does the landscape of being a theme developer turns into once we move fully into this excellent promise of user empowerment for Gutenberg? I figured who best to come and talk to us about that than these two. So welcome, Maggie. Welcome, Jeff. I’m really excited to have this conversation with you today.

\n\n\n\n

Jeff Ong  01:39

\n\n\n\n

Thank you for having us. Excited to be here. 

\n\n\n\n

Josepha Haden Chomphosy  01:45

\n\n\n\n

I’m just gonna hop right in, and we will see what happens. The first thing that I want to chat about, I hear so many questions and so much discussion about patterns in a lot of different places. Like obviously, the work that I helped to steward the most is around like the Block Pattern directory and various other user-facing tools. And so I have never really been able to give a really solid answer about like patterns and how they work inside themes. And so I wondered if you all had anything that you could offer to our listeners to help clarify what is the power of patterns inside themes in the future? Implementation of themes?

\n\n\n\n

Jeff Ong  02:34

\n\n\n\n

I can try to start unless, Maggie? Okay. Well, if you take a look at what I’ve been doing for the last couple of months working on Twenty Twenty-Two. And if you look at that theme, it’s mostly just the collection of patterns. Patterns. As you know, if you read the description, the theme, it’s designed to be the most flexible and kind of like flexible theme ever, dare I say ever created. 

\n\n\n\n

Josepha Haden Chomphosy  03:04

\n\n\n\n

I think you can dare to say it. 

\n\n\n\n

Jeff Ong  03:03

\n\n\n\n

And, you know, I think a huge part of that is because of the Full Site Editing being launched, introduced in 5.9. And also that theme itself ships with all of these patterns in it that work with the overall design, but really can be configured to your own kind of unique liking and kind of taste and ultimately, what you want to accomplish, whether that’s I want to make a portfolio, I want to make, you know, a single-page website promoting like my podcast, or there are patterns for that kind of shipping with the theme. And they’ve all been kind of designed and tailored to work with the typography choices at a baseline level with the color choices at a baseline level, but can very easily be tweaked. And you can kind of rely on them to work with the editor. And I guess, kind of zooming out for a little bit, not just about Twenty-Twenty Two. 

\n\n\n\n

Jeff Ong  04:04

\n\n\n\n

But like patterns as this idea that a theme, hopefully, what it is, it’s a collection of different design options or layout options that are ultimately presented as patterns to the user, the patterns are just a really easy way to basically say “I want you this layout, like two columns of text or with like some images here.” Basically, a theme becomes a way of packaging the patterns together in a way that feels like a coherent piece of a coherent website. And I think that’s a pretty powerful idea. I know that the patterns directory is also opening up making those patterns pretty widely available. But I think a theme you could think of as like a curation of those patterns in a way that makes sense. And I think Twenty-Twenty Two is a really good example. I mean, I’m biased.

\n\n\n\n

Josepha Haden Chomphosy  05:03

\n\n\n\n

I also think it’s a good example. Maggie, did you have anything that you wanted to add to that?

\n\n\n\n

Maggie Cabrera  05:08

\n\n\n\n

Yeah, What I really like about patterns is how it empowers the user, even if they don’t really have like a deep knowledge of code, or they’re not used to the more complex blocks. When the theme developer gives you this pattern about using the query block, for example, it lays out your posts in a very compelling manner. And you can edit it if you want it or just use it out of the box. And you have this dynamic blog that it’s, like, such a big important part of your website. Like if you want to have a page where you have, you have maybe a podcast website, and you want to showcase your podcasts differently than your regular blog posts. So you can use a different gray pattern for that. And it’s like, really, really easy to use, even if you’re not familiar with it.

\n\n\n\n

Josepha Haden Chomphosy  06:07

\n\n\n\n

One of the things that I have found compelling about this new version of themes and kind of the way that themes are planning to look in the future; it’s going to be like a super throwback, so everyone get ready for me to sound old, my guests and my listeners alike. It reminds me of my original days of blogging on the web. I was not a developer and even though I had this really short stint of working with JavaScript in my career, at some point. Like no one actually would ever look to me and be like, that one is excellent at design and fixing everything with code, like I was just killer at searching for the right pieces of code, right. 

\n\n\n\n

Josepha Haden Chomphosy  06:57

\n\n\n\n

And so I remember sitting there on Zynga, which is, of course, now powered by WordPress, I absolutely just went out and found bundles of code that are now what we would consider themes and modified the small pieces that I needed to change in order to like really suit what I wanted to have happen on the site at the time. And they’re like, I knew I could break it all. Really easily. But also, it was, it was not scary to think about breaking it. Like it was clear how I could fix it if I really broke it. The content, like what I had written, was separate from everything to do with the way that it was looking. And so like, I wouldn’t destroy all of my work, just because I didn’t put a semicolon in the right place, or whatever it was in that moment. And so like, this future of themes really reminds me of this a lot where someone has curated how it can look how it should look. And you can just like add in modular pieces that will augment what was already intended, but still kind of work. And if it’s not gonna work, it’s kind of easy to fix too. So like, I’m excited. That was a really exciting time in my learning of the web and certainly was formative in my career, as we all now see. And so yeah, I think that’s really exciting. 

\n\n\n\n

Josepha Haden Chomphosy  08:20

\n\n\n\n

I did have actually another question that this conversation has kind of brought up for me. I have, obviously just use the term modular, which no one has ever used in the context of themes for WordPress. And I know that there is a lot there are a lot of terms kind of wandering around about themes right now. And especially as we’re moving into what themes can look like in the future. There was block based theme as a term for a while. And now it’s block themes. There was like this floating around the term, universal themes. And now we’re looking at just like block themes forever. And so I wondered if y’all could give us a just like a clear understanding of these terms that had been being used and maybe are going out of fashion? Like, are they important for us to keep knowing?

\n\n\n\n

Jeff Ong  09:11

\n\n\n\n

So yes, the history of terms around themes. And obviously, even my knowledge only goes back so far. But it was around when we started doing the block based themes meeting. And trying to I think that’s where that term kind of came from is like, oh, let’s, let’s start talking about this idea that themes can be completely made up out of blocks. And what does that mean? 

\n\n\n\n

Jeff Ong  09:33

\n\n\n\n

I think over time, it wasn’t just block themes, because, you know, previously, there were themes and even default themes that used and took into account the fact that blocks existed. So there was some confusion there. Enough time has gone on where we focus on this idea that themes whose templates are ultimately made out of blocks are block themes. And to me, it’s kind of as simple as that. Its themes that supply a set of templates that previously in the past were a collection of PHP and various template tags and whatnot is all transitioned to themes made up including other blocks, as well as themes that supply styles through theme.json configuration instead of supplying it in raw CSS. To me this idea is really crystallizing around like this is a block theme, one that is really, at its core, supplying a set of templates, and styles through a language that WordPress understands natively, and can allow it to be configured and customized in a really powerful way. And then maybe someday in the future, they’ll just be called themes again. If we do a good enough they will just be called themes.

\n\n\n\n

Josepha Haden Chomphosy  10:57

\n\n\n\n

I’m gonna, I’m gonna take us into a philosophical area now that you’ve just put us in there. You said, someday they’ll be called Themes. Again, I’ve talked about this on this podcast a few times. And for anyone who’s worked with me for any length of time, like you all probably heard this from me as well. But like, adjectives are so frequently the realm of things that are not what you expect, right? Because like you have coffee, and then decaf coffee, no one’s like caffeinated coffee, because that’s what you expect out of it. And so when you’re like themes, and block themes, it makes it look like block themes are secondary, which at the moment, they are, ish. But in the future, I think you’re probably right, there will be a time when the modifier isn’t necessary anymore because it will be hopefully a much better way for people to kind of change the way that their themes work and make it more usable for users and people who are, you know, having to manage their own site without necessarily wanting to or being able to, like, have a Maggie in the room to fix everything that they break. 

\n\n\n\n

Josepha Haden Chomphosy  12:08

\n\n\n\n

Maggie is nowhere near me. And so she’s never been in the room when I’ve broken anything. But I believe that Maggie on one occasion, at least, has come in and helped me fix something that I definitely broke. I’m an excellent breaker of WordPress things. Maggie, did you have anything you wanted to add to that question? 

\n\n\n\n

12:29

\n\n\n\n

Yeah, I guess, maybe clarify a bit, what universal themes are because, yeah, maybe some people have heard about the term but they don’t really know what they are. And maybe just clarify that. The term was born when developing block themes wasn’t something that you could actually do for production websites like you could build them to test some experiments, but they weren’t really ready for users to use. So universal themes want to grasp the power of love themes while still being ready for users. So the way they do it is they are block based, like we used to call them in the sense that the templates are made of blocks. But they are also able to be customized using the customizer, which is the old way of customizing themes, instead of using the site editor. So they can have a balance between two worlds between the worlds of classic themes and block themes. But they are, at heart, a temporary concept. They are bound to be blocked themes in the future, but with maybe a foot in the past, where they can actually serve users who are not ready for full-on site editor. But they are bound to be full block themes in the future.

\n\n\n\n

Josepha Haden Chomphosy  14:00

\n\n\n\n

There’s a really interesting concept in there. So universal themes, it sounds like are basically kind of like an on-ramp for people who are not really ready to fully commit to this for any number of reasons. Like we never want to say that we know the reason that people would be a little bit shy to get started with this. But like it’s kind of like an on-ramp, it’s a safe way to get back to something that they do know, in the event that what they don’t know, really hinders their progress makes it hard for them to get the work done.

\n\n\n\n

Maggie Cabrera  14:31

\n\n\n\n

I think I wouldn’t say that they are for people shyer to get into new stuff rather than developers who want to embrace the new stuff before it’s even really ready. They really want to embrace the power of the blocks instead of doing things the old way. But even if it’s not fully ready.

\n\n\n\n

Jeff Ong  14:54

\n\n\n\n

They still need to support the old way of doing things.

\n\n\n\n

Maggie Cabrera  14:58

\n\n\n\n

Like being backward compatible and being ready for any kind of user.

\n\n\n\n

Josepha Haden Chomphosy  15:05

\n\n\n\n

So mostly for developers, everyone who heard me just talking about how it was a great thing for users, ignore it.

\n\n\n\n

Maggie Cabrera  15:12

\n\n\n\n

It’s also good for users; If they feel secure in using the customizer.

\n\n\n\n

Josepha Haden Chomphosy  15:20

\n\n\n\n

Well, I think that there’s something important here that we certainly learned with the adoption of Gutenberg in 5.0. Right, which is that there is certainly one method of helping people to adopt things, which is to go like the art of war style, and kind of smash their rice pots and burn all their boats, like, that’s one way. Which works for a lot of companies in the world, I’m sure. But WordPress has always had kind of a commitment, not even kind of, has always had a commitment to backward compatibility. And like, we know that a lot of the work on Gutenberg is going to represent some breaking changes around the around workflows and around the user experience the interface, especially like, we know that. But the opportunity to like have a thing that gives you an early taste of what’s coming but also the ability to keep kind of working in your old space where you need to, I think it’s an excellent way to bring people forward into the future of things, I have never been a fan of the just like cut off all avenues and hope that they stay with your method because of course, like you can’t cut off all the methods. You can’t cut off all the ways people can get away from you. And even if we could, it wouldn’t be in line with how WordPress hopes to kind of help people through some tough stuff like making your first website is hard. If you are doing it as part of, an overall campaign that’s supposed to bring in leads for you or generate revenue like you don’t want to necessarily play with that in a way that could break things and be risky for you in the long term. So I think all the tools that we offer to help people kind of move forward with the technology move forward with the CMS as it’s moving forward, I think it’s really smart. And so universal themes are one of those things, but also not around to stay. As we move into non modified themes, just the word themes that happen to be based in blocks. If I’ve confused anyone, please email me at wpbriefing@wordpress.org. And tell me how I confused you. And I will do a follow-up to unconfuse everyone. 

\n\n\n\n

Josepha Haden Chomphosy  17:40

\n\n\n\n

So speaking of the way that we help people kind of move forward with WordPress and with the technology. So much has been done in the CMS in the past 12 months in the past 18 months to be able to move themes into this same future as the rest of the editor. Right. So like, for folks who have not been listening to me for the last five years, you may not know this. So I’m going to tell everybody now, like one of the pain points that Gutenberg overall is solving is the fact that you for a long time had to learn five different editing interfaces to get one thing done in WordPress, right. And so like the advent of blocks and moving it into more and more spaces in the CMS is intended to really flatten the editing experience by making the type of user interaction the type of workflow really similar across all of the editing interfaces in the CMS. And so themes are a natural extension of that, where we can take similar user patterns and workflows, and work them out into themes. So over the last 12 months or so probably a little bit more, there’s been a lot of work on the CMS to move us forward in that that is now enabling the work that we want to be able to do to move things forward ahead. And so, I mean, this is probably our last question. Is there anything that you all want to offer to people who maybe saw themes early on or saw Gutenberg early on and felt like this is just not for me, in that in that context of like, how far it’s moved ahead in the past 12 months or so.

\n\n\n\n

Jeff Ong  19:23

\n\n\n\n

So you’re asking like, what in the last 12 months has maybe like really surprised me or like sticks out to me as something that like, Wow, look how far we’ve come?

\n\n\n\n

Josepha Haden Chomphosy  19:36

\n\n\n\n

Yeah, yeah. So like, if you’re looking at what is the one thing that you saw in the last 12 months, that changed in the CMS that really enabled something wonderful for themes or from the other side of it. Like if someone had looked at themes or WordPress 18 months ago, and now they’re looking at it and seeing this new and different way to do things with the look and feel of their site, like what is one thing that they should be aware of? On either side of that question,

\n\n\n\n

Maggie Cabrera  20:05

\n\n\n\n

I think there’s more than one thing that has really evolved through this last year, year and a half. Like the maturity of some of the blocks is astounding now, like navigation blog, for example, was really bare-bones at the start and now it’s full potential, and it’s really looking really great. I would say the same thing about those days or the features on fire, like how basic it was at the start, was full potential. But now it’s really, really mature in terms of how much you can do with it. Like, I think the example, the perfect example of that is the work that Kjell [Reigstad] has done on Twenty-Twenty Two with the alternative theme.json files, where just changing that file basically feels like a new theme, with just the configuration and the styles. And without writing any CSS without changing any templates. It’s really, really amazing how that can turn into a reality. And it’s so easy for users to tinker with that if they want to. And it’s much easier than having to delve deep into CSS and changing everything in like 2000 lines of code. 

\n\n\n\n

Jeff Ong  21:23

\n\n\n\n

Yeah, I probably would echo most of that. What the thing that astounds me is global styles and how the UI can be shipping a theme or default theme with basically like, 20 lines of CSS, and have it be one of them. A beautiful, beautiful, like crisp and sharp, like, experience. It’s super fast. And it’s like, what this is a theme, you know, I thought a theme was supposed to supply all the styles like no, like, it’s just yeah. And workers do for you. Exactly. And like that. That’s pretty amazing to think in the last 12 months, we can go from, you know, shipping 1000s of lines of CSS to you none, it’s like, Wow, pretty cool. 

\n\n\n\n

Josepha Haden Chomphosy  22:10

\n\n\n\n

Well, my friends, thank you so much for joining me today. This has been a really interesting conversation. I hope that all y’all out listening. Also find it interesting. As I mentioned, if you have any follow-up questions, absolutely. Send them to me via email. And I collect all of my questions that I get through the year for answering at the end of the year, mostly because I don’t get lots of questions that people want to be answered on this. Everyone just asked me their questions on Twitter and in Slack, which is fine as well. 

\n\n\n\n

Josepha Haden Chomphosy  22:41

\n\n\n\n

So, Maggie, Jeff, thank you both for joining me. And I’m sure that we’ll talk to you all again soon. 

\n\n\n\n

Josepha Haden Chomphosy  22:56

\n\n\n\n

That brings us now to our small list of big things. In the last episode, I got all excited about being in the beta phase. But today, I’m rolling that back a little bit. As part of our usual open source processes, a group of contributors did a deep dive review on the WordPress 5.9 release and found a workflow that needed some refinement. So we are delaying the beta. 

\n\n\n\n

Josepha Haden Chomphosy  23:19

\n\n\n\n

Since we are in the midst of a major commerce slash/sales season, and of course, a lengthy holiday season, that delay also means that it makes sense to delay WordPress 5.9 final release a little as well. And so we are delaying that all the way into 2022 to January 25. For me, the trade-off works really well there. Every decision that we make in open source, of course, has some balance to it. It’s great for these aspects, it is less great for these aspects over here. But for myself, the opportunity to make sure that we have a really excellent experience for our users and also an opportunity to kind of avoid all of the chaos and hustle and bustle of the end of the year. Really, it seemed like a no-brainer for me. So in case you want to learn a little bit more about why we made the decision and get some insight into the actual milestones and where they have moved now, I’ll include some posts in the show notes below in case you want to read more and of course, if you have any additional questions you can always ask.

\n\n\n\n

Josepha Haden Chomphosy  24:33

\n\n\n\n

The second small list of big things is that the first back to people WordCamp. I don’t think that’s what we’re calling it. Our first back to people WordCamp is happening in a couple of weeks actually. WordCamp Sevilla is happening in person on December 11. And I’m so excited I wish I were local, but I’m not so if you are local stop by their website and pick up your ticket. 

\n\n\n\n

Josepha Haden Chomphosy  24:55

\n\n\n\n

And the third thing on our smallest a big things is that it is, of course, charitable giving season. I don’t know if you do your charitable giving at the end of the year or if that’s even part of your general ways of giving back. But I can think of two or three charitable organizations inside the WordPress ecosystem. There’s of course the WordPress Foundation, but also Big Orange Heart and HeroPress. If there are others out there, I certainly do want to know about them. WordPress Foundation also does additional giving on behalf of just like the open web and open source as a whole. So if you’re the sort of person who does their charitable giving at the end of the year, just a reminder that you have some options inside the WordPress ecosystem if you were trying to figure out some new places to donate to in 2021. 

\n\n\n\n

Josepha Haden Chomphosy  25:42

\n\n\n\n

And that is your small list of big things. Thank you so much for tuning in today for the WordPress Briefing. Thank you again to our special guests, Maggie and Jeff. I’m your host Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11636\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"Watch State of the Word at a Watch Party with your WordPress Friends\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:104:\"https://wordpress.org/news/2021/11/watch-state-of-the-word-at-a-watch-party-with-your-wordpress-friends/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 24 Nov 2021 18:30:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11641\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:322:\"State of the Word 2021 is just around the corner!  Although attending State of the Word in person would be ideal, not all WordPress community members get to enjoy the experience of attending the speech live with friends.  This year, as State of the Word is streamed live for the second time, we want to […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Hari Shanker R\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:20064:\"\n

State of the Word 2021 is just around the corner! 

\n\n\n\n

Although attending State of the Word in person would be ideal, not all WordPress community members get to enjoy the experience of attending the speech live with friends. 

\n\n\n\n

This year, as State of the Word is streamed live for the second time, we want to restore that in person camaraderie through State of the Word watch parties for WordPress Community members around the world.

\n\n\n\n

We encourage WordPress meetup organizers and community members worldwide to (safely) host State of the Word 2021 watch parties —read this handbook to learn more.

\n\n\n\n

Why organize a watch party? 

\n\n\n\n
  • If you are a WordPress meetup organizer, many folks in your meetup may be unaware of the State of the Word, and a watch party could be a great opportunity to introduce or remind them.
  • As meetup organizers slowly bid goodbye to a tough year, the watch party could be an excellent opportunity to revitalize your group, especially if you haven’t had many events this year.
  • Along with your Meetup group members, you get a platform to ask questions directly to Matt Mullenweg.
  • And last but not least, even if you are not a Meetup Organizer, a watch party can be the perfect opportunity to reconnect and have a blast with your WordPress friends!
\n\n\n\n

How do I organize a State of the Word watch party?

\n\n\n\n

You can choose to host a watch party online or in person. Check out our handbook for detailed instructions on how to schedule an event (including event templates).

\n\n\n\n
\n
\n

Online

\n\n\n\n

The simplest way to organize an online watch party is to schedule an online event for your WordPress group and add the State of the Word YouTube streaming link directly on Meetup.com. Alternatively, you can schedule an online meeting using tools like Zoom and broadcast the live stream over there by screen sharing––thereby facilitating better engagement.

\n\n\n\n
\n
Organize an Online Watch Party
\n
\n
\n\n\n\n
\n

In Person

\n\n\n\n

If your region meets the guidelines for in person events (if vaccines and testing are freely available), you can organize an in person watch party event (for fully vaccinated OR recently tested OR recently recovered folks) for your WordPress Meetup! Group members can hang out together (following local safety guidelines of course) and watch State of the Word live.

\n\n\n\n
\n
Plan an In person Watch Party
\n
\n
\n
\n\n\n\n
\n\n\n\n

NOTE: If State of the Word is happening at an odd hour in your timezone, you can still organize a watch party by organizing a replay of live stream, at a date/time that is convenient for your group.

\n\n\n\n

If your Local WordPress Meetup is organizing an in person watch party, fill out this form so that we can ship some swag for your group to celebrate!
Deadline: November 30, 2021

\n\n\n\n

What else do I need to know about organizing a State of the Word watch party?

\n\n\n\n

Excited? To help you get started, we’ve put together a few resources:

\n\n\n\n
  • Check out this handbook for detailed instructions on how to organize a watch party, be it online or in person.
  • Looking for a Zoom Pro account to host your online watch party? Request a community zoom pro account for your event right away!
  • We have prepared some email templates that Meetup Organizers can use to spread the word in their Meetup groups.
  • Don’t forget to share on social media about your watch party events using the hashtag #StateOfTheWord so we can join in on the fun!
\n\n\n\n

NOTE: The guidelines in this post are primarily aimed at WordPress Meetup organizers. However, you do not need to be a Meetup organizer to schedule a watch party! You can simply hang out together with your friends online or in person (while following local safety guidelines) and catch the event live!

\n\n\n\n

Join a State of the Word Watch Party near you!

\n\n\n\n

We have compiled a list of State of the Word Watch Parties around the world. If you don’t see a watch party in your region listed here, check this page on Meetup.com to see if your local WordPress group is organizing one. If not, why don’t you consider organizing a watch party on your own? \"🙂\"

\n\n\n\n\n\n\n\n
\n\n\n\n

If you are planning a watch party for State of the Word, and have questions, please drop us an email to: support@wordcamp.org if you have any questions. We are happy to help you in the best way possible.

\n\n\n\n

The following folks contributed to this post: @anjanavasan @eidolonnight @evarlese and @rmartinezduque

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11641\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:23:\"A Look at WordPress 5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wordpress.org/news/2021/11/a-look-at-wordpress-5-9/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 23 Nov 2021 21:02:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:6:\"Design\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11625\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:322:\"WordPress 5.9 is expected to be a ground-breaking release. It will introduce the next generation of themes with Twenty Twenty-Two joining the fun and over 30 theme blocks to build all parts of your site. In anticipation of the January 25th release, we hope you enjoy this sneak peek of 5.9. New design tools will […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Kelly Hoffman\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2987:\"\n
\n\n
\n\n\n\n

WordPress 5.9 is expected to be a ground-breaking release. It will introduce the next generation of themes with Twenty Twenty-Two joining the fun and over 30 theme blocks to build all parts of your site. In anticipation of the January 25th release, we hope you enjoy this sneak peek of 5.9.

\n\n\n\n

New design tools will allow you to create exactly what you want, from adding filters to all your images to fine-tuning the border radius on all your buttons. With WordPress 5.9 providing more design control along with streamlined access to patterns, you can easily change the entire look and feel of your site without switching themes.

\n\n\n\n

No matter what you’re editing, whether it’s crafting a new post or working on a header, improvements to List View make it simple to navigate content regardless of complexity. More improvements and features for everyone are to come in this release and we can’t wait to see what you create with WordPress 5.9! 

\n\n\n\n

Stay Tuned

\n\n\n\n

Stay tuned for more updates as the date draws near. If you want to help, the best thing you can do is test everything! For all the details, check out this Make Core post.

\n\n\n\n

Video props: @annezazu (also co-wrote the post) @michaelpick @matveb @beafialho @javiarce @critterverse @joen.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11625\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"Join us for State of the Word 2021, in person or online!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://wordpress.org/news/2021/11/join-us-for-state-of-the-word-2021-in-person-or-online/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 22 Nov 2021 21:08:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11611\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:297:\"As previously announced, State of the Word will be livestreamed from New York City. That means that you can join the fun either online or in person, on December 14, 2021, between 5 and 7 pm EST! To join State of the Word 2021 online, check your Meetup chapter for a local watch party, or […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:1726:\"\n

As previously announced, State of the Word will be livestreamed from New York City. That means that you can join the fun either online or in person, on December 14, 2021, between 5 and 7 pm EST!

\n\n\n\n

To join State of the Word 2021 online, check your Meetup chapter for a local watch party, or simply visit wordpress.org/news, where the livestream will be embedded. 

\n\n\n\n

If you would like to participate in person in New York City, please request a seat by filling out the registration form by Sunday, November 28. Not all requests will receive a seat due to venue capacity, but everyone who requests one will receive further notification on Tuesday, November 30. 

\n\n\n\n

In person attendees will be asked to show their COVID vaccination card at the venue entrance, and are expected to follow the safety measures in place. Because of these safety measures, there is a maximum of 50 attendees. 

\n\n\n\n
\n
Request a seat
\n
\n\n\n\n

Whether you participate in person or online, we are so excited to see you on December 14! Don’t forget, State of the Word will be followed by a Question & Answer session. If you have a question for Matt, you can send your question ahead of time to ask-matt@wordcamp.org, or ask during the event in the YouTube chat.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11611\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:55:\"\n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"WP Briefing: Episode 20: WordPress=Blogging+\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://wordpress.org/news/2021/11/episode-20-wordpressblogging/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 15 Nov 2021 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11556\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:386:\"In this episode, WordPress’s Executive Director, Josepha Haden Chomphosy, answers two recently asked questions. Tune in to hear what those questions were and her response, in addition to this week’s small list of big things. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/11/WP-Briefing-020.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:10275:\"\n

In this episode, WordPress’s Executive Director, Josepha Haden Chomphosy, answers two recently asked questions. Tune in to hear what those questions were and her response, in addition to this week’s small list of big things.

\n\n\n\n

Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.

\n\n\n\n

Credits

\n\n\n\n\n\n\n\n

References

\n\n\n\n\n\n\n\n

Transcript

\n\n\n\n\n\n\n\n

Josepha Haden Chomphosy  00:10

\n\n\n\n

Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!

\n\n\n\n

Josepha Haden Chomphosy  00:40

\n\n\n\n

So I was in a meeting recently, which I realize isn’t saying much for me since I spend a quarter of my time in meetings. But in this particular meeting, I was asked a couple of questions that I absolutely loved. The first question was, “if there were one thing you could change in people’s minds about WordPress, what would it be?” And my answer, predictable though it may be, was that I want to change the idea that WordPress is just a blogging platform. 

\n\n\n\n

Josepha Haden Chomphosy  01:06

\n\n\n\n

WordPress has grown into a lot more than that. But the idea of a content management system, even now, sometimes gets a mental shorthand where content is a stand-in for the word writing or words. If you’re using WordPress today in an enterprise context, or as part of a governmental agency, or if you use it in a classroom setting, you know that your content cannot be confined that way. And if you’re supporting or building anything to hand off to clients, you know that timely, easy-to-ship changes on a site are considered a vital part of any overarching brand and marketing strategy. And when was the last time that any marketing strategy was literally only about the words? 

\n\n\n\n

Josepha Haden Chomphosy  01:51

\n\n\n\n

So that was the first question. And also my first answer. There is also this kind of annual, not fear, necessarily, but this annual question that is sort of related that is raised to me and has been asked of me recently, that I’m just going to give you a small answer to. One annual worry that I get every year around November and December is, “What are we going to do about the fact that the term blog and blogging are declining in search popularity?” And I was gonna say it’s been a while since I answered that in any sort of public format. But I think maybe I’ve never answered it in a public format at all. And so I’m just going to answer it here. Because I think maybe a lot of people have that same question. 

\n\n\n\n

Josepha Haden Chomphosy  02:36

\n\n\n\n

So number one, I think that the way that people search now is different. There’s a lot more semantic cognition. This is not the way to answer this — search engines are smarter now. So like, it used to be the case with early search engines that yeah, there was a lot of just like, individual search terms that were looked for. But now, people are asking full questions; they have, essentially, an entire sentence that they are searching for. And then, search engines are able to parse that information better and get more high-quality answers and information for them. So like, that’s one thing that I’m already not worried about. If people are searching for individual words anymore, it’s so that they can get a definition of that word. So I’m not specifically worried about a decline in search volume for the word blog or blogging for that reason. But the answer to my first question, if there is probably the real reason that I’m not actually super worried about any decline in search volume for the word blog, or blogging, is that WordPress has really moved beyond that. And since we have moved beyond that, then it doesn’t necessarily make sense for WordPress as an entity for WordPress as a project to get overly hung up on the idea that the term blog has gone out of fashion. 

\n\n\n\n

Josepha Haden Chomphosy  03:52

\n\n\n\n

Okay, now that I did my first question, and the answer, and then an additional question that only ever gets asked in private and is being answered by me for the first time in public, I will tell you now, the second question that I loved, someone asking of me, and that question is this: “What is one thing you’d like people to see or experience, right when they first land on wordpress.org?” Now, I often don’t get asked questions about the wordpress.org website, like administrative tasks, things that we need to update, move around where they should go. Sure. But like, “Josepha, what’s the point and purpose of this site?” Never. I’ve never been asked that, and so I was really excited that someone asked me, and I’m going to give you a heads up. I think some of you might disagree with my answer. 

\n\n\n\n

Josepha Haden Chomphosy  04:40

\n\n\n\n

So the primary thing that I want people to see or experience when they first get to wordpress.org, the website is the depth of WordPress. Not which audience segment they should belong to or that we believe they should belong to or raw data about the CMS or even how much we care about the freedoms of open source. Now the first thing I want people to see on that site is that WordPress has not only 18 years of learned knowledge that every single new user benefits from, but that it also has 1,000s of really smart people making sure it works and gets better every day, now. 

\n\n\n\n

Josepha Haden Chomphosy  05:19

\n\n\n\n

WordPress is a Goliath in its field. I know that we cite this bit of context. Frequently, we say that we are 42% of the web. And that is true that is the percentage by usage. But in its field, which is websites that are using a content management system, we actually have a 65% market share. This is very easy to find. It’s on the W3Techs website: I can put a link in the show notes, but you could find it just by searching for it. 

\n\n\n\n

Josepha Haden Chomphosy  05:46

\n\n\n\n

So WordPress is a Goliath in its field of websites that are run using a CMS. Because we have always brought our learnings forward with us with the understanding that knowledge, when shared grows rather than diminishes. But open source, the heart of what defines this project, open source is not a Goliath; it’s barely even David somedays. Even though the web is built on scads of open source software, there’s a pervasive public perception that it is built by and for hobbyists or that it is inherently risky, and that if there were if it were worth something, then people would pay something. And I just know that if the first impression of WordPress, we’re, “we’ve got 18 years of experience and learning that brought us to today,” the rest of the sale to adopt software that protects other people’s freedoms would take care of itself. And I guess, to quote John Oliver, at this point, “And now this.”

\n\n\n\n

Josepha Haden Chomphosy  06:59

\n\n\n\n

Alright, that brings us now to our small list of big things. There are actually quite a few big things on this small list today. So number one, we have reached the beta phase for the year’s final release, which means that WordPress 5.9 beta one is happening tomorrow, Tuesday, November 16. And then seven days later, I believe on the 23rd, if I recall correctly, comes beta two. 

\n\n\n\n

Josepha Haden Chomphosy  07:24

\n\n\n\n

The second thing on my list is that team rep nominations are happening all over the project right now. I’ve got a post that I will share in the notes below that I believe all the team reps have put their team’s nomination posts on. So if you have had an interest in learning more about that and what it means to help keep teams kind of running in the WordPress project, then this is a great opportunity to check those out. 

\n\n\n\n

Josepha Haden Chomphosy  07:49

\n\n\n\n

And the third thing, this last thing actually isn’t in the next two weeks, but it is very important, nonetheless. Matt’s annual State of the Word is coming up on December 14. So basically a month from today. It’s going to join the growing list of in-person events that are on the calendar. It will be in New York City but will also be live-streamed across the world as usual. Keep an eye out for additional updates about that for anyone who, like me, really looks forward to this particular presentation from our project co-founder every year. 

\n\n\n\n

Josepha Haden Chomphosy  08:25

\n\n\n\n

And that is your small list of big things. Thank you for tuning in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11556\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"State of the Word 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpress.org/news/2021/11/state-of-the-word-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 13 Nov 2021 00:38:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11567\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:346:\"Howdy, World!  Mark your calendars; it’s almost time for State of the Word 2021! State of the Word is the annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg. Every year, the event allows us to reflect on the project’s progress and the future of open source. This year will include that and […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:17591:\"\n
\n\n
\n\n\n\n

Howdy, World! 

\n\n\n\n

Mark your calendars; it’s almost time for State of the Word 2021!

\n\n\n\n

State of the Word is the annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg. Every year, the event allows us to reflect on the project’s progress and the future of open source. This year will include that and more.

\n\n\n\n

Due to the pandemic, we moved the State of the Word online for the first time ever in 2020. This year, the event will be livestreamed from New York City. That will enable us to take as many folks as possible along for the ride!

\n\n\n\n

Join Matt as he provides a retrospective of 2021, discusses the latest trends he’s seeing, celebrates the community’s amazing wins, and explores the future. Expect to hear about a range of topics, from WordPress 5.9 and Openverse to Web3 and non-fungible tokens (NFTs).

\n\n\n\n

What: State of the Word 2021

\n\n\n\n

When: December 14, 2021, between 5 and 7 pm ET/10 – 12 am (December 15) UTC

\n\n\n\n

How: If you’re watching from the comfort of your home or local watch party, the livestream will be embedded on wordpress.org/news.

\n\n\n\n

Have a question for Matt?

\n\n\n\n

State of the Word will be followed by a Question & Answer session. If you want to participate, you can either send your question ahead of time to ask-matt@wordcamp.org, or ask during the event in the livestream chat on YouTube.

\n\n\n\n

If you’re new to State of the Word, the previous years’ recordings (below) will help you get a sense of what the event is about. Check them out:

\n\n\n\n\n\n\n\n

We hope to see you online on December 14th!

\n\n\n\n
\n\n\n\n

Join a State of the Word Watch Party near you

\n\n\n\n

We have compiled a list of State of the Word Watch Parties around the world. If you don’t see a watch party in your region listed here, check this page on Meetup.com to see if your local WordPress group is organizing one.

\n\n\n\n\n\n\n\n
\n\n\n\n

If you are planning a watch party for State of the Word, and have questions, please drop us an email to: support@wordcamp.org if you have any questions. We are happy to help you in the best way possible.

\n\n\n\n

Thanks to @anjanavasan @eidolonnight @rmartinezduque for their work on this post. The featured image was created by @beafialho.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11567\";s: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:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"Take the 2021 WordPress Annual Survey (and view the 2020 results)!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://wordpress.org/news/2021/11/take-the-2021-wordpress-annual-survey-and-view-the-2020-results/\";s: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, 11 Nov 2021 23:52:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11551\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:359:\"Each year, members of the WordPress community (users, site builders, extenders, and contributors) provide their valuable feedback through an annual survey. Key takeaways and trends that emerge from this survey often find their way into the annual State of the Word address, are shared in the public project blogs, and can influence the direction and […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4885:\"\n

Each year, members of the WordPress community (users, site builders, extenders, and contributors) provide their valuable feedback through an annual survey. Key takeaways and trends that emerge from this survey often find their way into the annual State of the Word address, are shared in the public project blogs, and can influence the direction and strategy for the WordPress Project.

\n\n\n\n

Simply put: this survey helps those who build WordPress understand more about how the software is used, and by whom. The survey also helps leaders in the WordPress open source project learn more about our contributors’ experiences.  

\n\n\n\n

To ensure that your WordPress experience is represented in the 2021 survey results, take the 2021 annual survey now.

\n\n\n\n
\n
Take the Annual Survey! (English)
\n
\n\n\n\n
\n\n\n\n

You may also take the survey in French, German, Japanese, Russian, or Spanish. These are the top five languages (other than English) based on the number of WordPress locale downloads. For 2022, additional languages may be considered for translation.

\n\n\n\n

The survey will be open through the end of 2021, and the results will be published in a future post on this blog for anyone to view. Next year, there will be a new format for this survey, including which segments and questions are included, so that your valuable time spent responding results in equally valuable information.

\n\n\n\n

2020 Survey Results

\n\n\n\n

For the 2020 survey, more than 17,000 responses were collected, representing the highest submission volume in four years, up three times from the prior year. In the inaugural year of the survey (2015), over 50,000 responses were collected. Given the reach and adoption of WordPress, there is a significant number we have not reached. As you take the 2021 survey, consider sharing the link on social media and with other colleagues who use WordPress. Gathering feedback from more folks who benefit from WordPress will strengthen our project.

\n\n\n\n
\n
View the 2020 Survey Results (PDF)
\n
\n\n\n\n
\n\n\n\n

The 2020 survey results show that the pandemic has had a major impact on how we operate as a community. With few in-person events, many community members continue to find it challenging to balance community contributions with their own personal and professional obligations. 

\n\n\n\n

Footnotes:

\n\n\n\n

Data security and privacy are paramount to the WordPress project and community. With this in mind, all data will be anonymized: no email addresses nor IP addresses will be associated with published results. To learn more about WordPress.org’s privacy practices, view the privacy policy.

\n\n\n\n

Like last year, the 2021 survey will be promoted via a banner on WordPress.org, and throughout the make blogs. However, taking a moment to amplify these posts through your own social media and Slack accounts will ensure broader participation. Each of the translated surveys will be promoted through banners on their associated localized-language WordPress.org sites.

\n\n\n\n

Thanks to @dansoschin for the initial draft of this post, and to @annezazu & @zackkrida for review!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11551\";s: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:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 5.8.2 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wordpress.org/news/2021/11/wordpress-5-8-2-security-and-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 10 Nov 2021 18:20:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Security\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11546\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:365:\"WordPress 5.8.2 is now available! This security and maintenance release features 2 bug fixes in addition to 1 security fix. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 5.2 have also been updated. WordPress 5.8.2 is a small focus security and maintenance release. The next […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Jonathan Desrosiers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3030:\"\n

WordPress 5.8.2 is now available!

\n\n\n\n

This security and maintenance release features 2 bug fixes in addition to 1 security fix. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 5.2 have also been updated.

\n\n\n\n

WordPress 5.8.2 is a small focus security and maintenance release. The next major release will be version 5.9.

\n\n\n\n

You can download WordPress 5.8.2 by downloading from WordPress.org, or visit your Dashboard → Updates and click Update Now. If you have sites that support automatic background updates, they’ve already started the update process.

\n\n\n\n

For more information, browse the full list of changes on Trac, or check out the version 5.8.2 HelpHub documentation page.

\n\n\n\n

Thanks and props!

\n\n\n\n

The 5.8.2 release was led by Jonathan Desrosiers and Evan Mullins.

\n\n\n\n

In addition to the release squad members mentioned above, thank you to everyone who helped make WordPress 5.8.2 happen:

\n\n\n\nAri Stathopoulos, Bradley Taylor, davidwebca, Evan Mullins, Greg Ziółkowski, Jonathan Desrosiers, Juliette Reinders Folmer, Mukesh Panchal, Sergey Biryukov, shimon246, and Yui.\n\n\n\n

Props @circlecube and @pbiron for peer review.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11546\";s: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:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"The Month in WordPress: October 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2021/11/the-month-in-wordpress-october-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 04 Nov 2021 23:35:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11501\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:344:\"October 2021 brought a lot of new things to WordPress, from release updates to new versions of Gutenberg. More notably, in the latest episode of WP Briefing, Executive Director Josepha Haden reminded us about the importance of freedom in open source platforms like WordPress. Free speech has with it a lot of responsibility, just like […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Anjana Vasan\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:24011:\"\n

October 2021 brought a lot of new things to WordPress, from release updates to new versions of Gutenberg. More notably, in the latest episode of WP Briefing, Executive Director Josepha Haden reminded us about the importance of freedom in open source platforms like WordPress.

\n\n\n\n

Free speech has with it a lot of responsibility, just like being a part of a community. Governments or communities, or in our case, this software is built by the people who show up.

For WordPress, at 42% of the web, every small choice we make can cause huge changes in the way that people experience the web today and tomorrow.

Josepha Haden, Executive Director of the WordPress project
\n\n\n\n

Last month was yet another chapter in this journey. So keep reading to learn what’s new. 

\n\n\n\n
\n\n\n\n

WordPress 5.9: All proposed updates will likely be included

\n\n\n\n
  • We announced the go/no-go for WordPress 5.9 features in mid-October. The release will probably include all the proposed features—though not all of them are ready yet, they should be by the proposed release date (December 14, 2021).
  • WordPress 5.9 will include a new default theme called Twenty Twenty-Two! The theme’s foundation will be strong, and the unpredictable yet reliable behavior of birds inspired the intentionally subtle design. 
\n\n\n\n
\"WordPress
\n\n\n\n\n\n\n\n

Interested in contributing to WordPress core? Join the #core channel, follow the Core Team blog, and check out the team handbook. Also, don’t miss the Core Team’s weekly developer chat on Wednesdays at 8 PM UTC.

\n\n\n\n
\n\n\n\n

Gutenberg releases: 11.6, 11.7, and 11.8 are here

\n\n\n\n

We released three new versions of the Gutenberg block editor between the end of September and October:

\n\n\n\n
  • Version 11.6 brings site logo cropping and rotation, block-level locking, improvements to Query Pagination block, support for child themes and thunks, template focus mode, and enhancements to the writing flow.
  • Gutenberg version 11.7 includes bug fixes and polishes to the navigation block and editor, global styles and full site editing (including a handy back button that lets you quickly return to the site editor), and columns block support, among other improvements.
  • Finally, Gutenberg 11.8 is the second to last version to make it into the WordPress 5.9 release, and it comes with plenty of developments to the editing experience: featured Block Patterns, new animations for a few elements (like Dropzone and Insertion Point), spacing tools for heading blocks, and a lot more.
\n\n\n\n

Want to get involved in developing Gutenberg? Follow the Core Team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Make WordPress Slack. For details on the latest updates, follow the “What’s next in Gutenberg” post.

\n\n\n\n
\n\n\n\n

WordCamp US returned virtually this year with more than 3,600 attendees

\n\n\n\n

WordCamp US 2021 was on October 1, and it was online for the first time. The event drew more than 3,600 attendees, 27 sponsors, and 18 remarkable speakers on topics ranging from accessibility and sustainability to e-commerce, to name a few. 

\n\n\n\n

Matt Mullenweg’s “State of the Word” is expected to be held as a separate event later this year, rather than being part of WordCamp US.

\n\n\n\n

If you missed the live event, you can still watch the Yukon Track and the Columbia Track of WordCamp US 2021.

\n\n\n\n
\n\n\n\n

Team Updates: Polyglots monthly newsletter, a new Performance team, and more

\n\n\n\n\n\n\n\n

Sign up for the Polyglots monthly newsletter, if you haven’t already.

\n\n\n\n
\n\n\n\n

Feedback/Testing requests: Deadline for redesigned Gutenberg landing page is November 5, 2021

\n\n\n\n
\"WordPress.Org
\n\n\n\n\n\n\n\n

Share your feedback on the new Gutenberg landing page design in Trac or by commenting on the blog post by November 5, 2021.

\n\n\n\n

Keep an eye out for WordCamp Spain, Sâo Paulo, and Taiwan 2021

\n\n\n\n

We had several WordPress events in October, and several more to look forward to the rest of the year:

\n\n\n\n\n\n\n\n

Don’t miss the following upcoming online WordCamps: WordCamp Spain 2021, WordCamp Sâo Paulo 2021, and WordCamp Taiwan 2021!

\n\n\n\n
\n\n\n\n

Have a story that we could include in the next ‘Month in WordPress’ post? Let us know by filling out this form.

\n\n\n\n

The following folks contributed to October 2021’s Month in WordPress: @anjanavasan, @harishanker, @rmartinezduque, @callye, @webcommsat, and chaion07.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11501\";s: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:55:\"\n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WP Briefing: Episode 19: The People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://wordpress.org/news/2021/11/episode-19-the-people-of-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 01 Nov 2021 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11368\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:463:\"In this nineteenth episode, WordPress’s Executive director, Josepha Haden Chomphosy, discusses and expresses gratitude for the inspiration behind the People of WordPress series, HeroPress. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho Production: Chloé Bringmann Song: Fearless First by Kevin […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/10/WP-Briefing-019.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:8207:\"\n

In this nineteenth episode, WordPress’s Executive director, Josepha Haden Chomphosy, discusses and expresses gratitude for the inspiration behind the People of WordPress series, HeroPress.

\n\n\n\n

Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.

\n\n\n\n

Credits

\n\n\n\n\n\n\n\n

References

\n\n\n\n

People of WordPress series

\n\n\n\n

HeroPress

\n\n\n\n

HeroPress Network

\n\n\n\n

WordPress 5.9 Development Cycle

\n\n\n\n

Call for Team Rep Nomination

\n\n\n\n

Transcript

\n\n\n\n\n\n\n\n

Josepha Haden Chomphosy  00:11

\n\n\n\n

Hello, everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!

\n\n\n\n

Josepha Haden Chomphosy  00:29

\n\n\n\n

The month of November includes the Thanksgiving holiday in my part of the world and in my familial traditions. And one of the things that November always brings up for me is the concept of gratitude. I have a gratitude practice that lasts throughout the year. But this time of year always kind of lets me look outside what makes me feel routinely grateful and explore areas that I don’t always notice. 

\n\n\n\n

Josepha Haden Chomphosy  01:05

\n\n\n\n

This year, I’m taking some time to do that in the context of the WordPress project, and it’s reminded me of one of the foundational things I talk about a lot that may be a little harder for folks to see. I am routinely grateful, of course, for the people who show up to maintain WordPress, the people who keep the back office work going, the contributors who contribute directly to the WordPress CMS and project, the folks who routinely go out and tell other people about WordPress and make sure others know how to use it. 

\n\n\n\n

Josepha Haden Chomphosy  01:35

\n\n\n\n

But there’s another group that I talk about a lot that is a little harder to grasp. And that’s this conceptual group of people whose lives have been changed by WordPress. I used to run into people like this all the time when I was organizing WordCamps. And the small but meaningful successes that they share year after year made me realize that my small contribution of organizing these events was really quite valuable; valuable to them, and I assumed also valuable to just other people in the WordPress project. 

\n\n\n\n

Josepha Haden Chomphosy  02:09

\n\n\n\n

Now, if you’re contributing in a way that doesn’t let you have contact with the same users consistently over time, or if contributing doesn’t quite balance out in your ledger at the moment, it can be hard to put names to faces in a way that lets you see how your contributions are making an impact. To help with that, a few years ago, the WordPress project partnered with the community Marketing team and the HeroPress team to share the People of WordPress series which you can find monthly on wordpress.org/news. For me, this series provides a glimpse into the humanity of the people who use WordPress, and for me, that’s enough. If all the series ever did was to remind us that WordPress was made for people whose needs matter, that would be enough to continue to have that series forever. But fortunately, the series does quite a bit more than that. 

\n\n\n\n

Josepha Haden Chomphosy  03:04

\n\n\n\n

The People of WordPress series also lifts up the stories of people who we don’t always hear from in technology. It highlights the wide array of origin stories that lead people to WordPress. It reminds us of the global nature of what we’re doing. It reconnects us to the hopefulness of our own first WordPress successes. And it draws a direct line to why we should care about refreshing the commons of this open ecosystem. I’m sure that there are more things that do as well. But those are just the things off the top of my head, we draw all of the people of WordPress stories that are inside that series directly from the HeroPress essays that have been submitted by users. And I was gonna say users like you in a kind of Reading Rainbow way. But I actually don’t know if any of you are everyday users who are also using WordPress but maybe not contributing yet. If you are then like I’m talking to you. And if you’re not, I’m probably still talking to you. Because all of these stories that go to HeroPress are very valuable and very important for us to know. Anyway, I digress.

\n\n\n\n

Josepha Haden Chomphosy  04:14

\n\n\n\n

Topher DeRosia, who founded HeroPress, is among the first people I met in the community lo these many years ago. And I think the impact that HeroPress has on the WordPress community as a whole is not always well recognized. So in the spirit of expanding the scope of my gratitude, and in the context of refreshing the commons, I would encourage you to head over to HeroPress.com and their newly launched HeroPress Network and see if there’s any little way that you can contribute to their commons, submitting your story donating to their network offering a small bit of volunteer time if you happen to have any spare time lying around. I know that the team would be delighted to hear from you.

\n\n\n\n

Josepha Haden Chomphosy  05:01

\n\n\n\n

That leads us now to our small list of big things. We are about a week away from the feature freeze for WordPress 5.9, the final release of the year. Feature freeze caused a little confusion last time. So I just want to clarify there won’t be a package released with this milestone. But no more enhancements or features will be worked on at that point. And bug fixing will become the primary focus. That will be on November 9, which I believe is next Tuesday. It’s definitely next week whenever the calendar turns to nine of November 2021. That’s the day that we’re going into feature freeze. 

\n\n\n\n

Josepha Haden Chomphosy  05:38

\n\n\n\n

The second big thing in our small list of big things is that team rep nomination season is upon us. If you are a team rep or want to learn more about being one, now is the time to kind of look at what’s going on and how to keep everything moving in that way. I’ll include a link to the announcement post of that in the notes below. 

\n\n\n\n

Josepha Haden Chomphosy  05:57

\n\n\n\n

And finally, Daylight Saving Time movements are also upon us. Some parts of the world are ending Daylight Saving Time others are starting it and some have already started or stopped that already. So no matter where you are, don’t forget to check and double-check the timing of things across time zones for the next few weeks. 

\n\n\n\n

Josepha Haden Chomphosy  06:21

\n\n\n\n

And that is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11368\";s: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:78:\"\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:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"People of WordPress: Ronald Gijsel\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wordpress.org/news/2021/10/people-of-wordpress-ecommerce-ronald-gijsel/\";s: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, 30 Oct 2021 12:21:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:8:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:17:\"Contributor Story\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:9:\"HeroPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:7:\"meetups\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:6;a:5:{s:4:\"data\";s:20:\"WordPress e-commerce\";s: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:5:{s:4:\"data\";s:17:\"WordPress journey\";s:7:\"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=11370\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:132:\"Ronald Gijsel on his path from chef to WordPress e-commerce specialist, in the latest People of WordPress feature. #ContributorStory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"webcommsat AbhaNonStopNewsUK\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11713:\"\n

In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a WordPress e-commerce specialist on the difference it makes.

\n\n\n\n

Empowered to make a change

\n\n\n\n

For WordPress contributor Ronald Gijsel, open source is a lifeline and a perfect place for people with creative minds. It led him on a transformational journey from chef to WordPress e-commerce specialist. Originally from the Netherlands, where he trained in hospitality, he was to find a restorative and energizing power within the WordPress local and global community.

\n\n\n\n

Ten years ago, life took a sad turn for Ronald and his wife Nihan when their baby daughter passed away only a few days after she was born. At that time, Ronald was a restaurant owner in the UK, working hard in a challenging economic environment. Discovering open source was in many ways his lifeline and helped him and his wife through their considerable heartache. Through this community, a journey to understand the opportunities of the web and new career paths began.

\n\n\n\n

Ronald believes that working together in WordPress and other open source communities can lead to massive benefits for a large number of users. Not least, an online presence has been essential to the survival of many businesses during the Covid-19 pandemic. 

\n\n\n\n

During recent years, he has visited open source events worldwide as a partnership manager at a WordPress e-commerce plugin company and community supporter. His enthusiasm for WordPress has steered him to being part of local support, solutions and collaboration as a co-organizer of WordCamp Bristol, the WordPress Cheltenham Meetup and more.

\n\n\n\n

Moving forward 

\n\n\n\n

When Nihan enrolled in the UK’s Open University to complete her computer science degree, Ronald found her course materials stirring his own interest. He started to follow the lectures with her and even attempted some of the course work for himself – all whilst he continued to work as a chef in various local pubs. 

\n\n\n\n

Through this, he discovered how to generate affiliate commission earnings through blogging on different platforms. “Creating websites was slowly becoming a passion. In these first few years, I enjoyed every part of the steep learning curve, from tackling the basics to more advanced coding and designs,” said Ronald.

\n\n\n\n

The Start of a Web Career

\n\n\n\n

Ronald reduced his hours as a chef and devoted more time to online courses learning coding, e-commerce, SEO, and online marketing. Yet when he applied for a job as a WordPress designer, he had only heard of the platform in the context of blogging. This was all to change when an online tutor on one of the training sites revealed the many functions available with WordPress. It was the start of a new career and life journey. This tutor was Topher DeRosia, who went on to create HeroPress.

\n\n\n\n
\"Ronald
Ronald with Topher at WordCamp London in 2019
\n\n\n\n

To learn WordPress, Ronald ‘binge-watched’ webinars on various development topics and over time he became more familiar with it. Securing a job as a designer was only the beginning of his journey into the WordPress ecosystem.

\n\n\n\n

A year later in 2015, after landing the job as a WordPress designer, Ronald’s boss asked him to consider taking on the business and its clients. With his wife, Ronald decided to take on the firm and to expand their work in WordPress e-commerce and online marketing.

\n\n\n\n

As an advocate for learning new skills and practicing them, Ronald encourages others to continue to expand their knowledge through study, attending talks at Meetups and WordCamps, and using the new Learn WordPress resource.

\n\n\n\n

“WordPress has evolved in so many branches that require different skills. There are hundreds of areas of expertise, roles, and jobs that complement WordPress to make it what it is.”

\n\n\n\n
\"Ronald
\n

“WordPress is an essential tool in my box.”
Ronald Gijsel

\n
\n\n\n\n

Ronald believes WordPress thrives on diversity, with many contributor opportunities and jobs in the ecosystem that require a wide range of skills. 

\n\n\n\n

“A big part of this is that each person’s personal background complements their skill sets. Who you are and what you do is influenced by what you have done and learned. We need to cherish this. These things also add to our culture, language, experience, and knowledge,” he said.

\n\n\n\n

A journey into WordPress e-commerce

\n\n\n\n
\"Ronald
Ronald shares his enthusiasm for building WordPress and e-commerce websites at WordCamp London in 2019
\n\n\n\n

Ronald initially extended his interest in the WordPress ecosystem through representing a plugin company at WordCamps in the UK. He became hooked and went on to attend events in many different countries. 

\n\n\n\n

In 2018, he realized he could do more with his connections and create meaningful partnerships. Within a few weeks, he had crafted his dream job and sent a proposal to the CEO of a WordPress e-commerce firm.

\n\n\n\n

But pitching to strangers wasn’t an easy task, as he did not know if they would understand his vision.

\n\n\n\n

Ronald said: “The doubts went through my head for months. ‘Do I give up my business and work for the benefit of another company? What if I don’t get on? What do I do with my customers?’ But I decided to take the leap.” His pitch proved successful, joining his current firm in 2019.

In the firm’s CEO, Ronald found a mentor, supporter, and a friend. He explained: “Nando Pappalardo never tells me what to do, but instead, he asks questions to make me realize what is achievable, or could be even better. He simply makes suggestions that I read something and reach my own conclusions.”

\n\n\n\n

Looking back at the journey 

\n\n\n\n

Taking risks or changing directions in mid-career often involves a giant leap. In Ronald’s view, through WordPress, you don’t need to be alone. He believes its community can offer support and help to process thinking.

\n\n\n\n

Ronald said: “I often think back to the moment my daughter passed away. She only lived for a few days. Every day, I wonder how events would have unfolded if she had survived. Maybe her memory lives on in every decision I make and the paths I decide to take.”

\n\n\n\n

From his experience, he found that changing a career can sometimes take a few years and have a period of transition. He said: “Only looking back do I realize that each small step slowly made a difference in my life.”

\n\n\n\n

“It was WordPress that made the online world easier to navigate and empowered me to make a change” 

Ronald Gijsel
\n\n\n\n

He added: “Feeling welcomed into the WordPress community through Meetups and WordCamps added a human dimension and confidence that I can do ‘this’ too.”

\n\n\n\n

Ronald’s wish is that his story will offer support to others who may have experienced tragedy in their lives. “I hope that I can give you the hope and strength to try and put your energy into something else that can lead to more significant changes in your life. Try to take it as one positive decision at a time.”

\n\n\n\n

Share the stories

\n\n\n\n

Help us share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series. #ContributorStory.

\n\n\n\n

Contributors

\n\n\n\n

Thank you to Abha Thakor (@webcommsat), and Surendra Thakor (@sthakor) for the interviews and writing this feature, and to Ronald Gijsel (@just2ronald) for sharing his story.

\n\n\n\n

Thanks to Meher Bala (@meher), Chloé Bringmann (@cbringmann), Anjana Vasan (@anjanavasan), Collieth Clarke (@callye), and Reyes Martinez (@rmartinezduque) for their content contributions, and Josepha Haden Chomphosy (@chanthaboune), and Topher DeRosia (@topher1kenobe) for their support for the series.

\n\n\n\n

This People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"11370\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Mon, 03 Jan 2022 21:09:40 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:25:\"strict-transport-security\";s:11:\"max-age=360\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Fri, 31 Dec 2021 00:04:20 GMT\";s:4:\"link\";s:63:\"; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";}}s:5:\"build\";s:14:\"20211221224051\";}', 'no'), -(173, '_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3', '1641287381', 'no'), -(174, '_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3', '1641244181', 'no'), -(175, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1641287382', 'no'), -(176, '_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:26:\"Matt: Celebrate by Writing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=55257\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://ma.tt/2022/01/celebrate-by-writing/\";s: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:1965:\"

My birthday is coming up soon so it’s that time of the year when friends start reaching out and asking where they should fly to and how we’re going to celebrate.

\n\n\n\n

After a good run in the post-vaccinated-and-boosted part of 2020 that felt relatively “normal”, including traveling almost 200k miles, I’m going back into a pretty locked-down state of things. Omicron has just been catching too many friends and loved ones, even with fairly careful measures and testing. So what’s happening on January 11th?

\n\n\n\n

What I’m asking for my birthday is for people to blog!

\n\n\n\n

Whether professionally on WP.com, socially on Tumblr, or privately journaling with Day One, there’s never been a better time to stop being a passive consumer of the internet and join the class of creators.

\n\n\n\n

Write for a single person. Share something cool you found. Summarize your year. Set a blogging goal with reminders. Get a Gutenberg-native theme and play around with building richer posts. Start a nom de plume. Answer daily prompts on Day One. Forget the metaverse, let’s hang out in the blogosphere. Get your own domain!

\n\n\n\n

If you’re a close friend that feels intimidated by the software at all or that you don’t know where to start, I’m happy to hop on a Zoom to go through everything on a screen share. That will also be a great learning for me for places we can improve things, which is also a fantastic gift!

\";s: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, 02 Jan 2022 22:22:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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: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:43:\"WPTavern: WP Tavern’s 2021 Year in Review\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127766\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"https://wptavern.com/wp-taverns-2021-year-in-review?utm_source=rss&utm_medium=rss&utm_campaign=wp-taverns-2021-year-in-review\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:13867:\"Abstract Lights by Marcus Kazmierczak\n\n\n\n

A friend prompted me to fix an issue with the WP Tavern archives page a few days ago. Not all of 2021’s posts were visible. As I glanced over the updated list, I realized our team put in a lot of work for the year.

\n\n\n\n

In the day-to-day mix of things, it is easy to forget how much you have written during the year. Some of the articles are memorable and stick with you for a while. Much passes by in a blur. But, I felt a sense of pride in the work our team has put in as I scrolled through the posts.

\n\n\n\n

These year-in-review posts tend to take about two days’ worth of work, gathering up all of the stats and notes and formatting them so that they are presentable. However, they are always one of my favorite articles to put together every year.

\n\n\n\n

We should always take some time to remind ourselves where we have been on this journey. This makes sure we are better informed before taking our next steps. At the Tavern, that means paying attention to what content people are reading and how they are engaging with it.

\n\n\n\n

So, let us just dive right into some of the 2021 highlights.

\n\n\n\n

The Year in WordPress

\n\n\n\n

WordPress turned 18 years old in 2021. That is a massive feat for any software, especially a CMS that consistently faces competition from newer web technologies.

\n\n\n\n

Unlike last year’s three, the platform only saw two major releases this year. WordPress 5.9 was initially slated to land in early December, but it was postponed until January 25, 2022. This should give contributors more time to smooth out several wrinkles with new features.

\n\n\n\n\n\n\n\n

The Gutenberg plugin was a consistent force, driving new features that would eventually make their way into core WordPress. We have covered its releases throughout the year here at the Tavern.

\n\n\n\n

Matt Mullenweg recorded his annual State of the Word before a live audience in New York City in mid-December. The address focused on WordPress’s growth in the past year, a decentralized web, and version 5.9 features. He also focused on contributing to the commons. He introduced Openverse, formerly Creative Commons Search, and noted the beta launch of the WordPress photo directory.

\n\n\n\n

Favorite Plugin

\n\n\n\nNewsletter Glue’s theme designer.\n\n\n\n

One of the best things about writing for WP Tavern is covering a range of new plugins every year. Unfortunately, we cannot get to them all. However, there are always a few projects that stand out in the crowded field.

\n\n\n\n

Maybe it was nostalgia for a bygone era of printed family newsletters. Perhaps it is just a neat idea, but my favorite plugin of the year is Newsletter Glue.

\n\n\n\n

It showcases how a small team can get a complex project off the ground via the block editor. Newsletter Glue is just over a year old, and Lesley Sim and Ahmed Fouad have created a solid product.

\n\n\n\n

Favorite Theme

\n\n\n\nEksell theme homepage\n\n\n\n

This should come as no surprise to Tavern readers. I have touted its well-rounded design and architecture on multiple occasions. Eksell by Anders Norén is my favorite theme of the year. Twenty Twenty-Two would be a close second, but it has not officially launched yet. Maybe it will reign in the year to come.

\n\n\n\n

I have been on the lookout for a block theme to win this for the entire year, but none of them quite lived up to Eksell. Not even Noren’s own attempt with Tove.

\n\n\n\n

Eksell plays well with blocks, supporting all current, stable advancements in WordPress theming. It is far more modern than many other classic-supported themes. And, it is just beautiful.

\n\n\n\n

WP Tavern Stats

\n\n\n\n

Over the past couple of years, we have increased our content output. Engagement via published comments is down, but “likes” continue climbing. The following is a table of the past three years of stats. Note that averages are per post.

\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 \n
202120202019
Total Posts443406382
Total Comments3,1513,6992,864
Avg. Comments7.19.27.5
Total Likes4,5083,5892,676
Avg. Likes10.29.07.0
Total Words324,842317,231225,117
Avg. Words733791589
\n\n\n\n\n

Of course, we moderate comments here at WP Tavern. We could let things run wild for a bump in commenting stats, but we want to continue creating an environment where people feel welcome to participate.

\n\n\n\n

I am the champion of comments this year with a total of 81. I would still like to engage a bit more. That is something I will work on in the new year.

\n\n\n\n

Props to the five people next in line for total comments in 2021:

\n\n\n\n
  • Miroslav Glavić
  • Eric Karkovack
  • Andrew Starr
  • Steven Gliebe
  • Paul Lacey
\n\n\n\n

Without you and other readers, there would be no Tavern. I hope to see more of you all and others in 2022.

\n\n\n\n

Top 10 Most Viewed Stories

\n\n\n\n

Sarah Gooding pretty much single-handedly broke our all-time daily views record in January, a record that had stood since 2015. It now stands at 24,887. I contributed a bit, but her coverage of WordPress.com’s website building service did the heavy lifting. And, it was not even the overall most-viewed story of the year.

\n\n\n\n

The following are the articles Tavern readers viewed the most in 2021:

\n\n\n\n\n\n\n\n

Top 10 Most Commented Stories

\n\n\n\n

You would think that our most-read articles are those that receive the most comments. However, that is not always the case. While there is some crossover between the two lists, our readers sometimes need to be vocal on a particular topic.

\n\n\n\n

Here are the top 10 most-commented posts of 2021:

\n\n\n\n\n\n\n\n
\n\n\n\n

I look forward to another year of delivering stories to all of our readers. The Tavern staff will see you all in 2022 for the next steps on this journey.

\";s: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, 31 Dec 2021 04:11:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:59:\"WordPress.org blog: People of WordPress: Collins Agbonghama\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11923\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wordpress.org/news/2021/12/people-of-wordpress-collins-agbonghama/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7730:\"

In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a website builder from Nigeria, who uses the open source WordPress platform to support his family and to share learning with others in his home country and beyond.

\n\n\n\n\"Collins\n\n\n\n

Creating a life in the WordPress Ecosystem

\n\n\n\n

Collins Agbonghama started his journey to becoming a web developer by reading the football news headlines on a friend’s mobile phone. His fascination with development and learning continued to grow, and he now makes a living using WordPress and the web.

\n\n\n\n

Read on to discover his story, which shows with creativity and determination you can create products and make a living using WordPress. 

\n\n\n\n

Starting web building on a phone

\n\n\n\n\"Collins\n\n\n\n

Collins began his exploration of the internet while attending Secondary School in Nigeria, or High School as it is known in some other countries. 

\n\n\n\n

A friend at the school had a simple mobile phone which could browse the internet. Collins had his first introduction to the World Wide Web through access to this device. He became hooked by reading headlines on a sports site about a famous English Premier League Football Club, Chelsea, a soccer team which he has long supported.

\n\n\n\n

“Being a very inquisitive person, I wanted to learn how the web works as well as have my own website. I was able to buy a classic mobile phone through the menial jobs I did after school,” he said. 

\n\n\n\n

His first website was a wapsite or Wireless Application Protocol site optimized for mobile devices. 

\n\n\n\n

He took to Google to learn how to actually build a site. He discovered he needed something called an ‘email address’ to sign-up for site builders. Google Search came to the rescue again, and he created the first email account for his first website.

\n\n\n\n

A desire for a website was the catalyst for further learning, starting with HTML and CSS from an online provider. His interest in building sites with more advanced tools grew, and then he came across WordPress. 

\n\n\n\n

Using his savings, he bought the cheapest hosting plan from a local Nigerian web host. He installed WordPress and started writing tutorials for a mobile device platform. He built the site, created the lessons, and started his entry into WordPress all on a mobile phone. 

\n\n\n\n

This led to him having the confidence to start building sites for others, and he was able to earn a small income from that. 

\n\n\n\n

Collins said: “I couldn’t go to the university because of my precarious financial situation. I continued to do menial jobs during the day and started learning PHP in the evenings and at night using my mobile phone via online learning platforms.”

\n\n\n\n

He was later able to get an old laptop, which helped him access ebooks to learn more and practice his coding. 

\n\n\n\n

Keen to share this learning, he started blogging about what he was learning on his website.  

\n\n\n\n

Collins said: “I later took up a job teaching children at a school primarily because I got tired of the menial jobs and wanted to earn enough to take care of my internet data plan. After a while, I became fairly proficient in PHP and even took up a job to build a school management system.”

\n\n\n\n

Using WordPress to make a living

\n\n\n\n

Collins’ blog wasn’t making money through advertisements, but he discovered opportunities to write tutorials for other platforms. 

\n\n\n\n

“I started writing PHP and WordPress development tutorials and got paid a few hundred dollars per article. In Nigeria, that’s quite a lot of money. I was able to improve the life and wellbeing of my family and myself,” he said.

\n\n\n\n

After getting into a higher education program to study computer science, his life dramatically changed. He decided to stop writing and began to focus on building and selling WordPress plugins. His first one was a user and profile plugin for WordPress sites.

\n\n\n\n

“Thankfully, after a year, it started making enough revenue for me to live pretty comfortably here in Nigeria because the cost of living here is relatively low,” he said

\n\n\n\n

Today, Collins has several plugins which have given him a sustainable source of income. He’s also a Core and Translation volunteer contributor to the WordPress.org Open Source project.

\n\n\n\n

I am thankful for WordPress because without it, I’m really not sure I would have been able to live a decent quality life.
Who knows what would have become of me?

Collins Agbonghama
\n\n\n\n

“I am also thankful for the community. I have made lots of friends that have been very supportive and helpful in my journey.”

\n\n\n\n

He added: “I tell people, life won’t give you what you want. You demand from life what you want. You make these demands by being determined and never giving up on your dreams and aspirations.

\n\n\n\n

“If you are poor, perhaps because you came from a humble and poor background, it is not your fault. You can’t go back in time to change things. I implore you to be strong, determined, and work hard.”

\n\n\n\n

\n\n\n\n

Meet more WordPress community members in our People of WordPress series.

\n\n\n\n

Contributors

\n\n\n\n

Thanks to Michael Geheren (@geheren), Abha Thakor (@webcommsat), for writing this feature, to @MeherBala (@meher) for follow-ups and photo-editing, and to Chloe Bringmann (@cbringmann) and Nalini Thakor (@nalininonstopnewsuk) for the final proofing. Thank you to Collins Agbonghama (@collizo4sky) for sharing his Contributor Story.

\n\n\n\n

Thanks to Josepha Haden Chomphosy (@chanthaboune), Topher DeRosia (@topher1kenobe) and others for their support of this initiative.

\n\n\n\n

The People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia, which highlights people in the WordPress community who have overcome barriers. 

\n\n\n\n

#HeroPress #ContributorStory

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 Dec 2021 22:45:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"webcommsat AbhaNonStopNewsUK\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"Post Status: Post Status Comments (No. 5) — The First Annual WordPress News Draft\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=91900\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/comments/5/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:76553:\"

“This story reminded me that big company, big money doesn\'t mean just more profit but can also mean big contributions.” —Aurooba Ahmed

\n\n\n\n

It\'s the first-ever Post Status WordPress News Draft! The initial group of news “avengers” in this episode are Aurooba Ahmed, Jason Cosper, Daniel Schutzsmith, Robert Jacobi, and Lesley Sim — with David Bisset hosting. In three rounds of draft picks, this group assembled the most noteworthy or influential WordPress news stories of 2021.

\n\n\n\n

Also: There was also a final “quick link” round with some interesting choices the guests brought to the table.

\n\n\n\n\n\n\n\n

Post Status Comments \"💬\" provides a stage for WordPress professionals to exchange ideas and talk about recent topics and trends.

Browse past episodes and subscribe to our podcasts on  Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or get them by RSS. \"🎙\"

\n\n\n\n

\"🔗\" Mentioned in the show:

\n\n\n\n\n\n\n\n

\"🙏\" Sponsor: Gravity Forms

\n\n\n\n

Gravity Forms is the easiest and most trusted advanced forms solution for your WordPress website. Packed with time-saving tools and features, Gravity Forms is the only WordPress form management plugin you will ever need. Stop losing valuable leads and grow your business with Gravity.

\n\n\n\n

Transcript

\n\n\n\n

[00:00:00] David Bisset: All right. Welcome to the first and maybe even last news draft for post status. My name is David White screen Bisset, I\'ll be your host this evening. We have some great panelists here this evening. Let me explain to you the concept of what\'s going on first. So there are sports drafts where people pick players within a group.

\n\n\n\n

And at the end of the draft, these people pick the players they want, and they form these teams. Well, we are basically doing that except for WordPress news. So we have five panelists plus myself here this evening. There\'ll be introducing themselves in a second. They all have their top WordPress stories of 2021.

\n\n\n\n

I asked what WordPress stories of 2021. They think we\'re the most important or the most influential that meant the most to them. So in a draft, there is an order. We have our order set. The only two rules, I think are one. You obviously can\'t repeat another pick once it\'s out. So you have go to your [00:02:00] alternate picks and you have to be specific in your pick.

\n\n\n\n

So it can\'t be just acquisitions. It has to be a specific news story. So X acquired Y and I think there is also one more rule where it\'s about the story, not where it\'s posted from. So if X acquired, Y was taken from the Tavern, the next person can\'t pick the same story just because it was the new story there.

\n\n\n\n

The link that they\'re sharing is from another source Post Status. So if we\'re all good on that, let\'s , introduce our panel and the order that was picked by random.org. Ruba, why don\'t we start off with you

\n\n\n\n

Aurooba Ahmed: I\'m Aurooba, I\'m a WordPress developer, and I\'m excited to be here,

\n\n\n\n

David Bisset: Daniel, your name, occupation, and rank.

\n\n\n\n

Daniel Schutzsmith: Daniel\'s Schutzsmith. I\'m a web developer and get to work on things like WP live streams, directory.

\n\n\n\n

David Bisset: Yeah. And next is Jason Cosper, not Cooper Cosper.

\n\n\n\n

Jason Cosper: Hey, what up everybody? This is Jason Cosper, AKA fat Mullenweg. I am the [00:03:00] WordPress product advocate over at DreamHost and also I cohost WP water cooler with my friends Jason Tucker and Steve Zynga,

\n\n\n\n

David Bisset: Robert Jacoby. You\'re up next. How\'s it going?

\n\n\n\n

Robert Jacobi: And grade what a wonderful way to end the sort of year Robert Jacobi director of WordPress at cloud ways, a WordPress cloud manage hosting service.

\n\n\n\n

David Bisset: And you go the way of the clouds last, but certainly not least. Leslie, tell us a little bit about your.

\n\n\n\n

Lesley Sim: Hey, it\'s Leslie SIM I\'m co-founder of newsletter glue.

\n\n\n\n

It\'s a WordPress newsletter plugin and also a big Post Status fan.

\n\n\n\n

David Bisset: Oh, okay. Well, that\'s not going to get you anywhere, but the the nice remark is appreciated. All right, let\'s start off with Aurooba, what is your first pick?

\n\n\n\n

Aurooba Ahmed: I apologize to everyone, but it\'s that 5.9 was delayed. This was really, really big.

\n\n\n\n

I [00:04:00] remember at the beginning of this year, complaining and complaining about 5.8 being released with half-baked features and, for developers who were working on products for clients, this was a really frustrating time. So on 5.9 was delayed because some of the features were not as you know, still needed some issues fixed in them.

\n\n\n\n

That felt like we were hurt a little bit. And this was setting a precedent of never doing. A release with half big features and maybe even a president of never doing a release around December holidays. Like maybe this will just shift the whole cycle. That would be really nice. And I mean, I remember someone said that deadlines are not arbitrary and they\'re not, but meeting a deadline for the sake of meeting a deadline is also not a valid approach.

\n\n\n\n

And I hope that we can have more discussions around that with WordPress release cycles.

\n\n\n\n

David Bisset: This was not on my list, but because I only have like five or six items on my list, but I agree that this is a bit of a change. I mean, five nine would have come out. It would have come out. Guess when it [00:05:00] would have come out? On state of the word night.

\n\n\n\n

Yeah, I don\'t know. It\'s certainly affecting next year somewhat because I think the schedule they\'re trying to talk about next year as a potential four release schedule, or at least two of the four or two of the three we\'ve never had. I don\'t think we\'ve had a release in January. I think that\'s potential.

\n\n\n\n

That\'s a very good first round pick. I don\'t know if anybody got that, but so far I\'m safe, but I think that\'s a very good pick. And that\'s one of those picks that\'s going to be by like maybe middle of the year next year, we\'re going to look back on here and say, this is how much this decision made in terms of change.

\n\n\n\n

And I think it was good decision to . All right. Let\'s see Daniel, you\'re up. What\'s your first pick?

\n\n\n\n

Daniel Schutzsmith: This happened this year and I didn\'t even realize it was this year was the whole profile press WP user avatar debacle. They had a. 400,000 active installs at the time. And basically I believe what happened was the company got taken over basically and renamed the plug-in [00:06:00] overnight to which it was a bit different than when it used to be.

\n\n\n\n

And for those who didn\'t use WP use avatar, it was basically a kind of a one function type of plugin. But all of a sudden you had this profile press, which was much more involved. And it basically changed the user interface of everything. I had a few clients using it, so it was a bit of a shock. And uh, since then, I\'ve, I believe on all those, we just got rid of it and just did something else instead.

\n\n\n\n

But to me, I was looking back then, you know, what happened in the past year and 2021 and this stuck out right away. Once I realized it did happen in 2021. Yeah. Well, Collins Collins is the owner of profile press and he\'s a developer and owner and really nice guy. There\'s actually a great interview with him over on the WP minute.

\n\n\n\n

That was also done around the same time. So it wasn\'t a malicious intent at all. I think it was just, you know, just a misstep basically in in best business practices.

\n\n\n\n

David Bisset: And just goes to show you the like, I think now as we get further, along in the WordPress ecosystem, how, like, if that would\'ve happened, maybe.[00:07:00]

\n\n\n\n

Maybe with less users, maybe like four years ago. I think it wouldn\'t have been such a magnified or a focus type of issue. Right. So as WordPress plugins go on, you know, and people have to be really, even more careful because the audiences are getting bigger. The stakes are getting bigger. My headache medications getting bigger.

\n\n\n\n

All right. But that\'s okay. Great. Excellent pick. So profile press debacle, unintended debacle, but debacle was Daniel\'s pick. And thank you very much. So, Jason what\'s your first pick? Yeah.

\n\n\n\n

Jason Cosper: So, Aruba took my pick naturally. Yeah.

\n\n\n\n

David Bisset: We have our first snipe.

\n\n\n\n

This is awesome. This is like the first night.

\n\n\n\n

I didn\'t really think we\'d have one tonight.

\n\n\n\n

Jason Cosper: Yeah. well, I mean, she\'s in the catbird seat. She is basically you know, there, first up so I applaud you for grabbing that one. So I\'ve got to go with what was going to be my second pick, which is the WordPress performance team.

\n\n\n\n

David Bisset: Ah, [00:08:00] I got sniped.

\n\n\n\n

Okay.

\n\n\n\n

Jason Cosper: Yeah, there we go. So I snipe with a snipe. Perfect. So as somebody who has been focused on WordPress performance through a pretty significant portion of my time in WordPress making WordPress faster, I think that it is great that we are finally seeing a focus for this on core and the people who are throwing their names in till Cruz Henry Helvetica a few other you know, just really amazing people and just the amount of activity that\'s happening in the performance channel or when they have their weekly team meetings is just phenomenal to me.

\n\n\n\n

And it was kind of a late in the year thing, but I\'m really excited to see it grow in 2022.

\n\n\n\n

David Bisset: I honestly had doubts in the beginning when I first read it, that it was going to be a thing. It was a proposal when I read it first. And I\'m not saying that nobody cares about performance, but it was just, I don\'t know.

\n\n\n\n

[00:09:00] It\'s one of those things where I guess maybe it was too good to be true. Right. You know, one of those, one of those deals it\'s being Frank here, my views and opinions don\'t reflect those of any collective or individual Post Status and Post Status team can incorporate. Well, that\'s a great first. Okay.

\n\n\n\n

That\'s a great first pick word, press performance team. And yes, I would. I would admit I was sniped on that. So Robert Jacobi, please leave me with a list I can share

\n\n\n\n

Robert Jacobi: with the 2017 first pick the Chicago bears choose Mitch Trubisky.

\n\n\n\n

David Bisset: That sounds like a great clam chowder too

\n\n\n\n

Robert Jacobi: Rochelle wrong show.

\n\n\n\n

David Bisset: Oh, that\'s been wrong year. Good Lord. Oh, wrong team.

\n\n\n\n

Robert Jacobi: I\'m going to snipe. Everyone\'s acquisition. Want to be. Drafts and say that the biggest acquisition news of the year was Yoast being acquired by new fold. Digital

\n\n\n\n

David Bisset: hard to ignore that one.

\n\n\n\n

Robert Jacobi: It\'s I think it\'s important [00:10:00] because everyone knows Yost from like, you know, community hardcore folk to end your end users and users almost got ghosted by Yoast. And I think it really shows what the WordPress economy is evolving into and no opinions here, but it\'s changing. And when you have a huge, acquisition by someone like new fold slash blue host, for all intents and purposes of Yoast I think it really sent up flares economic flares throughout.

\n\n\n\n

WordPress ecosystem

\n\n\n\n

it very few long old-school WordPress plugin companies left. And that way I think on a lot of people\'s lists was the first one they thought of. Yeah. I\'m not going to mention the other ones, because if I say it three times, maybe like Candyman there\'ll be acquired or they\'re already acquired or they\'re already in the works for all I know for all we know.

\n\n\n\n

Right. I think it was the suddenness of it too. [00:11:00] That was a quick one. Right. I think with the like advanced custom fields, you could see it a little bit coming, or you wondered in the back of your mind one lazy day on wonder what\'s. I wonder if they\'re ever going to be acquired some day, but I personally never felt that way with Yoast.

\n\n\n\n

It\'s just the yellow steel was approximately nine to 12 months in the works.

\n\n\n\n

David Bisset: Yeah. Which, you know, obviously for that good, you keep a secret, right? Yeah. But yeah. So, okay. Well our first acquisition pick off the tape. Fortunately for us, we\'ve got 85,000 more acquisitions on the table. So that may be a popular one, but it\'s not the

\n\n\n\n

Robert Jacobi: I\'m following all the acquisitions with that one.

\n\n\n\n

David Bisset: Oh, it\'s going to be a long night. So Leslie, maybe you can what\'s your pick first round?

\n\n\n\n

Lesley Sim: So my I\'m going with an acquisition related topic and it\'s extending insight Awesome Motives self-perpetuating marketing machine. So I think like this post was inspired because of Awesome Motives acquisition of [00:12:00] Pippins plugins, but it\'s called something else.

\n\n\n\n

It\'s not called that. And so what I liked about this article was kind of how it mapped out the huge fast SEO machine that Awesome Motive is building and how Sandhills and all their plugins kind of fits into that and how it kind of, yeah, just like creates this big content marketing machine, which is hard to replicate on a smaller scale.

\n\n\n\n

And I guess like people often talk about WordPress from a developer point of view. I think like most of you here are, you know, developer centric. And so I wanted to bring in marketing the marketing side of things and, you know, like talk about how begin and WP and all of the automotive blog assets plays such a big part in the WordPress ecosystem.

\n\n\n\n

Like anyone who\'s not a WordPress professional, if they\'re coming into WordPress for the first time, it\'s likely that [00:13:00] Awesome Motives blogs will be the first point of contact into WordPress. And I think like that\'s really interesting to consider and also what that looks like going forward as well for the ecosystem.

\n\n\n\n

David Bisset: They have a very good content management strategy I used to work there. So I can tell you if they\'ve got a nice well-oiled machine over there and that in your right. I don\'t, I, you know, maybe it\'s just the circles that I travel with or the circles that allow me to travel with them, if you want to look at it that way.

\n\n\n\n

But I don\'t think that gets a lot of attention, so, so great job,

\n\n\n\n

Robert Jacobi: David. I think Syed likes it that way.

\n\n\n\n

David Bisset: Let\'s quickly move on to my pick. So this was my first pick and it\'s a pick from the Tavern and it\'s specific it\'s Tavern. It\'s partly the subject material, but also because Sarah Gooding just did an excellent job.

\n\n\n\n

It\'s amp has irreparably damaged publisher\'s trust in Google led incentives. This got on hacker news, which appeals to a broader audience than beyond WordPress, which is one reason why I [00:14:00] picked it. The other is if anybody remembers how amp was I\'m going to say promoted at word camps. And I remember one word camp, it probably it\'s either 2018 one or the 19 one. Like I think it was in giant letters. Google had a huge, and they were advertised. There was other things being promoted there. But I remember all of the discussion and the effort that went into convincing developers to contribute to the amp project. I remember discussions about.

\n\n\n\n

Well, it\'s the old automatic contribution controversy that some people like to bring up, like, you know, like it\'s open source, but there\'s so many people from this company working on it, that they have a certain level of control that is unfair or is unwarranted and so forth. And people made that case for the Google and people again, to, in that project, regardless of where, which site you fell on that.

\n\n\n\n

Cause I ultimately, in the end, I think that discussion never [00:15:00] really reached an official conclusion or closure. There was a lot of talk and this kind of, regardless of how many developers were aware of what Google was doing, their trust there has been broken and it\'s broken today. It\'s going to take a very long time for Google, I think, to come into the WordPress community and open project or not, and not be looked at with a mark of suspicion, even if the developer, and I\'m not even saying the developers involved with NAMP knew everything that was going on or what, or whatever was brought up. It\'s an excellent article by Sarah on that. And I thought it was fair and it got picked up by a wider audience. And it does address, not just Google, but you know what happens when we have companies, larger companies that are in the news because of the, you know, of antitrust or because of their worker policies or whatever, what far extent do you trust them?

\n\n\n\n

Knowing that not everybody in the [00:16:00] company has the same evil intentions, what you think are evil, but how far do you trust them when it comes to the, you know, WordPress and open source projects? And I think that\'s a good question. And I think everybody has the right to have a different answer. So I thought it was a very thought provoking article.

\n\n\n\n

So that was my first pick there.

\n\n\n\n

Robert Jacobi: Even if I may, you snipe me. That was my number three pick, but I actually came at it from a different way. It was the Jeremy Keith blog post about resigning from the amp advisory committee.

\n\n\n\n

David Bisset: Okay. That\'s another good one. Yeah. And what did you think about what stood out from you on that one?

\n\n\n\n

I\'ll throw you a bone.

\n\n\n\n

Robert Jacobi: That\'s what I think I\'ve been I\'m not an eight amp. Let\'s just call it an amp because that\'s what everyone else calls it. I\'m not an amp fan in the first place. I don\'t like public content being made proprietary. And I think for Justin, all the reasons that he left are the exact reasons no one should be using amp in the first place.

\n\n\n\n

I think it\'s bad tech for band.

\n\n\n\n

David Bisset: It\'s a shame too. Cause I know some people that were, you had some people [00:17:00] for and against it, but in the end that I think that article combined with Sarah\'s excellent evaluation of it. Just really it\'s hard to get a lot of positive. Again, this is my opinion.

\n\n\n\n

This is not an opinion of anybody else. So that was my pick. I thought it was very thought provoking and it went beyond the WordPress industry. Ruba. What is your second we\'re in the second round pick? What\'s your second pick?

\n\n\n\n

Aurooba Ahmed: So I had a different second pick, but then something happened today that made me change my second pick.

\n\n\n\n

And that was frost being acquired by WP engine. So the reason I had to choose this as my pick is because as a developer and as a person who use WordPress a lot and seeing all these acquisitions happen, I am wary of acquisitions. I wonder how good these bigger companies are going to be as stewards of these plugins and where are they going to take it next?

\n\n\n\n

And when co when plugins and smaller companies get acquired, I tend to think, oh, okay, now this is going to [00:18:00] be more profit heavy, more money-making, less contribution, less being part of the community. But then WP engine did this thing where they acquired a commercial thing and they made it open source.

\n\n\n\n

And it reminded me that big company, big money doesn\'t have to mean only more profits and more sales. And in fact you can have big money that brings big contributions back to the community as well. If they choose to. And it made me look at WPS. In a more positive light. So I think that was a great marketing move on their end.

\n\n\n\n

David Bisset: In fact, I didn\'t have a chance to absorb it a lot, but I know they refunded. Everybody bought a copy, so yeah. Which in all honesty, no, I probably that was jumped, changed the engine, but I think that\'s a Goodwill, both there.

\n\n\n\n

Robert Jacobi: Who created frost again?

\n\n\n\n

David Bisset: Brian Gardner

\n\n\n\n

Robert Jacobi: and Diego. That\'s it. Where does where\'s Brian work [00:19:00] now

\n\n\n\n

Aurooba Ahmed: at WP engine?

\n\n\n\n

Jason Cosper: Where does Nick also work now

\n\n\n\n

David Bisset: WP engine.

\n\n\n\n

Daniel Schutzsmith: There\'s something to be said too, though, for Brian Garner has a formula down for doing this because before he had studio press, that also went to

\n\n\n\n

Robert Jacobi: WP engine. Oh, and PS. I love Brian Gardner he\'s. He\'s a local. WordPress supergroup because he\'s in the Chicago community. So that\'s amazing.

\n\n\n\n

But you know, I don\'t think it\'s an accident that frost followed Brian to WP engine. . If you know Brian up at some other place, frost may have wound up at that other place. That\'s all I\'m saying

\n\n\n\n

David Bisset: Frost isn\'t even a year old or is it, I think it\'s barely a year old or,

\n\n\n\n

Robert Jacobi: yeah, I I don\'t if it came out.

\n\n\n\n

Yeah. I thought it came out in 21. Yeah.

\n\n\n\n

David Bisset: Yeah. Okay. Well, good. That\'s another great acquisition picks. So new off the presses. So new and [00:20:00] still at time, Daniel. Let\'s see. What\'s your round two.

\n\n\n\n

Daniel Schutzsmith: Yeah, mine\'s more an editorial.

\n\n\n\n

David Bisset: Thank goodness. So,

\n\n\n\n

Daniel Schutzsmith: so this was Paul Lacey had done rather lengthy post about his stance on WordPress, how he was going to leave in the community for a little while.

\n\n\n\n

You know, I think he\'ll probably come back, but but it was also, you know, truly about his feeling of Gutenberg and the dichotomy between WordPress foundation and automatic and reflections on him, fishing with his father. I mean, it took you for a roller coaster and it\'s probably one of the most beautiful reads I had of the year in the WordPress space, which was really odd because usually we\'re talking about technology more than anything, and this was a little bit more human felt.

\n\n\n\n

So it, you know, in, you know, everyone should really take a look at it and he voices some really good concerns. You know, concerns of again, of, what\'s the role of different companies and what we\'re doing, what\'s their own Gutenberg and kind of pushing forward and how that\'s going to reflect, you know, making websites in the future.[00:21:00]

\n\n\n\n

And how do we bring people into the fold that might be having more difficulty with adopting Gutenberg or, traditionally want to be able to use page builders more often and feel like they\'re getting neglected or pushed out of the community? Personally aside, I mean, I think page builders are here to stay.

\n\n\n\n

I don\'t think it\'s a, this or that. I think it\'s just an added additional kind of quality aspect that people can use, you know, to use an element or use you know, ocean\'s WP or something like that or oxygen. But it was a really good article and it spread like wildfire through the community.

\n\n\n\n

So you actually saw a lot of people doing blog posts or other posts that were reflecting similar things and, you know, referring back to the specific posts they\'re over on the WP minute.

\n\n\n\n

David Bisset: Okay. Great pick. Yeah. And that\'s why we have the people we have here tonight, because I didn\'t, I w I was hoping to get diverse collection of articles and not just a name, as many acquisitions as we can in the next hour.

\n\n\n\n

So, but yeah, it\'s the heart of, and if it impacts you in a heart impacted a [00:22:00] lot of people emotionally, then that\'s definitely a good pick. So, Jason, what\'s your outreach around to here? Yeah.

\n\n\n\n

Jason Cosper: I\'m maybe gonna pull a Babe Ruth pointed the bleachers and call the shot that round two is going to be pretty Gutenberg heavy because my second pick is a theme dot Jason shipping with WordPress five point eight.

\n\n\n\n

I think this is a really a huge deal for folks. I know that you\'re kind of when it comes to custom CSS and stuff like that you can either wear in CSS or json it\'s not really necessarily the easiest switch to make. Like if you present somebody who is a little less experienced with code however I just think that the impact of this or the amount of things that it can control with blocks is going to be massive.

\n\n\n\n

And the next few versions of WordPress when five nine finally drops when you know, as [00:23:00] things mature. I just think that theme json really is going to make a huge impact on how themes are built, how child themes are belts, how like all of that basically

\n\n\n\n

David Bisset: Who\'s doing the theme. I know that more than one person is doing it, but who\'s is David. Somebody is doing the theme .Json generator. Has anybody seen that? Yep. Yeah. David, what\'s the last name I keep forgetting. Yeah. I mean, it\'s looking pretty good, remember when. We had themes and then the underscore generator came out and there was another generator whose name escapes my mind right now, but it seems once we get these generators going, things accelerate.

\n\n\n\n

But I think that\'s a really great pick because obviously theme .json is something that can be turned into a builder or tool or a companion there\'s so much you can do because Jason\'s practically human readable. That\'s the point of it. So I think that\'s, yeah, I think that\'s an excellent technological we\'ll, we\'ll look back in a couple of years and say, is it, you know, if we [00:24:00] have a thousand themes or variations, is it because of the theme .json and I would venture a guess.

\n\n\n\n

It\'s going to have a heck of a lot to do with it. So that\'s an excellent.

\n\n\n\n

Daniel Schutzsmith: And it\'s also setting itself up for good expansion in the future, too, of what the capabilities will be

\n\n\n\n

like.

\n\n\n\n

David Bisset: So it could have been hopefully extensibility. Yeah, because it could have been that could have gone a different way and not a easily readable editable, text file kind of way either.

\n\n\n\n

So in fact, there\'s probably some things in Gutenberg that are, you know, that you have to know some deep knowledge on that. I wish they could just make it like that magically somehow as easy as adding a file. So. Excellent. Excellent pick. Okay, Robert, you\'re up. What\'s your round number two pick.

\n\n\n\n

Robert Jacobi: I\'m going with the, I want to extend the extensibility with open verse.

\n\n\n\n

Welcome to the open verse. Now we\'re not adding just the code. We\'re extending all the media that comes in contact with work. And the acquisition [00:25:00] technically by automatic of CC search. I think part of the state Matt\'s state of the word is going to insanely impact what every single, you know, day-to-day user can do with audio video and who knows what else will wind up in the open verse?

\n\n\n\n

David Bisset: Okay. So what is the difference between for our listeners and for maybe me, but our listeners? What is the difference between open verse and wordpress.org/photos?

\n\n\n\n

Robert Jacobi: wordpress.org/photos will be a curated, subset of open verse. As I understand it from the state of the word and that\'ll, you know, have audio and video at some point, but let\'s not say it\'s going to be tomorrow.

\n\n\n\n

So that\'ll be. Family-friendly the open-source friendly, the community friendly version of what open verse is because open verse will probably encapsulate a lot more content than probably wp.org can. [00:26:00]

\n\n\n\n

David Bisset: Well, yeah, it\'s spot from creative comments. Right? So creative commons looks like they didn\'t have the support financially or structurally to be able to have that library automatic acquired it, brought it into the open source.

\n\n\n\n

Robert Jacobi: Correct. So the library technically still exists. The creative comments, it\'s the whole search engine and all the infrastructure around that, because that\'s the hard part. Right. I could have a billion photo albums that are creative commons license zero. But if you can\'t find the folder, you\'re looking for, if you\'re looking for that flower or that bird, you know, you can\'t find it unless there\'s a tool to do it.

\n\n\n\n

And that\'s the one that takes all the you know, the hit on performance. Yeah, just getting stuff done. So, I mean, that\'s the bigger deal at the end of the day. And I think that\'s where they were creative commons was having problems running that on a day-to-day basis. And you know, I\'m going to give automatic and frankly, Matt kudos for that.

\n\n\n\n

I mean, I think that really changes the conversation [00:27:00] about what open source means. Now it\'s not a geeky code thing, like GPL this GPL that now it\'s like, oh, I can put up a website and I can click the photos button and I\'m not going to get sued for, you know, this picture of a walrus.

\n\n\n\n

Aurooba Ahmed: Keep in mind that creative con open verse still has non CC zero images as well.

\n\n\n\n

That\'s the difference between slash photos and open verse because the one on photos will only have

\n\n\n\n

Robert Jacobi: CTCs. Exactly. Thanks so much Aruba. Yup. Yup. I mean, that\'s a huge difference. So yeah, on the open verse side, Deal with the licensing voodoo, whereas photos that\'s done, you can use it. Commercial pers personal edit, no attribution, whatever.

\n\n\n\n

Yeah. You can do whatever you want with it. So it\'s become the free version of of Getty for all intensive purposes. Oh,

\n\n\n\n

David Bisset: and we all know how the, how another site that rhymes with bee splash started that. And Matt likes to, [00:28:00]

\n\n\n\n

Robert Jacobi: the good part is it\'s not being called WP slash

\n\n\n\n

David Bisset: Unsplash.

\n\n\n\n

Robert Jacobi: I trust Matt and automatic with what he said, state of the word, you know, about making sure open is open

\n\n\n\n

David Bisset: and automatic had to be involved because they\'re the ones with the money in the infrastructure.

\n\n\n\n

So automated the actual acquisition. And I think they had to, because it\'s not, it can\'t be just mad. It has to be in it. It needs to be a company privately.

\n\n\n\n

Robert Jacobi: Well, there is a WordPress foundation, but they don\'t have the money to acquire anything.

\n\n\n\n

David Bisset: Then you\'re starting to get into, there\'s probably reasons why legally and why it did, why I did what I had to do, but I\'m just glad it\'s back the word they just said it was contributing it back to the, you know, they use the words contributing back to the open source project.

\n\n\n\n

I mean, for all intents and purposes, I like you, I trust Matt and I trust them that the fact is they\'re not trying to make a buck off of this. They\'re not trying to take what Getty did with that certain website and turn it into something it wasn\'t originally intended for.

\n\n\n\n

Robert Jacobi: Oh no, everyone\'s going to make a buck out of this.

\n\n\n\n

This is the best part about of [00:29:00] even photos. It\'s the fact that any one can integrate this. It\'s Matt said it stated the word. It is open. It\'s an open API. Wix can use this.

\n\n\n\n

David Bisset: Careful. We can only say that three times.

\n\n\n\n

Robert Jacobi: What if I use the alternative, if I say Squarespace and Weebly.

\n\n\n\n

David Bisset: Oh crap. There, it goes two more.

\n\n\n\n

No, but you\'re right. Anybody can use, and they are the ones, but it\'s not it\'s like creative commons, like you said, they can do anything with it. They\'re just ones to maintaining the database. So I can\'t wait to see what like with apple, I can\'t wait to see what your, what you\'ll do with it.

\n\n\n\n

And I just feel the only thing I don\'t like about open versus that it sounds like something else, but Matt Mullenweg thought of the name probably before mark Zuckerberg did announced it anyway.

\n\n\n\n

So anyway, Leslie let\'s get to your number two pick. We\'ve got some great choices here. I have you been sniped.

\n\n\n\n

Lesley Sim: I have not I feel like I actually picked my picks to avoid being sniped. So I hope

\n\n\n\n

David Bisset: your\'e so [00:30:00] smug, I like that, it\'s going to be easier to take you down next round.

\n\n\n\n

Lesley Sim: So my next pick is a podcast. It\'s called the founder\'s field guide and they interview met Mellon wig. The host is Patrick O\'Shaughnessy. And it\'s it\'s just I\'m not sure how many, sorry. I\'m like flipping between zoom and the sites. I don\'t know if any of you listen to the podcast, but it\'s super cool.

\n\n\n\n

And it talks. So, basically it\'s an hour long interview and we learn about Matt\'s kind of approach to WordPress. And, you know, he\'s talked a lot about this in the past, but it was nice to just kind of hear it in one hour long podcast. He talks about one day to work on WordPress for the rest of his life and his approach to making WordPress the open source platform or operating platform that also happens to be open source for the web and how he sees, you know, kind of the law [00:31:00] of platforms being.

\n\n\n\n

As a company that\'s building a platform, you can only profit 5% off of the platform being built. And that\'s kind of like a good gauge of a thriving platform. So he uses Microsoft as an example, like he says that Microsoft benefits 5% and the platform that they built, you know, everyone else that builds on top of it gets the 95% yeah.

\n\n\n\n

Profit. And I thought that was a really cool approach. I never heard him talk about that before and that, and you know, it really kind of expands your mind in terms of what he thinks is possible and what he wants, you know, like it\'s not going to be a cash grab, you know, at the end of the day, which and that kind of, I guess, leads into what he\'s doing with open verse and what we just talked about.

\n\n\n\n

It really, you know, Makes you feel like you can trust the future of WordPress because he\'s trying to build it towards this 5%. I\'m trying not to like [00:32:00] add into many different you know, the salsas as well, because then I\'m going to accidentally snake other people. But you know, he\'s always talking about avoiding the tragedy of the comments and he\'s always talking about Firefox for the future and how you know, he wants more people to contribute.

\n\n\n\n

And I think understanding that this is kind of where he\'s coming from, like wanting work has to be a platform I want to only ever have take 5% of the profit of the platform. I think that\'s like, yeah, just like a really good once you understand that you can make a lot of business decisions from there and be comfortable in those decisions.

\n\n\n\n

David Bisset: Didn\'t he say and say to the word that ratio is that 5% ratio is how five of the future was five. I got that. I- if we accidentally sniped someone\'s specific article on that specific mention of the ratio, then I guess we\'ve done that. But, there\'s, if somebody still has something to share for five for the future I\'ll I\'ll hear it, but that\'s yeah.

\n\n\n\n

I think that\'s a great pick two and I haven\'t [00:33:00] had a chance to listen to the podcast, man. To do now, if everybody\'s comfortable with it, I\'d like to go through one more quick round, which means share your pick and maybe give a minute explanation.

\n\n\n\n

And then once we go through that, we\'re basically we\'re basically at that point going to just share real quickly in a fourth round, just basically throwing out. At that point, you don\'t need to explain them. They were just going to blow through it. So we\'re going ever perpetually faster toward the singularity rubella.

\n\n\n\n

You\'re up next? What is, what quick now is your third and third pick and real quick, why?

\n\n\n\n

Aurooba Ahmed: Oh, okay. This is not from a news place, but it\'s something that made a really big impact on me. I\'m going to post this. It\'s a Twitter thread by Nicole Sullivan, where she\'s talking about how she doesn\'t want to be erased when talking about a utility classes and you know, tailwind, for example, is like a library of utility classes.

\n\n\n\n

And it made me think about in our own community and we\'re press who we choose to [00:34:00] amplify who are the kinds of people that we choose to listen to and share more from and how that impacts. What we understand about the kind of work everyone\'s doing. So for example, Nicole is talking about this because people were asking, Hey, who started this whole trend?

\n\n\n\n

And people are playing to all these men. And it\'s like, hi, I was doing this before the men, but nobody went, nobody\'s sharing that because lots of people chose to amplify the men and not the women doesn\'t mean the women aren\'t doing good work. It means that they\'re just not being amplified. It made me think a lot about like, there was a thread also on Twitter about, Hey, who are all the people like involved in all of these acquisitions?

\n\n\n\n

I don\'t remember who put out this post Leslie matting but it was like all men. It\'s like, you know, there\'s women involved in this situation too. Let\'s talk about and be more mindful of who we\'re thinking of and who we\'re involving and sharing about. And that\'s you know, it\'s a topic close to [00:35:00] heart.

\n\n\n\n

Cool.

\n\n\n\n

David Bisset: So two things first you gave out a Twitter thread. I did not think of that. I\'m we\'re going to go for it. It\'s it\'s I think Twitter is news it\'s okay. Twitter is news. And second of all, I forgot about me. I skipped myself. So real quick, remember I was at the world with that,

\n\n\n\n

Robert Jacobi: Dave. We\'re all good.

\n\n\n\n

David Bisset: Yes. But like my wife, you still have to endure me so real quick.

\n\n\n\n

I\'m just going backwards a little bit. I actually have a brand new pick that actually has been ma it\'s only been online since December 21st. So it\'s only been online for two days and it actually took an acquisition. I had an acquisition pick ready, but it\'s moved it down in terms of it\'s. It\'s a thought piece.

\n\n\n\n

It\'s actually, I think it\'s a thought piece. Cause I don\'t he did talk with Matt, but it\'s not an interview. It is from protocol written by David Pierce called, and this has a click baity title, but it\'s the only thing that I didn\'t like about the article. It was. Can Matt Mullenweg [00:36:00] save the internet?

\n\n\n\n

I think it\'s a really catchy I can see now probably the more I get into it, like sometimes writers don\'t get to pick their titles. Sometimes the editors or whatever\'s do. I thought it was a little click baity. Dan David responded by Twitter. He says, yeah, that\'s I, you know, I\'ll take that judgment then that\'s fine.

\n\n\n\n

But as you go through that, this is not just another profile on Matt Mullenweg. At least I don\'t think so. The more I get into it, it is about, it does start in the beginnings where Matt was a young guy, they have a photo of him. He did upgrade parties instead of whatever kids his age were doing at that time.

\n\n\n\n

And which I thought was really cool, but it really kind of lays the impression that, you know, we\'re in this phase right now of such closed walled gardens from Google, from Apple, from Microsoft, from all the big players, right. And even the stuff that is coming up front of all the web three technologies and the promises of that being open and ownership, there\'s still some controversy in that regarding how that\'s going.

\n\n\n\n

I didn\'t, you know, once you realize [00:37:00] that automatic has been buying, basically one of everything it\'s been acquiring it, I\'m going to forget some names here because I\'m being put on. I didn\'t put, I put myself on the spot, but it\'s acquired that journal app. It is a quiet. Yep. It has. We talked about already how the creative comments things was basically acquired slowly, but surely it seems like Matt through automatic is acquiring one, like one piece of something that should always remain open source from various different kinds of categories.

\n\n\n\n

I\'m trying to remember, there\'s an analytics. If you go to poststatus.com/acquisition, she could probably just look at the automatic parsley. Yeah. So that\'s an acquisition type of fleet. So it looks like he, if you look at it and this article mentions that, but it hides it in like a history and talks about Matt and how he uses WordPress and how he will continue to use WordPress for his full-time career, or at least that\'s how he hopes.

\n\n\n\n

But once you start reading this, you begin to realize what, and I [00:38:00] think Matt\'s state of the word kind of hinted that more this year than any other year, In terms of where WordPress is like Gutenberg, he says going to be bigger than he considers Gutenberg bigger than WordPress. Not just because it\'s a product, but because of the openness at other people can use it.

\n\n\n\n

Gutenberg in of itself is in my mind. Now I\'m thinking of it more like a parsley or more day one is a day one, the app I\'m thinking of, it\'s another piece of this family of products that kind of cover what you would want to maintain an open presence on the web. Maybe social network is one thing that it hasn\'t been touched yet maybe, but I think maybe wordpress.org could be that too.

\n\n\n\n

Who knows? But if you, so anyway, that was my more lengthier number to pick. I think that if you give it a good and fair read sometimes articles really put Matt on a pedestal in terms of things. But I think if you take a step back and realize the and tumbler too. Yes. Somebody mentioned tumbler.

\n\n\n\n

Yes. That\'s a big one too. And we may not see all of the pieces right away, but once you read this and appreciate the acquisitions automatic [00:39:00] has been doing, I think it starts to give you at least a little bit of a different perspective. And that\'s why I liked it. It wasn\'t just another interview piece about Matt.

\n\n\n\n

It was really well done. So anyway, that was my number two, epic. Sorry I got skipped. Daniel, what\'s your quickie number three? Oh, God, don\'t get it. Don\'t take that out of context either. All right, thanks. Sorry, go ahead.

\n\n\n\n

Daniel Schutzsmith: I gotta tell you, you\'re making me nervous. I\'m sweating bullets over here.

\n\n\n\n

Cause he just started rattling off all the different acquisitions. Oh no, we got a good one. I think I got a good one.

\n\n\n\n

David Bisset: You can mention some

\n\n\n\n

Daniel Schutzsmith: pocket casts being acquired by automatic. To me, this was a pretty big one. This was actually on the nine to five Mac blog slash easing. That\'s just, you know, podcasts is a great podcast application kind of a competitor to apple podcasts and things like that.

\n\n\n\n

So, you know, that\'s literally what I listen to on my podcast, but but they have a nice web interface to which most don\'t have. And so that\'s really, you know, been a key thing for me, being able to kind of listen to those while I\'m working and during the day.

\n\n\n\n

David Bisset: Okay. Yeah. And that\'s another thing.

\n\n\n\n

Yeah, [00:40:00] like you said, that\'s just adding to all these, like the article I was previously talking about. Yeah. That even adds even more to it. Robert, which. At this point,

\n\n\n\n

Robert Jacobi: Mr. Cassper is ahead of me.

\n\n\n\n

David Bisset: Oh, I\'m sorry. I\'m sorry. Jason, do you switched zoom? I had my zoom windows set appropriately. Go ahead, sir. I mean,

\n\n\n\n

Jason Cosper: I had to mute my video for a second to get my standout and on my apple watch.

\n\n\n\n

David Bisset: I\'m very sorry. Oh God, we\'re going through hell right now, sir, but what\'s your quickie?

\n\n\n\n

Jason Cosper: So yeah the quick one I have is Google\'s flock and the federated learning of cohorts. Yeah. So, flock was a fairly large thing back in. I wanna say April may that had the electronic frontier foundation up in arms, a lot of privacy advocates up in arms.

\n\n\n\n

Basically like we\'re replacing cookies with this like federated learning cohorts. There\'ve been a few other proposals as well. But [00:41:00] the interesting and the WordPress spin on this is that there was a post up on the make blog about basically like, Hey, let\'s treat flock. Like it\'s a security concern.

\n\n\n\n

We, we don\'t want people who visit our sites to be tracked. So, it seems like Google took its foot off the gas a little bit in part because of large projects like WordPress saying, Hey, hold

\n\n\n\n

David Bisset: up. Yeah. And WordPress, I mean, that decision is not made by one person. Right. So Google would have, or at least Google views that as a decision made by a committee or a party or the project or the contributors.

\n\n\n\n

So it\'s kind of hard to predict if that will go through. It\'s kind of hard to push that through. Right. So, yeah, I think that\'s an XII I\'ve actually forgotten about that. I forgotten about flock. How can I forget such an acronym? It was a long year it\'s. Okay, man. I had some flock last night with my chicken was delicious, but to Google\'s flux just [00:42:00] doesn\'t need to go.

\n\n\n\n

Robert, what is your, what\'s your quickie three.

\n\n\n\n

Robert Jacobi: Gosh. I\'m so like jealous of Jason\'s pick for flock. I even wrote about this in April and I, how did I miss that one? I called it flock. Is cash a centralized analytics of segmented humans because that\'s really what it was. It was just another, no, I gotta write that

\n\n\n\n

David Bisset: down.

\n\n\n\n

Robert Jacobi: My number three is. It\'s technically not a WordPress thing. Oh, that\'s a loud, I\'m gonna, you know, upset the apple cart. I want to talk about the American airlines lawsuit of open source matters and an associated hosting company open source matters is the holding company for JeWella. As we know from the state of the word, the second largest, and really the only other top five content management system [00:43:00] you know, that\'s being really utilized out there.

\n\n\n\n

American airlines ha earlier this year, sued open source matters because someone slash someone, created a fishing site with a joomla.com name. Because that was being light. You know, it gets an all into all that.

\n\n\n\n

David Bisset: Am I drawing a blank on this? Oh my goodness.

\n\n\n\n

Robert Jacobi: Oh, that\'s, you know, draw, it happens, you know, the WordPress space, but

\n\n\n\n

David Bisset: my medication, it\'s not a hundred percent,

\n\n\n\n

Robert Jacobi: but this is a big deal actually, because this will impact how, you know, I think at the end of the day, what happens when you license a domain name to a third party to utilize for revenue or whatever, and this is where this comes to.

\n\n\n\n

So yeah, this happened the lawsuit was announced in August of this year, but actually I think some of the nitty-gritty was happening much earlier.

\n\n\n\n

David Bisset: Wow. That\'s an, oh, well, I\'ll be reading this right [00:44:00] afterwards. This is news. If I saw this man, I went right by it. This is pretty, very good pick. Very good pick.

\n\n\n\n

Robert Jacobi: Well, I\'ll be doing a deep dive of it next week.

\n\n\n\n

David Bisset: Okay. Well, come up for air. Let me know when you come up for air, let\'s save Leslie. You\'re at the bottom of the three here bef before me anyway, what\'s your third quickie. I got to stop saying that.

\n\n\n\n

Lesley Sim: My pick is broadly the introduction of the F S E outreach program that started this year. I think it was talked about last year, but it started for reals this year. And yeah, and McCarthy\'s been doing an amazing job. One of the things that I find constantly interesting and maybe a tiny bit irritating is how many millions of people use WordPress, but like, think of WordPress as something that happens to them, like

\n\n\n\n

David Bisset: a traffic accident?

\n\n\n\n

Lesley Sim: Like, you know, like when Gutenberg comes up and they\'re like, oh, I hit it.

\n\n\n\n

You know, this [00:45:00] sucks and all that. Right. But like it\'s open source so everyone can have their say even, I mean, I get the people who have their essay and then get ignored. But the people who just kind of sit back and just wait for Gutenberg to happen to them or for stuff to happen to them. I\'m not such a fan of that.

\n\n\n\n

And so I like the FSE outreach program because it kind of goes out and tries to get people involved. It does a much better job at communicating the things that are happening next. It encourages people to do testing, like the amount of times I\'ve seen and kind of reach out to different people in different platforms.

\n\n\n\n

Just trying to get someone, anyone to come and test the next video. This is like, I don\'t ever want to do her job. And I\'m always constantly surprised by how few people come and help tests. I think 10, definitely under 20 people is the kind of typical number which is, [00:46:00] it said right. So, so hopefully, you know, me talking about this gets more people interested in going to do it.

\n\n\n\n

But yeah it\'s a cool thing. I like Alex seeing the livestream she\'s been doing and like, seeing it, like she puts out the first time I tried to do on the tests following all the instructions was it was tough. Like I realized it wasn\'t actually that easy to test. And I think like that\'s gotten better over time as well.

\n\n\n\n

And yeah, so it\'s just kind of a cool project that I hope to see it continue next year as well.

\n\n\n\n

David Bisset: Great. Well, I agree. I, like I said, I\'d like to see more testing as well. So my third quickie pick is actually an acquisition one. Very quick. It was basically Awesome Motive acquired

\n\n\n\n

sorry, dribble. I\'m sorry. Do a blank. I wanted to make sure I got this right. It got easy digital downloads some out of acquired WP, simple pay affiliate WP. And it basically grabbed all those assets and I\'m dropping the actual article is from DVB beginner, but there\'s also another article. A few there\'s few people covered this as well, but [00:47:00] I thought it was just if I had to pick one acquisition, I think this was the biggest one.

\n\n\n\n

I think Sand Hills development, I know was another with bread not on Pippin, sorry. With Pippin basically short term retiring and or another old school, one there all of those products going to automotive I thought was probably the biggest shift. If I had to pick one acquisition that had a big shift, that would be definitely in my top three.

\n\n\n\n

Somebody already picked one and somebody probably will also pick the other one I have in mind too. So, yeah, a lot of products underneath one, one company. I thought that was significant on multiple levels, which I won\'t have time to go into. So that was my third round pick. Now comes our last round, which has been called by other podcasts and I\'ll stick with it and see if it sticks for our first round here, it\'s called the, bring out your dead round, where we are not going to give any explanations.

\n\n\n\n

Just simply read what you have left and let us know if anybody, if including, if you got sniped by anybody else, if you haven\'t mentioned already Ruba, what have you got left [00:48:00] real quick listed out for us.

\n\n\n\n

Aurooba Ahmed: I got a snipe when you talked about Pippin retiring. The other thing I had was MailChimp\'s sail and the public draft release of cascade layers, which is going to be really big in CSS.

\n\n\n\n

The gravity forms 2.5 release, which was, and ECF being acquired by delicious brains and the element tours, pricing update.

\n\n\n\n

David Bisset: Oh, yeah, you got lots of good ones in there. I can\'t pick just one to critique on Daniel. What is your-

\n\n\n\n

Robert Jacobi: element or cloud or whatever they\'re calling it today.

\n\n\n\n

Daniel Schutzsmith: Let\'s see. I got sniped on the protocol article about Matt. Also got sniped on the uh amped thing there. The ones I had left were let me just bring it up. Yeah. Oh, I got snapped on the frost one too. That\'s right. And the man I got,

\n\n\n\n

David Bisset: you got sniped a lot for being somebody who was number two on the list.

\n\n\n\n

Daniel Schutzsmith: I do have a good one here though, which was our future together at post status, which was coordinator\'s post about taking over post status. And I had just joined Post Status, I think maybe a month before that. [00:49:00] And so that was a pretty transitional thing for me.

\n\n\n\n

David Bisset: Right. Pretty good. Yeah. That obviously had impact for me for me as well.

\n\n\n\n

That seemed like so long ago, but a yes, at the beginning of this year, Brian Cross guard was still owner of Post Status. So, Jason, I have, I think you\'re up next.

\n\n\n\n

Jason Cosper: That\'s correct. Yeah. So, let\'s just get through my small handful of other articles automatic acquiring frontier. And having their founders working full-time on Gutenberg, like, Hey fantasy, like, you know, you\'re a cool looking project, but get out of here.

\n\n\n\n

We need you for Gutenberg.

\n\n\n\n

David Bisset: Yeah. They gave up their rest. They gave up what they were working on to the open source community, which basically means this is your problem then.

\n\n\n\n

Jason Cosper: Yeah. It dead.

\n\n\n\n

David Bisset: Well, I\'m not going to say dead. Well, I mean, they gave it up to the open source community. It\'s kind of like leaving food out for the bears.

\n\n\n\n

It\'s like, just don\'t look back and you\'ll just pretend the bears had a. [00:50:00]

\n\n\n\n

Jason Cosper: Well, I guess to keep in the theme with the, bring out your dead it\'s, I\'m not dead yet.

\n\n\n\n

Aurooba Ahmed: It\'s just a fresh of stewards and they\'re gone and there\'s no transitioning team. It\'s dead.

\n\n\n\n

Jason Cosper: So, also dropping support for internet Explorer 11 that happened this year.

\n\n\n\n

Wow. Yeah. Out of self-interest WP, watercooler turned nine years old this year. 400 episodes. You know, we\'ve been at it for awhile. I came along within the past, like four or five years. So I\'ve only been a row along for part of that ride, but you know, it\'s just you run into a lot of WordPress podcasts that don\'t stick around that maybe only put out like 10 or 20 episodes

\n\n\n\n

David Bisset: or 300 episodes is only that much, but yeah.

\n\n\n\n

Right.

\n\n\n\n

Jason Cosper: And the last one, a weird pick Matt Mullenweg backing open insulin open source insulin back in July. And he kind of, put his money behind [00:51:00] that. And I think that is, I mean, it\'s not necessarily a WordPress thing for the people who are in the WordPress community affected by type one diabetes.

\n\n\n\n

It\'s a huge thing. But just the fact that he did that I thought was super cool.

\n\n\n\n

David Bisset: Yeah. I think I remember hearing about that, but yeah I, it just, so went along with Matt personality and his view of the open web, that it wasn\'t a surprise when I heard about it, even if it wasn\'t WordPress related, but it is so nice to hear something when it comes to man, and it\'s not WordPress related because sometimes that\'s rare when it comes to our radar.

\n\n\n\n

Robert bring out your dead.

\n\n\n\n

Robert Jacobi: I\'m going to lead with open source is broken by Christine. Daughdrill this, I liken the shaking the up and down nods of approval on this one. It I\'ve been in the open source space for almost 20 years. And I know that open [00:52:00] source contributors are treated less than dirt until something completely explodes, cough log for J.

\n\n\n\n

Then the folks all like four of them who are supporting this thing for free get yelled at for destroying the internet for like three days. And that\'s ridiculous. What is the, you know, the mindset of, you know, folks who have worked their tails off to make this stuff. And yeah, it\'s their fault because no one wants to pay them to make sure that, you know, there\'s, you know, syntax error somewhere keeps running.

\n\n\n\n

Yeah. So look at it, look at our lives, everyone here, certainly on this calls. And certainly everyone listening to this is wholly dependent on a million billion pieces of code written by [00:53:00] folks who did it for fun for dinner, for, you know, testing the bounds of tech trying to solve a bigger puzzle, WordPress Linux, Apache, DNS, every, I mean, we could go on and on.

\n\n\n\n

And the support for these communities is crap and yeah, that, you know, that\'s going to be. Whether it\'s the it\'s a story that no one cares about because if they cared about they\'d already paying into it. So yeah. Support your open source project. Yeah, I like it. Cause it runs every minute of your day.

\n\n\n\n

David Bisset: I got, when I tweeted something, once it was about like a company saying we have, we make tons of money off open source. We linked to support the open source community and the open source community says pay us. And the company says, but not like that. I like that.

\n\n\n\n

Robert Jacobi: Yeah. I mean that, that\'s the problem.

\n\n\n\n

David Bisset: All right.

\n\n\n\n

Well, very good. We\'ll just, I\'ll put a pour one out for the open source contributors tonight, ladies and gentlemen, [00:54:00] as we move to our final. Leslie, what\'s your bring out your deads or mostly dead.

\n\n\n\n

Lesley Sim: So I\'m going to piggyback on what Robert just talked about. So one of my picks is Nadia. I\'m going to pronounce her last name, wrong her book called working in public, the making and maintenance of open source software.

\n\n\n\n

I think that might have come out last year, but let\'s pretend the chemo this year.

\n\n\n\n

Yeah. So it\'s kind of, the same as what Robert talked about. It looks into open source, how it\'s all structured, the, you know, tiny bits of code that, that run so much of our platforms today. And interestingly, it talks also about the communities that maintain it and how different open source projects have different, have evolved to have different styles.

\n\n\n\n

So for example, some. Some [00:55:00] maintainers like to be contacted on Twitter, for example, and others such as WordPress express, the city don\'t ever contact us on Twitter because that\'s not how we\'re able to communicate. And it just talks to about the size and the scale and the scope of open source projects and how they\'re all so different.

\n\n\n\n

And it, it kind of actually sent us around, get hub and talks also about how much get hub has changed, how open source is run and operated any team these days. So yeah, a really good book. How do you recommend it? So that\'s one of my picks and I\'d quickly just go through the other two. The next one is Wix.

\n\n\n\n

David Bisset: The second one here, second mention. The

\n\n\n\n

Lesley Sim: WP Tevin article title is “Wix takes a jab at WordPress with bewildering new marketing campaign,”.

\n\n\n\n

David Bisset: I got you. Snake me, sniped him. One of my, when my, my, one of my dead ones here.

\n\n\n\n

Lesley Sim: Yeah. So wix going taking a snipe at [00:56:00] WordPress. It\'s those army headphones though in know a bunch of people who\'ve got them and we were just really confused.

\n\n\n\n

And the last pick that I had was the white house. So I\'m not American, but the white house.gov website being rebuilt in like crazy short amount of time maybe a month and completely rebuilt going from Jupiter back to WordPress and being built in Gutenberg, which I thought was really cool.

\n\n\n\n

So yeah, those are my picks.

\n\n\n\n

David Bisset: Yeah. And Helen actually gave a pretty good presentation of how all that went down during the word camp Europe know WordCamp US a couple of months ago she gave the full story. Well, as much as she can reveal, and the fact that they turned it around that fast was mind-boggling. That was also a snipe.

\n\n\n\n

You, you pretty much slept the rest of my dad. Leslie there I had white house runs on WordPress. I also had things like proposed WordPress performance team gets Greenlight that was also taken I had the Wix one as [00:57:00] well, the marketing campaign. How could you forget that? I think the only one I have left that wasn\'t touched by anybody here is the WordPress economy drives more than half a trillion revenue, which was a report reported, or it was a report authored by WP engine.

\n\n\n\n

And since our WordPress market share Alexa is being not the Alexa the device, but Alexa company, they supply the numbers for w three texts, market share numbers, which is where we get all of our 43%, 40%, were a little over 43% right now that shuts down in may. So if that shuts down, our ability for that market share number is going to be, I don\'t know if anything will take its place, but in my opinion, relying on the market share number, especially when it\'s going to stop.

\n\n\n\n

Eventually at some point it\'s not a good way to, it\'s not a good, real quick way to tell WordPress is a success in terms of growth, in terms of all of this, we ha we relied on that number because of as easy. And, but I think what we should start doing now is looking at other places [00:58:00] to determine the strength of a WordPress the community and all of that.

\n\n\n\n

And one of it is money. I thought this article really kind of, it was the first time I\'ve think I\'ve seen half a trillion in revenue in terms of the entire WordPress space, not just somebody like Automattic is we\'re 7.4. Or some which also I think was news this year. So I thought that was a pretty critical article that other people now can start to build off of and, or add to their collection of how they can tell how the WordPress ecosystem is moving along because market share, it was kind of a poor metric to begin with.

\n\n\n\n

And it\'s, you know, the closer you get, the higher you go up, whether we\'re presses growth slows or not in terms of market share, it\'s kind of like the iPhone market share doubled every year. You know, I phoned for so more than all the I-phones previous years put together iPhone five, the same thing, but eventually that iPhone market share slowed.

\n\n\n\n

But it\'s still making record profits. It\'s still doing all of these wonderful things today. And I think that\'s where the WordPress economy [00:59:00] is going to be. You won\'t see that market share number, go up, even if we have a market share number, but you\'re going to see all these other factors. And that\'s why I think the.

\n\n\n\n

Article from WP engine is a good article to start thinking like that. Well, that was fantastic. Thank you everybody. I I think we had a very wonderful, diverse set. Some surprises, some things I never even read before. Let me see if I can look in slack right now. This may be Barra, edit something out.

\n\n\n\n

Okay. So if you can go ahead right now and just paste the, I only need the top three. I\'ll get the others later. If you haven\'t put your top three in slack, just all you need to do is just drop the link. I\'ll be able to figure it out from there. And then what I\'ll do is I\'ll go through everyone, read it off, and then we\'ll be done.

\n\n\n\n

Since I\'m editing this part out anyway, and I\'m waiting for Jason and Daniel, you put it in there. So we\'re rating waiting on Robert. Leslie. Ruba needs to just update slack real quick. This podcast episode will probably be out next [01:00:00] week. It\'s hard to say near the end of the year, cause we have a lot of end of year stuff going on, but I\'ll let you know about that.

\n\n\n\n

I need a picture from every one of you at some point in the next couple of days to put in graphics for promotion for this. And I\'ll try to keep you updated in terms of anything else I might need from you. But I think that\'s basically it because we should have all the links in slack. I can order them and all of that.

\n\n\n\n

If this goes well, we were hoping to get a second episode out of this with some other people who couldn\'t make it for this time zone too, but you are the first congratulations, no longer a draft versions, as they say, well, I should probably shouldn\'t use that word. Okay. Strike it. New word, newbs noobs.

\n\n\n\n

There we go. This is why I have, this is why I have producers. They have poo-pooed my ideas so often. And I didn\'t really, I didn\'t say poopoo in the beginning, but they told me to say that word instead. I\'m calling

\n\n\n\n

Robert Jacobi: Corey right now.

\n\n\n\n

David Bisset: Oh, you can come, please. It probably thinks of

\n\n\n\n

Daniel Schutzsmith: you. Oh, also too. If you want to spice [01:01:00] up the podcast, you should throw in some more combat stuff like bonus round

\n\n\n\n

David Bisset: finish. Well, that\'s why you, we should deal with the end. We should just finish it. Alright. Let\'s see what we got. All right. Jeff is still alive that he\'s only in slack. We should\'ve just brought him on. He could have just listened. All right. So here we go. Running through the top three here. Ruba.

\n\n\n\n

Yours is up there we go. Yours was the WordPress 5.9 release. It was frost being acquired and made open source and stubborn Nella utilities classes, Twitter thread. That was your three picks. Excellent picks. Daniel, your picks were you w the WP user avatar tobacco with profile press.

\n\n\n\n

That was how Gutenberg has divided WordPress. That\'s what the article was titled. Remind me of the author again on that.

\n\n\n\n

Robert Jacobi: Let

\n\n\n\n

Daniel Schutzsmith: me see. I

\n\n\n\n

David Bisset: don\'t remember. It\'s a long night. I\'ll edit this. Hopefully [01:02:00] don\'t worry. It\'s from the WP minute. I\'m just remembering who policy. Okay. Thank you very much. He deserves the credit and then finally podcast app podcast acquired by automatic again, another great one of those. Acquisitions that you may not have thought of at first in 2021, but I think definitely fits into a grand scheme of things.

\n\n\n\n

Let\'s see Jason, your top three, the WordPress performance team. That was an excellent one. The theme digests on another great one with 5.8 and Google\'s flock and WordPress they\'re pretty good. Solid picks. Robert yours were the Yoast joins the new phone, digital acquisition, the open verse announcement and the American airlines, Susan sues online publisher and host over fake website involving Joomla, which is something I\'ll be reading right after this.

\n\n\n\n

And Leslie you\'re top three was the marketing machine blog post from the get elliptics.com. It was the the article about the past, the present of the future with Matt mullenweg\'s. And that was from my [01:03:00] podcast. Joined Colossus that the name of the podcast, or that\'s at least the URL where we\'re pointing out.

\n\n\n\n

And then your last pick was the waking of, excuse me, working in public, the making in maintenance of open source software. I won\'t try to pronounce the author\'s name, but it is a book on amazon.com published in August of 2020. I thought that was a very excellent pick as well on our first book pick. So,

\n\n\n\n

Lesley Sim: and also the FSC outreach program.

\n\n\n\n

David Bisset: Yes. And that too, I don\'t know. I can\'t remember if that was in your quickies or your deads definitely need to be renamed. My, my final three or my big three was the amp was, has a rapidly damaged publisher\'s trust. And half of the credit goes to the subject matter. Half of it goes to Sarah Gooding\'s writing on that piece.

\n\n\n\n

Ken saved the internet from the David from the protocol. Article written by David Pierce and the acquisition of automotives acquisition of easy digital downloads, [01:04:00] WP, simple pay affiliate WP, and all of that stuff from Sandhills development as well. I think that was my one acquisition pick, which I I\'m surprised nobody got to Pagely, but that\'s fine.

\n\n\n\n

They\'ll they? I managed

\n\n\n\n

Robert Jacobi: chat, but it\'s just, you know, it happened so recently. And there\'s just so many other things that

\n\n\n\n

David Bisset: I have to say it once, because it\'ll show up in the transcript. It\'ll just make everybody feel good. Yeah. We\'ve only said Wix twice. Oh, crap.

\n\n\n\n

Robert Jacobi: Well, let\'s say go daddy mode. What happens when you say GoDaddy three times?

\n\n\n\n

David Bisset: I get a coupon in the, in my email for free months. I was thinking, so why do so ever? I know what I do on the first of.

\n\n\n\n

Robert Jacobi: It\'s like a Sinatra. I\'m going to give him a shout out for that.

\n\n\n\n

David Bisset: It should, he should. It\'s a lots of companies did a lot of hard work this year. I will. So I want to thank my panelists and I\'m going to go on the order of which they were delivered.

\n\n\n\n

And please let me know as you\'re closing off here, where people can find you on the internet, let\'s start with Aurooba.

\n\n\n\n

Aurooba Ahmed: I\'m a [01:05:00] Aurooba.com or twitter.com/aurooba, Aurooba. Thanks for having me.

\n\n\n\n

David Bisset: No, thank you for having us. I think you were one of the first people that said yes. It\'s very rare. Yes. When it comes to this podcast.

\n\n\n\n

Yes. At least anyway Daniel where people can find you.

\n\n\n\n

Daniel Schutzsmith: Yeah. Danielschutzsmith.com. You know, I do a lot of different projects, but really just find me on Twitter. So it\'s S C H U T Z S M I T H.

\n\n\n\n

David Bisset: Great. And Jason Cosper, where can we find you? Yeah.

\n\n\n\n

Jason Cosper: You can find me at Jason.Cosper.ME or on Twitter at B as in boy, O G as in girl, a H

\n\n\n\n

David Bisset: like, Ooh.

\n\n\n\n

Yeah, it sounds like I, yeah, something I should yell in the middle of the Costco\'s and see what happens. Robert trying

\n\n\n\n

Robert Jacobi: to spell Jason\'s Twitter handle. Hold on. I\'ll be there. I\'ll be back in a minute. When I figure out all

\n\n\n\n

David Bisset: the letters well, admire your a mustache in the meantime. [01:06:00] Go ahead.

\n\n\n\n

Robert Jacobi: You can always reach me somewhere at cloudways.com but on Twitter at Robert Jacobi spelled like it\'s sounds except it\'s an I at the end and Robertjacobi.com.

\n\n\n\n

Well, there\'s Jason, you know, we\'ve got triple J who\'s got the Jacoby with the.

\n\n\n\n

David Bisset: Yes. Yes.

\n\n\n\n

Robert Jacobi: It\'s really supposed to be an eye.

\n\n\n\n

David Bisset: I\'m just telling you, we don\'t want to get you too mixed up. That\'s right. Definitely not different facial hair at the very least. And finally, Leslie, my darling, Leslie, where can people find you?

\n\n\n\n

Lesley Sim: You can find me on Twitter. I\'m there too much. I\'m only second to you. And your means stated you can find me on Twitter at lesley_pizza, L E S L E Y underscore pizza. And you can find my plugin at newsletters new.

\n\n\n\n

David Bisset: Yes, that\'s right. And if you need a newsletter and a plugin form, put her on the list and definitely I [01:07:00] want to thank you all for coming this evening.

\n\n\n\n

This was the first time we did this first time I\'ve done this. I think it went really well. I, we there\'s a lot of people doing into the year roundups. In about two weeks, you\'ll see everybody doing the predictions for 2020 twos. That\'s your, if I\'ll be able to do anything differently there, but I wanted to close out the year what our best picks were in a format.

\n\n\n\n

That was we\'ll show these off on post status.com as our, as kind of like our teams, you know, this is, these are the picks that represent us and what we thought. And I think we got a really great mixture. Thank you for not turning this into acquisition. Allie, really appreciate that. I probably will be our invite by five VCs on next time.

\n\n\n\n

And, you know, I\'ll just sit here and just, you know, watch Seinfeld or something while they rattle off all their acquisition acquisitional hires. But thank you very much for coming. And I hope you guys have a good night and I wait a minute. Let\'s back up. Let me re edit that. I hope all you people have a good [01:08:00] night.

\n\n\n\n

All right. Thank you.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 Dec 2021 17:30:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Olivia Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:42:\"WordPress Foundation: Looking back at 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://wordpressfoundation.org/?p=206345\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"https://wordpressfoundation.org/news/2021/looking-back-at-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6647:\"

As 2021 is coming to an end, it is time to look back at the year that was. 2021 was a challenging year for the world due to the continued spread of the COVID-19 pandemic. However, despite all the challenges, the WordPress Foundation was able to make excellent progress in its mission of educating the public about open source software and serving the public good – thanks to our global team of spirited volunteers and contributors.

\n\n\n\n

Read on to find out about our various programs in 2021.

\n\n\n\n

do_action charity hackathons

\n\n\n\n

One of our focuses this year was to revamp our do_action program. Thanks to our hard work, do_action organizers now have a dedicated location@doaction.org email ID powered by Google Workspace for Non profits, which will help them in their initiatives. We also kick-started discussions to organize a global do_action charity hackathon held fully online, and we are all set to execute this idea in 2022. We also announced the return of in-person do_action hackathons after nearly 18 months of online events!

\n\n\n\n

We had two do_action charity hackathons planned this year: do_action Karnataka and do_action Nigeria. do_action Karnataka was held in August 2021, where 12 volunteers worked hand-in-hand to create websites for three non profits. You can read more about the event here:

\n\n\n\n
\n
do_action Karnataka 2021: A report
\n
\n\n\n\n

While do_action Nigeria had to be canceled due to unforeseen circumstances, the local WordPress community – led by WordPress Community Deputy Mary Job, is doing a phenomenal job on the ground by uplifting women and children through their own charitable initiatives using WordPress.

\n\n\n\n

Introduction to Open source workshops

\n\n\n\n

Last year, during the COVID-19 pandemic, we brought back our Introduction to Open source workshops as a way to re-engage the community and to reinforce our core mission of promoting open source software to the community. At the start of this year, we announced our plans to continue these workshops in 2021.

\n\n\n\n

At the time of writing this post, we have had 11 Global Introduction to Open source workshops, which have had a total of 233 RSVPs so far. We also have our final Introduction to Open source workshop for the year scheduled for tomorrow (December 31) as well!

\n\n\n\n

Learn WordPress

\n\n\n\n

Learn WordPress (learn.wordpress.org) – a cross-team initiative led by the Make WordPress Training team was launched in December 2020. The initiative serves to democratize and support WordPress learning by providing high-quality WordPress learning content in different formats. At the time of publishing this post, the platform had published the following content in 2021 alone:

\n\n\n\n\n\n\n\n

The contributor teams working on this project have some amazing plans for the project, and the WordPress Foundation will continue to support their work in the best way possible.

\n\n\n\n
\n\n\n\n

Several individuals contributed generously to the WordPress foundation this year. We would like to extend our heartfelt gratitude to all our donors who supported us in sustaining the foundation this year. Special mention to the following individuals who went above and beyond in supporting us in 2021:

\n\n\n\n
\n
\n

Sustainer – $1000 per year

\n\n\n\n
  • 10up
  • Human Made
  • Jetpack
  • Matt Mullenweg
  • Multidots, Inc
  • Sujay Pawar
  • Wordfence
  • InMotion Hosting
\n
\n\n\n\n
\n

Sustainer – $200 per year

\n\n\n\n
  • Donavon Guyot
  • Eric Kuznacic
  • Ellen and Karl Olinger
  • Pippin Williamson
  • W4
  • René Hermenau / WP Staging
\n
\n
\n\n\n\n

The WordPress Foundation has several ambitious plans for 2022, none of which would be possible without your help. If you would like to support the WordPress Foundation and contribute to our mission of serving the public good and educating the public about open source software, please consider donating to the WordPress Foundation. Your donation goes a long way in keeping the web open. Please use the link below to donate.

\n\n\n\n
\n
Donate
\n
\n\n\n\n

Thank you for your continued support of the WordPress Foundation. Here’s wishing you all an excellent holiday season and a happy 2022!

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 Dec 2021 12:48: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:12:\"Hari Shanker\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:53:\"WPTavern: A Throwback to the Past: Retro Winamp Block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127752\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:149:\"https://wptavern.com/a-throwback-to-the-past-retro-winamp-block?utm_source=rss&utm_medium=rss&utm_campaign=a-throwback-to-the-past-retro-winamp-block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4112:\"

In mid-November, I happened upon a block plugin called Retro Winamp Block. As many of our readers know, I am always on the lookout for those WordPress extensions that remind me of the era when I first started using computers and exploring the web.

\n\n\n\n

The plugin seemed to fit the bill. It had “retro” in the title, so it had already piqued my interest without even installing it. It had been years since I used Winamp. The media player was first released in 1997 for Microsoft Windows and grew in popularity through the early 2000s. By the time I arrived on the scene, it had already built a massive user base. It was the best option available for creating music playlists at the time, and it was skinnable.

\n\n\n\n

Winamp was popular back when the world wide web felt more alive. I still look upon it as the golden era of user creation and the blossoming of fandom. Where else could you find a collection of Brad Pitt skins for your computer’s media player? Or, One Piece? Even Super Mario?

\n\n\n\n

I did not hesitate to install this throwback plugin. Unfortunately, it errored out whenever I attempted to add an audio file. So, I set it aside with a note to look at it down the road.

\n\n\n\n

A few weeks later, I read WordPress lead developer Helen Hou-Sandí’s goodbye announcement to 10up, the company she had been with for a decade. With the help of Mel Choyce, co-workers Jeff Paul, Darin Kotter, and Tung Du created the Retro Winamp Block in her honor.

\n\n\n\n

I checked back in on the plugin. There was an update, and the change log noted a fix for the error I had encountered. In minutes, I was able to once again experience the glory of one of the first media players I had used on my old Gateway laptop.

\n\n\n\nRetro Winamp Block in the editor.\n\n\n\n

Retro Winamp Block has does not have many options. Actually, it only has one customization that users will be interested in: the player skin. They can enter any URL for it, and over 83,000 are available via the Winamp Skin Museum.

\n\n\n\nWinamp Skin Museum.\n\n\n\n

The museum is hosted by Webamp, a project that implements an HTML5 and JavaScript of the old Winamp 2.9. 10up used it for its own Retro Winamp Block plugin.

\n\n\n\n

Since installing the latest version 1.0.1 of the plugin, I have only hit one issue. The live preview in the editor is partially broken. The player floats in the same spot instead of scrolling with the page..

\n\n\n\n

If I had one wish for this plugin, it would be to see the addition of Milkdrop, the popular Winamp visualizer add-on.

\n\n\n\nWinamp with Milkdrop add-on.\n\n\n\n

Mostly, I simply enjoyed this jaunt down memory lane. I even went as far as installing the latest Winamp on my computer. The original player still has a thriving community if its forums are any indication. The UI is practically unusable on my laptop, so I dropped it after listening to an old Ashlee Simpson album.

\n\n\n\n

While I enjoyed the nostalgia of the old player, I want to see modern-day implementations of these types of features for WordPress. Instead of a throwback to Winamp, where is the skinnable audio block?

\n\n\n\n

I put together a quick pattern to test out some ideas (code on Gist):

\n\n\n\nCover + Audio + Social block pattern.\n\n\n\n

The background is by Jeff Golenski from WordPress Photos (this directory is already coming in handy). A few adjustments later, I had a custom-styled audio layout. However, I could not modify the audio player itself. It is just the browser default. There is no equalizer, track info, or visual flair. Just a clean, boring player that longs for someone to sprinkle a little pizazz on it.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 Dec 2021 02:43:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:101:\"Post Status: Post Status Excerpt (No. 39) — WordPress 5.9: Delays, the Customizer, and Contributing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=91867\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/excerpt/39/\";s: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:59922:\"

“Too many things were interrelated and we didn’t have enough people who were looking across…” —Anne McCarthy

\n\n\n\n

In this episode of Post Status Excerpt, David has an informative chat with Anne McCarthy. Anne is a Developer Relations Wrangler for Automattic and (among other things) has been responsible for many of the recent videos showcasing the features of Full Site Editing and WordPress 5.9. David and Anne talk about what decisions led to the delay of WordPress 5.9, her start with Automattic, COVID\'s effect on core contributions, and how polished Full Site Editing might be by the end of January 2022.

\n\n\n\n

Also: David asks Anne what the future of the WordPress Customizer will be in a world of Full Site Editing.

\n\n\n\n\n\n\n\n

Every week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash. \"⚡\"

You can listen to past episodes of The Excerpt, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS. \"🎧\"

\n\n\n\n

\"🔗\" Mentioned in the show:

\n\n\n\n\n\n\n\n

\"🙏\" Sponsor: Gravity Forms

\n\n\n\n

Gravity Forms is the easiest and most trusted advanced forms solution for your WordPress website. Packed with time-saving tools and features, Gravity Forms is the only WordPress form management plugin you will ever need. Stop losing valuable leads and grow your business with Gravity.

\n\n\n\n

Transcript

\n\n\n\n

David Bisset: I didn\'t go to the state of the word, obviously, w it was, it would take too much time away from me, tweeting fun, little memes and remarks. So I decided to stay home and it hurt your

\n\n\n\n

Anne McCarthy: Twitter

\n\n\n\n

David Bisset: game. Yeah. Twitter didn\'t ban me. So, you know, I must be on the good list. But yeah, it was, I thought it was you.

\n\n\n\n

Did you did you watch it?

\n\n\n\n

Anne McCarthy: I did watch it, but I will admit that I was helping with the slides that day. So what I did actually watch, I was pretty fried by the time I actually watched it.

\n\n\n\n

David Bisset: How did you help with the slides?

\n\n\n\n

Anne McCarthy: Just from afar. There were some demos that needed some voiceovers and designers had done two wonderful demos, but there was just no con like voiceover to explain what was actually happening.

\n\n\n\n

So I jumped in to do some of those and just kind of fill filling gaps with the

\n\n\n\n

David Bisset: bar.

\n\n\n\n

I knew that voice sounded familiar.I mean, not every voice cause I\'m like, wow, you must have had a lot of cigarettes that day for that for that voice. But no I forget his name, but we, there was a voice that I remember for one of the [00:02:00] demos that previously did, like a whole bunch of WordPress demos and he has an accent and I can\'t think of his name right now, but I will later…

\n\n\n\n

Anne McCarthy: Oh, you\'re probably thinking Michael Peck.

\n\n\n\n

David Bisset: Yes, that\'s probably

\n\n\n\n

Anne McCarthy: yes, he did the 5.9 voiceover demo. And that\'s actually like, I don\'t know if you\'ve seen a YouTube video, but there\'s a awesome YouTube video. That group has worked on. A WordPress YouTube channel. And he did the voice over for that. And it\'s like a really cool kind of throwback to the early days where he would do release videos and he like knocked it out of the park.

\n\n\n\n

Pretty sure.

\n\n\n\n

David Bisset: What does he do besides does all he do is voiceovers. What does he do?

\n\n\n\n

Anne McCarthy: No, he works for automatic. Now. He\'s mainly focused, I think on a combination of probably. Brand and design stuff or a purse.com. So

\n\n\n\n

we got them on loan.

\n\n\n\n

David Bisset: I said, he must have, you must have been in some virtual cafeteria, regular cafeteria back then in the here.

\n\n\n\n

And you\'re like, oh, that voice, I must have that voice.

\n\n\n\n

Anne McCarthy: It\'s very impressive. I have a friend who has a really good radio voice. I\'m always really [00:03:00] jealous. I want him to record my voicemail at some point.

\n\n\n\n

David Bisset: Oh yes. Anybody with an accident? I wanted to be good. I want it on mine. My parents said I always had a great face and voice for books.

\n\n\n\n

So let\'s talk about, let\'s actually talk a little bit, the videos. How did the I know you\'re involved in them now. I, you seem to be in the. We\'re going to have our IC a video. Most of the time, outside of the state of the word, it looks like you, that you are pushing them. Are you primarily the one that makes those.

\n\n\n\n

Anne McCarthy: Yeah, for the YouTube videos. I have some on my personal channel that I do, I did help with the 5.9 video, mainly from a logistics wrangling, like figuring out script actually did an initial voiceover that got nixed and be like, Michael police come in here. I was very sick and Michael very graciously hopped it at the last minute, but mainly I just kind of help out in terms of.

\n\n\n\n

Coming up with ideas. So sometimes with learn WordPress folks, I\'ll also share some like review what they\'re working on, but a lot of the YouTube videos on my channel are [00:04:00] just things that I find interesting or that I anticipate with the next release. We just need to get some content out there and I\'m fortunate to be so.

\n\n\n\n

So the project that I can share things early and from there I can then send them to folks who actually have real followings and be like, Hey, I know you\'re probably going to create content, but the navigation block, here\'s like a rundown of all the features. Here\'s how I\'m presenting it, like do your thing.

\n\n\n\n

So it actually started that way where I was just creating content as a way to actually demonstrate something for other people to kind of just. Get the word out about something new that was coming and it was easier to communicate, especially from afar using videos. I had no aspiration. It helps a lot.

\n\n\n\n

Yeah. And I have zero aspirations to be like a YouTuber. I just like, I don\'t think I\'m, you know, have the equipment or the ability to be very good at it. Like some folks are in the WordPress community, but it is fun. It\'s cool. I guess to have it\'s very visual.

\n\n\n\n

It\'s very visual. I know a lot of people really appreciate the, like, just give me the heads up [00:05:00] in two to three minutes.

\n\n\n\n

Cause I remember when I think after Gutenberg was launched, we really appreciated those two or three minute demos that was at Marcus did during the state of the words or during presentations at work camp us or something like that, where you sat down in two minutes or three minutes when you got basically.

\n\n\n\n

All you needed to know. And it was, there was a wow factor there. They, you know, they look at time and space by doing this. I think that\'s a very good idea and I hope you continue. Yeah, I plan to, so

\n\n\n\n

yeah, I appreciate that because I\'ve got a lot of encouragement from Paul AC and Nathan Wrigley, and they were both like, you should do it, but you\'d be fine.

\n\n\n\n

And I was like, I don\'t know, like, I don\'t think I have the time or I don\'t think it\'s like saying that I would be very good at. And I\'ve gotten good feedback where people are kind of like what you\'re saying was like, I need to see the visual and also. Who is so close to the project on a day-to-day basis.

\n\n\n\n

It\'s like, give me the little details. Like, I don\'t want to just see it at a high level. Give me the like bells and [00:06:00] whistles. So it\'s kind of a, it\'s a cool, neat way to connect with folks too. I\'ve gotten this just this week. I had like three or four people reach out and my contact form, like, Hey, I watched your video about this.

\n\n\n\n

Like, can you help me with facts?

\n\n\n\n

David Bisset: Oh great, I\'m a support person now! Yeah. Now. But it\'s, you know, in the beginning was so easy to see the mess because there were massive changes or adjustments happening to Gutenberg, but, and there still are, but now things are being tweaked and being refined. And over a post status, Courtney produces like every week she produced.

\n\n\n\n

So this is the list of things that are happening in core. And of course, a lot of it\'s Gutenberg related. Yeah. And, you know, share, feel free to share with me your thoughts on this is it. I think it\'s becoming a little bit harder now to gauge a lot, unless it\'s a big headline feature and full site editing.

\n\n\n\n

We can get into that unless it\'s a headlined feature that you\'ve been hearing about. I think, you know, when I do the summaries and do the post for post status and what little time I have to review the text, which is in a [00:07:00] make.wordpress.org document. It\'s kind of hard to visualize a lot of that.

\n\n\n\n

And therefore it\'s kind of hard for anyone outside of maybe two or three dozen people to really communicate and train, you know, translate that excitement to other people or to show how much progress is being made. Because you read a bullet list and it\'s, you don\'t know, you don\'t know how much work is happening behind those bullet lists for starters.

\n\n\n\n

And then, you know, something could do something very cool visually, but if it\'s just on a bullet list on make.wordpress.org, the public not gonna see that.

\n\n\n\n

Anne McCarthy: Yeah, no, I think you\'re right about that. And that\'s one of the things I don\'t know if you\'ve noticed, but in the last year or so the designs and like the visuals that had come with the what\'s new in Gutenberg posts have definitely been upgraded because of that exact problem is it\'s like, show me the value, show me how it actually connects, how it makes my life easier.

\n\n\n\n

And there\'s also a series of posts. I do the core editor improvement posts. Yeah, that also seeks to even highlight that more. And it started out as like highlighting individual things. And recently I\'ve [00:08:00] actually had to switch to not have to, but it actually makes sense to switch to like a collection of improvement.

\n\n\n\n

So I have a post right now that I\'m working on with a couple of folks. On like performance at 5.9. So let\'s talk about the performance enhancements. Let\'s run through it in one place so you can see it. Yeah.

\n\n\n\n

David Bisset: You\'ve given me a topic to talk to you about. Thank you. But to some somebody\'s credit though, and I think when they do the Gutenberg plugin, Release posts.

\n\n\n\n

They do offer him graphics and they\'ve gotten better with videos. I just wish everything was an animated GIF so I could share it. That\'s a lot easier. Thank you very much. So those existed, but like, I think for what you\'re doing and for some of the things that I think flying under the radar, you know, that, you know, not again, not the headline features.

\n\n\n\n

I think the there\'s nothing. Then a short video. Yeah.

\n\n\n\n

Anne McCarthy: And the connecting the dots. Like I started that connecting the dots series, just kind of on a whim because I found something that I was like, you can do this. If you combine these different tools, you can then do this crazy thing. Like I think [00:09:00] that\'s also, I actually, that\'s the series I\'m probably most excited about.

\n\n\n\n

Like, it\'s fun to do these headline, like explore navigation blockers from 5.9 or the query look like that. Those are fun videos to do, but the connecting the dots. It feels more exciting. Like I\'m like, gosh, yes, get this major feature in your head. But then also like, let\'s talk about like the weird things you can do and the cool things you can do when you actually combine these things.

\n\n\n\n

Cause that\'s, what\'s really powerful is it\'s not like cool. We added dimension controls to this thing, but like what does this actually allow me to do? Okay. This.

\n\n\n\n

David Bisset: Practical application right? Yes. Cause those are the videos I\'d like to show off from the meetup groups. And a lot of times meet up organizers, just say, this is cool.

\n\n\n\n

And then the media bargain meet up organizers. If they\'re good meetup organizers say, and this is how it could apply to you person, that\'s running an agency out of there out of a phone booth or whatever it is you do. Let\'s transition from weird to WordPress 5.9, because you could say something [00:10:00] happened a little bit weird on that.

\n\n\n\n

Oh yeah. It\'s supposed to be out or right around this time of rigidly, right? I think it was before the holidays. Yeah. You mean the same date as the state of the word? Really? Yeah. I didn\'t put those dots. Yeah. That, that, that would yeah, that\'s a coincidence. So it didn\'t happen.

\n\n\n\n

Can you tell me a little bit about what happened and what was involved in making the decision? No spoilers, but to push that into charity.

\n\n\n\n

Anne McCarthy: Yeah, it\'s a really tough decision. And I\'ll preface this by saying I wrote a post that on why I voted to delay it. So I won\'t go into hyper detail cause there\'s a lot of detail on that post that I try to make it very practical.

\n\n\n\n

Here\'s how you can enact a lot of videos and like images being like, this is why. But yeah, this is my first time on a really squad too. So I don\'t have the historical knowledge that other folks bring to the table, but from my point of view and from my experience. Which program, which really is where I\'m coming from too many things were interrelated.

\n\n\n\n

And then we didn\'t [00:11:00] have enough people. Who were looking across basically is the long and short of it. So, you know, 2022 is relying on you know, certain things get in place with styles, but at the same time, those working on styles aren\'t necessarily solely focused on 2022. So like, it was kind of, there was a weird tension there of bringing a lot of unrelated things together,

\n\n\n\n

David Bisset: ultimately, I\'m sorry, was it like the sunny from Philadelphia meme where the chart is. I think it\'s Charlie, he\'s looking at the board behind him and then the oldest red strings going everywhere. And he\'s trying to explain something was a kind of like that a

\n\n\n\n

Anne McCarthy: little bit. Yeah. There is a little element of that, but almost imagine. That if you were to remove one of the strings, like that feature wouldn\'t make as much sense anymore.

\n\n\n\n

So remember how we were just talking about connecting the dots and how things working together is actually where the value like hyper value goes. That\'s what basically was going on, where it was like, if we ship these things independently, we could in theory, remove some of the stuff. But it\'s going to be, it\'s just the value kind of isn\'t as exponential when they\'re all together.

\n\n\n\n

And I was [00:12:00] looking at the issues. I test it every day, like, especially leading up to release for 5.8, 5.9. I\'ve been testing every single day in this stuff all the time. And a lot of it was refinements. It was like, there were a couple of things that, some big decisions. So one I can tell. There was stuff around the navigation block, how to reuse it across Wakim\'s.

\n\n\n\n

So originally there was a thing called navigation areas that was a new block that got reverted. That was I think, the right call. And then there the browsing. So when I talk about browsing, it\'s like, how do you navigate between your homepage, your templates and your template, parts and styles? Like what does that system look like from an information architecture perspective?

\n\n\n\n

And there was a weird combination of. Technical constraints that came up as well as like design, so design and the technical constraints. We\'re kind of dancing with each other. And at a certain point, it just got to a place where. Fortunately like a middle ground could be found. And I think the solution they have right now is excellent.

\n\n\n\n

Originally that, that seemed to be not viable. So kind of by having the delay, we\'ve [00:13:00] had like a better solution, I think, than what was originally in place. That\'s been tested a lot with the outreach program, so it\'s a lot of it. Yeah.

\n\n\n\n

David Bisset: Am I correct in understanding you that you were the one who initially brought something up?

\n\n\n\n

Anne McCarthy: I was not necessarily, there was a team.

\n\n\n\n

David Bisset: Yeah, everybody started getting the idea around the same time. Maybe.

\n\n\n\n

Anne McCarthy: Yeah, it was one of those where I think enough people kind of paused and like, I can tell you leading up to the release. I was like, okay, are we really feeling good about this? Like, I had some moments, but I also wasn\'t like confident and being the person to say like, we can\'t ship this, we can\'t ship this.

\n\n\n\n

Like, I\'m definitely not one of those decision makers, but I mean, I\'m filing, I was filing tons of issues and getting, and with the outreach program, obviously, like I\'m seeing the complaints, I\'m writing a summary post. So like I knew what the pain points were. And then at a certain point, it becomes a decision for the designers.

\n\n\n\n

Like what design direction do we want to go in? And that\'s kind of where we landed, where it was just like a last minute kind [00:14:00] of Too much to figure out. And a lot of it\'s like little things too. So I\'m talking about these big decisions. If there were a lot of small things that need to be sorted out that thankfully were more refinements.

\n\n\n\n

And so I felt really comfortable delaying and voting to delay because of that, because I was like, the value will be exponential. If we can ship these altogether, everything I\'m seeing right now can be figured out like at first. And I think this is where the confusion really started. There was this like long list and it was all seen as blockers.

\n\n\n\n

So originally there was like this get hub issue that Someone did there. I think it was Rob who\'s, the corridor tech lead, who has been doing an excellent job. All the lease lead folks have been doing amazing work and he wrote all the issues out and gathered all of them that people were flagging.

\n\n\n\n

But they were seeing all his blockers and that wasn\'t the case. Really from that list, there were like a subset of blockers that were truly like, we need to delay this. And that\'s part of the chaos of, you know, working remotely. Yes.

\n\n\n\n

David Bisset: You had a translated into a sound. It would be mostly that. So yeah, I would imagine the [00:15:00] holidays.

\n\n\n\n

It didn\'t help that the fact that we have this, let\'s be honest, the last two weeks of the year or the last week of the year, the first week in the new year, however you want to slice it really for me, three weeks, really, or two and a half at best, but sometimes three weeks for everybody to get.

\n\n\n\n

Even if they\'re staying home, even if they\'re not traveling, it\'s your brain is kind of in a reset mode. Yeah. Like I need, listen, I may not be leaving my house, but I\'m taking a vacation, so you\'re not talking to me. Regardless if you celebrate any of the holidays or not, there\'s enough mass people taking time off visiting family, or just staying at home or away from computers that I would imagine productivity would\'ve hit a dive there and, or you didn\'t want to, nobody would want it have taken the chance.

\n\n\n\n

You know, we don\'t want to make Matt Mullenweg into Scrooge because he\'s to he\'s the lead. Right. He\'s the lead. Right. So that would be, yeah, that I\'m correctly associating the[00:16:00] fictional character with the appropriate reference. Thank you. Case. I get an email later. So when is a WordPress 5.9 coming up?

\n\n\n\n

Anne McCarthy: It\'s going to be released January 25th. And as you were saying, like originally the beta was only pushed by two weeks, but then we had to add extra time because of the end of the year period and beginning of the year. I mean, it\'s just a chaotic time. And I think that is also the right call. I don\'t think it\'ll hyper disrupt any other releases.

\n\n\n\n

I think there\'s a ton of stuff for 6.02. It\'s not like, oh, by delaying, we\'re going to have a really light 6.0 release. I think it\'s gonna be. How\'s that going to change as

\n\n\n\n

David Bisset: well? Is that going to be a little bit compressed then in the first part of the year, you think, or is different people working on different things?

\n\n\n\n

Anne McCarthy: Yeah, I think at a certain point it might compress it a bit, meaning like there might be a release in like March or something like that, but they actually didn\'t release the schedule for 6.0 yet. So I\'m not really sure how that\'s going to impact. Things I will say part of the discussion that\'s come up amongst score contributors when I\'ve checked in with a lot of them, when this was going on to make sure everyone was doing okay.

\n\n\n\n

And a lot of them were like, man, this is when I wish [00:17:00] we had more releases. Like I wish we could have this like more of a release cadence where it\'s more frequent. So we\'re not like needing to do with delay. Cause like the options were not fun, but that\'s the constraints of the current system. And, you know, ideally in a future world, it isn\'t as Yeah.

\n\n\n\n

Each release. You can kind of say like, it\'s okay. We can ship this because we have another release coming in a month rather than like three months.

\n\n\n\n

David Bisset: Yeah. Is that possible though? I mean, is that possible at least where we stand right now, because we just talked about how. And like how integrated are, how one piece is related to this.

\n\n\n\n

And, you know, you know, maybe this is just one of those junctures in the four stages of Gutenberg or whatever timeline you want to pick where yes, it all is intersecting together. Cause it\'s full site editing. I mean, it\'s the words are in there. It\'s full side. Right. And then maybe down the road with when he gets to collaboration and translation, maybe things will go a bit easier, but regardless it\'s like.

\n\n\n\n

I know there\'s so many, there\'s so many ways you can look at it. I hear about a lot of time in other technology groups, in terms of first, you have people say, well, why [00:18:00] don\'t you just release every month? It\'s no worries. Any automatic updates. It\'s fine. And then that happens. And then you say, why are we getting so many updates?

\n\n\n\n

I have to keep updating.

\n\n\n\n

Yeah. Which, which, you know, is another subject in of itself because in theory, You shouldn\'t have update fatigue, if you have automatic updates turned on and you know, that\'s another thing too. You know, in some situations that\'s not possible. So you\'re going to have people, whether it\'s a real problem or something that someone projects into their mind, like some sort of ghost but it\'s still a legitimate thing to deal with.

\n\n\n\n

So I see. So yeah, you have this, you it\'s a bunch of. All not the code, but the responsibilities and the dependencies is a bunch of, you know, a bunch of well cooked, fine high quality spaghetti.

\n\n\n\n

Anne McCarthy: And yeah, it would be really tricky to do. Like, I don\'t necessarily think that\'s like a viable thing right now, or I don\'t, I can\'t speak to it in the future, but I do [00:19:00] think it is a result of, you know, the circumstances that we\'re in.

\n\n\n\n

Like we\'re all impacted by the same constraints. And I think that\'s one of the things where. You know, for example, there are, I don\'t think it was fully scoped out even like, what would a dependency plan look like where it\'s like, or contingency plan? Sorry, look like where if let\'s say we had to remove some of these things, would we, excuse for example, we could do things like remove browsing entirely, which is one of the things that was, I think, shipped at some point.

\n\n\n\n

We\'re instead you have, you know, your appearance menu, you have templates, simpler parts, the editor styles. And so you have no sort of browsing in the sidebar. You could also like say, you know what, the navigation block isn\'t ready or counting it to another release. You could also say like, you know what, you can\'t actually create new templates.

\n\n\n\n

You can only just view the ones that come with your theme. Like there\'s a lot of ways that could have been pulled back. But thankfully what shipping is very comprehensive. Like I think that\'s the good thing with this delays also.

\n\n\n\n

David Bisset: I don\'t think anybody\'s looking at it going on, man.[00:20:00]

\n\n\n\n

Anne McCarthy: Yeah. And I mean, I also think the good news is ultimately these features that we\'re talking about, which get a lot of attention are going to impact a small subset of people. Like this is not going to be five point where all of a sudden it takes over your site and you have to use it like this is it.

\n\n\n\n

It\'s very much. So in line with the gradual adoption, where if you want to use these features, you have to literally hyper opt-in. You have to switch your theme. You have to like seek it out. Like it\'s very much something that. That also gave me confidence where it\'s like, I know these like full siting and all the collection features that go along with that.

\n\n\n\n

You get a lot of attention. But even if you upgrade, you\'re not switching to full site editing, you\'re still gonna get a ton of value in this release. And that, that to me is what\'s really exciting is it\'s almost like, because this is a smaller subset. The features are more high impact exponentially when they\'re working together.

\n\n\n\n

I think it was just the right call, but I\'m really excited to see people get their hands on 5.9. And speaking of police health tests, the Tesco lead, I\'m like, please help test. It\'d be a huge help.

\n\n\n\n

David Bisset: We\'ll get through testing in a second, because I [00:21:00] do want to, I do want to get, like, if you had the opportunity.

\n\n\n\n

To make it to make a pitch for you. You did mention 5.0 though. When that first came out, I think there was a there\'s a number of people that, and you know, that the circumstances behind that you know, around the state of the word time, everybody was busy or give Ghana was one of those. I think it wasn\'t November.

\n\n\n\n

So, I mean, it was approaching a holiday season or something or something like that, but it was, I would be, I don\'t know, a lot of people said it was around rough around the edges. I\'m not going to argue with him about that when it came out but over time that the improvements on it have been, I think in my opinion, pretty good.

\n\n\n\n

Pretty, pretty tremendous. In fact, do you think and you may, I think you touched on this already, but do you think with a full site editing, we\'re going to see not what 5.0 is. Cause I think you just said that, but do you feel comfortable with the level of Polish that will be out at the end of January?

\n\n\n\n

Anne McCarthy: Oh,

\n\n\n\n

that\'s a great question. There\'s a lot of nuance here, so it depends [00:22:00] upon someone\'s skill level. If you were brand new WordPress user, I would, I\'d say very beta. So like, I think it\'s literally going to ship with a beta warning. So in terms of, is it hyper polished? I would call it functional kind of empowering.

\n\n\n\n

But I wouldn\'t necessarily be like, oh, it\'s delightful. And you can, it\'s completely intuitive. Like I think, and I say this partially because especially if someone, maybe if someone was new, they might actually have an easier time, because there\'s a lot of concepts built within full that are really hard to grasp.

\n\n\n\n

For those of us who\'ve been in WordPress for a long time. Things

\n\n\n\n

David Bisset: Can they get those videos in there? That would probably help.

\n\n\n\n

Anne McCarthy: Yeah, no, I think that\'s part of, so I actually am also helping with the user support docs for this release. So I\'m co testing it and then helping with the user docs. And that\'s one of the things that\'s really difficult to communicate simply.

\n\n\n\n

So like, how do you explain to someone, what template parts are. And how do you explain when to use them? So, like one of the, I just opened an issue for this yesterday, but it\'s like, we probably need to explain the difference [00:23:00] between template parts, reusable, blocks and patterns. And when do you use each? So I probably need to write a doc on that.

\n\n\n\n

So there\'s a lot to be explained there in a way that\'s very simple so that people can make good decisions. And right now their, what is being shifted doesn\'t necessarily have guardrails to nudge someone in the right direction. If that makes sense. So you\'d have to have some level of knowledge in order to write.

\n\n\n\n

Put it together, but do I think it\'s a polished V1 for someone who likes to tinker? Definitely. Like, I, for sure think that\'s the case. The only I can tell you my major sticking point, which is driving me nuts right now is right now. Are you familiar with the template editing mode?

\n\n\n\n

I launched.

\n\n\n\n

I\'ve played with it.

\n\n\n\n

Yes. Yeah. So right now let\'s say I have a block theme activated and I\'m using 5.98. I can go in and I\'m using a theme with template mode. I can go in and I can like add a new post. And then under the posts kind of sidebar, I can select and create any template. And from there I can have a fresh new template that I can then assign to the post.

\n\n\n\n

However, if I\'m in [00:24:00] the site editor and I\'m navigating through the templates, I cannot create a new generic template. And there\'s an issue open for this. I can create an archive when I complete a search warrant. I create a new front page one, but there\'s not a. I want to create a new template and I want to sign this poster page or this category to it.

\n\n\n\n

So there\'s a lot like that basic infrastructure you can, it\'s a workflow thing. So it\'s like in one place, you can do this thing, but in the other place that feels more intuitive. You can\'t. And then on top of that, obviously for this release, some stuff is constrained. So this was one of the decisions that had to be made.

\n\n\n\n

So you can\'t have. If you wanted a category to use a specific template, you\'d have to actually add it to your blocking files rather than like being able to do it in the interface. So the good news is it\'ll ship, but then there\'s some really common. Possibly common use cases where people are going to be like, oh, but I want to do this.

\n\n\n\n

And that\'s where I think 6.0 6.1, like these future releases will continue to deliver on the promise to pull siding. And I think right now what is in place is really powerful. And I think it\'ll [00:25:00] actually jumpstart. People\'s excitement into everything that you can do. But there are just some. I don\'t know.

\n\n\n\n

I think Justin Tadlock had a good description where he\'s like, it works, but then as you\'re getting involved in it, there\'s like some common things that you\'re not yet able to do. And I\'m like, yeah, that\'s very true. Like there are some things that I can imagine. I\'m like, I would love on my personal site to have a specific template for.

\n\n\n\n

All my posts that are tagged with WordPress resources so that I could just send people there and I could have a different header. I could have a different contact form, like have a completely different experience with that. I think it\'d be really cool.

\n\n\n\n

David Bisset: But you know, I was like, it sounds like something in the old days before Gutenberg, that would be like a WordPress plugin.

\n\n\n\n

You would have to find

\n\n\n\n

Anne McCarthy: correct.

\n\n\n\n

David Bisset: Which in the defense of Gutenberg, in terms of that, I mean, You know, you\'re, it seems like a lot of the, you know, a lot of the major work being done, but also some things that are being done in Gutenberg. Like duotone, for example, maybe it\'s the one that jumps out at me. It\'s like, [00:26:00] like before it was just, you had to go find a plugin for that.

\n\n\n\n

I mean, you\'re you and birds taking off. Lots of cool and interesting things that were before with maybe with, or with maybe with a page builder, with an add on with a page builder or just a plugin that those were just like little thrills that you would just find in the plugin stuff, getting Berg\'s incorporating this in the course.

\n\n\n\n

So Gutenberg, I mean, it\'s not just a, it\'s not just the blocks anymore. You\'re incorporating all these like, you know, fun stuff that like, maybe. Not even the majority of people might even use some time, unless there\'s a big, duotone a fan group out there. In other words,

\n\n\n\n

Anne McCarthy: the only thing that I think is cool is that you can add it on theme level.

\n\n\n\n

I think that\'s part of it. It is very much a design tool in that sense. And I think that. To me where I\'ve seen it really come to life is when I\'ve seen some theme authors. I think some automatic female author is released. It\'s skate park is a theme, but it has like do a twin filters baked in. So like, if you change the [00:27:00] background of your theme, the images were also like a doc, the duo tone.

\n\n\n\n

David Bisset: Oh no. My F my life is a French film to atone anyway. So I\'m full of that. Did you happen to hear. I think when it comes to block themes, Matt said something about wanting 3000 a year or so. Was he exaggerating there a little bit? I

\n\n\n\n

Anne McCarthy: think he\'s serious. And like, I also, this sounds wild, but I think it is very much so, like he actually thought it was interesting that he said it in that way, because how do I explain this?

\n\n\n\n

Like, You could take one block theme, like let\'s take 20, 22. For example, the announcement post showed this and any announcement posts, it shows like four or five different style theme Jason files and switching between them. And it looks like a completely different theme. And I think that\'s where it\'s like, you could literally take the base of one theme with the same patterns, all that sort of stuff, and create.

\n\n\n\n

20 different theme, Jason files to switch [00:28:00] between and have a complete different experience. And to me, that\'s, what\'s really cool. And then once you start integrating with the pattern directory even more, I think that unlocks some really cool stuff. So when he says that, I\'m like, yeah, I understand what he\'s saying, but I actually, I think that\'s a way to connect with like the.

\n\n\n\n

FIM world that we have come to know to last however many years. Yeah. But I think the future with block themes, things are going to be wildly different. I think rich table were asked a question about, you know, could there be a directory for different style? And I\'m like, yes, like that to me, I think is a really cool model and there\'s work being done to enable.

\n\n\n\n

And json switching within a block theme,

\n\n\n\n

David Bisset: so definitely would make it competitive with you know, like, like a Wix or Squarespace in terms of like you could have, this is a completely customizable experience. Speaking of customizable, I do have a question for you. When it comes to the full site editing, what happens to the customizer?

\n\n\n\n

There\'s numerous people that use that there\'s people that use that and granted they use that for their theme settings and maybe. And [00:29:00] for other things, and in addition to the normal customization, so what\'s going to happen to the customizer?.

\n\n\n\n

Anne McCarthy: Yeah. So this is actually something that I\'m so glad you\'re asking me this, because this is a thing I\'ve seen, brought up a ton.

\n\n\n\n

I\'ve gotten, especially in the span of like, it felt like two weeks, I was getting a ping, like every other day being like customizer. And I\'m like,

\n\n\n\n

David Bisset: I know like a bot on Twitter about the customizer, but I\'ve figured that ask you.

\n\n\n\n

Anne McCarthy: So basically the customizer, if a plugin or theme happens to look into it the customizer will be available to actually it\'ll direct you to it.

\n\n\n\n

So it\'s not like it\'s going away forever. Is it removed from the menu item? Yes. If you\'re using a block theme, you will not see it unless you are using a plugin that somehow hooks into the

\n\n\n\n

David Bisset: customizer, but you have to switch to a block theme and then at the official

\n\n\n\n

Anne McCarthy: blocking the lose, the customizer only superior.

\n\n\n\n

Correct. And it would only disappear if you don\'t have a plugin that happens to look into

\n\n\n\n

David Bisset: it as well. Right. I\'m sure somebody will come up with that in a few seconds, but

\n\n\n\n

Okay. Then I, you know, initially [00:30:00] here, I mean, I\'ve, haven\'t had my coffee yet, but it sounds like to me, that makes sense where in terms of, you know, you\'re not going to need it. You may not need it. Now, if anybody has anything in there, there\'s probably something developers that have put something in there that shouldn\'t be in there then, you know, get out, get it out of there.

\n\n\n\n

But okay. That answers that question pretty well, because it makes sense. With a block theme on there shouldn\'t be anything in the customizer left.

\n\n\n\n

Anne McCarthy: There is a universal theme. I don\'t know if you\'ve heard about universal themes, but they\'re also a combination. So there\'s like, let\'s see there\'s black beans hybrid themes, universal themes, and classic themes is like theme paradigm.

\n\n\n\n

We\'re about to enter and blockings are like fully built in with full siting. Like you\'re not, you know, using the customized or anything

\n\n\n\n

David Bisset: like that. You don\'t need the, you don\'t need the additional CSS. The one thing that sticks out in my mind is the additional CSS thing in the in the customizer and you and I both know.

\n\n\n\n

That if I don\'t usually use that, I use, I, I add the CSS some other way. It\'s usually through a plugin or through the style sheet, in the theme [00:31:00] or something like that, whatever. That\'s the only thing that kind of concerns me a little bit, because I\'ve seen people put CSS in there that relate even to plugin, not even the theme directly, because that\'s just one place that they\'re able to put CSS.

\n\n\n\n

They know it they\'ve seen it, or some webpage told them to put it there, that they don\'t have to like dig into any code to, they can just put the additional CSS. In fact, it wouldn\'t surprise me if some WordPress plugin support people have told people, oh, in order to resolve this issue with our. You just need a CSS tweak with your theme going here.

\n\n\n\n

But again, you\'re saying that it\'s still going to be there unless they switched to a block theme. So the only danger there is if you switch to a block theme, but if you\'re somehow using the plugin, is that, does that, it\'s just hiding it. It\'s not removing it.

\n\n\n\n

Anne McCarthy: It\'s just hiding it. It\'s not removing it. So

\n\n\n\n

David Bisset: sorry.

\n\n\n\n

I had to work that out. Yeah,

\n\n\n\n

Anne McCarthy: no I totally understand. Cause I used to work on Jetpack a lot and that was one of the things. It has an additional CSS part of it. So I understand what you\'re describing. [00:32:00] Yeah, it\'s very, I also want to advocate actually for universal themes, because if someone is like, I\'m curious about this world, but I don\'t want to jump in universal themes are basically designed so that you can use blocking functionality, but then also the customizer.

\n\n\n\n

So it basically bridges. Which is why it\'s called universal

\n\n\n\n

David Bisset: either that or the movie company bought you the rights.

\n\n\n\n

Anne McCarthy: Did you not hear about the new acquisition?

\n\n\n\n

David Bisset: I was going to go to the theme park in Orlando and see all the new Gutenberg blocks, right? The ride, the Gutenberg ride. Oh my God.

\n\n\n\n

Anne McCarthy: You say that.

\n\n\n\n

But I did. I was getting beer the other day at a store and there was a thing called gluten berg. Which is a form of gluten-free beer. And I was like, oh my God. And I was off work. So I was like, am I tripping right now? Like, what is happening, dude, bird everywhere.

\n\n\n\n

David Bisset: I made a slip on Twitter, I think yesterday morning.

\n\n\n\n

And I said something about like, I\'m having a state of the word hangover, a hashtag Gutenberg. And I left it in there and I just said, Gutenberg is just you [00:33:00] trying to contribute to the project, but you haven\'t figured out yet how to be sustainable. So you\'re, and you\'re not above begging. So, you know?

\n\n\n\n

Yeah. So I left Gutenberg and I left good Megan, there let\'s talk about at least two more things before I leave you to. Fantastic video editing work here. One thing is about testing. What is the number one way? What\'s the number one? What\'s number one thing you advocate regarding testing. And you\'re going to give me symbol links to put in the show notes for this.

\n\n\n\n

So we\'re not going to worry about that, but how does that work and what do what\'s the qualifications and what are you looking. In terms of testing.

\n\n\n\n

Anne McCarthy: It\'s a great, so like the beta posts on, I\'m going to drag people to the beta posts on your research backslash news, because there\'s actually a link under like a testing instructions to a post that I did that gets very detailed.

\n\n\n\n

So if you just are comfortable testing, go for it. If you\'re someone who needs more instruction or. Exactly. Like what to test, how to test. I have a post that\'s it\'s titled help test 5.9 features, and it [00:34:00] goes step by step through the different features with like a brief description of what they are, how to find.

\n\n\n\n

And as well as like, if you want to get even more detailed steps, a lot of them link out to calls for testing that were done through the outreach program. So you can even get like a step-by-step description of what needs to be done. But yeah, right now, if you can, I highly recommend testing both 5.9 in terms of, without a block.

\n\n\n\n

But then also take the 2022 thing first, then it is a very cool expansive team.

\n\n\n\n

David Bisset: Hey, Matt gave us the bird on Tuesday and my wife looked at me like I was, should report it to the. Yeah, but it\'s in, that\'s also another, that\'s another complication layer too. It\'s not just the five nine release. It\'s it\'s the new default WordPress theme. It looks fantastic. It is the, it looks fantastic.

\n\n\n\n

I\'m more excited. I can\'t remember the last time I\'ve been more excited about like a default theme coming up because it really looks like it\'s using the art state of the edge [00:35:00] stuff, plus, you know, the birds well, good. Well, thanks for you. Share those links with me. I\'ll make sure to add them.

\n\n\n\n

I make them in there. So here\'s one thing that\'s been. I was scratching my noggin the other day and trying to figure out the best way to describe this. So I\'ve been told by multiple sources that thanks to COVID thanks to the lack of in-person work camps. The contributions contributors have been, they\'ve been low for the past 16, 18 months, two years, something like that.

\n\n\n\n

And then. Do you think that first of all, do you think that\'s true? And if so of it\'s true. Do you think it\'s, is it impacted the project because Matt, I guess I\'m just gonna finish my sentence and let you speak at the end, because I don\'t know when to shut up, but I did see, I saw Matt slides on Tuesday.

\n\n\n\n

He did highlight. I mean, there are lots of circles in the slides, right. And then there was lots of new contributors. Yes. Circles. I work in [00:36:00] shapes. But there were, and there were lots of new contributors to that. We don\'t know what they worked on. I mean, new contributors, that\'s awesome in there.

\n\n\n\n

And there was definitely a lot of circles on there, but do you think that COVID has had an impact on the contributions or contributors over the past two years?

\n\n\n\n

Anne McCarthy: I mean, yes, both. And I will say, I think it\'s like a. Multi-directional so I think it\'s everything from, for example, the outreach program, I\'ve given out 70 badges for a test contribution, which is probably more than has been given in a long time, you know?

\n\n\n\n

So it\'s like, in some ways we\'ve had more contributors, probably in some spaces and have brought in. And I\'ve had the chance to work with folks who have gone out into their local communities or held things online with their local communities to help people test and explore that. So there\'s like, it\'s both right.

\n\n\n\n

Like I think in some cases it really burns some people out. I think it burned a lot of folks out were just dealing with like trying to survive day to day. You\'re probably not going to want to jump into open source and contribute. [00:37:00] But at the same time, I think suddenly the community had to become a lot more accessible.

\n\n\n\n

So actually I started this role in April of 2020, so right when things were really like in the U S it was. Getting really serious, like in lockdown, all this sort of stuff. So it\'s been very interesting. I, when I first started the job was told like, oh yeah, one of the first things we\'d probably do is send you around a bunch of word camps and word cancer, where people get onboarded and like all this sort of stuff.

\n\n\n\n

And I was like, okay, well that\'s not an option. So what are we going to do about this?

\n\n\n\n

David Bisset: Yeah.

\n\n\n\n

Anne McCarthy: And this is where we\'re all kind of delusional about like, oh, maybe this will pass. And so it\'s been very interesting and like, I can tell you speaking personally, a very anecdotally I have spoken at probably 10 or 11.

\n\n\n\n

Events, maybe more in the last year I do not like public speaking. If I had to go up on stage and do it, it would be way less successful for me. Like it causes way too much anxiety. And then on top of that, like, you know, I just gave the word camp Taiwan recorded or camp Taiwan keynote at [00:38:00] like one 30 in the morning of my time where like, normally I would have to travel to Taiwan.

\n\n\n\n

I would have to, you know, be jet lagged pregnant. There were a couple of days early, like all this sort of stuff. And then it. Being able to connect with brand new contributors and brand new folks has become way easier. And so I think that\'s like one of the things that makes me really excited is like, you can travel the world from your apartment.

\n\n\n\n

So I often look@theonlineeventson.org and just see what people were talking about. And we\'ll just jump in. Either a 5% or 50% meetup

\n\n\n\n

David Bisset: group. Oh, I love her. I love virtual stuff. I talked to my kids. That\'s how I talked to my kids all the time. My kids still live with me, a side note. So do you, so,

\n\n\n\n

Anne McCarthy: yes, I do think it\'s also caused a decrease.

\n\n\n\n

I think there\'s an over-reliance on On people who are sponsored contributors. And I think, but I think it also, at the same time, new pathways have been built. So I\'m both encouraged that like new pathways are being built. New folks are being brought in and things like the photo directory, the pattern directory even blockchains are way easier to build.

\n\n\n\n

[00:39:00] I think we\'re going to see an influx of more folks coming in.

\n\n\n\n

David Bisset: Yeah.

\n\n\n\n

The onboarding process. Right? I would imagine. Yeah, like you said, it\'s harder for any individuals with present condition. So I, you know, companies like, like, and Matt was showing those, the other bubble slide where there was automatic.

\n\n\n\n

I imagine there\'s like you said, you were doing one thing now you\'re doing another, it sounds like there\'s automatic made some adjustments there to. I\'m not putting words in your mouth, but if it wouldn\'t surprise me, if some companies made some adjustments to compensate for the fact that, you know, there is less of certain kinds of contributors out there just because of oral conditions.

\n\n\n\n

And we just finished. I don\'t know if you\'ve been following this log for. She fought with J or something.

\n\n\n\n

Anne McCarthy: Log4jI.

\n\n\n\n

David Bisset: Mean, everybody\'s talking about it. I mean, nobody\'s rewriting my software yet. Thank goodness. I\'m unpopular now. And it\'s an advantage but I mean, there, you have, like, I think two people, one [00:40:00] person working on that and the guy had a side job too, and now everybody\'s kind of relying on it and you know, that makes you sit back and watch.

\n\n\n\n

Well, a lot of people rely on WordPress. Obviously things are going to slip through the cracks, but overall it\'s nice to have, even if there was a major world event and this has been a major world event, then I think things from a feature standpoint, from a bug standing standpoint, it could, I guess it depends on your experience.

\n\n\n\n

You can either say it\'s been fantastic that it\'s managed to be as uninterrupted as it has been over the last two years. Or you can just say, Hey, it could have been worse. It, you know, WordPress runs 43% and the train has to keep moving. The show must go on. And some adjustments, I guess, have to be made.

\n\n\n\n

I\'m looking, I do want to see more independent or at least other companies enter into that bubble space. Just like Matt had. I mean, at one point it was a bubble\'s commercial, but I mean, you know, that second slide with just more independent bubbles on it. So it sounds it\'s, but it sounds like for [00:41:00] me talking with you here, that of all the challenges that\'s happened, both ones that I think everybody could imagine in some of the ones that you\'re not telling me, because we don\'t want to get into the weeds on it.

\n\n\n\n

It sounds like, from stability-wise I th the decision. To bump it. I think it was only a little bit controversial for a moment. At least from the outside. I can\'t speak within the inside of a group. I imagine there was a lot of talk and maybe there was some tradition or precedent there, but obviously that would have didn\'t sound like that lasted very long if there was any, and it was only controversial out here, like, you know, weirdo land where I live, you know, there was news, but it was.

\n\n\n\n

Okay, fine. You\'re bumping it from December. I think I\'d rather have that been bumped. And so it sounds like,

\n\n\n\n

Anne McCarthy: And that was part of why I wrote the post to be honest, because I was like, man, this is going to be so confusing and people who aren\'t just like knee deep in this, like it\'s going to be seen in a light.

\n\n\n\n

That\'s like really hard to parse. And so that was really part of my aim and writing [00:42:00] like, Hey, this is why I voted. And this is the details. If you really want to know Of course, Matt, I don\'t know if you saw Matt\'s comment where it\'s like, this is the actually information I want. Like that\'s a different post that Matt. Like, I can\'t, I don\'t want to write it.

\n\n\n\n

David Bisset: Let me do my work. Cool.

\n\n\n\n

Anne McCarthy: I know I got that comment on Sunday and I was like, oh, okay, cool. Like I, where do I need to write out a post about this? I was like no. We have to do a retro for the release. Like, this is a really good, but he\'s right. I was like, oh man, I should have included some stuff about like, here\'s what I think we can do going forward.

\n\n\n\n

You know, it was chaotic. I wrote it, I think, within a week of the decision. And it was doing it on top of other stuff. So

\n\n\n\n

David Bisset: yeah, next time it\'s a long story, but next time I have to get you to get him to say banana milkshake and the state of the word I have. If you don\'t know what it is, I\'ll try to put a link in the show notes, but anyway.

\n\n\n\n

Yeah. But th the thing about the bingo card is we put some obvious ones there, and then we put some less obvious ones. Like there\'s like, like NFT. He said NFT. Okay. How about metaverse? You said metaverse.. Okay. Now it\'s like, everybody\'s doing bingo. Bingo, and going, oh, crap. I could have made [00:43:00] this harder, except everybody has a one random generated word.

\n\n\n\n

It\'s like I was saying to myself, what\'s the antifree square. It\'s what\'s on a bingo card. What\'s one thing he would never say. And then everybody says, well, we can\'t get bingo. And he says banana milkshake. And I\'m like, all right, people put on your big person pants. And we\'re going to see if we can get someone there.

\n\n\n\n

But anyway, besides that way, we\'ll edit this all out. It\'s boring. but anyway, and what you do, but. To end on a good to end on a very good note here, because I\'m talking to you and you do very good things. So this is going to be very, it\'d be very you\'re very much appreciated in. And even if the resources, even if the testing, you know, is, you know, we could always use more testing.

\n\n\n\n

We can always use more contributors. I think the job that you\'re doing, the videos is doing two things really well, everything that you do, it\'s not just the videos, but the videos, just making things a lot easier to consume. Especially in this Tik TOK world we live in don\'t do tick. I didn\'t say the tick-tock

\n\n\n\n

world.

\n\n\n\n

Anne McCarthy: I mean,

\n\n\n\n

David Bisset: here, my kids don\'t either [00:44:00] I\'m that I\'m not going there, but two it\'s also about the transparency for something like this, I think because it wasn\'t such of a talking point, partly was because you and the team were so transparent. And the minute that we read, the minute I read the report, I\'m like, yeah, this sounds like the way you\'re presenting it.

\n\n\n\n

A it\'s a, no, it sounds like a no-brainer and B we can wait another month. I can wait another month.,

\n\n\n\n

Anne McCarthy: I really credit folks like Tonja and Mary and Rob. And like, there\'s a lot of folks who made that transparency. This is tough decisions, Jonathan to Rogers. Who\'s not even on release squad was like giving advice about timing.

\n\n\n\n

Like it really was a team effort to operate in that way. And I loved seeing the liveliness of the 5.9 release leads channel, and it folks are curious about how our release works. And you can literally watch us talk. And there is no back channel. Like it\'s like, I have a question I\'m going to that channel.

\n\n\n\n

David Bisset: Yeah. I need that. I need kind of that for my, from my marriage. Cause it\'d be nice to have some texts. You didn\'t say that will [00:45:00] let me do a little search here. And where are you going to your mother\'s? Okay. I\'ll catch you later. All right. So, and tell us where we can find you on the web and where people can reach out to you, especially if they have questions.

\n\n\n\n

Anne McCarthy: I\'m at an Zazu and an E Z a Z U on we\'re personal work slack. And then I have a block like I\'m very I know shocking nomad dot block.

\n\n\n\n

David Bisset: Make sure to throw that into the show notes or give that to me and I\'ll put in the show. Yeah. Yeah,

\n\n\n\n

Anne McCarthy: I will. And like, I honestly am not, you can find me on LinkedIn, but I\'m off of Instagram. I activate and deactivate quite frequently. It\'s the one that I seem to be, I do too, but that\'s in

\n\n\n\n

David Bisset: real life, but yes.

\n\n\n\n

I know you\'re not on Twitter and you\'re sometimes on Instagram. That\'s why I wanted to get a few links for you because I\'m in post out a slack and there\'s posts at a slack there\'s WordPress slack. Thank you very much for sitting down and talk to me about this. I think

\n\n\n\n

Anne McCarthy: thanks for the opportunity.

\n\n\n\n

There\'s so much, I feel like we could talk about, which is always such a great feeling is it\'s like, gosh, I could just talk for hours about these different things, because I think so much about them and you [00:46:00] really hit everything that I want to talk about. So it\'s awesome.

\n\n\n\n

David Bisset: Yeah. Why didn\'t I have this skill when I was young and single, I have no idea.

\n\n\n\n

That gives me food for thought later, but anyway, I really appreciate it. And I will I\'ll definitely be checking out the betas for 5.9. We can\'t wait for January.

\n\n\n\n

Anne McCarthy: Awesome.

\";s: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, 29 Dec 2021 23:18:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Olivia Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:51:\"Akismet: How to Stop Contact Form Spam on 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:31:\"http://blog.akismet.com/?p=2177\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://blog.akismet.com/2021/12/29/how-to-stop-contact-form-spam-on-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:15509:\"

Are you getting useless contact form emails in your inbox? Contact form spam is a problem every website owner deals with at some point. Spambots target websites of all sizes, regardless of the amount of traffic you get. 

\n\n\n\n

Sifting through hundreds of messages to separate spam from genuine inquiries is time-consuming and frustrating. Luckily, there are some easy and effective ways to protect your WordPress site from spam and take advantage of the benefits of contact forms. Let’s discuss! 

\n\n\n\n\n\n\n\n

What is contact form spam? 

\n\n\n\n

Before solving this common issue, you’ll need to understand what contact form spam is and how it affects your website and business. 

\n\n\n\n

Contact form spam is exactly what it sounds like: unwanted messages that are submitted through the contact forms on your site. Since these forms have blank fields, an individual spammer (or bot) can fill these out however they’d like. 

\n\n\n\n

You might just get one or two occasional messages with irrelevant promotional material or even offensive language and links. Or, you’ll sometimes receive hundreds or even thousands of form submissions to your inbox. You’re left sifting through the spam so that you don’t miss real messages from interested followers or potential customers. Worse yet, all of these submissions can hog server resources, resulting in a slower site or errors when you try to make changes. 

\n\n\n\n

Spammers target contact forms in one of two ways:

\n\n\n\n

1. Manual spammers

\n\n\n\n

Manual spammers are humans who navigate to your website, fill out your forms, and submit them personally. They typically use false information, often copying and pasting to spam your site quickly. In most cases, these spammers are trying to promote specific websites. But they can also spread malware and funnel traffic to malicious sites. Manual contact form spam is more difficult to overcome because spammers can get past many anti-spam solutions like CAPTCHAs. 

\n\n\n\n

2. Spambots

\n\n\n\n

Spambots are the most common sender of form spam and often the most dangerous. These programs automatically search the internet for forms and, depending on how spammers program the bots, they leave junk text and phishing links that appear in your inbox. 

\n\n\n\n

Spambots threaten the integrity of your website when programmed to perform more malicious activities like taking personal information, spreading malware, or taking control of your website. These automated programs can leave a larger number of form submissions at once. But they’re easier to stop because they can’t combat specific anti-spam solutions. 

\n\n\n\n

Why do bots and human spammers target contact forms? 

\n\n\n\n

With all the advances in technology and increased security options, it’s hard to think that this type of spam still exists. But bots and human spammers still target contact forms because they can, and it works. 

\n\n\n\n

Here are several reasons spammers look for loopholes and vulnerabilities in your website forms: 

\n\n\n\n
  1. They want to send you spam. Most spam includes links to phishing sites or revenue-generating ad sites.
  2. They want to exploit your contact form to spam others. Spammers use your contact forms to relay email spam messages to others. When these emails land in people’s inboxes, they typically look like an email you sent. Unaware that it is spam, users open these emails and click links that lead them to another website. This increases website traffic and engagement to that site, rewarding the spammer. 
  3. They’re searching for vulnerabilities to access the backend of your website or server. This is typically where malicious intent comes into play. When spammers target your contact forms to look for vulnerabilities in your website, they often want to attack it. Spammers can install malware that leaves your website and visitors at risk. They can also steal personal information, a significant risk for eCommerce sites with sensitive customer data. 
\n\n\n\n

How to identify contact form submission spam

\n\n\n\n

Keeping a close eye on your contact form submissions makes it easy to identify spam. Watch out for the following signs that indicate spammers are targeting your website:

\n\n\n\n
  • Phishing links. Spammers use phishing URLs to obtain sensitive information for malicious use. This includes usernames, passwords, or banking details. Phishing links appear to direct to a legitimate site, but it’s really a fake one meant to steal this valuable data. 
  • Irrelevant messages. Another typical indication of spam is unsolicited or irrelevant messages. Spammers send these messages out in large numbers for advertising, phishing, or spreading malware. 
  • Submissions with no real name. If you get submissions with no real name or a fake name, you’ll want to look into blocking form spam. 
  • Grammatical errors or typos. Most spammers don’t take the time to proofread their submissions or check for grammatical errors. Instead, they work hard to send as much spam as possible in the shortest amount of time. Therefore, if you notice messages or comments with a significant amount of typos or grammatical errors, your website is likely under attack. 
  • An offer that’s too good to be true. Like everything in life, an offer too good to be true also indicates a problem. Don’t fall for this easy trap. 
\n\n\n\n

Once you notice a spam issue, it’s vital to find a fast and effective solution. While it’s both annoying and potentially dangerous, spam can also damage your brand reputation. Let’s explore some ways to prevent contact form spam on your website. 

\n\n\n\n

How to block contact form spam

\n\n\n\n

1. Install the right WordPress anti-spam plugin

\n\n\n\n

The easiest and fastest way to combat contact form spam is to install the right anti-spam WordPress plugin. Anti-spam plugins work independently from your forms by comparing submissions to blocklists of words, names, IP addresses, and email addresses. They use both global and local learning to identify spam. Some also give you the ability to manually mark items as spam (or not spam), so it learns what you like and don’t like on your site. 

\n\n\n\n

With several options available, it’s critical to pick the right anti-spam plugin. Akismet is an excellent option used by millions of websites to filter out hundreds of millions of spam comments and form submissions. It will check all comments and form submissions for spam and filter out any that look suspicious. You can review all filtered submissions directly in the WordPress dashboard. 

\n\n\n\n

An option like this frees up your time to focus on the more critical parts of your website. It also gives you the peace of mind that your site, visitors, and reputation are safe. While there aren’t many disadvantages to this method, you’ll need to make sure you update the plugin as recommended to avoid any security issues in the future. 

\n\n\n\n

How to set up an anti-spam plugin:

\n\n\n\n

Installing a WordPress plugin is easy. In your WordPress dashboard, go to Plugins → Add New. Search for the one you’d like to add, then click Install → Activate. Then, follow any specific instructions for the tool that you chose. For example, Akismet provides a great how to activate tutorial with easy-to-follow instructions and visual cues. 

\n\n\n\n\n\n\n\n

2. Add a custom CAPTCHA

\n\n\n\n

Custom CAPTCHAs are another way to target and resolve spam problems. You can add a custom, word-based code or random math question to your website that visitors must answer to submit forms successfully. When users attempt to add a comment or submit a form, they’ll need to answer the question or type what they see above the submit button to proceed. You can add several custom word-based questions that users cycle through randomly. 

\n\n\n\n

While CAPTCHAs are a great way to combat spambots, they aren’t effective with human spammers. They can also be frustrating and time-consuming for legitimate site visitors who struggle to answer the questions or answer them incorrectly. If you choose to add a CAPTCHA to combat spam, you’ll also need to think about users with limited sight or other challenges. 

\n\n\n\n

How to implement a CAPTCHA:

\n\n\n\n

To add a CAPTCHA to your website, you’ll need to choose a service provider. Google is the most popular CAPTCHA service, with essential functions offered at no cost to website owners. You can find your options in the Products part of the Google Developers page. Make sure to sign in to your Google account. Next, you’ll read through a short overview before clicking on Sign up for an API key pair. You’ll need to fill in your website information and follow the prompts to complete the process. 

\n\n\n\n

3. Use Google reCAPTCHA

\n\n\n\n

Google’s reCAPTCHA is a more advanced option than custom CAPTCHAs. Initially introduced to overcome the user frustrations of custom CAPTCHAs, reCAPTCHAs require users to answer more straightforward questions to submit forms. reCAPTCHAs also work by detecting user behavior while visitors navigate your site and assigning each user a “spam score” based on what the tool considers suspicious activity. 

\n\n\n\n

The most common form of reCAPTCHAs is the picture puzzle you’ve seen on many websites. Instead of typing a word or answering a math question, users answer an image-based question. Visitors must select all the squares in the picture with a specific object like a car or a traffic light. Once all images have been selected, the button switches to allow the user to submit their form response. 

\n\n\n\n

Here are some other types of reCAPTCHAs:

\n\n\n\n
  • Checkbox reCAPTCHA v2 is a simple box that users must check to submit a form. It’s the popular option you see on many websites accompanied by the “I am not a robot” text.  
  • Invisible reCAPTCHA v2 does not display any visible fields to human users. Instead, it monitors user behavior for suspicious activity to identify potential spammers. Invisible reCAPTCHA also adds an extra field into the code of your form. Since most spambots use code to submit responses, these spammers automatically fill in the fake fields before being flagged. Human users never even notice the spam control as they submit answers directly on the form. 
  • reCAPTCHA v3 is an advanced option that uses JavaScript to detect human visitors. It is the most advanced form of reCAPTCHA, so you should only use it if you’re a WordPress expert. 
\n\n\n\n

reCAPTCHAs can still prevent genuine visitors from submitting forms, but they’ve improved from the earlier custom CAPTCHA options. Most come with the ability to add an audio option for those with visual impairments. The visible option they offer is also a solution for the hearing impaired. 

\n\n\n\nPhoto © Google\n\n\n\n

How to implement Google reCAPTCHAs:

\n\n\n\n

You’ll add reCAPTCHAs to your website following the same steps listed above for CAPTCHAs. Google reCAPTCHA is also a free service for basic functionality, but you can purchase the Enterprise solution for more advanced options. You’ll need to sign up for an API key pair for your site and follow the prompts to proceed.

\n\n\n\n

4. Use an IP access list

\n\n\n\n

If you notice a lot of spambot action on your website coming from specific sources, you can use an IP access list to block spam. With this method, you add IP addresses to a list that restricts access to your website from that location. You’ll do this by adding IPs to the Comment Blacklist section of the Discussion settings page in the WordPress admin. 

\n\n\n\n

Using an IP access list is an excellent option for blocking specific people. But it takes a lot of work to block a more significant number of spammers and requires constant maintenance. You can also accidentally block legitimate form submissions from the IP addresses you list, so make sure you’re confident before using this method. 

\n\n\n\n\n\n\n\n

How to implement an IP access list: 

\n\n\n\n

If you want to block an IP address, navigate to Settings → Discussion → Comment Moderation in your WordPress dashboard. Then, simply add any IP addresses you want to block and save your settings.

\n\n\n\n

5. Take advantage of the honeypot method

\n\n\n\n

If you’re not a fan of CAPTCHAs, try the honeypot method. Honeypots are little bits of code used to catch spambots. The code creates a hidden field in your form that’s invisible to human visitors but visible to spambots who are usually looking at the code of your form. Spambots automatically fill out the hidden field and submit the forms. The additional information flags these submissions and rejects them, saving you time and effort. 

\n\n\n\n

One advantage of honeypots is that they stay hidden from human visitors. Your visitors don’t need to deal with the inconvenience of CAPTCHAs. Some WordPress form plugins even allow you to add the honeypot method in their settings. 

\n\n\n\n

How to implement honeypot:

\n\n\n\n

Some plugins allow you to quickly check the option to add honeypot to your forms. But if they don’t, you’ll need to add a hidden field to your form manually. Once you add the form to your site, use the CSS style “display: none !important;” to make the field hidden and tabindex=”-1″ autocomplete=”false;” to ensure the field is empty by default. 

\n\n\n\n

Protect your WordPress contact forms

\n\n\n\n

Contact forms are a great tool to connect with your audience and enhance your website’s user experience. But they can also be a problem when spammers attack. Don’t be the target of human spammers and spambots that reduce the effectiveness of your website forms. Use the six steps listed above to successfully stop spam from your WordPress site so you can focus your time and effort on more essential tasks. 

\";s: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, 29 Dec 2021 12:28:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Simon Keating\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:75:\"WordCamp Central: The first in-person WordCamp Europe in 3 years is coming!\";s:7:\"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=3143787\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:102:\"https://central.wordcamp.org/news/2021/12/28/the-first-in-person-wordcamp-europe-in-3-years-is-coming/\";s: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:1047:\"

WordCamp Europe organizing team has shared what we are planning for the first in-person WCEU in 3 years.

\n\n\n\n

It’s taking place in Porto, Portugal, on 2-4 June 2022.

\n\n\n\n

With all safety measures, our beautiful spacious venue, Super Bock Arena can hold up to 4000 people, and we can’t wait to welcome you there.

\n\n\n\n

Call For Sponsors and Call For Speakers are already open!

\n\n\n\n

Subscribe to WordCamp Europe Newsletter to get to know about all WordCamp Europe 2022 updates first!

\n\n\n\n\"\"\";s: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, 28 Dec 2021 12:52:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Sabrina Zeidan\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:25:\"Matt: Saving the Internet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=55240\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://ma.tt/2021/12/saving-the-internet/\";s: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:1935:\"

David Pierce wrote a deep profile, over 4,000 words, for Protocol and asks the question in the headline, Can Matt Mullenweg save the internet?

\n\n\n\n\n\n\n\n

Which brings to mind Betteridge’s law of headlines (née Hinchliffe’s rule), “Any headline that ends in a question mark can be answered by the word no.”

\n\n\n\n

I can’t save the internet. But you know who can? A movement. A community of like-minded individuals, unified by a common philosophy, and working together to create tools of freedom.

\n\n\n\n

It’s a human right to be able to see how that technology works and modify it. It’s as key to freedom as freedom of speech or freedom of religion. So that is what I plan to spend the rest of my life fighting for.

\n\n\n\n

Working together we’ve created something special, unlike anything the internet has seen before, and I’m excited to continue.

\n\n\n\n

Thank you to David Pierce for taking such an in-depth look at the history of WordPress and Automattic and talking to dozens of sources. Thank you to the people quoted in the article: Scott Beale, Om Malik, Toni Schneider, Russell Ivanovic, Deven Parekh, Paul Mayne, and Anil Dash. Thank you to Arturo Olmos for the photos, and Odili Donald Odita for the amazing painting behind me.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 24 Dec 2021 13:07: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:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"WPTavern: Multiple State of the Word Attendees Test Positive for COVID-19\";s:7:\"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=127655\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:191:\"https://wptavern.com/multiple-state-of-the-word-attendees-test-positive-for-covid-19?utm_source=rss&utm_medium=rss&utm_campaign=multiple-state-of-the-word-attendees-test-positive-for-covid-19\";s: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:6225:\"
State of the Word 2021 in NYC
\n\n\n\n

Matt Mullenweg’s 2021 State of the Word address was held in New York City nine days ago with a live studio audience. On Sunday, December 19, all in-person attendees were notified by email that they were possibly exposed to COVID-19 after one of the attendees tested positive.

\n\n\n\n

Although proof of vaccination was required at the door, multiple people have reported recent infections after traveling home from the event. Aaron Jorbin tweeted about his case today, and four more have been reported in a private channel on Post Status Slack.

\n\n\n\n
\n

I don\'t know where I actually got infected, State of The Word is just one possibility and it being \"swag\" is a good joke. A great joke even.

— Aaron Jorbin (@aaronjorbin) December 23, 2021
\n
\n\n\n\n

There’s no way to know for certain whether the attendees who contracted COVID-19 caught the virus at the State of the Word, as many of them traveled from far away places and had meetups with other attendees outside of the main event.

\n\n\n\n

Concerns about the lack of masks and no requirement for rapid tests began popping up prior to the event. From the perspective of viewing the livestream, masks were scant and attendees were quite close together in a small space.

\n\n\n\n
\n

Anyone tracking the COVID cases coming from the #StateOfTheWord ?

Hate to be a downer, but it’s still a raging pandemic and all those people traveling from all over and in groups without masks has my anxiety spiking.

— Pandemically Joshua \"💉\" ³ (@onemorejosh) December 14, 2021
\n
\n\n\n\n

The day before the event, the WHO warned that evidence suggested the new Omicron variant could escape prior immunity and would lead to surges with a high transmission rate. Studies were already showing reduced effectiveness of existing vaccines against the variant. On December 13, New York governor Kathy Hochul announced a new temporary indoor mask mandate for public spaces, which could be bypassed by requiring vaccines for entrance.

\n\n\n\n

When asked how the State of the Word’s coordinators decided on the precautions, WordPress Executive Director Josepha Haden Chomphosy said the event met the local guidelines while allowing attendees to make their own choices for anything beyond the requirements.

\n\n\n\n

“We followed the guidelines as laid out by the city,” Haden Chomphosy said. “Masks and hand sanitizer were liberally available throughout the venue, and we encouraged attendees to make informed decisions about their health.”

\n\n\n\n

It has been well-documented that indoor masking can significantly reduce transmission, so it was curious that the event did not require them at this pivotal time when governments are taking more stringent measures to stop the spread of the virus.

\n\n\n\n

Fortunately all those who were recently infected have reported mild illnesses, but the incident raises an important question for onlookers: Is this an indicator of how in-person WordCamps are going to go in 2022? There are already several on the schedule.

\n\n\n\n
\n

Agreed. It has definitely killed any thought I had of attending a WordCamp for a good long while.

— Chris Wiegman (@ChrisWiegman) December 23, 2021
\n
\n\n\n\n

Whether or not attendees’ infections originated at the State of the Word or in outside gatherings is going to be impossible to pinpoint, but the nominal safety protocols sends a message to all those considering attending in-person events in 2022.

\n\n\n\n

Since receiving the notification of possible exposure, many State of the Word attendees have been monitoring their health with tests. One attendee reported in Post Status Slack that she has had difficulty getting tested and is still waiting for one in the mail. In the meantime, she has opted out of a family gathering for Christmas as a safeguard.

\n\n\n\n

“As someone who wants nothing more than to be able to attend WordCamp Europe or WordCamp US in person next year this doesn’t give me much confidence,” Gravity Forms CEO and co-founder Carl Hancock said. “With such a small event the COVID protocols could and should have been super tight to test things out for larger events. The lack of masks and social distancing at an indoor event without added protocols such as rapid testing for entry was disappointing to see.”

\n\n\n\n

WordCamp organizers will need to consider how they can protect attendees beyond simply meeting the basic, local requirements, which may not fully acknowledge the nature of the current threat. They will also need to be responsive to the rapidly changing pandemic landscape and be ready to implement more safety protocols at the last minute, if necessary. If the State of the Word is any indication, future WordCamp organizers will need to have a plan for sending exposure notifications to attendees, in case the events become the source of an outbreak.

\";s: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, 24 Dec 2021 04:38:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:35:\"BuddyPress: BuddyPress 10.0.0-beta2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=322588\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"https://buddypress.org/2021/12/buddypress-10-0-0-beta2/\";s: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:3714:\"

Hello BuddyPress community!

\n\n\n\n

\"🎶\" All BuddyPress wants for Christmas\"🧑‍🎄\" is you \"🎵\" … to test this new pre-release!

\n\n\n\n

If you haven’t tested our first 10.0.0 beta release, here’s another opportunity to help us put the final touches on our next major release so that we make sure it will fit perfectly into your WordPress-/ BuddyPress-specific configuration.

\n\n\n\n

Beta testing is very important, and we need you all, whether you’re a novice or an advanced user, a theme designer or a plugin author. Please contribute \"🙏\".

\n\n\n\n
\n\n\n\n
\n
Try BuddyPress 10.0.0-beta2
\n
\n\n\n\n
\n\n\n\n

What has changed in 10.0.0-beta2?

\n\n\n\n
  1. Custom Group Extensions: if you activated one or more plugins adding a new tab to your groups or if you built one or more plugins playing with the Group Extension API. It’s very important you take some time to make sure everything is working as expected in this area.
  2. Contribute to WordPress 5.9 beta tests as well! Let’s all check that BuddyPress pages are getting along well with Twenty Twenty-Two, the next WordPress default theme.
  3. The Private Messages component just got a new feature: messages thread exit. Users can now remove themselves from a conversation.
\n\n\n\n
\n\n\n\n

How to get 10.0.0-beta2?

\n\n\n\n\n\n\n\n
\n\n\n\n

The final release is slated for early January and we need your help to get there: please test 10.0.0-beta2. If you find a bug, please report it on our Trac or as a reply to this forum topic.

\n\n\n\n

The BuddyPress core team is wishing you all: Merry Christmas \"🎄\"

\";s: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, 23 Dec 2021 22:14:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:94:\"WPTavern: WordPress 5.9 Beta 4 Fixes 20 Bugs, Polishes Workflow for Switching to a Block Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127650\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:231:\"https://wptavern.com/wordpress-5-9-beta-4-fixes-20-bugs-polishes-workflow-for-switching-to-a-block-theme?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-9-beta-4-fixes-20-bugs-polishes-workflow-for-switching-to-a-block-theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3004:\"

WordPress 5.9 beta 4 was released this week with fixes for 20 bugs since beta 3. There are a few important changes to note in this release regarding how the WordPress admin will direct users who are exploring block themes.

\n\n\n\n

Prior to a fix in beta 4, it was possible for users to switch to a block theme within the Customizer. This has been changed so that users will see a banner notifying them that the block theme is incompatible, if they try to switch within the Customizer. Here’s the commit message:

\n\n\n\n

Starting in 5.9, block themes are not compatible with (do not support) Customizer; rather, they use the Site Editor. Viewing installed themes in Customizer, this commit adds an overlay message to alert users and give them a way to activate the block theme. Clicking on the “Activate” button activates the block theme and redirects back to the Appearance > Themes interface, where the user can then enter the Site Editor for customization.

Non-block themes are not affected by this change and continue to work in Customizer.

\n\n\n\n

Having themes work only in the site editor or the Customizer, depending on which they support, is likely to be a confusing workflow for users when testing themes. This incompatibility message and redirection is necessary but not ideal for the long term. Streamlining the customization workflow will depend on how quickly the WordPress community is able to produce and adopt block themes.

\n\n\n\n

Some testers also reported that the Site Editor doesn’t allow users to edit or preview non-active block themes. The preview only works with active themes. This isn’t necessarily a bug but rather a feature that needs to be discussed for the future. A ticket is open in the Gutenberg repository, recommending the implementation of a Live Preview for non-active block themes.

\n\n\n\n

Featured patterns from the pattern directory should be displayed under Patterns in the the block inserter, but for some reason this wasn’t included in 5.9. It has been backported in beta 4.

\n\n\n\n

This beta also adds a filter that allows developers to disable the login screen language switcher, which is a new feature coming in 5.9.

\n\n\n\n

The release team has determined that a fifth beta will not be necessary, as of yesterday’s core dev chat. The revised 5.9 release schedule has RC1 shipping on January 4, 2022, and the official release on January 25.

\";s: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, 23 Dec 2021 18:42:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: WP Engine Acquires Brian Gardner’s Frost, Opens It to the Public\";s:7:\"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=127547\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:189:\"https://wptavern.com/wp-engine-acquires-brian-gardners-frost-opens-it-to-the-public?utm_source=rss&utm_medium=rss&utm_campaign=wp-engine-acquires-brian-gardners-frost-opens-it-to-the-public\";s: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:7120:\"\n\n\n\n

Brian Gardner announced today that WP Engine has acquired his latest project, Frost. In an email sent out to all customers, Gardner said his team had issued refunds to all current customers. The business model is changing, and Frost will be a freely-available project going forward and focus on full site editing.

\n\n\n\n

Frost is a WordPress theme that Gardner released earlier this year as the main product of a new startup business. The original version was shipped as a child theme of Genesis, the StudioPress theme framework he had spent much of his WordPress career working on. WP Engine acquired StudioPress in 2018, and Gardner stepped down from his role in October 2019. It did not take him long to find his way back into the WordPress theme development game, bringing his personal style back to the theming world with Frost. Then, he landed a new job within WP Engine’s ranks in September.

\n\n\n\n

“I am leading the WordPress Developer Relations team at WP Engine,” he said. “We have a simple mission: Accelerate innovation in WordPress and help the community transition to the block editor and Full Site Editing (né Gutenberg). In addition, we want to cultivate an interactive and immersive community resource that serves as a treasure chest of knowledge and operates as a conduit between the WordPress project and its users.”

\n\n\n\n

I asked if there was something concrete he could share, maybe what form that would take, but he did not go into any other details. In general, the more resources the development and design community have around the block system, the faster the ecosystem can evolve. Only time will tell what Gardner’s team within WP Engine creates.

\n\n\n\n

“When I joined WP Engine in late September, it was evident to me [WP Engine] saw the value in building relationships with designers, developers, and creators — within our Atlas product line, as well as with WordPress,” said Gardner. “While there was interest in Frost when I came on board, it wasn’t until my vision for our team became clear did an acquisition enter the picture. I recommended bringing Frost into the company and hiring Nick Diego.”

\n\n\n\n

Diego is the creator of the Block Visibility and Icon Block plugins. He also began working on Frost in late September.

\n\n\n\n

“In alignment with WP Engine’s core value of ‘Committed to Give Back,’ Frost is transitioning from a paid product to a free one,” said Gardner. “Given the change in business model, we issued full refunds to all active customers. By open-sourcing Frost and focusing on Full Site Editing, we hope to encourage a community of builders to experiment with the expanding capabilities of the block editor. We believe in its potential and look forward to helping it grow.”

\n\n\n\n

Frost is open to everyone via the WP Engine themes repository on GitHub.

\n\n\n\n

Leaping into Block Theming

\n\n\n\n

When Gardner sold StudioPress in 2018, several factors played a part in the decision. Among them were the uncertainty around the Gutenberg project and WordPress’s future.

\n\n\n\n

“It took some time for me to put the pieces together, but when I did, I saw just how powerful the block editor has become,” he said. “In particular, I am excited about block patterns, global styles, and building themes that folks can use to create beautiful websites with little effort.”

\n\n\n\n

The result of his newfound enthusiasm around the block system was Frost. I have had the opportunity to tinker around with the theme. It has Gardner’s signature minimalist design style, a focus on readable typography, and ample breathing room for the content.

\n\n\n\n

Simpler designs almost feel par for the course with any block theme these days, regardless of the theme author. What is likely to set Frost apart is its block patterns. It currently ships with 38 of them. The layouts should allow users to quickly set up their sites, along with the theme’s custom block styles.

\n\n\n\n

“I am a huge fan of block patterns and see their potential when paired with the growing support of design/style elements within theme.json,” said Gardner of the things he is excited about. “Additionally, the site editor is something I feel, once mature, will be a game-changer for WordPress and those who build for it.”

\n\n\n\n

The Block Pattern Explorer plugin was initially a part of the Frost library plugin, but Gardner and Diego pulled it out and make it available to everyone. They also wanted to serve the Frost patterns through it. The hope is that the enhancements already in place via the plugin find their way into core WordPress.

\n\n\n\nFrost theme patterns via Block Patterns Explorer\n\n\n\n

The design is a bit more polished than core. It includes category types, a feature the theme uses to separate its own pattern categories from others. The experimental explorer plugin allows users to preview patterns via desktop, tablet, and mobile views. And, it has a clear “Add Pattern” button for inserting a block pattern into the post.

\n\n\n\n

Eventually, they plan to sunset the plugin once its features make their way into WordPress.

\n\n\n\n

WordPress theming has come a long way since Gardner first dove in over a decade ago. Back then, users had to open template files to customize bits and pieces of their homepage. As we move toward WordPress 5.9, users will have that same power. However, they will modify Frost via the WordPress site editor instead of PHP files.

\n\n\n\n

“Yes, I feel we are circling back to some degree,” he said. It was in response to a question of his early days designing themes for WordPress in comparison to now.

\n\n\n\n

“While WordPress will never be solely a blogging platform ever again, it seems like the software is shedding its skin. The irony here is that we see WordPress used in sophisticated ways that — to be honest — I never thought would be possible. As for me, I believe in the power of simplicity. That has become my north star for everything I create and has allowed me to navigate the ebbs and flows of an ever-changing software and industry.”

\";s: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, 23 Dec 2021 15:35:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:68:\"Akismet: Do CAPTCHA and reCAPTCHA Protect WordPress Sites from Bots?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"http://blog.akismet.com/?p=2164\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://blog.akismet.com/2021/12/23/do-captcha-and-recaptcha-protect-wordpress-sites-from-bots/\";s: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:17231:\"

If you’ve used the internet anytime in the last decade, chances are you’ve had to pass a CAPTCHA or reCAPTCHA test. You may have done so many of these little quizzes that you groan just seeing one on a form.

\n\n\n\n

There are quite a few different versions, but they all can help protect your WordPress website from spambots and make your life simpler.

\n\n\n\n

In this post, we’ll cover the evolution of CAPTCHA and reCAPTCHA. We’ll also go over the different versions and the pros and cons of each one. Then, we’ll show you how to enable reCAPTCHA on WordPress and explore additional security measures you should implement.

\n\n\n\n\n\n\n\n

What are CAPTCHA and reCAPTCHA?

\n\n\n\n

CAPTCHA and reCAPTCHA serve the same purpose: protecting your website against bots and other security threats. They’re typically found on contact, comment, login, and password reset forms. But there are some key differences between the two safety checks. Let’s take a look at each one in detail. 

\n\n\n\n

What is CAPTCHA?

\n\n\n\n

The acronym CAPTCHA stands for Completely Automated Public Turing Test to Tell Computers and Humans Apart. It’s a mouthful, but the name says it all — it can decipher the difference between a human and a computer operator. Still, the specifics are important.

\n\n\n\n

In the early 2000s, when it was created, CAPTCHA used a distorted text (letters and numbers) test to prevent bots from compromising websites.

\n\n\n\n

When faced with a CAPTCHA, users needed to decipher broken text correctly to prove that they were, in fact, human. If they couldn’t identify the letters and numbers, the test wouldn’t submit their requests. 

\n\n\n\n

This was revolutionary because most humans could pass it easily, but computers couldn’t solve it themselves. 

\n\n\n\n

What is reCAPTCHA?

\n\n\n\n

reCAPTCHA follows a similar principle, but instead of just utilizing meaningless text to see if the user is a real human, it was designed to help computers digitize old books and newspapers. The test was essentially split into two parts shown side-by-side — one traditional CAPTCHA to determine the humanity of the user, and a second image of letters from a piece of text the computer was trying to digitize. If the human could pass the first part, it would accept the user’s input for the second part as an accurate translation. 

\n\n\n\nPhoto from http://www.captcha.net/\n\n\n\n

The point is that reCAPTCHA added a second part to the test to put millions of human users to work — a few seconds at a time — to digitize historical text for ongoing record keeping. Now sites were protected from bots and users weren’t totally wasting their time. 

\n\n\n\n

Google purchased the technology in 2009 and improved upon it over the years. You see, artificial intelligence (AI) eventually became sophisticated enough to read and decipher even the most challenging text with 99.8 percent accuracy. By doing so, they could pass the test and trick it into thinking bots were humans. 

\n\n\n\n

To deal with this new issue, reCAPTCHA made things even more challenging, introducing new options like the famous “I’m not a robot” check box. 

\n\n\n\n\n\n\n\n

Today, reCAPTCHA is a widely-used security measure that protects websites from various spambots and cybercriminals by helping to ensure that comments on blog posts or in forums, and submissions on forms come from real people. 

\n\n\n\n

What are the different versions of reCAPTCHA?

\n\n\n\n

There are technically four different types of active reCAPTCHAs. Instead of text, some tests may use images, audio, or even math equations. They also utilize some variation of  “No CAPTCHA reCAPTCHA”, which determines whether a user is suspicious simply based on their behavior on a site.

\n\n\n\n

If you’re setting up WordPress website security, you may have the option to choose between different reCAPTCHA types. For example, you can select a checkbox or background verification:

\n\n\n\n\n\n\n\n

Here are the different types of reCAPTCHA:

\n\n\n\n
  • ReCAPTCHA v2 (“I’m not a robot” checkbox): This is the simplest and easiest test to add with limited coding knowledge. Sometimes it passes or approves users right away and prompts them to check a box. Other times, it asks them to verify that they’re human with a puzzle challenge.
  • ReCAPTCHA v2 (Invisible reCAPTCHA badge): For this version, there’s usually no checkbox. It simply uses an existing button on your site or a JavaScript API call for verification. You’ll see a badge that says Protected by reCAPTCHA. Essentially, verification happens in the background. Only the strangest behavior will prompt a test.
  • ReCAPTCHA v2 (Android): This version utilizes a reCAPTCHA Android library that’s part of Google Play’s SafetyNet APIs. This validates requests from within an Android app, so it’s not the right choice to use for a WordPress site. 
  • ReCAPTCHA v3: This is the most advanced and discreet of all the versions. Visitors won’t even know it’s happening. It uses a JavaScript API and automatically assigns a score to each user to approve or deny them. This version also gives more advanced developers extended flexibility for integrations with other security measures to dictate the level of site security. 
  • ReCAPTCHA Enterprise: Like v3, this runs in the background. It gives each site visitor a score based on their behavior. If a visitor is deemed suspicious, it may require them to verify their identity through custom options determined by each site — two-factor authentication or email verification. As its name implies, this is typically for enterprise-level sites and requires advanced customization.
\n\n\n\n

What should I consider when choosing a reCAPTCHA version?

\n\n\n\n

Since reCAPTCHA Enterprise is reserved for larger companies, it’s safe to say that most websites will need either reCAPTCHA v2 or reCAPTCHA v3. Still, it’s important to know what you’re getting into with each one. 

\n\n\n\n

What are the pros and cons of reCAPTCHA v2? 

\n\n\n\n

The most significant advantage of reCAPTCHA v2 is that, whether you choose to include the “I’m not a robot” checkbox or leave it discreetly running in the background, it protects you from spam while offering humans the opportunity to prove that they’re real. 

\n\n\n\n

With the invisible version, if it detects suspicious behavior, it will require a test. If it doesn’t, the user can proceed none the wiser. 

\n\n\n\n

However, any reCAPTCHA v2 test can seriously hurt the user experience for site visitors. To combat increasingly smart AI technology, tests have become so tricky that many real humans have trouble passing.

\n\n\n\n

The test’s difficulty may leave users frustrated, wondering why they fail when they are actual humans. In fact, the situation has become so bad that popular tech magazines give people tips on passing these tests.

\n\n\n\n

Plus, it’s also important to consider the accessibility of reCAPTCHAs. A graphical puzzle, for example, would be inaccessible for people who have vision impairments. So, if you do decide to use reCAPTCHA v2, it’s important to present other options, like audio or text-based tests.

\n\n\n\n

What are the pros and cons of reCAPTCHA v3?

\n\n\n\n

reCAPTCHA v3 was specifically designed to improve the user experience. With no verification tests to complete, it’s seamless. Website visitors are happily unaware of the entire process. 

\n\n\n\n

It also gives administrators much more control. With reCAPTCHA v3, you have advanced options to customize your interaction with Google’s API to adjust scoring thresholds and define what is considered suspicious behavior. 

\n\n\n\n

Some may consider this added control a good thing, while others may find it a weighty and cumbersome responsibility. Additionally, some critics believe that reCAPTCHA v3 may pose a privacy risk because it provides Google with too much data. 

\n\n\n\n

In addition, reCAPTCHA v3 can deter good bots from doing important work. People tend to remember the villains like spambots, but forget about their positive counterparts. Good bots deal with things like SEO and performance monitoring. If you get in their way, your overall website success could suffer. 

\n\n\n\n

A final downside is that, since spam scoring happens in the background, there’s no alternative test provided to suspicious users (like with the invisible reCAPTCHA v2 badge). Visitors who are wrongly flagged as bots don’t have an opportunity to prove their legitimacy. This means that you could turn away real customers, clients, and followers.

\n\n\n\n

Can bots bypass reCAPTCHA?

\n\n\n\n

This is the big question. Unfortunately, the answer may not be straightforward or definitive.

\n\n\n\n

The many versions of reCAPTCHA are evidence that malicious spambots evolve quickly.

\n\n\n\n

They’re constantly adapting to outsmart reCAPTCHA. When the original CAPTCHA was introduced, it was revolutionary in its ability to decipher between real users and bots. But it didn’t take long before the bots caught on. People have even started using human labor to get past tests manually. 

\n\n\n\n

Computer scientists are regularly working to increase the effectiveness of reCAPTCHA, however. Some have proposed new challenges, like puzzles that require a user to maneuver pieces or nursery rhyme completion games based on the location of site visitors.

\n\n\n\n

That’s one major reason tests have become so frustrating for real users — difficulty has had to increase to stay ahead of computer learning. Unfortunately, it seems we’re at a point where to continue to outsmart computers, we have to make tests that are sometimes too difficult for real users to solve — a major problem. 

\n\n\n\n

It’s gotten so bad that Amazon now owns a patent for a new kind of CAPTCHA-esque test that is so difficult to solve that only a computer can do it. Meaning… if you pass, you’ve actually failed because you’ve proven that you can’t possibly be human. 

\n\n\n\n

So can reCAPTCHA stop bots? 

\n\n\n\n

Yes, it can stop many of them. But it can’t stop them all. And the percentage of bots that make it through is increasing by the day. This means you can’t simply rely on reCAPTCHA to prevent spam submissions. You’d be signing up for a highly imperfect, temporary system that’s only going to get less effective. 

\n\n\n\n

So what should you do? 

\n\n\n\n

Other security measures to protect your website from spambots

\n\n\n\n

1. Lock down your comment forms

\n\n\n\n

The best place to start is by configuring your WordPress comments in a way that protects your site against bots. Navigate to Settings → Discussion in your site dashboard and and consider requiring:

\n\n\n\n
  • Comment authors to submit a name and email
  • Users to be registered and logged in to comment
  • Comments to be manually approved before publication
  • Authors to have a previously approved comment to submit a new one
\n\n\n\n

In the Comment Moderation box, you can also flag a comment that contains a certain number of links — lots of links is a common indication of spam. Or, if you’re getting a lot of spam that contains certain words, email addresses, IP addresses, and other characteristics, you can ban them entirely.

\n\n\n\n

2. Protect your login forms

\n\n\n\n

To lock down your login forms without using a CAPTCHA, you can implement two-factor authentication. This requires a user to have both login details and a physical device to access your site. When someone logs in, they’ll have to enter a username and password as well as a one-time code that’s sent to the mobile device on file. This is virtually impossible for bots to get past.

\n\n\n\n

3. Use honeypot

\n\n\n\n

Honeypots are an option for protecting contact forms. Think of them as a mouse trap for bots. They essentially create a hidden field in your forms that isn’t visible to site visitors but that can be seen by spambots. If the field is filled out, the bot is stopped in its tracks.

\n\n\n\n

Many contact form plugins allow you to implement this feature in their default settings.

\n\n\n\n

4. Protect your comment and contact forms with Akismet

\n\n\n\n

Akismet is hands-down the best way to eliminate the headaches of bots (or even real humans) spamming your comments or sending unwanted messages through forms on your site. 

\n\n\n\n

With millions of users, Akismet has blocked over 500,000,000,000 spam submissions at the time of writing this article. With each one, it learns a bit more. So while bots might have AI to get past reCAPTCHAs, Akismet’s AI is working to protect your site in an entirely different way. 

\n\n\n\n

Akismet can accurately identify spammy behavior and keeps a blocklist of words, IP addresses, names, and emails to prevent pests. Plus, it gives you control to provide feedback about any spam it misses or real comments that it accidentally flagged. Then, it customizes its spam-fighting solution just for your site. Amazing. 

\n\n\n\n\n\n\n\n

You can get a free version of Akismet for your personal blog. In addition, there are three paid plans for commercial sites starting at just $10 per month. 

\n\n\n\n

Win the fight against spam bots

\n\n\n\n

Spam bots and less-than-ethical cyber actors are always trying to take advantage of visitors and the sites they love (like yours!). They can cause annoyance or even do real-world damage.

\n\n\n\n

CAPTCHA and reCAPTCHA have evolved many times over the years and continue to be one trusted way to prevent bots from flooding sites. But these solutions aren’t perfect, and sites need other measures to prevent spam from causing trouble. Consider protecting login forms with two-factor authentication, deploying WordPress best-practices, and using Akismet to filter comment and contact form submissions automatically. 

\";s: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, 23 Dec 2021 10:25:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Simon Keating\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:77:\"Post Status: Post Status Excerpt (No. 38) — In Person For State of the Word\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=91657\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/excerpt/38/\";s: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:38726:\"

“I believe our community can make significant contributions to Gutenberg and the Block Editor.” —Cory Miller

\n\n\n\n

In this episode of Post Status Excerpt, Cory shares his experience among the 30+ individuals who attended the State of the Word in New York in person. David and Cory talk about how Matt presented himself, his views on the necessary ratio of community contributions to open source projects, Five for the Future, the next generation of leaders, and what it means to give back to the community and WordPress core.

\n\n\n\n

Also: Cory hints at what Post Status will be doing in 2022 when it comes to giving back — along with how Post Status will encourage and assist people in contributing to the WordPress community.

\n\n\n\n\n\n\n\n

Every week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash. \"⚡\"

You can listen to past episodes of The Excerpt, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS. \"🎧\"

\n\n\n\n

\"🔗\" Mentioned in the show:

\n\n\n\n\n\n\n\n

\"🙏\" Sponsor: Yoast SEO

\n\n\n\n

Yoast is SEO for everyone. Yoast SEO Premium gives you 24/7 support and extra features like internal linking, social previews, a redirect manager, tutorial videos, and integration with Google Webmaster Tools. Get on board today with the premiere SEO plugin for WordPress — Yoast.

\n\n\n\n

Transcript

\n\n\n\n

David Bisset: [00:00:00] Since I wasn\'t there because as I was telling somebody earlier, I couldn\'t, hurt my Twitter game by being there. I had to be in front of my computer with with my keyboards and making a bingo games and hashtag 

\n\n\n\n

Cory Miller: that\'s my fondest memories of you, David is like going to these events and somebody live tweeting.

\n\n\n\n

It\'s like, here\'s this dimension media person. And it\'s like, holy crap. 

\n\n\n\n

David Bisset: Yeah. They used to call me dementia media. So. 

\n\n\n\n

Cory Miller: Signature though is still in the lodge waiting. And I remember when Twitter kind of first came out and it was a thing to live tweet a lot. And but I always like yours because you always summarize what.

\n\n\n\n

The takeaway is like you\'re starring the cool quotes along the way. And that\'s part of what we\'re trying to do at post status is give you the too long, didn\'t read content, the inside analysis commentary for the stuff that matters to you. So that\'s your claim to fame or friend? 

\n\n\n\n

David Bisset: Yeah. Yeah.

\n\n\n\n

Well, that\'s how I took notes and I really didn\'t care who listened. I that\'s how I just took [00:01:00] notes. It kind of knocked off a couple of killed a couple birds with one stone, but enough about me. Let\'s. Let\'s talk about you being there in person. And can you tell me where this place w what was this place like?

\n\n\n\n

Was it in like a tall building or like, I hear it was tumblers all the offices or something. 

\n\n\n\n

Cory Miller: So my understanding was it\'s the automatics new event space in New York city. And of course, some of their investors in New York city and things like that. And it was incredible space. I would try to guess how big of a space it was.

\n\n\n\n

David Bisset: I couldn\'t tell, the camera angles were just, they did the camera angles just right. So you never got a true dimension of the room on the live stream

\n\n\n\n

 yeah, that\'s 

\n\n\n\n

Cory Miller: what I just said. I do more tell me I bet you it\'s about 15,000 to 20,000 square feet in there that I saw really great space. And it\'s a whole floor of a billion is my understanding, but it was gorgeous.

\n\n\n\n

And then there\'s the sunset of New York city out the window rep for state of the word. And it was really good, but I. I, you know, I got to see [00:02:00] Matt about a month ago and San Francisco, we got to talk and he mentioned inviting you David, to stay the word. And also he\'d love to have Post Status there. So I was like, yes, we\'re going to make that happen.

\n\n\n\n

I know you had things that come up, you couldn\'t be there. But you know, I want to guess there\'s about 25 30 people there in person. And it was a really nice night. I mean, automatic. Rolled out the carpet for all of us, which is super nice. Matt as always is a charming, elegant presenter and host and did a fantastic job.

\n\n\n\n

I thought it was normal. You know, I want to give him kudos, but like, he\'s really good on stage. 

\n\n\n\n

David Bisset: Well he was different this time and I realized I wasn\'t in the room, but I almost had, I have a 30 inch monitor. So I saw a lot of him and I saw a lot of his facial expressions pretty clearly. There was there was something different about them in a good way.

\n\n\n\n

And I can\'t, I think he, you know, not just not to put emotions on a person, I\'m pretty sure he was nervous in some regard. I think anybody is nervous to some extent of public speaking, but he definitely had some sort of [00:03:00] energy that he was releasing. And you know, me, I record animated gifs all the time.

\n\n\n\n

I decided not to post, I don\'t know what I decided to post, but in the very beginning before he was kind of. He was almost dancing a jig right before way before the state of the word started up on stage. So he was really excited and really, you know, anxious maybe, but you could just see the energy even before he spoke anything.

\n\n\n\n

You could just see the pent up energy that he had, which was reflected later, by the way. 

\n\n\n\n

Cory Miller: And not trying to speak for him, but if for me, I go, I haven\'t done this in two years. There\'s some cool people here that I have invited to be here and I\'m talking about the thing that I want to spend all of my life doing.

\n\n\n\n

And so. Yeah, totally. I spoke a couple of weeks ago at our three recurring revenue retreat. And I remember getting feeling nervous cause I\'m like I was rusty, you know? And there was this quote and I\'m trying to remember what it was, but it\'s basically turning fear, the anxiety into [00:04:00] energy and excitement.

\n\n\n\n

And that\'s what I tried to do is like channel that\'s now Matt doesn\'t need my public speaking tips, but those are my thoughts. What I. As long as I\'ve known him. And it goes back to 2008, where camp DFW in Frisco, Texas. There\'s one thing that\'s always standard with Matt and that is his passion for the WordPress open source project.

\n\n\n\n

Yeah. So, you know, and it just has never wavered. And I think he mentioned on state of the word that he wants to spend the rest of his life. He\'s 38 rest of this. On WordPress project. And I totally believe this. This is his contribution to humidity, you know, and at Post Status makers of the open web WordPress, this 42% of this big number that he shared out there, I think we should all take a moment, take a big deep breath and go.

\n\n\n\n

The web is still in its infancy. I don\'t know, life-stage wise where it would be comparatively to like a human, but it\'s still early, like in history of all that\'s going to happen in this world. In the future, the web is [00:05:00] still kind of an infant. And if you think about it, our place is WordPress makers.

\n\n\n\n

People that build on WordPress, extend WordPress, teach WordPress, all that stuff people have. Post-test the business to WordPress is this is historic and what we\'ve been doing. I started with WordPress, my first blog in 2006. That was just me using this amazing platform called WordPress, but, you know, history historically sake and going through.

\n\n\n\n

42%, that number, it just keeps getting bigger. And that\'s exciting for us, those of us that make our living with on for WordPress. 

\n\n\n\n

David Bisset: Yeah, he did. I got a couple of quotes out of them and it was, you know, livestream is a little bit easier. Cause you can pause and rewind a little bit just to make sure, because you want to get it as close as possible. Regarding the The WordPress space.

\n\n\n\n

He did say the court word press belongs. Just, you know, just to anybody it\'s not just you or me it\'s regardless of economic or political situations. And he said something about WordPress can\'t be [00:06:00] created by just one company and people adding a line of code is like giving that, give a penny, take a penny and I feel like there\'s quite a number of people that thanks to five for the future that are giving that he was, he actually said he actually gave a quote or something about, I don\'t know if you caught it. He was studying other CMSs. And he said for every dollar that has made $20 has made in the ecosystem.

\n\n\n\n

And that\'s ratio is how they came up with the five for the future. Did you know that. I did not. 

\n\n\n\n

Cory Miller: You know, I don\'t know how long, far, because the future has been out, but there\'s two things I wanted to highlight. Part of State of the Word you\'ve just put a square in this one, which is contributing back to core five for the future.

\n\n\n\n

I don\'t know how long that\'s been going, but, you know, I know our Post Status members. I mentioned this to Matt. They, you know, like me and I themes, we had, let\'s say at her height, I want to say 27, 28 people or something like that. And you go, okay, how do we, excuse me, our team or company contribute to core.

\n\n\n\n

We don\'t have the profit bandwidth, all that stuff to take a full-time dev for instance 

\n\n\n\n

David Bisset: right

\n\n\n\n

Cory Miller: [00:07:00] off. And I mentioned this because I know there\'s so many giving hearts in WordPress and founders and entrepreneurs and people that lead companies. That benefit from WordPress that want to do five for the future.

\n\n\n\n

It\'s tough. I get it from your standpoint of how do we meaningfully contributed, even though we believe we are contributing to the ecosystem or what we\'re doing. And I grant that a hundred percent, what we want to do at Post Status though I did tag on the contributions that push to continue to contribute to core. 

\n\n\n\n

I think that\'s the reflective I dunno, KPI for the ecosystem too, by the way. But, and I know there\'s companies that do it, even if it doesn\'t fall under the strict banner of farm from feature or whatever it is that like, they\'re doing it just like, we felt like we were contributing to WordPress for years.

\n\n\n\n

What I want to do is translate that help that better for our Post Status crowd to, to actually meaningfully contribute. So Courtney Robertson on our team, who is also great, awesome person at Go Daddy pro is really [00:08:00] taking the banner for the contributor days for post status. So next year, we\'re going to be talking about enrolling out contributor days, but that\'s one thing to say, we\'re going to do a contributor day, right?

\n\n\n\n

That\'s nothing new. This is where Courtney\'s idea was. Let\'s go to the team leads and ask for their wishlist. Things they would love for people of post status to contribute. And from that gives us something that we can go. Let\'s say we take that day eight hours. And we\'re going to show up for contributor today. at Post Status, were gonna, make it a contribute and then pick something off the board.

\n\n\n\n

So we\'re already trying to help you do a little thinking in the stuff that\'s going to be most valuable to the core team, core teams that are doing things, and then say pick one off the list and try to get as far as you can. You know, and I\'m excited about that. I know it\'s very meaningfully and for good reason to Matt, both as CEO of automatic, but also the leader of the WordPress open source project.

\n\n\n\n

And that was one thing that for sure came out, you know, to me in that call.

\n\n\n\n

David Bisset: Yeah. There, [00:09:00] there was quite a bit talk about, there was talk about the contributors earlier in the live stream. And then afterwards it was how to get new and especially young people involved and you know, young people, they have so many distractions these days, but they have more time and they more energy.

\n\n\n\n

Then we do cause we were running, families were running businesses and so forth like that. And I liked the question that Allie posed about. How can these people learn WordPress? But contributing I, you know, I, I lost my thought there for a second, but I really wanted to. I was hoping that the five for the future was going to spark some more ideas.

\n\n\n\n

And I think it will, because if you have people that are, if companies are being sponsored or sponsoring people to work on contributing and there should be. Like an on-ramp in there somewhere for people who want to get into it too, because you know, like many people have pointed out. You have to, unless you\'re a young person within, [00:10:00] with an inordinate amount of time, you don\'t have the time to do that.

\n\n\n\n

So even for a couple of hours, and I think part of five for the future, and some people have brought this, you know, written about it after state of the word. And about that five for the future, maybe someday five for the future can be expanded a bit to help some people not only contribute, but also kind of help them find people are willing to cover them so they can contribute whether that\'s financially or some other means.

\n\n\n\n

Or maybe it\'s just some sort of internship if somebody is brand new and needs to be exposed to anything in WordPress. So I think five for the future is a great thing now, and I think it has got room to grow, but you know, it needs that it needs. Momentum of support right now and whether that\'s the repost status and all these other methods, I think we\'re still seeing the early stages of a comprehensive program for contributing.

\n\n\n\n

Cory Miller: And I understand the apprehensions from companies and founders and leaders. You know, you have to make a [00:11:00] profit for sure. And you\'re like, okay, I want to give back, but I, can\'t just, I\'m not a nonprofit, I\'m a profit in enterprise and everything, and I want to help with them and contribute to these.

\n\n\n\n

But something you mentioned just a second ago was pinged for my second thought. And when you said next generation, the no, our intern Here and has helping to post that by the way. But I also know your passion, heart for next generation with WordPress too. And it, that just brings up, well, one Sandy Edwards work with kids camp.

\n\n\n\n

Talk to her about that a couple of weeks ago at our three, how post-test wants to contribute to that. But the other thing, the second theme is Gutenberg. You know, you can\'t probably talk to Matt about WordPress without hearing Gutenberg and for good reason, here\'s the thing. I was not a vocal advocate at all of ruling out Gutenberg in the way we did 

\n\n\n\n

David Bisset: I like how politically, that was so eloquently put, but yes. 

\n\n\n\n

Cory Miller: Yeah, I thought it was way early and everything, and it took me a year or two to finally [00:12:00] okay. You know, use Gutenberg and but it here\'s the reality situation, no matter what, the way we feel about the past, it is here and it\'s not going away.

\n\n\n\n

So you hear this over and over from Matt and for good reasons, there\'s some cool stuff coming. That he talked about the styles, some of the typical libraries. I see that as a very similar innovation and direction, that themes as a whole went when I started, I think back in 2008, There\'s so much innovation to do.

\n\n\n\n

So first and foremost, it\'s here. We\'ve got to accept it and move on. And I think what his plea here was too, and again, probably my nuance. It\'s not, I\'m not going to play, but I\'m just saying my nuances. It\'s not going away. We should accept it and embrace it. And then the question becomes, how do we improve that?

\n\n\n\n

And I think our community can make considerable contribution. To the conversation and the actual implementation of Gutenberg, the block editor for WordPress. I\'ll tell ya, I\'m looking, I\'m going to redo my [00:13:00] personal site cause I want to start blogging every day. And I say blogging, it\'s going to be just sharing my thoughts.

\n\n\n\n

Not just on Twitter, but you know, my site and I\'m probably going to pig blank canvas. I\'m still up in the air and I want to use. And I want to really like embrace using it and see what I, what my takeaways are. And I did that back in August with the click publish. I want to use Gutenberg because I\'ve criss cross the threshold.

\n\n\n\n

And for me, I\'ll tell you the big benefit David was used to because no one even believes I\'m ever been a developer. I\'m not, but I was like 

\n\n\n\n

David Bisset: Don\'t be ashamed. I\'m a programmer. I do websites. I do plug-ins. I do all of that. And what does Matt say to everybody that I am during state of the word?

\n\n\n\n

I tweet a lot. So that\'s my claim to fame. That\'ll be on my tombstone where the developer, but you\'re not a developer, but 

\n\n\n\n

Cory Miller: I was looking for, I wanted to do a buy now button or something. You know, I just wanted to button and I can\'t, I can [00:14:00] figure it out. I mean, I don\'t want to figure out how to write a button coordination, or, CSS or whatever.

\n\n\n\n

So I, what I normally would have done is went look for a plugin. I can\'t remember. I want to say max plugins or something was that max buttons was out there as a plug in. Well, and I can\'t remember what might\'ve been AGA again. But it was like, that\'s a block that was a game changer for me to go.

\n\n\n\n

You don\'t have to get something extra to do things you want to do in the post. That was pretty cool turning point for me. It\'s not there. It\'s getting better, this awesome people working on it. And I think we should. We can and should contribute to the conversation and the implementation once it gets going, because it\'s not going away.

\n\n\n\n

And back to your point about next generation Syed Balkhi that if you WP Beginner and awesome motive, I remember asking him a couple of years about Gutenberg. I was like I kind of expect he\'s going to get on the bandwagon. Let me it\'s like, we don\'t like it. It shouldn\'t be out there. And Syed was like, I love it.

\n\n\n\n

I was like why? And he goes, because the next generation look at how people are [00:15:00] publishing today and it\'s changed from what you and I learned now. He\'s like, he\'s over 10 years, 15 years younger than me. But like even young kids like Olivia and like the platforms have changed in the way to express yourself change.

\n\n\n\n

And that always stuck with me what Syed said. And so I really have high hopes for Gutenberg. Yeah, again, now that I am in strong, like of it. 

\n\n\n\n

David Bisset: So another thing Matt talked about which I\'m actually a little bit surprised he did bring it up. I\'m wondering who, by the way, Tuesday was when WordPress 5.9 was supposed to be out before they pushed it to January. So I talked to Anne McCarthy today. And first of all, I mentioned to her, like you mentioned, like 5.0 release when Gutenberg first came up, was rough around the edges. And she has assured me that the full site editor coming out in January with 5.9 is it may not have the entire kitchen sink, but it is very stable and doable. So I can\'t wait to share that [00:16:00] interview with everybody, but Matt did call out acquisitions and I like, and I thought is this one of the things that if 5.9 was out, would he gone over more quickly? I don\'t know, but they got on one slide. He started with 42 logos. And I thought there were more acquisitions than that.

\n\n\n\n

I\'ll have to go back to our Post Status tracker. But he had 42 logos up there and then he proceeded with, and I\'m not a finance person. I\'m just going to take his word for it. , his charts were taken from other people\'s analysis. He gave proper credit to them, but he says the number of the deals that are happening in the tech space, he says there were 10,000 transactions in the first nine months of 2021 alone.

\n\n\n\n

Which is up 24% over the last year. And then he brought out another chart that was called inflows to stocks. And I couldn\'t even, I don\'t even know what that was. I was, but all I know is there was a big bar at the end with the, with our year in it though. And I guess what he was trying to prove is that [00:17:00] don\'t panic.

\n\n\n\n

The acquisition space is not unique to the WordPress space right now. This is all going, you know, bonkers. And it\'s not just WordPress. So I, you know, with you being a business person, how did you feel, do you feel that was properly delivered or delivered? Well, do you think he got the message.

\n\n\n\n

Cory Miller: But the question I think about that is what prompted him to even do the slides, you know, and that\'s the bigger question we always want to be thinking about here, you know, for our people is what is the founder co-founder of WordPress, the movement of open source project. Fill the need to say that. And we have some sense of the people that are like change sucks.

\n\n\n\n

Nobody likes change, you know, and the fact of the matter, if you bullet down these acquisitions, why would anybody even care? It\'s because it could potentially change something that I\'m used to doing. And I\'m not saying it\'s good, right? Bad, wrong indifferent. I\'m just saying, you know, I think change is [00:18:00] tough and I\'ve heard some sentiment from the WordPress community about, I don\'t even recognize it anymore and all this stuff.

\n\n\n\n

And then I just go down, like, here\'s my comparison for it is when I left.iThemes and started this new journey and Post Status . It was over a year before I became a partner and it was probably nine months before Brian and I even started talking about me becoming a partner. There was a big gap there and I was like, I didn\'t know what I was going to do next and trying to figure that out.

\n\n\n\n

But I did one simple thing, which was, I\'m never going to say publicly privately, I\'m leaving WordPress. I joked all the time. I\'m going to be a WordPress user a blogger, which I was still am. But the important thing is I didn\'t want to lose or even think all the amazing friendships I\'ve made over 15 years being in the space.

\n\n\n\n

To say, I\'m saying goodbye to you. That\'s not it. You heard Pippin Williamson when he left Sandhill dev that he was like, I\'m not saying about a difference, but I need to step away from the project. [00:19:00] And I just go that sentiment to me comes back to this acquisition. Like things are changing, all that stuff.

\n\n\n\n

I, I totally get that. I\'m not trying to change your emotion. My way of thinking about it though, is the people are still here and that\'s what matters. I\'ve known you David for God. Has it been 10 years since 

\n\n\n\n

I\'ve known you for 10 years? 

\n\n\n\n

David Bisset: Since the first conference in Arizona whose name is escaping my. I think that\'s where we may have known.

\n\n\n\n

We may have known each other prior to that. That\'s the first time we met in person, I think officially, 

\n\n\n\n

Cory Miller: but you know, the premise of all, this is like, the people are still here, for the most part. Now you\'re always going to get people leaving the ecosystem, leaving it, you know, and coming in new people, coming in, who I met, one of our post-test members was when Stina and I\'d love to hear her story.

\n\n\n\n

She was there. Got invited to State of the Word we got to talk Post Status member and That\'s a new person, I didn\'t know, a year ago or two years ago, you [00:20:00] know? And so some may leave and you\'re always going to have that in some, and cause there was even a picture. I think one of those slides, David of Kim. Oh, you know, and you think about people who have left and for instance, this world Kim back in the day but I saw her picture on one of those slides, you know, and it made me smile, but all that to say, WordPress is not about code it\'s about the people.

\n\n\n\n

And that is what I hang on. I\'m not trying to change your heart, your feelings, but I\'m just saying, if you think about it, go it\'s about the people. No matter if it\'s a team, if it\'s outside of WordPress, whatever it is, it\'s like, what matters are the people there? And are we growing together and all that?

\n\n\n\n

So that\'s the way I think about that, but that the merger is that it\'s I it\'s right for people to go and question what\'s what the heck\'s going on here. Things are changing on that space, but I still go the Michelle Frechette. Actually as a team member of people, some of my best friends and my former team and I themes now, is that interesting?

\n\n\n\n

Well, I\'ve known Michelle for a long time and now she\'s a part of the scene. That\'s cool. You know, that, that change happened where gives, [00:21:00] got by. And cellar rolled out and she moved over roles and now we get to work with her Post Status too. And again, I just call back to, if you\'re worried about that, just go back to the people now there\'s other worries, but I just, the heart of it is about people.

\n\n\n\n

David Bisset: Yeah. And 

\n\n\n\n

I also, I have also have a motto too, in terms of you don\'t let the people that are leaving a community, distract you from who is coming into the community or who they should, or who should be invited into the community and vice versa. But don\'t let one side distract you from who\'s coming in versus who\'s going out and that sort of thing.

\n\n\n\n

And I think we\'re doing a pretty good job with that. What happened after state of the word after it ended what happened. 

\n\n\n\n

Cory Miller: Well, so there was about, I can\'t remember how many, but at least 20 of us, I could probably adapt touch straight back to Post Status and we all kind of stayed at the same hotel and had a little, two day fun before the event and all that stuff.

\n\n\n\n

And so a bunch of us went back to our hotel and we\'re at the restaurant, the hotel restaurant bar, [00:22:00] and just kinda talking, you know, and I got to meet great people. I\'ve just met in like Robert. Who runs OSTP training there? I got to see again for the third time, Robert Jacoby of cloud waves. The hero press couple Kate, and Tofor, I\'m trying to think of othersAC Morse was there? Gravity forms. 

\n\n\n\n

David Bisset: Aaron Campbell was there. 

\n\n\n\n

Cory Miller: The Aaron and I laughed. He lives in Oklahoma. Like me, he\'s literally an hour away. I bet it\'d take me 45 minutes to be on his doorstep and vice versa. And we\'re like, we had to laugh. So we\'re sitting in New York city Soho, somewhere in the coffee shop. We\'re like, isn\'t it funny how we have to either go out of the country or to go across the states to see each other when we live like that close to each other.

\n\n\n\n

And I love Aaron. He has such a great. For WordPress, all things WordPress and I love what he\'s doing. 

\n\n\n\n

David Bisset: Bob was there too. Of course, he traveled by train. He traveled by training the width of the Wu train clan. And it was, I think one of the best moments of the night was when he got up to ask the question and he had the simplest of questions, which was like, he [00:23:00] like, what\'s up for WooCommerce or in the next year I traveled 2000 miles to ask this question.

\n\n\n\n

And how did Matt respond 

\n\n\n\n

Cory Miller: that\'s all the bingo card and slack Post Status slack light up because Bob asked it, you know, finally he got the invoke. Woo. Yeah. I love Bob. Bob does and has been around for a long time too. And what I said about him personally at the vent was the one thing I admire about him is he has just consistently showed up.

\n\n\n\n

And get work in this space and has mad respect from everybody because of it. So we sponsored his train trip out because we wanted to I mean, Bob is such a vital member of the WordPress community and then specifically WooCommerse. So Bob did all of that kind of community logistic, wrangling there, in addition to being like, and he was trying to record, he set up a studio in his room and I got to be with Robbie and Robert and Bob and

\n\n\n\n

do the woo podcasts there. So, it was a great time for that on the note of getting people together. And Post Status [00:24:00] specifically we\'re right now getting our in person. Camps together for Post Status Brian and intended to do it last year. And you know what, two years ago, and you know what happened, right.

\n\n\n\n

But this year we\'re putting some plans in place to get together in a small way to talk shop, to do life together as a community. I would love for everybody to be there next. December 22nd for, it\'s going to 

\n\n\n\n

David Bisset: say, as we wrap up here, what is the schedule look like for our post status members?

\n\n\n\n

What do they, pay attention to?

\n\n\n\n

Cory Miller: So we\'re doing a year in, remember huddle. We\'re going to be doing these next year, by the way, in which I\'ll be talking about, but our member huddle you\'re in next Wednesday, December 22nd, 11:00 AM central time. There\'ll be zoom links in slack and all that.

\n\n\n\n

And so. We\'re going to do our, that member huddle. How-to it\'s going to be one part like reflective review last year, thinking about next year. So look back, look forward, and then we\'re going to do some fun stuff. I want you to meet the Post Status team. All the people that are doing all this crazy awesome [00:25:00] stuff behind the scenes that you don\'t all see.

\n\n\n\n

And then talk about some of the things we got in store for our Post Status community. A couple of times I\'ve heard people say energy with post status and it is, and it ain\'t just me, by the way, it\'s people like David who had been here faithfully for years, Michelle Frechette, Courtney Robertson, Taleesha, you\'ll get to meet her.

\n\n\n\n

She\'s our new director of operations and all kinds of people in between. I can\'t wait to do that. And then laugh together. Our theme for the ongoing, I hesitate to say it\'s going to be 2022, because I just want it to be forever is give. Together. 

\n\n\n\n

David Bisset: What was that again?

\n\n\n\n

Cory Miller: Give, grow together. It\'s part of what I want to be our member mantra.

\n\n\n\n

The thing we come to post to us and say, I\'m here to give of myself my time, talent, treasure, all that stuff. Not true necessarily, but like give up myself in the spirit of open source to the commuity. To each other. Second is I\'m here to grow. I want to grow myself. I want to grow my business.

\n\n\n\n

I want to grow my career. We\'ve got specific plans for the growth side and then together, it\'s [00:26:00] just the thing that wraps everything together. It\'s not I. It\'s not you. It\'s always, we at Post Status. It\'s not just me. I happen to be on, you know, I had my face out there and stuff like that. But if this is truly a community and truly a team too, and I want us to just emphasize those three things, give in spirit of WordPress, same thing, just give to each other in the community business of WordPress second is to grow commit. You want to be here, let\'s grow yourself, grow professionally, grow your business, whatever it is, come here to grow. And then to do it together do it all of us together. So, even our products, like, as you will know David is called and that\'s a Portuguese word for probably mispronounced it, but together we\'re together.

\n\n\n\n

So it\'s been a theme of my life even before clinical campaigns and the COVID time. But I really mean it next year as I\'m going to do these things from in-person camps, how we do slack, how we do some of the cohorts, we\'re going to be rolling out. And I hope you\'ll show up next week and we can talk more about that and get your feet.

\n\n\n\n

David Bisset: What was the date again?

\n\n\n\n

Cory Miller: [00:27:00] December 22nd.

\n\n\n\n

David Bisset: So December 22nd, Wednesday, are we going to see any sign of a state of post status with you in a suit? Is that something we can look forward to? 

\n\n\n\n

Cory Miller: You\'re probably not the second 

\n\n\n\n

David Bisset: the people that are listening for the people that are listening at home.

\n\n\n\n

Cory shook his head so quickly that I thought his neck was about to snap. 

\n\n\n\n

Cory Miller: Yeah, I think we should do these types of things where as our leader of post, as getting in front listing talk, discuss, put things out there that help you learn and grow and all that with postdocs, for sure. And I always want to get to Canada.

\n\n\n\n

So maybe to the first to the second one, the suit, you know, I mean, I\'ve got two suits. I probably don\'t fit currently. So. I think you\'re more likely to see me in a Chewbacca outfit than a suit, but no shady. Anybody else? It\'s just, 

\n\n\n\n

David Bisset: no, you have to stand up. You gotta make yourself stand out with all these other state of the blah-blah-blah.

\n\n\n\n

I mean, if Matt does a [00:28:00] suit, I think. Any, if you\'re going to wear a hairy Chewbacca outfit, I think that\'s a good countermove. But anyway, 

\n\n\n\n

Cory Miller: Somebody is gonna remember this and come back and say, Cory memory, you say you do that. 

\n\n\n\n

David Bisset: Oh, people will remember it. I might have a little bit of a night terror about it. I\'ve got a thing against Wookiees. But other than that, I think it\'s a fantastic idea. Well, it sounds like you had a blast and it was a blast watching. I see you in some of the photos. Sometimes you\'re in the background You\'re in the background photo bombing. It\'s fantastic. I\'m glad that this happened and I\'m glad to see Matt so open.

\n\n\n\n

Maybe it was because it was a smaller venue or it was the fact that there wasn\'t a word campy west surrounding Matt. You know how draining that is even to, just to be at a work camp us and then, and that WordCamp us with a talk in front of a thousand, 2000 people, it would look like a really nice event with a ton of energy, but.

\n\n\n\n

Personable intimate. And I\'m glad you all in this, in the few got to experience that. And I, of course, next year though, [00:29:00] or next time this happens, hopefully it will be under different circumstances and we\'ll have more people. In fact, think he said, if all goes well, San Diego is going to be the work camp spot for 20, 22.

\n\n\n\n

Have you ever been to Sandy? Oh, really? I\'ve never been. So it\'ll be interesting for me. Was there anything else that you wanted to share? I think we, it was good seeing you. It was good seeing you. I\'m glad you\'re home safe. And then it sounded like they do all the safety precautions and everything, which was fantastic.

\n\n\n\n

I\'m glad they did that. And it was good to see Josepha and the others there as well representing so great. So next time. Let\'s it sounds like we\'re going to talk about wrapping up our thoughts about the year with the biggest news stories that you think Corey or the most influential to you personally.

\n\n\n\n

And we\'ve asked the same question to our post status members, this awesome service zip message. I want to say zap message, but that sounds more painful. Zip message. It\'s zip message. And we\'re encouraging people [00:30:00] to go in there and just leave a brief clip about what story to them was the most influential for WordPress this year.

\n\n\n\n

And to them personally, and maybe by the time we talk next time, we will have a couple of us to talk about and share our own as well.

\n\n\n\n

Cory Miller: Thanks, david. And thanks everybody.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 Dec 2021 04:32:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:64:\"WPTavern: Gutenberg 12.2 Focuses on User Experience Improvements\";s:7:\"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=127612\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:173:\"https://wptavern.com/gutenberg-12-2-focuses-on-user-experience-improvements?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-12-2-focuses-on-user-experience-improvements\";s: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:5854:\"

Some Gutenberg plugin releases feel like heavy-hitters with new user-facing features. Others, such as today’s version 12.2 update, smooth over problems and create a more well-rounded experience.

\n\n\n\n

Switching between the site editor and templates is smoother. The color picker is no longer a hot mess. And, border controls now use the tools panel approach of allowing users to enable or disable the options they want.

\n\n\n\n

Contributors have made progress on updating the Comments Query Loop block, which will eventually be the backbone of displaying comments in block themes. One of the tallest hurdles was making nested comments work. With that now fixed, moving forward with other comment-related components should be less problematic. The latest release also introduced the Comments Pagination Numbers block for handling paginated comment lists.

\n\n\n\n

View Templates Without a Page Reload

\n\n\n\nTemplates view in the site editor.\n\n\n\n

When Gutenberg 12.1 launched two weeks ago, I was happy to see the new and much improved slide-out panel in the site editor for viewing templates. My primary complaint: it was slow. Switching between the editor and template view required a page reload.

\n\n\n\n

In the latest 12.2 release, this has all changed. Thanks to client-side routing in the site editor, the transition between the editor and templates feels fast and smooth.

\n\n\n\n

Changes like this are one of the reasons I have welcomed the postponement of WordPress 5.9 until late January. Some of these little wrinkles needed ironing before showing the site editor to the world.

\n\n\n\n

Improved Color Picker

\n\n\n\nColor picker popup.\n\n\n\n

Gutenberg 12.2 introduces a much-improved color picker. The previous iteration was unwieldy, bulky to the point of being an annoyance. Users would have to scroll and scroll and scroll some more just to jump between changing a block’s text color and its link color. This was especially true if the theme showed both its colors and those from core.

\n\n\n\n

The latest iteration tightens up the UI to the point where users can see the text, background, and link color options all at once. If they want to customize any of them, they can click on one to pull up the color picker popup.

\n\n\n\n

Perhaps this change will open the door for other color options in the future, such as one for link hover/focus. It would have been far too messy in the old UI. However, the new minimalist design leaves ample room.

\n\n\n\n

I would love to see the border-color control get the same treatment. However, there is a separate ticket that offers more fine-tuned control.

\n\n\n\n

Font Size UI Change

\n\n\n\nNumbered-style font-size selector.\n\n\n\n

The font size control for supported blocks looks much different. It shows a list of numbered buttons for themes with five or fewer custom sizes. The font-size name appears when one is selected. Otherwise, it is simply a list of numbers with no context.

\n\n\n\n

I have generally liked the progress made toward updating the block options UI. But, I am not a fan of this change. As a user, what do these numbers even mean? Is the “1” size small or medium? There is no way of knowing without testing it. Plus, the context will change from theme to theme. A UI change like this may have been OK on the back of a standardized naming scheme. However, that will be tough to implement after three years of usage.

\n\n\n\n

In general, clicking a single button feels like a better experience than clicking a dropdown, followed by a second click of making a selection. I am just not sure that it works here. However, I am open to seeing where it goes upon further iteration.

\n\n\n\n

There is also no visible way to clear the current selection and return to the default size. If the theme supports custom sizes, users can switch to the “Custom” field and clear it out. This is not obvious unless you stumble upon it. Users could also hit the “Reset All” button, but doing so resets all typography options.

\n\n\n\n

The easiest way to avoid this UI change is for theme authors to register at least six custom font sizes. The option will automatically revert to its former dropdown select field. Fortunately, I have 13 in the theme I primarily work on, so it is a non-issue for me.

\n\n\n\n

Block Template Part Hooks

\n\n\n\n

Theme and plugin developers now have additional action hooks around the block template part system. These should be handy for debugging or other complex use cases.

\n\n\n\n
  • render_block_core_template_part_post fires when a part is found from the database.
  • render_block_core_template_part_file fires when a part comes from a theme file.
  • render_block_core_template_part_none fires when no part is located.
\";s: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, 23 Dec 2021 01:19:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"WPTavern: WordPress Contributors Discuss the Possibility of 4 Major Releases in 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127550\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:213:\"https://wptavern.com/wordpress-contributors-discuss-the-possibility-of-4-major-releases-in-2022?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-contributors-discuss-the-possibility-of-4-major-releases-in-2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6344:\"\n\n\n\n

Last week, WordPress Executive Director Josepha Haden Chomphosy opened a discussion on how many releases the project will aim for in 2022.

\n\n\n\n

“Given that we have a release in January already, I wonder if we might be able to use 2022 to attempt four releases,” Haden Chomphosy said. She proposed three different release schedules:

\n\n\n\n
  • Quarterly releases: January, April, July, October
  • Trimester-ly releases: January, May, September
  • Known release and then evenly spaced targets?: January, May, August, November
\n\n\n\n

When she brought it up in the #core Slack channel, a few contributors said they would like to see the project move towards more frequent releases. They were optimistic that it can be done, since a January release is already on the schedule.

\n\n\n\n

Responses to the post on make.wordpress.org were markedly different. A few commented that they would be comfortable with a quarterly releases as long as they avoid major holidays. Several participants in the conversation have urged WordPress to slow down to two or three releases. Others suggested WordPress simply wait to release new features until they are ready, with no schedule. This particular suggestion makes it difficult for various stakeholders, like hosting companies, agencies, and WordPress product businesses, to plan effectively.

\n\n\n\n

In 2021, WordPress released version 5.7 in March and 5.8 in July. A third major release planned for December was postponed due to critical blockers and decreased volunteer availability. A jump to four releases next year seems overly ambitious without a change in processes.

\n\n\n\n

“Is it realistic to plan four releases for 2022 right after three releases per year plan was not fulfilled?” Oleg Kharchenko asked in the comments. “I don’t get what’s the benefit of having more releases just for the sake of number. It looks good in business reports but it has no real value for WordPress users as frequent releases lead to half-baked features which are hard to use.

\n\n\n\n

“Also plugin and theme authors will have to put more time into testing instead of their product development. Finally, there are many tickets on Trac with ‘early’ keyword which are punted for years just because everybody is too busy to find time to include these tickets in the upcoming release, making the release schedule tighter would worsen this situation even more.”

\n\n\n\n

Jessica Lyschik, a developer and an active member of the German WordPress community, said she would prefer two releases for the future.

\n\n\n\n

“As several people already mentioned, planning more releases did not work out in the past, so why should it work now?” Lyschik asked. “5.9 got postponed to have refined features included so it can be actually used. The complexity of the new features is huge and trying to split that up in smaller releases is not something I see to work in the future.”

\n\n\n\n

The roadmap for 2021 originally planned for four major releases but was scaled back to three in February. At that time Haden Chomphosy cited a lack of automation and the necessary personnel to execute the plan without risking contributor burnout and update fatigue.

\n\n\n\n

WordPress core committer John Blackbourn commented on the discussion, urging Haden Chomphosy to elaborate on why she is proposing the potential of more frequent releases. He also requested she summarize the original list of challenges and needed changes and the progress that has been made towards improving them.

\n\n\n\n

In a post titled “Why I Voted to Delay WordPress 5.9,” Anne McCarthy explained a few of the factors and blockers that caused the release to be postponed to January 2022.

\n\n\n\n

“What I’d like to understand better is what are we going to do to make sure this doesn’t happen again?” WordPress 5.9 release lead Matt Mullenweg commented. “There could always be more polish, more bugs fixed, and I would challenge you to pick a year in the past decade that didn’t have its share of human issues. I’d like us to really understand and agree what went wrong, particularly in the first months of 5.9, and what we’re starting now to make sure 6.0 is effortlessly on time.”

\n\n\n\n

McCarthy responded, citing the following reasons:

\n\n\n\n
  • lack of contingency plans around the interrelated features
  • lack of clarity around scope for various individual features (particularly the browsing feature)
  • lack of a comprehensive check in early enough ahead of feature freeze
  • a need for more decision makers who have a high level view of where the work is headed
\n\n\n\n

“Personally, I’d love to see the Go/No Go meeting overhauled to be less aspirational and more concrete as to where things stand as I think that’ll set the tone early enough in the release cycle to avoid some of these problems again,” McCarthy said.

\n\n\n\n

A few of these challenges with 5.9 correspond to the items Haden Chomphosy identified in February as needing to change in order to make WordPress releases easier and more frequent: better testing, more seasoned core developers available with time focused on core, better handoff in design/dev iterations, and shifts in collective philosophies towards continuous development.

\n\n\n\n

In the absence of a comprehensive 5.9 retrospective, it may be difficult to plan the next year’s release schedule based on the reality of what contributors experienced most recently. Moving to four major releases will be a tough sell after closing out a year where WordPress could not post three major releases. It will require significant changes to how the work is scoped and managed as it is in process. The topic will be up for discussion again during today’s weekly core dev chat at 20:00 UTC.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 22 Dec 2021 19:50:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:72:\"HeroPress: Living Well and Enabling Success For Others Through WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=4328\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:196:\"https://heropress.com/essays/living-well-and-enabling-success-for-others-through-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=living-well-and-enabling-success-for-others-through-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:12420:\"\"Pull

From a very young age, I can remember dreaming about a business I would one day own. It would be a restaurant named “The Comfy Chair.” Serving mainly breakfast and light lunch, I pictured a funky space with a mix of unique, comfortable chairs. Patrons could choose the chair that fit their mood of the day.

\n

I’m sorry to report that my childhood dream never came true.

\n

Instead, I now lead a 15-person remote team that develops open source software on WordPress, our primary product is the membership plugin Paid Memberships Pro.

\n

The road that led me to WordPress didn’t begin with a passion for the web, or democratizing publishing, or coding, or anything technology-related.

\n

I began my career in WordPress through my passion for entrepreneurship. A passion to control my earnings, “be my own boss,” and maybe more specifically, work when I want, on what I want, and for the price I choose.

\n

That is the most kickass thing about WordPress—people can enter our community and leverage WordPress for free, from anywhere, anytime, for any reason.

\n

From Craigslist to Plugins

\n

Throughout college, I freelanced doing simple brochure websites, graphic design, and a lot of print work. I used Craigslist and word of mouth to get projects, taking nearly any job that a) paid and b) I could handle on my own or with some help from my “high school sweetheart, husband, co-founder, and best friend” Jason.

\n

After graduation, my parents were cautiously enthusiastic about my decision to start a web design business. I knew I had many months of runway and felt it was a no brainer. Starting a business is a risk. The bigger risk was missing the opportunity to create my own business in the “carefree” days of youth.

\n

Business ownership teaches you a ton—I was learning not just about emerging web technologies like WordPress. I had to learn every aspect of small business: sales and marketing, project scoping, invoicing and accounts receivable, taxes, healthcare…everything.

\n

In Fall 2006, Jason left his job at Accenture and joined me full time. I had my projects and clients, Jason had his. He led the projects that were more development-focused, I led the more design-focused projects.

\n

By 2007, we started doing WordPress sites almost exclusively. WordPress was about four years old at the time. The community was starting to take shape. Meetups and WordCamps were becoming a thing, but the events were very different back then.

\n

I didn’t identify with the early WordPress community. Events were primarily attended by developers and coders, who were primarily male. So I stayed on the periphery of the community.

\n

Jason and I continued operating Stranger Studios as a two-person team. In an agency, there are two main ways to grow revenue: charge more per hour or bill more hours (grow the team). I couldn’t picture myself managing other people. Life and business was good just the way it was. So we regularly raised rates, focused on high value clients, and tried our best not to keep too many clients on maintenance plans.

\n

The WordPress “CMS” helped us increase the number of clients we could serve by giving them more independence in managing their own sites.

\n

Then, life decided to push me into my next chapter with an event that happened when we had our first child, Isaac.

\n

A Building Block For Change

\n

Isaac had a rough start to life 13 years ago and needed surgery a day after his birth. We are endlessly grateful to St. Christopher’s Hospital and The Philadelphia Ronald McDonald House for supporting us through his first two weeks.

\n

And while going through those heartbreaking, chaotic, and hopeful weeks, we still had to work. I remember waiting in our hotel room for Jason to wrap up an urgent call with a client so we could go see our days-old baby. It’s a ridiculous scene to reflect on.

\n

I thought I was living life my way. In reality, I was financially tying myself to a handful of long-term clients. And what’s worse: there was no one to hand things off to when my personal life needed attention.

\n

Consulting work felt like being on call 24/7.

\n

That event changed my life in more ways than I could ever put into words. For the intention of this essay, let’s just say that our business needed to change dramatically, quickly.

\n

When I talk with other entrepreneurs and business owners, we often break down the differences between a services company and a product company. You may have heard a WordPress talk on this very topic: the move from “consulting to products”.

\n

It’s an appealing path for many WordPressers. And now that I’m on the other side of the transition, I can’t deny it is an awesome space to be in—even with the product space going through some major shifts with all the acquisition activity. But that’s a topic for another conversation entirely…

\n

The biggest turning point in my WordPress journey was the decision to create a product. By moving to a product company, I could make more money without working 24 hours a day or (immediately) having to hire people and grow as an agency.

\n

But what kind of product should we build? What untapped market could we serve? What was missing in the WordPress ecosystem?

\n

We found the answer by looking at our history of proposals and projects.

\n

A growing number of our freelance projects had a “membership-type” component. People wanted to protect access to features of their site (content, tools, applications). People wanted to get paid through their WordPress site. More specifically, they wanted to “make money while they sleep” and get paid on a recurring basis. Sell once, get paid over and over again.

\n

Jason and I recognized this trend and the lack of a leading WordPress plugin for memberships. We focused only on freelance projects for “membership-type” sites built on WordPress. These projects helped us bootstrap the development of what is now Paid Memberships Pro.

\n

Open Source Products Are Better Products

\n

I believe in open source. I believe open source products are better products.

\n

We release all of our products with an open source license, just like WordPress. We make our code publicly available on GitHub in a format that removes barriers to collaboration for internal and external contributors. And we make a very good living for ourselves and our team by building a business on top of our open source products.

\n

The decision to be open source has made an overwhelmingly positive impact on the growth of our business. But there’s another major reason why we’ve made it in the WordPress product space.

\n

Paid Memberships Pro is a success in large part because we release the full version for free in the WordPress.org Plugins repository.

\n

Putting my beliefs in OSS aside, the repo makes your plugin available for every WordPress site. That’s 43.1% of websites that exist today. The repo is an amazing resource for every site using WordPress and also for every business building a WordPress product. Not only does the repo facilitate installs and updates, it also builds in a layer of security for WordPress users.

\n

I am deeply grateful for the WordPress community members (the Plugins team) that maintains, reviews, and supports the repository. Without you, I wouldn’t be sitting here today writing an essay about my WordPress journey.

\n

Building a Team That’s Diverse In Many Ways

\n

I’ve always been a woman business owner in a male-dominated field. But I can’t say that my being a woman was something that limited or, on the flip side, catapulted my career forward.

\n

I say this because there are many people in the WordPress community that speak intelligently and openly about important topics like diversity, inclusion, and the serious problem of underrepresentation. I have not devoted enough time to educate myself on their efforts.

\n

But as a person who has interviewed and hired people for a variety of roles, I do have some perspective on the value diversity has brought to our team.

\n

Nearly half of our team are women. And we are diverse in other ways including age, geography, physical ability, and experience.

\n

I value diversity as I value any other positive trait that an employee brings to the table.

\n

When I am interviewing another woman, I recognize that they bring a woman’s perspective to the team, which is valuable. When I am interviewing someone with very little experience, I recognize that I can teach anyone that’s willing to learn and grow, which is valuable. When I am interviewing someone that lives a 20-hour plane ride away, I know that we work remotely and don’t have to overlap for our entire work day.

\n

The diversity in our team has changed my worldview. I have learned endless things about other cultures, such as the troubling issues that a Nigerian mother has faced to find a safe and enriching school for her daughter. I’ve learned about the lasting effects of apartheid in South Africa, about the progess has been made to unify the country and where there is work to be done.

\n

As a parent of “tweens”, I’ve learned valuable lessons from people with adult children. And on the flip side, I’ve shared my stories with people at an earlier stage in the parenting journey.

\n

WordPress is an open, free, accessible tool used by the whole world. Getting involved in WordPress doesn’t require a special form of education, grasp of the English language, or boatloads of money.

\n

I wouldn’t have been able to build a diverse team if the WordPress community, itself, wasn’t diverse.

\n

Live Your Way

\n

Live your life your way. Do more of the things you want. Do less of the things you don’t want.

\n

I am extremely grateful that I am safe, comfortable, and able to live my life, my way. I know that many people are in a place where this type of thinking is not possible.

\n

But even people with everything can have a feeling that something is missing. For me, that feeling is influenced by what other people want for me, when I feel pressure to live out someone else’s dream.

\n

Jason tells me (and others) that my skills are wasted on this product. He boosts me up with encouragement and praise. He says that I am capable of bigger, grander things.

\n

The message I take from this is that I can do anything. So I will do what I want to do. I will do more of the things I like to do, and less of the things I don’t.

\n

In work, that looks like filling senior roles on our team to do things I am currently responsible for. Freeing up my time to nurture the next big product. Or, freeing up my time to spend in ways that my kids need me. Or, I could get another dog.

\n

What I want to leave you with here is that you don’t have to feel pressured to go after someone else’s dream. I’ve watched companies like mine get acquired. Their founders take extended vacations and are living semi-retired lives. I think “is this what I’m supposed to do next?”

\n

Then I join my team on a call and I think “I never want to stop working with these people. This is my family.”

\n

I’ve had opportunities to swing for the fences. To push harder. To get bigger, faster. To be wildly successful.

\n

This is a monetary measure of success. This is feeling successful because other people think you are.

\n

To me, success isn’t measured by dollars or ego. Success is a life well lived. I want to energetically pursue living well. I want to build products that help people find this success. I want to grow a team that has the same freedoms in life that I humbly enjoy.

\n

I want to keep pursuing success with WordPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 22 Dec 2021 13:00:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Kim Coleman\";s: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:76:\"WPTavern: Ask the Bartender: Will It Become Easier To Create Block Patterns?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127545\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/ask-the-bartender-will-it-become-easier-to-create-block-patterns?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-will-it-become-easier-to-create-block-patterns\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4048:\"

Do you know if WordPress FSE is working to make it easier to create block patterns? Templates and Parts need to just click a button to download them. But patterns are very manual, and you need to register all of them programmatically.

Thiago
\n\n\n\n

You are not the first person to ask this question, and it is something that I have been mulling over for a while. With theme development quickly encroaching a point where it could almost exclusively be done via the site editor, it makes sense that block patterns follow along with their template counterparts.

\n\n\n\n

The feature has not been given any sort of official green light. I am not aware of a specific ticket for it, but it seems like it will be a part of the natural evolution of themes and patterns. I encourage opening a new ticket via the Gutenberg GitHub directory.

\n\n\n\n

Two core features need to precede it:

\n\n\n\n
  • A standard folder for storing patterns in themes.
  • A way to save patterns in the database.
\n\n\n\n

Fortunately, there are tickets for both of these. Last month, Gutenberg lead Matías Ventura opened a new issue for standardizing how themes are organized. WordPress 5.9 will see the introduction of /templates and /parts folders for templates and template parts, respectively. These will be the officially-supported locations in block themes.

\n\n\n\n

That same ticket proposes future enhancements of a /styles folder for global style variations and /patterns for block patterns. Having a standard location for these things is vital because the exporter in the site editor needs to know where to put them in the exported ZIP file.

\n\n\n\n

A side benefit of this feature is that theme authors would no longer be required to register their custom patterns via PHP. They could merely drop the files into their /patterns folders and move on. The format of this is nowhere near official at this point. There is an unmerged pull request that implements this by searching file headers.

\n\n\n\n

The second piece of solving this issue is figuring out how to allow users to save patterns via the UI similarly to reusable blocks. This is a more complex issue. There are existing plugins that already do this, such as my own Block Pattern Builder, which sorely needs updating, and BlockMeister, a more robust solution. Reusable Blocks Extended even allows users to convert reusable blocks into patterns. So, there are already folks who are trying to solve the problem.

\n\n\n\n

There are still questions about the implementation before it can be officially supported. Are saved patterns a subtype of wp_block, which is currently the post type for reusable blocks? Are they something separate? Then, the project must also decide whether it wants to allow custom pattern categories via a new taxonomy.

\n\n\n\n

There are also other considerations before adding another feature into core, such as adding a design library for components in the global space.

\n\n\n\n

We are not quite to the point where you want, but we are on the path. The /patterns folder alone would remove the code-writing requirement. If it lands in WordPress, you could copy and paste block HTML over. It is not the same as exporting them alongside templates, but I hope the platform arrives at that destination one day.

\";s: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, 22 Dec 2021 01:36:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:40:\"WordPress.org blog: WordPress 5.9 Beta 4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11876\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2021/12/wordpress-5-9-beta-4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5144:\"

WordPress 5.9 Beta 4 is now available for testing!

\n\n\n\n

This software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.

\n\n\n\n

You can test the WordPress 5.9 Beta 4 in three ways:

\n\n\n\n

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

\n\n\n\n

Option 2: Direct download the beta version here (zip).

\n\n\n\n

Option 3: When using WP-CLI to upgrade from Beta 1, 2, or 3 to Beta 4 on a case-insensitive filesystem, please use the following command sequence:

\n\n\n\n

Command One:

\n\n\n\n
wp core update --version=5.9-beta4
\n\n\n\n

Command Two:

\n\n\n\n
wp core update --version=5.9-beta4 --force
\n\n\n\n

The current target for the final release of 5.9 is January 25, 2022, which is only five weeks away. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

\n\n\n\n

Some Highlights

\n\n\n\n

Since Beta 3, 20 bugs have been fixed. Here are a few of the changes you will find in Beta 4:

\n\n\n\n
  • Bundled Theme: Fixed duplicate CSS rules in Twenty Twenty-One theme (#53605).
  • Customizer: It’s possible to switch to a block theme from within Customizer (#54549).
  • Themes: Provide guidance to users seeking to preview block themes on WordPress versions below 5.9 (#54575).
  • REST API: The get_theme_item method should respect fields param (#54595).
  • Editor: Block Patterns: “Featured” category & patterns missing from inserter (#54623).
  • Login and registration: Add a filter to allow to disable the Login screen language dropdown – (#54675).
\n\n\n\n

How You Can Help

\n\n\n\n

Do some testing!

\n\n\n\n

Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute. 

\n\n\n\n

Please post to the Alpha/Beta area in the support forums if you find a bug. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

\n\n\n\n

Got questions? Here are some answers

\n\n\n\n

In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that will cover these items in detail.

\n\n\n\n

So far, contributors have fixed 326 tickets and 108 new features and enhancements in WordPress 5.9. More bug fixes are on the way with your help through testing.

\n\n\n\n

Props to @cbringmann, @psykro, @hellofromtonya, @marybaum, @webcommsat, @audrasjb, @cbringmann, @costdev and @meher for contributions to this post.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 Dec 2021 21:17:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:70:\"WPTavern: WordPress 5.9 to Introduce Language Switcher on Login Screen\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127496\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:185:\"https://wptavern.com/wordpress-5-9-to-introduce-language-switcher-on-login-screen?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-9-to-introduce-language-switcher-on-login-screen\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2867:\"

More than half of all WordPress sites (50.5%) are using translations for non-English speaking locales. It’s only natural that these users would want the ability to register, log in, and reset their passwords in their own languages. A new language switcher on the login screen has finally made its way into core, four years after the ticket was opened.

\n\n\n\n

WordPress 5.9 will introduce a new dropdown on the login screen that will display all the languages that are currently installed. (New languages can be added under the Settings > General screen in the admin.)

\n\n\n\n
\n\n\n\n

In a dev note for the new features, WordPress Core Committer Jb Audras demonstrated how developers can filter the default arguments for the languages dropdown. This might be useful for sites that have dozens of languages installed where administrators only wish to display a handful in the dropdown.

\n\n\n\n

WordPress 5.9 beta 3 was released last week. In addition to the new language switcher, the latest beta also includes the following:

\n\n\n\n
  • Editor: Add FSE infrastructure from Gutenberg plugin into Core (#54335).
  • Formatting: Allow PDFs to embedded as objects (#54261)
  • REST API: Add navigation areas REST API endpoint from Gutenberg plugin (#54393)
  • Themes: A fix for the Live Preview button bug (#54578)
\n\n\n\n

RC1 is expected January 4, 2022, which will bring a code freeze for both Gutenberg and core and a hard string freeze. Contributors are also aiming to have the field guide with dev notes published at this time.

\n\n\n\n

If you have time to contribute during the upcoming holiday weeks, the 5.9 release team welcomes more testing for bugs. Anne McCarthy has published a detailed guide to testing the full-site editing features that are anticipated in 5.9. Testers should check against the list of known issues before reporting bugs on Trac or in the Alpha/Beta forums.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 Dec 2021 04:23:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"WPTavern: The WordPress Photo Directory Is the Open-Source Image Project We Have Long Needed\";s:7:\"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=127492\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:229:\"https://wptavern.com/the-wordpress-photo-directory-is-the-open-source-image-project-we-have-long-needed?utm_source=rss&utm_medium=rss&utm_campaign=the-wordpress-photo-directory-is-the-open-source-image-project-we-have-long-needed\";s: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:6333:\"\n\n\n\n

In last week’s annual State of the Word address, WordPress project lead Matt Mullenweg announced the WordPress.org photo directory. Officially, it has not yet “fully launched.” However, it is live on the site, and anyone with an account can submit their photos.

\n\n\n\n

Thus far, the directory has 103 submissions and are under the CC0 license. Unfortunately, there is only a single photo of a house cat. Perhaps I will need to contribute to the commons that this project has made possible.

\n\n\n\n

This is a separate project from Openverse, a search engine for finding open-source media, launched before the State of the Word event. Eventually, images from WordPress Photos should be discoverable via the Openverse search.

\n\n\n\n

Earlier this year, I was already envisioning what Openverse could be. However, what I really wanted was a WordPress photo directory. Actually, I wanted a WordPress media directory, but starting with images is easier:

\n\n\n\n

Openverse must become more than a media search engine. It needs to be a project where the Average Joe can upload a nice nature picture he took over the weekend barbecue. A place where Average Jane can share a video clip of the ocean waves hitting the shoreline from her beach trip. And a place where professionals can pay it forward to the world.

\n\n\n\n

When Jeff Chandler of WP Mainline shared his first photo, I quickly turned it into a block pattern that wrapped the image in a wooden frame (pattern and image links available via Gist). When the WordPress pattern directory opens its submission process, I would love to submit it or some variation.

\n\n\n\nWooden frame block pattern around Chandler’s image.\n\n\n\n

My customization was not anything special. I wanted to showcase how vital CC0 photos are to those building WordPress extensions like patterns and themes. Having a reliable image resource is invaluable to our creator community. It also gives non-developers another way to contribute to the project.

\n\n\n\n

I also like seeing the faces of people I know listed in the directory. It very much feels like a photo directory made by the people of WordPress. One of my favorites is this one from Topher DeRosia (he has already submitted five):

\n\n\n\n\n\n\n\n

Single image posts provide additional photo information, categories, and tags. Each photo also has multiple download sizes.

\n\n\n\n

The front page and search could still use a little work. Being able to at least search for images based on orientation (e.g., landscape vs. portrait) would be helpful. A nav menu with all of the categories would be handy too.

\n\n\n\n

The Space Needed Disruption

\n\n\n\n

The stock imagery space needed to be turned upside down. More and more, creators from the WordPress community have stepped away from some of the sites they once loved.

\n\n\n\n

Unsplash. Pexels. Pixabay. They have all had an opportunity to become the most significant open-source photo website in the world. They are places for snagging a quick photograph for free. And, for the most part, they have allowed people to give back with their art.

\n\n\n\n

However, these stock photo sites that previously distributed images in the public domain began adding restrictive licensing terms. It started with Unsplash in 2017. Pexels soon followed, and Pixabay was in lock-step with the others by 2019.

\n\n\n\n

Most of these restrictions disallow users to build similar “collection sites” with those same images, essentially creating a competing service. However, they all have other restrictive terms on selling photos, especially unaltered ones. Note: Pexels still allows its contributors to choose between the Pexels License and CC0 (public domain).

\n\n\n\n

Many photo-sharing sites built their empires on top open source, only to turn their backs on it down the road. The open-source spirit embraces competing websites. The art itself is meant to be shared. That is kind of the point. To be fair, the aforementioned were not the only such sites. They were just the most prevalent in the WordPress ecosystem.

\n\n\n\n

WordPress theme authors were often champions of those sites in years prior. However, they saw service after service disappear before their eyes as they were banned from use on WordPress.org. Themers could not distribute the images because the users who downloaded them would not have the same freedoms as promised by the GPL. It was a loss for open-source.

\n\n\n\n

Now that WordPress has a pattern directory, the issue has become more evident. In the coming months and years, creators will need high-quality photos to showcase their patterns.

\n\n\n\n

The easiest path was to leverage the millions of people who use WordPress and build our own thing. WordPress Photos could very well become the de facto standard of open photos on the web, and that is something we should all welcome with open arms.

\n\n\n\n

The project is necessary. WordPress.org has the resources to make something remarkable: a photo-sharing site that is 100% open and will never change.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 Dec 2021 01:43:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:62:\"WordPress.org blog: WP Briefing: Episode 22: A Carol of Thanks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11880\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://wordpress.org/news/2021/12/episode-22-a-carol-of-thanks/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5718:\"

In this last episode of 2021, Josepha Haden Chomphosy takes the time to appreciate those who make the WordPress project a success and offers a carol of thanks.

\n\n\n\n

Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.

\n\n\n\n

Credits

\n\n\n\n\n\n\n\n

References

\n\n\n\n

Have yourself A Merry Little Christmas

\n\n\n\n

Transcript

\n\n\n\n\n\n\n\n

Josepha Haden Chomphosy  00:10

\n\n\n\n

Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project. Some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!

\n\n\n\n

Josepha Haden Chomphosy  00:39

\n\n\n\n

So, ages and ages ago, when I first started this podcast, someone basically requested that Matt and I do a duet for the last podcast of the year. A Christmas carol duet; him on the saxophone and me on voice. I obviously did not get that coordinated I don’t even know why I said obviously. I’ll tell you right now I did not get that coordinated. I was a very busy lady this year. So I don’t have a Matt on saxophone. Still, I did think that maybe it might be nice just for me to sing a teensy little Christmas carol for you all just because it seems especially poignant the words this year, especially after the 2020, 2021 COVID, all the things and trying to get back in person. So I’m going to sing you all one little verse from Have Yourself a Merry Little Christmas.

\n\n\n\n

Josepha Haden Chomphosy 01:35 Singing  

\n\n\n\n

Have yourself a merry little Christmas

\n\n\n\n

Let your heart be light

\n\n\n\n

From now on our troubles

\n\n\n\n

Will be out of sight

\n\n\n\n

Have yourself a merry little Christmas

\n\n\n\n

Make the Yuletide gay

\n\n\n\n

From now on our troubles

\n\n\n\n

Will be miles away

\n\n\n\n

Here we are as in olden days

\n\n\n\n

Happy golden days of yore

\n\n\n\n

Faithful friends who are dear to us

\n\n\n\n

Gather near to us, once more

\n\n\n\n

Through the years we all will be together

\n\n\n\n

If the fates allow

\n\n\n\n

Hang a shining star upon the highest bough

\n\n\n\n

And have yourself a merry little Christmas now

\n\n\n\n

Here we are as in olden days

\n\n\n\n

Happy golden days of yore

\n\n\n\n

Faithful friends who are dear to us

\n\n\n\n

Gather near to us, once more

\n\n\n\n

Through the years we all will be together

\n\n\n\n

If the fates allow

\n\n\n\n

Hang a shining star upon the highest bough

\n\n\n\n

And have yourself a merry little Christmas now

\n\n\n\n

Josepha Haden Chomphosy  03:34

\n\n\n\n

Alright, my friends, that was from my heart to yours if you happened to listen. If you skipped a few seconds to get through it, which I would totally understand, that is also fine. But I did want to just kind of wrap up the year to let you all know that I am so incredibly grateful for all of the people who show up for the WordPress project to make it a success. I have made so many friends and wonderful acquaintances throughout my time here with the WordPress project. And especially in my three years as the project’s Executive Director. You all have put a lot of trust in me and a lot of faith. And I know that we have gotten so much done together in the last few years. And I am equally sure that we’re going to get so much done in the years to come. And so thank you all so much for your continued work with WordPress and the way that you just bring your best at all times. 

\n\n\n\n

Josepha Haden Chomphosy  04:32

\n\n\n\n

One other little thanks I want to give. Over the course of this year, I’ve had an excellent team that works with me on this podcast. I have editing and design folks and people who’ve joined me here and there, folks who helped me with my production. So big thank you to Dustin, Bea, I realize your name is Beatriz in the actual credits, but I call you Bea, and so thank you. Also, a huge thank you to Chloé, who does all of our production and wrangling every couple of weeks. A big round of applause and kudos to that tiny but tough team that helps me get this all done.

\n\n\n\n

Josepha Haden Chomphosy  05:10

\n\n\n\n

That’s to go on top of the general thanks to the WordPress project. And if you all are celebrators, I hope you have a wonderful holiday season. If you are not celebrators, I hope that you have a wonderful end to your year and that everything you wanted to get done, you did get done, and that you can start 2022 with a fresh slate. Again, this is the WP Briefing. Thank you so much for listening. I’m your host Josepha Haden Chomphosy, and I’ll see you again in 2022.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 20 Dec 2021 19:22:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"Gutenberg Times: Charts & Memes Blocks, State of the Word, and more Weekend Edition #197\";s:7:\"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=19863\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"https://gutenbergtimes.com/charts-memes-blocks-state-of-the-word-and-more-weekend-edition-197/\";s: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:12746:\"

Howdy,

\n\n\n\n

Wow, this is already the fourth year-end message, I send out with this newsletter. There isn’t much, I have been doing so consistently then this weekly newsletter. It’s been such an inspiring journey, thanks to you and the WordPress contributors, extenders and users. Your creations, questions, comments have been wonderful, especially when in-person contact have been sparse and zoom-fatigue set in.

\n\n\n\n

For Gutenberg, the block editor the best is yet to come.

\n\n\n\n

In his State of the Word presentation, Matt Mullenweg mentioned for next year Full-Site Editing in WordPress 5.9, which he called the MVP, minimal viable product, Openverse and WordPress Photos, maybe four WordPress releases and in-person meetings. Work on Phase 3, Collaborative editing, won’t come until 2023. This was not all and below you’ll find an array of Recap posts and media for your perusal.

\n\n\n\n

This is my last edition of the year 2021. I wish you a great time with family and friends and a Happy New Year. I am excited to connect with you again around January 9th with the next weekend edition.

\n\n\n\n

Yours, 💕
Birgit

\n\n\n\n

PS: 2129 users voted at the WPAwards produced by Davinder Si ngh Kainth. It’s all in good spirit and a fun activity. In the category of Page builders, Gutenberg landed on second place behind Elementor and before Beaver Builder. 🙂 Thank you, for those who voted for the Gutenberg Times and the Gutenberg Changelog. Seems we need to do some more community outreach and lobbying next time around. 🤔

\n\n\n\n

PPS: To bridge the gap until the next edition, I sprinkled some Gutenberg highlights of the year sprinkles among the links below: starting with the recordings of Gutenberg talks from WordCamp US 2021 on WordPress.TV.

\n\n\n\n
\n\n\n\n\n

Table of Contents

\n\n\n\n
\n\n\n\n\n\n

 “Keeping up with Gutenberg – Index 2021” 
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here

\n\n\n\n\n

State of the Word and Q and A

\n\n\n\n

My longtime Webdev friend, Deborah Edwards-Onoro shared her thoughts in Takeaways from State of the Word 2021.

\n\n\n\n

The Posts Status team collected voices from the community after the State of the Word & Q & Two ways.

\n\n\n\n\n\n\n\n

Courtney Robertson, WordPress Training team, sponsored by GoDaddy, also wrote a Recap of both Mullenweg’s presentation and the Q & A.

\n\n\n\n
\n\n\n\n

The Feedback for the 11th Call for testing from the FSE program is in, and Anne McCarthy published the Site Editing Safari Summary.

\n\n\n\n

“As folks dug in, there were numerous enhancements that quickly came to mind as awesome nice to haves. These desired enhancements not only underscores the potential of various full site editing pieces when put together, but also highlights the frustration around the current limitations” McCarthy wrote. She also created a list of GitHub Issue for those feature requests. Check them out and comment if you are interested in those features as well.

\n\n\n\n
\n\n\n\n

Building Custom Blocks and developing for Gutenberg

\n\n\n\n

Before you start thinking about building a custom block, read Tammie Lister‘s Block patterns are better than blocks, published on the Extendify‘s blog.

\n\n\n\n

The Team at Learn.WordPress.org has two workshops for developers and more are coming.

\n\n\n\n\n\n\n\n
\n\n\n\n

Ari Stathopoulos posted a WordPress 5.9 DevNote on Using multiple stylesheets per block

\n\n\n\n

“Blocks will now be able to register multiple stylesheets, and load styles from other blocks when needed. Themes will be able to add styles on a per-block basis instead of loading monolithic stylesheets that are force-loaded anywhere. This has a greater impact on block themes where stylesheets loading is optimized based on the page & layout contents, but can also be used by classic themes.”, Stathopoulos wrote.

\n\n\n\n

He continued: “This change can benefit both block developers and theme developers, further reducing the total page-weight by only loading styles for blocks that exist on a page.”

\n\n\n\n
\n\n\n\n

Justin Tadlock reviewed a new plugin providing chart blocks in this post: Hello Charts Launches a Native Chart-Building Experience for the Block Editor. In the article, he also lists other block plugins that allow you to create charts. There are actually four:

\n\n\n\n\n\n\n\n

Hello Charts is not available in the WordPress repository, only from their website. It’s the first block-based product site, I noticed, that sells single block features.

\n\n\n\n
\n\n\n\n

In his last stream before the holidays, Ryan Welcher took his viewer through extending the meme block he created last week, to use images from the Media library. You can watch it on YouTube: Expanding the Meme Generator plugin.
If you prefer not to watch the programming part and just look at the code, you can see all code from the Twitch stream on GitHub. Be aware they are educational and not meant to be used in production.

\n\n\n\n\n

Need a plugin .zip from Gutenberg’s main (trunk) branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.

\n\n\n\n

\"GitHub

\n\n\n\n\n

Block Themes for Theme developers

\n\n\n\n

Maggie Cabrera published the Gutenberg + Themes Digest for this week. She highlights PRs and discussions on four topics:

\n\n\n\n
  • Typography supports for group and row blocks
  • Nameless font sizes
  • Approach to global padding
  • Default font sizes renamed
  • Template parts in child themes
\n\n\n\n
\n\n\n\n

I suffered from serious flashbacks, when I noticed that Riad Benguella recreated the Kubrick Theme as a block theme. Matias Ventura tweeted a short video on how to change the header color gradient with the site editor. You can study the block theme on GitHub. It might even show up in the WordPress repository.

\n\n\n\n

Justin Tadlock also has a few more thoughts and screenshots Yes, a Block-Based Version of the Kubrick WordPress Theme Exists

\n\n\n\n\n\n\n\n\n

Post’s Featured Image: “Building blocks, color, abstract, international, global, corporate, colorful” by Wonderlane is licensed under CC0 1.0

\n\n\n\n\n\n
\n\n\n\n

Don’t want to miss the next Weekend Edition?

\n\n\n\n

We hate spam, too and won’t give your email address to anyone except Mailchimp to send out our Weekend Edition

Thanks for subscribing.
\n\n\n\n
\";s: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, 18 Dec 2021 06:11:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"WPTavern: Disable Over a Dozen WordPress Features With the No Nonsense 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=127402\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:199:\"https://wptavern.com/disable-over-a-dozen-wordpress-features-with-the-no-nonsense-plugin?utm_source=rss&utm_medium=rss&utm_campaign=disable-over-a-dozen-wordpress-features-with-the-no-nonsense-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:3429:\"

One of the best things about WordPress is the hundreds of ways of turning things off. There are likely dozens of plugins for disabling various items, each with its own unique set of options. No Nonsense is no different. It is a plugin that allows users to control whether they want to use over a dozen features.

\n\n\n\n

The plugin was developed by Room 34, a Minneapolis-based web development and creative consulting studio. No Nonsense is the team’s 11th free plugin available through the WordPress.org plugin directory.

\n\n\n\n

The team’s plugin caught my eye because it has options for features that I routinely disable on WordPress site builds, such as emoji JavaScript, individual dashboard widgets, and the toolbar. Today’s update (version 1.2) even added an option to permanently remove the Hello Dolly plugin.

\n\n\n\n

Before anyone asks — someone always asks —, the plugin does not disable the block editor. However, it does have an option for turning off the block-based widgets editor.

\n\n\n\n

Room 34 released the plugin on Tuesday, so it has fewer than 10 active installs at the moment. It also does not have any reviews. I suppose this post will suffice as the first. Based on my experience and a peek at its code, the plugin looks solid.

\n\n\n\nPlugin settings screen.\n\n\n\n

I tested each feature and did not find any issues, so it gets a 5/5 for doing what it says on the tin. I would love to see a few more options. One example that immediately comes to mind is the the “Posts” screen. Since users can remove the “Comments” section in the admin, it makes sense to have a similar setting for posts. Both are related to blogging, and not all WordPress websites need them.

\n\n\n\n

No Nonsense includes one of my favorite admin-access limitations. It can redirect logged-in users to the homepage when accessing anything other than their user profile in the WordPress admin.

\n\n\n\n

Its toolbar options are all things I have lying around in my code toolbox. The plugin has settings for hiding it for users without editing access, removing the WordPress logo, and ditching the “Howdy” text.

\n\n\n\n

The plugin includes options for many commonly-disabled features, but a new one that I had not thought about was the core update email. When managing sites for several family and friends, those “your site has updated to WordPress x.x.x” emails can become irritating. The plugin allows you to disable those except in cases of an error.

\n\n\n\n

If someone has not already done so, I would love to see a deactivation plugin to end all deactivation plugins. It would feature a complete list of things that a site owner can turn off, disable, deactivate, remove, or whatever you want from a WordPress website.

\n\n\n\n

No Nonsense looks like a good starting place, but there are always other things that I might remove from an install. I almost always give the ax to the theme and plugin editors. As well as the plugin works, there’s always just a little something more I need to get rid of, depending on the site in question. So, I am still looking for that behemoth plugin that gives me that one-click access to disable anything. For now, I can see myself deploying this on a few sites.

\";s: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, 18 Dec 2021 00:20:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WPTavern: Free Software Foundation Adds a Code of Ethics for Board Members\";s:7:\"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=127388\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/free-software-foundation-adds-a-code-of-ethics-for-board-members?utm_source=rss&utm_medium=rss&utm_campaign=free-software-foundation-adds-a-code-of-ethics-for-board-members\";s: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:4441:\"

The Free Software Foundation (FSF) announced it is implementing a new Board Member Agreement and  Code of Ethics that is meant to guide members in their responsibilities, decision-making, and activities. The documents, which FSF says were “designed to help make FSF governance more transparent, accountable, ethical, and responsible,” were created as part of a six-month long consultant-led review.

\n\n\n\n

In March, FSF founder and GPL author, Richard Stallman, announced that he was returning to the board, after resigning as director of the board and president of the FSF in 2019. His resignation followed a series of controversial remarks on rape, assault, and child sex trafficking, along with two decades of behaviors and statements that many have found to be disturbing and offensive. He was subsequently ousted by GNU project maintainers from his position as head of the project.

\n\n\n\n

Stallman’s controversial return was supported by the majority of FSF’s board, with the exception of board member Kat Walsh who resigned after voting against his reinstatement. The organization’s executive director, deputy director, and chief technology officer also resigned in protest. 

\n\n\n\n

At that time, the FSF’s board published a statement saying they “take full responsibility for how badly we handled the news of his election to a board seat. We had planned a flow of information that was not executed in a timely manner or delivered in the proper sequence.” His reinstatement took FSF’s staff by surprise, as they were not informed or consulted.

\n\n\n\n

Mozilla, the Open Source Initiative, Red Hat, the Electronic Frontier Foundation, and other prominent tech organizations also opposed the decision in published statements and removed their support for FSF and critical funding.

\n\n\n\n

The WordPress Foundation, which previously listed FSF among the project’s inspirations, quietly removed the link from the website following the controversy. WordPress’ executive director Josepha Haden Chomphosy published a statement, saying she did not support Stallman’s return as a board member, and confirmed to the Tavern that this is also the WordPress project’s official stance.

\n\n\n\n

In what appears to be an attempt to claw its way back to a semblance of accountability, FSF’s newly approved Code of Ethics is targeted at preempting future incidents of board members acting on behalf of the organization without permission. A few relevant ethics in the document include the following:

\n\n\n\n
  • Members of the board of directors will not undertake an activity that substantially hurts the FSF. When acting as board members, they will work toward the success of the FSF.
  • Board members shall all avoid placing–and the appearance of placing–one’s own self interest or any third-party interest, including the interests of associate members, above that of the organization as a whole.
  • Board members shall not speak on behalf of the FSF unless given explicit permission. Directors must not represent that their authority as board members extends any further than it actually extends. The board speaks as a whole, not as individuals.
\n\n\n\n

New governance is a positive step towards transparency and accountability, but after all the damage done during the botched rollout of Stallman’s reinstatement, it’s not likely that opposing organizations will settle for anything less than his removal from the board.

\";s: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, 17 Dec 2021 21:45:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"Post Status: Post Status Excerpt (No. 37) — WordPress Community In Africa\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=89996\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/excerpt/37/\";s: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:3639:\"

“You shouldn\'t be the one to always take, you want to be the one to always give.” —Mary Job

\n\n\n\n

In this episode of Post Status Excerpt, David chats with special guest Mary Job. Mary is a remote, “nomad” worker in Africa who travels from city to city. She is an engineer with Paid Memberships Pro but also spends a large amount of time growing and stimulating the African WordPress community. Mary has helped start WP Africa, a site devoted to the community of WordPress users on the continent. She talks about challenges they face, compares the WordPress presence with Google in Africa, and looks forward to the day when there can be a WordCamp Africa.

\n\n\n\n

Also: Mary shares how she got involved in WordPress, and how appreciative she is of the giving nature of the WordPress community. David will have to figure out how to get Mary\'s invite to Matt.

\n\n\n\n\n\n\n\n

Every week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash. \"⚡\"

You can listen to past episodes of The Excerpt, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS. \"🎧\"

\n\n\n\n

\"🔗\" Mentioned in the show:

\n\n\n\n\n\n\n\n

\"🙏\" Sponsor: Pagely

\n\n\n\n

You need durable Managed WordPress Hosting for all your mission-critical sites. Pagely offers managed DevOps and a flexible stack with the same enterprise-level support to all its customers. Peace of mind starts with Pagely. Try it today!

\";s: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, 17 Dec 2021 13:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:28;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WPTavern: Yes, a Block-Based Version of the Kubrick WordPress Theme Exists\";s:7:\"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=127153\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:191:\"https://wptavern.com/yes-a-block-based-version-of-the-kubrick-wordpress-theme-exists?utm_source=rss&utm_medium=rss&utm_campaign=yes-a-block-based-version-of-the-kubrick-wordpress-theme-exists\";s: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:4464:\"\n\n\n\n

It is literally the one thing that no one was asking for, but we can all collectively agree is kind of cool. A block-based version of the old-school Kubrick WordPress theme exists.

\n\n\n\n

Gutenberg lead Matías Ventura tweeted a quick video of it in action yesterday. Fellow Automattic engineer Riad Benguella had put the theme together.

\n\n\n\n
\n

Wait, what? \"🤯\"

(I had no part in this, all credit goes to @riadbenguella.) pic.twitter.com/2WF8HShvSa

— Matías Ventura (@matias_ventura) December 15, 2021
\n
\n\n\n\n

I am always on the lookout for those nostalgic plugins and themes that harken back to my early days on the web, the early-to-mid 2000s, the golden age of blogging. And, there is nothing that embodies that more than Kubrick, WordPress’s second default theme. It was literally named “Default” and represented the platform for over half a decade.

\n\n\n\n

Even today, Kubrick/Default still has over 10,000 active installs. I wonder whether it is running on now-defunct sites or if the number represents still-active bloggers.

\n\n\n\n

The theme was the face of WordPress during its rise to dominance as a CMS. Theme authors owe more credit to it than any others. It was copied, forked, repackaged, and redistributed more times than most of us will likely ever know.

\n\n\n\n

Kubrick 2, as it is named in the GitHub repository, is still a work in progress. There are still a few kinks, such as single posts showing the excerpt instead of the full content. However, it is a working theme.

\n\n\n\n

The shocking thing about it is how little code it took to recreate Kubrick with the block system. The original theme, last updated in 2020 and now at version 1.7.2, falls short of 11 kb of CSS. I cannot remember the last time I saw a classic WordPress theme with so little code. The block-based version currently uses a handful of theme.json settings and has no CSS.

\n\n\n\n

Of course, it did not take me long to dive into the site editor and start customizing. The most recognizable design aspect of Kubrick was its gradient-blue header. It was also one of the pieces that users from around the blogging world would customize to make their site feel like their own. They would decorate it with custom colors, gradients, and even images.

\n\n\n\n

Today, with the block editor, that is far simpler than a decade and a half ago. Plus, there are more options.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n

With such power in my hands back in 2005, I am not sure if I would have pursued theme development at all. I probably could have done everything I needed to do within the WordPress admin. Kubrick was one of my first introductions to theme design, and I owe an unpayable debt to it. It is nice to know that its legacy continues to live on.

\n\n\n\n

For old time’s sake, I spent a few minutes making modifications via the site editor — ever so slightly modernizing it. However, I did not want to lose the flavor of the original work.

\n\n\n\n\n\n\n\n

I am as comfortable as anyone can be in the editor. I know most of its pain points, but this somehow felt more natural than usual. Maybe it was the simplicity of a theme from a bygone era. Perhaps the site editor and I were just seeing eye to eye today. Or, it might simply have been in the cards. I had a lot of fun venturing down memory lane.

\n\n\n\n

I doubt Kubrick 2 sees a lot of action in the real world. Maybe a few folks who are as nostalgic as I am will install it when it is ready for production.

\n\n\n\n

Much like Ian Stewart did with Kirby in 2010, maybe some adventurous theme author will take it upon him or herself to build a modern-day successor to Kubrick. One that both leans into the block system and has readable typography. I am getting older and blinder. A 13px font size is not as easy on the eyes these days.

\";s: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, 17 Dec 2021 00:29:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"Post Status: Matt on Acquisitions and Work in WordPress — An interview with Michelle\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=91488\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://poststatus.com/matt-on-mergers-and-acquisitions/\";s: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:751:\"

Following the 2021 State of the Word, Michelle Frechette spoke with Matt Mullenweg about the wave of mergers and acquisitions in the WordPress space this year and their implications for employment and the product ecosystem.

\n\n\n\n

You can read Michelle\'s and the rest of the Post Status team\'s takes on this year\'s SOTW. We\'ve also got a community discussion hosted by David Bisset following Matt\'s address for you to listen to, and we rounded up reactions to the event from the whole Post Status 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Dec 2021 18:20:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Dan Knauss\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"Post Status: Post Status Comments (No. 4) — State of the Word 2021 Analysis\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=91445\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/comments/4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:77750:\"

Members of the WordPress Community on Their Takeaways from SOTW

\n\n\n\n

This episode of Post Status Comments features a live conversation in Twitter Spaces that was recorded right after Matt Mullenweg‘s State of the Word 2021 broadcast on December 14th. Bet Hannon, Eric Karkovack, Maciek Palmowski, and Rae Morey joined David to share their reactions. Others from the audience join in, including Jeff Chandler, Ryan Marks, Hazel Quimpo, Scott Kingsley Clark, Jason Taylor, and Amber Hinds.

\n\n\n\n

Among the questions discussed: What stood out in the State of the Word for each of our guests? What did they think of Matt Mullenweg\'s take on web3, NFTs, and ownership? Was there agreement about Matt\'s points on WordPress market share, acquisitions, and contributions to WordPress core teams?

\n\n\n\n

This engaging conversation went on for a little over an hour.

\n\n\n\n

Bonus: Michelle Frechette caught Matt for a brief interview after the SOTW address, and we rounded up reactions to the event from the whole Post Status team.

\n\n\n\n\n\n\n\n

Post Status Comments \"💬\" provides a stage for WordPress professionals to exchange ideas and talk about recent topics and trends.

Browse past episodes and subscribe to our podcasts on  Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or get them by RSS. \"🎙\"

\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n

\"🔗\" Mentioned in the show:

\n\n\n\n\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n

\"🙏\" Sponsor: Pagely

\n\n\n\n

You need durable Managed WordPress Hosting for all your mission-critical sites. 

\n\n\n\n

Pagely offers managed DevOps and a flexible stack with the same enterprise-level support to all its customers. Peace of mind starts with Pagely. Try it today!

\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n

Transcript

\n\n\n\n

David Bisset: [00:00:00] Uh, my name is David Bisset. I am one of the people at post status. Um, if you\'re not familiar, go to post status.com. It\'s a great community. In fact, they might as well be sponsoring this whole thing. What we do is we record, we do Twitter spaces every once in a while we record them and we make them available as podcasts.

\n\n\n\n

So, um, a few rules before we get started here, as we still get a few more people coming in, um, just we\'ll make it very simple, prove a code of conduct. Just pretend this is a work camp. Be nice. You try to be family friendly in terms of your language and your feedback and your comments. And be be advised that this is a public space and you will likely be recorded and used later in a podcast or something like that.

\n\n\n\n

If you are listening on your mobile app, you have the opportunity to request, um, feedback. We would like to, uh, like to ask if you could limit your questions or feedback to at least 30 or 60 seconds at a time. Initially that [00:01:00] way we are only planning for maybe 30 minutes or so of discussion this evening may be a little bit longer.

\n\n\n\n

So we\'ll try to get to everyone. And I know people are still digesting what Matt spoke about tonight as well. I didn\'t get a chance to hear everything he said either. So we\'re hoping if we don\'t bring up some things that were covered. And if you feel like something was important that stood out into night\'s state of the word, then please feel free to bring it up.

\n\n\n\n

We\'re also watching the post status slack right now on the club channel. If you feel like typing rather than talk. So anyway, um, there is a distinction just once again, we had some confusion on this last month, you can listen to Twitter spaces on the desktop that does work, but you will not be able to raise your hand or talk as far as I know you need the mobile app for that.

\n\n\n\n

So if you feel like you want to contribute, switch over to the mobile app. Okay. So we have with start off with our initial four, um, speakers for tonight. [00:02:00] Um, Eric, can you tell us just a few seconds of, can you unmute yourself first of all, Eric, and tell us, um, who you are in the WordPress space in 30 seconds or less.

\n\n\n\n

Eric Karkovack: I\'m Eric Karch, evac. I\'m a web designer and writer for specie boy.com. And I\'ve been using WordPress for well over a decade. And this is my 25th year in the industry overall.

\n\n\n\n

David Bisset: Um, Ray, is this the F, is that your first? Am I doing that? Right? There was only three letters, but I feel like, okay. Where, where are you from right now in the world? 

\n\n\n\n

Rae Morey: Um, I\'m based in Melbourne Australia. It\'s currently just after 11:00 AM here.

\n\n\n\n

David Bisset: I am so stinking jealous, but go ahead. What, what published, what publication are you from?

\n\n\n\n

Rae Morey: I published the repository. It\'s a weekly newsletter that, um, takes a bit of a deep dive into the news each week and, and kind of picks apart [00:03:00] with the headlines and what people are saying about 

\n\n\n\n

David Bisset: oh, excellent. We\'ll be look forward to hearing some of your comments. Um, Mr. Palomo Palomo whiskey. I think I butchered that like some fine beef.

\n\n\n\n

Uh, can you, uh, unmute yourself and tell us a few things about. 

\n\n\n\n

Maciek Palmowski: Yes, you did a bit. Uh and, uh, well of course, when you say it that fast, it sounds better, but go ahead. Yeah. Uh, yeah, you know, Polish is, is, is very hard. So English is hard for me, but yes, but if you\'re from another publication as well. Yes. Uh, I am from WP owls, uh, which let\'s say I do at night because, uh, during the day I am a hundred percent Basadur at body and, uh, w P owls.

\n\n\n\n

Uh, we also try to find some interesting things that are happening in the WordPress space. Uh, we try to [00:04:00] focus a bit more on the things that happens for developers, but of course, we also find all the news and try to share everything with this interests. Hmm. Here at night. WPLS I S I see the connection.

\n\n\n\n

David Bisset: All right. Finally, that Hannon welcome to the program. 

\n\n\n\n

Bet Hannon: Hi, David I\'m Ben and I live in central Oregon and the USA. I run an agency that designs and develops WordPress does manage hosting for WordPress. So we have a specialization with accessibility. So we do a lot of things with accessibility, and I\'m also a local meetup organism.

\n\n\n\n

David Bisset: So we, uh, we have a little bit of a diverse bunch here in terms of, at least we have at least an agency owner. We have a couple of people from the news we have, and there\'s a lot more interesting people that hopefully we\'ll get to meet in the audience as well. So Eric, why don\'t we start with you from maybe a developer perspective, but from any perspective, what\'s the biggest thing that jumped out at you that Matt talked about tonight?[00:05:00] 

\n\n\n\n

Eric Karkovack: Well, first of all, I was glad that he, he kind of explained, uh, you know, the whole web series. Um, topic that, you know, we weren\'t quite sure what he was going to say on that. Uh, we weren\'t sure if maybe he was going to introduce NFTs to a WordPress somehow. Uh, so I was glad he kind of, um, spoke about how that already fits in with work.

\n\n\n\n

WordPress, WordPress is already doing it. It is a decentralized platform. It is, um, you know, something that you own the content of your site. So I was really happy about that. And I think the other thing that really, um, interested me was when he was actually talking about his youth a little bit about his time building B2, um, those things kind of stood out to me because he started out much the same way I did no, you know, formal education and it just did it because he was passionate about it.

\n\n\n\n

And I think that\'s something we don\'t always hear from Matt. So I thought that was, um, [00:06:00] really great to hear.

\n\n\n\n

David Bisset: He seemed to be a little more personable. I mean, I don\'t mean, I, you know, I guess I\'ll go next and a little bit in terms of what I thought overall. Um, we\'ll, I\'ll let you all handle the technical, but overall, maybe it was the smaller stage.

\n\n\n\n

Maybe it was the fact that he hadn\'t spoken in front of people maybe in two years, I think he said, or maybe he, or at least in front of a WordPress crowd, he seemed to like be more happy or at least like a little bit more. And he seemed to be a little bit more, um, I don\'t know. I can\'t really put a word on it of personable or, um, maybe nervous too, maybe a little bit of that.

\n\n\n\n

Maybe it could have been the most nervous. I\'ve seen Matt out of state of the word in a long time and maybe that was because of the proximity or because of COVID or whatever. Um, 

\n\n\n\n

Bet Hannon: I think it\'s really different when you\'re speaking to a small. Based versus thousands, you know, thousands of people in a big auditorium, it just feels really different when you\'re in front of a small audience since we, you, since we have you bet, why [00:07:00] don\'t you tell us what, what\'s the one thing that probably stood out to you the most now?

\n\n\n\n

Yeah. Yeah. You know, it\'s actually a thing that kind of surfaces again and again for me, and it\'s a little bit of a push Paul. And so, uh, uh, on the one hand, I really celebrate all the ways that we are, um, making customization so much apart. And we\'re giving so much ability for people with little or no coding skills to be able to do these amazing things with their sites.

\n\n\n\n

As an agency owner, you know, I have clients who have, you know, five or 10 or 15 content creators, and they don\'t want to give that kind of, they don\'t want their content creators necessarily going off brand for example. And so there\'s, uh, I\'m always kind of trying to think about, uh, you know, balancing that out or, uh, thinking about how will we help our clients work with their content creators, amid [00:08:00] all of this amazing ability to customize.

\n\n\n\n

David Bisset: As an, as an agency owner where you overall satisfied with what was presented tonight. 

\n\n\n\n

Bet Hannon: Oh yeah. You know, uh, it\'s always great to hear how things are going, looking. Uh, I thought it was really interesting the, um, the perspective that Matt was giving on some of the acquisitions, but it\'s a, it\'s not just happening in WordPress, that there\'s a much broader kind of, um, you know, that\'s happening at a much larger scale and all across many industries.

\n\n\n\n

And, um, so yeah, no, I, I really was pleased. 

\n\n\n\n

David Bisset: So, um, our, our WP gals and our repository people here, they cover the news. They cover acquisitions as far as everything else. I\'ll let you decide which one of you wants to go first, but again, same question. What was the biggest thing that stood out to you during maths?

\n\n\n\n

Talk the seat. 

\n\n\n\n

Rae Morey: I\'m happy to jump in. Um, I think, um, [00:09:00] one of the big things for me, I think, which you\'ve kind of already touched on is the energy of the address today. Um, it was very obvious that Matt was really happy just to be around like-minded people who, like he said, I got him dancing, a jig as an animator, which he also pointed out or your case, but it was really nice seeing him so happy he\'s been there and vocal about how uncomfortable he was last year during the prerecording.

\n\n\n\n

So it was nice to see him in front of a crowd again. Um, but I, I guess just the energy of seeing things moving forward again, after a bit of a, not a stagnant past couple of years, but things have been a bit slower with contributors being involved, I guess in WordPress has been, um, a bit of a slow down in number of people contributing to the project.

\n\n\n\n

Um, And I, he was feeding off the energy in the room, as bet said. Um, I guess one of the other takeaways for me was, um, just, uh, you know, uh, [00:10:00] we didn\'t know what he was going to talk about, um, around web three. And, and if T\'s, it was, uh, you know, there a bit of speculation around what he was going to say, few ideas floating around, but it was really nice to see or to hear him talk about, you know, basically WordPress is already leading the way when it comes to web three to centralization of the web and, and ownership over content.

\n\n\n\n

So it was really nice for him to address that and, and talk about where WordPress fits into that space. Um, you know, as well as the focus on open verse and, um, you know, where that\'s going to go in, in 2022 is, is really exciting. 

\n\n\n\n

David Bisset: Oh, and Mr. Owl, I feel like I need to ask you something about the Tootsie roll pop, but I don\'t think the kids today will get that.

\n\n\n\n

Maciek Palmowski: So, um, for me, uh, there were two things that really stood out. First of all, uh, when he mentioned the number of, uh, people doing translations and the languages in the repository, uh, because [00:11:00] I am a non native English speaker, which probably you can hear with my thick accent. 

\n\n\n\n

David Bisset: I think it\'s cool. 

\n\n\n\n

Maciek Palmowski: Thank you. Uh, but um, I know how many people in Poland, for example, need to see their CMS in, in Polish because English, it\'s not something they want to, they want to read some, some of my clients that I had don\'t even knew English or just didn\'t felt comfortable with it.

\n\n\n\n

So, um, the, the growing number of polyglots, this is really something great. And this is really a thing that, uh, Um, that will really make WordPress bigger and bigger. Uh, w when we confronted with, uh, other CMS is out there because most of them are still mostly created and maintained [00:12:00] in English. So this is something very important.

\n\n\n\n

And there was one sentence that was also very intriguing for me. Maybe I, um, I misheard it, but I thought that Matt, at some point mentioned something about breaking a bit, uh, how he called it, that backward compatibility. Yeah, he did. I remember him talking about that, what specifically thinking of exactly.

\n\n\n\n

And this is, um, I know that he mentioned it, uh, in the, in the context of, uh, in the context of themes, maybe, maybe, and this is. A bigger step to some bigger changes in, in inside of core, inside of, uh, uh, of, of, uh, of the coal tooling and stuff like this. So, uh, really Matt saying, let\'s break the [00:13:00] backwards compatibility.

\n\n\n\n

This is something huge. 

\n\n\n\n

David Bisset: Did he say that though? Break? I remember I may have missed that quote. 

\n\n\n\n

Maciek Palmowski: You mentioned something. I mean, it wasn\'t, uh, as the size, if it\'s let\'s break that backwards compatibility, but in terms of WordPress, when we, I would say we have a bit paranoid, backward compatibility, which is great in some cases, um, Talking about breaking any backward compatibility is something.

\n\n\n\n

David Bisset: Yeah. Matt did quote, this was a quote in this again, take, take in context and keep in mind that, you know, we\'ll listen to this again. And again, probably a few times to get a better understanding of what was said, but he did say in the presentation that a theme that was created with like an early version of WordPress, will it be like 1, 2 0 1, 5 or something like that would work with WordPress 5.9 next month.

\n\n\n\n

That is what he said. And that\'s his, and that he said, quote, that\'s how serious we are about backwards compatibility. [00:14:00] Um, but like we said, that I would have to go back and listen, but I know, I know at least currently has strengthened backwards. Compatibility seemed pretty strong, at least from that statement now, whether or not it stays that way.

\n\n\n\n

Maciek Palmowski: Um, but I think it was a sentence before, when he mentioned that. The developers should move from the old editor to the new one. So we should update. So this is something, uh, but, uh, yes, I, like I said, I wasn\'t sure about this, but, uh, it caught my attention. So I think that, uh, yeah, I will have to relisten it once again to, to make sure.

\n\n\n\n

David Bisset: So we\'ll let, we\'ll let that, uh, bet chime in here and then I\'m going to open before you start that. I\'m good. Then after you, I\'m going to open the floor a little bit of a few other people who are going to raise their hands and we\'re going to keep everyone on stage though. So you can keep interjecting back and forth.

\n\n\n\n

We\'re not kicking anybody off. I\'m sorry. Go ahead. 

\n\n\n\n

Bet Hannon: I might be wrong, but I think that Matt was referring to the breaking the backward compatibility in terms of the introduction of Gutenberg that the Gutenberg would break a [00:15:00] backward. That that would not be backward compatible as we move forward with blocks. Well, I might be wrong.

\n\n\n\n

David Bisset: Well, I don\'t know about you, but some of my old themes won\'t work with flux gear guaranteed. Yeah. And, and the old editor things in the old adage that use that tiny MCE editor are not going to work. And so there\'s some backward compatibility that is broken with the introduction of blocks. So, um, all right.

\n\n\n\n

Uh, Jeff, welcome to the show. Welcome on stage. Um, Eric Ray, Brett, and Mr. Owl. I\'m going to refer to him as, um, are still on stage with us and are going to interact with anybody we bring up. Can you hear us, Jeff? Uh, absolutely I can. And Ray, you have an awesome accent. Thanks for that. She has, she\'s also in the morning too, so she\'s got that.

\n\n\n\n

Perkiness that currently very few of us have right now, but oh, I have a coffee. So I\'m doing well, sorry. You\'re not making me [00:16:00] like you in any more, right. Uh, so Jeff, what for the, for us up here on stage and for the rest of the audience, what would you like to share about what you heard.

\n\n\n\n

Jeff Chandler: Um, I, you know, I think people on the, in a web three space might look at what Matt said on stage as him maybe Disney web three.

\n\n\n\n

But I think what he did was he cautiously tiptoed around the subject. He brought it up, he skimmed the surface. So I think at the very least people know that he\'s aware of it. He\'s going to keep his eye on it. And it may come up again in next year\'s state of the word, but I don\'t, I think you did a good job with bringing it up.

\n\n\n\n

But one of the things I also enjoyed that he brought up, I\'m glad that he brought up was when he went over the market share numbers. And this is something that Yoast EVOC did in his CMS market analysis posts is that he talked about how software as a service company is Wix Squarespace. And, uh, some of the other ones they\'re all rapidly growing and all of the open source solutions minus WordPress are losing.

\n\n\n\n

And I was glad that he brought [00:17:00] that up and that\'s something that we should keep an eye on. Uh, here in the next few years, 

\n\n\n\n

David Bisset: He also said something interesting too. About, and this was in a different part of the presentation, but regarding Drupal and Joomla, I got him quoted as saying he thought they would be more successful if they had apps, which I thought was interesting.

\n\n\n\n

Jeff Chandler: I, I thought, I thought they had the apps, but if they don\'t, I think that\'s a very valid point.

\n\n\n\n

David Bisset: Yeah, that\'s true. So market share was definitely something that, that brought up 43%. And I won\'t go into it now because it\'s not relevant to the state of the word precisely, but wean very soon because of an Amazon shutting down, Alexa, we may not have the privilege or the opportunity to have percentage of market share numbers like we do today, so that, you know, examining this information now for Matt, I think during the state of the word is very important because without those are W3C texts, numbers are based on Alexa and Alexa is shutting down in, I think may of next year, Amazon shutting it down, not that Alexa, [00:18:00] the other Alexa, and I\'m just turned on a bunch of Alexis and people\'s houses.

\n\n\n\n

Jeff Chandler: And one of the last things I\'ll say here before I get off, is that I think it\'s obvious that 20, 22 is going to be the year of the open verse. 

\n\n\n\n

David Bisset: I, I can\'t, I, every time I think of open verse, I think of something else and I hate myself every time. I think of that associate, thank you very much, Jeff, for, for sharing with us, Scott.

\n\n\n\n

Um, let\'s see. We\'re inviting Scott upstage or SKC. I think he likes to, I think that\'s his rap name. 

\n\n\n\n

Scott Kingsley: Hey, what\'s up? 

\n\n\n\n

David Bisset: What\'s up?

\n\n\n\n

Scott Kingsley: Let\'s say Casey, you know me? 

\n\n\n\n

David Bisset: Oh God. He started her up already quickly before, before he does tell us what you thought of tonight. 

\n\n\n\n

Scott Kingsley: Uh, the 

\n\n\n\n

lack of banana milkshake representation, it was kind of a disappointment, but, and wanted to run that operation banana milkshake failed.

\n\n\n\n

David Bisset: It was fine. Nobody knows what we\'re talking about.

\n\n\n\n

Scott Kingsley: Oh, one out, but, uh, availed on asking the question. [00:19:00] So, cause he got up right near the end. I was like, oh, come on. You can get, you can get the question in there. But uh, I thought it was really interesting. Um, well obviously. I think web three is a whole thing, but I\'m really glad that he brought it more towards like reminding people.

\n\n\n\n

You need to remain cautiously optimistic about things and keep things open. Um, especially from the perspective of making sure things are, are done right. And you\'re not watching hucksters and stuff, but, um, but I think maybe the part I really liked the most was probably all around how, um, collaboration is phase three and we\'re, I know we\'re still a year out now, but, uh, if we could have gotten to that in 2022, I think that would have been a pretty big thing because there\'s so much about the collaboration idea of just like going into, um, uh, Figma or Google docs and you seeing everyone else were working together and, and just that collaboration aspect of things could make things so much easier, especially on the open web, we\'re trying to replace something like Google docs, [00:20:00] having an experience like that inside of WordPress and being able to collaborate like that would be pretty, pretty.

\n\n\n\n

David Bisset: Yeah, I wish I knew more about it in terms of, um, he did say he was going to talk about web three and he did say NFTs in his blog post, but I don\'t think he said much about it unless I missed that part. I think he was just putting a bunch of keywords together. Um, yeah. Um, but he did make it a point to kind of bring up the larger issue about what those individual things stood for, at least from a philosophy philosophy standpoint, what you hear on the web in terms of, um, ownership.

\n\n\n\n

And I\'m drawing a blank on the other things right now, but he did really kind of go into why WordPress was representing those things. And he did make a point that you can overlook some of the things that are the WordPress has four freedoms can be overlooked if you focus too much into some of the, I don\'t think he used the word hype, but I think he meant something like it.

\n\n\n\n

So [00:21:00] there\'s a danger there overlooking what he thinks are the critical freedoms to WordPress. Eric, did you have. 

\n\n\n\n

Eric Karkovack: Yeah, I think he was also talking about decentralization a little bit with that. Um, just the basic idea that, you know, you can take your WordPress website with you to any host. Um, maybe it doesn\'t fit in exactly with like something like blockchain.

\n\n\n\n

Um, but it does kind of speak to, you know, the danger of going with, uh, you know, his favorite, uh, competitor Wix. I think he said that WordPress grew by two Weeks\'s over the last year, which was kind of a good line. Might have been my favorite of the night. I, I have a, I have a little chalkboard up here and every time he made a mark a comment about Wix, I drew a line and I\'ve got a couple of lines here on the board, but yes, he did make that comparison.

\n\n\n\n

David Bisset: Go ahead. 

\n\n\n\n

Eric Karkovack: Okay. I just going to say, I think that, that, um, you know, having that ability to move content from place to place is what\'s going to [00:22:00] separate. WordPress from everything else right now. I mean, as we see Joomla and Drupal dropping down well, WordPress is kind of like the last bastion of hope for open source at this moment.

\n\n\n\n

Maybe. I don\'t know, like see what other people think about that 

\n\n\n\n

David Bisset: You need to write a transformers movie.

\n\n\n\n

 That was excellent.

\n\n\n\n

Eric Karkovack: Well, I, I think, you know, if, if, if that\'s the case, then you know, that\'s going to be the big selling point. Um, I actually had someone in my family wanted to start a blog this week and I pushed him to WordPress and not to Squarespace or Wix, because if you don\'t like the service, you\'re not going to be able to just take the website with you.

\n\n\n\n

It doesn\'t work that way. 

\n\n\n\n

David Bisset: So let me let, speaking of that, um, let me ask a broader question. Cause I get a feeling we\'re going to boomerang back to the web three stuff anyway. Matt said, and this question goes for everybody on stage or anybody in the audience. Matt did say a quote later on in his, um, I think in his Q and a about, he said that, um, [00:23:00] 85% or some big percent of the web doesn\'t really care about it was either open source or owning your own content or something along those lines that most that WordPress would have in order to be usable.

\n\n\n\n

WordPress would have to be a great user experience and WordPress will be invisible to those people. And that\'s okay. Does, what does anybody think about that? Do you agreed, or do you, do you think that number is larger or smaller or does that seem to gel with your philosophies and your observation?

\n\n\n\n

Bet Hannon: That\'s true for a lot of people, they think they just, you know, uh, they just want to get the website up and they\'re really, uh, a little more platform agnostic. They want to know. Is it going to be hard? Right. They want to know about ease of use. They don\'t, but they don\'t really care that it\'s open source for not.

\n\n\n\n

David Bisset: Jeff, what do you [00:24:00] think?

\n\n\n\n

Jeff Chandler: Uh, I think for a lot of people that way, he said in terms of like maybe one or 2% of the people who understand TPO and its freedoms and what they mean, uh, those are the people, very, very small percentage of people. Uh, you know, it be an open source is not the concern. It\'s how to get the aid to be the fastest and the easiest.

\n\n\n\n

And you, that pretty much explains why a Shopify and somebody software as a service solutions are growing a market share because they\'re providing a great user experience for a lot of people out there to get from a to B quickly and easily. So I think it was a nice for Matt to bring it up and saying, you know, if we\'re going to, uh, become the dominant player and get open for some more hands that even if it means that we\'re presses invisible.

\n\n\n\n

David Bisset: That\'s okay. Yeah. I think that\'s reasonable. I think that\'s a little hard for some of us to like we accept on the surface, but I think some of us have to kind of dig down a little bit and realize that some of the things that we\'re passionate about us, not what 99% of most people passionate about. You know, they want something that works.

\n\n\n\n

Ray Ray, uh, did [00:25:00] you have something to say, and then I\'m going to bring in a new speaker?

\n\n\n\n

Rae Morey: Yeah, no, I\'d absolutely agree if you\'re running a small business, you know, like my hairdresser, for example, she just built a website recently to support her new business and she\'s, um, using, um, GoDaddy, um, and they\'re, you know, website builder, and she built a site in an afternoon really easily with WordPress and, you know, people like that, they don\'t want to muck around with something that\'s really tricky to, to work with.

\n\n\n\n

They, they wanna drop in their images or their content and have their website up and running with in her case. E-commerce as well, really quickly. And, um, you know, it\'s important. Um, platforms like, you know, it\'s not all about, um, WordPress being the center of attention in, in that space. It\'s, it\'s about elevating the user experience and making sure that users, um, can, um, have the tools they need to run their business without WordPress necessarily being front and center.

\n\n\n\n

Maciek Palmowski: And, um, [00:26:00] I wanted to mess one more thing because when the whole COVID madness started, many people realized that their business needs a website. Right. And you all remember that this was the moment. Uh, workers had a much bigger amount of downloads. WooCommerce was downloaded the biggest amount of, uh, of times.

\n\n\n\n

And this was because first of all, workers was kind of popular. So people were able to find materials about how to insulate, how to create their first e-commerce. So they could, so their business could work during the pandemic. And it seems that WordPress was easy enough for them to just start to make their business round during those, uh, those hard times.

\n\n\n\n

And probably during the process, [00:27:00] they started to. More and more things, how to optimize some things. And some of them learned probably a finger to about, uh, about C, about search engine optimization about performance and stuff like this, but still, uh, we saw how many businesses started their websites on WordPress, because it was easy.

\n\n\n\n

It was free. 

\n\n\n\n

David Bisset: Yeah. Free. In fact, a real Aruba hope. I probably butchered your name in the chat. She says, I think for a lot of folks open source means free in that vein for some folks, open source also means hard to install. And she says, when I pitched WP, I rarely talk about the open source aspect. I talk about the ease of use security, constant updates, et cetera.

\n\n\n\n

So, you know, playing to the strong, playing to the strong points there. If it\'s okay with you, Mr. Owl, I liked to switch over to Hazel. Who\'s been waiting patiently. Hopefully she\'s not mad at me. 

\n\n\n\n

Hazel Quimpo: Hi. I don\'t get mad. Um, [00:28:00] quick. No, I mean, I think I\'m on the same page with a lot of the folks is like, I don\'t know.

\n\n\n\n

I think of like travel agents, right? And I feel like we\'re at this stage where, you know, you used to go to a travel agent to get all your stuff. And I think if you have a really small website, you don\'t need to even go to like your cousin. Who\'s a WordPress developer. Well, you might need to today. But I think that the expectation is you shouldn\'t have to.

\n\n\n\n

Um, and I like from the lay person who doesn\'t know about WordPress, who doesn\'t know what, whatever they think they should be able to go and set up their website and frankly they can. And I think that\'s where we need to realize that\'s where the people, I was recently looking at tons of web hosts. And so many of them tout like image compression.

\n\n\n\n

And do you know how many people I know that start businesses every day, who care about image compression? Like zero to say a lot, but I guess I was way wrong

\n\n\n\n

for touting these things. Expect. And I think we need to realize some of that when we do WordPress stuff is like, cool. Like we do believe in the open source nature of the things we believe in [00:29:00] owning your content. But I view it a lot of the way. Like, you know, my doctor tells me to drink less and eat healthier, and I think that\'s a good idea, but I don\'t care that much.

\n\n\n\n

And I think that\'s how the rest of the world is right. And Hazel, for as long as we have you in the living, as long as we have you in the living world. 

\n\n\n\n

David Bisset: Thank you for, thank you for that. Um, I\'m gonna put, I\'m gonna put you back into the audience, but for the love of God, please don\'t disappear right away cause you\'re scaring me now. Um, stick around please in the world that we\'re living and in our, in our little chat room here, Dave, Ryan, um, you\'re onstage. Welcome to whatever we\'re calling this little freak show. How are you? Apparently Dave\'s a quiet person. That\'s fine. 

\n\n\n\n

Dave: Sorry, Twitter space is cut out there for a second.

\n\n\n\n

David Bisset: No problem. Real quick. Tell us what you thought of that. What, what stood out to you or what did you, or maybe you\'re responding to someone else\'s comment? 

\n\n\n\n

Dave: Well, I guess on the current topic, I think of WordPress. You know, if we look at [00:30:00] automobiles, there\'s a lot of different ways to get where you want to go, right?

\n\n\n\n

But WordPress is ideally these sort of Toyota Camry, the undeniable, you know, lay person, car that anyone, you know, that almost just blends into the background, but is everywhere. And you live where I live with. But also, you know, like the Ford transit van, if we\'re looking at blue commerce, the thing that every business needs to get, where it needs to go and, you know, it can be customized.

\n\n\n\n

Um, I guess the one thing that really stood out to me about the presentation today is just kind of the talk about the open verse photo directories, digital art, the project doesn\'t really have an apparatus today to do content moderation at scale. And I\'m not sure that that\'s something that volunteers could really easily be asked to do.

\n\n\n\n

Um, you know, once you create a way for people to easily express themselves, you also open up, you know, copyright [00:31:00] issues, uh, hate, um, questions about what\'s decent and what isn\'t, and you have to navigate a global web of legal frameworks or. So I think as excited as I am about those ideas, and I think it\'s a great opportunity.

\n\n\n\n

I also think that Twitter and Facebook have proven that money and AI don\'t necessarily solve those problems. And so I\'m just curious how the project that going forward. 

\n\n\n\n

David Bisset: That\'s uh, I would, I would say that too, Adam attempted to ask that toy. He did ask it, um, or attempted to address that as well. And I\'m, I\'ll, I\'ll be honest with you.

\n\n\n\n

I don\'t know much about now there was a distinction between the open verse project and the, what was the other thing? Was the WordPress photo project or photo library? Something, um, I\'ll admit. I admit I, I\'m not really good in depth on both of those, by the way. Did I mention, I worked for post tennis? Um, But I, yeah, so there was definitely talk of like, if you uploaded a [00:32:00] photo somewhere with that data, some of the data that sticks to it, you know, like how you upload a photo, like if you upload a photo to Twitter, for example, from your phone on your phone, there\'s metadata attached to that photo.

\n\n\n\n

And when you upload it to Twitter, it\'s gone. Um, but that\'s just, that\'s just one level. And what you\'re talking about is the, what hits the news a lot, like in terms of, you know, you could be posting photos without people\'s permission, or you could be posting hate speech or that sort of thing. So, and we all know that\'s a moderation nightmare, right?

\n\n\n\n

Guest: I think today, the ways that we contribute to WordPress have a steep enough curve and our barrier to entry that we don\'t deal with as much of that. But I think the big question is going forward as we make it radically easier to contribute, how are we going to tackle the problem that all these other networks have had to deal with once they scale.

\n\n\n\n

David Bisset: That\'s an excellent question. I feel like I\'m still at the Q and a part of State of the Word. I really, yeah. Subtly we should, [00:33:00] we should get that question in front of Matt and some other, some other people\'s. So I think that\'s an excellent question. Dale has decided they don\'t have a really good answer.

\n\n\n\n

A thought about that. Thank you though, for, for speaking up. Um, so one of the other things that was spoken about here, and I get a feeling this was in, in an inescapable gravitational force in 2021 was acquisitions. And we mentioned this briefly. Um, do you agree, does the, is there anybody here that maybe sees Matt\'s point, but has a different opinion in terms of this is I think it\'s, I think the point he was getting across was this is happening everywhere.

\n\n\n\n

It\'s not just in the WordPress space. Is that, is that generally something that you would agree to? Um, the way he presented it, especially with lots of nice old charts. Does anybody have an opinion on his take on acquisitions?

\n\n\n\n

And if I can take a silence as a yes. If anybody wants to, [00:34:00] I, I can, uh, chime in, I guess. 

\n\n\n\n

Jeff Chandler: Um, I think one of the things he mentioned, he mentioned Yost by name, and I think he also talked about, you know, the number of employees and what they\'re doing and kind of extrapolating the impact that, that accompany like that has like all the millions and millions of websites that are like, just for example, running Yoast right now.

\n\n\n\n

Um, and I think he\'s what he\'s kind of getting at is that there\'s a lot of responsibility in that. And for a lot of smaller entrepreneurs who started out with these plugins. You know, maybe that\'s just getting to be to a point where they\'re just not able to do it anymore. I know that was part of the, the case with advanced custom fields from they, they were sold, um, you know, it was a one man operation with a user base in the millions and, you know, kind of how do [00:35:00] you, how do you manage that?

\n\n\n\n

How do you continue to, to support it and build the product at that scale? When, you know, you\'re just a small group of people or even just an individual. Um, so it\'s, it\'s a matter of WordPress is growing so radically big and you can\'t be a one person team, especially on something that large sure. Seems like it these days.

\n\n\n\n

I mean, I I\'m, I don\'t doubt that, you know, individuals are still gonna come up with amazing things, but to compete at the level of a Yoast or an AC. I don\'t know how that\'s sustainable for a long period for such a small group of people.

\n\n\n\n

David Bisset: Well, I think that also, and not to get off track here because this isn\'t, I think Matt didn\'t mention this at some point directly cause he ma he brought up the CD comic about, um, about it there\'s I tweeted [00:36:00] it, but I\'m looking, I\'m trying to look at the picture right now.

\n\n\n\n

It\'s basically about picture a all modern digital infrastructure being a giant castle. And there\'s this one little piece of the bottom that says a random, some random person in Nebraska, thankfully maintaining a project since 2003. Um, that, that is kind of also the same problem, in my opinion, in terms of like, it is this, there is a strength of open source and yet there\'s this weakness.

\n\n\n\n

And I think this week two, if anybody\'s been following the news about the Java exploit that came out on Friday, who\'s named now, I\'m not remembering logs. Um,

\n\n\n\n

Guest: log4j

\n\n\n\n

David Bisset: yes, that\'s, that\'s it. So we\'re beginning to see these things happening outside of WordPress and open source that we\'ve been kind of contemplating now for quite some time, whether it\'s bugs, whether it\'s something that needs to be addressed in terms of open source manpower, or woman power human power, or it\'s a, like you said, Eric, it\'s an acquisition thing you absorb, somebody gets [00:37:00] acquired because they can\'t physically maintain it on the same scale anymore.

\n\n\n\n

Um, did that did accurately that I accurately represent you there? Eric didn\'t mean to? 

\n\n\n\n

Eric Karkovack: Oh yeah, absolutely.

\n\n\n\n

David Bisset: Okay, great. I\'ve got uh, oh, Ooh. We\'ve got an entire company on the line right now. It\'s Pagely so this, this should be interesting. Pagely uh, who specifically inside page? 

\n\n\n\n

Dave from Pagely: It\'s Dave struggle as I\'m probably having dinner right now.

\n\n\n\n

David Bisset: Bless his heart. Go ahead, sir.

\n\n\n\n

Dave from Pagely: Well, it\'s great to see us on the big board with the acquisitions. It\'s been quite a month for us. We\'ve been part of GoDaddy now for a little over four weeks, and I want to dovetail something that was said earlier, which I tweeted a Jeffer a second ago. Um, we should be concerned about closed source platforms gaining in popularity, um, because none of us want to see the depth of the open web, right.

\n\n\n\n

And it\'s great to see or press with the market share that it has. And you know, when everyone kind of says we need to get online, what\'s the first thing I think of is usually [00:38:00] WordPress, which is great. Um, Well, we\'ve been brought in to build with GoDaddy is this next generation of, of an open source commerce product on top of WooCommerce.

\n\n\n\n

And that gets us excited because that is open source. That\'s going to be built upon this platform and not, you know, going the way of, you know, Wix or Squarespace or any of that. So, you know, we\'re, we\'re still kind of committed to that, making sure everything is open source and that the open web doesn\'t go away.

\n\n\n\n

David Bisset: Hmm. Okay. Well, send a thank you very much and thank you for being a recognizable P avatars. I could quickly point around right here. Thank you. I mean, oh, sorry. Sorry. Going through a tunnel, going through a tunnel right now. Sorry, I can\'t hear you. No, we\'ll, we\'ll keep you on. We\'ll keep you on the stage a little longer.

\n\n\n\n

Um, Ryan, welcome to the party. Do you, did you have a comment for the group, Ryan? I [00:39:00] think that\'s Ryan mark. It is. Yes. Okay. Ryan, welcome. Welcome to the show.

\n\n\n\n

Ryan Marks: Oh, well, thanks. Uh, the, the graphic that you were talking about and the person in Nebraska reminded me of the recent news with the PHP foundation and the fact that there was a bus factor of two, uh, with respect to how many people actually knew the code base, according to articles.

\n\n\n\n

And, um, I just thought that was somewhat similar, right? 

\n\n\n\n

David Bisset: So, yeah, so I\'m, so this was all coming to the original, um, me bringing up the acquisitions part of it. And some of it is the acquisitions that especially, I think it absorbed the one or two people. The small companies are, are probably doing WordPress a favor in some regards in the long run, because otherwise, like you get hit by a bus, what happens to advanced custom fields, which a lot of people rely on, uh, I think Matt presented that pretty well in terms [00:40:00] of, um, the numbers and some people, some people have different opinions about what is happening in the WordPress space, but there is some validation or some validity of taking a step back and looking at the largest.

\n\n\n\n

There was one bar graph and I\'ll be honest with you. I\'m not really that business oriented again. I work at post status. Thank you very much that on 2021, a bar graph just like shot the way the heck up. I think it was the, um, think it was, it was, it was something about the money that was, that was being transferred at hand-to-hand or something along those lines.

\n\n\n\n

Um, it\'s just 20, 21 just basically exploded for the rest of the tech industry. And WordPress is a part of that tech industry. So it\'s not just WordPress and, but at the same time, I think WordPress has its own valid reasons for why it\'s happening. There were 42 logos on Matt\'s slide. At one point we have a WordPress acquisition tracker.

\n\n\n\n

I posted a sock hops last acquisition. So I\'ll have to go back later and see if all those logos are. Otherwise, I\'m not doing my job. Um, what [00:41:00] else did we, oh, bet. Did you have a common rule? 

\n\n\n\n

Bet Hannon: Well, I was just gonna say, I think some of the acquisitions or, you know, the pandemic really caused people to just stop and think a lot more about quality of life.

\n\n\n\n

And, uh, you know, I think sometimes you stop and you take a look around and you say, I think I want to move on and do some other things, or I think I\'ve done what I can do here for now. And so some of that can be there. And so I think in 2021, you know, that that\'s a piece of more, more broadly. A lot of those acquisitions happening is just people thinking differently about what they want to do.

\n\n\n\n

David Bisset: There was a good comment made on another podcast of there was, um, if you look at the big tech, big tech companies, now that started maybe 10 years ago, um, Amazon\'s founder is no longer with the company he\'s off on rocket ships or something. Um, there\'s the, the original founders of Microsoft are long, no longer there.

\n\n\n\n

The founders of Google are no longer there. Apple\'s obviously [00:42:00] had new leadership. The only person I think running the same ship they have for awhile has been mark Zuckerberg at Facebook. So all of these people have moved on after a certain period of time and they\'ve done it all within a relatively short period of time.

\n\n\n\n

I think Twitter has been the latest one where Jack Dorsey just basically stepped completely away and he\'s off following his next adventure. Other people have just basically retired. So it\'s not just about the money in the, in the, in the acquisitions, but it sounds like to me, people, you know, you can, if you, if you\'re really successful, you have the opportunity after 5, 6, 7, 8 years to say, maybe I want to do something different.

\n\n\n\n

Maybe. All right. Um, Jeff, can you, what do you, what are your thoughts? 

\n\n\n\n

Jeff Chandler: I, in and talking about the acquisitions for a little bit, there is kind of like two separate topics for getting conflated with each other, between the five for the future and an acquisition. I dunno, I was getting little confused, but I think [00:43:00] the whole fight for the future initiative, I think is going to take on even more important as we go forward.

\n\n\n\n

As we look at open source maintainers and the bus factor of two and open source is seen as something that\'s free, but there\'s people behind it. There were people putting in time and work and effort and the passion, and it can only go so far and somebody is going to have to flip the bill. And I\'m looking forward to ma maybe putting like an executive director or somebody in charge of the five for the future initiative and get that out into the public\'s eye more often because outside of web dev studios, uh, advertising what they\'re doing and how they\'re contributing, and then some efforts from GoDaddy and 10 up, I mean, it\'s kind of like a behind the scenes thing, and I\'d like to see more effort on making the whole fight for the future thing, uh, initiative, go more public, get more people involved and get more people to know about, especially companies.

\n\n\n\n

David Bisset: Oh, okay. Sounds good. Sorry, [00:44:00] Jeff. A bucket, a bucket of chicken wings just went by my field of view and I got distracted for a second. Courtney, um, Robertson, let me add you as a speaker here. Um, after this, I want to talk about the next generation of WordPress users, which was part of the Q and a at the end there.

\n\n\n\n

Um, and what we might think might be our thoughts on bringing in, or people attracted to WordPress for the first time, especially the next generation, but Courtney, what do you got for us? 

\n\n\n\n

Courtney Robertson: Hey there. So, um, one, we saw Andrea and Middleton lurking in the crowd, and I just have to say, I am so glad to see your face popping up and we all miss you as we\'re talking about five for the future, 

\n\n\n\n

David Bisset: let\'s do a show just about her.

\n\n\n\n

I think that would drive her. I think that she would love it.

\n\n\n\n

Courtney Robertson: I think so. So did anybody else notice piggybacking off of what Jeff just said, but the very last thing that Andrea wrote to the WordPress community, aside from a fantastic series of posts on her own site, you [00:45:00] head over, if you head over to make.wordpress.org/project suggested iterations for the five for the future program and the tool, um, and ways that we can perhaps reinvision what five for the future could look like from this point, moving forward, how to.

\n\n\n\n

Do a fantastic job at connecting the five for the future initiative, with the various teams. Um, there are things in Andrea\'s post on the project about the pledges to the different teams and ways to get more connected, partnering up the talents of those that are able to contribute with five for the future, with those in the teams that need to have stuff happen to get work done.

\n\n\n\n

Um, I wanna say that I participated in a number. I want to say five probably contributor days over the past year on behalf of the training team, all of these being virtual summit attached to a word camp, [00:46:00] some as part of the translator day, which was really a month and a few other kinds of things. Yoast did a fantastic job at partnering the various folks with different sets.

\n\n\n\n

And reaching out to the various make teams and saying, w we have this day coming up, we\'re going to break into, um, a hybrid partially online, partially in person break into different groups and get to work on different things. What are some of the tasks that we can look at? I think when we look at five for the future, um, you know, my employer go, daddy has been amazing at helping fund through five for the future fund.

\n\n\n\n

Part of the word camp events that we see happen, um, sponsoring some other great places like post status and other things, too. But as we\'re, as we\'re looking to the future, I really am excited around doing contributor days through post status, inviting all folks that are in [00:47:00] post status and the wider community.

\n\n\n\n

To get connected and similar to how Yost has done it. And perhaps in conjunction with Yoast, we\'ll see in the very near future. Um, but connecting with the various team reps and connecting with the teams that have needs and saying, let\'s match up these skill sets of the talent that we\'ve got in our company and the things that need to happen.

\n\n\n\n

And also simultaneously open that thing up by calling in the wider WordPress community, because across the teams, teams are really hurting during COVID not only can we seen the attendance of things like bird camps and all of the setback, uh, you know, a number of years comparatively in the stats, but across the teams were hurting to have.

\n\n\n\n

Contributors that are showing up to actually do some of the work on the teams. And there\'s a lot of talent and a lot of interest in what\'s going on. So, um, I just, I love the posts that Andrea left us with. I love that Andrea is in the room right now. I loved the, [00:48:00] we could do a five for the future contributor day series through post status.

\n\n\n\n

So quarterly ones that will probably be hybrid. I welcome anyone that would like to help organize something like that, um, to connect with me over in post status. Oh, well, thank you very much. And, um, I\'m sure Andrea is very honored. Um, I\'ll speak for her a little bit here. Um, yeah, so obviously I\'m a little bit biased.

\n\n\n\n

David Bisset: Cause my daughter was mentioned. I don\'t think she\'ll be in the witness protection program anytime soon. Thanks to tonight. But she was absolutely absolutely thrilled, but she\'s not like, but I don\'t. I want her to be more like blending into a larger crowd of younger people that are running their own hackathons or they\'re doing their own thing within the comforts of, you know, being even mildly associated with the pro WordPress community. Even if they\'re not sitting down to crew to quote unquote directly contribute. Um, um, Amir, I think, do we have you [00:49:00] back on now? Can you say something, let us know that you\'re still alive.

\n\n\n\n

We might be having some difficulties, maybe your Mike\'s not on or something. I try and again here. Um, yep. Oh, you\'re muting yourself on and off. Are you, is it Morris code? I see a blinking. Nope. All right. I\'m going to leave you on speaker for a second and then I\'ll let Ryan cut into here, Ryan

\n\n\n\n

Ryan Marks: . Um, so I had a question for those that do pledge five for the future.

\n\n\n\n

Do you feel that you do it primarily with people man hours, or do you do it with dollars or is it a mix? Do you feel like you actually get the 5%, if anything, or is it more, we try to get something close. I think that has her hand, right? So we do fight for the future. Um, I don\'t know that we calculate it, but you know, certainly, um, you know, [00:50:00] I contribute my time.

\n\n\n\n

Bet Hannon: Um, and then our, our agency subsidizes our people as they, you know, they can, they can put in, uh, you know, time that they\'re doing community work and get, um, get paid for that. Um, as a way that we try to support the wider community, I think that\'s just a part of, you know, my wife is an economist, so I understand that tragedy, the commons, uh, example really well.

\n\n\n\n

And I want to make sure that the ecosystem stays supported. And so that\'s, that\'s a really, you don\'t have to be really big to do those things right. To, um, to, to make a difference. Uh, but I just feel like that\'s an important part of what we do is for the community. 

\n\n\n\n

David Bisset: All right. So as we start to run down here, cause.

\n\n\n\n

Did promise, uh, it promise someone I would be home in time for bed. I do. I want lot of stall all us to think about a maybe if, if there\'s any final comments you had about what Matt talked about or Matt\'s comments about uni questions or about how that [00:51:00] fits in with your version of WordPress in the future.

\n\n\n\n

While you\'re thinking about that, let me quickly get, um, Olivia on. I think she wanted to make a quick comment.

\n\n\n\n

You\'re muted. Olivia,

\n\n\n\n

maybe we have a maximum number here. Maybe it\'s why this isn\'t working. Let me remove a speaker. 

\n\n\n\n

Olivia Bisset: I can speak

\n\n\n\n

David Bisset: Sorry, go ahead. What\'s your comment listener. 

\n\n\n\n

Olivia Bisset: Okay. So with five for the future, I don\'t know what, but it just got the general vibe that that\'s starting to head towards, like, okay.

\n\n\n\n

Yeah, we got people now, but like youth, I feel like there was more of a youth focus. This state is a word, especially with the question from Allie and others. I don\'t know. That\'s my 2 cents. 

\n\n\n\n

David Bisset: I thought Allie gave an excellent question and [00:52:00] that was followed up by others as well. Um, and we\'ll have to go back and review that because my memory is beginning to fade a little bit, but I thought she had a very excellent question about what Matt thought the youth, um, what his advice to you would be regarding how to use WordPress for the next generation.

\n\n\n\n

So, um, let\'s um, let\'s take one more comment from the audience here and then we\'ll see if we go around. Anybody has any final thoughts, Aaron Edwards, um, welcome to whatever we\'re calling this. What, what do you have to share? 

\n\n\n\n

Aaron Edwards: Uh, hi, I\'m the co-founder of web three WP. So of course we are very interested in what Matt had to say about web three.

\n\n\n\n

I thought it was a good kind of balance, like opinion, like, like Jeff Rose said, um, just the fact comparing WordPress to kind of some of the ideals, uh, web three, I think that was kind of a good tact that he took, but it was interesting just discussing in our community. It\'s like, it does follow like those ideals of data [00:53:00] ownership when you\'re the site owner, but it doesn\'t really address the site users, which is something that web three is kind of known for you.

\n\n\n\n

It basically allows you, WordPress allows you to create your own data silo, you know, to maybe compete with the Facebooks or whatever centralized apps there are, but it doesn\'t necessarily empower users to continue to have your site on their own data. So that\'s kind of a interesting take that I heard in our community.

\n\n\n\n

David Bisset: Interesting take at that sounded like I haven\'t heard that take exactly like that before. Uh, well, I kind of wrote that same thing on our website, but, oh, would you mind sending a link to that in post at a slack or wherever your finest links are sold?

\n\n\n\n

Aaron Edwards: Yeah. The web three wp.com pages talking about WordPress being, um, kind of along those ideals, but definitely it was, it was interesting to, to hear his take in that, uh, another thing he kind of made a joke about dowels and [00:54:00] domains, um, which kind of seemed like disingenuous to me personally, because I\'ve had experiences where I\'ve had domain registrars, uh, shut down my domain because someone filed a false abuse report, you know?

\n\n\n\n

So it\'s like that\'s renting. That\'s not really owning. As he kind of made it out to be okay.

\n\n\n\n

David Bisset: I can see that point. Absolutely. And hopefully I won\'t have anything shut down on my side Verde, but thanks. Thanks for sharing and feel free to ping me in post status or on Twitter. I\'d like to get that link from you.

\n\n\n\n

All right. So, um, it\'s been about an hour. Um, so I wanted to, um, I did make, uh, wanted to see if anybody else has any last comments. Um, either somebody who hasn\'t spoken yet are part of our, um, ongoing panels here, um, that I know you wanted to share. Something felt like a last lot quickly with us, and then I\'ll nail a few other people that didn\'t sound right in my head.

\n\n\n\n

But go ahead and you under, do you [00:55:00] please take it, please take the mic from me. 

\n\n\n\n

Bet Hannon: Yes. Um, so I\'m a little disappointed that Matt didn\'t say more about accessibility. And the times when he talked about accessibility, he really meant it in the terms of just making things available to people, uh, like features available.

\n\n\n\n

Um, but you know, we didn\'t talk about web accessibility and we we\'ve had some issues with that. Um, in the past, things are better than they were, but we still have a long way to go for web accessibility, especially in the WP admin side, in the dash, in the backend side. So Amber Heinz tried to call out Matt earlier in the week, uh, just to try and get him to speak a little bit more about accessibility, but he didn\'t so well, his slides were probably already written by then too.

\n\n\n\n

David Bisset: I don\'t, I\'m not going to speak for them 

\n\n\n\n

They said they were editing them 

\n\n\n\n

Bet Hannon: up to the last minute. 

\n\n\n\n

David Bisset: I know what that\'s probably true too. I can\'t speak to that, but no, he did mention it, but I\'m getting a feeling that for some people who wanted him to mention accessibility of may not have filled their cup to. [00:56:00] It\'s an important piece and growing in importance.

\n\n\n\n

Bet Hannon: And so we have to pay attention to it if we want to keep that market term. Yes. Because like he said, we\'re pressed should be like, for most of the people, WordPress will be invisible. Right. If the, if the user experience is done. Right. And would you bet, um, I know you\'ve said many times that part of the user experience is what, well, it\'s gotta be accessible.

\n\n\n\n

Right. And it\'s gotta be, um, and as we\'re increasingly in the us having some, um, legal pieces where people are going to be required to have their sites accessible, we we\'re gonna need to be ready for that. Um, so we can help people do that. 

\n\n\n\n

David Bisset: All right. Um, speaking of Amber, I think we said her name three times.

\n\n\n\n

She\'s appeared. Um, we\'ll get right before we get to Ryan. Um, Amber, did you want to share something with us? I\'m guessing you want to share something that starts with the letter a and it\'s not your first name.

\n\n\n\n

Amber: Uh, not Amber, uh, accessibility. Yeah, I think, I think the thing that\'s interesting too, I [00:57:00] actually got a couple of messages from, um, some users after they read, you know, the thread and conversations and in process.

\n\n\n\n

And I think maybe the contribution to core accessibility, the people on the accessibility team, particularly maybe some people that have disabilities that are part of the accessibility team. Probably I think there are some of them that feel like it\'s still not as positive or as central of a focus as it as maybe Matt kind of thinks that it is.

\n\n\n\n

Um, I think it still is a lot of an afterthought and really that\'s, you know, one of my hopes that I\'m really would love to see more. Thinking about accessibility as something you do at the beginning, not something that you do wait around at the end of the process, whether it\'s in core or whether it is, you know, in plugins or themes or on the front end of the end websites, [00:58:00] let\'s start at the beginning, not in the middle of the end.

\n\n\n\n

David Bisset: It\'s like how I should do most things in my life, especially the chores around the house. Thank you, Emery. We did see a lot of this stuff in accessibility mentioned in post status too. So we\'ve been following that as well. And thanks for speaking up here today. Really appreciate it. Okay. Let\'s let\'s go through the rest here.

\n\n\n\n

We\'re going to be ending shortly, but Ryan, you are up next. Um, what closing remarks do you have for us?

\n\n\n\n

Ryan Marks: So three things caught my attention. Uh, and then I\'ll hang up and let you guys talk about, we\'ll just pretend you\'re not here. I can remove you as a speaker.

\n\n\n\n

David Bisset: You don\'t have to hang up, but we can ignore you easily, but go ahead.

\n\n\n\n

Ryan Marks: Um, I thought that there was an open invitation for up to 50 people. So I tend to stand in the word, but then later it seemed like there were about 30 people there, there were all five for the future. And I thought that was just, that was an interesting change. Maybe a two, I thought the idea of a query block was something new and I liked it.

\n\n\n\n

[00:59:00] And there was a lot of focus on multi-lingual at the beginning and towards the end. And I\'m really interested to see how that will pan out. Me too. I don\'t think Matt was in it. It seemed like Matt wasn\'t in a position to quote a lot about phase four and rightly so, because not even phase three is happening next year officially, but I think we\'re, can\'t be aware of me maybe a little strange, a little bit more out of them, but I\'m looking forward to the language aspect as well.

\n\n\n\n

David Bisset: In fact, I\'m kind of surprised I was at the phase four at the four phases when he first announced it a couple of years ago. Um, Um, let\'s see who, uh, who else we got here? I think we have, um, let\'s see. I think we, Eric, I think it\'s down to you now. Um, you might, you might be closing here. I know no big pressure.

\n\n\n\n

Eric Karkovack: For baseball fans during this lockout, I\'ll try to be the closer here. Get on the mound and pitches to a victory here, 

\n\n\n\n

David Bisset: not a sports person, but tackle, go and tackle and hit a fuel. Go right through the goalposts for me, please. 

\n\n\n\n

Eric Karkovack: Okay. I\'ll shoot it into the [01:00:00] net for you. All right. So my bedroom aside, I think one thing I\'m interested to watch is the, um, the growth of block themes.

\n\n\n\n

Matt talked about, you know, hoping to have 3000 available, uh, at the next state of the word. That\'s going to be interesting because. I haven\'t seen like the commercial theme market takeoff for that yet. Um, there\'s a few opportunities there. I\'m seeing some, you know, some new ones come out. So it\'ll be very interesting to see in 2022, how much, uh, adoption rate there is for block themes and full site editing and what number of themes we actually get to buy the next state of the word.

\n\n\n\n

David Bisset: What do you think? What\'s your guess? 

\n\n\n\n

Eric Karkovack: I\'m going to say somewhere around a thousand, that\'ll just be my completely uneducated guests. I think there\'s so many theme authors that are still kind of hanging to the classic theme, uh, you know, style and way of [01:01:00] building. Um, and it\'s probably going to be a little bit slower adoption than maybe Matt hopes, but, uh, you know, I may be very wrong on that.

\n\n\n\n

David Bisset: Do you think it has to do with just being, not familiar and trying to stick with what works as long as possible? 

\n\n\n\n

Eric Karkovack: I think so. I think it\'s. If you watch how this is unfolding, it changes like almost weekly. And if I\'m a theme developer, I\'m probably going to hold off until I have a pretty good idea of what\'s going to be required and how these themes are going to work over the long-term before I invest a bunch of time in it.

\n\n\n\n

So I think we\'re going to get there, but it may just take a little bit of time for people to get used to the idea and for standards to form.

\n\n\n\n

David Bisset: Hmm. That sounds reasonable. That\'s okay. I don\'t know. Or it could be something I just drank. That\'s making me agreeable to everything I\'d already said right now. It\'s possible. Well, anyway, I [01:02:00] really want to thank everybody who I think by the way, that was excellently, put Eric in terms of I could have been, that was just probably. 3000 sounds like an ambitious number. Who knows if we\'ll get there, but, uh, I think I\'ll put you down for a thousand and then this time, next year we\'ll come around and we\'ll see if we can collect on that bet and see if you were high or low.

\n\n\n\n

So appreciate it. Oh, wait. What\'s uh, let\'s get Jeff here is the real closer about you or the fake closer Eric. Let\'s let\'s not to put any pressure on you there, but Jeff, can you, can you close this out for us here? Oh, wait, whoa, sorry, Jeff. I think I just,

\n\n\n\n

okay. Jeff. Now you can go,

\n\n\n\n

Jeff Chandler: uh, yeah, three words, block theme generator,

\n\n\n\n

David Bisset: block theme generator. Oh, isn\'t somebody working on that or is that somebody is already working on it. 

\n\n\n\n

Jeff Chandler: There\'s going to be more of [01:03:00] those created throughout next year. And 3000 I think is easily doable and there\'s going to be a bunch of them.

\n\n\n\n

Bunch of themes created from these generators. That\'s my take.

\n\n\n\n

David Bisset: So we\'re thinking, we\'re thinking the themes did themes really take off after the underscore S generator or a discourse came about? Is that, is that where you\'re considering more or less the equal the, was it underscore? 

\n\n\n\n

Jeff Chandler: Uh, I don\'t underscore is just like a starter theme, but you know, what, what I\'m seeing from the theme.json theme by theme generators nowadays seems to be just makes the theme generation process so much easier.

\n\n\n\n

I mean, if you\'re, if you\'re a theme developer and you\'re not excited about what\'s coming down the pike in 2022, what is wrong with you? 

\n\n\n\n

David Bisset: Well, wow. I mean, people ask what\'s wrong with me and I, they don\'t literally have the, I don\'t have the time to tell them all day. Um, okay, well, good. Yeah. So generator, we\'ll put that down as something for 2022.

\n\n\n\n

Jason, did you have something to share before [01:04:00] we close out here or did I accidentally pushed the wrong. 

\n\n\n\n

Jason: No, you didn\'t accidentally push the wrong button. Hi everyone. 

\n\n\n\n

David Bisset: Hi Jason.

\n\n\n\n

Jason: Hello. Well, there was a lot to, uh, digest and, um, the state of the word think it was interesting. Um, one of the things that we started noticing, uh, during our, our live broadcast of, of it was the fact that it\'s really interesting to, to have Matt interact with a smaller group of people versus such a larger room of people.

\n\n\n\n

And we were also very disappointed that there was no boot. 

\n\n\n\n

David Bisset: Well, I mean, where did it fit in the room? And that would, would\'ve been a lot of polishing dude to remove any, I don\'t know. I feel like I would have to be like the Adrian monk on that show where he just, you just basically have to hand wipe the entire thing.

\n\n\n\n

It doesn\'t seem so clean. Now after the last two years to be coming out of a boot, I mean, it was questionable to begin with. [01:05:00] Yeah, indeed. But yes, but yes, I, I think all of us are walking away here that this had a different, definitely that a different vibe. And I don\'t think it was just because we have, it\'s been two years since we\'ve seen Matt in front of a live studio audience.

\n\n\n\n

I think it was the size of the event. I think the mood was a lot lighter. Um, and there was a lot, not just because of the less people in the room. I think Matt\'s attitude and his casualness were a little bit more open, a little bit more different directed, but it was still very good. So I, I agree with Jason that I think it had a lot to do with the environment on that.

\n\n\n\n

And we got to see me be a little bit more open Frank. Um, I dare say even some of it was even not that even rehearsed, not saying less rehearse, but I think maybe he, this is a couple of times tonight. He did pause for a while before answering a question, usually math pretty quick, usually mats pretty quick with questions.

\n\n\n\n

And he\'s always been a talented speaker in that regard. Something I\'ll never learn even after doing so many of these things with you people, but, but yeah, it really did see him [01:06:00] when seeing him pause and consider the questions, especially I think from Allie\'s question to really. It did mean a lot more.

\n\n\n\n

And I kind of enjoyed what tonight brought even though I think next time in, by if this happens at the end of 2022 and it\'s in front of a larger audience, I don\'t think I\'d mind that either, but yes. Thanks. Thank you very much for having me. I appreciate it. No problem. No problem at all. Okay. I think that just about, does it this time?

\n\n\n\n

I promise. I want to thank everyone for joining us this evening, especially on the east coast and in where the time zones are and where the time zones, where you\'re very late. Mr. Owl. Um, I just want to say thank you very much for your, um, it\'s. What is it like one in the morning over there? I, I can\'t imagine what.

\n\n\n\n

Putting into your body right now to just doing the morning two in the morning. Oh my goodness. Oh, well, we admire your dedication, sir. Thank you for coming here and we hope to have you back soon. Uh, really, really appreciate it, Ray. Uh, on the other hand, you are bright and [01:07:00] cheery with your coffee in the morning.

\n\n\n\n

So, uh, damn you my dear, but I want to thank you for coming as well.

\n\n\n\n

She\'s not speaking to

\n\n\n\n

Bet Hannon: thanks so much for inviting me to be part of this chat David. 

\n\n\n\n

David Bisset: No problem. We want you back more for some of you, the more insights that you have, um, examining the entire WordPress through the repository or that\'s something that\'s in my inbox and I read it first. Every, every chance I get I\'m going to drop in.

\n\n\n\n

I think it\'s Friday my time. I don\'t know. Time\'s a flat circle for me, but thanks for coming. Bet. Thank you for coming as well. Greatly. Appreciate you taking some viewpoints from an agency standpoint and accessibility. Thanks for coming.

\n\n\n\n

Hazel Quimpo: Great. Thanks for having me. 

\n\n\n\n

David Bisset: Eric. Thanks for okay, now we\'re even now you don\'t owe me anything.

\n\n\n\n

Thanks for coming.

\n\n\n\n

Eric Karkovack: Hey, my pleasure. 

\n\n\n\n

David Bisset: And I want to thank, um, LemonadeCode, who is the cohost right now. Um, she has been my producer, my, my wing person. I want to thank her as well for her help this evening as well, making sure the equipment has been organized, pointing out when people were raising [01:08:00] their hands and criticizing me when I\'ve made very, very poor means on the web tonight.

\n\n\n\n

So I want to thank you as well, Olivia. Thank you very much. Um, we\'re going to, this will be recorded and posted on post status in, in a day or two. So you can feel free to check out post status.com or our podcast links for that. And if you have any questions about anything we\'ve shared here, you want a copy of the recording, whatever.

\n\n\n\n

I\'ll feel free to share it with you. I don\'t want to thank everybody again and have a good evening. Goodbye.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Dec 2021 14:00:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"Post Status: Post Status Team Responses to the State of the Word 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=91362\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://poststatus.com/post-status-team-responses-to-the-state-of-the-word-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14390:\"

Our Thoughts After SOTW

\n\n\n\n
\"Michelle
\n\n\n\n

Michelle Frechette: I was shocked and thrilled to receive an invitation to State of the Word in New York, and even happier when my travel was approved at StellarWP.  Arriving at the venue (Tumblr’s old digs) we were required to prove our vaccination status to go up to the loft. I got off the elevator and was immediately greeted by Josepha and then Matt. It was SO GOOD to see so many friends and well-known WordPress faces!

I took a reserved place in the front row and sat captivated by the environment, the information, and the nervous energy in the room. We were returning to some level of normalcy by being in that space together, and it felt both familiar and foreign after the last two years…but it was good.

When the address was done, and all the questions had been answered, and the broadcast had ended, there was an elegant reception with food and beverages. I met new people and enjoyed the conversation.

Not to be one to miss an opportunity, I asked Matt for an interview for Post Status, and recorded a 7+ minute conversation with him on the recent surge of acquisitions and the future of work in WordPress, that we will share later. He was truly gracious with his time, and I appreciated that very much.

On leaving, I gathered my jacket and was handed a swag bag.

All in all, I felt a bit like Cinderella, with a Lyft for a pumpkin carriage, purple hair as my tiara, and scads of friends helping me navigate the time with my electric scooter.

I enjoyed every minute.

Bonus: Michelle caught Matt for a brief interview after the SOTW address!

\n\n\n\n
\"Anna
\n\n\n\n

Anna Maria Radu: I was happy to learn about Openverse as a visual storytelling fan myself. The fact that Creative Commons has become part of WordPress is probably one of the best things that could happen for creators. Their work can now be even more easily incorporated and credited within anyone\'s storytelling. By doing this we, as a community, are supporting artists to gain recognition and appreciation through WordPress. Open Content for the win!

But probably the topic that stood out to me the most was the Diverse Speaker Program. I have worn many hats behind the scenes of pre-pandemic WordCamp events and WordPress-themed events in general. I loved seeing so much diversity — yet, there’s no such thing as too much diversity. I immediately joined the #diverse-speaker-support channel on WordPress Slack to learn more about it.

\n\n\n\n
\"AJ
\n\n\n\n

AJ Morris: I\'m excited for the future of block patterns and global styles! Having the native ability to use core block editor options for themes is going to drastically change the way we look at WordPress themes over the next 5 years.

\n\n\n\n
\"Courtney
\n\n\n\n

Courtney Robertson: Matt\'s vision of what contribution could look like was really exciting. As a Make WP Training Team co-rep, I eagerly welcome more contribution efforts across the WordPress project by connecting with teams. See Five Ways to Participate in Five for the Future for examples of how you can get involved as a contributor.

Also, Michelle Frechette\'s and Allie Nimmons‘ questions for Matt after his presentation — about introducing WordPress to youth and young adults — really reminded me of why I teach WordPress. I\'ve instructed high school students as WP developers, and there are logistical challenges. I\'d love to partner more closely with more educational organizations to help resolve these challenges. We can improve content across WordPress.org as we become compatible with COPPA requirements.  Sandy Edwards, Youth Working Group Team Co-Lead, is also eager to resume KidsCamps as we return to in-person WordCamp events. 

\n\n\n\n
\"Kayla
\n\n\n\n

Kayla Demopoulos: This year\'s SOTW was a great reminder that all the pieces of the puzzle work together to create the whole. It is great to remember where the project has come from, but more importantly, inspiring to think where together we can take it.

\n\n\n\n
\"Dan
\n\n\n\n

Dan Knauss: What a difference a physical venue makes! At the old Tumblr offices in Noho, this year\'s State of the Word looked like an opening at a small art gallery. No big screen, just a lot of framed visual art. No stage, just a simple podium. And after such a long period of time without in-person events, there was Matt waiting to go up front, casually leaning off to the side of the audience (maybe two dozen people) a few feet away. There were some awkward (but good!) moments, plenty of laughs, and a personable atmosphere that came through — even on YouTube. A lot of important facts and numbers were shared that we\'ll dig into later, I\'m sure. That\'s what we usually focus our attention on. But my initial impressions had to do with mood, atmosphere, and tone — the emotional register of the themes that went through Matt\'s address and into his dialogue with the audience afterward.

We learned Matt wishes he had done things differently with the WordPress 5.0 release, and I thought of Courtney pointing out to me last month how the decision to delay 5.9 was a quiet sign of significant growth. We learned how Matt relates to the story of Ernest Shackleton turning back from an attempt to reach the South Pole only 97 miles from it — and why Matt wears a suit for SOTW. These were small things that came up in the question period, but they touch important themes for the WordPress community — growth and maturity — and maybe what they should look like. (More than a touch of humility and grace?)

Those who were in attendance are well-known for their contributions to the WordPress community, including many whose companies\' participate in Five for the Future. The constant and increasing importance of giving back, of getting young people involved, and taking ownership of the largest open source community effort of its kind — together — these are the mature, future-facing themes that stood out to me.

I was talking with Matt Medeiros a few hours before SOTW, and he remarked how WordPress is paradoxically gigantic and small at the same time. It\'s a huge project with a giant ecosystem relative to the community of active contributors and what we might call the core culture of WordPress — including the people who make, distribute, and consume the news, information, and ideas that help direct the project. There\'s fragility and power, weakness and opportunity in being small in a big distributed network.

We\'re coming through (and possibly getting deeper into) pivotal and challenging times — not just for WordPress but the larger world of web tech and the global human community. Matt didn\'t mince words when he named the threats from big tech companies that aren\'t friends of The Open Web. If we\'re not just spinning our wheels, the future we want is what we\'re building toward today, together. These are some of the big themes we\'re focused on at Post Status too, as we move into a new year.

\n\n\n\n
\"David
\n\n\n\n

David Bisset: After watching Matt give this annual talk for years I could tell early on that something was different (in a good way) — but I couldn’t my finger on the cause. Matt seemed to be the most excited person in the room, along with whatever nervousness he had. He seemed more excited than in any State of the Word I can recall. Matt laughed more, and I think he went “off script” more too, telling stories and jokes. “I haven’t spoken to a crowd in two years,” he said at one point. Maybe that was it. I caught him a few times in a “nervous happy” state before the conference started. With no WordCamp US to provide a big crowd, this might have been the most open we’ve seen Matt, and I think he reflected the energy coming from the crowd.

I\'m glad the “next generation of WordPress users” was brought up by Allie Nimmons and later Michelle. This topic was raised in the last in-person SOTW in 2019 as well. WordPress market share growth will eventually stop, and we’ll need to create and sustain new generations of developers, designers, and contributors from within the community. It’s really going to be up to the WordPress community and WordPress companies to mentor, intern, and train our future leaders and core contributors.

About “Be Like David” — it\'s the worse advice ever. (Editor\'s note: we respectfully disagree.)

\n\n\n\n
\"Cory
\n\n\n\n

Cory Miller: Gutenberg and contributing to core continue to be key themes from Matt for the project.

Regarding Gutenberg — I greatly appreciate the work being done to make the Block Editor easier to use. It reminds me of the creative innovations that have happened since I started doing themes in 2006. I hope that continues to accelerate like it did with themes.

About Five for the Future and contributing to core — When I was leading iThemes and as a small team, I always struggled with how to meaningfully contribute to Core on a consistent basis. Courtney and I are working on Post Status Contributor Days for 2022 to help bridge that gap. She’s been pinging Team Leads to ask for their wish lists. Then we plan to put some dates out and tackle them together as a community. Stay tuned.

\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n
\"Post
\n

You — and your whole team can Join Post Status too!

\n\n\n\n

Build your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. \"✉\" Listen to podcasts. \"🎙\" Follow @Post_Status. \"🐦\"

\n
\n\n\n\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Dec 2021 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:10:\"Dan Knauss\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"WordPress.org blog: Highlights from State of the Word 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11869\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wordpress.org/news/2021/12/highlights-from-state-of-the-word-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3128:\"
\n\n
\n\n\n\n

State of the Word 2021, the annual keynote from WordPress co-founder Matt Mullenweg, happened on December 14. The hybrid event took place in New York City with a small audience (proof of vaccination required). As Matt said, “we had people join by plane, train, and automobile.” Those who didn’t make the trek to the live event watched the livestream from wherever they call home, all around the world. 

\n\n\n\n

It was an exciting moment for the WordPress community which also celebrated its first in-person WordCamp in Sevilla, Spain, after a lengthy hiatus for in-person events.

\n\n\n\n

You can view the full recording, complete with captions and transcripts on WordPress.tv.

\n\n\n\n

It was thrilling to see so many meetup organizers host watch parties worldwide. Twenty-six watch parties were held across eleven countries, with more than 300 RSVPs.  

\n\n\n\n

Similar to past State of the Word events, Matt covered a broad range of topics. This year was no different. WordPress’ past, present, and future were in the spotlight, with highlights on the growth of the contributors, language translations, recent release milestones, and educational initiatives, to name a few.

\n\n\n\n

Audience members and livestreamers alike viewed product demos showcasing upcoming features that will be the hallmark of WordPress 5.9, such as full site editing, block patterns, global styling options, and enhanced image controls.

\n\n\n\n

Matt took the opportunity to remind everyone of the WordPress roadmap which includes native multi-lingual support and real-time collaborative site editing. He also pointed out that anyone can contribute to WordPress’ progress through a number of different initiatives ranging from creating new features and testing to helping spread the word and educate others.

\n\n\n\n

Matt emphasized the way that open source software gets better by reminding everyone that “The more people that use a program like WordPress, the better it gets.”

\n\n\n\n

Broader topics covering the tech landscape including web3, merger and acquisition activity, as well as the growth and support of open source software, rounded out the energetic presentation. 

\n\n\n\n

The one-hour multimedia presentation was followed by an interactive question and answer session where Matt fielded questions that were submitted ahead of the event, as well as questions from the livestream and studio audience.

\n\n\n\n

Discover everything that was covered by watching the official event recording and join the ongoing #ILoveWP conversation on Twitter!

\n\n\n\n

Special thanks to @dansoschin for review and edits!

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Dec 2021 01:04:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Anjana Vasan\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"WPTavern: David Gwyer Teases Block Theme Generator App, Plans for a Community of Creators\";s:7:\"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=127160\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:221:\"https://wptavern.com/david-gwyer-teases-block-theme-generator-app-plans-for-a-community-of-creators?utm_source=rss&utm_medium=rss&utm_campaign=david-gwyer-teases-block-theme-generator-app-plans-for-a-community-of-creators\";s: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:5020:\"\n\n\n\n

David Gwyer has been teasing ThemeGen over the last couple of weeks. It is his upcoming block theme generator app. Piece by piece, it has seemed to be coming together and could prove invaluable for theme developers. Currently, it is in beta testing.

\n\n\n\n

He provided me with a link to an early preview to get my feedback on the tool. This is also available to anyone who signs up for access via the ThemeGen website.

\n\n\n\n

Currently, the app only generates theme.json files. The feature was first launched in WordPress 5.8 for classic and block themes. It can have a bit of a learning curve for theme authors diving in for the first time. Plus, it is easy to make mistakes when hand-coding JSON files.

\n\n\n\n

The dream goes beyond theme.json. That is the obvious starting point for such a project because it helps with current and future theme development. However, Gwyer wants to take this to another level as the project evolves.

\n\n\n\n

“It’s not 100% functional yet, but I’m adding features daily,” he said. “I’m hoping that designers and non-coders will soon be able to create block themes visually, independently of WordPress. And be able to manage all their themes in a centralized location via the app. This opens up possibilities of a community of theme creators sharing and contributing to a resource of templates, styles, designs, etc.”

\n\n\n\n

These goals align directly with my hopes for WordPress and its block system. I want to see creators actively involved in a give-and-take design community. The ideal place for this to happen is WordPress.org, but third parties can often develop these things faster without any potential hurdles from the platform’s official site. They can also push the WordPress project in a specific direction if successful on their own.

\n\n\n\n

Using the App

\n\n\n\nSettings fields and generated theme.json.\n\n\n\n

For generating a theme.json file, the app works well. Currently, it allows creators to configure settings, templates, and template parts. The missing piece is building out styles, which is coming soon.

\n\n\n\n

There is also an “Other” section. It has a single setting for supporting the Theme JSON Schema. This is handy for developers who like built-in validation, tooltips, and autocomplete if their code editors support it.

\n\n\n\n

The most fleshed-out area of the app is for generating global settings. It covers border, color, layout, spacing, and typography options. As far as I can tell, it has most of the available flags that a theme author can set. It is hard to remember them all offhand, one of the reasons tools like this are helpful.

\n\n\n\n

I did notice that a way to input font families was missing. He could do a lot with that in the future, especially if a web fonts API is ever bundled in core WordPress.

\n\n\n\n

The “Custom” settings section is still unfinished. This will likely take some time to implement because theme authors can add any type of data with multiple levels of nesting. Unsurprisingly, it is not ready yet, but I am eager to see how Gwyer tackles the UI for it.

\n\n\n\n

Creators can import colors from the Twenty Twenty-Two, Blockbase, or Tove themes. Implementing such a feature this early tells me that Gwyer is likely already thinking ahead to that future of shared resources. How neat would it be to pull in any piece of an existing block theme into another at the click of a button?

\n\n\n\n

Colors, gradients, and duotone filters are missing one configuration option I would like to see. Right now, creators can add a name. However, they cannot manually add a slug, which is automatically generated.

\n\n\n\nCreating custom colors.\n\n\n\n

There are scenarios where some designers might use developer-friendly slugs like primary-100, primary-300, and primary-500. Then, they would use names that make more sense to end-users, such as “Primary Lightest,” “Primary Light,” and “Primary Medium,” respectively.

\n\n\n\n

The auto-generated slugs feature is nice. However, it should allow for manual input too.

\n\n\n\n

ThemeGen will likely be a welcome resource for theme authors as they navigate the block theme world in the coming months. Given enough interest, it could also become that community of like-minded creators who are open to sharing with one another. The first step is to get more testers and feedback during this beta period.

\";s: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, 15 Dec 2021 21:56:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:34;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"WPTavern: State of the Word 2021: WordPress Passes 43% Market Share, Looks to Expand the Commons Through Openverse\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127047\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:267:\"https://wptavern.com/state-of-the-word-2021-wordpress-passes-43-market-share-looks-to-expand-the-commons-through-openverse?utm_source=rss&utm_medium=rss&utm_campaign=state-of-the-word-2021-wordpress-passes-43-market-share-looks-to-expand-the-commons-through-openverse\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:13992:\"

Matt Mullenweg delivered his annual State of the Word address yesterday before a live studio audience in New York City. The majority of WordPress enthusiasts joined the event through the livestream on YouTube. More than 25 meetups gathered for in-person and online watch parties around the world – from Detroit, Singapore, Pakistan, and Medellín, to name a few.

\n\n\n\n

Mullenweg began by reviewing WordPress’ growth over the past year, beginning with the Polyglots’ continued efforts to make WordPress available to the non-English-speaking world. In 2021, translators have significantly increased access to WordPress through language packs and active translations:

\n\n\n\n
  • 13,659 language packs in core (+76%)
  • 15,900 active translations (+28%)
\n\n\n\n

WordPress also expanded its Diverse Speaker Training program, gaining 135 participants in 66 cities across 16 countries.

\n\n\n\n

The Learn.Wordpress.org site is now available in 21 languages, and Mullenweg said it is going to be a more prominent part of what visitors see when they visit the WordPress website. The platform has had 186 learning spaces, which he said is essentially cohorts of people going through the different courses. Learn.WordPress.org’s catalogue has grown to 73 workshops and 70 different lesson plans. There are now two courses available, which include collections of lesson plans.

\n\n\n\n

“I think this is actually one of our biggest opportunities to expand the knowledge of what WordPress is, and also define it to a new audience through these courses,” Mullenweg said.

\n\n\n\n
\n\n\n\n

One of the most notable stats from the presentation is WordPress’ distribution, which is now at 43.1% usage on the web, according to W3Techs, up from 39.1% last year.

\n\n\n\n

One concern is that open source CMS’s are slowly disappearing from the top five competitors, as proprietary systems pass up Drupal and Joomla. Mullenweg said in general the CMS’s aren’t taking market share from each other but rather from the websites which previously had no detectable CMS.

\n\n\n\n
\n\n\n\n

“We actually grew two entire Wixes this year, which is a new unit of measurement,” Mullenweg joked.

\n\n\n\n

“And to put that in perspective, we’re still 10 times larger than number two out there, but this doesn’t happen for free. And we shouldn’t take any of this for granted. There are in the history of software, and certainly the internet, many services that were once dominant that now we need museums to remember what they were there to maintain.

\n\n\n\n

“We really need to stay humble and stay close to users and iterate the software as quickly as possible.”

\n\n\n\n

Mullenweg hinted that 2022 might be a year that WordPress aims for four releases instead of three.

\n\n\n\n

“I’m proud to say it was a good year for WordPress security,” he said. More than 30 people contributed to security patches, and 1/3 of those were first-time contributors.

\n\n\n\n
\n\n\n\n

“Security is a process,” Mullenweg said. “Anyone who says they are perfectly secure is tempting fate.

\n\n\n\n

“Our ability to be one of the most secure platforms in the world is one hundred percent a result of how much we’re going to be able to update sites because humans are fallible sometimes.”

\n\n\n\n

State of the Word Features WordPress 5.9 Demos

\n\n\n\n
\n\n\n\n

Mullenweg highlighted a few new features coming in 5.9, with demos of block themes, template editing in the block editor, global styles, and pattern improvements. He reiterated that Gutenberg is the future of WordPress for the next decade:

\n\n\n\n

As we look towards the future of WordPress, we are finally achieving one of the things that WordPress set out to do 18 years ago.

This is why we started the Gutenberg project. When we first introduced Gutenberg a few years ago, we said this was going to be the foundation, what the new versions of WordPress were built on, what our next 10 years would be.

Not only are we enabling folks to express themselves uniquely on the web, unlike the cookie cutter that all the social sites try to put you into, the cookie cutter looks. We’re doing it in a way, which is standards based, interoperable, based on open source, and increases the amount of freedom on the web, which is very key, certainly to me, and the most important thing that I work on.

\n\n\n\n

WordPress has just begun on its journey with Gutenberg. Mullenweg reviewed the four planned phases, which began with “Easier Editing” in 2018. The second phase, Customization, started in 2019 and Mullenweg said 5.9 will be the MVP of this phase.

\n\n\n\n

With 5.9 delayed until 2022, he has the third phase, Collaboration, slated for 2023, so that contributors don’t leave customization too early before it’s polished. There are only 28 block themes available so far. “That needs to be 5,000,” Mullenweg said. Later during the presentation he said he hopes that WordPress will “have 300 or ideally 3,000 of these block themes” before entering the Collaboration phase.

\n\n\n\n

There is no timeline yet for the fourth Multilingual phase, which aims to make it easy to publish sites in multiple languages with a workflow that makes sense.

\n\n\n\n

Web3 and the Decentralized Web

\n\n\n\n

Many State of the Word viewers were eagerly anticipating Mullenweg’s thoughts on Web3 and NFT’s, after the controversial topic was included in the State of the Word announcement last month. They speculated on how WordPress might incentivize contribution through tokens or NFT’s. For now, it appears WordPress will keep attracting contributors the old-fashioned way.

\n\n\n\n

Mullenweg’s message was essentially that WordPress already embodies Web3 ideals and has from the beginning.

\n\n\n\n

“What Web3 embodies is two essential ideas — decentralization and individual ownership,” he said. “Those are both things that WordPress is both well-poised to be already doing and to continue doing for some time to come.”

\n\n\n\n
\n\n\n\n

He also cautioned those exploring Web3 projects to keep the freedoms of open source in mind:

\n\n\n\n

There’s been an incredible amount of innovation. I think this has also attracted some hucksters and some folks kind of hustling things that aren’t truly open. So you all are very familiar with WordPress. For every project, which is asking for your money dollars, or for you to pay the cost of a house for a picture of an ape, you should ask, does it apply the same freedoms which WordPress itself does, and how closely does it apply to increasing your individual agency and freedom in the world?

\n\n\n\n

Mullenweg also spoke about the many acquisitions in the WordPress space and put them in the context of what’s happening in the world of business. WordPress appears to be a microcosm of global acquisition activity.

\n\n\n\n
\n\n\n\n

“And if you were to broaden it to the global M&A landscape, not just technology, we’ve seen over 45,000 different acquisitions,” Mullenweg said. This is up over 24% from last year, which is already a huge year and represents $3.6 trillion of different mergers and acquisitions.

\n\n\n\n

“This is driven by another trend, which I found utterly shocking to learn and understand, which is capital inflows to stocks,” Mullenweg said. He shared a chart that shows how much money is moving from other assets into the public equity markets.

\n\n\n\n
\n\n\n\n

A Call to Contribute Back to the Commons

\n\n\n\n

With an economy estimated at over $10 billion per year, and all the companies making millions of dollars using WordPress, Mullenweg took a few minutes to highlight how the Five for the Future program has protected the project from the Tragedy of the Commons.

\n\n\n\n

In one slide, he dispelled the myth that the impact a company has on the future of WordPress is dependent on the size of the company.

\n\n\n\n
\n\n\n\n

For example, Yoast has a major impact on WordPress, despite having 80x fewer employees than GoDaddy, a web host that Mullenweg seemed to be specifically calling out in the presentation when driving the point home:

\n\n\n\n

So the impact the company has on the future of WordPress is not at all related to the size of the company. There’s no reason that if we really take to heart what’s made us successful so far, that we can’t get more companies participating in the commons of what’s happening.

When a company benefits from WordPress, when they put something back into the core, whether that’s your translations community volunteering or code, as this particular graph is representing, it ensures that there’s something left in the future for WordPress to be there. You can’t run Wix or Squarespace on GoDaddy.

\n\n\n\n

Mullenweg also officially introduced Openverse now that the first version is live. He shared some of his vision for the project’s future with WordPress. The plan is to build this into the admin, so that when users upload a new image or video, they will be able to choose from among Creative Commons licenses and perhaps have their work indexed in the Openverse.

\n\n\n\n

“It’s all about creators having the control and autonomy they need to license their content, however possible,” Mullenweg said. “And for those that choose to put into the commons, that then becomes a part of what is shared in humanity and allows us to grow and create cool things together.”

\n\n\n\n

He also introduced the new WordPress.org Photo Directory, which hosts totally open imagery that can be used on any site for commercial and non-commercial uses. Someday WordPress users will be able to insert works from the Openverse into their content with just one click.

\n\n\n\n

In addition to contributing to Gutenberg through patterns and block themes and other means, Mullenweg also encouraged users to put some of their work into the Openverse.

\n\n\n\n

We’ll go deeper into some of his Q&A answers in an upcoming post, but one common theme among the questions was how WordPress might attract a younger generation of contributors and what advice Mullenweg might give to the young people inheriting the investments contributors have made in WordPress.

\n\n\n\n

In his response Mullenweg returned to his call to replenish the commons. This lifestyle of giving back and making things as open as possible is the golden thread running through the message of this year’s State of the Word.

\n\n\n\n

I think if you just give a person a blog, or even worse, a social media account, you feed them for a day. You teach them how to create the web, which is in many ways, in my opinion, the most amazing actualization of shared humanity and knowledge – how do we create something that lasts beyond our own individual lifetimes? It’s the web.

How do we create something that lasts beyond us? A legacy, a true legacy. It’s adding to the information. That’s part of what hopefully goes forward for future generations and then allows us to sort of fast [forward], skip all the mistakes, skip all the learnings, to what’s latest. It’s upgrading the clock speed and version of humanity.

\n\n\n\n

With the official launch of Openverse and the continued growth of WordPress against proprietary systems, Mullenweg was able to make a compelling case for contribution as a matter of importance to humanity — a meaningful way to increase the commons available to future generations and to be part of defining the future of the web. The vision of Openverse goes beyond WordPress, as Mullenweg said it is “something the WordPress community is creating for the benefit of the world,” with works that people are free to use on any platform.

\n\n\n\n

“I think it’s possible to have an abundance of the commons,” Mullenweg said.

\n\n\n\n

“So the more people that use a program, the better it gets in so many ways. More bugs get reported, more translations happening, more plugins get developed, more themes get developed.” This is one of the reasons market share is a strong indicator of the health of the project and its potential to continue meeting users’ needs.

\n\n\n\n

“But part of that is some percentage of the people who essentially directly benefit from WordPress, putting something back into the commons, fertilizing the soil, planting some more grass,” Mullenweg said.

\n\n\n\n

\";s: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, 15 Dec 2021 21:45:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"WPTavern: All In One SEO Plugin Patches Severe Vulnerabilities\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127049\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:169:\"https://wptavern.com/all-in-one-seo-plugin-patches-severe-vulnerabilities?utm_source=rss&utm_medium=rss&utm_campaign=all-in-one-seo-plugin-patches-severe-vulnerabilities\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2410:\"

The All In One SEO plugin has patched a set of severe vulnerabilities that were discovered by the Jetpack Scan team two weeks ago. Version 4.1.5.3, released December 8, includes fixes for a SQL Injection vulnerability and a Privilege Escalation bug.

\n\n\n\n

Marc Montpas, the researcher who discovered the vulnerabilities, explained how they could be exploited:

\n\n\n\n

If exploited, the SQL Injection vulnerability could grant attackers access to privileged information from the affected site’s database (e.g., usernames and hashed passwords).

The Privilege Escalation bug we discovered may grant bad actors access to protected REST API endpoints they shouldn’t have access to. This could ultimately enable users with low-privileged accounts, like subscribers, to perform remote code execution on affected sites.

\n\n\n\n

The Common Vulnerability Scoring System (CVSS) gave the vulnerabilities High and Critical scores for exploitability.

\n\n\n\n

Montpas explained that All In One SEO failed to secure the plugin’s REST API endpoints, allowing users with low-privileged accounts (such as subscribers) to bypass the privilege checks and gain access to every endpoint the plugin registers. This includes a particularly sensitive htaccess endpoint, which is capable rewriting a site’s .htaccess file with arbitrary content. Montpas said an attacker could abuse this feature to hide .htaccess backdoors and execute malicious code on the server.

\n\n\n\n

All in One SEO is active on more than 3 million WordPress sites, and every version of the plugin between 4.0.0 and 4.1.5.2 is affected and vulnerable. Users with automatic updates enabled for minor releases should already have the patch since it was released six days ago. For those who are updating manually, the Jetpack Scan team recommends users within the affected range update to the latest version as soon as possible.

\";s: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, 15 Dec 2021 03:08:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"WPTavern: Alara Block Theme Promises a New Pattern or Design Variation Every Week for the Next Year\";s:7:\"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=126282\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:243:\"https://wptavern.com/alara-block-theme-promises-a-new-pattern-or-design-variation-every-week-for-the-next-year?utm_source=rss&utm_medium=rss&utm_campaign=alara-block-theme-promises-a-new-pattern-or-design-variation-every-week-for-the-next-year\";s: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:4556:\"\n\n\n\n

One month ago, UXL Themes released Alara. It was a theme that carried with it one bold promise: every week for the next year, users could expect a new design variation, child theme, or block pattern. And, all of this would be done on the back of the block theme system that is slated to launch with WordPress 5.9 next month.

\n\n\n\n

Aside from one part-time member of the support crew, Andrew Starr is the sole developer for UXL Themes. With the promise, he put a whole lot of creative work on his shoulders for most of 2022. Alara already has 41 block patterns and one child theme available. Presumably, he will ship global style variations when the feature lands.

\n\n\n\n

Alara is the third block theme by UXL Themes. In February, I covered the first, Hansen. Block theming was still in its infancy at the time. The system has matured, and Starr has built some experience on top of it. It shows with his latest outing. And, for this theme, he has thus far kept up with his plan to offer new features every week.

\n\n\n\n

I am not the biggest fan of the theme’s default typography. The font-size and line-height work well enough for long-form content. However, its light font-weight can make text tough to read. The great thing about block themes is that they integrate with the site editor. Users who prefer a thicker weight only need to select it via the Typography panel.

\n\n\n\nChanging the theme’s default font-weight.\n\n\n\n

What Alara does well is offer a large selection of patterns for its users. I will sound like a broken record here, but this is how themes will differentiate themselves from others in the block-theming paradigm. If users can essentially overwrite anything about the design, the value-add is all the extras themers offer to them. Right now, that is in the form of patterns and block styles. Eventually, global style variations will be included in that list.

\n\n\n\n

Alara initially launched with 29 patterns, but Starr has added 12 more since then. They are broken down into 13 categories. One of those is an “Alara – New” category, which showcases the latest patterns bundled with the theme.

\n\n\n\nLatest patterns bundled with the theme.\n\n\n\n

I like this approach to letting users know what is new with the theme. Since WordPress has no built-in way for theme authors to highlight new features, I expect to see more theme authors take similar approaches.

\n\n\n\n

The patterns cover a range of use cases. The latest release includes some new recipe patterns for food bloggers. It includes business-friendly layouts for pricing tables, reviews, and call-to-action sections. Plus, it has several more for general-purpose use.

\n\n\n\n

Some of my favorites are the “About” patterns. There are layouts for both single site owners and teams.

\n\n\n\n“Team 3” block pattern.\n\n\n\n

The theme also offers two full-page patterns. Users can insert them and instantly have an editable page with filled-in content.

\n\n\n\n

Such patterns often take up a lot of room in the inserter when opened as a sidebar. They are better viewed in the full-screen pattern explorer overlay.

\n\n\n\nFull-page patterns.\n\n\n\n

I would still like to see WordPress officially adopt the starter page templates system or something similar to handle these use cases. Many users will rather insert a full page of content instead of piecing it together with smaller patterns. They should have a dedicated section in the UI for easy access.

\n\n\n\n

For users who prefer brighter and bolder color choices over Alara’s more vintage default design, UXL Themes has also released a child theme named Ceres.

\n\n\n\n

Alara could be a solid block theme for those eager to tinker with WordPress 5.9 features. There are still a few quirks, depending on which version of the Gutenberg plugin (or beta version of WordPress 5.9) is in use. I am excited to see if Starr keeps up with the promise of weekly design and pattern releases over the next year.

\";s: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, 15 Dec 2021 02:12:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"WordPress.org blog: WordPress 5.9 Beta 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11835\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2021/12/wordpress-5-9-beta-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5913:\"

WordPress 5.9 Beta 3 is now available for testing!

\n\n\n\n

This software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.

\n\n\n\n

You can test the WordPress 5.9 Beta 3 in three ways:

\n\n\n\n

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

\n\n\n\n

Option 2: Direct download the beta version.

\n\n\n\n

Option 3: If you use WP-CLI to upgrade from Beta 1 or Beta 2 to Beta 3 on a case-insensitive filesystem, please use the following command sequence:

\n\n\n\n

Command One:

\n\n\n\n
wp core update --version=5.9-beta2
\n\n\n\n

Command Two:

\n\n\n\n
wp core update --version=5.9-beta3 --force
\n\n\n\n

The current target for the final release of 5.9 is January 25, 2022, which gets closer every minute. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

\n\n\n\n

Some Highlights

\n\n\n\n

Since Beta 2, 14 bugs have been fixed. Here are a few of the changes you will find in Beta 3:

\n\n\n\n
  • Editor: Add FSE infrastructure from Gutenberg plugin into Core (#54335).
  • Formatting: Allow PDFs to embedded as objects (#54261)
  • Language switcher on the login screen (#43700)
  • REST API: Add navigation areas REST API endpoint from Gutenberg plugin (#54393)
  • Themes: Live Preview button bug (#54578)
\n\n\n\n

How You Can Help

\n\n\n\n

Do some testing!

\n\n\n\n

Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute. 

\n\n\n\n

If you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.

\n\n\n\n

For even more ways to test, you can also refer to this official Full Site Editing post from @annezazu.

\n\n\n\n

Got questions? Here are some answers

\n\n\n\n

In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that cover these items in detail. So far, contributors have fixed 316 tickets in WordPress 5.9, including 100 new features and enhancements. More bug fixes are on the way with your help through testing.

\n\n\n\n

Props to @psykro, @estelaris, @hellofromtonya, @marybaum, @webcommsat, @cbringmann, @costdev, and @audrasjb for contributions to this post.

\n\n\n\n

Filed under #release, #5.9, #beta

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Dec 2021 20:19:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"WPTavern: Creative Commons Search Is Now Openverse\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=126990\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:145:\"https://wptavern.com/creative-commons-search-is-now-openverse?utm_source=rss&utm_medium=rss&utm_campaign=creative-commons-search-is-now-openverse\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3812:\"

The Creative Commons search engine has been rebranded to Openverse and now redirects to its new home at wordpress.org/openverse.

\n\n\n\n

Users will find the revamped interface maintains the ability to search the same collections, narrowing results by use case, license type, image type, file type, aspect ratio, and more. The Openverse search engine is also now available in more than 10 languages, with more translations approaching completion. This update includes access to images from StockSnap and new  Meta Search providers EDUimages and Images of Empowerment.

\n\n\n\n
\n\n\n\n

“We’d like to once again express our thanks to WordPress for carrying forward the important work of providing the open community with a search engine to find works to remix, reuse, and openly enjoy,” Creative Commons COO Anna Tumadóttir said in a post passing the torch of CC Search to Openverse.

\n\n\n\n

In April 2021, Matt Mullenweg announced that CC Search would be joining the WordPress project. Automattic hired key members of the CC Search team in support of its continued development and sponsors their contributions to the project as part of the company’s Five for the Future commitment.

\n\n\n\n

Beyond hosting the search engine, adding Openverse searching and image downloading is on the roadmap for WordPress core. When asked in the comments of his blog if the WordPress media library can be integrated with Opeverse, Mullenweg confirmed that is the plan. Users may also be able to share their own works back to the commons in the future.

\n\n\n\n

In an episode of the Open Minds podcast published in August, Mullenweg elaborated on one of the motivations behind bringing Creative Commons Search into WordPress. In the early days of WordPress, GPL-compatible images were not easy to find. Mullenweg said he had even shared his personal collection of 30,000 photographs as open works that anyone could use for designs and themes, to spur on creativity when CC0 images were more scarce.

\n\n\n\n

“I also really want to make it easy for people within WordPress to license their images in a way they can be accessible to others,” he said. “Now it’s exciting to know that there’s going to be open-source-compatible images across any number of sites, to any number of people building things for the web, whether that’s on WordPress or something else.”

\n\n\n\n

Mullenweg is expected to speak more about Openverse at his annual State of the Word address tomorrow, which will stream live from New York City with a small studio audience.

\n\n\n\n

If you’re interested to contribute to the maintenance and the future of the Openverse project, you can connect with the team at make.worpress.org/openverse or in the #openverse channel on WordPress Slack.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Dec 2021 04:30:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"WPTavern: The Next Generation of WordPress Theme Authors Will Design From the Site Editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=126691\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:223:\"https://wptavern.com/the-next-generation-of-wordpress-theme-authors-will-design-from-the-site-editor?utm_source=rss&utm_medium=rss&utm_campaign=the-next-generation-of-wordpress-theme-authors-will-design-from-the-site-editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6193:\"

Last week, I played around with a new plugin that allows users to export a custom theme.json file. The project is still a little buggy at the moment, but I look forward to covering it in more detail soon. The export function was more of a secondary objective for the plugin, but it represents a feature I look forward to landing in WordPress one day.

\n\n\n\n

While tinkering with the plugin, I reminded myself to check on the progress of a related ticket for Gutenberg. Currently, the site editor feature allows end-users to export their theme templates. However, there is still no way to do so for global styles.

\n\n\n\n

Essentially, block themes need two components: templates and a global styles configuration. There are other pieces. The functions.php file is increasingly unnecessary, and the standard style.css file is often used for adding theme data instead of CSS. There is talk of adding both /patterns and /styles folder support for automatically registering block patterns and global style variations, respectively.

\n\n\n\nTwenty Twenty-Two theme folder and file structure.\n\n\n\n

WordPress theme development already looks different than it did just a few years ago. Soon, old-school themers will hardly recognize it.

\n\n\n\n

That is not necessarily a bad thing. The ongoing mantra is that the platform seeks to democratize design much as it did for publishing. I have often wondered how feasible such a goal really was. I would see sparks of genius littered throughout the project in the past few years. It took a while for all the moving parts to become a well-oiled machine. There are still some missing components, but the platform’s promise is becoming a reality.

\n\n\n\n
\n\n\n\n

Over the weekend, I happened across an old friend’s Facebook profile. He is one of the few bloggers I began following in the early 2000s. I noticed he had shared something from his blog, and I checked it out. He has a background in journalism, and he has always had unique insights into what most of us might consider the mundane, day-to-day life stuff.

\n\n\n\n

I continued reading other posts. It was a welcome change of pace to pour through thoughts from someone who is simply blogging for the sake of blogging, even if still on Blogger and not WordPress. The site does not look any different than it did years ago. He even has a blogroll. I spent about an hour going from site to site, reading the ramblings of other passionate bloggers, most of them on the self-hosted WordPress software or WordPress.com. It was a reminder of why we continue building this platform.

\n\n\n\n

Of course, we all have different reasons for coming to the same place. We must also have a healthy economy behind WordPress, which helps fund the project’s more altruistic mission. At the end of the day, the goal is to provide free software for the masses, offering an alternative to the gatekeepers and walled gardens elsewhere on the web.

\n\n\n\n

Theme design needed to be shaken up. I enjoy finding the odd diamond in the rough. But, it has been a long time since the average end-user has had true freedom with their website’s design. Kubrick was fine in the mid-2000s. WordPress catered to a DIY crowd that was OK with making CSS changes to get their desired outcome. However, in the 2020s, the platform must bring a new set of tools to a wide-ranging audience. That is what the global styles feature is all about.

\n\n\n\n
\n\n\n\n

When WordPress 5.9 launches next month, many users will get a taste of the site editor. Users who switch over to the upcoming Twenty Twenty-Two theme will have more design power at their fingertips than ever before with stock WordPress. From templates to styles, they will change the front end of their sites to whatever they dream up.

\n\n\n\n

Some will undoubtedly stumble upon the “Export” button in the site editor:

\n\n\n\nExporting the site’s templates.\n\n\n\n

It is a handy tool for theme authors transitioning to block theme development, but that little button has a world of potential. Right now, it spits out an edit-site-editor.zip file with a /theme sub-folder. Within that, sits /templates and /parts.

\n\n\n\n

What is missing is the theme.json file, which represents the global styles. When that lands, users will essentially be exporting an entire theme. Well, minus a screenshot and required legacy files like style.css.

\n\n\n\n

Part of democratizing design is not just handing over the ability to customize the site. Fulfilling the mission means people can share those designs. The next generation of WordPress themers will not be stuck in a code editor like those of us today. They will cut their teeth on the built-in site editor. Some will graduate to more advanced development, but others will have everything they need to publish their themes on WordPress.org or even venture out and build their own businesses. In part, it will level the playing field for those with an eye for design but not the coding chops to create those projects.

\n\n\n\n

Exporting global styles cannot get here fast enough. Then, we need to add pattern exports to the equation, but the mission requires we take it one more step.

\n\n\n\n

I look forward to the day when a user can build an entire theme from scratch in WordPress. Then, they submit it to the theme directory without writing a bit of code. Could one of those “average” bloggers find a talent for web design they never knew they had? Could someone who always wanted to learn but did not have the time/resources/privilege create the next most popular theme? I like to think so.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Dec 2021 00:37:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"BuddyPress: BuddyPress 10.0.0-beta1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=322432\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"https://buddypress.org/2021/12/buddypress-10-0-0-beta1/\";s: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:5913:\"

BuddyPress 10.0.0-beta1 is finally available for testing! \"🎄\"

\n\n\n\n

Please note the plugin is still in development, so we recommend running this beta release on a testing site.

\n\n\n\n

You can test BuddyPress 10.0.0-beta1 in 4 ways :

\n\n\n\n\n\n\n\n

The current target for final release is early next year : January 5, 2022. That’s only 3 weeks away \"😱\", so we would appreciate your help making sure this next major version of your community engine is as good as it can be.

\n\n\n\n

Please note BuddyPress 10.0.0 will require at least WordPress 5.4.

\n\n\n\n

As usual, testing for bugs is the key to a safe upgrade. It’s the main reason we actually package beta/RC versions \"👉\" so please give us a few minutes of your time to make sure this pre-release behaves the right way with your specific WordPress configuration, your theme, and the other WordPress plugins you are using. Try to use a testing site which is very close to the one you are using in production. If you find something weird (aside from the great new features below), please report it on BuddyPress Trac or post a reply to this support topic.

\n\n\n\n
\n\n\n\n

Around 70 changes to expect in 10.0.0

\n\n\n\n

You can check out this report on Trac for the full list of them. Below are the ones we believe will improve your BuddyPress experience in the most significant way.

\n\n\n\n
\n\n\n\n

\"🛂\" Site Membership Requests

\n\n\n\n

Site Administrators wishing to have more control over who can join their community will be able to enable site membership requests from their BuddyPress Options Administration screen. Once done, BuddyPress sign-ups are transformed into membership requests to be manually reviewed and approved by an Administrator to validate new user accounts.

\n\n\n\n
\n\n\n\n

\"🗞\" More engaging logging activities

\n\n\n\n

These simple activities about specific user interactions or events (e.g.: a user became a friend of another user) will be more visually attractive to improve user engagement in your community. The most impressive new activity is that which is generated when a user updates their profile photo: it will include the profile photo that spurred the creation of the activity item, even if it has been updated since \"📸\"!

\n\n\n\n
\n\n\n\n

\"🎨\" WordPress Full Site Editing compatibility

\n\n\n\n

You’re beta testing WordPress 5.9: first thank you, second please take a few more minutes to check the improvements we’ve made to our BP Theme Compatibility API to play nice with themes supporting Full Site Editing such as the next WordPress default theme: Twenty Twenty-Two.

\n\n\n\n
\n\n\n\n

\"➕\" A new place to easily discover our next BuddyPress Add-ons

\n\n\n\n

BuddyPress Add-ons are side projects/projects as features/next BuddyPress blocks maintained by the BuddyPress development team we’ll soon make more widely available by publishing them on the WordPress plugin directory. When BuddyPress 10.0.0 is released, you’ll find a new tab to your “Add Plugins” Administration screen. On it, you’ll see a new add-on for a potentially upcoming feature: BP Rewrites. We think this will bring more contributions to the BuddyPress project as a whole.

\n\n\n\n

\"🎮\" Happy testing!

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 12 Dec 2021 18:05: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:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"Gutenberg Times: Pattern Block, State of the Word and theme.json builders – Weekend Edition 196\";s:7:\"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=19815\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"https://gutenbergtimes.com/pattern-block-state-of-the-word-and-theme-json-builders-weekend-edition-196/\";s: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:15905:\"

Howdy,

\n\n\n\n

it’s great to be home again! How are you?

\n\n\n\n

We are coming up to the end of the year, and it’s time for the annual State of the Word (SOTW). Matt Mullenweg, co-founder of WordPress, presents the accomplishments and challenges of the outgoing year and of what’s to come for next year to the WordPress open-source project.

The event will be live-streamed from New York, on Tuesday, December 14th, at at 5 pm ET – 22:00 UTC. On the SOTW announcement page, you can also find a list of watch parties from around the world, some in-person, some virtual.

\n\n\n\n

After the two-hour event, the Post Status team will hold a live event on Twitter Spaces to discuss SOTW. I’ll be there to listen in.

\n\n\n\n

Now, let’s catch up on last week’s Gutenberg news!

\n\n\n\n

Yours, 💕
Birgit

\n\n\n\n\n\n
\n\n\n\n\n

Table of Contents

\n\n\n\n
\n\n\n\n
\n\n\n\n\n

Gutenberg Plugin Version 12.1

\n\n\n\n

The new plugin version came out Wednesday Dec 8th, 2021, with plenty of bug fixes that made it also into WordPress 5.9 Beta 2.

\n\n\n\n

Riad Benguella published the release notes: What’s new in Gutenberg 12.1 ( 8 December)

\n\n\n\n

Justin Tadlock took it for a spin. You can read his take in Gutenberg 12.1 Fixes Block Appender Layout Shift, Adds Template List Views, and Enhances Global Styles. And Congratulations to the WPTavern team to the new Site design, released together with the WordPress Special Projects team at Automattic.

\n\n\n\n

Grzegorz Ziolkowski and I discussed the new Gutenberg version in our episode 57 of the Gutenberg Changelog podcast. Many links in the show notes.

\n\n\n\n\n
\n

Subscribe to the Gutenberg Changelog podcast
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed 

\n\n\n\n\n
\n\n\n\n\n

Plugins and other tools for the Block Editor.

\n\n\n\n

The agency, 10up published their Publisher Media Kit Page plugin that created pre-configured media pages using Block Patterns. It works with Newspack and the Twenty-Twenty-one default theme.

\n\n\n\n

Justin Tadlock gave it a whirl. Here is his post: 10up Releases the Publisher Media Kit WordPress Plugin

\n\n\n\n
\n\n\n\n

The number of “Full-site Editing” Themes in the WordPress repository increased to 31 this week. The newest Theme is Videomaker by the designers at Automattic. It’s aimed at film directors and video creators. Justin Tadlock posted this review: Videomaker Block Theme Targets Film Directors and Video Creators

\n\n\n\n
\n\n\n\n

In Cwicly Gutenberg Toolkit: A New Full Site Editing Solution, David McCan reviews the kit that includes a block-based theme, a Gutenberg blocks add-on, and Advanced Custom Fields Pro. McCan includes a video walk-through of this new tool.

\n\n\n\n
\n\n\n\n

The team of Trewknowledge wrote The Future is Coming, Now. Watch and Learn About WordPress 5.9 Anticipated Features and summarizes the most important features coming to a WordPress instance near you in January 2022.

\n\n\n\n
\n\n\n\n

In his article, Custom Single Post Layouts with WordPress Gutenberg, Jamie Marsland covers the process on how to build a custom layout for your single posts using the WordPress Gutenberg Block Editor and Full Site Editing. He covers the dynamic post blocks and how to use the template editor.

\n\n\n\n\n

 “Keeping up with Gutenberg – Index 2021” 
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly. The index 2020 is here

\n\n\n\n\n

Building Custom Blocks and Features

\n\n\n\n

This week, Ryan Welcher showed us how to create a Meme Block on his live stream. The code is available on GitHub.

\n\n\n\n“I don’t always type badly, but when I do, it’s during a live stream”.\n\n\n\n

Phil Sola and James Koussertari are the WPBros and started their YouTube Channel with episodes covering Gutenberg Block Development. The first four episodes are already available. Check them out.

\n\n\n\n

Creating Block Themes

\n\n\n\n

Rich Tabor has been a giant fan of Block Patterns. This week, he wrote a tutorial on Building WordPress Block Themes with the New Gutenberg Pattern Block.

\n\n\n\n

The Pattern block renders a pattern — typically used within a template from a block theme. The main advantage is that it allows for translatable templates in themes.

\n\n\n\n
\n\n\n\n

David Gwyer has been working on a Block Theme Generator and the first version is already online. It offers HTML form and some tools to select all the settings you would want to configure for your theme in the theme.json file, assembles it and lets you download the file to add to your theme. It’s a first version, but already quite nifty. I, for one, had great fun playing around with the color pickers for all kind of features.

\n\n\n\nScreenshot: Block Theme Generator by David Gwyer.\n\n\n\n
\n\n\n\n

On a side note, Ryan Welcher is also working on creating a theme.json generating tool within the block editor. You can watch the progress on this GitHub repository.

\n\n\n\n
\n\n\n\n

Jeff Ong and Jason Crist picked 4 topics to highlight in the post Gutenberg + Themes: Week of Dec 5.

\n\n\n\n
  1. New Color Picker is coming to Gutenberg
  2. There is an ongoing discussion on how best to add global padding, and still allow for full-width alignment. Check out the ideas that are tested. 
  3. Opt into block styles via theme.json. This is to allow wp-block-styles support via theme.jscon. 
  4. Contrary to other styling, it seems Global link styles override block-level styles. Chime in on the issue. 
\n\n\n\n

I am a big fan of the digest form of their weekly round-up post.

\n\n\n\n

As always, the weekly round up also lists Overview issues for various feature in the works, like the Typography Tools, the Global Styles interface, the Default theme and a few more items. 

\n\n\n\n

And lastly you find a list of General Resources to documentation and tutorial. 

\n\n\n\n
\n\n\n\n

Block Themes were also a topic for the Ask the Bartender column at the WPTavern: Justin Tadlock answered the question: Is There a Starter for Building Block Themes?

\n\n\n\n
\n\n\n\n

Upcoming WordPress Events

\n\n\n\n

December 13, Monday 1pm ET / 6pm UTC
WordPress Trends to Watch in 2022
Discussion with Paul Lacey, Ronald Gijsel, Cami MacNamara, and Anne McCarthy.
They’ll share ideas about emerging trends beyond WordPress 5.9 for:

\n\n\n\n
  • Full Site Editing
  • Block Themes
  • Where Gutenberg goes from here
  • Performance improvements and more
\n\n\n\n

RSVP now to attend or catch the replay (GoDaddy Pro Online)

\n\n\n\n
\n\n\n\n

Post Status is not the only team getting the hang of Twitter Spaces. Ellen Bauer, friend of Gutenberg Times and co-founder of Elma Studio, also started informal audio-only discussion. Bauer shared her schedule for the next few weeks:

\n\n\n\n
  • 16 Dec, Thursday, 6pm UTC / 1pm ET
    Thoughts on Matt’s ‘State of the Word’
  • 22 Dec, Wednesday, 9am UTC / 4am ET,
    How to prepare for FSE & the WP5.9 release
  • 30 Dec, Thursday, 6pm UTC / 1pm ET,
    Casual End of 2021 WordPress recap/chat
\n\n\n\n

Follow Ellen Bauer on Twitter to get the links to the Twitter Spaces events.

\n\n\n\n
\n\n\n\n

December Fri, Dec 17, 2021 at on 10:00 AM ET / 15:00 UTC
Kyle Van Deusen will host a live event and show people interested in building blocks how he rebuilt the WaveApps homepage with his favorite block packages, He will answer viewer questions. Add the event to your calendar

\n\n\n\n
\n\n\n\n

On the Calendar for WordPress Online Events site, you can browse a list of the upcoming WordPress Events, around the world, including WordCamps, WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.

\n\n\n\n\n
\n\n\n\n

Don’t want to miss the next Weekend Edition?

\n\n\n\n

We hate spam, too and won’t give your email address to anyone except Mailchimp to send out our Weekend Edition

Thanks for subscribing.
\n\n\n\n
\n\n\n\n\n\n

Featured Image: “LetterPressBlocks_RT5” by fiveten is licensed under CC BY-NC 2.0 via Openverse

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 12 Dec 2021 00:18:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:42;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:110:\"Gutenberg Times: Gutenberg Changelog #57 – Gutenberg 12.1, Block Theme.json Builder, WordPress 5.9 Beta 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://gutenbergtimes.com/?post_type=podcast&p=19822\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://gutenbergtimes.com/podcast/gutenberg-changelog-57-block-theme-json-builder/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:48664:\"

Birgit Pauli-Haack and Grzegorz Ziolkowski discuss Gutenberg 12.1, Block Theme.json Builder, WordPress 5.9 Beta 2 and Twitter Spaces

\n\n\n\n\n\n\n\n

Show Notes / Transcript

\n\n\n\n\n\n\n\n

Subscribe to the Gutenberg Changelog podcast via your favorite podcast apps!
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed 

\n\n\n\n

Show Notes

\n\n\n\n

David Gwyer has been working on a Block Theme Generator

\n\n\n\n

Ryan Welcher is working on a Theme.json Builder

\n\n\n\n

Follow Ellen Bauer to learn about upcoming Twitter Spaces

\n\n\n\n

Recording of this year’s React conference

\n\n\n\n

WordPress 5.9 Beta 2 released

\n\n\n\n

What’s new in Gutenberg 12.1 ( 8 December)

\n\n\n\n

Gutenberg 12.1 Fixes Block Appender Layout Shift, Adds Template List Views, and Enhances Global Styles

\n\n\n\n

New directory names for block-based (FSE) themes

\n\n\n\n

Gutenberg + Themes: Week of Dec 5

\n\n\n\n

Follow Twitter Bot @GoodFirstBugs

\n\n\n\n

Stay in Touch

\n\n\n\n
\n\n
\n\n\n\n

Transcript

\n\n\n\n

Birgit Pauli-Haack: Well, hello and welcome to our 57th episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about Gutenberg 12.1 release, block theme.json builders and WordPress 5.9 Beta 2, and Twitter Spaces. I’m Birgit Pauli-Haack, curator at the Gutenberg Times, and Developer Advocate at Automattic. And I’m here with my co-host Grzegorz Ziolkowski, JavaScript developer at Automattic and WordPress core contributor. So how are you today, Grzegorz?

\n\n\n\n

Grzegorz Ziolkowski: Oh, thank you, I’m great. Winter is already in Poland. We have a tons of snow outside, so we were outside with my daughter today doing angels. That was fun, so yeah.

\n\n\n\n

Birgit Pauli-Haack: Yeah.

\n\n\n\n

Grzegorz Ziolkowski: It’s pretty surprising that it’s so early, because usually it’s in January. Anyway, how is it at your place? How are you?

\n\n\n\n

Birgit Pauli-Haack: Well, in Florida, it’s really warm. It’s 70 degrees Celsius, so I’m not going to complain about anything. And I just got back from Germany where it was really cold and I got to test all my winter clothes configurations, and yeah, it was end to end testing and it worked.

\n\n\n\n

Grzegorz Ziolkowski: Thank you, all good. We are prepared.

\n\n\n\n

Birgit Pauli-Haack: We are prepared. Yeah. And we have to, because we are heading out to Vancouver for the holidays and visit friends. So there is going to be snow in the forecast as well. 

\n\n\n\n

Yeah, so we have a great episode today. No guest, and is also the last one from 2021, the last episode for 2021, because we are going for holidays and there is a release, the Gutenberg release 12.2 is scheduled for December 22nd, but that’s so close to the Christmas holidays that we said, okay, let’s push it into January and we will do two releases with the episode 5.8.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. I’m not sure if there is, will be all on, like the way you said like on time, I mean on time, like at this time of the year. So the Gutenberg core team, there’s always discussion whether to postpone some of the releases or not. So I’m not sure this type of discussion already happened and it can be on 22 because it’s just before major holidays for most of the contributors, so it should be good. But I remember that there was a time when we had three weeks between releases and maybe even once we skipped one of their releases. So it’s something that’s unclear in my opinion.

\n\n\n\n

Birgit Pauli-Haack: Yeah. Okay. So if you want to subscribe, dear listeners, to the Gutenberg Weekend Edition, we will keep up during the holidays, maybe not every week, but definitely more often than the Gutenberg Changelog Podcast. You will learn the newest about the release schedule for the Gutenberg plugin to come. 

\n\n\n\n

Community Contributions

\n\n\n\n

So today I also wanted to, we don’t have any announcements or listener questions, but I found on Twitter that David Gwyer has been working on a block theme.json generator, and I connected with him and it’s still in preview, but it’s a next json, next JS application that he’s building with a form, and then you can then download the theme.json for it. He has different tabs that you can see. So it’s not yet out, but I’m just announcing that it’s something you could keep an eye out for when it comes out. And if you are nice to him maybe, and ask him for a preview link on the Theme.json Generator. Yeah.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. I think it’s a very nice idea. It’s something that, it’s been on my mind as well, that we should have something like that already in WordPress core. So I’m glad that the community, as usual, is ready to jump in and accelerate all the explorations in that regard. So that’s brilliant. I’m looking forward to see how it plays out. And yeah, it’s something that we wanted to mention that Ryan Welcher from Automattic, he is already looking into something similar. I don’t know more about the approach he took in his tooling.

\n\n\n\n

Birgit Pauli-Haack: Yeah. He’s building a plugin that you can install on a site and then you would use the block editor, the forms will show up in the block editor. So you can then do the configuration for the styles, the color settings, and all that right in your block editor. So he is also, he’s not that far yet either, but it’s all something, the two tools to watch evolve and see what is a solution that you would want to use in that regard. So I’m glad that this is going to be a thing over the holidays. And I know that John Q at one point had a site where he started something similar and both Ryan and David knew about that before they started it. But in the meantime, John Q took it offline because it wasn’t updated anymore. The theme.json schema has changed quite a bit since he started that and he wasn’t working on this project anymore. So there are two new initiatives around it. Pretty cool.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. It reminds me a little bit jQuery UI. So in the past, when jQuery was everything, you could use this library for components, and then there was this page that you could tweak the styles using the controls and it would generate CSS files for you. So I think standalone apps is great because of that experience that you have call canvas for you, and you can play with everything and see how it changes. Whereas the approach of using the site editor, it’s a little bit off because you don’t have all the components presented on the page. So that might be a challenge for some of the folks to use a plugin version for that. But it’s like maybe there is something in the middle, that you can combine those two and have this nice experience of using WordPress core and having the standalone experience of the next JS app that you gives you the power of all the components that you could style.

\n\n\n\n

Birgit Pauli-Haack: Yeah. It’s interesting, different approaches, to see how they evolve and how they probably fit different use cases as well. And Ellen Bauer of Elma Studio, she’s a good friend of the Gutenberg Times, has been on multiple live Q and As for theme as a theme builder, and also has a great block theme in the webpress.org repository called Aino that’s A-I-N-O. And she started with Twitter spaces and having discussions around theme building, freelancing, and she sent us the dates for her next events and she will have them… so she will have one on December 16th. And that’s on the topic after the State of the Word from Matt Mullenweg, kind of discuss the thoughts from the community there. Then on December 22nd, that’s a Wednesday, it’s probably too early for US because it’s at 9:00 AM UTC, Ellen Bauer is from New Zealand. So she’s kind of very flexible in her time, but sometimes it’s going to be a real rough thing.

\n\n\n\n

So 9:00 AM UTC, that’s 5:00 PM Eastern. I know people who are up there, I’m not. So how to prepare for FSE and the WordPress 5.9 release, which is going to be quite interesting. And then on December 30th at 6:00 PM UTC, 1:00 PM Eastern, it’s a casual end of 2021 WordPress recap and chat. Now I would love to give you links to all of those, but it seems that Twitter Space still has a few restrictions, and one is that you can only schedule one event in advance. So I would suggest you follow Ellen Bauer @Ellenbauer, E-L-L-E-N-B-A-U-E-R on Twitter. So you get the notification for her next events. So Twitter Spaces has kind of come really around in the WordPress community. I know that Post Status is doing quite a few Twitter Spaces. Have you any experience with Twitter Spaces?

\n\n\n\n

Grzegorz Ziolkowski: So I participated yesterday, I mean, for 10 minutes maybe, but there was a React conference and afterwards they were doing as well, the session with speakers. So they were discussing some key topics that were covered during the day and discussing how the community fits in, all that pictures, other frameworks and libraries. So that was quite interesting, but I could join only SLD center, but still something that I just joined randomly because it’s like there was this blue button on the top with all the faces of participants and that caught my attention. So I like that. But as you said, the fact that you don’t know upfront, that something like that is happening is a bit annoying, I think. Although it has also some benefits because maybe that’s the whole idea to have it to something that just started because people exchange opinions on Twitter and then suddenly they can just jump in and start talking about the topic.

\n\n\n\n

Birgit Pauli-Haack: Yeah. So I like it as a more casual way to connect with other people that are in your Twitter stream, or you are part of it. One restriction is that on your desktop, you can only connect as a listener. If you want to be a part of the… in speaking with the other people and have your input, you would need to be on the mobile app, the Twitter mobile app. So I don’t know if you said it, but Twitter Spaces is just audio. So that is also a lower barrier than a live stream because you don’t have to be on video. It’s almost like a group phone call, so to speak, with other people listening in, and it’s much less formal. And I like that part. Yeah. Oh, speaking of React conference, I think that we have the link for the recordings in our show notes, if you’re interested in what’s happening with React. Are there anything that stood out for you, what WordPress developers would need to know? I know I’m throwing that at you right now.

\n\n\n\n

Grzegorz Ziolkowski: So one thing that they are introducing new features and they’re introducing many changes, although the way how they approach it is very nice because everything will be backward compatible, so they just follow what WordPress does in that regard, which is amazing. And they had some other plans for the next major version, which is 18, that should be released early next year. And what I found very interesting is that initially they wanted to have some sort of switch for new features that is you need to apply for a whole application, however, they changed the plan. And it’s very interesting that you will be able to just pick a subset of your application and enable one given feature.

\n\n\n\n

And there’ll be a few features that you will be able to use concurrent mode, those are very technical things, but in general, they are saying that your application will work exactly the same in 99,999 percent of time, which is great. And yes, I think that there will be a few improvements that the block editor would benefit from. I cannot confirm that because we don’t have any numbers for now, but I think that in terms of performance, there will be some benefits. And yeah, and also Diego Haz had a presentation about accessibility and he was showing his Reakit library that is used inside WordPress.

\n\n\n\n

So that’s an interesting part. And he also was presenting the composite component that we use in the block inserter. And he showed how the new APIs will benefit that. And so one thing that I like the most is that there will be some sort of behavior that allows you to show loaders in a very smart way. So for instance, when you show the results for the blocking set, and the block patterns, you will be able to still present the previous set of results while the new is loading and assume that’s ready, then it’ll replace that. And it’s like very nice APIs for us. So that’s very technical, very deep. And I think the block editor will benefit from that in the next releases in 2022.

\n\n\n\n

Birgit Pauli-Haack: Yeah. So sounds like everything is really evolving. So now let’s get back to our immediate release. 

\n\n\n\n

What’s Released – WordPress 5.9 Beta 2 and Gutenberg 12.1

\n\n\n\n

So what’s released section in the Gutenberg Changelog is, well first, WordPress 5.9 Beta 2 was released on Tuesday, December 7th and the community is going to yeah, asked to really stress test this because it’s one of the latest releases and there are not a whole more to come. There is probably a Beta 3 in the works, but it’s still unclear if there should be a January 4th Beta 4 release before the release candidate comes out. But yeah, so we have the news item, the news page about the release in our show notes. And it gives you great instructions on how you can test things, especially the bug fixes that came in late there. 

\n\n\n\n

And that brings us to the Gutenberg plugin release 12.1. So some of the changes were back boarded to the 5.9 WordPress core. But yeah, so what’s in the Gutenberg, 12.1? Do you want to start us off?

\n\n\n\n

Grzegorz Ziolkowski: Yeah. I’m just thinking about that, if everything was back board, I mean, it will be back boarded as far as I understand that, or no, it might be already there. Yes. It it is already, sorry. I had to think how the process goes and because we are using RC of the plugin when we start cherry picking comments. So that’s like already happened this week on Monday and yeah. So I think the biggest change is that one of the blockers that was right during the time when the release date was postponed, was the experience around picking templates. And now we have a separate page for templates and it contains the list view, that contains the name and the source of the template, whether it comes from the team or maybe whether that was created by the one of the users from the site.

\n\n\n\n

So that shows the list, and on the same screen, there is also a new button that is on the top right side. And it allows you to create a missing template. So let’s say you don’t have a 404 page provided by the theme, and you can just use button to create that one, that experience. Yeah. I mean, it’s like that’s the biggest change. That was something that was missing. I mean, that was in the plugin to work different in a different way. So there was a sidebar on the left side that allows you to do all those things. However, I don’t know. Do you remember why it was not included?

\n\n\n\n

Enhancements

\n\n\n\n

Birgit Pauli-Haack: It was in 5.8. There was a template section in the right hand sidebar. Yes. But that was because the full site editor didn’t have all the right workflow. So you are only able to edit the template that you were on though, the post or the page template, but now they have this under appearance, the additional menu. And that’s where you can look at templates as well as template parts. It’s a separate menu. And that is now available for WordPress 5.9. Another big change is, or what was missing, was that in the site editor, you were able to add blocks as well as block patterns. But now you also can add reusable blocks that you already built to add them to a template. So that was a missing piece right there. And I’m glad that’s in there now for 5.9.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. I think that for sure was overlooked at some point, because there’s so many features already in the post content editor that it wasn’t so easy to bring them to the site editor and it was like, each feature needs to be also evaluated, whether it makes sense in that context.

\n\n\n\n

Birgit Pauli-Haack: Yeah. And I can understand that, yeah, that some features are not finished until they are evaluated for a broader usage. Like if it works in a post edit, it doesn’t mean it works that way in the site editor, so some things need to change to actually make it work for the site editor, which also kind of updates the UI or something like that. So it’s quite a complex system that is back and forth from new features to old features, to new features kind of way. It’s almost like a feedback loop that you also have with users, and you introduced few new features.

\n\n\n\n

So yeah, in the global styles now it’s also possible to opt out of the default palette for the interface. So if a theme and theme JSON opts out in the default colors for a site, then those colors are not shown in the site editor sidebar, which, yeah, certainly that was a big complaint that people said, well, I don’t want users to actually be using those colors. But on the other hand, you need those colors when there is no color palette from the theme. So it, yeah, it kind of offers something, yeah. So it’s kind of an interesting problem to solve.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. But I guess the stats, they still exist because you could change teams and you could be using one of those core colors. So they need to be there in case you use them in one of the overridden templates or template parts, or reusable blocks or whatever. But yeah, I think also on the feature section, it’s something that is more like a developer experience. So we were talking about the schemas for theme.json that helps developers and designers when they building their teams have this hints, what given property could be, or just showing the list of possibilities. And there was change other that allows to use custom blocks. So not only the core blocks, but if you have a custom block and you could apply some style changes and do the hints, because it’s now smart enough to figure out that that’s also a block that could have some styling. So just a handy improvement for-

\n\n\n\n

Birgit Pauli-Haack: Yeah, absolutely. Yeah.

\n\n\n\n

Grzegorz Ziolkowski: …that use, because if you are not playing with the block Theme.json generators….

\n\n\n\n

Birgit Pauli-Haack: Yeah. And that’s certainly a challenge for the Theme.json generators, to keep up with the new changes in the schema. And that’s an ongoing story about Gutenberg development that every person involved in it needs to kind of keep up with it, being theme developers or plug-in developers now, tool developers it’s… yeah. I hope it slows down a bit in, I don’t know, three or four years.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. At least because of backwards compatibility, some of the existing features will stay there. So that’s one good thing, but there’s so many new features coming every two weeks. So yeah.

\n\n\n\n

Birgit Pauli-Haack: And so there was one other improvement, is the position of the block appenders and the behavior of it, which is really, it was a long ongoing problem for the last two or three years.

\n\n\n\n

Grzegorz Ziolkowski: Yes.

\n\n\n\n

Birgit Pauli-Haack: That the layout kind of jumped a little bit when the appenders come in. Appender is the plus sign where you can then add new blocks to it. And now that’s the little plus button and now you can, they are now, what is it, fixed in their positioning. And then so with the relation to the block, so they’re not underneath the block where they created those jumps and that alone is a feature that actually makes the block editor less awkward, I say, yeah.

\n\n\n\n

Grzegorz Ziolkowski: Yes, yes. I mean also that helps you to, because it’s now on the bottom right side of the space that the block occupies, the parent blocks that can have blocks inside, which is really good because you exactly know where are you adding this block. Whereas before the plus sign was in many cases it was positioned in a way that you weren’t sure whether that goes to the block you want to add or just is outside. So yeah. I like that a lot. I must admit when I saw that for the first time I was a bit lost. I didn’t know what this icon is all about. I was thinking that something is misplaced, but once you learn how it works now, it’s so much better.

\n\n\n\n

Birgit Pauli-Haack: Yeah. Yeah. I totally agree. Yeah. Good job everyone. And there is now a keyboard shortcut to double escape unselected blocks.

\n\n\n\n

Grzegorz Ziolkowski: No, no. So you need to press escape twice.

\n\n\n\n

Birgit Pauli-Haack: Okay.

\n\n\n\n

Grzegorz Ziolkowski: So because now alt select all blocks, whereas one escape just makes you go out on the edit mode. So it goes outside of the single block.

\n\n\n\n

Birgit Pauli-Haack: Okay.

\n\n\n\n

Grzegorz Ziolkowski: So it just….

\n\n\n\n

Birgit Pauli-Haack: Yeah. Does that take care of, sometimes it happens that I’m not getting out of select. I cannot edit things. And is that….

\n\n\n\n

Grzegorz Ziolkowski: Yes.

\n\n\n\n

Birgit Pauli-Haack: Yeah.

\n\n\n\n

Grzegorz Ziolkowski: Yeah, because we have two modes. One is for browsing. I know, it’s like, what’s the name, but the idea, yeah. The one is that it’s for accessibility. When you are contained in a blog that you are editing and then when you tap, it goes to the sidebar. And when you tap it just go to the toolbar, like there’s a cycle inside the single block, whereas when you escape and you can just use arrow up down just to navigate between blocks. So that makes you faster to move between blocks if you are using keyboard a lot.

\n\n\n\n

Birgit Pauli-Haack: Yeah. So I’m going to test this out over the weekend when I do the weekend edition, because that’s where I sometimes got trapped and I got out of it by just reloading the page. 

\n\n\n\n

Grzegorz Ziolkowski: When you keep press enter, then you go again in the edit mode so that’s… You need to learn some of those shortcuts and just use mouse and…

\n\n\n\n

Birgit Pauli-Haack: So the next thing is adjust the order of theme blocks and reorder the inserted items, the inserter items, sorry. And that has to do with the site editor and the theme blocks that are available. So the order is adjusted so you might find it on a different spot if you have been testing this before.

\n\n\n\n

Grzegorz Ziolkowski: There are now so many theme blocks and you know, some of them aren’t that important. so that’s why you can see now, like on the top of that is the navigation block or site title, site logo, or the logo that you would rather prefer to use when you start thinking about building the design for your template.

\n\n\n\n

Birgit Pauli-Haack: Yeah. And also, so it’s more the, oh, I did not know that it was actually a login logout block there. I just saw that because it’s now on the top.

\n\n\n\n

Grzegorz Ziolkowski: Yes.

\n\n\n\n

Birgit Pauli-Haack: Yeah, yeah. Awesome. Yeah. What’s next?

\n\n\n\n

Grzegorz Ziolkowski: Yeah. In the block library, there is now a new block, which is comments pagination blocks. So just to explain, there is now an ongoing quark on the comments query loop, which is like more or less the same concept, like query loop, which is a technical name for the list of posts or pages or whatever post type you pick. And the idea is to replicate the same capability for designing how comments look and that pagination is one of the things that you can have with comments in the classic themes. So it’s there and the next and previous blocks for the pagination are missing still, but they should land soon. So in general, this comment square look, I would consider that very experimental in the WordPress 5.9. There will be a different block that is just wrapped around on the comment form or comment template. I don’t remember the name, but it’s just the PHP function that does everything for you and shows you the comments that you see on the single post page.

\n\n\n\n

Birgit Pauli-Haack: All right. Okay, cool. Yeah. So the comments pagination block and all the other single comments blocks that are in the works, or have been released with the plugin will be in WordPress 6.0, because it’s still all experimental.

\n\n\n\n

Grzegorz Ziolkowski: Yes. I mean, if everything is done, which is most likely, yes.Birgit Pauli-Haack: Okay. All right. So then there were some updates on the navigation block and now it shows its changes to the sub menu options to show an error button when relevant and then implement suitable fallback to a navigation block on the front end when there is no menu yet selected. That was something that the team experimented with quite a bit, and there are four or five PRs that are related to that. It certainly is… that’s part of the backwards compatibility also for the navigation block that if there is no menu, because it’s a new site, yeah, you still can use the navigation block and get hints on that. But it also shows you a fall back. I tested this and it was quite interesting to see that it kind of took over and showed me all the pages if I wanted to, the navigation block is coming along quite nicely. Yeah.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. I think they also added PHP filter in case someone doesn’t like the default behavior for the fallback. So you can opt out with that. The filter name is block under score core underscore navigation underscore render underscore fallback, quite long one. And yeah. And basically you can just opt out or just provide your own way of doing that, which is pretty nice. And also there’s a technical change, which is less important, but they decided that instead of having the navigation menu ID attribute, there will be a ref which is aligned with how usable blocks work.

\n\n\n\n

Bug Fixes

\n\n\n\n

Birgit Pauli-Haack: Awesome. Yeah. So next item that we want to point out is the template part block that when you convert it to a reusable block, it kind of removes the color space and layout options of the template block. That’s very interesting to kind of test out if on… I’m kind of wondering, the interesting part is because I’m wondering about the use case for that, but I think the more you use it, the more you kind of understand it much better, then there is a change to the gallery block. That’s the refactored gallery block. And now they turned on the auto migration from our version one gallery block to our version two format when the post is edited. So that’s quite nice so you don’t have to physically do anything when you open up a post or a page that has a previous gallery version. It automatically converts it to the gallery version that has each image as an image block and uses the inner block. So you have all the features of an image block also available to your gallery.

\n\n\n\n

Grzegorz Ziolkowski: Yeah, it’s interesting. Although, I guess you still need to save it just to make sure that the version two is stored in the database. Although if you don’t change anything, that’s probably not that important. So, I mean, when you don’t change anything in the gallery, so you probably don’t have to save it. I haven’t tested that yet. I’m just wondering whether the save button just immediately marks itself as actionable, but you need to do something, whether just something behind the scenes until you don’t change any attribute it is just invisible. So that’s the only thing that….

\n\n\n\n

Birgit Pauli-Haack: Yeah. I’m glad you mentioned that because I’m going through a few tests for the gallery block just to see how it works. And that’s certainly something to test some more. All right. What’s next? We talked about this post featured image to move the width and height controls into the dimension panel.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. Although this, this sounds quite technical. I mean, because it was moved to the dimension panel, is like in a different place now, I mean the width and height is just better organized now. So there’s one important things for the themes. And the change is that when you are creating the structure for the theme, before you would use block templates and the block slash template slash parts folders for your templates and template parts, and the decision was to rename those folder, the old folders you can still use them as long as you use, like you cannot mix.

\n\n\n\n

So you cannot use the new name and old name, as long as you use the old names or new names everything should work as before. And there is, yeah, I think I see that you, I think that there is announcement post for that, that we will link in the notes and yes, so templates and parts, new names, shorter and better. And that is because there are upcoming features coming. It’ll be possible to have a folder for styles and folder for patterns, which is quite interesting, the patterns part, in my opinion that will be great. And yeah for styles, do you know what the plan is for styles? Would it be in there?

\n\n\n\n

Birgit Pauli-Haack: Well, I think it’s a separate PHP file where you register them, and then they’re also talking about variations folders. So yeah. So if you have a block that is an image block, and you want to add additional styles, like frame to it, or a different shape of it, then those don’t have to be in the functions PHP, you can create for each pattern your own file and then have them be added to the theme rendering kind of part. Yeah. So its styles, it’s variations, and it’s block patterns that get a little bit of a better folder structure like that. 

\n\n\n\n

Grzegorz Ziolkowski: Yeah. But it’s far in the future as I understand it.

\n\n\n\n

Birgit Pauli-Haack: Right. Yeah. But the only part that is now in Gutenberg is the renaming of the folders for the template parts and the templates, because you don’t need the block in front of them. Yeah. There was another change that is interesting for those who use the appearance menu, that as soon you use a block-based theme that is built for full site editing, the current theme editor, where you get access to the file system on your site will be under tools. It will not be showing up in the appearance menu. It’s not disappearing, but they decided it to hide it or move it to the tools subheader so it’s not confused with the site editor template, editor, it all looks kind of the same. Naming things is really hard. And it was always a little odd that that was actually available for a user to edit the PHP files on your site and kind of render them. If you make a mistake, you render the whole site with a white screen of death, so to speak. So hiding is probably a good, or placing that under the tools menu is probably a good decision.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. So I just wanted to also mention from the… going back to the global styles and changes apply there. So there was one thing that is quite interesting. So there was a change to the typographic panel, so it’s now better organized. So now they call it elements. So by elements, I means there’s text, but other elements can be a link. So now they are separated in a way that you can drill down into the link and see only settings related to the link, like colors, like, I mean, in this case it’s typographic.

\n\n\n\n

So you can change font size, you can change font weight, and so on. And that’s also a preparation for future changes so you will be able to register your own elements, so let’s say when you have a blog that contains a few visual parts, so that you will be able to mark that. So let’s say in the bottom, you will be able to say, I want to have special, maybe for typographic it’s not the best, but for colors there are a lot of requirements like navigation and then it can have now nested menus. So you could just start differently nested menus. And that would be like using this API. So that’s really interesting how it evolves.

\n\n\n\n

Birgit Pauli-Haack: Yeah. And looking at the PR giphy that the designers use there though it has menus and submenu, or panels and then subpanels, so if you want to change the text, you click on text and then you get an additional panel. If you want to change the link, you click on link. So a it’s a multilevel user interface now, and you need to really know where things are to actually change them. But it’s going from the top and global thing to the yeah, single element part.

\n\n\n\n

And yeah, it’s going to be really interesting to see what people do with that and how they find things. I know that the learn team, the learn.webpress.org team is already looking at creating videos for tutorials for all these features. So I hope… it’s unclear if they will make it to the release, but shortly after, definitely. Yeah. They will have something. It’s a whole new way of editing your site. So we all have to learn how to use it. And sometimes you don’t pick up on the interfaces intuitively unless somebody points you to, well, what was the thinking behind it, you know? So. Yeah, so what else?

\n\n\n\n

Grzegorz Ziolkowski: Yeah. It’s also so powerful that the organization for that needs to be really, really complex, but it’s like as long as you use good workflows that are the same for every block, it’s something that you should learn quite quickly.

\n\n\n\n

Birgit Pauli-Haack: Yeah. Consistency is definitely key for that. Yes. We talked about things, bug fixes, there are plenty of navigation block bug fixes and also for the gallery block that came out of the testing but nothing really major.

\n\n\n\n

Grzegorz Ziolkowski: Yeah it’s quite expected because the navigation block is the biggest feature that is in there that was also iterated for two years. And yes, it should be in very good shape now. So I think it’s fine to have those bug fixes because it improves the experience further.

\n\n\n\n

Birgit Pauli-Haack: Yeah, yeah, absolutely. Yeah. So there’s one change in the components bug fixes that daytime picker is now setting PM hours correctly. I don’t know what was wrong with it, but it sounds like times are really hard.

\n\n\n\n

Grzegorz Ziolkowski: No, that one is really annoying. I think two weeks ago I ran into this issue that I wanted to post something in the afternoon, but it was published in the future, set in a few days in the morning because it wasn’t working correctly. So that’s a very important feature. So I’m glad that is fixed now.

\n\n\n\n

Birgit Pauli-Haack: Yeah. Announcement. Now you don’t have to double check your times on the publishing things. 

\n\n\n\n

Experiments

\n\n\n\n

Yeah. And after, aside from that, there is under experiments, we find an experimental confirm dialogue. Did you see what that was about?

\n\n\n\n

Grzegorz Ziolkowski: Yeah, because the browser, I mean, it’s mostly from as far as I understand that they want to remove the confirm function. That is the one that blocks you, that shows you a big popup. You need to click yes or no. It’s like the one that comes from the browser that doesn’t look good. And I guess that is one of the reasons why they want to remove that and there’s ongoing work to prepare a replacement for that. I’m not quite sure if that’s going to work in exactly the same way, because the good part about this confirm dialogue is then when you have unsafe changes in your editor, when you try to close the tab, it will just prevent that and ask you whether, are you sure that you want to continue, and I hope that this is going to be possible to replicate that using Java script. So let’s see how it goes.

\n\n\n\n

Documentation

\n\n\n\n

Birgit Pauli-Haack: Yeah. Yeah, I understand. Cool. And then we come to the documentation piece, documentation PRs that are in Gutenberg 12.1. And there’s some information about the block gap to theme.json and there have been improvements to the greater block tutorial in the handbook. Well, the developers responsible for the documentation also alphabetized the how to guides section, which is probably an improvement. So you can find things. And then that’s pretty much, oh, for the tools panel it’s updated the panel and read me and the stories all have been updated. And there’s also updated documentation for the pattern block category.

\n\n\n\n

Grzegorz Ziolkowski: I see that there are also changes to the history page. Interesting. Just there is just a news section explaining what it is about. But yeah, if you want to check something the block at your handbook, the history page, that could be interesting to learn about inspiration and like some world post explaining the block editor, and you can learn how far it’ll….

\n\n\n\n

Birgit Pauli-Haack: Yeah. It was interesting. We had a discussion when we were at the theme meetup that the interest in the block editor comes in waves. Yeah. And I’m thinking now we are in the fourth waves of having new people coming into the block editor for the first time. And it’s hard for those of us who have been with it for four years to kind of go back in three years and kind of think, okay, what was published back then that would help anybody now three years later to get started with a block editor? And it’s quite an quite a hard thing to solve when you have been so far ahead of those who are just coming in, to kind of think back into the shoes of someone who experienced the block editor for the first time. So yeah. Having a history where people can go back to read those posts is really good and helpful. See anything else that you want to talk about?

\n\n\n\n

Code Quality

\n\n\n\n

Grzegorz Ziolkowski: Yeah. There’s also got quality section as usual, but that are some minor changes. I think the biggest change is the reorganization in how the PHP files are structured. So there’s an ongoing effort to move some of the functions to folders that are related to the WordPress major version, because we have so many features that we still support for WordPress 5.8, 5.7, and it becomes a pain to make sure that the same features work in older version, even though the code is not in WordPress core, but yes, that helps a lot. And that help also to catch a few smaller bugs that some features weren’t fully backboarded to work with 5.9 release. So I hope that this will prevent some surprises.

\n\n\n\n

Birgit Pauli-Haack: All right, well, and this concludes our Gutenberg Changelog, going through the Gutenberg plugin release. 

\n\n\n\n

What’s in Active Development or Discussed

\n\n\n\n

There are a few things I wanted to point out in the active development or what’s discussed. There is the Gutenberg, the themes team on WordPress, they actually, every Friday they publish a weekly roundup of theme-related discussions. And this week they published the 75th weekly roundup edition. So if you haven’t followed up on that or followed that particular way, Jeff Ong and and Jason Chris picked four topics to highlight in the post.

\n\n\n\n

And so one was the new color picker that’s coming to Gutenberg. And then the online discussion on how best to add global padding and still allow for full width alignment. There are some ideas that are tested and in the post you find the links to the GitHub issues about that. And also how make the WP block style support available through the theme.JSON, to opt in instead of the functions PHP support, and then contrary to other styling, it seems that global link styles override block level styles.

\n\n\n\n

So they try to find a solution for that as well. And as always the weekly roundup has a list of overview issues for various features that are in the works like the typography tools, the global styles interface, and the default theme, for instance. And then it ends with a general resource section with links to documentation and tutorials. So if you are a theme developer and you want to keep up with the Gutenberg development and the discussions around it, signing up for the theme team make blog would definitely keep you in the loop on that. And of course we have the link in the show notes.

\n\n\n\n

So before we leave, I want to point out that the Twitter bot is called good first bugs, which is maintained by Ryan Welcher and it has been updated. And now you can follow along as it tweets out all the GitHub issues that are labeled good first bugs. And for the Gutenberg group, as well as for the tags in the WordPress track. So if you are ready to contribute to Gutenberg and don’t know where to start, follow that Twitter handle @goodfirstbugs and it tweets out, yeah, I don’t know how often, but several times a day, the links to those issues that are good first bugs to tackle.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. I’m seeing those tweets from time to time. I don’t follow the account, but it looks like it’s popular because Twitter somehow is deciding to show it. So yes, it’s a definitely very good way to identify some areas where you could contribute.

\n\n\n\n

Birgit Pauli-Haack: Yeah. Of course there is a label on GitHub, so we can also share the link to the label. There’s also a good first review label, if you want to review some code, that you can do that too. You could learn a lot by reviewing somebody else’s code. And have a discussion with the developer around it. Yeah. All right. So this is the end of our show today. Let me wish you or us wish you wonderful holidays when you celebrate that and a wonderful new year. Prosperity and health to everyone. Yeah.

\n\n\n\n

Grzegorz Ziolkowski: Yeah. I also wanted to wish everyone happy new year and happy release in January and all the best, by using a full site editing experience in 2022 on your WordPress websites.

\n\n\n\n

Birgit Pauli-Haack: Yes. Yeah. That’s the big feature for 2022. Yes. So as always, the show notes will be published on guttenbergtimes.com/podcast. This is the 57th episode. And if you have question suggestions, or news you want us to include, send them to changelog@guttenbergtimes.com that’s changelog@guttenbergtimes.com. That’s an email address. You could also reach out on Twitter, and the links to that are in the show notes. My Twitter handle is @BPH, like my initials, on Twitter. And what’s your handle?

\n\n\n\n

Grzegorz Ziolkowski: My handle is G-Z-I-O-L-O so if you miss us, because we don’t record in two weeks, you can just hang out with us on Twitter.

\n\n\n\n

Birgit Pauli-Haack: Yes.

\n\n\n\n

Grzegorz Ziolkowski: Or on GitHub, or WordPress Slack.

\n\n\n\n

Birgit Pauli-Haack: Yeah. WordPress Slack, definitely. And my DMs are open. Feel free to contact me. I might not respond right away, but asynchronous, is it. All right. That’s it for the year 2021. I can’t believe it’s over. It’s not, yeah. It’s still three weeks, but yeah, it’s been a great experience. Well, thanks for listening and goodbye.

\n\n\n\n

Grzegorz Ziolkowski: Thank you everyone. Goodbye.

\";s: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, 11 Dec 2021 22:44:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: 10up Releases the Publisher Media Kit WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=126899\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:173:\"https://wptavern.com/10up-releases-the-publisher-media-kit-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=10up-releases-the-publisher-media-kit-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3381:\"

Earlier today, version 1.0 of 10up’s Publisher Media Kit went live in the WordPress plugin directory. It is a preconfigured set of blocks and patterns for jump-starting a media kit page for small and medium-sized publications.

\n\n\n\n

When I first noticed the plugin, my mind immediately jumped to press kits and branding pages for businesses. Not enough companies within the WordPress space have such pages, and it can often be hard for journalists and other writers to find information. While this plugin is geared toward publications, small businesses can still get some use out of the plugin with a few changes.

\n\n\n\n

Given that WP Tavern just launched its new design yesterday, this might be an opportunity for us to lead the way. The plugin does give me a few ideas on what we could do with a similar page here on the site.

\n\n\n\n

Publisher Media Kit has been tested with Twenty Twenty-One, Newspack, and several Newspack child themes. I did run it through most of those to check for compatibility, and the plugin worked admirably. However, I primarily tested it with Twenty Twenty-Two, the upcoming default WordPress theme. Aside from a few layout alignment quirks, it worked well.

\n\n\n\n

The plugin automatically creates a new “Media Kit” draft page on the website once it is activated. The content is a set of pre-defined sections built from eight patterns and an accompanying Tabs block.

\n\n\n\nPartial screenshot of Media Kit page.\n\n\n\n

This allows users to quickly fill in their own content and make customizations. Once done, it is just a matter of hitting the publish button.

\n\n\n\n

However, end-users can take things into their own hands by using the various patterns on any post or page of their site. The cover, stats, and questions/contact patterns work well as general-use patterns.

\n\n\n\nThe plugin’s custom block patterns.\n\n\n\n

Note: I deleted a couple of the patterns from the screenshot above. For some reason, they were rendered invalid in the patterns explorer but worked fine when inserted into the content canvas.

\n\n\n\n

I would love to see a standalone version of the Tabs block included with the plugin. It is showcased in the rates and digital ad specs patterns, but it is so easy to create new tabbed content that I cannot help but want to use it with other projects.

\n\n\n\nTabs block in the editor.\n\n\n\n

It could become a popular tabs solution with a few design options like colors, borders, and typography. It is minimal at the moment, but its user experience would make for an ideal foundation for a single-block plugin.

\n\n\n\n

One of my favorite things about the block system is that it makes plugins like Publisher Media Kit feasible. In the past, it was virtually impossible to ship a content-focused plugin and expect it to work with most themes, at least not without a lot of custom design work. That meant that solid solutions would often stay in-house with agencies with no ideal way of shipping them.

\n\n\n\n

The standardization of blocks has bridged much of that gap. As the system continues evolving, especially with more design options, I expect to see similar plugins in the future.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 11 Dec 2021 01:23: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:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"Matt: State of the Word… in person!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=55181\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"https://ma.tt/2021/12/state-of-the-word-in-person/\";s: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:1629:\"

Update: Here’s the recording!

\n\n\n\n
\n\n
\n\n\n\n

I’m very excited that we’ll be broadcasting the State of the Word “live from New York City” this coming Tuesday, December 14th! There will be a very small “studio audience” of community members there in person.

\n\n\n\n

Recording the solo version last year was actually one of the hardest things I’ve done in a long time. It’s funny, with a live audience I can comfortably present for an hour no problem, but recording that 25 minute presentation, alone in a room staring at a camera, was an excruciating process over two days and dozens of takes. I got the advice afterward that even if you’re just staring into a camera, it can be helpful to have an “audience” of a few friends in the room.

\n\n\n\n

Even more than that, though, I’m positively giddy to see some of my friends from the WordPress community in person for the first time in several years. Please join via streaming on the 14th, and also there will also be at least 20 watch parties around the globe if there’s one in your neighborhood. Looking forward to catching up, celebrating the community’s accomplishments over the last year, and hopefully raising a torch for our march toward freedom on the web in 2022.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Dec 2021 23:08:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:45;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"WPTavern: More than 200 Local Newspaper Publishers Are Suing Google and Facebook for Damages\";s:7:\"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=126851\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:229:\"https://wptavern.com/more-than-200-local-newspaper-publishers-are-suing-google-and-facebook-for-damages?utm_source=rss&utm_medium=rss&utm_campaign=more-than-200-local-newspaper-publishers-are-suing-google-and-facebook-for-damages\";s: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:4058:\"

A group of 30 companies that own more than 200 local newspapers have formed a coalition against Google and Facebook in a newly consolidated antitrust lawsuit, alleging the tech giants have manipulated the digital ad market to the detriment of local news.

\n\n\n\n

The Charleston Gazette-Mail, a small West Virginia newspaper, was the first to file suit in January 2021. Doug Reynolds, managing partner at the holding company that owns several West Virginia newspapers, gave an interview to the Wall Street Journal, comparing Google and Facebook to last century’s robber barons.

\n\n\n\n

“These companies are more powerful than Standard Oil in its heyday, so no one wants to be the first to take them on,” Reynolds said. “We felt the political and legal climate have moved in our favor and are ready to go ahead.”

\n\n\n\n

In May, the News Media Alliance successfully filed a declaration to consolidate the newspapers’ cases and they were consolidated by a judicial panel shortly after that in the Southern District of New York.

\n\n\n\n

Clayton Fitzsimmons, one of the attorneys representing the plaintiffs, told Axios their objective is “to recover past damages to newspapers” and
to “establish a new system going forward in which newspapers aren’t just competitive again, but can thrive.”

\n\n\n\n

The newspapers’ collective suit echoes many of the same allegations of the antitrust suit filed against Google by Texas Attorney General Ken Paxton and nine other state attorneys general. They make a strong case for the myriad of ways that Google and Facebook have had a damaging impact on the publishing industry.

\n\n\n\n

The recently unredacted complaint references internal Google documents which show that AMP pages brought 40% less revenue to publishers. The documents show that Google acknowledged that its fees are very high but the company can demand them because of its market power. One Google employee explained that “smaller publishers don’t have alternative revenue sources,” when commenting on the lack competing ad networks. The suit also alleges that Facebook and Google colluded to manipulate header bidding auctions, among many other anticompetitive practices.

\n\n\n\n

Many of the small newspapers among the 200+ included in the consolidated antitrust lawsuit are using WordPress, such as the Brown County Democrat, The Delaware Gazette, Wisconsin Rapids City Times, Waupaca County News, and the Fairborn Daily Herald — to name just a few. They are doing important work, keeping their elected officials accountable and their communities informed.

\n\n\n\n

As the slow death of the American newspaper forced more publications to go online-only, digital advertising was the only lifeline for these outlets. The effects of collusion and manipulation of the digital ad market fall heavy on the already beleaguered local news industry.

\n\n\n\n

The consolidated cases are currently pending and could go a number of different ways. Fitzsimmons said the court could select some as bellwethers, opt to test all cases for the individual claims, or send them back to the states of origination to be tried.

\";s: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, 10 Dec 2021 22:37:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WordCamp Central: WordCamp Sevilla 2021 in-person! Last Tickets!\";s:7:\"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=3143567\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://central.wordcamp.org/news/2021/12/10/wordcamp-sevilla-2021-in-person-last-tickets/\";s: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:2437:\"

Only 2 days left for the first in-person WordCamp after pandemia!

\n

\"\"

\n

At WordPress Sevilla, we have put hands-on work to get back together and fill the space and distance that has left us this big parenthesis opened by the pandemic.

\n

On next December 11 and 12, the WordPress Sevilla community invites you to participate in the first in-person WordCamp, an event to meet again.

\n

Requirements to attend

\n

To attend WordCamp Sevilla 2021, you must meet at least one of the following requirements:

\n
    \n
  •  have a complete vaccination schedule,
    • \n
  •  have a recent negative PCR,
    • \n
  •  or having passed the COVID-19 less than 3 months ago.
    • \n
\n

The program

\n

On this occasion, our program is designed to take a look at the community’s past, to see how this time of pandemic has affected us, and how we have adapted to this new future.

\n

We will discuss in an informal way, giving the word to anyone who, from their experience, wants to contribute new ideas for the relations, meetings, and spread of WordPress and its community.

\n

\"\"

\n

But the highlight of this first in-person event is the special Community Day that we have prepared for Sunday, December 12. The details are yet to be defined, but if I were you, I wouldn’t miss it!

\n

Your ticket

\n

\"\"

\n

 For only 18 €, you will enjoy:

\n
    \n
  • Breakfast, lunch, and even dinner.
    • \n
  • Live an authentic after-party.
    • \n
  • Great gifts.
    • \n
  • And the human and professional warmth from the members of one of the best technological communities.
    • \n
\n

BUY YOUR TICKET

\n

Welcome to the first in-person WordCamp since the beginning of this pandemic!

\";s: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, 10 Dec 2021 08:51:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Ana Gavilán\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"Post Status: Post Status Excerpt (No. 36) — Help Needed: WordPress Docs 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:31:\"https://poststatus.com/?p=90881\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/excerpt/36/\";s: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:3991:\"

“The best documentation is written by people who are using it.” —Milana Cap

\n\n\n\n

In this episode of Post Status Excerpt, Milana Cap tells David about the stark reality of the near-overwhelming workload facing the WordPress Documentation Team. Currently, about four sponsored volunteers and fewer than 10 volunteers in total make up the Docs team — a team that is assigned to manage documentation for software that powers over 43% of the web. If you have ever complained about outdated documentation or a lack of documentation for WordPress, listen to this episode.

\n\n\n\n

Also: Milana shared some encouraging projects and efforts — much of which is recent and associated with the upcoming WordPress 5.9 release. Writers “shadowing” developers could be one of the keys to improving the quantity and quality of documentation in the future.

\n\n\n\n\n\n\n\n

Every week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash. \"⚡\"

You can listen to past episodes of The Excerpt, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS. \"🎧\"

\n\n\n\n

\"🔗\" Mentioned in the show:

\n\n\n\n\n\n\n\n

\"🙏\" Sponsor: Wordfence

\n\n\n\n

Who can afford downtime, a black mark on their brand’s reputation, or the SEO impact of getting hacked? That’s why so many WordPress sites rely on the real-time protection provided by Wordfence Premium. Now, Wordfence Central offers Premium subscribers a powerful and efficient dashboard to manage security for all their sites from one central location. Try Wordfence today!

\";s: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, 10 Dec 2021 07:00:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"WPTavern: WP Tavern Is Sporting a New Website Design\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=126832\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:149:\"https://wptavern.com/wp-tavern-is-sporting-a-new-website-design?utm_source=rss&utm_medium=rss&utm_campaign=wp-tavern-is-sporting-a-new-website-design\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5761:\"

We are back with a brand-new edition of WP Tavern. Technically, we have a spiffy new coat of paint that I hope you all can see if viewing from your browsers. If you are reading this post via a feed reader, email, or something else, hop over to the site and check it out.

\n\n\n\n

The Tavern received a few updates under the hood too. I will not go into those details, but some of you may have noticed that we are now hosted on Pressable, a hosting service owned by Automattic. Thus far, things seem to be going off without a hitch.

\n\n\n\n

For posterity, the following is a screenshot of the old homepage design along with the new one:

\n\n\n\n\n\n\n\n\n\nOld Tavern design vs. new design.\n\n\n\n

This is as much your home as it is ours. We just write the articles, but you are the ones who spend time browsing the front end — actually using the website. Constructive feedback is always valued and taken into account.

\n\n\n\n

A Yearlong Design Project

\n\n\n\n

It is hard to imagine the last time WP Tavern was not running a WordPress theme that I built. Before joining the staff here in 2019, the website had almost always had a little piece of me tucked in.

\n\n\n\n

I would have to dig back into the archives, but I know for sure it used to run a modified version of the Hybrid News theme I released in 2009 and eventually a custom child theme on top of Stargazer years later.

\n\n\n\n

I created our last theme in the middle of the early block editor days, and the changes over the past two years have been like running a stress test against my skills as a developer and designer. For the most part, it held up well as we ran the latest version of the Gutenberg plugin in production. I had to fix a ton of few things here and there, but I am happy to say that the site kept chugging along.

\n\n\n\n

Our last theme was aging, though, and we needed to freshen up the place. We had ideas dating back to late 2019 that we had not implemented, and it is always tough to squeeze in the time for a full-blown redesign when there is so much going on in the WordPress world. Our first priority is always sharing the news.

\n\n\n\n

We were fortunate that the WordPress.com Special Projects team contacted us in November 2020 with a proposal. Their mission:

\n\n\n\n

We help interesting people, organizations, and projects to have an excellent experience with WordPress.

\n\n\n\n

It did not begin as a new site design project. The team had actually reached out about building a feature that I would like to bring back to the Tavern. That part of the project is not quite ready yet, so we will hold it as a surprise for the new year. Folks are gearing up for the holiday season, and there is no reason to rush it.

\n\n\n\n

Our team had planned on redesigning the site ourselves. We were just waiting for Full Site Editing to launch alongside WordPress 5.7 — so, that did not happen at all.

\n\n\n\n

After some back-and-forth, a group call, and a leap forward to January 2021, we were looking at design tiles. Our plans had changed. And that is part of the magical process of keeping communication open. When you surround yourself with smart people who excel at their jobs, you can end walking a path far better than the one you first set foot on.

\n\n\n\n

Let us fast forward beyond logo decisions, design mockups, and the constant FSE changes throughout 2021. It was a long journey, but we finally arrived at our destination of a new and improved version of WP Tavern.

\n\n\n\n

From the Tavern to the WordPress.com Special Projects team: thank you for your work and professionalism throughout this entire process.

\n\n\n\n

From the Outside Looking In

\n\n\n\n

Admittedly, I had reservations about the project from the beginning. I look at other developers’ code almost every day, and I usually prefer to do my own thing. It is one of the reasons I never took any of the dozens upon dozens of agency job offers over the years. I would be that one employee who would want to uproot everything on Day #1. By the end of the first couple of weeks, I would be “let go,” my employee file labeled with “does not work well with others.”

\n\n\n\n

The team provided me with committer access to our development repo and used my preferred commands for the build process. It was a welcome gesture, and I was happy to know that I could change anything I needed.

\n\n\n\n

But, I have not once used any of the power at my disposal.

\n\n\n\n

I was comfortable feeling like we were in a partnership. Plus, every ticket I opened in the repository was handled — and I absolutely opened plenty of issues.

\n\n\n\n

Relinquishing development control was a weight off of my shoulders. I quickly learned that this was a team of professionals who knew what they were doing.

\n\n\n\n

Sure, there were some things I would have done differently with the code, such as modernizing some of the PHP (something that was unnecessary in the context of the project). I would have probably reorganized a few folders too. At the same time, this was an opportunity for me to learn, and I absorbed as much as I could.

\n\n\n\n

Aside from wearing my student hat, I also kept my client cap on. This was the first time I had ever gotten to play that role. There were moments where I worried whether everything would work out as I scanned an unfinished project. However, most of the time, I was able to sit back and watch in awe as the team put this whole thing together.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 09 Dec 2021 22:59:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"Gary: WordPress and web3\";s:7:\"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=5539\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://pento.net/2021/12/10/wordpress-and-web3/\";s: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:20381:\"

Blockchain. Cryptocurrency. Ethereum. NFTs. DAOs. Smart Contracts. web3. It’s impossible to avoid the blockchain hype machine these days, but it’s often just as difficult to decipher what it all means.

\n\n\n\n

On top of that, discourse around web3 is extremely polarising: everyone involved is very keen to a) pick a team, and b) get you to join their team. If you haven’t picked a team, you must be secretly with the other team.

\n\n\n\n

Max Read made a compelling argument that the web3 debate is in fact two different debates:

\n\n\n\n

But, OK, what is the root disagreement, exactly? The way I read it there are two broad “is web3 bullshit?” debates, not just one, centered around the following questions:

Can the blockchain do anything that other currently existing technology cannot do and/or do anything better or more efficiently than other currently existing technology?

Will the blockchain form the architecture of the internet of the future (i.e. “web3”), and/or will blockchain-native companies and organizations become important and powerful?

Max Read — Is web3 bullshit?
\n\n\n\n

I’m inclined to agree with Max’s analysis here: there’s a technical question, and there’s a business/cultural question. It’s hard to separate the two when every day sees new headlines about millions of dollars being stolen or scammed; or thousands of people putting millions of dollars into highly optimistic ventures. There are extreme positives and extreme negatives happening all the time in the web3 world.

\n\n\n\n

With that in mind, I want to take a step back from the day-to-day excitement of cryptocurrency and web3, and look at some of the driving philosophies espoused by the movement.

\n\n\n\n

Philosophies of web3

\n\n\n\n

There are a lot of differing viewpoints on web3, every individual has a slightly different take on it. There are three broad themes that stand out, however.

\n\n\n\n

Decentralised

\n\n\n\n

Blockchain-based technology is inherently distributed (with some esoteric caveats, but we can safely ignore them for now). In a world where the web centres around a handful of major services, where we’ve seen the harm that the likes of Facebook and YouTube can inflict on society, it’s not surprising that decentralisation would be a powerful theme drawing in anyone looking for an alternative.

\n\n\n\n

Decentralisation isn’t new to the Internet, of course: it’s right there in the name. This giant set of “interconnected networks” has been decentralised from the very beginning. It’s not perfect, of course: oppressive governments can take control of the borders of their portion of the Internet, and we’ve come to rely on a handful of web services to handle the trickier parts of using the web. But fundamentally, that decentralised architecture is still there. I can still set up a web site hosted on my home computer, which anyone in the world could access.

\n\n\n\n

I don’t do that, however, for the same reason that web3 isn’t immune from centralised services: Centralisation is convenient. Just as we have Facebook, or Google, or Amazon as giant centralised services on the current web, we can already see similar services appearing for web3. For payments, Coinbase has established itself as a hugely popular place exchange cryptocurrencies and traditional currencies. For NFTs, OpenSea is the service where you’ll find nearly every NFT collection. MetaMask keeps all of your crypto-based keys, tokens, and logins in a single “crypto wallet”.

\n\n\n\n

Centralisation is convenient.

\n\n\n\n

While web3 proponents give a lot of credence to the decentralised nature of cryptocurrency being a driver of popularity, I’m not so sure. At best, I’m inclined to think that decentralisation is table stakes these days: you can’t even get started as a global movement without a strong commitment to decentralisation.

\n\n\n\n

But if decentralisation isn’t the key, what is?

\n\n\n\n

Ownership

\n\n\n\n

When we talk about ownership in web3, NFTs are clearly the flavour of the month, but recent research indicates that the entire NFT market is massively artificially inflated.

\n\n\n\n
\n

Analysis of 6.1 million trades of 4.7 million NFTs shows that the top 10% of traders have traded 97% of NFTs which definitely puts meat on the bones of the hypothesis that a lot of NFT trades are wash sales intended to artificially boost prices. https://t.co/ufgmhE2iBi

— Dare Obasanjo (@Carnage4Life) November 30, 2021
\n
\n\n\n\n

Rather than taking pot-shots at the NFT straw man, I think it’s more interesting to look at the idea of ownership in terms of attribution. The more powerful element of this philosophy isn’t about who owns something, it’s who created it. NFTs do something rather novel with attribution, allowing royalty payments to the original artist every time an NFT is resold. I love this aspect: royalties shouldn’t just be for movie stars, they should be for everyone.

\n\n\n\n

Comparing that to the current web, take the 3 paragraphs written by Max Read that I quoted above. I was certainly under no technical obligation to show that it was a quote, to attribute it to him, or to link to the source. In fact, it would have been easier for me to just paste his words into this post, and pretend they were my own. I didn’t, of course, because I feel an ethical obligation to properly attribute the quote.

\n\n\n\n

In a world where unethical actors will automatically copy/paste your content for SEO juice (indeed, I expect this blog post to show up on a bunch of these kinds of sites); where massive corporations will consume everything they can find about you, in order to advertise more effectively to you, it’s not at all surprising that people are looking for a technical solution for taking back control of their data, and for being properly attributed for their creations.

\n\n\n\n

The interesting element of this philosophy isn’t about who owns something, it’s who created it.

\n\n\n\n

That’s not to say that existing services discourage attribution: a core function of Twitter is retweets, a core function of Tumblr is reblogging. WordPress still supports trackbacks, even if many folks turn them off these days.

\n\n\n\n

These are all blunt instruments, though, aimed at attributing an entire piece, rather than a more targeted approach. What I’d really like is a way to easily quote and attribute a small chunk of a post: 3 paragraphs (or blocks, if you want to see where I’m heading \"😉\"), inserted into my post, linking back to where I got them from. If someone chooses to quote some of this post, I’d love to receive a pingback just for that quote, so it can be seen in the right context.

\n\n\n\n

The functionality provide by Twitter and Tumblr is less of a technologically-based enforcement of attribution, and more of an example of paving the cow path: by and large, people want to properly attribute others, providing the tools to do so can easily become a fundamental part of how any software is used.

\n\n\n\n

These tools only work so long as there’s an incentive to use them, however. web3 certainly provides the tools to attribute others, but much like SEO scammers copy/pasting blog posts, the economics of the NFT bubble is clearly a huge incentive to ignore those tools and ethical obligations, to the point that existing services have had to build additional features just to detect this abuse.

\n\n\n\n
\n
Digital Bandits: The New Art Thieves Selling Stolen Works As NFTs
\n
\n\n\n\n

Monetisation

\n\n\n\n

With every major blockchain also being a cryptocurrency, monetisation is at the heart of the entire web3 movement. Every level of the web3 tech stack involves a cryptocurrency-based protocol. This naturally permeates through the entire web3 ecosystem, where money becomes a major driving factor for every web3-based project.

\n\n\n\n

And so, it’s impossible to look at web3 applications without also considering the financial aspect. When you have to pay just to participate, you have to ask whether every piece of content you create is “worth it”.

\n\n\n\n

Again, let’s go back to the 3 paragraphs I quote above. In a theoretical web3 world, I’d publish this post on a blockchain in some form or another, and that act would also likely include noting that I’d quoted 3 blocks of text attributed to Max Read. I’d potentially pay some amount of money to Max, along with the fees that every blockchain charges in order to perform a transaction. While this process is potentially helpful to the original author at a first glance, I suspect the second and third order effects will be problematic. Having only just clicked the Publish button a few seconds earlier, I’m already some indeterminate amount of money out of pocket. Which brings me back to the question, is this post “worth it”? Will enough people tip/quote/remix/whatever me, to cover the cost of publishing? When every creative work must be viewed through a lens of financial impact, it fundamentally alters that creative process.

\n\n\n\n

When you have to pay just to participate, you have to ask whether every piece of content you create is “worth it”.

\n\n\n\n

Ultimately, we live in a capitalist society, and everyone deserves the opportunity to profit off their work. But by baking monetisation into the underlying infrastructure of web3, it becomes impossible to opt-out. You either have the money to participate without being concerned about the cost, or you’re going to need to weigh up every interaction by whether or not you can afford it.

\n\n\n\n

Web3 Philosophies in WordPress

\n\n\n\n

After breaking it all down, we can see that it’s not all black-and-white. There are some positive parts of web3, and some negative parts. Not that different to the web of today, in fact. \"🙂\" That’s not to say that either approach is the correct one: instead, we should be looking to learn from both, and produce something better.

\n\n\n\n

Decentralised

\n\n\n\n

I’ve long been a proponent of leveraging the massive install base of WordPress to provide distributed services to anyone. Years ago, I spoke about an idea called “Connected WordPress” that would do exactly that. While the idea didn’t gain a huge amount of traction at the time, the DNA of the Connected WordPress concept shares a lot of similar traits to the decentralised nature of web3.

\n\n\n\n

I’m a big fan of decentralised technologies as a way for individuals to claw back power over their own data from the governments and massive corporations that would prefer to keep it all centralised, and I absolutely think we should be exploring ways to make the existing web more resistant to censorship.

\n\n\n\n

At the same time, we have to acknowledge that there are certainly benefits to centralisation. As long as people have the freedom to choose how and where they participate, and centralised services are required to play nicely with self hosted sites, is there a practical difference?

\n\n\n\n

I quite like how Solid allows you have it both ways, whilst maintaining control over your own data.

\n\n\n\n

Ownership Attribution

\n\n\n\n

Here’s the thing about attribution: you can’t enforce it with technology alone. Snapchat have indirectly demonstrated exactly this problem: in order to not lose a message, people would screenshot or record the message on their phone. In response, Snapchat implemented a feature to notify the other party when you screenshot a message from them. To avoid this, people will now use a second phone to take a photo or video of the message. While this example isn’t specifically about attribution, it demonstrates the problem that there’s no way to technologically restrict how someone interacts with content that you’ve published, once they’ve been granted access.

\n\n\n\n

Instead of worrying about technical restrictions, then, we should be looking at how attribution can be made easier.

\n\n\n\n

IndieWeb is a great example of how this can be done in a totally decentralised fashion.

\n\n\n\n

Monetisation

\n\n\n\n

I’m firmly of the opinion that monetisation of the things you create should be opt-in, rather than opt-out.

\n\n\n\n

Modern society is currently obsessed with monetising everything, however. It comes in many different forms: hustle culture, side gigs, transforming hobbies into businesses, meme stocks, and cryptocurrencies: they’re all symptoms of this obsession.

\n\n\n\n

I would argue that, rather than accepting as fait accompli that the next iteration of the web will be monetised to the core, we should be pushing back against this approach. Fundamentally, we should be looking to build for a post scarcity society, rather than trying to introduce scarcity where there previously was none.

\n\n\n\n

While we work towards that future, we should certainly be easier for folks to monetise their work, but the current raft of cryptocurrencies just aren’t up to the task of operating as… currencies.

\n\n\n\n

What Should You Do?

\n\n\n\n

Well, that depends on what your priorities are. The conversations around web3 are taking up a lot of air right now, so it’s possible to get the impression web3 will be imminently replacing everything. It’s important to keep perspective on this, though. While there’s a lot of money in the web3 ecosystem right now, it’s dwarfed by the sheer size of the existing web.

\n\n\n\n

If you’re excited about the hot new tech, and feeling inspired by the ideas espoused in web3 circles? Jump right in! I’m certain you’ll find something interesting to work on.

\n\n\n\n

Always wanted to get into currency speculation, but didn’t want to deal with all those pesky “regulations” and “safeguards”? Boy howdy, are cryptocurrencies or NFTs the place for you. (Please don’t pretend that this paragraph is investment advice, it is nothing of the sort.)

\n\n\n\n

Want to continue building stuff on the web, and you’re willing to learn new things when you need them, but are otherwise happy with your trajectory? Just keep on doing what you’re doing. Even if web3 does manage to live up to the hype, it’ll take a long time for it to be adopted by the mainstream. You’ll have years to adapt.

\n\n\n\n

Final Thoughts

\n\n\n\n

There are some big promises associated with web3, many of which sound very similar to the promises that were made around web 2.0, particularly around open APIs, and global interoperability. We saw what happened when those kinds of tools go wrong, and web3 doesn’t really solve those problems. It may exacerbate them in some ways, since it’s impossible to delete your data from a blockchain.

\n\n\n\n

That said, (and I say this as a WordPress Core developer), just because a particular piece of software is not the optimal technical solution doesn’t mean it won’t become the most popular. Market forces can be a far stronger factor that technical superiority. There are many legitimate complaints about blockchain (including performance, bloat, fit for purpose, and security) that have been levelled against WordPress in the past, but WordPress certainly isn’t slowing down. I’m not even close to convinced that blockchain is the right technology to base the web on, but I’ve been doing this for too long to bet everything against it.

\n\n\n\n

Markets can remain irrational a lot longer than you and I can remain solvent.

—A. Gary Shilling
\n\n\n\n

As for me, well… \"😄\"

\n\n\n\n
\n

Web3? Pass.

I’ll wait for Web 3.11 for Workgroups, thanks. pic.twitter.com/bauv3rH4bh

— Gary (@GaryPendergast) December 4, 2021
\n
\n\n\n\n

I remain sceptical of web3 as it’s currently defined, but I think there’s room to change it, and to adopt the best bits into the existing web. Web 1.0 didn’t magically disappear when Web 2.0 rolled in, it adapted. Maybe we’ll look back in 10 years and say this was a time when the web fundamentally changed. Or, maybe we’ll refer to blockchain in the same breath as pets.com, and other examples from the dotcom boom of the 1990’s.

\n\n\n\n

The Net interprets censorship as damage and routes around it.

—John Gilmore
\n\n\n\n

This quote was originally referring to Usenet, but it’s stayed highly relevant in the decades since. I think it applies here, too: if the artificial scarcity built into web3 behaves too much like censorship, preventing people from sharing what they want to share, the internet (or, more accurately, the billions of people who interact with the internet) will just… go around it. It won’t all be smooth sailing, but we’ll continue to experiment, evolve, and adapt as it changes.

\n\n\n\n

Personally, I think now is a great time for us to be embracing the values and ideals of projects like Solid, and IndieWeb. Before web3 referred to blockchains, it was more commonly used in reference to the Semantic Web, which is far more in line with WordPress’ ideals, whilst also matching many of the values prioritised by the new web3. As a major driver of the Open Web, WordPress can help people own their content in a sustainable way, engage with others on their own terms, and build communities that don’t depend on massive corporations or hand-wavy magical tech solutions.

\n\n\n\n

Don’t get too caught up in the drama of whatever is the flavour of the month. I’m optimistic about the long term resilience of the internet, and I think you should be, too. \"🥳\"

\";s: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, 09 Dec 2021 21:16:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Mon, 03 Jan 2022 21:09:41 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Mon, 03 Jan 2022 21:00:08 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:2:\"br\";}}s:5:\"build\";s:14:\"20211221224051\";}', 'no'), -(177, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1641287382', 'no'), -(178, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1641244182', 'no'), -(179, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1641287382', 'no'), -(180, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '
', 'no'), -(181, '_site_transient_timeout_available_translations', '1641254984', 'no'); -INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES -(182, '_site_transient_available_translations', 'a:127:{s:2:\"af\";a:8:{s:8:\"language\";s:2:\"af\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-05-13 15:59:22\";s:12:\"english_name\";s:9:\"Afrikaans\";s:11:\"native_name\";s:9:\"Afrikaans\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8-beta/af.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"af\";i:2;s:3:\"afr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Gaan voort\";}}s:2:\"ar\";a:8:{s:8:\"language\";s:2:\"ar\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-17 11:49:29\";s:12:\"english_name\";s:6:\"Arabic\";s:11:\"native_name\";s:14:\"العربية\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/ar.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ar\";i:2;s:3:\"ara\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"المتابعة\";}}s:3:\"ary\";a:8:{s:8:\"language\";s:3:\"ary\";s:7:\"version\";s:6:\"4.8.17\";s:7:\"updated\";s:19:\"2017-01-26 15:42:35\";s:12:\"english_name\";s:15:\"Moroccan Arabic\";s:11:\"native_name\";s:31:\"العربية المغربية\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.8.17/ary.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ar\";i:3;s:3:\"ary\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"المتابعة\";}}s:2:\"as\";a:8:{s:8:\"language\";s:2:\"as\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-08 17:57:56\";s:12:\"english_name\";s:8:\"Assamese\";s:11:\"native_name\";s:21:\"অসমীয়া\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/as.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"as\";i:2;s:3:\"asm\";i:3;s:3:\"asm\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"az\";a:8:{s:8:\"language\";s:2:\"az\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-06 00:09:27\";s:12:\"english_name\";s:11:\"Azerbaijani\";s:11:\"native_name\";s:16:\"Azərbaycan dili\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/az.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"az\";i:2;s:3:\"aze\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Davam\";}}s:3:\"azb\";a:8:{s:8:\"language\";s:3:\"azb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-12 20:34:31\";s:12:\"english_name\";s:17:\"South Azerbaijani\";s:11:\"native_name\";s:29:\"گؤنئی آذربایجان\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/azb.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"az\";i:3;s:3:\"azb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:3:\"bel\";a:8:{s:8:\"language\";s:3:\"bel\";s:7:\"version\";s:6:\"4.9.18\";s:7:\"updated\";s:19:\"2019-10-29 07:54:22\";s:12:\"english_name\";s:10:\"Belarusian\";s:11:\"native_name\";s:29:\"Беларуская мова\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.9.18/bel.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"be\";i:2;s:3:\"bel\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Працягнуць\";}}s:5:\"bg_BG\";a:8:{s:8:\"language\";s:5:\"bg_BG\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-01 15:31:45\";s:12:\"english_name\";s:9:\"Bulgarian\";s:11:\"native_name\";s:18:\"Български\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/bg_BG.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bg\";i:2;s:3:\"bul\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Напред\";}}s:5:\"bn_BD\";a:8:{s:8:\"language\";s:5:\"bn_BD\";s:7:\"version\";s:5:\"5.4.8\";s:7:\"updated\";s:19:\"2020-10-31 08:48:37\";s:12:\"english_name\";s:20:\"Bengali (Bangladesh)\";s:11:\"native_name\";s:15:\"বাংলা\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.4.8/bn_BD.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"bn\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:23:\"এগিয়ে চল.\";}}s:2:\"bo\";a:8:{s:8:\"language\";s:2:\"bo\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2020-10-30 03:24:38\";s:12:\"english_name\";s:7:\"Tibetan\";s:11:\"native_name\";s:21:\"བོད་ཡིག\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8-beta/bo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bo\";i:2;s:3:\"tib\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:33:\"མུ་མཐུད་དུ།\";}}s:5:\"bs_BA\";a:8:{s:8:\"language\";s:5:\"bs_BA\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-16 21:42:36\";s:12:\"english_name\";s:7:\"Bosnian\";s:11:\"native_name\";s:8:\"Bosanski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/bs_BA.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bs\";i:2;s:3:\"bos\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nastavi\";}}s:2:\"ca\";a:8:{s:8:\"language\";s:2:\"ca\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-15 09:50:05\";s:12:\"english_name\";s:7:\"Catalan\";s:11:\"native_name\";s:7:\"Català\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/ca.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ca\";i:2;s:3:\"cat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continua\";}}s:3:\"ceb\";a:8:{s:8:\"language\";s:3:\"ceb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-02 17:25:51\";s:12:\"english_name\";s:7:\"Cebuano\";s:11:\"native_name\";s:7:\"Cebuano\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/ceb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"ceb\";i:3;s:3:\"ceb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Padayun\";}}s:5:\"cs_CZ\";a:8:{s:8:\"language\";s:5:\"cs_CZ\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-15 22:52:34\";s:12:\"english_name\";s:5:\"Czech\";s:11:\"native_name\";s:9:\"Čeština\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/cs_CZ.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"cs\";i:2;s:3:\"ces\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:11:\"Pokračovat\";}}s:2:\"cy\";a:8:{s:8:\"language\";s:2:\"cy\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-16 20:33:10\";s:12:\"english_name\";s:5:\"Welsh\";s:11:\"native_name\";s:7:\"Cymraeg\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/cy.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"cy\";i:2;s:3:\"cym\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Parhau\";}}s:5:\"da_DK\";a:8:{s:8:\"language\";s:5:\"da_DK\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-12 13:35:53\";s:12:\"english_name\";s:6:\"Danish\";s:11:\"native_name\";s:5:\"Dansk\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/da_DK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"da\";i:2;s:3:\"dan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Fortsæt\";}}s:5:\"de_DE\";a:8:{s:8:\"language\";s:5:\"de_DE\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-13 18:06:50\";s:12:\"english_name\";s:6:\"German\";s:11:\"native_name\";s:7:\"Deutsch\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/de_DE.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:14:\"de_CH_informal\";a:8:{s:8:\"language\";s:14:\"de_CH_informal\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-07-22 10:24:47\";s:12:\"english_name\";s:30:\"German (Switzerland, Informal)\";s:11:\"native_name\";s:21:\"Deutsch (Schweiz, Du)\";s:7:\"package\";s:73:\"https://downloads.wordpress.org/translation/core/5.8.2/de_CH_informal.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:5:\"de_CH\";a:8:{s:8:\"language\";s:5:\"de_CH\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-07-22 10:24:20\";s:12:\"english_name\";s:20:\"German (Switzerland)\";s:11:\"native_name\";s:17:\"Deutsch (Schweiz)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/de_CH.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:5:\"de_AT\";a:8:{s:8:\"language\";s:5:\"de_AT\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-07-10 12:19:50\";s:12:\"english_name\";s:16:\"German (Austria)\";s:11:\"native_name\";s:21:\"Deutsch (Österreich)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/de_AT.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:12:\"de_DE_formal\";a:8:{s:8:\"language\";s:12:\"de_DE_formal\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-13 18:09:57\";s:12:\"english_name\";s:15:\"German (Formal)\";s:11:\"native_name\";s:13:\"Deutsch (Sie)\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/translation/core/5.8.2/de_DE_formal.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:3:\"dsb\";a:8:{s:8:\"language\";s:3:\"dsb\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-02 11:17:46\";s:12:\"english_name\";s:13:\"Lower Sorbian\";s:11:\"native_name\";s:16:\"Dolnoserbšćina\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.8.2/dsb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"dsb\";i:3;s:3:\"dsb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Dalej\";}}s:3:\"dzo\";a:8:{s:8:\"language\";s:3:\"dzo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-06-29 08:59:03\";s:12:\"english_name\";s:8:\"Dzongkha\";s:11:\"native_name\";s:18:\"རྫོང་ཁ\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/dzo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"dz\";i:2;s:3:\"dzo\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"el\";a:8:{s:8:\"language\";s:2:\"el\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-06 23:28:37\";s:12:\"english_name\";s:5:\"Greek\";s:11:\"native_name\";s:16:\"Ελληνικά\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/el.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"el\";i:2;s:3:\"ell\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"Συνέχεια\";}}s:5:\"en_AU\";a:8:{s:8:\"language\";s:5:\"en_AU\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-25 03:05:46\";s:12:\"english_name\";s:19:\"English (Australia)\";s:11:\"native_name\";s:19:\"English (Australia)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/en_AU.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_CA\";a:8:{s:8:\"language\";s:5:\"en_CA\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-04 18:08:37\";s:12:\"english_name\";s:16:\"English (Canada)\";s:11:\"native_name\";s:16:\"English (Canada)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/en_CA.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_NZ\";a:8:{s:8:\"language\";s:5:\"en_NZ\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-25 03:09:33\";s:12:\"english_name\";s:21:\"English (New Zealand)\";s:11:\"native_name\";s:21:\"English (New Zealand)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/en_NZ.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_ZA\";a:8:{s:8:\"language\";s:5:\"en_ZA\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-03 10:52:30\";s:12:\"english_name\";s:22:\"English (South Africa)\";s:11:\"native_name\";s:22:\"English (South Africa)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/en_ZA.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_GB\";a:8:{s:8:\"language\";s:5:\"en_GB\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-09 10:29:25\";s:12:\"english_name\";s:12:\"English (UK)\";s:11:\"native_name\";s:12:\"English (UK)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/en_GB.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"eo\";a:8:{s:8:\"language\";s:2:\"eo\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-12 16:17:36\";s:12:\"english_name\";s:9:\"Esperanto\";s:11:\"native_name\";s:9:\"Esperanto\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/eo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"eo\";i:2;s:3:\"epo\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Daŭrigi\";}}s:5:\"es_ES\";a:8:{s:8:\"language\";s:5:\"es_ES\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-06 11:31:19\";s:12:\"english_name\";s:15:\"Spanish (Spain)\";s:11:\"native_name\";s:8:\"Español\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_ES.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CR\";a:8:{s:8:\"language\";s:5:\"es_CR\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-07-30 00:35:05\";s:12:\"english_name\";s:20:\"Spanish (Costa Rica)\";s:11:\"native_name\";s:22:\"Español de Costa Rica\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_CR.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_DO\";a:8:{s:8:\"language\";s:5:\"es_DO\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-08 14:32:50\";s:12:\"english_name\";s:28:\"Spanish (Dominican Republic)\";s:11:\"native_name\";s:33:\"Español de República Dominicana\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_DO.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_PE\";a:8:{s:8:\"language\";s:5:\"es_PE\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-04 20:53:18\";s:12:\"english_name\";s:14:\"Spanish (Peru)\";s:11:\"native_name\";s:17:\"Español de Perú\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_PE.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_UY\";a:8:{s:8:\"language\";s:5:\"es_UY\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-03-31 18:33:26\";s:12:\"english_name\";s:17:\"Spanish (Uruguay)\";s:11:\"native_name\";s:19:\"Español de Uruguay\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/es_UY.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CL\";a:8:{s:8:\"language\";s:5:\"es_CL\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-06-14 16:02:22\";s:12:\"english_name\";s:15:\"Spanish (Chile)\";s:11:\"native_name\";s:17:\"Español de Chile\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/es_CL.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_PR\";a:8:{s:8:\"language\";s:5:\"es_PR\";s:7:\"version\";s:5:\"5.4.8\";s:7:\"updated\";s:19:\"2020-04-29 15:36:59\";s:12:\"english_name\";s:21:\"Spanish (Puerto Rico)\";s:11:\"native_name\";s:23:\"Español de Puerto Rico\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.4.8/es_PR.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_GT\";a:8:{s:8:\"language\";s:5:\"es_GT\";s:7:\"version\";s:6:\"5.2.13\";s:7:\"updated\";s:19:\"2019-03-02 06:35:01\";s:12:\"english_name\";s:19:\"Spanish (Guatemala)\";s:11:\"native_name\";s:21:\"Español de Guatemala\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/5.2.13/es_GT.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_AR\";a:8:{s:8:\"language\";s:5:\"es_AR\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-18 06:07:34\";s:12:\"english_name\";s:19:\"Spanish (Argentina)\";s:11:\"native_name\";s:21:\"Español de Argentina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_AR.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CO\";a:8:{s:8:\"language\";s:5:\"es_CO\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-14 13:29:01\";s:12:\"english_name\";s:18:\"Spanish (Colombia)\";s:11:\"native_name\";s:20:\"Español de Colombia\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_CO.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_VE\";a:8:{s:8:\"language\";s:5:\"es_VE\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-02 02:19:00\";s:12:\"english_name\";s:19:\"Spanish (Venezuela)\";s:11:\"native_name\";s:21:\"Español de Venezuela\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_VE.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_MX\";a:8:{s:8:\"language\";s:5:\"es_MX\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-02 13:13:00\";s:12:\"english_name\";s:16:\"Spanish (Mexico)\";s:11:\"native_name\";s:19:\"Español de México\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_MX.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_EC\";a:8:{s:8:\"language\";s:5:\"es_EC\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-02 02:19:31\";s:12:\"english_name\";s:17:\"Spanish (Ecuador)\";s:11:\"native_name\";s:19:\"Español de Ecuador\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/es_EC.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:2:\"et\";a:8:{s:8:\"language\";s:2:\"et\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2020-08-12 08:38:59\";s:12:\"english_name\";s:8:\"Estonian\";s:11:\"native_name\";s:5:\"Eesti\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8-beta/et.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"et\";i:2;s:3:\"est\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Jätka\";}}s:2:\"eu\";a:8:{s:8:\"language\";s:2:\"eu\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-11 09:49:40\";s:12:\"english_name\";s:6:\"Basque\";s:11:\"native_name\";s:7:\"Euskara\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/eu.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"eu\";i:2;s:3:\"eus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Jarraitu\";}}s:5:\"fa_AF\";a:8:{s:8:\"language\";s:5:\"fa_AF\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-20 16:34:11\";s:12:\"english_name\";s:21:\"Persian (Afghanistan)\";s:11:\"native_name\";s:31:\"(فارسی (افغانستان\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/fa_AF.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fa\";i:2;s:3:\"fas\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:5:\"fa_IR\";a:8:{s:8:\"language\";s:5:\"fa_IR\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-20 12:04:09\";s:12:\"english_name\";s:7:\"Persian\";s:11:\"native_name\";s:10:\"فارسی\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/fa_IR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fa\";i:2;s:3:\"fas\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:2:\"fi\";a:8:{s:8:\"language\";s:2:\"fi\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-17 11:15:06\";s:12:\"english_name\";s:7:\"Finnish\";s:11:\"native_name\";s:5:\"Suomi\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/fi.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fi\";i:2;s:3:\"fin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Jatka\";}}s:5:\"fr_CA\";a:8:{s:8:\"language\";s:5:\"fr_CA\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-07 15:52:29\";s:12:\"english_name\";s:15:\"French (Canada)\";s:11:\"native_name\";s:19:\"Français du Canada\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/fr_CA.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fr\";i:2;s:3:\"fra\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:5:\"fr_FR\";a:8:{s:8:\"language\";s:5:\"fr_FR\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-25 12:20:46\";s:12:\"english_name\";s:15:\"French (France)\";s:11:\"native_name\";s:9:\"Français\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/fr_FR.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"fr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:5:\"fr_BE\";a:8:{s:8:\"language\";s:5:\"fr_BE\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-02-22 13:54:46\";s:12:\"english_name\";s:16:\"French (Belgium)\";s:11:\"native_name\";s:21:\"Français de Belgique\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/fr_BE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fr\";i:2;s:3:\"fra\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:3:\"fur\";a:8:{s:8:\"language\";s:3:\"fur\";s:7:\"version\";s:6:\"4.8.17\";s:7:\"updated\";s:19:\"2018-01-29 17:32:35\";s:12:\"english_name\";s:8:\"Friulian\";s:11:\"native_name\";s:8:\"Friulian\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.8.17/fur.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"fur\";i:3;s:3:\"fur\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"gd\";a:8:{s:8:\"language\";s:2:\"gd\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-08-23 17:41:37\";s:12:\"english_name\";s:15:\"Scottish Gaelic\";s:11:\"native_name\";s:9:\"Gàidhlig\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/gd.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"gd\";i:2;s:3:\"gla\";i:3;s:3:\"gla\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"Lean air adhart\";}}s:5:\"gl_ES\";a:8:{s:8:\"language\";s:5:\"gl_ES\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-26 18:07:06\";s:12:\"english_name\";s:8:\"Galician\";s:11:\"native_name\";s:6:\"Galego\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/gl_ES.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"gl\";i:2;s:3:\"glg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:2:\"gu\";a:8:{s:8:\"language\";s:2:\"gu\";s:7:\"version\";s:6:\"4.9.18\";s:7:\"updated\";s:19:\"2018-09-14 12:33:48\";s:12:\"english_name\";s:8:\"Gujarati\";s:11:\"native_name\";s:21:\"ગુજરાતી\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.18/gu.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"gu\";i:2;s:3:\"guj\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:31:\"ચાલુ રાખવું\";}}s:3:\"haz\";a:8:{s:8:\"language\";s:3:\"haz\";s:7:\"version\";s:6:\"4.4.25\";s:7:\"updated\";s:19:\"2015-12-05 00:59:09\";s:12:\"english_name\";s:8:\"Hazaragi\";s:11:\"native_name\";s:15:\"هزاره گی\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.4.25/haz.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"haz\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:5:\"he_IL\";a:8:{s:8:\"language\";s:5:\"he_IL\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-20 10:01:27\";s:12:\"english_name\";s:6:\"Hebrew\";s:11:\"native_name\";s:16:\"עִבְרִית\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/he_IL.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"he\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"המשך\";}}s:5:\"hi_IN\";a:8:{s:8:\"language\";s:5:\"hi_IN\";s:7:\"version\";s:5:\"5.4.8\";s:7:\"updated\";s:19:\"2020-11-06 12:34:38\";s:12:\"english_name\";s:5:\"Hindi\";s:11:\"native_name\";s:18:\"हिन्दी\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.4.8/hi_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hi\";i:2;s:3:\"hin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"जारी रखें\";}}s:2:\"hr\";a:8:{s:8:\"language\";s:2:\"hr\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-15 18:51:47\";s:12:\"english_name\";s:8:\"Croatian\";s:11:\"native_name\";s:8:\"Hrvatski\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/hr.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hr\";i:2;s:3:\"hrv\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nastavi\";}}s:3:\"hsb\";a:8:{s:8:\"language\";s:3:\"hsb\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-02 11:18:08\";s:12:\"english_name\";s:13:\"Upper Sorbian\";s:11:\"native_name\";s:17:\"Hornjoserbšćina\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.8.2/hsb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"hsb\";i:3;s:3:\"hsb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:4:\"Dale\";}}s:5:\"hu_HU\";a:8:{s:8:\"language\";s:5:\"hu_HU\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-13 09:45:39\";s:12:\"english_name\";s:9:\"Hungarian\";s:11:\"native_name\";s:6:\"Magyar\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/hu_HU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hu\";i:2;s:3:\"hun\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Folytatás\";}}s:2:\"hy\";a:8:{s:8:\"language\";s:2:\"hy\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-12-03 16:21:10\";s:12:\"english_name\";s:8:\"Armenian\";s:11:\"native_name\";s:14:\"Հայերեն\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/hy.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hy\";i:2;s:3:\"hye\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Շարունակել\";}}s:5:\"id_ID\";a:8:{s:8:\"language\";s:5:\"id_ID\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-25 11:28:10\";s:12:\"english_name\";s:10:\"Indonesian\";s:11:\"native_name\";s:16:\"Bahasa Indonesia\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/id_ID.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"id\";i:2;s:3:\"ind\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Lanjutkan\";}}s:5:\"is_IS\";a:8:{s:8:\"language\";s:5:\"is_IS\";s:7:\"version\";s:6:\"4.9.18\";s:7:\"updated\";s:19:\"2018-12-11 10:40:02\";s:12:\"english_name\";s:9:\"Icelandic\";s:11:\"native_name\";s:9:\"Íslenska\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.9.18/is_IS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"is\";i:2;s:3:\"isl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Áfram\";}}s:5:\"it_IT\";a:8:{s:8:\"language\";s:5:\"it_IT\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-14 16:49:52\";s:12:\"english_name\";s:7:\"Italian\";s:11:\"native_name\";s:8:\"Italiano\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/it_IT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"it\";i:2;s:3:\"ita\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continua\";}}s:2:\"ja\";a:8:{s:8:\"language\";s:2:\"ja\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-27 05:18:09\";s:12:\"english_name\";s:8:\"Japanese\";s:11:\"native_name\";s:9:\"日本語\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/ja.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"ja\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"次へ\";}}s:5:\"jv_ID\";a:8:{s:8:\"language\";s:5:\"jv_ID\";s:7:\"version\";s:6:\"4.9.18\";s:7:\"updated\";s:19:\"2019-02-16 23:58:56\";s:12:\"english_name\";s:8:\"Javanese\";s:11:\"native_name\";s:9:\"Basa Jawa\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.9.18/jv_ID.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"jv\";i:2;s:3:\"jav\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Nerusaké\";}}s:5:\"ka_GE\";a:8:{s:8:\"language\";s:5:\"ka_GE\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-21 06:43:12\";s:12:\"english_name\";s:8:\"Georgian\";s:11:\"native_name\";s:21:\"ქართული\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/ka_GE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ka\";i:2;s:3:\"kat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"გაგრძელება\";}}s:3:\"kab\";a:8:{s:8:\"language\";s:3:\"kab\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-14 17:37:38\";s:12:\"english_name\";s:6:\"Kabyle\";s:11:\"native_name\";s:9:\"Taqbaylit\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.8.2/kab.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"kab\";i:3;s:3:\"kab\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Kemmel\";}}s:2:\"kk\";a:8:{s:8:\"language\";s:2:\"kk\";s:7:\"version\";s:6:\"4.9.18\";s:7:\"updated\";s:19:\"2018-07-10 11:35:44\";s:12:\"english_name\";s:6:\"Kazakh\";s:11:\"native_name\";s:19:\"Қазақ тілі\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.18/kk.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"kk\";i:2;s:3:\"kaz\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Жалғастыру\";}}s:2:\"km\";a:8:{s:8:\"language\";s:2:\"km\";s:7:\"version\";s:6:\"5.2.13\";s:7:\"updated\";s:19:\"2019-06-10 16:18:28\";s:12:\"english_name\";s:5:\"Khmer\";s:11:\"native_name\";s:27:\"ភាសាខ្មែរ\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.2.13/km.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"km\";i:2;s:3:\"khm\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"បន្ត\";}}s:2:\"kn\";a:8:{s:8:\"language\";s:2:\"kn\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-03 06:17:02\";s:12:\"english_name\";s:7:\"Kannada\";s:11:\"native_name\";s:15:\"ಕನ್ನಡ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/kn.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"kn\";i:2;s:3:\"kan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"ಮುಂದುವರಿಸು\";}}s:5:\"ko_KR\";a:8:{s:8:\"language\";s:5:\"ko_KR\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-06 13:14:34\";s:12:\"english_name\";s:6:\"Korean\";s:11:\"native_name\";s:9:\"한국어\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/ko_KR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ko\";i:2;s:3:\"kor\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"계속\";}}s:3:\"ckb\";a:8:{s:8:\"language\";s:3:\"ckb\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-07 16:32:30\";s:12:\"english_name\";s:16:\"Kurdish (Sorani)\";s:11:\"native_name\";s:13:\"كوردی‎\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.8.2/ckb.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ku\";i:3;s:3:\"ckb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"به‌رده‌وام به‌\";}}s:2:\"lo\";a:8:{s:8:\"language\";s:2:\"lo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-12 09:59:23\";s:12:\"english_name\";s:3:\"Lao\";s:11:\"native_name\";s:21:\"ພາສາລາວ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/lo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lo\";i:2;s:3:\"lao\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"ຕໍ່​ໄປ\";}}s:5:\"lt_LT\";a:8:{s:8:\"language\";s:5:\"lt_LT\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-03-23 12:35:40\";s:12:\"english_name\";s:10:\"Lithuanian\";s:11:\"native_name\";s:15:\"Lietuvių kalba\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/lt_LT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lt\";i:2;s:3:\"lit\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Tęsti\";}}s:2:\"lv\";a:8:{s:8:\"language\";s:2:\"lv\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-17 20:04:07\";s:12:\"english_name\";s:7:\"Latvian\";s:11:\"native_name\";s:16:\"Latviešu valoda\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/lv.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lv\";i:2;s:3:\"lav\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Turpināt\";}}s:5:\"mk_MK\";a:8:{s:8:\"language\";s:5:\"mk_MK\";s:7:\"version\";s:5:\"5.4.8\";s:7:\"updated\";s:19:\"2020-07-01 09:16:57\";s:12:\"english_name\";s:10:\"Macedonian\";s:11:\"native_name\";s:31:\"Македонски јазик\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.4.8/mk_MK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mk\";i:2;s:3:\"mkd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"Продолжи\";}}s:5:\"ml_IN\";a:8:{s:8:\"language\";s:5:\"ml_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 03:43:32\";s:12:\"english_name\";s:9:\"Malayalam\";s:11:\"native_name\";s:18:\"മലയാളം\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ml_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ml\";i:2;s:3:\"mal\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"തുടരുക\";}}s:2:\"mn\";a:8:{s:8:\"language\";s:2:\"mn\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-12 07:29:35\";s:12:\"english_name\";s:9:\"Mongolian\";s:11:\"native_name\";s:12:\"Монгол\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/mn.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mn\";i:2;s:3:\"mon\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"Үргэлжлүүлэх\";}}s:2:\"mr\";a:8:{s:8:\"language\";s:2:\"mr\";s:7:\"version\";s:6:\"4.9.18\";s:7:\"updated\";s:19:\"2019-11-22 15:32:08\";s:12:\"english_name\";s:7:\"Marathi\";s:11:\"native_name\";s:15:\"मराठी\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.18/mr.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mr\";i:2;s:3:\"mar\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"सुरु ठेवा\";}}s:5:\"ms_MY\";a:8:{s:8:\"language\";s:5:\"ms_MY\";s:7:\"version\";s:6:\"4.9.18\";s:7:\"updated\";s:19:\"2018-08-31 11:57:07\";s:12:\"english_name\";s:5:\"Malay\";s:11:\"native_name\";s:13:\"Bahasa Melayu\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.9.18/ms_MY.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ms\";i:2;s:3:\"msa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Teruskan\";}}s:5:\"my_MM\";a:8:{s:8:\"language\";s:5:\"my_MM\";s:7:\"version\";s:6:\"4.2.30\";s:7:\"updated\";s:19:\"2017-12-26 11:57:10\";s:12:\"english_name\";s:17:\"Myanmar (Burmese)\";s:11:\"native_name\";s:15:\"ဗမာစာ\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.2.30/my_MM.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"my\";i:2;s:3:\"mya\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:54:\"ဆက်လက်လုပ်ဆောင်ပါ။\";}}s:5:\"nb_NO\";a:8:{s:8:\"language\";s:5:\"nb_NO\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-21 04:11:41\";s:12:\"english_name\";s:19:\"Norwegian (Bokmål)\";s:11:\"native_name\";s:13:\"Norsk bokmål\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/nb_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nb\";i:2;s:3:\"nob\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Fortsett\";}}s:5:\"ne_NP\";a:8:{s:8:\"language\";s:5:\"ne_NP\";s:7:\"version\";s:6:\"5.2.13\";s:7:\"updated\";s:19:\"2020-05-31 16:07:59\";s:12:\"english_name\";s:6:\"Nepali\";s:11:\"native_name\";s:18:\"नेपाली\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/5.2.13/ne_NP.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ne\";i:2;s:3:\"nep\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:43:\"जारी राख्नुहोस्\";}}s:12:\"nl_NL_formal\";a:8:{s:8:\"language\";s:12:\"nl_NL_formal\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-14 12:51:29\";s:12:\"english_name\";s:14:\"Dutch (Formal)\";s:11:\"native_name\";s:20:\"Nederlands (Formeel)\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/translation/core/5.8.2/nl_NL_formal.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nl_NL\";a:8:{s:8:\"language\";s:5:\"nl_NL\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-06 13:55:08\";s:12:\"english_name\";s:5:\"Dutch\";s:11:\"native_name\";s:10:\"Nederlands\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/nl_NL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nl_BE\";a:8:{s:8:\"language\";s:5:\"nl_BE\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-12 17:53:09\";s:12:\"english_name\";s:15:\"Dutch (Belgium)\";s:11:\"native_name\";s:20:\"Nederlands (België)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/nl_BE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nn_NO\";a:8:{s:8:\"language\";s:5:\"nn_NO\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-03-18 10:59:16\";s:12:\"english_name\";s:19:\"Norwegian (Nynorsk)\";s:11:\"native_name\";s:13:\"Norsk nynorsk\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/nn_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nn\";i:2;s:3:\"nno\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Hald fram\";}}s:3:\"oci\";a:8:{s:8:\"language\";s:3:\"oci\";s:7:\"version\";s:6:\"4.8.17\";s:7:\"updated\";s:19:\"2017-08-25 10:03:08\";s:12:\"english_name\";s:7:\"Occitan\";s:11:\"native_name\";s:7:\"Occitan\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.8.17/oci.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"oc\";i:2;s:3:\"oci\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Contunhar\";}}s:5:\"pa_IN\";a:8:{s:8:\"language\";s:5:\"pa_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-16 05:19:43\";s:12:\"english_name\";s:7:\"Punjabi\";s:11:\"native_name\";s:18:\"ਪੰਜਾਬੀ\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/pa_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pa\";i:2;s:3:\"pan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"ਜਾਰੀ ਰੱਖੋ\";}}s:5:\"pl_PL\";a:8:{s:8:\"language\";s:5:\"pl_PL\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-21 17:33:07\";s:12:\"english_name\";s:6:\"Polish\";s:11:\"native_name\";s:6:\"Polski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/pl_PL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pl\";i:2;s:3:\"pol\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Kontynuuj\";}}s:2:\"ps\";a:8:{s:8:\"language\";s:2:\"ps\";s:7:\"version\";s:6:\"4.3.26\";s:7:\"updated\";s:19:\"2015-12-02 21:41:29\";s:12:\"english_name\";s:6:\"Pashto\";s:11:\"native_name\";s:8:\"پښتو\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.3.26/ps.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ps\";i:2;s:3:\"pus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:19:\"دوام ورکړه\";}}s:5:\"pt_AO\";a:8:{s:8:\"language\";s:5:\"pt_AO\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-27 16:28:47\";s:12:\"english_name\";s:19:\"Portuguese (Angola)\";s:11:\"native_name\";s:20:\"Português de Angola\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/pt_AO.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:10:\"pt_PT_ao90\";a:8:{s:8:\"language\";s:10:\"pt_PT_ao90\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-09 21:40:55\";s:12:\"english_name\";s:27:\"Portuguese (Portugal, AO90)\";s:11:\"native_name\";s:17:\"Português (AO90)\";s:7:\"package\";s:69:\"https://downloads.wordpress.org/translation/core/5.8.2/pt_PT_ao90.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"pt_PT\";a:8:{s:8:\"language\";s:5:\"pt_PT\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-15 08:56:03\";s:12:\"english_name\";s:21:\"Portuguese (Portugal)\";s:11:\"native_name\";s:10:\"Português\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/pt_PT.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"pt_BR\";a:8:{s:8:\"language\";s:5:\"pt_BR\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-09-08 19:39:30\";s:12:\"english_name\";s:19:\"Portuguese (Brazil)\";s:11:\"native_name\";s:20:\"Português do Brasil\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/pt_BR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pt\";i:2;s:3:\"por\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:3:\"rhg\";a:8:{s:8:\"language\";s:3:\"rhg\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-16 13:03:18\";s:12:\"english_name\";s:8:\"Rohingya\";s:11:\"native_name\";s:8:\"Ruáinga\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/rhg.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"rhg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"ro_RO\";a:8:{s:8:\"language\";s:5:\"ro_RO\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-22 19:38:07\";s:12:\"english_name\";s:8:\"Romanian\";s:11:\"native_name\";s:8:\"Română\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/ro_RO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ro\";i:2;s:3:\"ron\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuă\";}}s:5:\"ru_RU\";a:8:{s:8:\"language\";s:5:\"ru_RU\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-16 23:35:59\";s:12:\"english_name\";s:7:\"Russian\";s:11:\"native_name\";s:14:\"Русский\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/ru_RU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ru\";i:2;s:3:\"rus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продолжить\";}}s:3:\"sah\";a:8:{s:8:\"language\";s:3:\"sah\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-21 02:06:41\";s:12:\"english_name\";s:5:\"Sakha\";s:11:\"native_name\";s:14:\"Сахалыы\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/sah.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"sah\";i:3;s:3:\"sah\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Салҕаа\";}}s:3:\"snd\";a:8:{s:8:\"language\";s:3:\"snd\";s:7:\"version\";s:5:\"5.4.8\";s:7:\"updated\";s:19:\"2020-07-07 01:53:37\";s:12:\"english_name\";s:6:\"Sindhi\";s:11:\"native_name\";s:8:\"سنڌي\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.4.8/snd.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"sd\";i:2;s:3:\"snd\";i:3;s:3:\"snd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"اڳتي هلو\";}}s:5:\"si_LK\";a:8:{s:8:\"language\";s:5:\"si_LK\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-12 06:00:52\";s:12:\"english_name\";s:7:\"Sinhala\";s:11:\"native_name\";s:15:\"සිංහල\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/si_LK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"si\";i:2;s:3:\"sin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:44:\"දිගටම කරගෙන යන්න\";}}s:5:\"sk_SK\";a:8:{s:8:\"language\";s:5:\"sk_SK\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-10 07:31:29\";s:12:\"english_name\";s:6:\"Slovak\";s:11:\"native_name\";s:11:\"Slovenčina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/sk_SK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sk\";i:2;s:3:\"slk\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Pokračovať\";}}s:3:\"skr\";a:8:{s:8:\"language\";s:3:\"skr\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-15 15:37:00\";s:12:\"english_name\";s:7:\"Saraiki\";s:11:\"native_name\";s:14:\"سرائیکی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.8.2/skr.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"skr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:17:\"جاری رکھو\";}}s:5:\"sl_SI\";a:8:{s:8:\"language\";s:5:\"sl_SI\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-23 08:11:23\";s:12:\"english_name\";s:9:\"Slovenian\";s:11:\"native_name\";s:13:\"Slovenščina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/sl_SI.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sl\";i:2;s:3:\"slv\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Nadaljuj\";}}s:2:\"sq\";a:8:{s:8:\"language\";s:2:\"sq\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-02 20:06:53\";s:12:\"english_name\";s:8:\"Albanian\";s:11:\"native_name\";s:5:\"Shqip\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/sq.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sq\";i:2;s:3:\"sqi\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Vazhdo\";}}s:5:\"sr_RS\";a:8:{s:8:\"language\";s:5:\"sr_RS\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-08-01 21:21:06\";s:12:\"english_name\";s:7:\"Serbian\";s:11:\"native_name\";s:23:\"Српски језик\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/sr_RS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sr\";i:2;s:3:\"srp\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:14:\"Настави\";}}s:5:\"sv_SE\";a:8:{s:8:\"language\";s:5:\"sv_SE\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-16 08:39:17\";s:12:\"english_name\";s:7:\"Swedish\";s:11:\"native_name\";s:7:\"Svenska\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/sv_SE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sv\";i:2;s:3:\"swe\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Fortsätt\";}}s:2:\"sw\";a:8:{s:8:\"language\";s:2:\"sw\";s:7:\"version\";s:6:\"5.3.10\";s:7:\"updated\";s:19:\"2019-10-13 15:35:35\";s:12:\"english_name\";s:7:\"Swahili\";s:11:\"native_name\";s:9:\"Kiswahili\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.3.10/sw.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sw\";i:2;s:3:\"swa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Endelea\";}}s:3:\"szl\";a:8:{s:8:\"language\";s:3:\"szl\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-24 19:58:14\";s:12:\"english_name\";s:8:\"Silesian\";s:11:\"native_name\";s:17:\"Ślōnskŏ gŏdka\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/szl.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"szl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:13:\"Kōntynuować\";}}s:5:\"ta_IN\";a:8:{s:8:\"language\";s:5:\"ta_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 03:22:47\";s:12:\"english_name\";s:5:\"Tamil\";s:11:\"native_name\";s:15:\"தமிழ்\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ta_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ta\";i:2;s:3:\"tam\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"தொடரவும்\";}}s:5:\"ta_LK\";a:8:{s:8:\"language\";s:5:\"ta_LK\";s:7:\"version\";s:6:\"4.2.30\";s:7:\"updated\";s:19:\"2015-12-03 01:07:44\";s:12:\"english_name\";s:17:\"Tamil (Sri Lanka)\";s:11:\"native_name\";s:15:\"தமிழ்\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.2.30/ta_LK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ta\";i:2;s:3:\"tam\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"தொடர்க\";}}s:2:\"te\";a:8:{s:8:\"language\";s:2:\"te\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-26 15:47:39\";s:12:\"english_name\";s:6:\"Telugu\";s:11:\"native_name\";s:18:\"తెలుగు\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/te.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"te\";i:2;s:3:\"tel\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"కొనసాగించు\";}}s:2:\"th\";a:8:{s:8:\"language\";s:2:\"th\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-12-28 02:58:38\";s:12:\"english_name\";s:4:\"Thai\";s:11:\"native_name\";s:9:\"ไทย\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/th.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"th\";i:2;s:3:\"tha\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"ต่อไป\";}}s:2:\"tl\";a:8:{s:8:\"language\";s:2:\"tl\";s:7:\"version\";s:6:\"4.8.17\";s:7:\"updated\";s:19:\"2017-09-30 09:04:29\";s:12:\"english_name\";s:7:\"Tagalog\";s:11:\"native_name\";s:7:\"Tagalog\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8.17/tl.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tl\";i:2;s:3:\"tgl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Magpatuloy\";}}s:5:\"tr_TR\";a:8:{s:8:\"language\";s:5:\"tr_TR\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-04 12:16:39\";s:12:\"english_name\";s:7:\"Turkish\";s:11:\"native_name\";s:8:\"Türkçe\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/tr_TR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tr\";i:2;s:3:\"tur\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Devam\";}}s:5:\"tt_RU\";a:8:{s:8:\"language\";s:5:\"tt_RU\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-20 20:20:50\";s:12:\"english_name\";s:5:\"Tatar\";s:11:\"native_name\";s:19:\"Татар теле\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/tt_RU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tt\";i:2;s:3:\"tat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:17:\"дәвам итү\";}}s:3:\"tah\";a:8:{s:8:\"language\";s:3:\"tah\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-06 18:39:39\";s:12:\"english_name\";s:8:\"Tahitian\";s:11:\"native_name\";s:10:\"Reo Tahiti\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/tah.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"ty\";i:2;s:3:\"tah\";i:3;s:3:\"tah\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"ug_CN\";a:8:{s:8:\"language\";s:5:\"ug_CN\";s:7:\"version\";s:6:\"4.9.18\";s:7:\"updated\";s:19:\"2021-07-03 18:41:33\";s:12:\"english_name\";s:6:\"Uighur\";s:11:\"native_name\";s:16:\"ئۇيغۇرچە\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.9.18/ug_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ug\";i:2;s:3:\"uig\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:26:\"داۋاملاشتۇرۇش\";}}s:2:\"uk\";a:8:{s:8:\"language\";s:2:\"uk\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-10-10 16:46:39\";s:12:\"english_name\";s:9:\"Ukrainian\";s:11:\"native_name\";s:20:\"Українська\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/uk.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uk\";i:2;s:3:\"ukr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продовжити\";}}s:2:\"ur\";a:8:{s:8:\"language\";s:2:\"ur\";s:7:\"version\";s:5:\"5.4.8\";s:7:\"updated\";s:19:\"2020-04-09 11:17:33\";s:12:\"english_name\";s:4:\"Urdu\";s:11:\"native_name\";s:8:\"اردو\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.4.8/ur.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ur\";i:2;s:3:\"urd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:19:\"جاری رکھیں\";}}s:5:\"uz_UZ\";a:8:{s:8:\"language\";s:5:\"uz_UZ\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-02-28 12:02:22\";s:12:\"english_name\";s:5:\"Uzbek\";s:11:\"native_name\";s:11:\"O‘zbekcha\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/uz_UZ.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uz\";i:2;s:3:\"uzb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:11:\"Davom etish\";}}s:2:\"vi\";a:8:{s:8:\"language\";s:2:\"vi\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-16 07:16:28\";s:12:\"english_name\";s:10:\"Vietnamese\";s:11:\"native_name\";s:14:\"Tiếng Việt\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.2/vi.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"vi\";i:2;s:3:\"vie\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Tiếp tục\";}}s:5:\"zh_TW\";a:8:{s:8:\"language\";s:5:\"zh_TW\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-16 00:27:59\";s:12:\"english_name\";s:16:\"Chinese (Taiwan)\";s:11:\"native_name\";s:12:\"繁體中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/zh_TW.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"繼續\";}}s:5:\"zh_CN\";a:8:{s:8:\"language\";s:5:\"zh_CN\";s:7:\"version\";s:5:\"5.8.2\";s:7:\"updated\";s:19:\"2021-11-05 11:55:27\";s:12:\"english_name\";s:15:\"Chinese (China)\";s:11:\"native_name\";s:12:\"简体中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.2/zh_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"继续\";}}s:5:\"zh_HK\";a:8:{s:8:\"language\";s:5:\"zh_HK\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-06-27 10:46:14\";s:12:\"english_name\";s:19:\"Chinese (Hong Kong)\";s:11:\"native_name\";s:16:\"香港中文版 \";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/zh_HK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"繼續\";}}}', 'no'), -(185, '_site_transient_update_core', 'O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.8.2.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.8.2.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.8.2-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.8.2-new-bundled.zip\";s:7:\"partial\";s:0:\"\";s:8:\"rollback\";s:0:\"\";}s:7:\"current\";s:5:\"5.8.2\";s:7:\"version\";s:5:\"5.8.2\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.6\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1641244203;s:15:\"version_checked\";s:5:\"5.8.2\";s:12:\"translations\";a:0:{}}', 'no'), -(186, 'widget_multiple_authors_widget', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(187, 'widget_multiple_authors_list_widget', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(188, 'publishpress-authors_wp_reviews_installed_on', '2022-01-03 22:20:23', 'yes'), -(189, 'multiple_authors_version', '3.14.9-hotfix-552.1', 'yes'), -(190, 'multiple_authors_modules_settings_options', 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), -(191, 'multiple_authors_settings_options', 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), -(192, 'multiple_authors_multiple_authors_options', 'O:8:\"stdClass\":10:{s:7:\"enabled\";s:2:\"on\";s:10:\"post_types\";a:2:{s:4:\"post\";s:2:\"on\";s:4:\"page\";s:2:\"on\";}s:17:\"append_to_content\";s:3:\"yes\";s:20:\"author_for_new_users\";a:0:{}s:6:\"layout\";s:5:\"boxed\";s:18:\"force_empty_author\";s:2:\"no\";s:24:\"username_in_search_field\";s:2:\"no\";s:28:\"default_author_for_new_posts\";N;s:22:\"author_page_post_types\";a:0:{}s:11:\"loaded_once\";b:1;}', 'yes'), -(193, 'multiple_authors_default_layouts_options', 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), -(194, 'multiple_authors_rest_api_options', 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), -(195, 'multiple_authors_pro_placeholders_options', 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), -(196, 'multiple_authors_polylang_integration_options', 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), -(197, 'multiple_authors_reviews_options', 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), -(198, 'PP_AUTHORS_VERSION', '3.14.9-hotfix-552.1', 'yes'), -(199, 'publishpress_multiple_authors_settings_migrated_3_0_0', '1', 'yes'); +INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) +VALUES (1, 'siteurl', 'https://tests.local', 'yes'), + (2, 'home', 'https://tests.local', 'yes'), + (3, 'blogname', 'Sandbox', 'yes'), + (4, 'blogdescription', 'Just another WordPress site', 'yes'), + (5, 'users_can_register', '0', 'yes'), + (6, 'admin_email', 'publishpress-dev@example.com', 'yes'), + (7, 'start_of_week', '1', 'yes'), + (8, 'use_balanceTags', '0', 'yes'), + (9, 'use_smilies', '1', 'yes'), + (10, 'require_name_email', '1', 'yes'), + (11, 'comments_notify', '1', 'yes'), + (12, 'posts_per_rss', '10', 'yes'), + (13, 'rss_use_excerpt', '0', 'yes'), + (14, 'mailserver_url', 'mail.example.com', 'yes'), + (15, 'mailserver_login', 'login@example.com', 'yes'), + (16, 'mailserver_pass', 'password', 'yes'), + (17, 'mailserver_port', '110', 'yes'), + (18, 'default_category', '1', 'yes'), + (19, 'default_comment_status', 'open', 'yes'), + (20, 'default_ping_status', 'open', 'yes'), + (21, 'default_pingback_flag', '1', 'yes'), + (22, 'posts_per_page', '10', 'yes'), + (23, 'date_format', 'F j, Y', 'yes'), + (24, 'time_format', 'g:i a', 'yes'), + (25, 'links_updated_date_format', 'F j, Y g:i a', 'yes'), + (26, 'comment_moderation', '0', 'yes'), + (27, 'moderation_notify', '1', 'yes'), + (28, 'permalink_structure', '', 'yes'), + (29, 'rewrite_rules', '', 'yes'), + (30, 'hack_file', '0', 'yes'), + (31, 'blog_charset', 'UTF-8', 'yes'), + (32, 'moderation_keys', '', 'no'), + (33, 'active_plugins', + 'a:2:{i:0;s:37:\"custom-post-type/custom-post-type.php\";i:1;s:45:\"publishpress-authors/publishpress-authors.php\";}', + 'yes'), + (34, 'category_base', '', 'yes'), + (35, 'ping_sites', 'http://rpc.pingomatic.com/', 'yes'), + (36, 'comment_max_links', '2', 'yes'), + (37, 'gmt_offset', '0', 'yes'), + (38, 'default_email_category', '1', 'yes'), + (39, 'recently_edited', '', 'no'), + (40, 'template', 'twentytwenty', 'yes'), + (41, 'stylesheet', 'twentytwenty', 'yes'), + (44, 'comment_registration', '0', 'yes'), + (45, 'html_type', 'text/html', 'yes'), + (46, 'use_trackback', '0', 'yes'), + (47, 'default_role', 'subscriber', 'yes'), + (48, 'db_version', '51917', 'yes'), + (49, 'uploads_use_yearmonth_folders', '1', 'yes'), + (50, 'upload_path', '', 'yes'), + (51, 'blog_public', '1', 'yes'), + (52, 'default_link_category', '2', 'yes'), + (53, 'show_on_front', 'posts', 'yes'), + (54, 'tag_base', '', 'yes'), + (55, 'show_avatars', '1', 'yes'), + (56, 'avatar_rating', 'G', 'yes'), + (57, 'upload_url_path', '', 'yes'), + (58, 'thumbnail_size_w', '150', 'yes'), + (59, 'thumbnail_size_h', '150', 'yes'), + (60, 'thumbnail_crop', '1', 'yes'), + (61, 'medium_size_w', '300', 'yes'), + (62, 'medium_size_h', '300', 'yes'), + (63, 'avatar_default', 'mystery', 'yes'), + (64, 'large_size_w', '1024', 'yes'), + (65, 'large_size_h', '1024', 'yes'), + (66, 'image_default_link_type', 'none', 'yes'), + (67, 'image_default_size', '', 'yes'), + (68, 'image_default_align', '', 'yes'), + (69, 'close_comments_for_old_posts', '0', 'yes'), + (70, 'close_comments_days_old', '14', 'yes'), + (71, 'thread_comments', '1', 'yes'), + (72, 'thread_comments_depth', '5', 'yes'), + (73, 'page_comments', '0', 'yes'), + (74, 'comments_per_page', '50', 'yes'), + (75, 'default_comments_page', 'newest', 'yes'), + (76, 'comment_order', 'asc', 'yes'), + (77, 'sticky_posts', 'a:0:{}', 'yes'), + (78, 'widget_categories', + 'a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}', + 'yes'), + (79, 'widget_text', 'a:0:{}', 'yes'), + (80, 'widget_rss', 'a:0:{}', 'yes'), + (81, 'uninstall_plugins', 'a:0:{}', 'no'), + (82, 'timezone_string', '', 'yes'), + (83, 'page_for_posts', '0', 'yes'), + (84, 'page_on_front', '0', 'yes'), + (85, 'default_post_format', '0', 'yes'), + (86, 'link_manager_enabled', '0', 'yes'), + (87, 'finished_splitting_shared_terms', '1', 'yes'), + (88, 'site_icon', '0', 'yes'), + (89, 'medium_large_size_w', '768', 'yes'), + (90, 'medium_large_size_h', '0', 'yes'), + (91, 'wp_page_for_privacy_policy', '3', 'yes'), + (92, 'show_comments_cookies_opt_in', '1', 'yes'), + (94, 'initial_db_version', '45805', 'yes'), + (95, 'wp_user_roles', + 'a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:63:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;s:19:\"ppma_manage_authors\";b:1;s:22:\"ppma_edit_post_authors\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:35:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:22:\"ppma_edit_post_authors\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:11:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:22:\"ppma_edit_post_authors\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:6:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"ppma_edit_post_authors\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}', + 'yes'), + (96, 'fresh_site', '0', 'yes'), + (97, 'widget_search', 'a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}', 'yes'), + (98, 'widget_recent-posts', + 'a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}', 'yes'), + (99, 'widget_recent-comments', + 'a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}', 'yes'), + (100, 'widget_archives', + 'a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}', + 'yes'), + (101, 'widget_meta', 'a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}', 'yes'), + (102, 'sidebars_widgets', + 'a:4:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:3:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";}s:9:\"sidebar-2\";a:3:{i:0;s:10:\"archives-2\";i:1;s:12:\"categories-2\";i:2;s:6:\"meta-2\";}s:13:\"array_version\";i:3;}', + 'yes'), + (103, 'cron', + 'a:6:{i:1641243686;a:6:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:18:\"wp_https_detection\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1641243688;a:1:{s:8:\"do_pings\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}}i:1641243772;a:1:{s:28:\"wp_update_comment_type_batch\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}}i:1641244170;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1641330086;a:1:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}s:7:\"version\";i:2;}', + 'yes'), + (104, 'widget_pages', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (105, 'widget_calendar', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (106, 'widget_media_audio', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (107, 'widget_media_image', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (108, 'widget_media_gallery', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (109, 'widget_media_video', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (110, 'widget_tag_cloud', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (111, 'widget_nav_menu', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (112, 'widget_custom_html', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (139, 'db_upgraded', '', 'yes'), + (142, 'recently_activated', 'a:0:{}', 'yes'), + (143, '_site_transient_update_plugins', + 'O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1641248344;s:8:\"response\";a:2:{s:45:\"publishpress-authors/publishpress-authors.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:34:\"w.org/plugins/publishpress-authors\";s:4:\"slug\";s:20:\"publishpress-authors\";s:6:\"plugin\";s:45:\"publishpress-authors/publishpress-authors.php\";s:11:\"new_version\";s:6:\"3.14.9\";s:3:\"url\";s:51:\"https://wordpress.org/plugins/publishpress-authors/\";s:7:\"package\";s:70:\"https://downloads.wordpress.org/plugin/publishpress-authors.3.14.9.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:73:\"https://ps.w.org/publishpress-authors/assets/icon-256x256.png?rev=2472504\";s:2:\"1x\";s:73:\"https://ps.w.org/publishpress-authors/assets/icon-128x128.png?rev=2472504\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:76:\"https://ps.w.org/publishpress-authors/assets/banner-1544x500.jpg?rev=2472504\";s:2:\"1x\";s:75:\"https://ps.w.org/publishpress-authors/assets/banner-772x250.jpg?rev=2472504\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.7\";s:6:\"tested\";s:5:\"5.8.2\";s:12:\"requires_php\";s:3:\"5.6\";}s:37:\"custom-post-type/custom-post-type.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:30:\"w.org/plugins/custom-post-type\";s:4:\"slug\";s:16:\"custom-post-type\";s:6:\"plugin\";s:37:\"custom-post-type/custom-post-type.php\";s:11:\"new_version\";s:3:\"1.0\";s:3:\"url\";s:47:\"https://wordpress.org/plugins/custom-post-type/\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/plugin/custom-post-type.zip\";s:5:\"icons\";a:1:{s:7:\"default\";s:60:\"https://s.w.org/plugins/geopattern-icon/custom-post-type.svg\";}s:7:\"banners\";a:0:{}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.0\";s:6:\"tested\";s:6:\"4.6.21\";s:12:\"requires_php\";b:0;}}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:2:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:5:\"4.2.1\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.2.1.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:59:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272\";s:2:\"1x\";s:59:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:61:\"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"5.0\";}s:9:\"hello.php\";O:8:\"stdClass\":10:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:5:\"1.7.2\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855\";s:2:\"1x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/hello-dolly/assets/banner-1544x500.jpg?rev=2645582\";s:2:\"1x\";s:66:\"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855\";}s:11:\"banners_rtl\";a:0:{}s:8:\"requires\";s:3:\"4.6\";}}s:7:\"checked\";a:4:{s:19:\"akismet/akismet.php\";s:5:\"4.2.1\";s:9:\"hello.php\";s:5:\"1.7.2\";s:45:\"publishpress-authors/publishpress-authors.php\";s:19:\"3.14.9-hotfix-552.1\";s:37:\"custom-post-type/custom-post-type.php\";s:5:\"0.1.0\";}}', + 'no'), + (144, '_site_transient_update_themes', + 'O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1641244202;s:7:\"checked\";a:2:{s:14:\"twentynineteen\";s:3:\"2.1\";s:15:\"twentytwentyone\";s:3:\"1.4\";}s:8:\"response\";a:0:{}s:9:\"no_update\";a:2:{s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"2.1\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.2.1.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentytwentyone\";a:6:{s:5:\"theme\";s:15:\"twentytwentyone\";s:11:\"new_version\";s:3:\"1.4\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentytwentyone/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentytwentyone.1.4.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"5.6\";}}s:12:\"translations\";a:0:{}}', + 'no'), + (147, 'widget_block', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (148, 'theme_mods_twentytwenty', 'a:1:{s:18:\"custom_css_post_id\";i:-1;}', 'yes'), + (151, 'disallowed_keys', '', 'no'), + (152, 'comment_previously_approved', '1', 'yes'), + (153, 'auto_plugin_theme_update_emails', 'a:0:{}', 'no'), + (154, 'auto_update_core_dev', 'enabled', 'yes'), + (155, 'auto_update_core_minor', 'enabled', 'yes'), + (156, 'auto_update_core_major', 'unset', 'yes'), + (157, 'wp_force_deactivated_plugins', 'a:0:{}', 'yes'), + (158, 'finished_updating_comment_type', '0', 'yes'), + (185, '_site_transient_update_core', + 'O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.8.2.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.8.2.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.8.2-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.8.2-new-bundled.zip\";s:7:\"partial\";s:0:\"\";s:8:\"rollback\";s:0:\"\";}s:7:\"current\";s:5:\"5.8.2\";s:7:\"version\";s:5:\"5.8.2\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.6\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1641244203;s:15:\"version_checked\";s:5:\"5.8.2\";s:12:\"translations\";a:0:{}}', + 'no'), + (186, 'widget_multiple_authors_widget', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (187, 'widget_multiple_authors_list_widget', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), + (188, 'publishpress-authors_wp_reviews_installed_on', '2022-01-03 22:20:23', 'yes'), + (189, 'multiple_authors_version', '3.14.9-hotfix-552.1', 'yes'), + (190, 'multiple_authors_modules_settings_options', + 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), + (191, 'multiple_authors_settings_options', + 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), + (192, 'multiple_authors_multiple_authors_options', + 'O:8:\"stdClass\":10:{s:7:\"enabled\";s:2:\"on\";s:10:\"post_types\";a:2:{s:4:\"post\";s:2:\"on\";s:4:\"page\";s:2:\"on\";}s:17:\"append_to_content\";s:3:\"yes\";s:20:\"author_for_new_users\";a:0:{}s:6:\"layout\";s:5:\"boxed\";s:18:\"force_empty_author\";s:2:\"no\";s:24:\"username_in_search_field\";s:2:\"no\";s:28:\"default_author_for_new_posts\";N;s:22:\"author_page_post_types\";a:0:{}s:11:\"loaded_once\";b:1;}', + 'yes'), + (193, 'multiple_authors_default_layouts_options', + 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), + (194, 'multiple_authors_rest_api_options', + 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), + (195, 'multiple_authors_pro_placeholders_options', + 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), + (196, 'multiple_authors_polylang_integration_options', + 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), + (197, 'multiple_authors_reviews_options', + 'O:8:\"stdClass\":2:{s:7:\"enabled\";s:2:\"on\";s:11:\"loaded_once\";b:1;}', 'yes'), + (198, 'PP_AUTHORS_VERSION', '3.14.9-hotfix-552.1', 'yes'), + (199, 'publishpress_multiple_authors_settings_migrated_3_0_0', '1', 'yes'), + (202, '_transient_doing_cron', '1648056851.0514230728149414062500', 'yes'), + (203, 'admin_email_lifespan', '1663608850', 'yes'); DROP TABLE IF EXISTS `wp_postmeta`; -CREATE TABLE `wp_postmeta` ( - `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `post_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 DEFAULT NULL, - PRIMARY KEY (`meta_id`), - KEY `post_id` (`post_id`), - KEY `meta_key` (`meta_key`(191)) -) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +CREATE TABLE `wp_postmeta` +( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `post_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 DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `post_id` (`post_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE = InnoDB + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES -(1, 2, '_wp_page_template', 'default'), -(2, 3, '_wp_page_template', 'default'), -(3, 1, 'ppma_authors_name', 'admin'), -(4, 2, 'ppma_authors_name', 'admin'), -(5, 3, 'ppma_authors_name', 'admin'), -(6, 4, 'ppma_authors_name', 'admin'); +INSERT INTO `wp_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) +VALUES (1, 2, '_wp_page_template', 'default'), + (2, 3, '_wp_page_template', 'default'), + (3, 1, 'ppma_authors_name', 'admin'), + (4, 2, 'ppma_authors_name', 'admin'), + (5, 3, 'ppma_authors_name', 'admin'), + (6, 4, 'ppma_authors_name', 'admin'); DROP TABLE IF EXISTS `wp_posts`; -CREATE TABLE `wp_posts` ( - `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `post_author` bigint(20) unsigned NOT NULL DEFAULT 0, - `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `post_content` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, - `post_title` text COLLATE utf8mb4_unicode_520_ci NOT NULL, - `post_excerpt` text COLLATE utf8mb4_unicode_520_ci NOT NULL, - `post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'publish', - `comment_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', - `ping_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', - `post_password` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `post_name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `to_ping` text COLLATE utf8mb4_unicode_520_ci NOT NULL, - `pinged` text COLLATE utf8mb4_unicode_520_ci NOT NULL, - `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `post_content_filtered` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, - `post_parent` bigint(20) unsigned NOT NULL DEFAULT 0, - `guid` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `menu_order` int(11) NOT NULL DEFAULT 0, - `post_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post', - `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `comment_count` bigint(20) NOT NULL DEFAULT 0, - PRIMARY KEY (`ID`), - KEY `post_name` (`post_name`(191)), - KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), - KEY `post_parent` (`post_parent`), - KEY `post_author` (`post_author`) -) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +CREATE TABLE `wp_posts` +( + `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `post_author` bigint(20) unsigned NOT NULL DEFAULT 0, + `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `post_content` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, + `post_title` text COLLATE utf8mb4_unicode_520_ci NOT NULL, + `post_excerpt` text COLLATE utf8mb4_unicode_520_ci NOT NULL, + `post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'publish', + `comment_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', + `ping_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', + `post_password` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `post_name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `to_ping` text COLLATE utf8mb4_unicode_520_ci NOT NULL, + `pinged` text COLLATE utf8mb4_unicode_520_ci NOT NULL, + `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `post_content_filtered` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, + `post_parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `guid` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `menu_order` int(11) NOT NULL DEFAULT 0, + `post_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post', + `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `comment_count` bigint(20) NOT NULL DEFAULT 0, + PRIMARY KEY (`ID`), + KEY `post_name` (`post_name`(191)), + KEY `type_status_date` (`post_type`, `post_status`, `post_date`, `ID`), + KEY `post_parent` (`post_parent`), + KEY `post_author` (`post_author`) +) ENGINE = InnoDB + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_posts` (`ID`, `post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, `menu_order`, `post_type`, `post_mime_type`, `comment_count`) VALUES -(1, 1, '2020-04-20 19:10:05', '2020-04-20 19:10:05', '\n

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

\n', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2020-04-20 19:10:05', '2020-04-20 19:10:05', '', 0, 'https://tests.local/?p=1', 0, 'post', '', 1), -(2, 1, '2020-04-20 19:10:05', '2020-04-20 19:10:05', '\n

This is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:

\n\n\n\n

Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)

\n\n\n\n

...or something like this:

\n\n\n\n

The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.

\n\n\n\n

As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!

\n', 'Sample Page', '', 'publish', 'closed', 'open', '', 'sample-page', '', '', '2020-04-20 19:10:05', '2020-04-20 19:10:05', '', 0, 'https://tests.local/?page_id=2', 0, 'page', '', 0), -(3, 1, '2020-04-20 19:10:05', '2020-04-20 19:10:05', '

Who we are

Our website address is: http://localhost:32880.

What personal data we collect and why we collect it

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Contact forms

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Analytics

Who we share your data with

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Your contact information

Additional information

How we protect your data

What data breach procedures we have in place

What third parties we receive data from

What automated decision making and/or profiling we do with user data

Industry regulatory disclosure requirements

', 'Privacy Policy', '', 'draft', 'closed', 'open', '', 'privacy-policy', '', '', '2020-04-20 19:10:05', '2020-04-20 19:10:05', '', 0, 'https://tests.local/?page_id=3', 0, 'page', '', 0), -(4, 1, '2020-04-20 19:10:16', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', '', '', '2020-04-20 19:10:16', '0000-00-00 00:00:00', '', 0, 'https://tests.local/?p=4', 0, 'post', '', 0); +INSERT INTO `wp_posts` (`ID`, `post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, + `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, + `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, + `menu_order`, `post_type`, `post_mime_type`, `comment_count`) +VALUES (1, 1, '2020-04-20 19:10:05', '2020-04-20 19:10:05', + '\n

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

\n', + 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2020-04-20 19:10:05', + '2020-04-20 19:10:05', '', 0, 'https://tests.local/?p=1', 0, 'post', '', 1), + (2, 1, '2020-04-20 19:10:05', '2020-04-20 19:10:05', + '\n

This is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:

\n\n\n\n

Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)

\n\n\n\n

...or something like this:

\n\n\n\n

The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.

\n\n\n\n

As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!

\n', + 'Sample Page', '', 'publish', 'closed', 'open', '', 'sample-page', '', '', '2020-04-20 19:10:05', + '2020-04-20 19:10:05', '', 0, 'https://tests.local/?page_id=2', 0, 'page', '', 0), + (3, 1, '2020-04-20 19:10:05', '2020-04-20 19:10:05', + '

Who we are

Our website address is: http://localhost:32880.

What personal data we collect and why we collect it

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Contact forms

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Analytics

Who we share your data with

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Your contact information

Additional information

How we protect your data

What data breach procedures we have in place

What third parties we receive data from

What automated decision making and/or profiling we do with user data

Industry regulatory disclosure requirements

', + 'Privacy Policy', '', 'draft', 'closed', 'open', '', 'privacy-policy', '', '', '2020-04-20 19:10:05', + '2020-04-20 19:10:05', '', 0, 'https://tests.local/?page_id=3', 0, 'page', '', 0), + (4, 1, '2020-04-20 19:10:16', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', + '', '', '2020-04-20 19:10:16', '0000-00-00 00:00:00', '', 0, 'https://tests.local/?p=4', 0, 'post', '', 0); DROP TABLE IF EXISTS `wp_termmeta`; -CREATE TABLE `wp_termmeta` ( - `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `term_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 DEFAULT NULL, - PRIMARY KEY (`meta_id`), - KEY `term_id` (`term_id`), - KEY `meta_key` (`meta_key`(191)) -) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +CREATE TABLE `wp_termmeta` +( + `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `term_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 DEFAULT NULL, + PRIMARY KEY (`meta_id`), + KEY `term_id` (`term_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE = InnoDB + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_termmeta` (`meta_id`, `term_id`, `meta_key`, `meta_value`) VALUES -(9, 3, 'user_id_1', 'user_id'), -(10, 3, 'user_id', '1'), -(11, 3, 'first_name', ''), -(12, 3, 'last_name', ''), -(13, 3, 'user_email', 'publishpress-dev@example.com'), -(14, 3, 'user_login', 'admin'), -(15, 3, 'user_url', ''), -(16, 3, 'description', ''); +INSERT INTO `wp_termmeta` (`meta_id`, `term_id`, `meta_key`, `meta_value`) +VALUES (9, 3, 'user_id_1', 'user_id'), + (10, 3, 'user_id', '1'), + (11, 3, 'first_name', ''), + (12, 3, 'last_name', ''), + (13, 3, 'user_email', 'publishpress-dev@example.com'), + (14, 3, 'user_login', 'admin'), + (15, 3, 'user_url', ''), + (16, 3, 'description', ''); DROP TABLE IF EXISTS `wp_terms`; -CREATE TABLE `wp_terms` ( - `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `slug` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `term_group` bigint(10) NOT NULL DEFAULT 0, - PRIMARY KEY (`term_id`), - KEY `slug` (`slug`(191)), - KEY `name` (`name`(191)) -) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +CREATE TABLE `wp_terms` +( + `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `slug` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `term_group` bigint(10) NOT NULL DEFAULT 0, + PRIMARY KEY (`term_id`), + KEY `slug` (`slug`(191)), + KEY `name` (`name`(191)) +) ENGINE = InnoDB + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES -(1, 'Uncategorized', 'uncategorized', 0), -(3, 'admin', 'admin', 0); +INSERT INTO `wp_terms` (`term_id`, `name`, `slug`, `term_group`) +VALUES (1, 'Uncategorized', 'uncategorized', 0), + (3, 'admin', 'admin', 0); DROP TABLE IF EXISTS `wp_term_relationships`; -CREATE TABLE `wp_term_relationships` ( - `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `term_order` int(11) NOT NULL DEFAULT 0, - PRIMARY KEY (`object_id`,`term_taxonomy_id`), - KEY `term_taxonomy_id` (`term_taxonomy_id`) -) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +CREATE TABLE `wp_term_relationships` +( + `object_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `term_order` int(11) NOT NULL DEFAULT 0, + PRIMARY KEY (`object_id`, `term_taxonomy_id`), + KEY `term_taxonomy_id` (`term_taxonomy_id`) +) ENGINE = InnoDB + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES -(1, 1, 0), -(1, 3, 0), -(2, 3, 0), -(3, 3, 0), -(4, 3, 0); +INSERT INTO `wp_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) +VALUES (1, 1, 0), + (1, 3, 0), + (2, 3, 0), + (3, 3, 0), + (4, 3, 0); DROP TABLE IF EXISTS `wp_term_taxonomy`; -CREATE TABLE `wp_term_taxonomy` ( - `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, - `taxonomy` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `description` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, - `parent` bigint(20) unsigned NOT NULL DEFAULT 0, - `count` bigint(20) NOT NULL DEFAULT 0, - PRIMARY KEY (`term_taxonomy_id`), - UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), - KEY `taxonomy` (`taxonomy`) -) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +CREATE TABLE `wp_term_taxonomy` +( + `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `term_id` bigint(20) unsigned NOT NULL DEFAULT 0, + `taxonomy` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `description` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, + `parent` bigint(20) unsigned NOT NULL DEFAULT 0, + `count` bigint(20) NOT NULL DEFAULT 0, + PRIMARY KEY (`term_taxonomy_id`), + UNIQUE KEY `term_id_taxonomy` (`term_id`, `taxonomy`), + KEY `taxonomy` (`taxonomy`) +) ENGINE = InnoDB + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES -(1, 1, 'category', '', 0, 1), -(2, 2, 'author', '', 0, 1), -(3, 3, 'author', '', 0, 2); +INSERT INTO `wp_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) +VALUES (1, 1, 'category', '', 0, 1), + (2, 2, 'author', '', 0, 1), + (3, 3, 'author', '', 0, 2); DROP TABLE IF EXISTS `wp_usermeta`; -CREATE TABLE `wp_usermeta` ( - `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `user_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 DEFAULT NULL, - PRIMARY KEY (`umeta_id`), - KEY `user_id` (`user_id`), - KEY `meta_key` (`meta_key`(191)) -) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +CREATE TABLE `wp_usermeta` +( + `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_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 DEFAULT NULL, + PRIMARY KEY (`umeta_id`), + KEY `user_id` (`user_id`), + KEY `meta_key` (`meta_key`(191)) +) ENGINE = InnoDB + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES -(1, 1, 'nickname', 'admin'), -(2, 1, 'first_name', ''), -(3, 1, 'last_name', ''), -(4, 1, 'description', ''), -(5, 1, 'rich_editing', 'true'), -(6, 1, 'syntax_highlighting', 'true'), -(7, 1, 'comment_shortcuts', 'false'), -(8, 1, 'admin_color', 'fresh'), -(9, 1, 'use_ssl', '0'), -(10, 1, 'show_admin_bar_front', 'true'), -(11, 1, 'locale', ''), -(12, 1, 'wp_capabilities', 'a:1:{s:13:\"administrator\";b:1;}'), -(13, 1, 'wp_user_level', '10'), -(14, 1, 'dismissed_wp_pointers', ''), -(15, 1, 'show_welcome_panel', '1'), -(16, 1, 'session_tokens', 'a:1:{s:64:\"a78d13111ad081983cd00e7f0065d656b3e1c72e8b9fd8903288016cf15397bf\";a:4:{s:10:\"expiration\";i:1641416970;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:105:\"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36\";s:5:\"login\";i:1641244170;}}'), -(17, 1, 'wp_user-settings', 'libraryContent=browse&editor=html&mfold=o'), -(18, 1, 'wp_user-settings-time', '1587409811'), -(19, 1, 'wp_dashboard_quick_press_last_post_id', '4'), -(20, 1, 'community-events-location', 'a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}'); +INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) +VALUES (1, 1, 'nickname', 'admin'), + (2, 1, 'first_name', ''), + (3, 1, 'last_name', ''), + (4, 1, 'description', ''), + (5, 1, 'rich_editing', 'true'), + (6, 1, 'syntax_highlighting', 'true'), + (7, 1, 'comment_shortcuts', 'false'), + (8, 1, 'admin_color', 'fresh'), + (9, 1, 'use_ssl', '0'), + (10, 1, 'show_admin_bar_front', 'true'), + (11, 1, 'locale', ''), + (12, 1, 'wp_capabilities', 'a:1:{s:13:\"administrator\";b:1;}'), + (13, 1, 'wp_user_level', '10'), + (14, 1, 'dismissed_wp_pointers', ''), + (15, 1, 'show_welcome_panel', '1'), + (16, 1, 'session_tokens', + 'a:1:{s:64:\"a78d13111ad081983cd00e7f0065d656b3e1c72e8b9fd8903288016cf15397bf\";a:4:{s:10:\"expiration\";i:1641416970;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:105:\"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36\";s:5:\"login\";i:1641244170;}}'), + (17, 1, 'wp_user-settings', 'libraryContent=browse&editor=html&mfold=o'), + (18, 1, 'wp_user-settings-time', '1587409811'), + (19, 1, 'wp_dashboard_quick_press_last_post_id', '4'), + (20, 1, 'community-events-location', 'a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}'), + (21, 2, 'nickname', '_admin_user623b5909816d2'), + (22, 2, 'first_name', ''), + (23, 2, 'last_name', ''), + (24, 2, 'description', ''), + (25, 2, 'rich_editing', 'true'), + (26, 2, 'syntax_highlighting', 'true'), + (27, 2, 'comment_shortcuts', 'false'), + (28, 2, 'admin_color', 'fresh'), + (29, 2, 'use_ssl', '0'), + (30, 2, 'show_admin_bar_front', 'true'), + (31, 2, 'locale', ''), + (32, 2, 'wp_capabilities', 'a:1:{s:13:\"administrator\";b:1;}'), + (33, 2, 'wp_user_level', '10'), + (34, 2, 'dismissed_wp_pointers', ''), + (35, 2, 'session_tokens', + 'a:1:{s:64:\"161897136068c59af05aab0949388ca12230777db32a513040a99b7276445a7a\";a:4:{s:10:\"expiration\";i:1648229385;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:112:\"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/99.0.4844.74 Safari/537.36\";s:5:\"login\";i:1648056585;}}'); DROP TABLE IF EXISTS `wp_users`; -CREATE TABLE `wp_users` ( - `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, - `user_login` varchar(60) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `user_pass` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `user_nicename` varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `user_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `user_url` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', - `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - `user_status` int(11) NOT NULL DEFAULT 0, - `display_name` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', - PRIMARY KEY (`ID`), - KEY `user_login_key` (`user_login`), - KEY `user_nicename` (`user_nicename`), - KEY `user_email` (`user_email`) -) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; +CREATE TABLE `wp_users` +( + `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, + `user_login` varchar(60) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `user_pass` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `user_nicename` varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `user_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `user_url` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', + `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + `user_status` int(11) NOT NULL DEFAULT 0, + `display_name` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', + PRIMARY KEY (`ID`), + KEY `user_login_key` (`user_login`), + KEY `user_nicename` (`user_nicename`), + KEY `user_email` (`user_email`) +) ENGINE = InnoDB + DEFAULT CHARSET = utf8mb4 + COLLATE = utf8mb4_unicode_520_ci; -INSERT INTO `wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES -(1, 'admin', '$P$BiHs2lVx75mgbZ2kBapRn49vUbDQKl0', 'admin', 'publishpress-dev@example.com', '', '2020-04-20 19:10:05', '', 0, 'admin'); +INSERT INTO `wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, + `user_activation_key`, `user_status`, `display_name`) +VALUES (1, 'admin', '$P$BiHs2lVx75mgbZ2kBapRn49vUbDQKl0', 'admin', 'publishpress-dev@example.com', '', + '2020-04-20 19:10:05', '', 0, 'admin'), + (2, '_admin_user623b5909816d2', '$P$BZqneg29ctTYkUqwe4lmLhHMeGFYTG1', '_admin_user623b5909816d2', + '_admin_user623b5909816d2@example.com', '', '2022-03-23 17:29:45', '', 0, '_admin_user623b5909816d2'); --- 2022-01-03 22:20:37 +-- 2022-03-23 17:34:14 diff --git a/tests/codeception/_support/_generated/FrontendTesterActions.php b/tests/codeception/_support/_generated/FrontendTesterActions.php index f722bfc4..85f928b0 100644 --- a/tests/codeception/_support/_generated/FrontendTesterActions.php +++ b/tests/codeception/_support/_generated/FrontendTesterActions.php @@ -1,4 +1,4 @@ -