.org\">buddypress.trac.wordpress.org</a> regularly</td>\n                <td>2020</td>\n                <td>25.6%</td>\n            </tr>\n            <tr>\n                <td>2018</td>\n                <td>22.5%</td>\n            </tr>\n            <tr>\n                <td>2018 to 2020</td>\n                <td>3.1%</td>\n            </tr>\n            <tr>\n                <td rowspan=\"3\">Twitter: <a href=\"https://twitter.com/buddypress\">@buddypress</a>, <a href=\"https://twitter.com/buddypressdev\">@buddypressdev</a>, and/or <a href=\"https://twitter.com/bptrac\">@bptrac</a></td>\n                <td>2020</td>\n                <td>23.1%</td>\n            </tr>\n            <tr>\n                <td>2018</td>\n                <td>19.5%</td>\n            </tr>\n            <tr>\n                <td>2018 to 2020</td>\n                <td>3.6%</td>\n            </tr>\n            <tr>\n                <td rowspan=\"3\">Slack: <a href=\"https://wordpress.slack.com/messages/buddypress\">#buddypress</a>, <a href=\"https://wordpress.slack.com/messages/buddypress-commits\">#buddypress-commits</a>, <a href=\"https://wordpress.slack.com/messages/buddypress-firehose\">#buddypress-firehose</a> and/or <a href=\"https://wordpress.slack.com/messages/buddypress-newtickets\">#buddypress-newtickets</a></td>\n                <td>2020</td>\n                <td>15.5%</td>\n            </tr>\n            <tr>\n                <td>2018</td>\n                <td>12.2%</td>\n            </tr>\n            <tr>\n                <td>2018 to 2020</td>\n                <td>3.3%</td>\n            </tr>\n            <tr>\n                <td rowspan=\"3\">Other</td>\n                <td>2020</td>\n                <td>16.1%</td>\n            </tr>\n            <tr>\n                <td>2018</td>\n                <td>11.8%</td>\n            </tr>\n            <tr>\n                <td>2018 to 2020</td>\n                <td>4.2%</td>\n            </tr>\n        </tbody>\n    </table>\n\n\n\n\n<p><strong>NB</strong>: between 2018 &amp; 2020 the &#8220;Checking buddypress.org/support regularly.&#8221; choice disappeared.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2 id=\"q-16\"><em><em><em>16. Case Studies: We&#8217;d like to feature how you are using BuddyPress in your current sites at BuddyPress.org. If you’re interested in sharing your BP story, please leave your name, email address, and your BP site URL.</em></em></em></h2>\n\n\n\n<p>Number of respondents: <strong>40</strong>.</p>\n\n\n\n<p>Many thanks to the 40 participants who shared their names, emails, and sites URL. We&#8217;ll try to contact you to share about your use cases on this website. It&#8217;s great to see how you&#8217;re using BuddyPress <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f4aa.png\" alt=\"?\" class=\"wp-smiley\" />.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2 id=\"q-17\"><em><em><em>17. BuddyPress is a large plugin with optional components (3MB zipped). There&#8217;s a proposal to reconstitute BuddyPress as core + members only and improved upon with new functionalities and API&#8217;s among others for new BP plugins to hook into. The current optional components like groups, friends, private messaging, etc. can be migrated into separate plugins which can be activated as needed. What do you think?</em></em></em></h2>\n\n\n\n<p>Number of respondents: <strong>407</strong>.</p>\n\n\n\n\n    <table class=\"has-fixed-layout\">\n        <thead>\n            <tr>\n                <th>Possible replies</th>\n                <th>Year</th>\n                <th>Results</th>\n            </tr>\n        </thead>\n        <tbody>\n            <tr>\n                <td><strong>Keep BuddyPress as is: core + members and optional components</strong></td>\n                <td>2020</td>\n                <td><span class=\"has-inline-color\"><strong>43.2%</strong></span></td>\n            </tr>\n            <tr>\n                <td>Break down BuddyPress: BuddyPress = core + members, optional components as BP plugins</td>\n                <td>2020</td>\n                <td>35.6%</td>\n            </tr>\n            <tr>\n                <td>I don&#8217;t know</td>\n                <td>2020</td>\n                <td>21.1%</td>\n            </tr>\n        </tbody>\n    </table>\n\n\n\n\n<p><strong>NB</strong>: this question wasn&#8217;t asked in 2018</p>\n\n\n\n<p>Ok. Thanks a lot for your replies, using optional components as separate add-ons is not something you are ready for <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f607.png\" alt=\"?\" class=\"wp-smiley\" />.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2 id=\"survey-map\">BuddyPress is used from all over the world!</h2>\n\n\n\n<div class=\"wp-block-image\"><a href=\"https://docs.google.com/spreadsheets/d/e/2PACX-1vT067Mc1bnQPTdiwZzzZj7Kn1Y2V22aJxJnvy13rN2DXg27awoA_GXPJvX0uv2He8udDL_bLjCeUv7M/pubhtml?gid=1888221811&single=true\"><img width=\"1024\" height=\"639\" src=\"https://buddypress.org/wp-content/uploads/1/2020/12/survey-participants-1024x639.png\" alt=\"\" class=\"wp-image-316008\" /></a></div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 08 Dec 2020 16:45: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: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: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:76:\"WPTavern: Easy WP SMTP 1.4.3 Patches Sensitive Data Disclosure Vulnerability\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=108630\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:197:\"https://wptavern.com/easy-wp-smtp-1-4-3-patches-sensitive-data-disclosure-vulnerability?utm_source=rss&utm_medium=rss&utm_campaign=easy-wp-smtp-1-4-3-patches-sensitive-data-disclosure-vulnerability\";s: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:3019:\"<p><a href=\"https://wordpress.org/plugins/easy-wp-smtp/\">Easy WP SMTP</a> has patched a vulnerability that allows attackers to capture the password reset link from the plugin&rsquo;s debug log file and gain unauthorized access to the site. The plugin is used by more than 500,000 WordPress sites to configure and send all outgoing emails via a SMTP server so they are less likely to end up in recipients&rsquo; junk/spam folders. </p>\n\n\n\n<p><a href=\"https://wpscan.com/vulnerability/10494\">WPScan</a> categorized the vulnerability as a &ldquo;sensitive data disclosure:&rdquo;</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>The plugin has an optional debug log file generated with a random name, located in the plugin folder and which contains all email messages sent. However, this folder does not have any index page, allowing access to log file on servers with the directory listing enabled or misconfigured. This could allow attackers to gain unauthorised access to the blog by reseting the admin password by getting the reset link from the log.</p></blockquote>\n\n\n\n<p>Easy WP SMTP version  1.4.3 contains the fix, adding an empty &ldquo;index.html&rdquo; file to the plugin&rsquo;s folder to prevent anyone from browsing the files (even if the Option -Indexes is missing on that server). Users are advised to update immediately, as the vulnerability has already been exploited in the wild. Several users took to the plugin&rsquo;s support forums to <a href=\"https://wordpress.org/support/topic/security-issue-with-debug-log/\">report</a> attempts on their sites.</p>\n\n\n\n<p>Jerome Bruandet, a security researcher from NinTechNet, reported the vulnerability and published a <a href=\"https://blog.nintechnet.com/wordpress-easy-wp-smtp-plugin-fixed-zero-day-vulnerability/\">post</a> explaining how an attacker might access the debug log where the plugin writes all the email messages sent by the site. Using author archive scans, the hacker can find a username and then send a password reset email that gets intercepted via the Easy WP SMTP debug log file:</p>\n\n\n\n<div class=\"wp-block-image\"><img />Easy WP SMTP log file &ndash; source: <a href=\"https://blog.nintechnet.com/wordpress-easy-wp-smtp-plugin-fixed-zero-day-vulnerability/\">NinTechNet</a></div>\n\n\n\n<p>At the time of publishing, approximately 51.8% of users are on 1.4.x versions of the plugin. Without a more specific breakdown, it&rsquo;s not clear how many users have updated to the patched 1.4.3 version. Approximately <a href=\"https://wordpress.org/plugins/easy-wp-smtp/advanced/\">59,000 sites</a> have downloaded the plugin today, leaving many installations still vulnerable.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>This is another case where automatic background updates on plugins can quietly save the day. Users who have auto-updates enabled for plugins have already received the fix. Administrators for older installations of WordPress or sites where auto-updates have been disabled will need to update manually as soon as possible.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 07 Dec 2020 20:56:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:42:\"WordPress.org blog: State of the Word 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9296\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpress.org/news/2020/12/state-of-the-word-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:717:\"<p>State of the Word is an annual keynote address delivered by the project co-founder, Matt Mullenweg. Catch this year&#8217;s keynote in the video below!</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<h3>New to State of the Word?</h3>\n\n\n\n<p>If this is your first time hearing of this talk, you’re in luck! Check out previous recordings below.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.tv/2019/11/03/2019-state-of-the-word/\">State of the Word 2019 &#8211; WordCamp US, St. Louis</a></li><li><a href=\"https://wordpress.tv/2018/12/27/state-of-the-word-2018/\">State of the Word 2018 &#8211; WordCamp US, Nashville</a></li><li><a href=\"https://wordpress.tv/tag/state-of-the-word/\">All recordings</a></li></ul>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Dec 2020 22:55:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:\"\";}}}}}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:48:\"BuddyPress: BuddyPress 7.0.0 Release Candidate 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=315858\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"https://buddypress.org/2020/12/buddypress-7-0-0-rc2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3608:\"<p>Hello,</p>\n\n\n\n<p>The second <a href=\"https://downloads.wordpress.org/plugin/buddypress.7.0.0-RC2.zip\">release candidate for BuddyPress 7.0.0</a> is now ready for an ultimate round of testing <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f642.png\" alt=\"?\" class=\"wp-smiley\" /></p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2>What happened Since the&nbsp;<a href=\"https://buddypress.org/2020/11/buddypress-7-0-0-release-candidate/\">first release candidate</a>?</h2>\n\n\n\n<p>We&#8217;ve been working on getting the BP Nouveau Template Pack looks great into the next WordPress default theme &#8220;<a href=\"https://make.wordpress.org/core/2020/09/23/introducing-twenty-twenty-one/\">Twenty Twenty-One</a>&#8220;. We believe BP Nouveau is now ready to enjoy this awesome theme whether you use its regular or dark mode.</p>\n\n\n\n<div class=\"wp-block-image\"><a href=\"https://buddypress.org/wp-content/uploads/1/2020/12/bp-nouveau-2021.png\"><img width=\"1000\" height=\"479\" src=\"https://buddypress.org/wp-content/uploads/1/2020/12/bp-nouveau-2021.png\" alt=\"\" class=\"wp-image-315860\" /></a><em>Screen capture of the Members directory</em> (dark mode)</div>\n\n\n\n<p>BuddPress 7.0.0 is&nbsp;still slated for release&nbsp;on&nbsp;<strong>Wednesday, December 9</strong>, and if you haven’t tried 7.0.0 yet,&nbsp;<strong>it’s probably your last chance to do so!</strong></p>\n\n\n\n<p>Let&#8217;s test <a href=\"https://downloads.wordpress.org/plugin/buddypress.7.0.0-RC2.zip\">BuddyPress 7.0.0-RC2</a> with <a href=\"https://make.wordpress.org/core/2020/12/03/wordpress-5-6-rc-3/\">WordPress 5.6-RC3</a> to be sure both will be great as soon as they will be released! It&#8217;s also important to do so if you want to help us check BP Nouveau&#8217;s integration with Twenty Twenty-One is as nice as we think <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f609.png\" alt=\"?\" class=\"wp-smiley\" /></p>\n\n\n\n<p>You can test the <a href=\"https://downloads.wordpress.org/plugin/buddypress.7.0.0-RC2.zip\">7.0.0-RC2</a> pre-release in 4 ways :</p>\n\n\n\n<ul><li>Try the <a href=\"https://wordpress.org/plugins/bp-beta-tester/\">BP Beta Tester</a> plugin.</li><li><a href=\"https://downloads.wordpress.org/plugin/buddypress.7.0.0-RC2.zip\">Download the release candidate here (zip file)</a>.</li><li>Check out our SVN repository: <code>svn co https://buddypress.svn.wordpress.org/trunk/</code></li><li>Clone our read-only Git repository: <code>git clone git://buddypress.git.wordpress.org/</code></li></ul>\n\n\n\n<p>A detailed changelog will be part of our official release note, but&nbsp;you can get a quick overview by reading the post about the&nbsp;<a href=\"https://buddypress.org/2020/10/buddypress-7-0-0-beta1/\">7.0.0 Beta1</a>&nbsp;release.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2>Polyglots contributors, let&#8217;s target 100% of translated strings.</h2>\n\n\n\n<p>Since previous release candidate we&#8217;ve reached the&nbsp;<a href=\"https://make.wordpress.org/polyglots/handbook/glossary/#string-freeze\">string freeze</a>&nbsp;point of the 7.0.0 release schedule, so this one (RC2) does not introduce new strings to translate. Let&#8217;s use the days we have left to try to make BuddyPress fully available into your locale as soon as it is released. Thanks in advance for your help.</p>\n\n\n\n<p>As usual, <strong>if you think you’ve found a bug</strong>, please let us know reporting it on <a href=\"https://buddypress.org/support/topic/buddypress-7-0-0-release-candidate-2/\">this support topic</a> and/or on <a href=\"https://buddypress.trac.wordpress.org/\">our development tracker</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Dec 2020 22:22:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"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: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:116:\"WPTavern: State of CSS 2020 Survey Results: Tailwind CSS Wins Most Adopted Technology, Utility-First CSS on the Rise\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=108561\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:273:\"https://wptavern.com/state-of-css-2020-survey-results-tailwind-css-wins-most-adopted-technology-utility-first-css-on-the-rise?utm_source=rss&utm_medium=rss&utm_campaign=state-of-css-2020-survey-results-tailwind-css-wins-most-adopted-technology-utility-first-css-on-the-rise\";s: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:3346:\"<p>The <a href=\"https://2020.stateofcss.com/en-US/\">State of CSS 2020</a> survey results have just been published, with a summary of the tools, methodologies, frameworks, and libraries that are currently favored by CSS professionals. It includes data from 11,492 respondents in 102 countries, after the questions were translated for the first time into a dozen different languages.</p>\n\n\n\n<p>In the layout category, CSS Grid logged a 34% increase over the prior year in respondents who report having used it to position elements on the screen. It won an award for &ldquo;Most Adopted Feature,&rdquo; which is assigned to the feature with the largest year-over-year &rdquo;have used&rdquo; progression. Only 6% of respondents said they have used Subgrid, which is included in Level 2 of the CSS Grid Layout specification. </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>CSS Flexible Box Layout has been used by 97.5% of respondents, a ~3% increase over the previous year. Multi-column Layout saw a moderate increase in usage and a small decrease in awareness. CSS Grid experienced the most growth by far in this category.</p>\n\n\n\n<p>The technologies section is one of the most interesting parts of the survey, as the CSS ecosystem is constantly changing. The results include a scatter plot graph showing the relationship between each technology&rsquo;s satisfaction ratio and its user count. Technologies in the &ldquo;avoid&rdquo; and &ldquo;analyze&rdquo; groupings are likely to decline in usage soon (or have already fallen out of favor). </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Tailwind CSS is once again the front-runner among CSS frameworks, followed by Bulma, which seems to be slowly waning in popularity. Tailwind CSS won the award for &ldquo;Most Adopted Technology,&rdquo; given to the technology with the largest year-over-year &ldquo;would use again&rdquo; progression, with a +17.8% progression over 2019. PureCSS, Ant Design, and Materialize CSS also recorded gains in their rankings from the previous year. </p>\n\n\n\n<p>A larger trend emerging is utility-first CSS frameworks and tools gaining momentum among professionals. The utility-first approach, which eschews traditional semantic class naming in favor of more functional class names, <a href=\"http://www.zeldman.com/2017/01/03/kiss-my-classname/\">has its ardent critics</a>.  It is somewhat of an eyesore reminiscent of inline styles, and essentially drops the &ldquo;cascading&rdquo; aspect of CSS. Nevertheless, its proponents appreciate being able to look at the HTML and see at a glance which styles are applied, as well as the enforced consistency it offers.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>If you are interested in some of the finer details on which properties and positioning features professionals are using, shapes, graphics, and interactions, check out the <a href=\"https://2020.stateofcss.com/en-US/\">full report</a>. Each section has recommended resources for learning more about popular and emerging technologies and techniques, including industry podcasts and blogs that professionals are currently enjoying.</p>\n\n\n\n<p>The <a href=\"https://stateofjs.com/\">State of JavaScript</a> survey is also now open, which offers a similar treasure trove of data on the JavaScript ecosystem once the results are published. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Dec 2020 21:30:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"WPTavern: WordPress Community Team Discusses Return to In-Person Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=108398\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:187:\"https://wptavern.com/wordpress-community-team-discusses-return-to-in-person-events?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-community-team-discusses-return-to-in-person-events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6803:\"<p>Although the promise of effective COVID-19 vaccines is shining a light at the end of a long tunnel, the world remains firmly in the virus&rsquo; grip until distribution can ramp up to cover at-risk groups as well as the general populace.</p>\n\n\n\n<p>As pandemic-weary communities muster the discipline to ride out the next few months under continued restrictions, a new discussion popped up on WordPress.org regarding the <a href=\"https://make.wordpress.org/community/2020/12/01/discussion-how-can-the-wordpress-community-return-to-hosting-safe-in-person-events/\">return to in-person events</a>. WordPress has canceled all in-person events through the end of the year and 2021 flagship events have already been designated as online-only. Community organizer Angela Jin cited recent successful vaccine trials as a prompt for discussing how WordPress can safely resume in-person events: </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>There has been promising news around some successful trials for vaccines recently! As such, it seems worthwhile to discuss how the WordPress community can return to hosting safe, in-person events.&nbsp;</p><p>Any in-person event would certainly be subject to local laws and any restrictions on gatherings, as they&rsquo;ve always been. Beyond what local health authorities require, the Global Community Team may need to to help organizers identify what additional precautions are necessary to ensure in-person events are safe for participants.&nbsp;</p></blockquote>\n\n\n\n<p>Jin offered several examples of &ldquo;additional precautions&rdquo; to ensure events are safe, such as mandatory masks, social distancing, outdoor events, limits on the number of attendees, and no food or drink service. </p>\n\n\n\n<p>Although countries like Australia, Taiwan, and New Zealand, seem to have adequately contained the virus, the U.S., Europe, India, and Russia have cases spiraling out of control. The discussion seems oddly timed, as this week the U.S., which is leading the world in deaths, has seen daily deaths climb to <a href=\"https://www.npr.org/sections/coronavirus-live-updates/2020/12/02/941902471/u-s-hits-100-000-covid-19-hospitalizations-breaks-daily-death-record\">2,804</a>, surpassing the previous record of 2,607 reported on April 15, during the first wave of the pandemic.</p>\n\n\n\n<p>Several of those commenting mentioned that the discussion opener neglects a critical detail about whether or not in-person events would resume before vaccines are widely distributed.</p>\n\n\n\n<p>&ldquo;I&rsquo;m surprised I don&rsquo;t see mention of the vaccine being a requirement,&rdquo; Mika Epstein said. &ldquo;I could assume so, but the risk of COVID is human life.</p>\n\n\n\n<p>&ldquo;That means that unless WordPress (or any public event) has a way to ensure that no one will contract (and die) of COVID, then they have no business having any event, indoor or outdoor.</p>\n\n\n\n<p>&ldquo;Not every country is handling things equally well, and just in the US alone, there are many places where the law says &lsquo;do not have events&rsquo; but the local authorities refuse to intercede, which resulted in 80% of the people attending an outdoor party not too far from me all testing positive.&rdquo; </p>\n\n\n\n<p>WordPress is a global community and reliance on local laws may still put event attendees at risk in communities that have been subject to a failure of leadership in protecting citizens.</p>\n\n\n\n<p>Cami Kaos, an eight-year WordPress community organizer, echoed these thoughts, saying, &ldquo;The one thing we need to have in place in order to make a safe re-entry into in person events is to have wide spread access to an effective vaccine.&rdquo; She commented on the difficulties of trying to ensure attendees don&rsquo;t inadvertently put each other at risk:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>It&rsquo;s all well and good for us to say you can only organize within the recommendations of your local community, but we have no way of knowing how responsible individuals are being. Of knowing if they have come in from out of town for the event. If a member of their household is a frontline worker who might be exposed daily, if someone in their family is high risk and we could be endangering a life.</p></blockquote>\n\n\n\n<p>Without widely distributed vaccines, hosting in-person gatherings with the possibility of attendees traveling from hotspot locations would be unconscionable.</p>\n\n\n\n<p>Kaos also commented on how difficult enforcement would be for WordPress community volunteers who would be tasked with making sure individuals wear masks properly, use hand sanitizer, maintain distance, and uphold any other requirements. </p>\n\n\n\n<p>&ldquo;All of this would be putting unpaid and uncompensated volunteers at risk unnecessarily,&rdquo; Kaos said.</p>\n\n\n\n<p>&ldquo;If people would like to make the choice to see their friends and collaborators in person, that can be their choice. But I don&rsquo;t feel morally comfortable legally and finically supporting in-person gatherings when I think we could prevent even one death by extending our pause on in-person events to wait for a vaccine to be readily available.&rdquo;</p>\n\n\n\n<p>Other commenters discussed how to manage the logistics of sponsoring masks and sanitizer for organizers by coordinating with local venues and figuring out a way around slow international shipments.  </p>\n\n\n\n<p>&ldquo;This actually opens totally new ways to organize WordPress events!&rdquo; WordCamp organizer Timi Wahalahti said. &ldquo;Why not have a bicycle trip or something similar with your WordPress friends?&rdquo;</p>\n\n\n\n<p>Live event recordings are another consideration for hosting events in a way that is accessible to more vulnerable populations. According to WordPress community organizer Andrea Middleton, professional video recording has historically been cost prohibitive at scale.</p>\n\n\n\n<p>&ldquo;A year ago focusing on recordings may have sounded in some ways counterproductive to growing in-person events,&rdquo; WordPress core contributor David Ryan said. &ldquo;But I think today they provide a short-term fix to the head count crunch, can help bring/keep folx in-the-fold while making in-person attendance even safer, all while adding long-term value even when travel and gatherings normalize.&rdquo;</p>\n\n\n\n<p>The discussion on finding a safe path forward for restarting in-person events will be open until December 16, 2020. Organizers and community members can <a href=\"https://make.wordpress.org/community/2020/12/01/discussion-how-can-the-wordpress-community-return-to-hosting-safe-in-person-events/\">comment on the post</a> for consideration. Angela Jin said the Community Team will continue to support online events in 2021 and beyond, regardless of any decisions resulting from the discussion.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 03 Dec 2020 22:10:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:91:\"WPTavern: Gutenberg 9.5 Improves Site Editor and Adds New Options for Cover and Code Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=108450\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:227:\"https://wptavern.com/gutenberg-9-5-improves-site-editor-and-adds-new-options-for-cover-and-code-blocks?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-9-5-improves-site-editor-and-adds-new-options-for-cover-and-code-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4774:\"<p class=\"has-drop-cap\">Gutenberg 9.5 <a href=\"https://make.wordpress.org/core/2020/12/02/whats-new-in-gutenberg-2-december/\">went live today</a>. The development team is continuing forward with work that we will start seeing down the road in WordPress 5.7 and beyond. The big user-facing highlights for this release were the additions of a full-height alignment option for the Cover block, font-size support in the Code block, and improved previews for block patterns.</p>\n\n\n\n<p>The majority of users will not see most of the work that went into the 9.5 release. The team addressed dozens of bugs and enhancements for the full-site editing feature. To test them, users must be using a block-based WordPress theme, such as <a href=\"https://wptavern.com/twenty-twenty-one-blocks-theme-launching-as-a-separate-project\">Twenty Twenty-One Blocks</a>, <a href=\"https://wptavern.com/q-first-fse-wordpress-theme-now-live\">Q</a>, or <a href=\"https://wptavern.com/block-based-bosco-second-full-site-editing-theme-lands-in-the-wordpress-directory\">Block-Based Bosco</a>.</p>\n\n\n\n<p>We are a long way from seeing a production-ready site editor, but it is nice to see the improvements with each major Gutenberg release, such as the ability to <a href=\"https://github.com/WordPress/gutenberg/pull/27224\">set a post&rsquo;s featured image</a> if it doesn&rsquo;t exist. The new description, status, and theme <a href=\"https://github.com/WordPress/gutenberg/pull/27156\">admin columns for templates and template parts</a> add useful information. And, the developer side of me is happy to see a new <code>wp_theme</code> <a href=\"https://github.com/WordPress/gutenberg/pull/27016\">taxonomy for grouping templates</a> under the hood rather than metadata.</p>\n\n\n\n<p>The development team has made progress on the Query block. It is probably the most important piece of the full-site editing puzzle, and its current state is still holding back movement on block-based themes. The block now sports a new <a href=\"https://github.com/WordPress/gutenberg/pull/27067\">&ldquo;grid view&rdquo; option</a>. There is also a <a href=\"https://github.com/WordPress/gutenberg/pull/26990\">Posts List variation</a> that sets up a default of listing blog posts and excluding sticky posts. This block variation is a step toward pushing third-party plugin developers into creating custom variations for their post types in the future, building from the example set by WordPress.</p>\n\n\n\n<h2>Full-Screen Cover Block</h2>\n\n\n\n<img />Setting the Cover block to full height.\n\n\n\n<p class=\"has-drop-cap\">The Gutenberg team added a new <a href=\"https://github.com/WordPress/gutenberg/pull/26615\">Full Height Alignment</a> toolbar option to the Cover block. This is an independent alignment option and does not interfere with the existing horizontal alignments.</p>\n\n\n\n<p>When adding the Cover block to a post, users will see a new frame-like button in the toolbar. After clicking, it will automatically set the height setting in the block options to <code>100 vh</code>, which is the full height of the browser viewport. This option is far more flexible than having users set a height with pixel units, which do not automatically adjust based on the visitor&rsquo;s screen size.</p>\n\n\n\n<p>By combining this new alignment with full-width alignment, users can create full-screen layouts with the Cover block.</p>\n\n\n\n<p>The new toolbar control will likely <a href=\"https://github.com/WordPress/gutenberg/issues/16385\">land in other core blocks</a>. The Media &amp; Text block is another good use case. Plus, third-party plugin developers can integrate it into their blocks. As its use becomes more widespread in blocks, it will offer more robust design options for theme developers too.</p>\n\n\n\n<h2>Change Code Block Font Size</h2>\n\n\n\n<img />Setting the Code block&rsquo;s font size.\n\n\n\n<p class=\"has-drop-cap\">The Code block now has the same <a href=\"https://github.com/WordPress/gutenberg/pull/27294\">font-size option</a> as other text-based blocks, such as Paragraph and List. In general, users should probably shy away from adjusting this on a per-post basis and stick to the global default set by their theme or the Global Styles options when they eventually land in WordPress.</p>\n\n\n\n<p>However, there are use cases where it makes sense to change the code font-size in particular layouts.  I imagine some development-related site owners will want to highlight or showcase code in some way.</p>\n\n\n\n<p>With that in mind, it would be interesting to see other design options brought to Code block. Currently, it does not offer much in the way of customization, but color and background options could allow users to spruce up their code examples a bit without relying on a third-party plugin for that extra bit of pizzazz.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 02 Dec 2020 23:45:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:57:\"WordPress.org blog: The Month in WordPress: November 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9283\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2020/12/the-month-in-wordpress-november-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:10892:\"<p>November 2020 saw several updates to the WordPress 5.6 release. Read on to follow all the latest news from the WordPress world!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.6 updates</h2>\n\n\n\n<p>The Core team released WordPress 5.6 <a href=\"https://wordpress.org/news/2020/11/wordpress-5-6-beta-3/\">Beta 3</a> on Nov. 2, <a href=\"https://wordpress.org/news/2020/11/wordpress-5-6-beta-4/\">Beta 4</a> on Nov. 12, <a href=\"https://wordpress.org/news/2020/11/wordpress-5-6-release-candidate/\">release candidate</a> 1 on Nov. 17, and <a href=\"https://wordpress.org/news/2020/12/wordpress-5-6-release-candidate-2/\">release candidate 2</a> on Dec. 1. You can test the Beta versions and the release candidates by <a href=\"https://wordpress.org/wordpress-5.6-beta2.zip\">downloading them from WordPress.org</a> or by using the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin. Check out the <a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">WordPress 5.6 field guide</a> to understand the features of WordPress 5.6 and learn how you can incorporate them into your websites. WordPress 5.6 <a href=\"https://make.wordpress.org/core/5-6/\">will be out by Dec. 9, 2020</a>. </p>\n\n\n\n<p>But our work is never done: You can submit <a href=\"https://make.wordpress.org/core/2020/11/23/wordpress-5-7-whats-on-your-wishlist/\">feature suggestions for WordPress 5.7</a> by Dec. 15.&nbsp;</p>\n\n\n\n<p>Want to contribute to upcoming WordPress releases? Join the WordPress Core dev chats on Wednesdays at 5 a.m. and 8 p.m. UTC in the <a href=\"https://wordpress.slack.com/archives/C02RQBWTW\">#core</a> channel on the <a href=\"https://make.wordpress.org/chat/\">Make WordPress Slack</a>, and <a href=\"https://make.wordpress.org/core/tag/dev-chat/\">catch up with recaps</a> on the <a href=\"https://make.wordpress.org/core/\">Core team blog</a>. If you would like to help with WordPress 5.6 outreach, contact the <a href=\"https://make.wordpress.org/marketing/\">WordPress Marketing team</a> on the <a href=\"https://wordpress.slack.com/archives/C0GKJ7TFA\">#marketing</a> channel.</p>\n\n\n\n<h2>Gutenberg 9.3 and 9.4 are out</h2>\n\n\n\n<p>Contributor teams released Gutenberg <a href=\"https://make.wordpress.org/core/2020/11/04/whats-new-in-gutenberg-4-november/\">Version 9.3</a> on Nov. 4 and <a href=\"https://make.wordpress.org/core/2020/11/19/whats-new-in-gutenberg-18-november-2/\">Version 9.4</a> on Nov. 18. Both versions include&nbsp; several improvements to Full Site Editing (FSE) flows, in addition to bug fixes and feature upgrades. Version 9.3 is the first release that isn’t included entirely in WordPress 5.6; the version automatically enables FSE experiments when a block-based theme is active. Version 9.4 introduces some new features like percentage width for button blocks, block variation transformations, social icon support, and font size support for the list block. You can find out more about the Gutenberg roadmap in the <a href=\"https://make.wordpress.org/core/2020/11/02/whats-next-in-gutenberg-november-2020/\">What’s next in Gutenberg blog post</a>.</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the <a href=\"https://wordpress.slack.com/archives/C02QB2JS7\">#core-editor</a> channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>Learn WordPress updates</h2>\n\n\n\n<p>WordPress contributor teams are all set to launch <a href=\"https://learn.wordpress.org/\">Learn WordPress</a> in December. Community members can now watch<a href=\"https://learn.wordpress.org/workshops\"> video workshops</a> to learn about various WordPress topics, <a href=\"https://www.meetup.com/learn-wordpress-discussions/\">participate in discussion groups</a>, and use <a href=\"https://learn.wordpress.org/lesson-plans/\">lesson plans</a> for organizing their own workshops. Contributor teams have launched <a href=\"https://make.wordpress.org/community/2020/11/18/quizzes-are-now-live-on-learn-wordpress/\">quizzes</a> and are also working on <a href=\"https://make.wordpress.org/community/2020/11/18/standards-for-learn-wordpress-workshop-content/\">setting standards</a> for workshops.<br /></p>\n\n\n\n<p>Want to contribute to Learn WordPress? You can now submit a <a href=\"https://learn.wordpress.org/workshop-presenter-application/\">workshop application</a> (submissions in languages other than English are welcome!), apply to become a <a href=\"https://learn.wordpress.org/discussion-group-leader-application/\">discussion group leader</a>, organize <a href=\"https://make.wordpress.org/community/handbook/virtual-events/organize-learn-wordpress-discussion-groups-for-your-wordpress-meetup/\">discussions for your local WordPress meetup group</a>, or <a href=\"https://make.wordpress.org/training/2020/11/25/high-priority-items-before-learn-wordpress-org-launch-part-2/\">help fix issues with existing lesson plans</a>.</p>\n\n\n\n<h2>WordPress 5.6 Translations and Polyglots survey</h2>\n\n\n\n<p>WordPress 5.6 is ready to be translated and is now at <a href=\"https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze\">hard string freeze</a>. If you would like to contribute, <a href=\"https://make.wordpress.org/polyglots/2020/11/07/wordpress-5-6-ready-to-be-translated/\">check out these instructions</a> and ensure that <a href=\"https://make.wordpress.org/polyglots/handbook/translating/packaging-localized-wordpress/automated-release-packages/\">your locale is ready for an automated release</a>. The Polyglots team has also kicked off its <a href=\"https://wordpressdotorg.survey.fm/polyglots-translator-research\">translator research survey</a>. Please <a href=\"https://wordpressdotorg.survey.fm/polyglots-translator-research\">participate in the survey</a>, share the <a href=\"https://wordpressdotorg.survey.fm/polyglots-translator-research\">survey link</a> with members of your locale, and help amplify the <a href=\"https://www.facebook.com/WPTranslationDay/posts/1275404086174610\">Facebook</a>, <a href=\"https://twitter.com/TranslateWP/status/1333342595913834496\">Twitter</a>, and <a href=\"https://www.linkedin.com/posts/wptranslationday_makewordpress-wordpress-activity-6739110862650523648-fX8R/\">LinkedIn</a> posts about it.</p>\n\n\n\n<p>Want to help WordPress speak your language? Follow <a href=\"https://make.wordpress.org/polyglots\">the Polyglots team blog</a> and join the <a href=\"https://wordpress.slack.com/archives/C02RP50LK\">#polyglots</a> channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.&nbsp;</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li><a href=\"https://www.php.net/releases/8.0/en.php\">PHP 8</a> is out, and WordPress 5.6 <a href=\"https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/\">aims to be &#8220;beta-compatible&#8221; with the latest PHP version</a>.</li><li>Contributor teams have kicked off <a href=\"https://make.wordpress.org/themes/2020/11/18/theme-previews-in-the-time-of-blocks/\">an ongoing discussion on starter content for WordPress themes</a>. Starter content for the <a href=\"http://wp-themes.com/twentytwentyone/\">Twenty Twenty One</a>, <a href=\"http://wp-themes.com/twentytwenty/\">Twenty Twenty</a>, and <a href=\"http://wp-themes.com/twentyseventeen/\">Twenty Seventeen</a> themes are now available.</li><li>The Accessibility team is <a href=\"https://github.com/10degrees/accessibility-statement-plugin\">testing a tool</a> to generate the structure of an accessibility statement for WordPress websites based on <a href=\"https://www.w3.org/WAI/planning/statements/generator/#create\">W3C standards</a>, and it is <a href=\"https://github.com/10degrees/accessibility-statement-plugin/issues\">requesting feedback from the community</a>.</li><li>The <a href=\"https://wordpressfoundation.org/\">WordPress Foundation</a> has published a <a href=\"https://wordpressfoundation.org/2020/open-source-workshops-november-2020-report/\">report on Open Source workshops</a> that were held online in 2020, based on the <a href=\"https://learn.wordpress.org/\">Learn WordPress</a> platform.</li><li>The Docs team is actively <a href=\"https://make.wordpress.org/docs/2020/11/12/follow-up-on-gutenberg-developer-documentation-restructuring-proposal/\">following up</a> on a proposal to <a href=\"https://make.wordpress.org/docs/2020/08/13/plan-proposal-for-a-new-better-structured-gutenberg-developer-documentation/\">restructure the Gutenberg developer documentation</a>.</li><li>The Community team is back with <a href=\"https://make.wordpress.org/community/tag/tuesdaytrainings/\">Tuesday Trainings</a>. The team is <a href=\"https://make.wordpress.org/community/2020/11/16/community-team-goals-for-2021-share-your-suggestions/\">also inviting suggestions on team goals for 2021</a> with a deadline of Dec. 14.</li><li>The Support team is <a href=\"https://make.wordpress.org/support/2020/11/changing-up-the-forum-front-page/\">making changes to the forum page</a> to improve discoverability. </li><li>Two online WordCamps took place in November: <a href=\"https://finland.wordcamp.org/2020/\">WordCamp Finland Online</a> and <a href=\"https://mexico.wordcamp.org/2020/\">WordCamp Mexico Online</a>. You can find Livestream recaps of the events on their websites. Videos will soon be available on WordPress.tv as well.</li><li>The Themes team <a href=\"https://make.wordpress.org/themes/2020/11/11/meeting-notes-tuesday-november-10-2020/\">made some changes to WordPress theme requirements</a>. These include removing updated CSS guidelines and a proposed plan to make WordPress themes accessibility-ready. The team is also <a href=\"https://make.wordpress.org/themes/2020/11/19/feedback-requested-resolution-process-for-issues-found-in-live-themes/\">requesting feedback</a> on the resolution process for issues found in live themes.</li><li>WordPress 5.6 will feature a <a href=\"https://make.wordpress.org/core/2020/11/05/updating-core-jquery-to-version-3-part-2/\">major jQuery change</a>, with the bundled jQuery version being updated to Version 3.5.1 and jQuery Migrate being updated to Version 3.3.2.</li><li>The <a href=\"https://make.wordpress.org/community/tag/wpdiversity/\">Diversity speaker training group</a> of the Community team is requesting feedback on reimagining their work. Please <a href=\"https://make.wordpress.org/community/2020/11/12/input-requested-re-imagining-the-work-of-the-diverse-speaker-training-group-wpdiversity/\">share your feedback as comments on the post</a> by Dec. 18.</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 02 Dec 2020 09:13:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Hari Shanker R\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:73:\"WPTavern: New Plugin Adds Google-Doc Style Commenting to Gutenberg Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=108408\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/new-plugin-adds-google-doc-style-commenting-to-gutenberg-blocks?utm_source=rss&utm_medium=rss&utm_campaign=new-plugin-adds-google-doc-style-commenting-to-gutenberg-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3328:\"<p><a href=\"https://www.multidots.com/\">Multidots</a>, a development agency and WordPress VIP Agency Partner, has released a plugin that brings content collaboration to the block editor. The <a href=\"https://wordpress.org/plugins/commenting-feature/\">Google-Doc Style Gutenberg Block Commenting</a> plugin landed on WordPress.org in October and is just starting to gain traction.</p>\n\n\n\n<p>It adds inline commenting to the editor where users can highlight text or select entire blocks and leave a comment. Other users can leave comments and/or mark the thread as resolved for a collaborative editing experience. Alternatively, the post author can use comments for making notes on sections that need to be improved or reviewed prior to publishing. The features support the following editorial workflow:</p>\n\n\n\n<ul><li>Add comments on Gutenberg blocks</li><li>Reply to comment</li><li>Get feedback</li><li>Resolve it</li><li>Get email notification of resolved comments</li></ul>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Multidots has a <a href=\"https://www.multidots.com/gutenberg-commenting-demo/\">live demo</a> set up where you can test leaving comments, replies, and marking threads as resolved. The plugin is currently compatible with a range of text-based blocks that are part of a page or post. Commenting can be accessed by highlighting text and then clicking on the dropdown arrow in the toolbar. Inline comments can be displayed or hidden via the icon in the top toolbar.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>The plugin restricts adding and editing comments to Super Administrators, Administrators, and Editors. These user roles can edit their own comments but cannot edit or delete those added by other users.</p>\n\n\n\n<p>Google-Doc Style Gutenberg Block Commenting could be useful for organizations where multiple teams need to review content before publishing. Not having the ability to collaborate using the block editor may even be a deal breaker for some teams that are considering WordPress. When collaborating on posts in the past I have often used Google Docs just for the ability to give inline comments with notifications. This plugin cuts many time-consuming steps out of that process, such as obtaining collaborators&rsquo; Gmail addresses, pasting the most recent version of the post into a document, and ultimately having to paste it all back into the editor. </p>\n\n\n\n<p>The plugin&rsquo;s authors consider this a beta version and plan to add more features based on community feedback. After testing it, I found that resolved threads seem to disappear, but it might be helpful to have a lasting record of them. Users cannot comment on images or other types of non-text-based blocks, and this seems somewhat limiting. There are no notifications for comments &ndash; only resolved threads, which makes it difficult to know when content needs further review.</p>\n\n\n\n<p>Multidots is planning for the next release to be a more optimized version with enhanced commenting features, including the ability to leave popup suggestions for adding/removing certain text at a specific location and asynchronous commenting. Anyone interested in following the progress or contributing can <a href=\"https://github.com/multidots/gutenberg_commenting/\">find the project on GitHub</a>.</p>\n\n\n\n<p></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 02 Dec 2020 04:40: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: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:53:\"WordPress.org blog: WordPress 5.6 Release Candidate 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9274\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2020/12/wordpress-5-6-release-candidate-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2247:\"<p>The second release candidate for WordPress 5.6 is here!</p>\n\n\n\n<p>WordPress 5.6 is slated for release on <strong>December 8, 2020</strong>, and we need <em>your</em> help to get there—if you haven’t tried 5.6 yet, now is the time!</p>\n\n\n\n<p>You can test WordPress 5.6 release candidate 2 in two ways:</p>\n\n\n\n<ul><li>Try the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (choose the “bleeding edge nightlies” option).</li><li>Or <a href=\"https://wordpress.org/wordpress-5.6-RC2.zip\">download the release candidate here (zip)</a>.</li></ul>\n\n\n\n<p>Thank you to all of the contributors who tested the&nbsp;Beta releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.</p>\n\n\n\n<h2>Plugin and Theme Developers</h2>\n\n\n\n<p>Please test your plugins and themes against WordPress 5.6 and update the <em>Tested up to</em> version in the readme file to 5.6. If you find compatibility problems, please be sure to post to the <a href=\"https://wordpress.org/support/forum/alphabeta/\">support forums</a>. That way, those can be figured out before the final release. </p>\n\n\n\n<p>For a more detailed breakdown of the changes included in WordPress 5.6, check out the <a href=\"https://wordpress.org/news/2020/10/wordpress-5-6-beta-1/\">WordPress 5.6 beta 1 post</a>. The <a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">WordPress 5.6 Field Guide</a> is also out! It’s your source for details on all the major changes.</p>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Do you speak a language other than English? <a href=\"https://translate.wordpress.org/projects/wp/dev\">Help translate WordPress into more than 100 languages!</a></p>\n\n\n\n<p><em><strong>Think you found a bug?</strong> Post it to the <a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a> in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible bug report you can <a href=\"https://make.wordpress.org/core/reports/\">file one on WordPress Trac</a>. Don&#8217;t forget to check <a href=\"https://core.trac.wordpress.org/tickets/major\">the list of known bugs</a></em>!</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 01 Dec 2020 22:09:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:\"\";}}}}}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:92:\"WPTavern: Block-Based Bosco, Second Full-Site Editing Theme Lands in the WordPress Directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=108321\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:227:\"https://wptavern.com/block-based-bosco-second-full-site-editing-theme-lands-in-the-wordpress-directory?utm_source=rss&utm_medium=rss&utm_campaign=block-based-bosco-second-full-site-editing-theme-lands-in-the-wordpress-directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5489:\"<img />\n\n\n\n<p class=\"has-drop-cap\">Fr&auml;nk Klein, a Principal Engineer at Human Made, is now the second theme developer to release a block-based theme to the WordPress theme directory. <a href=\"https://wordpress.org/themes/block-based-bosco/\">Block-Based Bosco</a> is a recreation of his <a href=\"https://wordpress.org/themes/bosco/\">Bosco</a> theme, which he released in 2014.</p>\n\n\n\n<p>Block-based themes, also called FSE (full-site editing) themes, are currently experimental. They require the use of the Gutenberg plugin, which will automatically detect their structure and activate the beta version of the site editor. This system allows users to experience a WordPress install that is comprised entirely of blocks. Widgets, nav menus, and the customizer screens are out. Everything from posts to site headers to navigation is handled through HTML templates, which users can customize via the site editor. It is still a raw experience but continually improves with each update of the Gutenberg plugin.</p>\n\n\n\n<p>Just over a month ago, Themes Team representative Ari Stathopoulos <a href=\"https://wptavern.com/q-first-fse-wordpress-theme-now-live\">released the first block-based theme</a>, named Q, to the official theme directory. It was both a milestone in WordPress theming history and an invitation for developers to follow his lead.</p>\n\n\n\n<p>We have since seen the initial work toward a <a href=\"https://wptavern.com/twenty-twenty-one-blocks-theme-launching-as-a-separate-project\">block-based version</a> of the upcoming Twenty Twenty-One default theme. It is not yet in the directory, but the community should expect it soon.</p>\n\n\n\n<p>Developers like Klein and Stathopoulos are paving the way for others. For those who do not have the time or the inclination to scour the Gutenberg plugin&rsquo;s code or follow dozens of tickets, they can take the easy route. Study the code of people who have done the legwork.</p>\n\n\n\n<p>Klein has also written a detailed post titled <a href=\"https://wpdevelopment.courses/articles/full-site-editing-theme-learnings/\">What I Learned Building a Full-Site Editing Theme</a> in which he goes into detail about his experience. Despite his optimism for the future of theming, he does not shy away from the problems he stumbled upon. It is a must-read for any theme author who is preparing to take the plunge into block-based theme building.</p>\n\n\n\n<p>One thing that some developers may find surprising or may even make them feel slightly uncomfortable is that Klein spent much of his development time working from the site editor rather than in a code editor. &ldquo;It&rsquo;s likely that this will be the future workflow for creating themes,&rdquo; he wrote. &ldquo;Because not only can you edit a theme visually, but it&rsquo;s also much more practical than writing block markup by hand. Especially because the interface makes it easy to discover the different options offered by blocks, so that you can adjust them as needed for your desired theme design.&rdquo;</p>\n\n\n\n<h2>About the Theme</h2>\n\n\n\n<img />Block-Based Bosco in the site editor.\n\n\n\n<p class=\"has-drop-cap\">Block-Based Bosco is relatively simple. It is a one-column, no-sidebar theme, which is what most block-based themes will look like at the moment.</p>\n\n\n\n<p>&ldquo;Full-site editing themes are still missing a lot of essential features,&rdquo; wrote Klein. &ldquo;Therefore it&rsquo;s important to choose a theme design that fits with these constraints. Else you&rsquo;re going to have a very frustrating experience.&rdquo;</p>\n\n\n\n<p>Unlike Q, which is a bare-bones theme primarily for testing theme-related features, Block-Based Bosco is based on a design that users might want to actually use on a site, at least someday. Currently, full-site editing is not yet ready for use with production sites. The theme design holds up well for a simple personal blog.</p>\n\n\n\n<p>There are things the theme could do better in the short term. Offering support for wide and full alignments would be ideal, particularly for a one-column theme. The editor and front-end content width also do not match, so it is not a perfect what-you-see-is-what-you-get experience. These are not make-or-break features for these types of experimental themes at this point. We are simply in the testing ground stage.</p>\n\n\n\n<p>Right now, end-users need to start tinkering with themes like Block-Based Bosco &mdash; please do so on a test install and not a live site &mdash; and offering feedback. They also allow other developers to get more comfortable with a new system before it suddenly feels like it comes crashing down in 2021.</p>\n\n\n\n<h2>Opening Up the Theme Directory</h2>\n\n\n\n<p class=\"has-drop-cap\">One thing is obvious at this point. The WordPress theme directory needs to allow theme authors to upload block-based themes without hacks or other workarounds. Block-Based Bosco and similar themes are currently being shipped with dummy files, such as <code>header.php</code> and <code>footer.php</code>, and unnecessary PHP code in <code>functions.php</code> to bypass the Theme Check system. With these extra files and code removed, block-based themes are minuscule in comparison to traditional WordPress themes.</p>\n\n\n\n<p>There is an <a href=\"https://meta.trac.wordpress.org/ticket/5504\">open ticket</a> on the WordPress Meta Trac and a <a href=\"https://github.com/WordPress/theme-check/pull/280\">patch for the Theme Check plugin</a>. Someone needs to pull the trigger and make it happen.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 01 Dec 2020 21:19: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: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:113:\"WPTavern: Admin 2020 Version 2 Introduces New Lite Version, Better Plugin Compatibility, and Modular Architecture\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=108302\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/admin-2020-version-2-introduces-new-lite-version-better-plugin-compatibility-and-modular-architecture?utm_source=rss&utm_medium=rss&utm_campaign=admin-2020-version-2-introduces-new-lite-version-better-plugin-compatibility-and-modular-architecture\";s: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:5328:\"<img />\n\n\n\n<p>Six months ago, <a href=\"https://admintwentytwenty.com/\">Admin 2020</a> captured the attention of WordPress users with its fresh approach to skinning the admin screens. <a href=\"https://admintwentytwenty.com/admin-2-is-here/\">Version 2</a> of the plugin has been completely rewritten to support a modular architecture so users can enable or disable features, or selectively enable them&nbsp;by user role or username. Some users prefer the default menu but want to be able to categorize their media into folders with the plugin&rsquo;s CMS-friendly architecture for organizing media and posts. This update significantly improves performance for those who don&rsquo;t require the analytics, admin bar, menu, or other features. </p>\n\n\n\n<p>The plugin now has a new settings interface that is less cluttered than the previous version.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>&ldquo;Admin 2020 started off as a WordPress admin theme, and that was always at the core of the plugin,&rdquo; developer Mark Ashton said. &ldquo;As we grew, we added more and more features on top of that and it became very difficult in its current iteration to separate those feature sets, or disable some features and let others carry on.&rdquo;</p>\n\n\n\n<p>Version 2 also greatly improves compatibility with other plugins. Ashton was spending a lot of time adding support for other plugins, which slowed down development. The new approach to compatibility causes fewer styling conflicts and works without having to add custom stylesheets for other plugins. Prior to this version, Admin 2020 disabled 90% of WordPress admin styling and applied its own. </p>\n\n\n\n<p>&ldquo;While this gave us complete control over layouts and styling, it was one of the reasons we had to spend a lot of time adding support for other plugins,&rdquo; Ashton said. &ldquo;So for version 2, we kept the WP styling (most of it anyway) and applied a lightweight theme on top&nbsp;of it. The end result is a theme that is more refined, quicker, and the most compatible we have ever put out.<br />Usually the only plugins we have problems with these days are the ones that actively disable non standard WP scripts and styles, which obviously breaks admin 2020&rsquo;s layout.&rdquo;</p>\n\n\n\n<p>In the interest of keeping Admin 2020 lightweight, the plugin now uses a custom build of the <a href=\"https://getuikit.com/\">UIkit</a> framework that is more tailored to its specific use case. </p>\n\n\n\n<p>&ldquo;Instead of having uikit as a base, and then layering on top of it, we just tailored it to suit the plugin needs and thanks to the wonders of scss it is an incredibly easy framework to modify,&rdquo; Ashton said. &ldquo;Doing this also allowed us to support RTL much easier which was a very common feature request.&rdquo;</p>\n\n\n\n<h2>New Admin 2020 Lite Version Offers Basic Features, Coming to WordPress.org in 2021</h2>\n\n\n\n<p>Admin 2020 is now available on the plugin&rsquo;s website in a Lite version for free. In recognition of WordPress.org&rsquo;s undeniable force as a distribution channel, Ashton is considering changing his previous strategy of pursuing a fully commercial model to embrace the idea of marketing a free plugin with a paid upgrade. </p>\n\n\n\n<p>&ldquo;Admin 2020 has grown so much since we launched in May this year and it&rsquo;s no longer just an admin theme,&rdquo; Ashton said. &ldquo;In fact, we see it as more of an admin extension now that also has a theme. Because of this, we felt there are now enough features to be able to offer the lite and pro versions.&rdquo;</p>\n\n\n\n<p>With the new modular system in version 2, the free and commercial versions are the same plugins, except the lite version has the paid modules removed.</p>\n\n\n\n<p>&ldquo;This means the development of the two versions is synched and updates,&nbsp;new features and bug&nbsp;fixes all rollout at the same time,&rdquo; Ashton said. &ldquo;For the time being we are going to stick to our own distribution&nbsp;channel just to keep everything streamlined, but releasing through&nbsp;<a rel=\"noreferrer noopener\" href=\"http://wordpress.org/\" target=\"_blank\">wordpress.org</a>&nbsp;is something we have planned for next year.&rdquo;</p>\n\n\n\n<p>Launching a new business during a pandemic is no easy feat but Ashton has grown Admin 2020&rsquo;s user base to 3,642 active installations and is still looking to hire someone to assist in developing and maintaining the plugin.</p>\n\n\n\n<p>&ldquo;This has grown dramatically since the release of version 2 and will likely be around 5,000 or more in a week due to the sales from the Black Friday/Cyber Monday event,&rdquo; he said. </p>\n\n\n\n<p>Next up on the roadmap, Admin 2020 users can expect more customization options and deeper integration with WooCommerce. Ashton is currently working on the custom admin pages feature set that will allow users to create admin pages using the block editor and some of the more popular page builders. </p>\n\n\n\n<p>&ldquo;We are also working on expanding our WooCommerce integration with the idea of having a full suite of cards and data available on the overview page to help better visualize your business and sales,&rdquo; Ashton said. &ldquo;We are also going to be changing admin 2020&rsquo;s name towards the end of the year but I won&rsquo;t say what to just yet.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Nov 2020 23:36:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:97:\"WPTavern: Block Navigation Plugin Provides Missing Context-Based Outline for the WordPress 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=108323\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:239:\"https://wptavern.com/block-navigation-plugin-provides-missing-context-based-outline-for-the-wordpress-editor?utm_source=rss&utm_medium=rss&utm_campaign=block-navigation-plugin-provides-missing-context-based-outline-for-the-wordpress-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:4596:\"<p class=\"has-drop-cap\">&Aacute;lvaro Garc&iacute;a wrote the first code for his <a href=\"https://wordpress.org/plugins/block-navigation\">Block Navigation</a> plugin back in November 2018. It is one of those hidden gems that I wish I had known about two years ago as I began using the block editor. It has been available. I simply did not know about it until blindly stumbling upon it in a <a href=\"https://www.facebook.com/groups/gutenberghub/permalink/2844169185815585/\">discussion</a> in the WordPress Gutenberg Community group on Facebook.</p>\n\n\n\n<p>The goal of the plugin is to provide an alternative to the editor&rsquo;s current navigation. For the most part, it excels. WordPress has set the bar so low that any improvement seems like a godsend.</p>\n\n\n\n<p>The plugin adds a new sidebar panel titled Block Navigation. That panel then lists each block with the added context needed to understand what block it is associated with in the content. For example, a Paragraph block in the navigation list will display its first few words. Other blocks do the same. Images and galleries in the list display their respective thumbnails. It handles nested blocks too.</p>\n\n\n\n<p>All users must do is search for and click on the block they want to jump to in the content.</p>\n\n\n\n<img />Navigating to  specific paragraph in the document.\n\n\n\n<p>The plugin is packed with several other features. Users can shift blocks up and down from the navigation panel. They can also move blocks anywhere in the document with the click of a button or remove them altogether.</p>\n\n\n\n<p>One of the more interesting features of the Block Navigation plugin is its ability to log a block&rsquo;s data to the console. For developers, this could be a handy feature to quickly look up information for a block. While I doubt the average user would use it, there might be some potential applications for support requests, particularly with third-party block plugins.</p>\n\n\n\n<img />Console log of a block&rsquo;s data.\n\n\n\n<p>The downside of the plugin is that it does not provide a color scheme that simply matches the default WordPress color palette. However, it does provide a dozen color options for users to choose from. The Banana (light) scheme seemed the least out of place.</p>\n\n\n\n<p>With the navigation being handled in the sidebar, it could interfere with some users&rsquo; workflows. For users who prefer to keep the block options sidebar available at all times, they will need to switch back and forth between sidebars. The plugin does provide a button for switching to each block&rsquo;s setting via its submenu (vertical ellipsis icon) in the navigation list.</p>\n\n\n\n<p>The thing that would make this plugin better would be putting it into the editor toolbar, replacing the current Outline dropdown.</p>\n\n\n\n<h2>It Should Be a Core WordPress Feature</h2>\n\n\n\n<p class=\"has-drop-cap\">The block editor&rsquo;s Outline dropdown is lackluster at best. For short posts, it is unnecessary. For long posts, there is no context for any of the blocks in the list. The goal is to be able to jump to specific points in the document without scrolling. However, unless you know the exact location in the block you want to jump to, it can sometimes be impossible to use the feature.</p>\n\n\n\n<img />Outline dropdown.\n\n\n\n<p>The Document Outline section of the Details dropdown provides some much-needed context. It displays the post&rsquo;s headings. However, this outline does not allow users to click on an item and jump to its associated block.</p>\n\n\n\n<img />Details dropdown.\n\n\n\n<p>Paal Joachim Romdahl proposed a fix for the Outline dropdown in October 2018. &ldquo;What about just using the icon and then showing some of the text in the beginning of the paragraph?&rdquo; he asked in a <a href=\"https://github.com/WordPress/gutenberg/issues/11010\">GitHub ticket</a> that has seen no discussion for nearly a year.</p>\n\n\n\n<div class=\"wp-block-image\"><img />Merged dropdowns.</div>\n\n\n\n<p>There is currently an <a href=\"https://github.com/WordPress/gutenberg/pull/14956\">open pull request</a> on GitHub to merge the Details and Outline dropdowns in the toolbar. The original proposal added a tabbed interface. However, an alternative patch without the tabs proposed in the same ticket would merge the best of both worlds by adding the more-detailed structural outline while linking to the blocks in the document.</p>\n\n\n\n<p>The only question left now is whether I can still update my <a href=\"https://wptavern.com/wordpress-5-7-wish-list-save-block-editor-settings-per-user\">WordPress 5.7 wish list</a> to include this feature.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Nov 2020 23:03:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:61:\"BuddyPress: BuddyPress 6.4.0 Maintenance and Security Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=315780\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://buddypress.org/2020/11/buddypress-6-4-0-maintenance-and-security-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1569:\"<p><a href=\"https://downloads.wordpress.org/plugin/buddypress.6.4.0.zip\">BuddyPress 6.4.0</a>&nbsp;is now available. This is a security and maintenance release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.</p>\n\n\n\n<p>The 6.4.0 release addresses one security issue: non-capable users could add a style attributes to “span” and “p” elements in possible rich text fields of their profile page. The vulnerability has been fixed.</p>\n\n\n\n<p>Version 6.4.0 also fixes 7 bugs, including compatibility updates to welcome <a href=\"https://www.php.net/releases/8.0/en.php?lang=en\">PHP 8.0 release</a> (Congratulations to all PHP 8.0 contributors!).</p>\n\n\n\n<p>For complete details, visit the&nbsp;<a href=\"https://codex.buddypress.org/releases/version-6-4-0/\">6.4.0 changelog</a>.</p>\n\n\n\n<p>Update to BuddyPress 6.4.0 today in your WordPress Dashboard, or by&nbsp;<a href=\"https://wordpress.org/plugins/buddypress/\">downloading from the WordPress.org plugin repository</a>.</p>\n\n\n\n<h2>Many thanks to 6.4.0 contributors&nbsp;<span class=\"dashicons dashicons-heart\"></span></h2>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/johnjamesjacoby\">John James Jacoby (johnjamesjacoby)</a>, <a href=\"https://profiles.wordpress.org/zeldatea/\">Zeldatea</a>, <a href=\"https://profiles.wordpress.org/dd32/\">Dion Hulse</a>, <a href=\"https://profiles.wordpress.org/r-a-y/\">Ray (r-a-y)</a>, <a href=\"https://profiles.wordpress.org/dcavins/\">David Cavins (dcavins)</a> &amp; <a href=\"https://profiles.wordpress.org/imath/\">Mathieu Viet (imath)</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 Nov 2020 22:32:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:65:\"WordPress Foundation: Open Source Workshops: November 2020 report\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=150204\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wordpressfoundation.org/2020/open-source-workshops-november-2020-report/\";s: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:3597:\"<p>The WordPress Foundation has been organizing <a href=\"https://wordpressfoundation.org/2018/open-source-training-events-announced/\">Introduction to Open Source workshops</a>, as part of our continuing efforts to educate the public about WordPress and related open-source software (OSS). In 2019, as part of our goal of organizing workshops in parts of the world with less participation in open source, we held <a href=\"https://wordpressfoundation.org/2019/successful-open-source-workshops-in-bhutan-india-pakistan-and-angola/\">four successful workshops</a> in India, Pakistan, Bhutan, and Thimphu.&nbsp;</p>\n\n\n\n<p>By March 2020, the COVID-19 pandemic had engulfed the world, forcing community organizers to cancel all in-person events. Unfazed by these challenges, our community organizers pivoted to online events by organizing <a href=\"https://wordpressfoundation.org/2020/charity-hackathons-august-2020-report/\">four successful online charity hackathons</a> in <a href=\"https://doaction.org/ja/event/japan-2020/\">Japan</a>, <a href=\"https://doaction.org/event/south-africa-2020/\">South Africa</a>, <a href=\"https://doaction.org/event/india-2020/\">India</a>, and <a href=\"https://doaction.org/event/nigeria-2020/\">Nigeria</a>, so far. The Introduction to Open Source workshops have also moved online. The <a href=\"https://learn.wordpress.org/workshop/introduction-to-open-source/\">workshop</a> is now available online as part of <a href=\"https://learn.wordpress.org/\">Learn WordPress</a>, which is a brand new initiative from WordPress contributor teams to help people learn how to use, build for, and contribute to WordPress. Community members across the world can now<a href=\"https://learn.wordpress.org/workshop/introduction-to-open-source/\"> learn about Open-Source</a> safely from the comfort of their homes and test their knowledge using <a href=\"https://learn.wordpress.org/quiz/introduction-to-open-source/\">the embedded quiz</a>. The workshops are also followed by <a href=\"https://www.meetup.com/learn-wordpress-discussions/\">discussion groups</a>, where participants can discuss their learnings in real-time and find answers to their questions.&nbsp;&nbsp;</p>\n\n\n\n<p>As of November 2020, the Introduction to Open-source workshop video has been viewed 757 times. Three online discussion group events with over 152 RSVPs were also held successfully. Sign-ups are open for two more discussion groups that are listed below:</p>\n\n\n\n<ul><li><a href=\"https://www.meetup.com/learn-wordpress-discussions/events/274841875/\">Tuesday, December 8 2020, at 6:00 AM UTC</a></li><li><a href=\"https://www.meetup.com/learn-wordpress-discussions/events/274841881/\">Wednesday, December 16 2020, at 4:00 PM UTC</a></li></ul>\n\n\n\n<p>You can watch the <a href=\"https://learn.wordpress.org/workshop/introduction-to-open-source/\">workshop video</a> and participate in these discussion groups to learn about open-source software and find answers to your questions on open-source.</p>\n\n\n\n<p>In addition to these scheduled discussion groups, community organizers can organize <a href=\"https://make.wordpress.org/community/handbook/virtual-events/organize-learn-wordpress-discussion-groups-for-your-wordpress-meetup/\">their own online discussion groups</a> or hold online watch parties for the <a href=\"https://learn.wordpress.org/workshop/introduction-to-open-source/\">Introduction to Open-Source workshop</a>.&nbsp;</p>\n\n\n\n<p>Given the global spread of the COVID-19 pandemic, WordPress Foundation events are likely to be held online in 2021. We will be announcing our plans for 2021 events later this year.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 Nov 2020 09:05:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:38:\"WPTavern: Something To Be Thankful For\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=108221\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://wptavern.com/something-to-be-thankful-for?utm_source=rss&utm_medium=rss&utm_campaign=something-to-be-thankful-for\";s: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:4328:\"<img />\n\n\n\n<p class=\"has-drop-cap\">Over the past several weeks, I have received around four dozen emails, texts, PMs, and other messages related to Black Friday and Cyber Monday deals. Last year, we ran a <a href=\"https://wptavern.com/wordpress-black-friday-sales-roundup\">roundup of deals</a> happening throughout the WordPress ecosystem.  However, we are not running such a post this year. It took a solid week to compile and piece together the previous article. It was a lot of work for what was a statistical dud. Readership tends to wane around holidays as people spend more time offline and with their families.</p>\n\n\n\n<p>Plus, I firmly believe that our readers would rather see what we have to say about a particular product than simply scroll through a list of offers that are already widely shared on Twitter, Facebook, and elsewhere.</p>\n\n\n\n<p>As George Olaru, the CEO of Pixelgrade, wrote in <em><a href=\"https://pixelgrade.com/upstairs/discounts/\">I discount, you discount, we both lose</a></em>, software is not a perishable food item. It is not at risk of spoilage in a few days, and if it is, we have a real problem. On the flip side, some small businesses rely on this holiday to generate a large portion of their yearly revenue. However, we should all have some serious conversations about whether it is healthy for discounted software to permeate the WordPress plugin and theme markets every time a holiday rolls around. Whatever your stance, Olaru&rsquo;s piece is worth reading and thinking on.</p>\n\n\n\n<p>It is also tough to get into the holiday spirit this year. With Covid-19, the Black Friday markets have changed, which is probably not a bad thing on the whole &mdash; <em>do we all really need to pile into stores to fight over the latest gadgets?</em> The pandemic has also meant that families have had to make hard decisions about gatherings. The Tadlock family decided to cancel our pre-Thanksgiving/reunion we have in early November. We host it early because the doctors and nurses in the family often have to work on the holiday, and they agreed that a large gathering was not ideal. Fortunately, we live in an era where we can connect with each other in moments and from vast distances.</p>\n\n\n\n<p>No, it did not feel right to do a sales roundup this year. Instead, I wanted to get back to the root of the Thanksgiving holiday, at least what I was taught the holiday was supposed to be about.</p>\n\n\n\n<p>While tomorrow&rsquo;s Thanksgiving holiday is an American tradition, I am certain our readers abroad can join in the celebration. It is a day of giving thanks for the blessings of the previous year. In times past, this has often meant being thankful for the harvest and having food on the table. Today, it still means the same to many. However, the holiday is all about counting our blessings, and that is something we should all take time to do.</p>\n\n\n\n<p>This year, the thing I am most thankful for is the community, the people who all band together to create the most used CMS on the web, the people who evangelize the platform, and the people who continually take part in this grand experiment.</p>\n\n\n\n<p>One of the things I attempt to do when writing is to share exciting things happening in our little corner of the world. Yes, I am often critical too. This is because I want to see people and companies strive to create better themes, plugins, and other products. For those times when I stretch to hyperbole or perhaps lean toward the negative, know that it comes from a place that is hoping for your success. It is hard to balance at times, but I am thankful that I can do this day in and day out.</p>\n\n\n\n<p>After writing for the Tavern for over a year now, I feel like I am on a wondrous journey with so many of you. Whether it is a random message just to say hello or a ping about a new product, I look forward to seeing it all.</p>\n\n\n\n<p>These human-to-human connections were not something I was expecting as I began this gig. Thank you to everyone who has made that possible.</p>\n\n\n\n<p>Let&rsquo;s all take a day and share some of the WordPress-related things we are thankful for this year &mdash; <em>we can all save our block editor criticisms for tomorrow</em>. It has been a rough year. We could all really use some positivity right now.</p>\n\n\n\n<p>What are you thankful for?</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 25 Nov 2020 19:51:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:67:\"WPTavern: Getting Your WordPress Plugins and Themes Ready for PHP 8\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=108160\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:179:\"https://wptavern.com/getting-your-wordpress-plugins-and-themes-ready-for-php-8?utm_source=rss&utm_medium=rss&utm_campaign=getting-your-wordpress-plugins-and-themes-ready-for-php-8\";s: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:7380:\"<p>On Monday, WordPress core contributor Jonathan Desrosiers published a <a rel=\"noreferrer noopener\" href=\"https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/\" target=\"_blank\">detailed post</a> on the Make WordPress Core blog about the upcoming PHP 8 release and how it affects WordPress.</p>\n\n\n\n<h2>PHP 8 Is Coming</h2>\n\n\n\n<p>Scheduled for release on <a rel=\"noreferrer noopener\" href=\"https://wiki.php.net/todo/php80\" target=\"_blank\">November 26, 2020</a>, PHP 8 is the next major update to our favorite scripting language. While previous PHP releases have not had too much of an adverse effect on the WordPress ecosystem, this update has some breaking changes that could affect backward compatibility. It should also be noted that many features that were deprecated in PHP 7.x will now be removed in PHP 8.</p>\n\n\n\n<h2>The Status of WordPress Core</h2>\n\n\n\n<p>In his post, Desrosiers highlights the work that has been done to keep the core software up to date.  &ldquo;WordPress Core aims to be compatible with PHP 8.0 in the 5.6 release (currently scheduled for December 8, 2020),&rdquo; he wrote. </p>\n\n\n\n<p>However, this does not mean it is safe to upgrade to PHP 8 when WordPress 5.6 is released.  WordPress is rarely run just on its own and usually relies on at least one theme and a collection of plugins to function as a blog or web site. As such, he points out, &ldquo;The state of PHP 8 support within the broader ecosystem (plugins, themes, etc.) is impossible to know. For that reason, WordPress 5.6 should be considered &lsquo;beta compatible&rsquo; with PHP 8<strong>.</strong>&ldquo;</p>\n\n\n\n<p>What this means, essentially, is that until most major themes and plugins are PHP 8 compatible, WordPress cannot be considered fully compatible.</p>\n\n\n\n<h2>Understand How PHP 8 Could Affect Your Plugin or Theme</h2>\n\n\n\n<p>Companies like Yoast have been preparing for this for a little while now. In late October, Yoast CTO Omar Reiss, along with fellow contributors Juliette Reinders Folmer, maintainer of the <a rel=\"noreferrer noopener\" href=\"https://github.com/WordPress/WordPress-Coding-Standards\" target=\"_blank\">WordPress Coding Standards Sniffs for PHPCS</a>, and Yoast DevOps manager Herre Groen, compiled and published a <a rel=\"noreferrer noopener\" href=\"https://developer.yoast.com/blog/the-2020-wordpress-and-php-8-compatibility-report/\" target=\"_blank\">comprehensive WordPress/PHP 8 compatibility report</a>. </p>\n\n\n\n<p>While I highly recommend you take the time to read through the entire report, it does outline the main reason that the PHP 8 upgrade could have such a drastic effect on large WordPress sites, especially the plugin and theme ecosystem.</p>\n\n\n\n<p>&ldquo;However, PHP 7.* versions have seen a far larger set of deprecations than previous versions of PHP. Where PHP 5.6 to PHP 7 was a relatively simple migration, going from 7.x to 8 could be very painful, especially for very old codebases, like WordPress and many of the plugins that are available for it. For well-typed codebases or codebases which have stayed up-to-date with the latest PHP versions, there isn&rsquo;t a big problem.&rdquo;</p>\n\n\n\n<p>As a maintainer of a few plugins, some built on code dating back eight years, it is worrisome that this upgrade could cause sites to break.</p>\n\n\n\n<img />PHPCompatibility repository.\n\n\n\n<h2>How to Prepare Yourself</h2>\n\n\n\n<p>I asked Reiss and Folmer what plugin and theme developers can do to get ready, and they shared some pointers.</p>\n\n\n\n<p>First and foremost, developers should inform themselves about the changes coming in PHP 8: read <a rel=\"noreferrer noopener\" href=\"https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/\" target=\"_blank\">the Make post about PHP 8</a>, read the <a rel=\"noreferrer noopener\" href=\"https://developer.yoast.com/blog/the-2020-wordpress-and-php-8-compatibility-report/\" target=\"_blank\">Yoast PHP8 Compatibility</a> report, read the &ldquo;<a rel=\"noreferrer noopener\" href=\"https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/\" target=\"_blank\">Migrating from PHP 7.4 to PHP 8.0</a>&rdquo; section of the PHP manual, and potentially dig deeper by reading the <a rel=\"noreferrer noopener\" href=\"https://github.com/php/php-src/blob/PHP-8.0/UPGRADING\" target=\"_blank\">UPGRADING doc in the PHP 8 branch</a> and the <a rel=\"noreferrer noopener\" href=\"https://wiki.php.net/rfc#php_80\" target=\"_blank\">RFCs for PHP 8</a>.</p>\n\n\n\n<p>Some available tools can be used to help look for incompatibilities:</p>\n\n\n\n<ul><li>Run PHP lint on PHP 8 over their code, either via the &nbsp;<code>php -l</code>&nbsp;command (making sure to iterate over all files) or by using <a rel=\"noreferrer noopener\" href=\"https://github.com/php-parallel-lint/PHP-Parallel-Lint\" target=\"_blank\">PHP Parallel Lint</a>.</li><li>Run <a rel=\"noreferrer noopener\" href=\"https://github.com/PHPCompatibility/PHPCompatibility\" target=\"_blank\">PHPCompatibility</a> over their code: it should be noted that nearly all PHP 8 related sniffs are in the as-of-yet-not-yet-released version 10.0.0 of PHPCompatibility, so people would need to use the&nbsp;<code>develop</code>&nbsp;branch or via Composer&nbsp;<code>dev-develop</code>&nbsp;for the time being, until version 10.0.0 is released. </li><li>Run the unit/integration tests for the plugin or theme on PHP 8 and fix anything which that comes up as an error. This will often mean that the test suite first needs to be made compatible with PHPUnit 9.3+. The <a rel=\"noreferrer noopener\" href=\"https://github.com/Yoast/PHPUnit-Polyfills\" target=\"_blank\">PHPUnit Polyfills</a> package and <a rel=\"noreferrer noopener\" href=\"https://github.com/Yoast/wp-test-utils\" target=\"_blank\">WP Test Utils</a> package (both published under the Yoast GitHub organization) can help with this. It&rsquo;s also important to note a considerable test coverage is needed to make this reliable.</li><li>Run the WordPress <a rel=\"noreferrer noopener\" href=\"https://make.wordpress.org/core/handbook/testing/automated-testing/phpunit/\" target=\"_blank\">unit tests</a> and WordPress <a rel=\"noreferrer noopener\" href=\"https://make.wordpress.org/core/2019/06/27/introducing-the-wordpress-e2e-tests/\" target=\"_blank\">e2e tests</a> with your plugin activated, and fix any issues that arise.</li><li>Check whether the (strict) code coverage of said tests is high enough and if not, add more tests, making sure both happy and unhappy paths are covered.</li><li>If there are no tests, test everything manually, focusing especially on the &ldquo;unhappy paths&rdquo;, and expect to receive bug reports for the foreseeable future. At the same time, this is probably a good time to look into implementing unit/integration tests for your plugin or theme.</li></ul>\n\n\n\n<h2>There Is Still Time, But It Is Running Out</h2>\n\n\n\n<p>As Desrosiers pointed out in the Make post, WordPress is only officially aiming to be PHP 8 ready by the time 5.6 is released in early December. Potentially, this means that many WordPress-focused hosting companies will only consider offering upgrades to their customers once WordPress core is compatible. So as plugin and theme developers, we have some time to test our products and get them ready, but that window is closing fast. </p>\n\n\n\n<p>Fortunately for us, the knowledge and tools to get up to date are out there.  We merely need to put them into action.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 25 Nov 2020 17:03: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: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: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:70:\"WPTavern: WordPress 5.7 Wish List: Save Block Editor Settings Per User\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=108176\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:183:\"https://wptavern.com/wordpress-5-7-wish-list-save-block-editor-settings-per-user?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-7-wish-list-save-block-editor-settings-per-user\";s: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:4651:\"<p class=\"has-drop-cap\">WordPress 5.6 development is winding down as we begin to close out the beta testing round, inching toward the final release on December 8. That means it is time to think about what WordPress 5.7 will look like. This is one of my favorite times of the WordPress development cycle because I get to see what others want to be added to the core platform. I also get to share a feature request of my own.</p>\n\n\n\n<p>Francesca Marano <a href=\"https://make.wordpress.org/core/2020/11/23/wordpress-5-7-whats-on-your-wishlist/\">opened the discussion</a> on the Make Core blog. She asks that people link to a specific ticket, which can be from WordPress Trac or the Gutenberg repository.</p>\n\n\n\n<p>One consideration for everyone&rsquo;s wish list is that 2021 will potentially see <a href=\"https://make.wordpress.org/core/2019/11/21/tentative-release-calendar-2020-2021/\">four major WordPress releases</a> rather than the typical three. WordPress 5.7 is tentatively scheduled to land on March 9, 2021. The team has scheduled future releases in three-month intervals. While the dates are not written in stone, it could mean each release&rsquo;s feature set might need to be scaled back to some small degree.</p>\n\n\n\n<p>Most features that land in WordPress 5.7 will be items that are already under development. Enhancements like <a href=\"https://wptavern.com/wordpress-5-6-release-team-pulls-the-plug-on-block-based-widgets\">block-based widgets</a> and <a href=\"https://wptavern.com/navigation-screen-sidelined-for-wordpress-5-6-full-site-editing-edges-closer-to-public-beta\">nav menus</a> that were punted from the 5.6 release should land early and be ready for a full three months of testing. The development team will also focus heavily on pushing an early/beta version of the site editor into core WordPress.</p>\n\n\n\n<p>There is still room for other things to land, and now is the time for everyone to make their case for their pet feature.</p>\n\n\n\n<p>Unlike past wish-list discussions, I am going to take a step back and control myself. Instead of asking for one of those big-ticket items that I know is unlikely to happen &mdash; <em>hello, <a href=\"https://wptavern.com/open-call-for-wordpress-5-5-tickets-whats-on-your-wish-list\">completed post type API</a> and <a href=\"https://wptavern.com/wordpress-5-6-wish-list-homepage-post-type-selection-and-block-management\">homepage post type selection</a></em> &mdash;, I will simply ask for something more practical.</p>\n\n\n\n<p>In WordPress 5.7, I want the block inspector tabs and some block option defaults to remain the same each time I write a new post.</p>\n\n\n\n<p>One of my biggest pet-peeves is with the image block in particular. Each time I add an image, I first close the Styles tab in the sidebar. I do not use it often, so it is not important enough to always be open. Then, I must switch the Image Size setting to Full Size from its default Large. I typically format my images for display before uploading and simply want to use the image at the size I uploaded. These are small things, but they break my workflow. As a daily writer, it has become a nuisance over time.</p>\n\n\n\n<img />Configuring image block settings.\n\n\n\n<p>These should be per-user settings. Each user&rsquo;s workflow is different, so WordPress likely needs to handle this as user metadata or a similar method.</p>\n\n\n\n<p>I was unable to track down an open ticket for saving the tab state. There are over 2,600 currently-open issues. Maybe I did not nail down the right search terminology. Or, it may be a non-issue for other users.</p>\n\n\n\n<p>However, there is a two-year-old ticket for <a href=\"https://github.com/WordPress/gutenberg/issues/8663\">remembering the last image size</a> used. I was happy to find like-minded peers who share my frustration in this case. There is also a more recent ticket about <a href=\"https://github.com/WordPress/gutenberg/pull/20269\">storing the default image size</a> on a per-user basis. The feedback in the tickets shows a clear and present need for WordPress to fix this problem.</p>\n\n\n\n<p>A representative of Feast Design Co. noted in the first ticket, &ldquo;Every time somebody inserts an image they have to change the image size. This seems small but at 10 seconds per image x 5 images per post x 2 posts per week x 52 weeks per year, this is 86 minutes per year.&rdquo; I believe I can manage it in a little less than 10 seconds per image, but it stills knocks me out of my flow each time. It is a seemingly trivial issue, but the time wastage adds up for those who add many images to posts throughout the year.</p>\n\n\n\n<p>What is on your wish list for WordPress 5.7?</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 24 Nov 2020 21:43: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:\"\";}}}}}}}}}}}}}}}}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, 28 Dec 2020 22:15:12 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Mon, 28 Dec 2020 22:00:09 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20201208223423\";}','no'),(261,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1609236912','no'),(262,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1609193712','no'),(263,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1609236912','no'),(264,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b','<div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2020/12/introducing-learn-wordpress/\'>Introducing Learn WordPress</a></li><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2020/12/simone/\'>WordPress 5.6 “Simone”</a></li></ul></div><div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wptavern.com/navigate-the-content-canvas-with-the-block-editor-outline-wordpress-plugin?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=navigate-the-content-canvas-with-the-block-editor-outline-wordpress-plugin\'>WPTavern: Navigate the Content Canvas With the Block Editor Outline WordPress Plugin</a></li><li><a class=\'rsswidget\' href=\'https://buddypress.org/2020/12/buddypress-in-2020-its-a-wrap/\'>BuddyPress: BuddyPress in 2020, it’s a wrap!</a></li><li><a class=\'rsswidget\' href=\'https://ma.tt/2020/12/sotw-2020/\'>Matt: State of the Word 2020</a></li></ul></div>','no');

--
-- Table structure for table `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,
  PRIMARY KEY (`meta_id`),
  KEY `post_id` (`post_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_postmeta`
--

INSERT INTO `wp_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default'),(3,5,'_edit_lock','1608591902:1'),(4,5,'_edit_last','1'),(5,5,'_wp_page_template','page-home.php');

--
-- Table structure for table `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 AUTO_INCREMENT=7 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_posts`
--

INSERT INTO `wp_posts` VALUES (1,1,'2020-12-21 23:03:35','2020-12-21 23:03:35','<!-- wp:paragraph -->\n<p>Welcome to WordPress. This is your first post. Edit or delete it, then start writing!</p>\n<!-- /wp:paragraph -->','Hello world!','','publish','open','open','','hello-world','','','2020-12-21 23:03:35','2020-12-21 23:03:35','',0,'https://oneacademy.labcp.co/?p=1',0,'post','',1),(2,1,'2020-12-21 23:03:35','2020-12-21 23:03:35','<!-- wp:paragraph -->\n<p>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:</p>\n<!-- /wp:paragraph -->\n\n<!-- wp:quote -->\n<blockquote class=\"wp-block-quote\"><p>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&#241;a coladas. (And gettin\' caught in the rain.)</p></blockquote>\n<!-- /wp:quote -->\n\n<!-- wp:paragraph -->\n<p>...or something like this:</p>\n<!-- /wp:paragraph -->\n\n<!-- wp:quote -->\n<blockquote class=\"wp-block-quote\"><p>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.</p></blockquote>\n<!-- /wp:quote -->\n\n<!-- wp:paragraph -->\n<p>As a new WordPress user, you should go to <a href=\"https://oneacademy.labcp.co//wp/wp-admin/\">your dashboard</a> to delete this page and create new pages for your content. Have fun!</p>\n<!-- /wp:paragraph -->','Sample Page','','publish','closed','open','','sample-page','','','2020-12-21 23:03:35','2020-12-21 23:03:35','',0,'https://oneacademy.labcp.co/?page_id=2',0,'page','',0),(3,1,'2020-12-21 23:03:35','2020-12-21 23:03:35','<!-- wp:heading --><h2>Who we are</h2><!-- /wp:heading --><!-- wp:paragraph --><p>Our website address is: https://oneacademy.labcp.co.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>What personal data we collect and why we collect it</h2><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Comments</h3><!-- /wp:heading --><!-- wp:paragraph --><p>When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor&#8217;s IP address and browser user agent string to help spam detection.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Media</h3><!-- /wp:heading --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Contact forms</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Cookies</h3><!-- /wp:heading --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>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 &quot;Remember Me&quot;, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Embedded content from other websites</h3><!-- /wp:heading --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Analytics</h3><!-- /wp:heading --><!-- wp:heading --><h2>Who we share your data with</h2><!-- /wp:heading --><!-- wp:paragraph --><p>If you request a password reset, your IP address will be included in the reset email.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>How long we retain your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>What rights you have over your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>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.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Where we send your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>Visitor comments may be checked through an automated spam detection service.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Your contact information</h2><!-- /wp:heading --><!-- wp:heading --><h2>Additional information</h2><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>How we protect your data</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What data breach procedures we have in place</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What third parties we receive data from</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What automated decision making and/or profiling we do with user data</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Industry regulatory disclosure requirements</h3><!-- /wp:heading -->','Privacy Policy','','draft','closed','open','','privacy-policy','','','2020-12-21 23:03:35','2020-12-21 23:03:35','',0,'https://oneacademy.labcp.co/?page_id=3',0,'page','',0),(4,1,'2020-12-21 23:03:40','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2020-12-21 23:03:40','0000-00-00 00:00:00','',0,'https://oneacademy.labcp.co/?p=4',0,'post','',0),(5,1,'2020-12-21 23:04:48','2020-12-21 23:04:48','','Home','','publish','closed','closed','','home','','','2020-12-21 23:05:02','2020-12-21 23:05:02','',0,'https://oneacademy.labcp.co/?page_id=5',0,'page','',0),(6,1,'2020-12-21 23:04:48','2020-12-21 23:04:48','','Home','','inherit','closed','closed','','5-revision-v1','','','2020-12-21 23:04:48','2020-12-21 23:04:48','',5,'https://oneacademy.labcp.co/2020/12/21/5-revision-v1/',0,'revision','',0);

--
-- Table structure for table `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;

--
-- Dumping data for table `wp_term_relationships`
--

INSERT INTO `wp_term_relationships` VALUES (1,1,0);

--
-- Table structure for table `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 AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_term_taxonomy`
--

INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,1);

--
-- Table structure for table `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,
  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;

--
-- Dumping data for table `wp_termmeta`
--


--
-- Table structure for table `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 AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_terms`
--

INSERT INTO `wp_terms` VALUES (1,'Uncategorized','uncategorized',0);

--
-- Table structure for table `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,
  PRIMARY KEY (`umeta_id`),
  KEY `user_id` (`user_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB AUTO_INCREMENT=19 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_usermeta`
--

INSERT INTO `wp_usermeta` VALUES (1,1,'nickname','cappen-dev'),(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:\"4de04b3973eebd0cddd2b0d1e4a4f1d722a45a0b4532042fee39be661740ca1a\";a:4:{s:10:\"expiration\";i:1609366510;s:2:\"ip\";s:13:\"186.218.6.141\";s:2:\"ua\";s:114:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36\";s:5:\"login\";i:1609193710;}}'),(17,1,'wp_dashboard_quick_press_last_post_id','4'),(18,1,'community-events-location','a:1:{s:2:\"ip\";s:11:\"186.218.6.0\";}');

--
-- Table structure for table `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 AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_users`
--

INSERT INTO `wp_users` VALUES (1,'cappen-dev','$2y$10$y/vphOpxWD1Sn6PpuRDUfuLwSdHE8pNEjsdv0ocujEO9yFdLYb.rW','cappen-dev','dev@cappen.com','https://oneacademy.labcp.co//wp','2020-12-21 23:03:35','',0,'cappen-dev');


