WordPress was launched on 27 May 2003 and, yesterday, became an adult!
\n\n\n\nWordPress now powers 40% of the web.
\n\n\n\nTo celebrate, here is a list of 40 milestones that have led to this remarkable achievement.
\n\n\n\nGrab your favourite food and drink and dive in!
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://en-gb.wordpress.org/2021/05/28/belated-18th-birthday-wishes-wordpress/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:76:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"WordPress 5.7.2 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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://en-gb.wordpress.org/2021/05/13/wordpress-5-7-2-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:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://en-gb.wordpress.org/2021/05/13/wordpress-5-7-2-security-release/#respond\";s: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, 13 May 2021 10:27:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Security\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://en-gb.wordpress.org/?p=1436\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:356:\"WordPress 5.7.2 is now available. This security release features one security fix. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated. WordPress 5.7.2 is a short-cycle security release. The next major release will be version 5.8. You can update to […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Mark Robson\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2189:\"\nWordPress 5.7.2 is now available.
\n\n\n\nThis security release features one security fix. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated.
\n\n\n\nWordPress 5.7.2 is a short-cycle security release. The next major release will be version 5.8.
\n\n\n\nYou can update to WordPress 5.7.2 by downloading from WordPress.org, or by visiting your Dashboard → Updates and clicking “Update Now”.
\n\n\n\nIf you have sites that support automatic background updates, they’ve already started the update process.
\n\n\n\nOne security issue affecting WordPress versions between 3.7 and 5.7. If you haven’t yet updated to 5.7, all WordPress versions since 3.7 have also been updated to fix the following security issue:
\n\n\n\nThank you to the members of the WordPress security team for implementing these fixes in WordPress.
\n\n\n\nFor more information refer to the version 5.7.2 HelpHub documentation page.
\n\n\n\nThe 5.7.2 release was led by @peterwilsoncc and @audrasjb.
\n\n\n\nThank you to everyone who helped make WordPress 5.7.2 happen: @audrasjb, @ayeshrajans, @desrosj, @dd32, @peterwilsoncc, @SergeyBiryukov, and @xknown.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"https://en-gb.wordpress.org/2021/05/13/wordpress-5-7-2-security-release/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:76:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 5.7.1 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:88:\"https://en-gb.wordpress.org/2021/04/15/wordpress-5-7-1-security-and-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"https://en-gb.wordpress.org/2021/04/15/wordpress-5-7-1-security-and-maintenance-release/#respond\";s: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, 15 Apr 2021 11:16:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Security\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://en-gb.wordpress.org/?p=1405\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:399:\"WordPress 5.7.1 is now available! This security and maintenance release features 26 bug fixes in addition to two security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 4.7 have also been updated. WordPress 5.7.1 is a short-cycle security and maintenance release. The next major release will […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Mark Robson\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:8948:\"\nWordPress 5.7.1 is now available!
\n\n\n\nThis security and maintenance release features 26 bug fixes in addition to two security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 4.7 have also been updated.
\n\n\n\nWordPress 5.7.1 is a short-cycle security and maintenance release. The next major release will be version 5.8.
\n\n\n\nYou can download WordPress 5.7.1 by downloading from WordPress.org, or by visiting your Dashboard → Updates and clicking “Update Now”.
\n\n\n\nIf you have sites that support automatic background updates, they’ve already started the update process.
\n\n\n\nTwo security issues affect WordPress versions between 4.7 and 5.7. If you haven’t yet updated to 5.7, all WordPress versions since 4.7 have also been updated to fix the following security issues:
\n\n\n\nThank you to all of the reporters for privately disclosing the vulnerabilities. This gave the security team time to fix the vulnerabilities before WordPress sites could be attacked.
\n\n\n\nProps to Adam Zielinski, Pascal Birchler, Peter Wilson, Juliette Reinders Folmer, Alex Concha, Ehtisham Siddiqui, Timothy Jacobs and the WordPress security team for their work on these issues.
\n\n\n\nFor more information, browse the full list of changes on Trac, or check out the version 5.7.1 HelpHub documentation page.
\n\n\n\nThe 5.7.1 release was led by @peterwilsoncc and @audrasjb.
\n\n\n\nIn addition to the security researchers and release squad members mentioned above, thank you to everyone who helped make WordPress 5.7.1 happen:
\n\n\n\n99w, Adam Silverstein, Andrew Ozz, annalamprou, anotherdave, Ari Stathopoulos, Ayesh Karunaratne, bobbingwide, Brecht, Daniel Richards, David Baumwald, dkoo, Dominik Schilling, dragongate, eatsleepcode, Ella van Durpe, Erik, Fabian Pimminger, Felix Arntz, Florian TIAR, gab81, Gal Baras, Geoffrey, George Mamadashvili, Glen Davies, Greg Ziółkowski, grzim, Ipstenu (Mika Epstein), Jake Spurlock, Jayman Pandya, Jb Audras, Joen A., Johan Jonk Stenström, Johannes Kinast, John Blackbourn, John James Jacoby, Jonathan Desrosiers, Josee Wouters, Joy, k3nsai, Kelly Choyce-Dwan, Kerry Liu, Marius L. J., Mel Choyce-Dwan, Mikhail Kobzarev, mmuyskens, Mukesh Panchal, nicegamer7, Otshelnik-Fm, Paal Joachim Romdahl, palmiak, Pascal Birchler, Peter Wilson, pwallner, Rachel Baker, Riad Benguella, Rinat Khaziev, Robert Anderson, Roger Theriault, Sergey Biryukov, Sergey Yakimov, SirStuey, stefanjoebstl, Stephen Bernhardt, Sumit Singh, Sybre Waaijer, Synchro, Terri Ann, tigertech, Timothy Jacobs, tmatsuur, TobiasBg, Tonya Mork, Toru Miki, Ulrich, and Vlad T.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"https://en-gb.wordpress.org/2021/04/15/wordpress-5-7-1-security-and-maintenance-release/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:74:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:5:{s:0:\"\";a:8:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"WordPress 5.7 “Esperanza”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"https://en-gb.wordpress.org/2021/03/10/wordpress-5-7-esperanza/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://en-gb.wordpress.org/2021/03/10/wordpress-5-7-esperanza/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 10 Mar 2021 13:02:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://en-gb.wordpress.org/?p=1352\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:364:\"Meet “Esperanza”, the first WordPress release of 2021. “Esperanza” is named in honour of Esperanza Spalding, a modern musical prodigy. Her path as a musician is varied and inspiring – learn more about her and give her music a listen! With this new version, WordPress brings you fresh colours. The editor helps you work in a […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://s.w.org/images/core/5.7/about-57-drag-drop-image.mp4\";s:6:\"length\";s:6:\"183815\";s:4:\"type\";s:9:\"video/mp4\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Mark Robson\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:42301:\"\nWordPress 5.7 “Esperanza”
\n\n\n\nBringing you fresh colours in the admin, simpler interactions in the editor, and controls right where you need them, WordPress 5.7 lets you focus on the content you create.
\n\n\n\n\n\n\n\n\nMeet “Esperanza”, the first WordPress release of 2021. “Esperanza” is named in honour of Esperanza Spalding, a modern musical prodigy. Her path as a musician is varied and inspiring – learn more about her and give her music a listen!
\n\n\n\nWith this new version, WordPress brings you fresh colours. The editor helps you work in a few places you couldn’t before without getting into code or hiring a pro. The controls you use most are right where you need them. Layout changes that should be simple, are even simpler to make.
\n\n\n\nFont-size adjustment in more places: now, font-size controls are right where you need them in the List and Code blocks. No more trekking to another screen to make that single change!
\n\n\n\nReusable blocks: several enhancements make reusable blocks more stable and easier to use. And now they save automatically with the post when you click the Update button.
\n\n\n\nInserter drag-and-drop: drag blocks and block patterns from the inserter right into your post.
\n\n\n\n\n\n\n\nFull-height alignment: have you ever wanted to make a block, like the Cover block, fill the whole window? Now you can.
\n\n\n\nButtons block: now you can choose a vertical or a horizontal layout. And you can set the width of a button to a preset percentage.
\n\n\n\nSocial Icons block: now you can change the size of the icons.
\n\n\n\n\n\n\n\nThis new streamlined colour palette collapses all the colours that used to be in the WordPress source code down to seven core colours and a range of 56 shades that meet the WCAG 2.0 AA recommended contrast ratio against white or black.
\n\n\n\nFind the new palette in the default WordPress Dashboard colour scheme, and use it when you’re building themes, plugins, or any other components. For all the details, check out the Colour Palette developer note.
\n\n\n\nStarting now, switching a site from HTTP to HTTPS is a one-click move. WordPress will automatically update database URLs when you make the switch. No more hunting and guessing!
\n\n\n\nThe new Robots API lets you include the filter directives in the robots meta tag, and the API includes the max-image-preview: large
directive by default. That means search engines can show bigger image previews, which can boost your traffic (unless the site is marked not-public).
Now it’s simple to let iframes lazy-load. By default, WordPress will add a loading=\"lazy\"
attribute to iframe tags when both width and height are specified.
For years, jQuery helped make things move on the screen in ways the basic tools couldn’t – but that keeps changing, and so does jQuery.
\n\n\n\nIn 5.7, jQuery gets more focused and less intrusive, with fewer messages in the console.
\n\n\n\nCheck out the latest version of the WordPress Field Guide. It highlights developer notes for each change you may want to be aware of. WordPress 5.7 Field Guide.
\n\n\n\nThe WordPress 5.7 release comes to you from a small and experienced release squad:
\n\n\n\nThis release is the reflection of the hard work of 481 generous volunteer contributors. Collaboration occurred on nearly 250 tickets on Trac and over 950 pull requests on GitHub.
\n\n\n\n7studio, aaribaud, Aaron Brazell, Aaron D. Campbell, Aaron Jorbin, aaronrobertshaw, abagtcs, acerempel, activecoder, ad7six, Adam Bosco, Adam Silverstein, adamboro, Addison Stavlo, Ahmad Awais, Ahmed Saeed, Albert Juhé Lluveras, albertomake, Alex Lende, Alex Woollam, alex27, Alexander Lueken, alexstine, allancole, Allen Snook, almendron, Amanda Riu, ambienthack, Amol Vhankalas, Andrea Fercia, Andrei Draganescu, Andrew Duthie, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrew Serong, André Maneiro, Andy Fragen, Andy Peatling, Ankit Panchal, Anne McCarthy, Anthony Burchell, Anton Lukin, Anton Timmermans, Anyssa Ferreira, archon810, Ari Stathopoulos, Arslan Ahmed, Artur Piszek, Aurélien Denis, Ayesh Karunaratne, bartosz777, basscan, bduclos, becdetat, Bego Mario Garde, Ben Dwyer, Bernhard Reiter, Bernhard Reiter, bhanusinghkre, Birgir Erlendsson (birgire), Birgit Pauli-Haack, bobbingwide, bonniebeeman, Boone Gorges, Boy Witthaya, Brandon Kraft, Brent Swisher, brijeshb42, burnuser, Caleb Burks, Cameron Voell, Carike, carloscastilloadhoc, carlosgprim, Carolina Nymark, celendesign, Cenay Nailor, ceyhun0, chexwarrior, Chip Snyder, Chloé Bringmann, Chouby, Chris Van Patten, Christian Sabo, Christina Workman, Christopher Finke, clayray, Clayton Collie, Code Amp, Collins Agbonghama, Copons, Corey, cristinasoponar, Damian Nowak, Dan Farrow, Daniel Richards, Daniele Scasciafratte, Danny van Kooten, Daria, Darren Ethier (nerrad), Dave Whitley, David Anderson, David Baumwald, David Biňovec, David Calhoun, David Herrera, David Page, dbtedg, dd32, Debabrata Karfa, dekervit, Denis Yanchevskiy, denishua, Diane Co, Dilip Bheda, Dominik Schilling, donmhico, dratwas, Drew Jaynes, Dávid Szabó, e_baker, Ebonie Butler, Edi Amin, Ella van Durpe, Ella van Durpe, Elliott Richmond, Enej Bajgorić, Enrico Carraro, epicfaace, epiqueras, Eric Andrew Lewis, Eric Binnion, Eric Mann, Erik Betshammar, Erin ‘Folletto’ Casali, Estela Rueda, etoledom, eventualo, Fabian Kägy, Felipe Elia, Felix Arntz, Florian TIAR, Florian Ziegler, floriswt, Francesca Marano, Frank Klein, fullofcaffeine, Gan Eng Chin, Garrett Hyder, Gary Pendergast, GeekPress, geekzebre, Geoff Guillain, George Stephanis, geriux, gKibria, glendaviesnz, gmariani405, Gord, greatsaltlake, Greg Ziółkowski, grzim, gumacahin, gunnard, Gustavo Bordoni, Hans-Christiaan Braun, Hardeep Asrani, Hareesh, hauvong, Haz, Helen Hou-Sandi, helmutwalker, Hemant Tejwani, Herre Groen, hirasso, hmabpera, Howdy_McGee, hsingyuc7, Ian Dunn, ianmjones, ibiza69, Igor Radovanov, ingereck, iprg, Ipstenu (Mika Epstein), Isabel Brison, Ismail El Korchi, iviweb, J.D. Grimes, jadeddragoon, Jake Spurlock, jakeparis, jakub.tyrcha, James Golovich, James Huff, James Koster, James Nylen, James Rosado, Jan Thiel, Jason Adams, Jason LeMahieu (MadtownLems), Jason Ryan, Jayman Pandya, Jean-Baptiste Audras, Jeff Chandler, Jeff Farthing, Jeff Paul, Jennifer M. Dodd, Jenny Dupuy, Jeremy Felt, Jeremy Yip, Jeroen Rotty, Jessica Duarte, Jessica Lyschik, joanrho, Joe Dolson, Joe McGill, joelclimbsthings, Joen Asmussen, Johannes Kinast, John Blackbourn, John James Jacoby, John Watkins, Jon Surrell, Jonathan Champ, Jonathan Desrosiers, Jonathan Stegall, Jonny Harris, Jono Alderson, Joost de Valk, jordesign, Jorge Costa, José Miguel, Jose Luis, Joseph Karr O’Connor, Josepha Haden, joshuatf, JoshuaWold, JOTAKI, Taisuke, Joy, JS Morisset, jsnajdr, Juliette Reinders Folmer, Julio Potier, Justin Ahinon, Justin Sainton, Justin Sternberg, kafleg, Kai Hao, Kailey (trepmal), Kalpesh Akabari, kara.mcnair, Karolina Vyskocilova, Kelly Choyce-Dwan, Kerry Liu, kimdcottrell, Kiril Zhelyazkov, Kirsty Burgoine, Kite, Kjell Reigstad, Knut Sparhell, Konrad Chmielewski, Konstantin Obenland, Konstantinos Xenos, Kurt Payne, Kyle B. Johnson, Lara Schenck, laurelfulford, Laxman Prajapati, leogermani, Levdbas, Lihä, litemotiv, Lovro Hrust, lucasbustamante, Luigi Cavalieri, Lukas Pawlik, Luke Carbis, Luke Cavanagh, Luke Walczak, magnuswebdesign, Mahafuz, Mahdi Akrami, malinajirka, mallorydxw, mallorydxw-old, Manzoor Wani, Manzur Ahammed, marcelo2605, Marcio Zebedeu, Marcus, Marcus Kazmierczak, Marie Comet, Marijn Koopman, Marin Atanasov, Marius Jensen, Mark D Wolinski, Mark Howells-Mead, Mark Robson, Mark Uraine, Marko Andrijasevic, Markus, Mary Baum, Mathieu Berard Smartfire, Mathieu Viet, Matias Ventura, Matt Chowning, Matt Mullenweg, Matt Wiebe, Maxime Pertici, Mayank Majeji, mdrockwell, Meg Phillips, megabyterose, Meher Bala, Mehrshad Darzi, Mehul Kaklotar, Mel Choyce-Dwan, mendezcode, mgol, Michael Arestad, Michael Babker, Miguel Fonseca, Miina Sikk, Mike Schroder, Milan Dinić, Milana Cap, mirka, Mohamed El Amine DADDOU, Monika, Monika Rao, morenaf, mrjoeldean, Mukesh Panchal, munyagu, mzorz, Naveen, net, nicky, Nico, Nico Martin, Nicola Laserra, Nicolas Juen, NicolasKulka, Nik Tsekouras, Noah Allen, nwjames, oakesjosh, Olga Gleckler, ovidiul, oxyc, Paal Joachim Romdahl, Pascal Birchler, Paul Bearne, Paul Biron, Paul Bunkham, Paul Schreiber, Paul Von Schrottky, pawki07, pbking, Pedro Mendonça, Pete Nelson, Peter Smits, Peter Wilson, Pinkal Devani, Piotrek Boniu, Prem Tiwari, presstoke, prettyboymp, Prince, pypwalters, Q, r-a-y, Rafael Galani, rafhun, Rami Yushuvaev, Ramon Ahnert, ratneshk, Ravi Vaghela, ravipatel, retrofox, Reza Ardestani, Riad Benguella, Rian Rietveld, Richard Tape, Robert Anderson, Rodrigo Primo, roger995, Rolf Siebers, Romain, Ronnie Burt, Ross Wintle, Ryan Boren, Sébastien SERRE, Sören Wrede, Saša, Sanket Chodavadiya, Sarah Ricker, sarayourfriend, Scott Taylor, Sebastian Pisula, SeBsZ, Sergey Biryukov, Sergey Yakimov, sergiomdgomes, Shahin Sid, shaunandrews, Shital Marakana, Slava Abakumov, snapfractalpop, souri_wpaustria, Stefano Minoia, Stefanos Togoulidis, Stephen Bernhardt, Stephen Edgar, Steven Word, Subrata Sarkar, Sunny, t-p, Takashi Kitajima, Tami, Tammie Lister, Tanvirul Haque, Tapan, TeamDNK, TeBenachi, Thierry Muller, thorlentz, Tim Hengeveld, Tim Nolte, Timi Wahalahti, Timothy Jacobs, tinodidriksen, Tkama, tmatsuur, Tobias Zimpel, tobifjellner (Tor-Bjorn Fjellner), Toni Viemerö, Tony A, Tonya Mork, tonysandwich, Torsten Landsiedel, Toru Miki, transl8or, Tyler Tork, Ulrich, Umang Vaghela, vandestouwe, vcanales, Vipul Chandel, Vlad T., webcommsat AbhaNonStopNewsUK, WebMan Design | Oliver Juhas, Wendy Chen, wesselvandenberg, Weston Ruter, Willis Allstead, worldedu, WP OnlineSupport, Xristopher Anderton, Yann Kozon, Yoav Farhi, yscik, Yui, yuliyan, Zebulan Stanphill, and zieladam.
\n\n\n\nCode is poetry.
\nWhy not take a look at this post regarding the second call for testing as part of the Full Site Editing Outreach Programme.
\n\n\n\nHere you will find everything you need to know about this exciting new programme and how you can get involved.
\n\n\n\nPlease leave any feedback in the comments of the post by Friday 5 March 2021.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:115:\"https://en-gb.wordpress.org/2021/02/24/fse-programme-testing-call-2-build-a-homepage-with-site-editing-blocks/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:73:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.6.2 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://en-gb.wordpress.org/2021/02/22/wordpress-5-6-2-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://en-gb.wordpress.org/2021/02/22/wordpress-5-6-2-maintenance-release/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 22 Feb 2021 17:23:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://en-gb.wordpress.org/?p=1336\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:452:\"WordPress 5.6.2 is now available! This maintenance release includes 5 bug fixes. These bugs affect WordPress version 5.6.1, so you’ll want to upgrade. You can download WordPress 5.6.2 directly, or visit the Dashboard → Updates screen and click Update Now. If your sites support automatic background updates, they’ve already started the update process. WordPress 5.6.2 is a small maintenance release focused […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Mark Robson\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5084:\"\nWordPress 5.6.2 is now available!
\n\n\n\nThis maintenance release includes 5 bug fixes. These bugs affect WordPress version 5.6.1, so you’ll want to upgrade.
\n\n\n\nYou can download WordPress 5.6.2 directly, or visit the Dashboard → Updates screen and click Update Now. If your sites support automatic background updates, they’ve already started the update process.
\n\n\n\nWordPress 5.6.2 is a small maintenance release focused on fixing user-facing issues discovered in 5.6.1. The next major release will be version 5.7, currently scheduled for release on 9 March 2021.
\n\n\n\nTo see a full list of changes, you can browse the list on Trac, read the 5.6.2 RC1 post, or visit the 5.6.2 documentation page.
\n\n\n\nThe 5.6.2 release was led by @desrosj. Special props to @isabel_brison and @talldanwp for helping to prepare the block editor related fixes, and @audrasjb and @sergeybiryukov for helping with other release related tasks.
\n\n\n\nProps to everyone who helped make WordPress 5.6.2 happen:
\n\n\n\naaronrobertshaw, Addie, André Maneiro, archon810, Ari Stathopoulos, bartosz777, Bernhard Reiter, Daniel Richards, David Anderson, dbtedg, glendaviesnz, hmabpera, ibiza69, Isabel Brison, Jason Ryan, Jb Audras, Juliette Reinders Folmer, Kai Hao, Kerry Liu, Konrad Chmielewski, Jorge Costa, magnuswebdesign, Marius L. J., Matt Wiebe, Mukesh Panchal, Paal Joachim Romdahl, Prem Tiwari, Q, Riad Benguella, Robert Anderson, roger995, Sergey Biryukov, Sergey Yakimov, Steven Stern (sterndata), Takashi Kitajima, tonysandwich, worldedu, Yui.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://en-gb.wordpress.org/2021/02/22/wordpress-5-6-2-maintenance-release/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:73:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.6.1 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://en-gb.wordpress.org/2021/02/04/wordpress-5-6-1-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://en-gb.wordpress.org/2021/02/04/wordpress-5-6-1-maintenance-release/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 04 Feb 2021 16:48:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://en-gb.wordpress.org/?p=1332\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:479:\"WordPress 5.6.1 is now available! This maintenance release features 20 bug fixes as well as 7 issues fixed for the block editor. These bugs affect WordPress version 5.6, so you’ll want to upgrade. You can download WordPress 5.6.1 directly, or visit the Dashboard → Updates screen and click Update Now. If your sites support automatic background updates, they’ve already started the update process. WordPress 5.6.1 […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Mark Robson\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:8383:\"\nWordPress 5.6.1 is now available!
\n\n\n\nThis maintenance release features 20 bug fixes as well as 7 issues fixed for the block editor. These bugs affect WordPress version 5.6, so you’ll want to upgrade.
\n\n\n\nYou can download WordPress 5.6.1 directly, or visit the Dashboard → Updates screen and click Update Now. If your sites support automatic background updates, they’ve already started the update process.
\n\n\n\nWordPress 5.6.1 is a short-cycle maintenance release. The next major release will be version 5.7.
\n\n\n\nTo see a full list of changes, you can browse the list on Trac, read the 5.6.1 RC1 post, or visit the 5.6.1 documentation page.
\n\n\n\nThe 5.6.1 release was led by @audrasjb, @desrosj, @sergeybiryukov and @whyisjake. Thanks to @metalandcoffee and @hellofromtonya for running bug scrubs, @planningwrite and @davidbaumwald for their help on the release post.
\n\n\n\nProps to everyone who helped make WordPress 5.6.1 happen:
\n\n\n\naaribaud, Aaron D. Campbell, Ahmed Saeed, Andrew Ozz, Anthony Burchell, archon810, Ari Stathopoulos, Ayesh Karunaratne, basscan, carloscastilloadhoc, Carolina Nymark, celendesign, Christopher Finke, Copons, Dan Farrow, Daniel Richards, david.binda, Denis Yanchevskiy, Dilip Bheda, Dominik Schilling, Ebonie Butler, Felix Arntz, Florian TIAR, Garrett Hyder, gKibria, Greg Ziółkowski, Helen Hou-Sandi, Ian Dunn, ifnoob, Isabel Brison, Ismail El Korchi, Jake Spurlock, James Huff, Jason LeMahieu (MadtownLems), Jb Audras, John Blackbourn, Jonathan Desrosiers, Jonathan Stegall, Jorge Costa, Josepha, Justin Ahinon, Kai Hao, Kelly Choyce-Dwan, Kjell Reigstad, Konstantinos Xenos, litemotiv, lucasbustamante, Mahdi Akrami, majhajob, Manzur Ahammed, Marius L. J., Matt Wiebe, Maxime Pertici, Mel Choyce-Dwan, Michael Babker, Mukesh Panchal, NicolasKulka, Nik Tsekouras, oakesjosh, Peter Wilson, Prem Tiwari, Riad Benguella, Richard Tape, Robert Anderson, Rodrigo Primo, SeBsZ, Sergey Biryukov, Slava Abakumov, Stephen Bernhardt, t-p, Takashi Kitajima, Tanvirul Haque, thorlentz, Timothy Jacobs, Toni Viemerö, Tony A, Tonya Mork, transl8or, and Vlad T.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://en-gb.wordpress.org/2021/02/04/wordpress-5-6-1-maintenance-release/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:73:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"WordPress 5.6 “Simone”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"https://en-gb.wordpress.org/2020/12/09/wordpress-5-6-simone/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://en-gb.wordpress.org/2020/12/09/wordpress-5-6-simone/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 09 Dec 2020 00:01:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://en-gb.wordpress.org/?p=1309\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:338:\"Meet Simone, our latest and greatest WordPress release. Named in honour of the legendary performer Nina Simone, who is known for tunes like “Feeling Good”, “Young, Gifted and Black”, and “Four Women”. Fire up a playlist with her best work and read on to discover what we have in store for you. Welcome to WordPress […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Mark Robson\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:61064:\"\nMeet Simone, our latest and greatest WordPress release. Named in honour of the legendary performer Nina Simone, who is known for tunes like “Feeling Good”, “Young, Gifted and Black”, and “Four Women”. Fire up a playlist with her best work and read on to discover what we have in store for you.
\n\n\n\n\n\n\n\nWelcome to WordPress 5.6
\n\n\n\nWordPress 5.6 brings you countless ways to set your ideas free and bring them to life. With a brand-new default theme as your canvas, it supports an ever-growing collection of blocks as your brushes. Paint with words. Pictures. Sound. Or rich embedded media.
\n\n\n\n\n\n\n\nBring your stories to life with more tools that let you edit your layout with or without code. Single column blocks, designs using mixed widths and columns, full-width headers, and gradients in your cover block – make small changes or big statements with equal ease!
\n\n\n\nIn some themes, preconfigured block patterns make setting up standard pages on your site a breeze. Let the power of patterns streamline your workflow and save you clicks. Plus, share these features with clients, editors, and more.
\n\n\n\nTo help you add subtitles or captions to your videos, you can now upload them within your post or page. This makes it easier than ever to make your videos accessible for anyone who needs or prefers to use subtitles.
\n\n\n\n\n\n\n\nTwenty Twenty-One is a blank canvas for your ideas, and the block editor is the best brush. It is built for the block editor and packed with brand-new block patterns you can only get in the default themes. Try different layouts in a matter of seconds, and let the theme’s eye-catching, yet timeless design make your work shine.
\n\n\n\nWhat’s more, this default theme puts accessibility at the heart of your website. It conforms to the WordPress accessibility-ready guidelines and addresses several more specialised standards from the Web Content Accessibility Guidelines (WCAG) 2.1 at level AAA. It will help you meet the highest level of international accessibility standards when you create accessible content and choose plugins which are accessible too!
\n\n\n\nPerfect for a new year, Twenty Twenty-One gives you a range of pre-selected colour palettes in pastel, all of which conform to AAA standards for contrast. You can also choose your own background colour for the theme, and the theme chooses accessibility-conscious text colours for you – automatically!
\n\n\n\nNeed more flexibility than that? You can also choose your own colour palette from the colour picker.
\n\n\n\n\n\n\n\nFor years, only developers have been able to update WordPress automatically. But now you have that option, right in your dashboard. If this is your first site, you have auto-updates ready to go, right now! Upgrading an existing site? No problem! Everything is the same as it was before.
\n\n\n\nEven if you’re not an expert, you can start letting others know about your site’s commitment to accessibility! The new feature plugin includes template copy for you to edit and publish, and it’s written to support different contexts and jurisdictions.
\n\n\n\nIf you’ve not had the chance to play with block patterns yet, all default themes now feature a range of block patterns that let you master complex layouts with minimal effort. Customise the patterns to your liking with the copy, images, and colours that fit your story or brand.
\n\n\n\n\n\n\n\nThanks to the API’s new Application Passwords authorisation feature, third-party apps can connect to your site seamlessly and securely. This new REST API feature lets you see what apps are connecting to your site and control what they do.
\n\n\n\n5.6 marks the first steps toward WordPress Core support for PHP 8. Now is a great time to start planning how your WordPress products, services, and sites can support the latest PHP version. For more information about what to expect next, read the PHP 8 developer note.
\n\n\n\nUpdates to jQuery in WordPress take place across three releases 5.5, 5.6, and 5.7. As we reach the mid-point of this process, run the update test plugin to check your sites for errors ahead of time.
\n\n\n\nIf you find issues with the way your site looks (eg a slider doesn’t work, a button is stuck – that sort of thing), install the jQuery Migrate plugin.
\n\n\n\nRead about the latest version of WordPress in this guide. It highlights developer notes for each change in the release.
\n\n\n\n“It’s a new day, it’s a new life for me….and I’m feeling good”.
\n\n\n\nThe WordPress 5.6 release comes to you from an all-women release squad:
\n\n\n\nAs always, this release reflects the hard work of 605 generous volunteer contributors. They collaborated on nearly 350 tickets on Trac and over 1,000 pull requests on GitHub. Özgür KARALAR, 1naveengiri, A5hleyRich, Aaron D. Campbell, Aaron Jorbin, aaronrobertshaw, abderrahman, Abha Thakor, Abhijit Rakas, Abhishek Pokhriyal, acosmin, Adam Silverstein, Adam Zielinski, Addie, Adrián de Grafreak, Adrianti Rusli, Afshana Diya, Ahmed Chaion, Ahmed Elgameel, ajensen, Ajit Bohra, Akira Tachibana, aktasfatih, Albert Juhé Lluveras, albertomake, Alex Concha, Alex Kirk, Alex Kozack, Alex Lende, Alex Mills, Alex Standiford, Alex Stine, allancole, Allie Nimmons, ambienthack, Amit Dudhat, Amol Vhankalas, Amy Kamala, Anand, Anders Norén, Andrea Fercia, Andrea Middleton, Andrei Baicus, Andrei Draganescu, Andrew Duthie, Andrew Nacin, Andrew Ozz, Andrey “Rarst” Savchenko, Andy Fragen, Andy Peatling, Andy Skelton, Andy Stitt, Angel Hess, Angela Jin, Ankit Gade, Ankit Panchal, Anne McCarthy, Anthony Burchell, Anthony Hortin, Anton Lukin, Antonis Lilis, anuj2, apedog, Apermo, archduck, archon810, Ari Stathopoulos, arippberger, arjendejong, ArnaudBan, Arpit G Shah, Arslan Ahmed, Arslan Ahmed Kalwar, Asvin Balloo, Atharva Dhekne, Austin Passy, austin880625, avixansa, ayesh, Ayesh Karunaratne, BackuPs, Barry, Bart Czyz, bduclos, Beatriz Fialho, Ben Meredith, Bernhard Kau, Bernhard Reiter, Beth Soderberg, bgermann, Bhagvan Mangukiya, bhautikvirani, Billy, Birgir Erlendsson (birgire), Birgit Pauli-Haack, bmcdede, bobbingwide, BoldGrid, Boone Gorges, Boy Witthaya, Brady Vercher, Brandon Kraft, Brandon Payton, Brent Miller, Brent Swisher, Brian Henry, Brian Hogg, bridgetwillard, brijeshb42, Burhan Nasir, Caleb Burks, Calin Don, Cameron Voell, campusboy, Carike, Carolina Nymark, Caroline, ceyhun0, Chad Reitsma, Chandrika Guntur, Chetan Prajapati, chexwarrior, Chintan hingrajiya, Chip Snyder, Chloé Bringmann, Chouby, Chris Alexander, Chris Van Patten, chriscct7, Christian Martin, Christoph Herr, Christopher Churchill, chunkysteveo, Claudiu Lodromanean, Clayton Collie, Collins Agbonghama, Commeuneimage, Copons, Corey Salzano, cpapazoglou, cranewest, Csaba (LittleBigThings), ctmartin, Dávid Szabó, Daisy Olsen, Dan Farrow, Daniel Bachhuber, Daniel Richards, Daniele Scasciafratte, danieltj, dantahoua, Darin Kotter, Dave McHale, David Aguilera, David Anderson, David Baumwald, David Gwyer, David Herrera, David Shanske, David Smith, David Wolfpaw, david.binda, Davis Shaver, dd32, Dean, Debabrata Karfa, Dee Teal, Deepak Lalwani, dekervit, demetris (Demetris Kikizas), Denis de Bernardy, Derek Herman, Designer023, dfenton, Dharmesh Patel, Dharmin Shah, Dhruvin, Dhul Wells, dietpawel, Dilip Bheda, dingo-d, DjZoNe, dogwithblog, Dominik Schilling, donmhico, donsony, Dossy Shiobara, dpacks, Dr. Ronny Harbich, dratwas, Drew Jaynes, dsifford, dushakov, dushanthi, dyrer, Earle Davies, Ebonie Butler, Edi Amin, Ella van Durpe, Ellen Bauer, Enej Bajgoric, Enrique Sánchez, epiqueras, Erik Betshammar, erikjandelange, Erin ‘Folletto’ Casali, eroraghav, Estela Rueda, etoledom, EugeneBos, Evan Mullins, Fabian, Fabian Kägy, Fabian Todt, Felipe Elia, Felix Arntz, Ferenc Forgacs, Florian TIAR, flymike, Francesca Marano, Frank Klein, Frankie Jarrett, fullofcaffeine, Gan Eng Chin, Garrett Hyder, Gary Cao, Gary Jones, Gary Pendergast, gchtr, Gennady Kovshenin, George, George Stephanis, geriux, Glauber Mota, glendaviesnz, goldenapples, Greg Ziółkowski, guidooffermans, gumacahin, H-var, hakre, happiryu, Hareesh, Haris Zulfiqar, harrym, harshbarach, Hauwa Abashiya, Haz, Helen Hou-Sandí, Henry Wright, Herre Groen, HoaSi, Howdy_McGee, Hugh Lashbrooke, Ian Dunn, Igor Radovanov, Imran Sayed, ingereck, Ipstenu (Mika Epstein), iqbalbary, Irene Strikkers, Isabel Brison, jagirbaheshwp, Jake Spurlock, Jake Whiteley, James Collins, James Koster, James Nylen, James Rosado, jameslnewell, Jan Thiel, Janvo Aldred, Jared Cobb, Jason Caldwell, Jason LeMahieu (MadtownLems), javorszky, Jaydip Rami, Jean-Baptiste Audras, Jeff Matson, Jeff Ong, Jeff Paul, jeffikus, jellypixel, Jeremy Felt, Jeremy Scott, Jeremy Yip, Jeroen Rotty, jeryj, Jeslen Bucci, Jessica Lyschik, jfoulquier, jimyaghi, Jip Moors, Joe Dolson, Joe McGill, joelclimbsthings, joelyoder, Joen Asmussen, Johanna de Vos, John Blackbourn, John Godley, John James Jacoby, Jon Brown, Jonathan Bossenger, Jonathan Desrosiers, Jonathan Stegall, Jonny Harris, Jono Alderson, Joost de Valk, jordesign, Jorge Bernal, Jorge Costa, joseaneto, Josepha Haden, Josh Levinson, Josh Pollock, joshuatf, JOTAKI, Taisuke, Joy, jsnajdr, Juliette Reinders Folmer, Junaid Bhura, Justin Ahinon, justlevine, K. Adam White, Kai Hao, Kailey (trepmal), Kalpesh Akabari, karthikbhatb, Kaspars, Kelly Dwan, Kelly Hoffman, Kelly R, kellybleck, kellylawrence, Kevin Hagerty, Kharis Sulistiyono, Kipperlenny, Kiril Zhelyazkov, Kirsty Burgoine, Kishan Jasani, Kite, KittMedia, kjbenk, Kjell Reigstad, Knut Sparhell, komagain, Konstantin Obenland, Krupa, Kyle B. Johnson, landau, Larissa Murillo, latifi, Laura Nelson, Laxman Prajapati, lcyh78, leogermani, Lester Chan, Leutrim Husaj, lim3ra, Lionel Pointet, llizard, Louis, Luca Grandicelli, Luigi Cavalieri, Luke Cavanagh, Lumne, mager19, Maggie Cabrera, Mahesh Waghmare, mailnew2ster, Mainul Hassan Main, malinajirka, manzwebdesigns, Marcus Kazmierczak, Marek Hrabe, Marie Comet, Marijn, Marius Jensen, Mark Jaquith, Mark Parnell, Mark Robson, Mark Smallman, Mark Uraine, Marko Heijnen, markshep, Marty Helmick, Mary Baum, Mateus Machado Luna, Mathieu Viet, Matias Ventura, Matt Cromwell, Matt Gibson, Matt Keys, Matt Mullenweg, Matt Wiebe, mattchowning, Matthias Pfefferle, mattoperry, Mayank Majeji, Meagan Hanes, Meg Phillips, Meher Bala, Mel Choyce-Dwan, mgol, mgrenierfarmmedia, Michael Arestad, Michael Beckwith, Michele Butcher-Jones, Michelle Frechette, Miguel Fonseca, mihdan, Mike Schroder, mikelopez, Mikey Arce, Milan Dinić, Milana Cap, Mitchell Bennis, mmarco9, Mohammad Jangda, Monika Rao, mopsyd, Morgan Estes, Morgan Kay, Morteza Geransayeh, mqudsi, mreishus, mrgrt, mrjoeldean, Mukesh Panchal, munyagu, musicaljoeker, mweichert, n5hzr, Nabil Moqbel, Nalini Thakor, Naoki Ohashi, Naoko Takano, Nate Gay, Nathan Johnson, Navanath Bhosale, Naveen Kharwar, nendeb, net, Netravnen, nicomollet, Niels Lange, Nik Tsekouras, Nikola, Nikolay Bachiyski, njbrown, nlpro, Noah Allen, noahshrader, nourma, O André, oakesjosh, oguzkocer, Olga Gleckler, Omar Alshaker, Omar Reiss, oolleegg55, Optimizing Matters, Ov3rfly, ovann86, ovenall, oxyc, Paal Joachim Romdahl, pabloselin, Paddy, Pankaj Mohale, Pascal Birchler, Pascal Casier, Paul Bearne, Paul Biron, Paul Bunkham, Paul Schreiber, Paul Stonier, Paul Von Schrottky, Pedro Mendonça, pentatonicfunk, pepe, Peter Elmered, Peter Smits, Peter Wilson, Phil Johnston, Pierre Gordon, Pilar Mera, Pinar, Piotrek Boniu, pishmishy, pkvillanueva, prashanttholia, Pratik K. Yadav, Presskopp, presstoke, prionkor, psealock, Puneet Sahalot, Q, Rachel Baker, Rajan Vijayan, rajeshsingh520, Rami Yushuvaev, Ravi Vaghela, ravipatel, rebasaurus, redstar504, Regan Khadgi, Rene Hermenau, retlehs, retrofox, riaanlom, Riad Benguella, ribaricplusplus, Rich Tabor, Rnaby, Robert Anderson, Robert Chapin, Rodrigo Arias, rogerlos, roikles, Rolf Siebers, Ronak Ganatra, roo2, rtagliento, Ryan Fredlund, Ryan Kienstra, Ryan McCue, Ryan Welcher, Sören Wrede, Sabrina Zeidan, Saeed Fard, salvoaranzulla, Sam Fullalove, Sam Webster, Samuel Wood (Otto), Sanjeev Aryal, Saqib Ameen, Sarah Ricker, sarayourfriend, sawanoboly, scarolan, Scott Cariss, Scott Reilly, scribu, scruffian, seanpaulrasmussen, Sebastian Pisula, SeBsZ, Senning, Sergey Biryukov, Sergey Yakimov, SergioEstevao, shaunandrews, Shawntelle Coker, Shital Marakana, shramee, Simon Resok, sirreal, smerriman, snapfractalpop, sproutchris, Stéphane Treilhou, Stanko Metodiev, Stefano Garuti, Stephen Bernhardt, Steve Dufresne, Steven Stern (sterndata), stevenlinx, Stoyan Georgiev, sudoshreyansh, Syed Balkhi, szaqal21, Tammie Lister, TeBenachi, techboyg5, Tellyworth, thefarlilacfield, Thelma Mutete, thib3113, thijsvanloef, Thomas M, Thomas Patrick Levy, thomaslhotta, Tim Havinga, Tim Hengeveld, Timi Wahalahti, Timothy Jacobs, TimoTijhof, Tkama, tmdesigned, TobiasBg, tobifjellner (Tor-Bjorn Fjellner), Tonya Mork, Toro_Unit (Hiroshi Urabe), torres126, Torsten Landsiedel, Towhidul I Chowdhury, treibstoff, Trisha Cornelius, Tung Du, tzafrir, Udit Desai, Ulrich, uxkai, Valentin Bora, Varun Sharma, vcanales, vidhiaddweb, Vinayak Anivase, Vinita Tandulkar, Vinny, virgodesign, WebMan Design | Oliver Juhas, Webmigrates Technologies, Weston Ruter, William Earnhardt, williampatton, Winstina Hughes, wittich, worldweb, Y_Kolev, Yan Sern, Yoav Farhi, yscik, Yui, Yvette Sonneveld, and Zebulan Stanphill.
\n\n\n\nIn addition, many thanks to all of the community volunteers who contribute in the support forums. They answer questions from people across the world, whether they are using WordPress for the first time, or they’ve been around since the first release all the way back in 2003. These releases are as successful as they are because of their efforts!
\n\n\n\nFinally, thanks to all the community translators who helped make WordPress 5.6. available in 38 languages at the time of release. Our community translators are hard at work ensuring more languages are on their way (70 are already at 90%). If contributing to WordPress appeals to you, it’s easy to learn more. Check out Make WordPress or the core development blog.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://en-gb.wordpress.org/2020/12/09/wordpress-5-6-simone/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:88:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"Manchester WordPress User Group November 2020 – Online\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"https://en-gb.wordpress.org/2020/11/18/manchester-wordpress-user-group-november-2020-online/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"https://en-gb.wordpress.org/2020/11/18/manchester-wordpress-user-group-november-2020-online/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 18 Nov 2020 14:26:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:6:{i:0;a:5:{s:4:\"data\";s:7:\"England\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:6:\"Meetup\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"North West\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:10:\"Manchester\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:31:\"Manchester WordPress User Group\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:6:\"Online\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://en-gb.wordpress.org/?p=1300\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:147:\"November’s Manchester WordPress User Group, run by WordPress co-founder Mike Little, takes place online on Wednesday, the 18th from 6pm to 8pm.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Mike Little\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:943:\"\nNovember’s Manchester WordPress User Group, run by WordPress co-founder Mike Little, takes place online on Wednesday, the 18th from 6pm to 8pm.
\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:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"https://en-gb.wordpress.org/2020/11/18/manchester-wordpress-user-group-november-2020-online/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:73:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"Help Improve WordPress Translation\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://en-gb.wordpress.org/2020/11/09/help-improve-wordpress-translation/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://en-gb.wordpress.org/2020/11/09/help-improve-wordpress-translation/#respond\";s: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, 09 Nov 2020 10:52:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"News\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://en-gb.wordpress.org/?p=1290\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:386:\"The global Polyglots team is conducting research among translation contributors to learn more about their experience. The questionnaire includes about 15 questions for individual translators or locale managers and editors. Our goal is to learn more about how contributors join Polyglots, why they contribute, and how to make their contributor experience better. The results of […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Mark Robson\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:1215:\"\n\n\n\n\nThe global Polyglots team is conducting research among translation contributors to learn more about their experience.
\n\n\n\nThe questionnaire includes about 15 questions for individual translators or locale managers and editors. Our goal is to learn more about how contributors join Polyglots, why they contribute, and how to make their contributor experience better.
\n\n\n\nThe results of this research will be used to inform future discussions about team priorities, including documentation, tools, and other ideas, especially as we plan for 2021. Hearing from both experienced contributors, and newcomers, will be extremely helpful – the more voices, the better!
\n\n\n\nThe form is open from 9 November 2020 to 8 December 2020.
\n\n\n\nClick here to share your translation experience.
\n\n\n\nThank you so much for your contribution, and for being part of the Polyglots community.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://en-gb.wordpress.org/2020/11/09/help-improve-wordpress-translation/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:38:\"https://en-gb.wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Tue, 08 Jun 2021 02:35:42 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Wed, 02 Sep 2020 10:33:19 GMT\";s:4:\"link\";s:64:\"Last week, Dumitru Brînzan announced Nutmeg Plus. It is the latest commercial theme offering through his ILOVEWP brand. Earlier today, the free version of Nutmeg landed in the WordPress theme directory. The theme is built for food and recipe bloggers and is another solid example of building on the block system.
\n\n\n\nAs is typical of his style, Nutmeg rests on a foundation of clean lines and readable typography. It pulls elements from some of Brînzan’s previous work, such as the featured pages section of Photozoom and the two-column intro from Endurance. Reusing code is one of the cornerstones of smart development.
\n\n\n\nThe theme never gets too flashy, nor is it a bold step forward in design. However, it has a timeless layout that is hard to go wrong with.
\n\n\n\nWhere it shines is in its use of block patterns and styles.
\n\n\n\nRecipe post built with Nutmeg.\n\n\n\nSometimes, theme authors surprise me with, in hindsight, simple solutions. Nutmeg’s List block styles had me asking, “Why didn’t I think of that?”
\n\n\n\nLast month, I challenged theme authors to build out patterns that are often created as custom blocks. In the post, I showcased an example of how themers could provide pricing columns for their users. The Nutmeg theme is a perfect example of that same concept, only applied to recipes.
\n\n\n\nThe unique aspect is that Brînzan did not make it complex. With a few simple styles for the List block, he had all the makings of the typical “recipe card” seen on many food blogs. Is it as advanced as a fully-featured recipe card plugin? No. But, that should not be the goal. If users need more advanced recipe-related features and functionality, that is where plugins make sense. The theme even recommends a few like WP Recipe Maker, Recipe Card Blocks, and Delicious Recipes for those who need more.
\n\n\n\nHowever, for bloggers who are just starting, undecided on recipe plugins, or simply do not want another dependency, the theme has built-in solutions for them. It is tough to discount the value in that.
\n\n\n\nAdding instructions and ingredients.\n\n\n\nWith a starting point of the Recipe Info, Ingredients List, or Ingredients + Instructions patterns, users can quickly pop these sections into their content. Or, they can go the alternate route of starting with the List block and selecting one of four custom styles.
\n\n\n\n\n\n\n\nTheme authors should be able to build unique and complex combinations of blocks with custom styles. Users should be able to just make it look like the demo.
Block Patterns Will Change Everything
It was March 2020. The Gutenberg development team had just pushed block patterns into the plugin, but the feature would not land in core WordPress for months. I do not want to call myself a prophet. It was plain enough for anyone to see: block patterns would eventually change how end-users interact with the editor and build their sites.
\n\n\n\nPatterns were the answer to elaborate homepage setups. Instead of jumping back and forth between non-standard theme options, hoping for the best from a theming community that never learned to entirely leverage the customizer, users could simply click buttons and insert layout sections where they wanted.
\n\n\n\nRecreating Nutmeg’s homepage demo was easy. By just picking a few patterns and adding some custom images, I was up and running in minutes. No tutorial necessary. No half-hour session of figuring out a theme’s custom options setup.
\n\n\n\nSimple setup processes like this are the exact thing that theme authors have been repeatedly asking about for the better part of a decade. Except for a powerful Query solution, which is arriving in a limited form in WordPress 5.8 (the Post Featured Image block is the weak point), the tools are mostly in place. The feature set is only growing with each release.
\n\n\n\nOne of my favorite solutions in the theme is the use of the Cover block’s inner container. The plugin has several styles for moving this inside box around and creating a featured section.
\n\n\n\nCustomizing the Cover block with styles.\n\n\n\nOne improvement I might suggest is to provide “width” styles for the inner container here. Core already provides an alignment matrix option. Styles for 25%, 50%, and 75% width (100% being the default) would offer more variety when coupled with the existing alignments.
\n\n\n\nThe only things that felt out of place with the theme were its alignment block styles for Heading and Paragraph blocks. WordPress already provides alignment options for these blocks. I am not sure if there is a use case that I am unaware of for the styles, but they were definitely confusing.
\n\n\n\nThe theme is worth a test run for any food or recipe bloggers who need a dash of Nutmeg to spice up their site.
\";s: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 Jun 2021 22:54:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"WordPress.org blog: People of WordPress: Tijana Andrejic\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10427\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2021/06/people-of-wordpress-tijana-andrejic/\";s: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:13617:\"WordPress is open source software, maintained by a global network of contributors. There are many examples of how WordPress has changed people’s lives for the better. In this monthly series, we share some of the amazing stories.
\n\n\n\nThis month to coincide with WordCamp Europe, we feature Tijana Andrejic from Belgrade, Serbia, about her journey from fitness trainer to the WordPress world, with the freelance and corporate opportunities it introduced.
\n\n\n\n\n\n\n\nAs a professional manager with a college degree in Organizational Science and a certified fitness instructor, Tijana is nothing if not driven and goal-oriented.
\n\n\n\nFollowing her time as a fitness trainer, Tijana moved to work in IT around 2016. She first explored content creation and design before focusing on SEO and becoming an independent specialist.
\n\n\n\nTijana was hired as a Customer Happiness Engineer for a hosting company, where she discovered the benefits of having a team. She realized that having close working relationships with colleagues is helpful for business success and accelerates personal growth.
\n\n\n\nTijana hopes that by sharing her story, she can help others who are either starting their career or are moving roles. She describes the opportunities she discovered in the WordPress community as ‘a huge epiphany’, especially in the world of freelancing.
\n\n\n\nShe highlights 5 things that helped her to start a new freelancing career. Let’s dive into them.
\n\n\n\n“Why am I doing this?” is the first question that Tijana asks herself before starting anything new. This self-review and honesty, she feels, allows her to determine her priorities. She also benchmarks options around her motivations of wanting a flexible schedule and to grow professionally.
\n\n\n\nShe lists the reasons to make a particular choice, like being a freelancer, to help her choose the right job, pathway, or identify alternatives.
\n\n\n\nShe recommends that others can take a similar approach. If freelancing is still the best solution after examining all their goals and motivations, Tijana believes a good next step would be to learn WordPress-related skills.
\n\n\n\n\n\n\n\nThe next question you may ask: “Why WordPress?”
\n\n\n\nWordPress is used by more than 40% of websites in some form and offers various roles, many of which are not developer-specific. Tijana highlights a few:
\n\n\n\nTijana emphasized: “Another reason why WordPress is great for freelancers is the strong community that exists around this content management system (CMS).” WordCamps and Meetups are a way to get useful information and meet people from a large and very diverse community and get answers to many questions straight away.
\n\n\n\nIn the past year, these events have been primarily online. However, the contributors who run them continue to make an effort to provide an experience as close to in-person events as possible. The biggest advantage to online events is that we can attend events from across the world, even if sometimes during these difficult times, it is difficult to get enough time to deeply into this new experience. Since Tijana’s first Meetup, she has attended many WordPress community events and volunteered as a speaker.
\n\n\n\nBecoming a freelancer takes time. For Tijana, success came with proper planning and following her plan to ‘acquire or improve relevant skills that will make you stand out in the freelance market.’ She strongly believes that learning and growing as a professional opens more business opportunities.
\n\n\n\nIf you are considering a freelance career, she advises improving relevant skills or developing new skills related to your hobbies as ‘there is nothing better than doing what you love.’ In cases where no previous experience and knowledge can be used, she suggests choosing ‘a job that has a shorter learning curve and builds your knowledge around that.’
\n\n\n\nTijana started as a content creator and learned to become an SEO expert. However, she highlights many alternative paths, including starting as a web implementer and moving to train as a developer.
\n\n\n\nShe suggests to others: “It would be a good idea to analyze the market before you jump into the learning process.” She also recommends people check the latest trends and consider the future of the skills they are developing.
\n\n\n\nVisit the new Learn WordPress.org to see what topics are of interest to you. In this newly established resource, the WordPress community aggregates workshops to support those who want to start and improve their skills, provides lesson plans for professional WordPress trainers and helps you create personal learning to develop key skills. There is also material on helping you be part of and organize events for your local community.
\n\n\n\nTijana highlights that there are many places for freelancers to find clients. For example, the WordPress Community has a place where companies and individual site owners publish their job advertisements – Jobs.WordPress.net.
\n\n\n\nAs a pragmatic person, Tijana recommends: “Save money before quitting your job to become a full-time freelancer. Alternatively, try freelancing for a few hours per week to see if you like it. Although some people do benefit when taking a risk, think twice before you take any irreversible actions.”
\n\n\n\nShe shared some possible next steps:
\n\n\n\n“By using video material, your clients will not see you like a list of skills and previous experiences, but as a real person that has these skills and experiences and that provides a certain service for them.”
\n\n\n\nShe adds: “Have a detailed strategy when choosing your first employer. Choose your first employer wisely, very wisely. I can’t emphasize enough how important this is”.
\n\n\n\nWhen Tijana took her first freelancing job, she considered the following:
\n\n\n\n“The first job is not all about the money. Don’t get greedy on your first job. If you get good recommendations, your second job can pay two to three times more. And your third job can go up to five times more. That was my experience.”
\n\n\n\nTijana reminds us: “Freedom often comes with responsibility; individual responsibility is key when it comes to freelancing.”
\n\n\n\nShe advises others not to take a job if you can not make a deadline and have someone reliable who can help you.
\n\n\n\nMissing deadlines will cost your client money and affect the review the client will be willing to leave about your job, and this can have a big impact on your future opportunities or freelance jobs.
\n\n\n\nShe adds: “This can start a downward spiral for your career. However, we are all humans, and unpredictable things can happen. If for some reason you are not able to complete your work in a timely manner, let your client know immediately so they can have enough time to hire someone else”.
\n\n\n\nTijana emphasizes the importance of making expectations clear before accepting a job, both what the client is expecting and what you can expect from the client.
\n\n\n\nLastly, she points out that if you are working from home, your friends and family should treat you the way they would if you were in an office. She advises: “Let them know about your working schedule.”
\n\n\n\nShe hopes that these basic guidelines will be useful in launching freelance careers, as they did her, even though there is no universal recipe for all.
\n\n\n\nTijana highlights: “It’s just important to stay focused on your goals and to be open to new opportunities.” Freelancing wasn’t the only way she could have fulfilled her goals, but it was an important part of her path, and it helped her be confident in her abilities to make the next big step in her life.
\n\n\n\nAs a freelancer, she was missing close relationships with colleagues and teamwork, which she has now found in her current firm. Her colleagues describe her as a: “walking-talking bundle of superpowers: sports medicine and fitness professional, SEO expert, blogger, designer and a kitty foster mum”.
\n\n\n\n\n\n\n\nIf you are considering starting your career as a freelancer, take the courses offered at learn.wordpress.org, reach out to companies that you would be interested in working with, and remember that there are a whole host of opportunities in the WordPress project.
\n\n\n\nThe WordPress.org Teams – what they do, when and where they meet
\n\n\n\nLearn WordPress resource – free to use to expand your knowledge and skills of using the platform and learning about the community around it.
\n\n\n\nThe 3-day WordCamp Europe 2021 online event begins on 7 June 2021. You can discover more about being a contributor in its live sessions and section on ways to contribute to WordPress.
\n\n\n\nThanks to Olga Gleckler (@oglekler), Abha Thakor (@webcommsat), Chloé Bringmann (@cbringmann), Surendra Thakor (@sthakor), and Meher Bala (@meher) for working on this story. Josepha Haden (@chanthaboune) and also to Topher DeRosia (@topher1kenobe) who created HeroPress. Thank you to Tijana Andrejic (@andtijana) for sharing her #ContributorStory
\n\n\n\n\n\n\n\nThis post is based on an article originally published on HeroPress.com. It highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.
\n\n\n\nMeet more WordPress community members in our People of WordPress series.
\n\n\n\n#ContributorStory #HeroPress
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 07 Jun 2021 22:00: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:28:\"webcommsat AbhaNonStopNewsUK\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"BuddyPress: BuddyPress 8.0.0 “Alfano”\";s:7:\"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=319133\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"https://buddypress.org/2021/06/buddypress-8-0-0-alfano/\";s: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:11623:\"“Alfano” is our first major release of 2021. It is named after Alfano’s Pizza in Rock Island, Illinois, a family-run pizzeria that’s been around since the 1970s. They know how to keep it simple: there’s nothing on the menu but mouth-watering pizzas and calzones featuring their own made-from-scratch sauce and crust. For the true Alfano’s experience, order a stuffed pizza and dine in with as many friends as you can bring. The massive, two-crust pizza will be brought to the table piping hot, and there will be plenty for everyone!
\n\n\n\n \n\n\n\n\n\n\n\nYou can get it clicking on the above button, downloading it from the WordPress.org plugin directory or checking it out from our Subversion repository.
\n\n\n\nIf you’re upgrading from a previous version of BuddyPress, it’s always a good idea to back-up your WordPress database and files ahead of time.
\n\n\n\nYou can review all of the changes in this 8.0.0 release in the release notes. Below are the key features we believe you are going to enjoy most!
\n\n\n\n\n\n\n\nWhether public registration is enabled or not, you can activate this great new opt-in feature from your site’s BuddyPress settings; with it, your trusted members will handpick new members who will enrich your community.
\n\n\n\n\n\n\n\nOnce activated, each member will be able to send new Member Invitation emails and manage the pending invitations directly from his or her profile area.
\n\n\n\n\n\n\n\nYou keep control of everything thanks to two new screens we added to the BuddyPress Tools dashboard: invitations and opt-outs management.
\n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\nFirst, you can select any xProfile field from any xProfile field group to use on your site’s registration form. Second, if your site requires that users accept specific rules such as terms of service or a code of conduct, you can now take advantage of the new Checkbox Acceptance xProfile Field type to record their agreement.
\n\n\n\n\n\n\n\nThird, once a user activates his or her account, BuddyPress will send a welcome email to help get him or her engaged with your community. You can customize the content of this email from the Emails menu of your WordPress dashboard. Have a look to this developer note to find out more about it.
\n\n\n\n\n\n\n\nThe WP Biography field type lets you include the user’s Biographical Info and thanks to the WP Textbox field you can include the first & last name, the Website URL as well as any of the custom contact methods of your users.
\n\n\n\n\n\n\n\n \n\n\n\n\n\n\n\n8.0.0 includes more than 45 changes to improve the Activity component, the BP Nouveau Template pack, the BP REST API and many more components and features.
\n\n\n\n\n\n\n\nAdil Oztaser (oztaser), Ahmed Chaion (chaion07), Andrea Tarantini (dontdream), Boone B Gorges (boonebgorges), Brajesh Singh (sbrajesh), Charles E. Frees-Melvin (thee17), Christian Wach (needle), comminski, Dan Caragea (dancaragea), David Cavins (dcavins), dominic-ks, Eduardo Speroni (edusperoni), Fernando Tellado (fernandot), Giuseppe (mociofiletto), hz_i3, Ian Barnes (ianbarnes), Iker Garaialde (atxamart), Javier Esteban (nobnob), John James Jacoby (johnjamesjacoby), Krupa (krupajnanda), Laurens Offereins, mahdiar, Mark Robson (markscottrobson), Mathieu Viet (imath), mattneil, meijioro, Michal Janata (kalich5), modemlooper, Paul Gibbs (DJPaul), podporawebu, Peter Smits (psmits1567), Pieterjan Deneys (nekojonez), r-a-y, Renato Alves (espellcaste), renegade1, Slava Abakumov (slaffik), Stephen Bernhardt (sabernhardt), Stephen Edgar (netweb), studiocrafted, Timi Wahalahti (sippis), Tomas (mobby2561), Topher (topher1kenobe), Utsav tilava (utsav72640), Varun Dubey (vapvarun), Venutius, WeddyWood, Yordan Soares (yordansoares).
\n\n\n\n\n\n\n\nReceiving your feedback and suggestions for future versions of BuddyPress genuinely motivates and encourages our contributors. Please share your feedback about this version of BuddyPress in the comments area of this post. And of course, if you’ve found a bug: please tell us about it into our Support forums.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 07 Jun 2021 19:45: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:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"WordPress.org blog: WP Briefing: Episode 10: Finding the Good In Disagreement\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=10424\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wordpress.org/news/2021/06/episode-10-finding-the-good-in-disagreement/\";s: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:12066:\"To Agree, disagree, and everything in-between. In this episode, Josepha talks about forming opinions and decision-making in the WordPress project.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nEditor: Dustin Hartzler
\n\n\n\nLogo: Beatriz Fialho
\n\n\n\nProduction: Chloé Bringmann
\n\n\n\nSong: Fearless First by Kevin MacLeod
\n\n\n\nWordPress 5.8 Development Cycle
\n\n\n\nJosepha Haden Chomphosy 00:10
\n\n\n\nHello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Joseph Haden Chomphosy. Here we go!
\n\n\n\nJosepha Haden Chomphosy 00:40
\n\n\n\nFor anyone who has ever organized something, whether it’s a social event, a school project, or an annual family gathering, you know that there are many different opinions. The more opinions you have, the more likely people don’t see eye to eye. And before you know it, you’ve got some disagreements. Some things make disagreements worse, like imbalance of information, lack of showing your work, and sometimes just “too many cooks in the kitchen,” to use a regional phrase. Frankly, sometimes it seems like the second you have more than one cook in your kitchen, you’re going to get some disagreements. But I think that’s a healthy thing. WordPress is huge. And there are huge numbers of people contributing to WordPress or any other open source project you want to name. So there’s a lot of stuff available to disagree about. If we never saw anyone pointing out an area that wasn’t quite right, there would probably be something wrong. If you, like me, think that a healthy tension of collaborative disagreement can be useful when approached thoughtfully, then this quick start guide is for you.
\n\n\n\nStep one, prepare to host a discussion. This is, by the way, just the hardest step out there. You have to take a little time to figure out what problem you’re solving with the solution you’re suggesting, any goals that it relates to, and then figure out what the bare minimum best outcome would be and what the wildest dreams magic wand waving outcome would be. And you have to be honest with yourself.
\n\n\n\nStep two, host the discussion. The venue will be different for different discussions, but you see a lot of these on team blogs or within the actual tickets where work is being done. Wherever you’re hosting it, state the problem, state your idea for the solution and ask for what you missed. If you’re hosting a discussion in person, like in a town hall format, this can be hard. And generally, hosting discussions in an in-person or voice call or zoom call kind of way is hard. So if you have an opportunity to start doing this in text first and level your way up to in person, that’s my recommendation.
\n\n\n\nStep three is to summarize the discussion and post a decision if possible. So organizing a big discussion into main points is a really good practice for the people you’re summarizing it for and yourself. It helps you to confirm your understanding, and it also gives you the chance to pair other solutions with the problem and goals you outlined in step one. If a different solution solves the same problem but with less time or effort, it’s worth taking a second look with less time or effort. There’s something that I say to WordPress contributors frequently, and that is there are a lot of yeses. There are a lot of right ways to do things and only a few clear wrong ways to do things. So be open-minded about whether or not someone else’s right way to do things could still achieve the goals you’re trying to accomplish with your solution. A note on step three where I said, “and post the decision if possible.” Sometimes you’re the person to make that decision, but sometimes you are not the person who can give something the green light, and so you’re preparing a recommendation. Whether you’re making a decision or a recommendation, sometimes you may experience a little decision-making paralysis. I know I do. So here are a few of the tools that I use.
\n\n\n\nIf you’re avoiding the decision, use the 10/10/10 rule; it can help you figure out if you’re stuck on a short-term problem. If there are too many good choices, use the Eisenhower Matrix that can help you to prioritize objectively. If there are too many bad choices, use the Maximin strategy. It can help you to identify how to minimize any potential negative impacts.
\n\n\n\nOkay, so you’ve considered your position. You’ve discussed everything. You summarized the big points. Maybe you also worked your way through to a recommendation or a decision. What about everyone who disagreed with the decision? Or have you made a recommendation, and it wasn’t accepted? How do you deal with that? That’s where “disagree and commit” shows up. This phrase was made popular by the folks over at Amazon, I think. But it first showed up, I believe at Sun Microsystems as this phrase, “agreeing, commit, disagree and commit or get out of the way.”
\n\n\n\nJosepha Haden Chomphosy 05:34
\n\n\n\nDisagree and commit as a concept works pretty well when everyone agrees on the vision and the goals, but not necessarily how to get to those goals. We’ve had moments in recent history where folks we’re not able to agree, we’re not able to commit, and so then left the project. I hate when that happens. I want people to thrive in this community for the entire length of their careers. But I also understand that situation shows up in the top five learnings of open source when you no longer have interest in the project and handed it off to a competent successor. So there it is – disagreements in open source in WordPress.
\n\n\n\nAs with so many of the things I discuss on this podcast, this is incredibly complex and nuanced in practice. Taking an argument, distilling facts from feelings, and adjusting frames of reference until the solution is well informed and risk-balanced. That is a skill set unto itself. But one that increases the health of any organization. I’ll share that list of references and general materials in the show notes, including a link explaining each of those decision-making tools that I shared. I’m also going to include the contributor training module on decision-making in the WordPress project. It’s got excellent information. It’s part of a series of modules that I asked team reps to take and sponsored contributors. I don’t require it from anyone, but I do hope that it is useful for you. Also, speaking of useful for you, if you are just here for leadership insights, I included some hot takes after the outro music for you. It’s like an Easter egg, but I just told you about it.
\n\n\n\nJosepha Haden Chomphosy 07:33
\n\n\n\nAnd that brings us to our small list of big things! First off, WordCamp Europe is happening this we; I hope that everybody has an opportunity to attend. If you still haven’t gotten your tickets, they are free, and I think there are still a few left. I will include a link in the show notes as well. There’s going to be a little demo with Matt Mullenweg and Matias Ventura on the WordPress 5.8 release that’s coming up. And then kind of a retrospective discussion between Matt and Brian Krogsgard. I encourage you to join; I think it’s going to be very interesting.
\n\n\n\nThere’s also WordCamp, Japan coming up June 20 through 26th. I mentioned it last time – it has a big section of contributing and contribution time. So if you’re looking to get started, some projects are laid out, and I encourage you to take a look at that as well.
\n\n\n\nThe new thing on this list, and I don’t know how new It is, in general, I hope it’s not too new to you, is that WordPress 5.8 release is reaching its beta one milestone on June 8th, so right in the middle of WordCamp Europe. I encourage every single theme developer, plugin developer that we have, agency owners that we have to really take a look at this release and dig into testing it. It’s a gigantic release. And I have so many questions about what will work and will not work once we get it into a broader testing area. We’ve been doing a lot of testing in the outreach program. But it’s always helpful to get people who are using WordPress daily in their jobs to really give a good solid test to the beta product to the beta package. And put it all through its paces for us.
\n\n\n\nSo, that my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\n\n\nJosepha Haden Chomphosy 10:09
\n\n\n\nHey there, you must be here because I told you about this totally not hidden easter egg about my hot takes on organizational health; I have three for you. And if you’ve ever worked with me, none of this will surprise you. But if you haven’t worked with me, hopefully, it kind of gives you some idea about how I approach all of this a bit differently. So, number one, critical feedback is the sign of a healthy organization. And I will never be dissuaded from that opinion. A complete lack of dissent doesn’t look like “alignment.” To me, that looks like fear. And it goes against the open source idea that many eyes make all bugs shallow.
\n\n\n\nTip number two, a bit of tension is good, a bit of disagreement is good. The same thing that I say about women in tech, we’re not all the same. And if we were, then we wouldn’t need to collaborate anyway. But diversity, whether that’s the diversity of thought or of a person or of experience, just doesn’t happen without some misunderstandings. It’s how we choose to grow through those misunderstandings that make all the difference for the type of organization we are.
\n\n\n\nAnd hot take number three, changing your mind isn’t flip-flopping or hypocritical. I think that’s a sign of growth and willingness to hear others. I like to think of my embarrassment at past bad decisions – as the sore muscles of a learning brain. And I, again, probably won’t be dissuaded from that opinion. Although, you know, if I’m sticking true to changing your mind some flip-flopping or hypocritical, maybe I will, but you can always try to, to give me the counter-argument for that, and we’ll see how it goes. Thank you for joining me for my little public easter egg.
\";s: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 Jun 2021 12:22: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:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"Gutenberg Times: Themes for Full-Site Editing and Getting ready for WordPress 5.8 – Weekend Edition #172\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=18038\";s:7:\"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:112:\"https://gutenbergtimes.com/themes-for-full-site-editing-and-getting-ready-for-wordpress-5-8-weekend-edition-172/\";s: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:19478:\"Howdy,
\n\n\n\nIt’s the eve of the second virtual WordCamp Europe. Tickets are still available for another awesome three days with talks, workshops and contributor events. This year, the organizer decide to sprinkle contributor event into the rest of the schedule and have for all three days, a mix between techtalk, business talks and contributor presentation and discussions. There are quite a few events around the Block editor, Full-site-editing and block-based themes. I compiled a list for you. And just because I am so focused on Gutenberg, doesn’t mean you have to. 😎 Check out the schedule and get your tickets now.
\n\n\n\nHopefully, it will be the last virtual conference and we will see each other at an in-person WordCamp Europe in 2022. I am still hoping for Porto, Portugal. At this state of withdrawal from meeting WordPress friends in person, it doesn’t matter where it will take place, thought. It’ll be a Hug-Fest.
\n\n\n\nLast week, I mentioned the next Gutenberg Times Live Q & A in the subscribers-only section of this newsletter. Now we have a full panel. Registration is officially open. I am thrileed to host Daisy Olsen, Jeff Ong and Tammie Lister for our show on How to get started on Theme building for Full-site Editing and using the Theme.json file to configure your theme, and its interaction with the block editor. The Theme.json file will be introduced with the release of WordPress 5.8 in July 2021. Get a head start and join us!
\n\n\n\nGrzegorz (Greg) Ziolkowski will be back from vaction next week and we will record our next Changelog episode on Friday 11, 2021. I am so excited and can’t wait until Grzegorz is back! If you have questions or suggestions or news, you want us to consider, hit reply or send them to changelog@gutenbergtimes.com. We now have consitently 500 – 800 downloads per week. It’s humbling, mind-boggling and inspiring. And if YOU are a listener, Thank You! If you have a minute or two, consider writing a review of the podcast. We’d be grateful and might read it out loud on the next show.
\n\n\n\nAlright, that’s the news around Gutenberg Times. Below you’ll find what else happened in the Gutenberg universe. Enjoy!
\n\n\n\nYours, 💕
Birgit
PS: Hope to see you at WordCamp Europe. Don’t forget to join the #WCEU channel on WordPress Slack and meet speaker, sponsors, organizer and attendees like you and me.
\n\n\n\n\n\nAnne McCarthy published the Stick the landing (pages) Summary. This post is a summary of the sixth call for testing for the experimental FSE outreach program, which also was translated into Italian to reach more of the non-English audience. Earlier calls were also translated into Japanese. The group of FSE testers is much bigger now, thanks to the persistent efforts by Anne to reach out to the community and stay on top of all the issues around the template editor.
\n\n\n\nA reminder: You can still join the the seventh call for testing: Polished Portfolios – The deadline for your feedback was extended to June 16th, 2021.
\n\n\n\nIf you read this before Sunday night, you can participate in the Full Site Editing Review and Test-a-thon Sunday, June 6th at 7 – 8:30 pm with the WordPress Meetup group in Philadelphia.
\n\n\n\nReading through the summary, I am stuck on trying to understand the difference between a template built by the site-owner and a theme template. What will happen with their templates when the site-owner decides to change the overall theme of their site? There is still plenty to be figured out. How edited block templates are linked to themes is topic of the discussion on GitHub. The Gutenberg team would appreciate some thoughts from folks familiar with these APIs (theme mods, performance, database).
\n\n\n\nKjell Reigstad posted again acomprehensive list of issues and discussions regarding block-based themes and Full-Site Editing: Gutenberg + Themes: Week of May 31, 2021. Any of the listed items are worth checking out and consider commenting. The more the team knows the better the next iteration of Full-Site editing and block-based themes becomes.
\n\n\n\nFrom the meeting notes of this week’s Dev Chat: “Docs needs the most help with end user documentation. For block editor in particular. Some changes from 5.6 and 5.7 are still not published and we had a significant drop in number of contributors due to pandemic situation. Anyone interested in getting involved please ping Milana Cap (zzap on Slack).
\n\n\n\nThe summary of needed DevNotes for new features in WordPress 5.8 is available on GitHub and could use contributors. There is also a “needs dev note” label for pull requests.
\n\n\n\nThe widget screen could use some more testing. As a reminder, please read Help Test the Widgets Editor for WordPress 5.8 by Andre Draganescu
\n\n\n\nHector Pietro wrote in his post What’s next in Gutenberg? (June 2021):
\n\n\n\n“Since Gutenberg 10.7, block patterns displayed in the inserter are fetched from the WordPress.org Pattern Directory. This opens the door to having a big amount of wonderful patterns available in the inserter, which will require iterating on the pattern insertion experience.
\n\n\n\nFor more updates on the Pattern Directory, stay tuned for Block Pattern Directory updates and check the most recent design iterations for the Pattern Directory.”.
\n\n\n\nFeatured Box Plugin with this plugin “you can highlight a image with your key features” wrote Sumaiya Siddika on WordPress.org. Justin Tadlock took it for a spin.
\n\n\n\nJetFormBuilder — Form Builder plugin for Gutenberg from the plugins stable at CrocoBlock. The developers Andrey Shevchenko and Oleksandr Ivanenko also added an extensive Post action hook system that allows you to daisy chain actions and integrated with 3rd party systems. I haven’t tested it yet, but it looks promising. Crocoblock has been building plugins and tools for Elementor and has now started supporing Gutenberg with their products as well.
\n\n\n\nAnother new plugin is the JetEngine for Gutenberg a dynamic content plugin that lets you build a complex websites fast and cost-effectively.
\n\n\n\nA few people ask about Themes that are already working with the Full-Site Editing system and Site Editor. So I put a list together of those I know about. Now before you use them, you need to be aware that they are all built while Full-Site Editing is still under active development, hasn’t been released yet and ergo many features are still experimental. Do not use in production or live site.
\n\n\n\nIf you find any missing, let me know.
\n\n\n\nThis week’s big WordPress business news is the aquisition of Eliots Condon‘s plugin Advanced Custom Fields (ACF) by Delicious Brains. With over more then 1 million active installs ACF is one of the widest used plugins. Thousands for developers depened on it in the last ten years to build complex WordPress sites.
\n\n\n\n\n\n\n\nStepping away from ACF has not been an easy decision to make. The reasoning behind it comes from a place of humility. As the number of installs have grown from thousands to millions, the needs of the product have outgrown my ability to develop solutions. The last thing I want to do to this amazing community is unintentionally hold back the project, so something needed to change.
Elliot Condon, ACF
Early on into the development of the block editor, Candon was also developing a php way to build blocks and integrated it into Advanced Custom Fields Pro starting with the version 5.8. This effort certainly helped developers even more. Now they could use their existing tools and offer their users Gutenberg compatible sites withouth learning ES6 JavaScript or ReactJS.
\n\n\n\nDelicious Brains also caters to WordPress Developers with products like SpinupWP (💕), WP Migrate DB and more. Their team seems to be the right fit to pick up the torch and put ACF on an even stronger path for future growth.
\n\n\n\nYou can learn more about the aquisition via
\n\n\n\nJoin us for our next Live Q & A
on June 24, 2021 at 11am EDT / 15:00 UTC
Theme.json for Theme Authors or building themes for full-site editing in WordPress.
Host: Birgit Pauli-Haack
Panel: Daily Olson, Tammie Lister and Jeff Ong Register Now
June 6, 2021 7:00 pm EDT / 23:00 UTC
WordPress Meetup Philadelphia
Full Site Editing Review and Test-a-thon
June 7 – 9th, 2021
WordCamp Europe
A virtual event and contributor day. Call for sponsors is open.
🎉 Gutenberg Times is a media partner of WordCamp Europe 2021
\n\n\n\nJune 10th, 2021
WordPress “Mega Meetup”: Plugins That Keep Websites Running
June 20 – 26, 2021
WordCamp Japan
The schedule has been posted. Most sessions will be in Japanese, with exceptions, I think…
June 24, 2021
WPEngine Summit 2021
The digital breakthrough conference just released their schedule. Personally, I am very much looking forward to the Keynote talk with Reshma Saujani, founder of Girls Who Code and Marchall Plan for Moms at 12:55 EDT / 16:55 UTC. I also hope to see talks with Rob Stinston, Carrie Dils and Chris Wiegman. There are also deep dive talks listed into Headless WordPress. Enterprise WordPress is definitely heading down that route.
June 24 – 26, 2021
WordCamp Cochabama (Colombia)
July 17 + 18th, 2021
WordCamp Santa Clarita
Calls for speakers ends TODAY!
July 23, 2021
WordFest Live – The festival of WordPress
August 6 + 7, 2021
WordCamp Nicaragua
September 21 + 22, 2021
WPCampus 2021 Online
“A free online conference for web accessibility and WordPress in higher education.”
On the Calendar for WordPress Online Events you can browse a list of the upcoming WordPress Meetups, around the world, including WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.
\n\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nFeatured Image: Photo by Xavi Cabrera on Unsplash
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 05 Jun 2021 19:32:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"Gutenberg Times: WordCamp Europe 2021 starts Monday\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=17964\";s:7:\"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:62:\"https://gutenbergtimes.com/wordcamp-europe-2021-starts-monday/\";s: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:6939:\"WordCamp Europe 2021 will be one of the largest virtual WordCamps again and the schedule has some great talks for every WordPress users, developers, site builders, theme designers, DIY site owners and content creators.
\n\n\n\nWe looked through the schedule and spotted very forward-looking Gutenberg related talks, workshops and discussions. Before you study the list, I would recommend the site Time Zone Converter to help you convert the listed times from Central Europe Summer Time (CEST) to your local time. Once in a while I get confused by time zones, and that’s my favorite site to set me straight.
\n\n\n\n\n\n\n\nFabian Kägy, developer at 10up:
Building great experiences in the new editor
Description: Starting out building blocks or experiences for the WordPress block editor can be a bit daunting. Where do I start? Custom blocks, block patterns or just styling core blocks. In this talk, Kägy will walk through the different options and share the benefits and downsides of each while talking about overall good practices for building great editorial experiences.
\n\n\n\nAs a sidenote: Almost exactly a year ago, Fabian Kägy was a presenter at a Gutenberg Times Live Q & A together with Grzegorz Ziolkowski, and demo’d how you can use and extend the official WordPress create-block scaffolding tool.
\n\n\n\nMonday, June 7th, 2021, at 10am EDT / 14:00 UTC / 16:00 CEST
\n\n\n\nThe names of the panelist are still a secret, and I will update the post when we know more.
\n\n\n\nIf you’d like to get a jump start here are few resources:
\n\n\n\nMonday, June 7, 2021 at 12:34 pm EDT / 16:34 UTC / CEST: 18:34
\n\n\n\nWorkshop: A walkthrough of Full Site Editing with Herb Miller, Web developer in UK,
\n\n\n\n\n\n\n\nDescription: Herb Miller will give a short tour of Full Site Editing (FSE) in this workshop from his perspective as a contributor to the outreach experiment for this major development in WordPress.
\n\n\n\nHe has created a learning resource which attendees can use to follow on during the workshop.
\n\n\n\nHerb will give attendees an overview of:
\n\n\n\nTuesday, June 8th, 2021 11am EDT / 15:00 UTC / 17:00 CEST
\n\n\n\nLee Shadle, web developer Blazing fast block development
\n\n\n\n\n\n\n\nLee Shadle wrote in his description: “I’ve been OBSESSED w/ building blocks since before Gutenberg was released. I’ve built a BUNCH of custom block plugins over the years. In this workshop I’m going to share the framework I’ve been using for quickly building custom block plugins for WordPress.”. Shadle recently also held a talk at WordSesh and demo’d his create-block-plugin scaffolding tool and it was inspiring. This is definitely not a talk to miss.
\n\n\n\nTuesday June 8, 2021 12:00 EDT / 16:00 UTC / 18:oo CEST
\n\n\n\nThe Future of Themes in WordPress
\n\n\n\nThe future of themes will be a topic of this panel discussion. Stay tuned or follow WordCamp Europe on Social Media (Twitter, Facebook, Instagram).
\n\n\n\nJoin us for our next Live Q & A
on June 24, 2021 at 11am EDT / 15:00 UTC
Theme.json for Theme Authors or building themes for full-site editing in WordPress.
Host: Birgit Pauli-Haack
Panel: Daily Olson, Tammie Lister and Jeff Ong Register Now
Conversation with Matt Mullenweg
\n\n\n\nMatt Mullenweg is the co-founder of WordPress and the CEO of Automattic. The conversation should be the highlight of the WordCamp Europe
\n\n\n\nWednesday, June 9th, 2021 – 11:42 EDT / 15:42 UTC / 17:42 CEST
\n\n\n\nThis edition of the WordCamp Europe also offers interesting Sponsor talks. Look for them on the schedule, too.
\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 05 Jun 2021 04:00: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:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"Gutenberg Times: So, You want to talk about Full-site Editing?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=17970\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://gutenbergtimes.com/so-you-want-to-talk-about-full-site-editing/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:16852:\"\n\n\n\nAs we’re nearing 5.8, there’s an increasing demand for people to speak about Full Site Editing and this post should help act as a resource guide to enable more people to do so. As always, I would love contributions from the wider community to build this out into an even more comprehensive resource! While this post covers a lot of content, see it as a go to place to mix and match as you’d like for your own presentation rather than something you need to know every detail of. For example, if you’re presenting to theme authors, you can use this to get a sense at a glance of what might be relevant from what to demo, what resources to share, what GitHub issues to highlight, and more.
\n\n\n\nJoin us for our next Live Q & A
on June 24, 2021 at 11am EDT / 15:00 UTC
Theme.json for Theme Authors or building themes for full-site editing in WordPress.
Host: Birgit Pauli-Haack
Panel: Daily Olson, Tammie Lister and Jeff Ong Register Now
Depending on who you are and who the audience, the following are your best bets for demo content:
\n\n\n\nThese are the top questions you can most likely expect to get asked with high level answers to get you started in the right direction. For a more comprehensive list of questions and answers, check out the FSE Outreach Program’s roundups.
\n\n\n\nFull Site Editing is a collection of features that bring the familiar experience and extendability of blocks to all parts of your site rather than just post and pages. In terms of value, it depends on who you are:
User: empowerment to customize what you want to your liking without needing to dive into code.
Themer/developer: focus less on coding thanks to various design tools and more on creating a compelling experience with your theme.
Agency: greater control and consistency over what you offer clients including things like setting custom branding colors or locking down various aspects of the site such as typography settings.
When you see or feel this value depends on who you are, how early you adopt features, and when stable features land in Core. Thanks to FSE being a collection of features, some independent and some interdependent, there’s wonderful room to ship what’s stable.
In the long run, it should make theme development much easier and simpler with design tools ready to tap into allowing theme authors to focus less on coding and functions and more on design expression and aesthetics. Because Full Site Editing requires a block based theme, this makes themes extremely important to get right! As a result, lots of pathways are being created including the ability to use theme blocks in a classic theme, exploring how to use the customizer and site editor as part of a “universal theme”, unlocking the ability to create a new block template in a classic theme, allowing classic themes to adopt the block widget editor, and more.
Key: Themes are a key part of the FSE experience, lots of work is being done to allow for a breadth of options going forward, and we need feedback from theme authors to make the transition easier.
FSE is being built in a way that site builders, if they choose to, can build on top of what’s being created. Overall though, FSE is being built partially so people don’t get locked into one site builder over another. While the goals shared between FSE and site builders are similar in terms of empowering users and give better tools to customize a site, the main difference is that we are developing tools that work for users, themers, and hopefully also page builders by expanding how WordPress uses blocks as a whole. Since Core has to strike a nice balance, it’s expected that future plugins will play a role here in exposing more/less depending on user needs.
This will depend on who is asking the question (a user, a theme author, a developer, etc) but some of the GitHub issues referenced above should help. For users, I’d focus on the fact that they would either need to seek out a block theme to use or their current theme would need to ship specific updates. For a themer/developer, I’d share that there will be various options to opt in and out of this work (for example with creating block templates). Upcoming 5.8 dev notes should address this for any new features.
No. 5.8 is focused on giving tools to extenders first and foremost before more user facing changes are launched going forward and integrated into themes. In terms of user facing features, you can expect to see
Anne McCarthy published this post on her personal blog and gave us permission to republish it here as well.
\n\n\n\nJoin us for our next Live Q & A
on June 24, 2021 at 11am EDT / 15:00 UTC
Theme.json for Theme Authors or building themes for full-site editing in WordPress.
Host: Birgit Pauli-Haack
Panel: Daily Olson, Tammie Lister and Jeff Ong Register Now
Jetpack 9.8 was released this week, introducing WordPress Stories as the headline feature. The Story block, which allows users to create interactive stories, was previously only available on mobile. It can now be used in the web editor. Stories went into public beta on the Android app in January 2021, and were officially released on the mobile apps in March.
\n\n\n\nVersion 9.8 also included a security patch for all sites using the Carousel feature. The vulnerability allowed the comments of non-published pages/posts to be leaked. It was severe enough for the Jetpack team to work with WordPress.org to release 78 patched versions – every version of Jetpack since 2.0. Sites not using the Carousel feature were not vulnerable but could be in the future if it was enabled and left unpatched.
\n\n\n\nIn a rare move, WordPress.org pushed a forced update to all vulnerable versions, surprising those who have auto-updates disabled. Several Jetpack users posted in the support forums, asking why the plugin had updated automatically without permission and in some cases not to the newest version.
\n\n\n\n \n\n\n\nJetpack team member Jeremy Herve said the vulnerability was responsibly disclosed via Hackerone, allowing them to work on a patch for the issue. After it was ready to go, the Jetpack team reached out to the WordPress.org security team to inform them of a vulnerability impacting multiple versions of the plugin.
\n\n\n\n“We sent them the patch alongside all the info we had (a PoC for the vulnerability, what features had to be active, what versions of Jetpack were impacted),” Herve said. “They recommended we release point releases for older versions of Jetpack as well.
\n\n\n\n“We created those new releases, and when we were ready to release them, someone from the WordPress.org team made some changes on the WordPress.org side so folks running old, vulnerable versions of the plugin would get auto-updated, just like it works for Core versions of WordPress.”
\n\n\n\nJetpack team member Brandon Kraft estimated the number of vulnerable sites at 18% of the plugin’s active installs. He said that Jetpack was not part of the discussion about the pushing out a forced update.
\n\n\n\n \n\n\n\n“What probably adds to the confusion is that WordPress 5.5 added a UI for plugin (and theme) autoupdates,” Herve said. “That UI, while helping one manage plugin autoupdates on their site, is a bit different from Core’s forced update process. Both of those update types can be deactivated by site owners, just like core’s autoupdates can be deactivated, but I don’t believe (and honestly wouldn’t recommend) that many folks deactivate those updates.”
\n\n\n\nBrandon Kraft dug deeper into the topic and published a post that explains the differences between auto-updates and forced updates. It includes how to lock down file modifications if you don’t want to receive any forced updates in the future. Forced updates, however, are exceedingly rare, and Kraft counts only three for Jetpack since 2013.
\n\n\n\nIn this instance, the Jetpack team followed the official process for reporting a critical vulnerability to the plugin and security teams who determine the impact for users based on a set criteria. Users who received an email notification about an automatic update from Jetpack, despite having the UI in the dashboard set to disable them, should be aware that these forced updates can come once in a blue moon for security purposes.
\n\n\n\nTony Perez, founder of NOC and former CEO at Sucuri, contends that forcing a security update like this violates the intent users’ assign when using the auto-updates UI in WordPress. He highlighted the potential for abuse if the system were to become vulnerable to a bad actor.
\n\n\n\n“The platform is making an active decision that is arguably contrary to what the site administrator is intending when they explicitly say they don’t want something done,” Perez said. “Put plainly, it’s an abuse of trust that exists between the WordPress user and the Foundation that helps maintain the project.
\n\n\n\n“My position is not that it shouldn’t exist. That’s a much deeper ideological debate, but it is about respecting an administrators explicit intent.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 05 Jun 2021 00:04:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"WPTavern: Create Per-Post Social Media Images With the Social Image Generator WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=117539\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:233:\"https://wptavern.com/create-per-post-social-media-images-with-the-social-image-generator-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=create-per-post-social-media-images-with-the-social-image-generator-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6689:\"\n\n\n\nIt was a bit of a low-key announcement when Daniel Post introduced Social Image Generator to the world in February via tweet. But, when you get repped by Chris Coyier of CSS-Tricks and the co-founder of WordPress uses your plugin (come on, Matt, set a default image), it means your product is on the right track.
\n\n\n\nI am not easily impressed by every new plugin to fly across my metaphorical desk. I probably install at least a couple dozen every week. Sometimes, I do so because something looks handy on the surface, and I want to see if I can find some use for it. Other times, I think it might be worth sharing with Tavern readers. More often than not, I consider most of them cringeworthy. I have high standards.
\n\n\n\nAs I chatted with Post about this new plugin, I was excited enough to call Social Image Generator one of those OMG-where-have-you-been? types of plugins. You will not hear that from me often.
\n\n\n\nPost quit his day job to venture out earlier this year, creating his one-man WordPress agency named Posty Studio. Social Image Generator is its first product.
\n\n\n\n“I kept seeing tutorials on my Twitter feed on how to automatically generate images for your social media posts, but unfortunately, they all used a similar approach (Node.js) that just wasn’t suitable for WordPress,” said Post of the inspiration for the plugin. “This got me thinking: would it be possible to make this for WordPress? I started playing around with image generation in PHP, and when I got my proof of concept working, I realized that this might actually be something I should pursue.”
\n\n\n\nIn our chat over Slack, we actually saw the plugin in action. As he shared Coyier’s article from CSS-Tricks, the chatting platform displayed the social image in real-time.
\n\n\n\nAuto-generated image appearing via Slack.\n\n\n\nMaybe it was fate. Maybe Post knew it would happen and thought it would be a good idea to show off his work as we talked about his project. Either way, it was enough to impress the writer who is unafraid to call your plugin a dumpster fire if he smells smoke.
\n\n\n\nPost seems to be hitting all the right notes with this commercial plugin. It has a slew of features built into version 1.x, which we will get to shortly. It is dead simple to use. It is something nearly any website owner needs, assuming they want to share their content via social networks. And, with a $39/year starting price, it is not an overly expensive product for those on the fence about buying.
\n\n\n\nAfter installing and activating Social Image Generator, users are taken to the plugin’s settings screen. Other than a license key field and a button for clearing the image cache, most users will want to dive straight into the template editor.
\n\n\n\nAt the moment, the plugin includes 23 templates. From Twenty Seventeen to Twenty Twenty-One, each of the last four default WordPress themes also has a dedicated template. After selecting one, users can customize the colors for the logo, post title, and more — the amount of customization depends on the chosen template.
\n\n\n\nBrowsing the plugin’s templates.\n\n\n\nAside from selecting colors, users can choose between various logo and text options. They can also upload a default image for posts without featured images.
\n\n\n\nEditing a template from Social Image Generator.\n\n\n\nWhen it comes time to publish, the plugin adds a meta box to the post sidebar. Users can further customize their social image and text on a per-post basis.
\n\n\n\nSocial image preview box on the post-editing screen.\n\n\n\nOnce published, the plugin creates an image that will appear when a post is shared on social media.
\n\n\n\nOn the whole, there is a ton that anyone can do with the built-in templates. There is also an API for developers to create their own. For a first outing, it is a robust offering. However, there is so much more that can be done to make the plugin more flexible.
\n\n\n\nThus far, Post said he has received tons of positive feedback along with feature requests. Primarily, users are asking for more customization options and the ability to create and use multiple templates. These are the focus areas for the next version. With a 1,718% increase in revenue in the past month, it seems he might have the initial financial backing to invest in them.
\n\n\n\n“I’ve started building a completely overhauled drag-n-drop editor, which will allow you to create basically any custom image you want,” he said. “It will be heavily inspired by the block editor, and I want to keep the UI and UX as close to the block editor as possible.”
\n\n\n\nThe new template editor would allow users to create multiple layers, an idea similar to how Photoshop, Gimp, and other image-editing software works. The difference would be that it can pull in data from WordPress.
\n\n\n\n“For example, an ‘Image’ layer will have options such as height/width and positioning, as well as some stylistic options like color filters and gradient overlays,” said Post. “A ‘Text’ layer can be any font, color, and size and can show predefined options (post title, date, etc.) or whatever you want. You can add an infinite number of layers and order them however you’d like.”
\n\n\n\nHe seems excited about opening up new possibilities with an overhauled editor. Users could potentially create social image templates for each post type. A custom layer might pull in post metadata, such as displaying product pricing or ratings from eCommerce plugins like WooCommerce.
\n\n\n\n“The prebuilt templates will still exist, similar to Block Patterns in the block editor,” said the plugin developer. “They will, however, serve as a starting point rather than the final product. I’ll also try to implement theme styling as much as possible.
\n\n\n\n“The possibilities here are so endless, and I’m incredibly excited for this next part.”
\";s: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 Jun 2021 23:59:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: Building Featured Boxes With the WordPress Block Editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=117803\";s:7:\"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:175:\"https://wptavern.com/building-featured-boxes-with-the-wordpress-block-editor?utm_source=rss&utm_medium=rss&utm_campaign=building-featured-boxes-with-the-wordpress-block-editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6333:\"It is a new day with another chase for that elusive block plugin that will bring a little joy into my life. Today’s experiment comes courtesy of the Feature Box plugin by Sumaiya Siddika. It is a simple block that allows end-users to upload an image and add some content to an offset box.
\n\n\n\nThe plugin’s output is a typical pattern on the web. As usual, I am excited to see plugin authors experimenting with bringing these features to WordPress users. I want to see more of it, especially from first-time plugin contributors.
\n\n\n\nI was able to quickly get the block up and running, adding my custom content. The following is what the block looked like after entering my content and customizing it. I envisioned myself as a recipe blogger for this test.
\n\n\n\nInserting and modifying the Feature Box block.\n\n\n\nOn a technical level, the plugin worked well. I ran into no errors. Everything was simple to customize. However, it never felt like an ideal user experience.
\n\n\n\nThe first thing I immediately noticed is that image uploading happens in the block options sidebar. Core WordPress blocks have a dedicated button in the toolbar for adding images and other media. I also found myself wanting more direct control over individual elements. How could I change the heading font size? Where were the typical button styles like Outline and Solid Color? How do I insert other blocks, like a list?
\n\n\n\nNone of those things were possible. Like many other blocks, the developer has created a system with specific parameters, and the user cannot move outside of them. There are times when that rigidity makes sense, such as when building custom blocks for clients. However, more often than not, publicly-released plugins should be far more open.
\n\n\n\nThis tightly controlled block is reflective of how WordPress worked in the past. It was often inflexible, leaving users to what theme and plugin developers thought was best for their sites.
\n\n\n\nThe block system is about tossing out these overly rigid concepts and giving users power over their content. The job of plugins and themes is to define the framework the user is operating under. They set up some rules to more or less keep things from breaking, but the users get to strap themselves into the driver’s seat. Their destination is their own.
\n\n\n\nThe block would have been far more well-rounded if users could control all of the content in the box. Ideally, they could put whatever blocks they wanted into the “content” area of the Feature Box block. The design would match their theme better too.
\n\n\n\nA couple of weeks ago, I wrote a post titled You Might Not Need That Block. The premise was that users could recreate some blocks with the current editor and that themers could make this easier by offering patterns.
\n\n\n\nI knew replicating this particular block would be impossible without at least a little custom code. WordPress’s editor does not have a feature for offsetting a block’s position.
\n\n\n\nA theme author could easily duplicate this functionality. Typically, I would create a custom pattern, complete with all the existing pieces in place. However, I wanted to approach this with custom block styles. This would allow end-users to select the content offset from the sidebar and switch it around if needed.
\n\n\n\nNote: For those who wish to learn how to create custom block styles, Carolina Nymark’s tutorial is the best resource.
\n\n\n\nThe Cover block made an ideal candidate for this. Because it has an existing “inner wrapper” element, it meant that I could target it with CSS and move it around. The following is a screenshot of the Offset Left style I created:
\n\n\n\nOffset Left Cover block style.\n\n\n\nI simply replicated the code and changed a few values to create an Offset Right style immediately after. The code is available as a GitHub Gist. It is a simple proof-of-concept and not a polished product. There are various approaches to this, and several Cover block options are left unhandled. Theme authors are free to take the code and run with it.
\n\n\n\nThese block styles looked far better because they matched my theme. Everything from the spacing to the border-radius to the button looked as it should.
\n\n\n\nThe big win was that I had design control over every aspect of the content box. I could select the button style I wanted. I could change my font sizes. The default spacing matched my theme as it should.
\n\n\n\nThe problem I ran into with the block style method is allowing users to control the content box’s background color. The Feature Box plugin wins in the user experience category here because it has an option for this. The block style I created inherits its background from the Cover block parent. It may not be immediately obvious how to change it.
\n\n\n\nThe other “problem” with the block style is that it does not handle wide and full alignments for the Cover block. That is because I did not take the experiment that far, only replicating the plugin’s layout. I will leave that to theme designers to tinker around with. There are many possibilities to explore; don’t wait for me to provide all the ideas.
\n\n\n\nMy goal with this post and similar ones is to show how I would approach these things as both a user and developer. As a user, I want flexibility in all things. As a developer, I want to provide the solutions that I desire as a user.
\n\n\n\nI also want to see plugin and theme authors thinking beyond their initial use case when building blocks, patterns, styles, and more. Lay the groundwork. Then, expand on that initial idea by thinking of all the ways that users might want to customize what you have built.
\";s: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 Jun 2021 05:07:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: Delicious Brains Acquires Advanced Custom Fields Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=117769\";s:7:\"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:175:\"https://wptavern.com/delicious-brains-acquires-advanced-custom-fields-plugin?utm_source=rss&utm_medium=rss&utm_campaign=delicious-brains-acquires-advanced-custom-fields-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4240:\"Delicious Brains, the company behind WP Migrate DB Pro and SpinupWP, has acquired the Advanced Custom Fields (ACF) plugin from its creator, Elliot Condon. After 10 years, the plugin has more than 1 million active installs and a thriving business based on the Pro version. It has become an indispensable part of the workflow for thousands of WordPress developers around the globe.
\n\n\n\nThe plugin allows developers to easily customize WordPress edit screens and custom field data. In 2019, the Pro version introduced ACF Blocks, a PHP-based framework for developing custom blocks. This came as a great relief to many developers who did not know how they were going to keep pace with learning the JavaScript required to use WordPress’ Block API.
\n\n\n\nGeneral reaction to the news was positive, as ACF fits in neatly with Delicious Brains’ suite of well-maintained developer products. The company’s founders also possess a genuine appreciation of ACF and its importance to the WordPress developer community.
\n\n\n\n“I don’t think WordPress would be where it is today without ACF,” Brad Touesnard said on a recent episode of the Delicious Brain Waves podcast.
\n\n\n\nCondon cited the scale of the project and “technology complexity and user expectation” as factors in his decision to sell ACF. As a one-person team, he was unable to keep up with the growth of ACF over the years.
\n\n\n\n“Stepping away from ACF has not been an easy decision to make,” Condon said. “The reasoning behind it comes from a place of humility. As the number of installs have grown from thousands to millions, the needs of the product have outgrown my ability to develop solutions. The last thing I want to do to this amazing community is unintentionally hold back the project, so something needed to change.”
\n\n\n\nDelicious Brains’ announcement stated that the company will be reviewing Condon’s roadmap for the product in hopes of fulfilling his vision moving forward.
\n\n\n\n“Two of our greatest strengths that we’ll bring to ACF are design (UI/UX) and developer education,” Touesnard said. “We’ll be focusing our initial efforts in those areas. I have a few UI/UX improvements in mind that would make a huge difference to users. We also see a significant opportunity to produce developer-focused content focused on effectively using ACF in your WordPress projects.”
\n\n\n\nTouesnard also confirmed that Delicious Brains will not be making any drastic changes to ACF or ACF Pro, nor do they plan to adjust the pricing of the product anytime soon.
\n\n\n\n“If we ever decide to update pricing in the future, we won’t force existing customers onto the new pricing,” he said.
\n\n\n\nAfter the initial announcement, there was some confusion surrounding lifetime licenses that originated from a hasty response to a customer inquiry. Delicious Brains has since updated the post to clarify the company’s commitment to ACF Pro’s lifetime customers.
\n\n\n\n“We are committed to honoring lifetime licenses forever,” Touesnard said. “Lifetime license holders will get all ACF Pro software updates forever.”
\n\n\n\nMore information on how the acquisition happened, as well as what customers can expect in the future, is available on the most recent episode of the Delicious Brain Waves podcast.
\";s: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 Jun 2021 03:35:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WordPress.org blog: A New Design is Coming to WordPress News\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10418\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://wordpress.org/news/2021/06/a-new-design-is-coming-to-wordpress-news/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1152:\"After many years of a tidy, white-space filled design on WordPress.org/news it’s time to bring new life to the way we present our content. So much has changed since this site was first created: the people who read it, the type and variety of what is published, even the way WordPress works has changed.
\n\n\n\nWhich means it makes sense to change our theme.
\n\n\n\nEarlier this year, Matt requested a new design from Beatriz Fialho (who also created the State of the Word slides for 2020). The design keeps a clean, white-space friendly format while incorporating a more jazzy, playful feeling with a refreshed color palette.
\n\n\n\n\n\n\n\nMore detail on this modern exploration have been posted on make.wordpress.org/design. I encourage you to stop by and read more about the thoughts behind the coming updates; and keep an eye out for the new look here and across WordPress.org!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 03 Jun 2021 20:47: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: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:12;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WPTavern: Forks and Alternatives: Custom User Avatar Plugins for WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=117207\";s:7:\"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/forks-and-alternatives-custom-user-avatar-plugins-for-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=forks-and-alternatives-custom-user-avatar-plugins-for-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7622:\"You know what one of the great things about open source is? Others can use a project’s code, share it wholesale, modify it, and/or distribute their changes. These are the pillars upon which WordPress stands. It is a beautiful thing to watch in practice.
\n\n\n\nMost often, it means we can build off the shoulders of those giants who came before us, continually improving the software for ourselves and others. It is how WordPress got its start nearly two decades ago as a fork of the b2/cafelog blogging system.
\n\n\n\nSometimes, it just means having the freedom to give your friend a copy of something you love and letting them use it. Other times, it is the gateway for a budding developer learning how functions or classes work for the first time, ripping apart a project to see what makes it tick.
\n\n\n\nEvery so often, the promise of free software means that others can decide to go their own way when they do not like the direction a project is heading. They can fork the code, carving a new destination for its future.
\n\n\n\nThis is what happened when ProfilePress overhauled its WP User Avatar plugin, turning it into a full-fledged membership solution. While its average user may not be able or willing to dip their toes into the depths of the development waters, when you have a 400,000+ user base, a few of them are bound to be programmers. Or at least tech-savvy enough to create a copy of the previous version and distribute it directly.
\n\n\n\nIt did not take long — mere days — before ex-users began sharing their forks. The beauty of open source is that they have the power to do this without some corporation cracking down on them. I wanted to acknowledge what they accomplished by jumping into a messy situation and making quick alternatives for many users who felt abandoned. This is my symbolic handclap. 👏
\n\n\n\nIt is not often that we get to mention WordPress’s license without gearing up for battle. However, the GPL played a crucial role in making these forks possible. The license protected the plugin’s user base, giving them multiple alternative paths to take.
\n\n\n\nWithout further preaching the merits of open source, the following are the current forks of WP User Avatar:
\n\n\n\nEach fork looks like a straight port of the latest version of WP User Avatar before version 3.0. There are some necessary code and branding changes. The first two also remove all advertising from the plugin.
\n\n\n\nFor anyone looking to return to the exact same functionality as the old plugin, any one of these will do the job.
\n\n\n\nStraight ports are nice to have, especially for those who need to keep their data intact for many user accounts, but this could also be an opportunity for others to look at alternatives. And, custom user avatar solutions are a dime a dozen. There is a little something for everyone out there.
\n\n\n\nThe following is nowhere near a comprehensive list. I have either tested or used most of these in the past couple of years. I encourage anyone to share plugins I did not include in the comments.
\n\n\n\nTopping any list of custom avatar solutions is Simple Local Avatars by 10up. The WordPress company is one of the most respected in the community, and its employees contribute heavily to core development. 10up tends to put together solid plugins.
\n\n\n\nSimple Local Avatars does just what it says on the box. It allows users to upload custom avatars to their site. It also generates requested image sizes on demand. It works alongside Gravatar, a feature that can be enabled or disabled. It also has built-in options for site administrators to grant permission to non-authorized roles to upload their photos.
\n\n\n\nWP User Avatars by John James Jacoby, a lead developer for bbPress and BuddyPress, is another simple plugin. Like many similar solutions, it adds a form for users to manage their avatar from their profile pages.
\n\n\n\nIt is unique in that it works alongside a suite of other user-related plugins that Jacoby offers. While it can work on its own, it is at least worth checking out his WP User Profiles plugin, which overhauls WordPress profile pages. It and his other user-related plugins work in conjunction with each other. Plugin users can pick and choose which they wish to install.
\n\n\n\nThere seems to be a pattern emerging here — users tend to love these simple avatar solutions. User Profile Picture by Cozmoslabs is another that fits this mold. It also includes a block to allow post or page authors to output any user’s profile (avatar, name, description, and posts link) on the site front end.
\n\n\n\nUsers without permission to upload an image cannot add an avatar with this plugin alone. By default, this is the Administrator, Editor, and Author roles. Site admins will need to install either a permissions plugin or Cozmoslabs’ Profile Builder for the extra capability.
\n\n\n\nPixel Avatars is a privacy-first Gravatar replacement. It takes a different route than similar options by not providing a method to upload a custom avatar. Instead, it automatically generates unique avatars for each user with a bit of JavaScript. It is a fun twist on the typical avatar system.
\n\n\n\nTechnically, this is not a standalone avatar plugin. The Pixel Avatars system is a sub-component of the Toolbelt plugin. Created by Ben Gillbanks, it is a collection of tools that he uses for most of his WordPress projects. It may be overkill for many, but each plugin module can be enabled or disabled based on user needs.
\n\n\n\nThis plugin is also different from other solutions because it does not allow local avatar uploading. However, it is a solid alternative for those who just need faster load times, especially on posts that display dozens or hundreds of Gravatar images in the comments.
\n\n\n\nLocal Gravatars by Ari Stathopoulos is a caching system. It stores Gravatar images on the user’s server for a week before flushing them out. This can make for a performance boost instead of hitting the Gravatar CDN for each image.
\";s: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 Jun 2021 01:33:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"WPTavern: WordCamp Europe 2021 Online Schedule Announced\";s:7:\"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=117521\";s:7:\"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:157:\"https://wptavern.com/wordcamp-europe-2021-online-schedule-announced?utm_source=rss&utm_medium=rss&utm_campaign=wordcamp-europe-2021-online-schedule-announced\";s: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:2933:\"Mark your calendars for the next major WordPress event coming up at the beginning of next week. WordCamp Europe is just five days away and will run from June 7-9. In July 2020, organizers announced that in-person events would not resume until 2022. At that time, attendees were deeply disappointed but resigned to the necessity of online events due to the pandemic.
\n\n\n\nOne of the advantages of scheduling a virtual event so far in advance is that organizers have been able to eliminate a great deal of uncertainty for attendees and their travel arrangements as well as have more time to create a better online experience. This is one of the few times in WordCamp Europe history where all attendees will be joining virtually, on equal footing from wherever they are in the world.
\n\n\n\nWCEU 2021 organizers have announced the speaker lineup and schedule for the upcoming three days of 30-minute sessions, 10-minute lightning talks, workshops, discussion panels, and interviews. Two tracks will run simultaneously.
\n\n\n\nThe schedule includes some big-picture topics like full-site editing and the future of WordPress themes, as well as more technical topics such as how to quickly build custom blocks, setting up a WooCommerce data hub, headless WordPress, and accessing APIs using OAuth on the Federated Web. At the close of day 3, WordPress co-founder Matt Mullenweg will join the event for a virtual chat.
\n\n\n\nBusiness owners, project managers, designers, and other professionals will all find topics related to their work and interests. The schedule has a built-in favoriting tool so attendees can mark the sessions they plan to attend and then print or email to themselves for a personalized schedule. Every hour or so there will be 10-minute breaks so attendees will have time to talk with others and socialize. WCEU organizers are planning to host virtual networking rooms where attendees can meet sponsors and take part in product demos.
\n\n\n\nRegistration is free and attendees will receive online goodiebags. Tickets are still available but organizers expect it to be another “sell out” year.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 03 Jun 2021 01:07:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"WordPress.org blog: The Month in WordPress: May 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10393\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2021/06/the-month-in-wordpress-may-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11057:\"\n\n\n\nIt’s really fun to contribute to something larger than yourself.
Matt Mullenweg’s words in “The Commons of Images” episode of the WP Briefing podcast exemplify the core philosophy of the WordPress project, especially as we inch closer to the next major release (version 5.8). This post covers exciting updates from the month of May.
\n\n\n\nWordPress celebrated the 18th anniversary of its launch on May 27, 2021. To celebrate 40+ releases and WordPress’ support of 40% of the web, the team released 40 milestones to celebrate the anniversary of the software. Here’s to the next 18 and beyond!
\n\n\n\nCreative Commons Search has officially joined the WordPress project. Creative Commons Search (CC Search) is a CC0 image search engine with over 500 million openly licensed images. The search product, which is being renamed to Openverse, will eventually live on the URL: https://wordpress.org/openverse. Contributors working on CC Search will continue their work as part of a new dedicated Make team: https://make.wordpress.org/openverse. Check out “The Commons of Images” podcast episode for more information.
\n\n\n\nWordPress version 5.7.2, a short-cycle security release, came out on May 13. Get the latest version directly from your WordPress dashboard or by downloading it from WordPress.org.
\n\n\n\nWant to contribute to WordPress core? Check out the Core Contributor Handbook. Don’t forget to join the WordPress #core channel in the Make WordPress Slack and follow the Core Team blog. The Core Team hosts weekly chats on Wednesdays at 5 AM and 8 PM UTC.
\n\n\n\nGutenberg version 10.6 and version 10.7 were launched this month. Version 10.6 features experimental Duotone filters (which are shipping with WordPress 5.8), block pattern suggestions in placeholders, and enhancements to the table block. Version 10.7 adds a responsive navigation block, block design tools, and the ability to load block patterns from the directory.
Want to get involved in building Gutenberg? Follow the Core Team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Make WordPress Slack. The latest “What’s next in Gutenberg” post offers more details on the latest updates. If you are unfamiliar with the Gutenberg plugin, learn more in this post.
\n\n\n\nDon’t miss the latest Full Site Editing (FSE) Outreach program testing call on building portfolio pages using the Template Editing feature shipping with WordPress 5.8! The deadline is June 9. The team has published a recap of the Query Quest FSE Testing call, which shares some interesting results. The answers to round two of FSE questions are also out.
\n\n\n\nThe countdown to one of the most anticipated WordPress events, WordCamp Europe 2021 (Online), has started! The full schedule of the event is now available, and the team has exciting plans! Don’t miss this event: get your tickets now before they run out!
\n\n\n\nHave a story that we should include in the next “Month in WordPress” post? Please submit it using this form.
\n\n\n\nThe following folks contributed to May’s Month in WordPress: @meher and @chaion07
\";s: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 Jun 2021 18:23:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:132:\"HeroPress: From Blogging to WordPress Communities: A Bolivian tale – De Blogger a comunidades de WordPress: Una historia boliviana\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=3626\";s:7:\"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:182:\"https://heropress.com/essays/from-blogging-to-wordpress-communities-a-bolivian-tale/#utm_source=rss&utm_medium=rss&utm_campaign=from-blogging-to-wordpress-communities-a-bolivian-tale\";s: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:15766:\"Este ensayo también está disponible en español.
\nI would have never imagined that working with WordPress would be a vital part of my current life and that I would be organizing the first WordCamp of my city Cochabamba, and the first of Bolivia.
\nTo start with my story, let me clarify that I don’t have any background in computer science or similar. I actually studied Industrial Engineering and even did a masters degree in Environmental studies. But life has taken me somewhere else and I’m very happy with my current destination. I won’t go into details of how my career changed so much, that would take hours of reading. But my early stages of WordPress started when I decided to start a small business designing and selling cushions and bed clothes. It was tiny and it only lasted a bit more than a year. It was a solo person business, little investment, and very little planning. While I sat in the small store I’d rented to sell these items, begging that people stopping at the shop’s windows would step in to buy something, I decided I needed to create a website for this business.
\nI had zero budget to hire somebody but I had good confidence in my ability to learn things on my own. I had always been the nerdy type and a close friend with computers in general. Thus, I decided I would figure out how to build a website on my own. I ended up building the most simple website/blog with WordPress.com. I didn’t even have a budget to buy a custom domain and I stayed with the free subdomain from WordPress.com. Unfortunately, soon my entrepreneurship was over. There were no profits and any income went mostly to pay the store’s rent. To add to the decision, a previous company with whom I had worked before, contacted me for a job opening that matched my profile. I needed that income. Therefore, I closed the store and forgot about my entrepreneurship.
\n\nHowever, that brief encounter with a simple website had opened a field out there that I wanted to explore better some day.
Back to the employee mode, I started my new job as a technical writer for a software development company. Since I had done my masters degree in the UK, I had a decent level of English, and somehow my close affinity with computers and technology made it easy for me to translate complex software jargon into simple tutorial steps. As I got more training in technical writing, I started to improve my writing skills in general. That reconnected me with a long lost passion of mine- writing. I’d forgotten that little girl in me that used to love writing stories and journaling. In all these years of my adult life, I hadn’t reconnected to it. That’s when I realized I had to have a blog. I needed a blog. And when WordPress.com came to my encounter again.
\nThis time I wanted to know the platform deeply. Creating my blog helped me become more familiar with WordPress and website building in general. I blogged about writing, my thoughts, book reviews, and everything that could come to my mind. That was in 2015.
\nI don’t remember exactly how I got into the WordPress support forums, probably looking for answers to a specific issue about my blog. That’s when I realized there were other people’s questions that I could actually answer. I began checking the forums a couple of times per week. I did it as a hobby. I liked that I was able to help people and learn more while doing that.
\n\nSome people at my work checked their Facebook to relax on their break time, I checked the WordPress.com forums.
That’s how I found out about the Happiness Engineer position in Automattic. A Happiness Engineer provides customer support to people building their blogs or websites with WordPress.com. When I read the job description, it was like reading a job that was perfect for me. Even more it offered the possibility to work remotely and even travel while still working. My career as a technical writer was stuck after three years and I was also certain that I didn’t want to go back to any job related to Industrial Engineering.
\nMy story about applying to Automattic is long. To summarize it, I didn’t get in it the first time I applied. I had to do the trial twice and re-applied three times in total. I had to learn about HTML and CSS. But after almost one year and a half in between the applications and the two trials, I finally got the job. WordPress became my main means of income.
\nIt was in this job that I learned about the WordPress communities around the world and WordCamps. And when somebody asked, how is the WordPress community where you live? I was speechless. I really didn’t know. Was there a community?
\nSoon after finding there wasn’t any community, I started to dig more information about what was needed to organize one. I talked about the idea with some colleagues and they provided good insights. But I was still debating inside myself, who would start it? Was it me? It couldn’t be. It was true I provided technical support for blogs and websites, but I knew nothing about coding, plugin or theme development.
\n\nIt had to be somebody else, an expert WordPress developer, not me.
But after trying to gauge interest and ask around I realized that the only way to find these community members was to start the community. Therefore, the WordPress community in Cochabamba was born. That was 3 years ago.
\nWe’ve had ups and downs, probably similar to any other community. And although Cochabamba is not a big city, we had issues finding a location that would be accessible to everybody and wouldn’t incur a cost. We had people coming from all different levels of knowledge, from people that had a vast experience with WordPress to people with no experience at all but that wanted to learn. Covid19 actually helped the community grow when meetups went online.
\nThe community also brought in me a side I didn’t know I would ever be interested in: public speaking. I had the opportunity to be a speaker at WordCamp Mexico, WordCamp Guayaquil and WordCamp Colombia online. I started to gain confidence while I enjoyed the opportunity to connect with other communities and meet people that were in similar pathways. Not all of them were developers as one tends to imagine in a WordPress community, many like me started only as bloggers.
\nFinally, after 3 years we decided to organize our first WordCamp. I never imagined myself organizing any WordCamp- me, the shy one, suddenly talking to sponsors, contacting companies to sponsor us, leading a group of people with different talents and backgrounds. I’m thrilled to say that I’ve learned so much from the experience.
\nIn all these years my career has taken a dramatic swift turn.
\n\nThanks to WordPress I have been able to find a good job, work remotely, and help build something in my community that helps people learn skills and find career opportunities.
I couldn’t be more grateful for all the good things that WordPress has given me.
\nNunca me hubiera imaginado que trabajar con WordPress sería una parte vital de mi vida y que estaría organizando el primer WordCamp de mi ciudad, Cochabamba, y el primero de Bolivia.
\nPara comenzar con mi historia, déjenme aclarar que no tengo ningún estudio en ciencias de la computación o similar. Estudié Ingeniería Industrial e incluso hice una maestría en estudios ambientales. Pero mi vida ha tomado otro rumbo y estoy feliz con donde estoy ahora.
\nNo iré en detalles de cómo mi carrera cambió, eso tomaría horas de lectura. Pero mis comienzos tempranos con WordPress empezaron cuando decidí comenzar un pequeño negocio diseñando y vendiendo almohadones y ropa de cama. Era muy pequeño y solo duró un poco más de un año. Era un negocio de una sola persona, con poca inversión y poca planeación. Mientras me sentaba dentro de mi tienda vendiendo mis productos y rogando que la gente que se detenía en frente de las vitrinas entrara a comprar algo, decidí que necesitaba crear un sitio web para mi negocio.
\nTenía cero presupuesto para contratar a alguién pero tenía confianza en mis habilidades para aprender cosas por mi misma. Siempre había sido del tipo nerd y muy amiga de las computadoras en general. Entonces decidí que encontraría la forma de construir el sitio web por mi misma. Terminé construyendo un sitio, casi blog, de lo más simple. No tenía ni siquiera presupuesto para comprar un dominio personalizado y me quedé con el subdominio gratuito de WordPress.com. Desafortunadamente, mi emprendimiento llegó al fin. No habían ganancias y cualquier ingreso era generalmente para pagar el alquiler de la tienda. Para influenciar aún más esta decisión, una compañía con quien había trabajado anteriormente me contactó para un trabajo que le iba muy bien a mi perfil. Necesitaba esos ingresos. Por lo tanto cerré la tienda y me olvidé de mi emprendimiento.
\n\nSin embargo, ese encuentro breve con un sitio web simplísimo abrió un campo delante de mis ojos que quería explorar mejor algún día.
De nuevo ya en modo de empleado, comencé mi trabajo como technical writer para una empresa de software. Como había hecho mi maestría en el Reino Unido, tenía un nivel decente de inglés y mi afinidad con las computadoras y la tecnología en general hacía que fuese sencillo para mi traducir la jerga compleja de los desarrolladores de software en tutoriales con sencillos pasos. A medida que recibía más entrenamiento en technical writing, comencé a mejorar mis habilidades de escritura. Eso me reconectó con una pasión perdida, la escritura. Me había olvidado de esa pequeña niña a la que le encantaba escribir historias. En todos estos años de mi vida adulta, no me había reconectado con eso. Entonces me di cuenta que necesitaba un blog, tenía que tener un blog. Y WordPress.com vino a mi encuentro otra vez.
\nEsta vez quería conocer la plataforma más profundamente. La creación de mi blog me ayudó a estar más familiarizada con WordPress y con la construcción de sitios web en general. Blogueé sobre el proceso de escritura, mis pensamientos, revisiones de libros, cualquier cosa que se venga a mi mente. Eso fué en 2015.
\nNo recuerdo exactamente cómo llegué a los foros de WordPress, tal vez buscando respuestas a algún problema con mi blog. Ahí fue cuando me di cuenta que habían preguntas de otras personas que en realidad podía responder. Empecé a revisar los foros un par de veces por semana. Lo hacía por hobby. Me gustaba que podía ayudar a la gente y aprender más mientras lo hacía.
\n\nAlguna gente en mi trabajo revisaba su Facebook durante el tiempo de descanso, yo revisaba los foros de WordPress.com
Fué así que me enteré del trabajo de Happiness Engineer en Automattic. Un Ingeniero de la Felicidad provee soporte técnico a personas que construyen sus sitios o blogs con WordPress.com. Cuando leí la descripción del trabajo, era como leer algo que era perfecto para mí. Adicionalmente me daba la posibilidad de trabajar remotamente e incluso trabajar mientras viajaba. Mi carrera como technical writer estaba estancada después de tres años y estaba segura que no quería retornar a algún trabajo relacionado con Ingeniería Industrial.
\nMi historia sobre mi postulación a Automattic es muy larga. Para resumirlo, no entré a la primera vez. Tuve que hacer el periodo de prueba 2 veces y postulé como 3 veces en general. Tuve que aprender HTML y CSS. Pero después de casi un año y medio entre estas postulaciones y los periodos de prueba, finalmente obtuve el trabajo. WordPress se convirtió en la fuente principal de ingreso.
\nFue en este trabajo que aprendí sobre las comunidades de WordPress en el mundo y los WordCamps. Y cuando alguien me preguntó cómo es la comunidad de WordPress de donde eres? No tenía respuesta. No sabía. ¿Había alguna comunidad?
\nMuy pronto después de darme cuenta que no había ninguna comunidad, empecé a buscar más información sobre lo que era necesario para organizar una. Hablé de la idea con algunos colegas y me dieron buenas perspectivas. Pero todavía me debatía dentro de mi, ¿quien empezaría esta comunidad? ¿Sería yo? No podía ser. Era cierto que proveía soporte técnico para los blogs y páginas web, pero no sabía nada de código o desarrollo de plugins o temas.
\n\nTenía que ser alguien más, un experto desarrollador en WordPress, no yo.
Después de tratar de ver el interés alrededor mío, me di cuenta que la única manera de encontrar a estos miembros de la comunidad era empezando la comunidad. Y es así como la comunidad de Cochabamba nació. Eso fue hace 3 años.
\nTuvimos subidas y bajadas, probablemente como cualquier comunidad. Aunque Cochabamba no es una ciudad grande, tuvimos problemas encontrando un lugar accesible a todos, que no incurría en grandes costos. Tuvimos gente viniendo de todo tipo de experiencias de WordPress, desde gente con vasta experiencia hasta gente que no tenía experiencia para nada pero que quería aprender. El Covid19 en realidad nos ayudó a que la comunidad crezca cuando las reuniones se volvieron virtuales.
\nLa comunidad de WordPress también despertó en mí una parte en la que nunca pensé que estaría interesada, hablar en público. Tuve la oportunidad de ser ponente en el WordCamp México, WordCamp Guayaquil y el WordCamp Colombia online. Empecé a adquirir confianza y disfrutar de la oportunidad de conectar con otras comunidades y conocer gente que estaba en caminos similares. No todos ellos eran desarrolladores como uno tiende a imaginar en una comunidad de WordPress, muchos como yo comenzaron solo como bloggers.
\nFinalmente, después de 3 años, decidimos organizar el primer WordCamp. Nunca me imaginé organizando ningún WordCamp de ningún tipo, yo, bastante tímida, hablando con patrocinadores, contactando compañías para patrocinarnos, liderando un grupo de gente con diferentes talentos y backgrounds. Estoy muy feliz de decir que he aprendido mucho de esta experiencia.
\nEn todos estos años, mi carrera ha dado un giro dramático.
\n\nGracias a WordPress he podido encontrar un buen trabajo, trabajar remotamente, y ayudar a construir algo en mi comunidad que ayuda a que la gente aprenda nuevas habilidades y encuentre oportunidades laborales.
No podría estar más agradecida por todas las cosas buenas que WordPress me ha dado.
\nThe post From Blogging to WordPress Communities: A Bolivian tale – De Blogger a comunidades de WordPress: Una historia boliviana appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 02 Jun 2021 12:00:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Carla Doria Medina\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: Chrome Canary Adds Flag for Disabling FLoC Testing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=117580\";s:7:\"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:165:\"https://wptavern.com/chrome-canary-adds-flag-for-disabling-floc-testing?utm_source=rss&utm_medium=rss&utm_campaign=chrome-canary-adds-flag-for-disabling-floc-testing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6223:\"Google’s controversial Federated Learning of Cohorts (FLoC) experiment now has a feature flag within Chrome Canary (the nightly build of Chrome for developers) that allows users to opt out.
\n\n\n\nIn January 2020, Google announced its plans to discontinue support for third-party cookies in Chrome within two years. The first bits and pieces of the company’s Privacy Sandbox initiative started landing in Chrome in December 2020 with an initial flag to disable it. FLoC, Google’s proposed replacement for third-party cookies, began testing as a developer origin trial in Chrome at the end of March 2021.
\n\n\n\nIn Canary, users can navigate to chrome://flags/#privacy-sandbox-settings-2 to find the Privacy Sandbox Settings 2 flag.
\n\n\n\n\n\n\n\nRelaunch Canary to save the changes. This will unlock the box that allows users to either reset their FLoC group or opt out of FLoC entirely. The new setting is available under chrome://settings/privacySandbox:
\n\n\n\n\n\n\n\nIf the setting remains enabled, which is the default, Chrome will group users into cohorts based on recent browsing activity and then advertisers select ads for the entire group. Browsing activity for the individual is “kept private on your device,” but Chrome certainly has access that information by way of mediating the cohorts. Google notes that the trial is currently only active in some regions.
\n\n\n\nUsers can also opt out of Privacy Sandbox trials on the same page. Current trials include the following:
\n\n\n\nGoogle has not specified how users would opt out of FLoC if the experiment is successful and moves forward. Organizations and site owners who are currently on the fence about it may go either way depending on how easy it is for Chrome users to opt out themselves.
\n\n\n\n“Instead of comparing FLoC to its predecessor, third party cookies, I feel it’s actually more like the Facebook Pixel – mostly in the sense that it’s controlled by a single surveillance capital company,” WordPress core contributor Roy Tanck commented on the trac ticket for the discussion. “FLoC may not be quite as nefarious, but I feel it should be something website owners consciously opt into.
\n\n\n\n“WordPress has always advocated for a free and open web, and FLoC appears to actively harm that goal. I think WordPress should take a stand against this, and do it now.”
\n\n\n\nA few others have chimed in on the ticket recently as other open source projects have started blocking FLoC by default. Plugin developer David McCan’s comment referenced analytics data published in early May suggesting that US users choose to opt out of tracking 96 percent of the time following the changes in iOS 14.5.
\n\n\n\n“There is no doubt that coming down on the side of user privacy vs user tracking is the right thing to do,” McCan said. “Which headline would we rather see? ‘By default millions of WordPress websites are allowing users to be tracked’ or ‘WordPress takes steps to block user tracking making millions of websites around the world safe to visit?’
\n\n\n\n“We already have a policy that opt-in by default tracking’ is not allowed in plugins hosted by WordPress. This is because we recognize the responsibility and benefit of protecting user privacy.”
\n\n\n\nDuring a live marketing event Google hosted at the end of last week, Jerry Dischler, vice president and general manager of Ads, addressed the recent privacy concerns surrounding FLoC.
\n\n\n\n“We’ll be using these [Privacy Sandbox] APIs for our own ads and measurement products just like everyone else, and we will not build any backdoors for ourselves,” Dischler said.
\n\n\n\nDischler also reaffirmed Google’s commitment to moving away from third-party cookies.
\n\n\n\n“Third-party cookies and other proposed identifiers that some in the industry are advocating for do not meet the rising expectations consumers have when it comes to privacy,” he said. “They will not stand up to rapidly evolving regulatory restrictions; they simply cannot be relied on in the long term.”
\n\n\n\nGoogle bears the burden of reassuring advertisers that effective advertising is still possible as the company moves beyond tracking cookies. It is aiming to future-proof advertisers’ measurement of campaign performance with what it claims are “privacy-safe solutions.” The company is pushing hard for advertisers to adopt these new techniques, promising more actionable first-party conversion data.
\n\n\n\nAlthough consumer expectations have changed, FLoC may not be the answer to the need for a privacy-preserving advertising model. So far it looks like Google will have an uphill battle to gain more broad support from browsers, advertisers, and consumers.
\";s: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 Jun 2021 03:12: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:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"WPTavern: Ujwal Thapa, Co-Founder of the WordPress Nepal Community, Passes Away\";s:7:\"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=117594\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:199:\"https://wptavern.com/ujwal-thapa-co-founder-of-the-wordpress-nepal-community-passes-away?utm_source=rss&utm_medium=rss&utm_campaign=ujwal-thapa-co-founder-of-the-wordpress-nepal-community-passes-away\";s: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:4028:\"“Here is my resume of professional Failures,” began his LinkedIn profile. On a site where most are apt to share success, Ujwal Thapa started with nearly a two-decade history of dreams that did not quite work out. Or, maybe they did in some ways.
\n\n\n\nMuch of Nepal is reeling from his death today. In the past week, he had been battling multiple health complications from Covid-19. The 44-year-old activist was the founder of the Bibeksheel Nepali political party, originally a peaceful movement that fought against political corruption and social injustice.
\n\n\n\nHowever, many Nepali WordPress users will remember him as a co-founder of their community. The WordPress Nepal Facebook group has now grown to nearly 8,000 members.
\n\n\n\nIn a 2015 interview with Nepal Buzz, he noted his proudest WordPress-related achievement as building this community. “That is not just creating tens and hundreds, but thousands of jobs in Nepal, and has the potential to create tens of thousands more, which basically means we are contributing to the nation by creating opportunities where there are none.”
\n\n\n\nLater in the interview, he said he was a provoker, and he continued to live the remainder of his life in that belief.
\n\n\n\n“I believe that the easiest way to bring change is to align all the positive people in the same direction,” he said. “So my job is to provoke and bring together people with similar interests, and align them in a similar direction, creating the change that they would never believe could come.”
\n\n\n\nThapa founded Digital Max Solutions in 2002, amidst the Nepalese Civil War. At one point, the company had as many as 35 employees. Over 30 eventually moved on to start their own IT businesses. He also created the Entrepreneurs for Nepal Facebook group, which now has over 100,000 members. From May 2013 to October 2019, he served as the Chairperson of the BibekSheel Nepali party.
\n\n\n\nMany in Nepal’s WordPress community owe him a debt of gratitude for having the vision of building off the core platform. WordPress.org Themes Team representative Ganga Kafle credits at least part of his career and deep involvement with WordPress to Thapa, helping him land an initial internship with Web Experts Nepal.
\n\n\n\n“Ujwal Thapa is the person who introduced WordPress to me in 2012 in a meetup,” he said. “After that, I was in close relation with him. In 2014, after my graduation, I went to Ujwal and asked him about the internship, and he took me to that office and talked with the boss and finalized for the internship. That’s how I jumped in WordPress, and now I am one of the leads of Themes Team.”
\n\n\n\n“Once he said to me, ‘WordPress is giving so much things for free, why you hesitate to put Proudly Powered by WordPress?\'” Kafle shared of the mentor, referencing the typical credit line in many WordPress site footers. “He was in love with WordPress.”
\n\n\n\nYou can view Thapa’s WordCamp presentations as a speaker and panel moderator via WordPress.tv.
\";s: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 Jun 2021 19:08:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:18;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"WPTavern: Breaking Down WPMarmite’s 127-Shop Full Site Editing Study\";s:7:\"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=117541\";s:7:\"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/breaking-down-wpmarmites-127-shop-full-site-editing-study?utm_source=rss&utm_medium=rss&utm_campaign=breaking-down-wpmarmites-127-shop-full-site-editing-study\";s: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:6698:\"Earlier today, the WPMarmite team released a massive study of 127 WordPress theme shops. It primarily focused on integration with the block editor. The team also surveyed 22 of the shops directly to dive deeper into what the future might look like when the Full Site Editing (FSE) project is entirely bundled into the core platform, which could be around the WordPress 5.9 release in late 2021.
\n\n\n\nFSE is not a single thing that WordPress will drop on users all at once. It is an ongoing project with several independent but related components that will ship based on their readiness. The goal is to move the block system beyond just content, bringing blocks into all facets of a site’s front end.
\n\n\n\nSingle post/page template editing and block-based widgets are expected to arrive with WordPress 5.8 in July. These are two user-facing components that serve as stepping stones toward a complete FSE experience.
\n\n\n\nPutting study into context, FSE-related discussion for theme authors is mainly about block templates and global styles. These components will create a drastic change to theme development where templates are made up of blocks themselves and styles are configured via a JSON file. For the first time in WordPress’s history, users will be able to directly edit both from an interface in their site admin without knowing any code.
\n\n\n\nUpcoming site editor with templates (left panel) and global styles (right panel).\n\n\n\nWordPress 5.0, the first version to include blocks, launched two and a half years ago. Theme authors have had time to catch up, migrate old projects, and create new ones. WPMarmite’s study gives a solid, at-a-glance view of how shops are fairing now that the shockwave of the block system’s introduction has long settled.
\n\n\n\nThe primary takeaway from the 127-shop study was that 57% of them featured their compatibility with the block editor in some way. Short of testing themes from each site individually or directly asking them all, there is no other way to know how many actually offer support. My guess is the number is not much higher.
\n\n\n\nTechnically, all themes “work” with the WordPress editor. However, not all are designed from the ground up to offer an ideal experience with it. As a commercial theme shop, you would want to mention this support somewhere in your marketing.
\n\n\n\nEven if that 57% is dead-on, a shop featuring block support does not always mean solid support. In my experience of viewing themes and their demos almost daily, “support” often means minimal adjustments to make sure the basics do not break the site. That number is far lower if you are counting themes that offer an immersive block-editor experience.
\n\n\n\nThe number that was surprising but not surprising was the percentage of shops currently providing block patterns. Only 3% (4 in total) bundle custom patterns.
\n\n\n\nInserting a block pattern into the WordPress editor.\n\n\n\nWhile the patterns API has only been around since WordPress 5.5, released less than a year ago, it is one of those crucial tools for the future of theme development. I thought the number was low. I just did not know it was 3% low.
\n\n\n\nIf 57% of shops offer some level of block editor support, why are they stopping short of complete integration and not using the most powerful features at their disposal?
\n\n\n\nPatterns are part of that immersive experience I mentioned. If a shop does not have any, I would question how much it actually supports the block system.
\n\n\n\nIn the WordPress.org free theme directory, that percentage is much higher. Currently, 514 themes add block editor styles, and 120 bundle at least one pattern.
\n\n\n\nNote: if you combine those two filters, the directory lists 107 themes. Some could be missing a tag.
\n\n\n\nOne data point the team missed was how many of these theme shops integrated with third-party page builders. I would wager that most of the ThemeForest authors support at least one additional builder, maybe two. It is almost a sure-fire bet that Elementor and Beaver Builder top that list. While the study was on the core block system, this would have given us a more accurate look at the current theme market.
\n\n\n\nOf the 127 shops, WPMarmite surveyed 22 of them with questions around FSE. The most telling statistic is that 82% of shops follow FSE-related news, citing WP Tavern as one of their sources. Thank you, dear readers.
\n\n\n\nOn a more serious note, 86% of those surveyed believe that FSE will be a breakthrough for users. I am not surprised at this. Many features that theme authors have attempted to accomplish over the last decade are being rolled into the Gutenberg plugin. It is a slow process, but having the pieces built into WordPress provides standard APIs that will make themers’ jobs easier. In turn, this will allow them to launch features that users ask for with less code and a faster turnaround.
\n\n\n\nThe number I want to see higher is those actively preparing for block templates and global styles. According to the survey, only 22% are doing so.
\n\n\n\nThese components are continually in flux. However, the foundational elements are far more stable than they were just a few months ago. This makes it a good moment for others to start diving in — there is less chance of breaking changes with the system. I expect the percentage of commercial theme shops working with FSE to jump throughout the year. However, it could be a slow process getting to the point where such themes are commonplace. We may need to see a breakout block theme that quickly rises in popularity first. Everyone else will fall in line.
\n\n\n\nIn the meantime, if anyone wants to experiment with FSE, there are six themes listed in the 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 01 Jun 2021 00:36:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:117:\"Gutenberg Times: Why WordPress Agencies Are Embracing Gutenberg – Help Test WordPress 5.8 – Weekend Edition #171\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=17922\";s:7:\"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:118:\"https://gutenbergtimes.com/why-wordpress-agencies-are-embracing-gutenberg-help-test-wordpress-5-8-weekend-edition-171/\";s: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:12753:\"Howdy,
\n\n\n\nMemorial Day is a federal holiday, honoring the men and women who died while serving in the U.S. military. Although a sad occasion for many people in the US, it is also the first long weekend after a cold winter. Many of you will hopefully take the opportunity to spend it leisurely outside with family and friends, away from the screens. Look up from your phone. The content keeps until Tuesday when you get back to work.
\n\n\n\nAfter catching up on my publishing schedule, I will spend the weekend with friends at the Cricket Club, and at the Dali Museum in St. Petersburg. Let me know about your weekend!
\n\n\n\n\n\nWith the release of Gutenberg 10.7 version, we are in the “feature freeze” which means from now to the first beta release on June 8th, 2021, it’s all about bug fixing. Below you’ll find several ways how you can help make it a great release.
\n\n\n\n\n\n\n\nThere is something to be said that 5.8 is probably the biggest release for Gutenberg since 5.0 and in terms of merged code might even be bigger.
Riad Benguella, editor release lead for WordPress 5.8, in #core-editor meeting 5/26/2021
Yours 💕,
Birgit
PS: Thank you to all who shared great resources on wp.data last week! If you used the wp.data package in your blocks, I am looking for real life examples. Ping me in Slack @bph or email me.
\n\n\n\nPPS: Huge “Thank You” to Dave Smith for his wonderful review of our podcast. Grzegorz (Greg) Ziolkowski is on vacation, and we’ll record the next Gutenberg Changelog on Friday Jun 11, covering both releases 10.7 and 10.8. Send us your questions to changelog@gutenbergtimes.com.
\n\n\n\nA new call for testing is now available from the FSE outreach program! Deadline: Jun 9th, 2021. Anne McCarthy sends you down the rabbit hole to create a Polished Portfolio Pages, using the Template Editor and your personal Query Blocks design. She guides you with nice ideas for your Portfolio page, the accompanying template and shares designs from the web. On WPTavern, Justin Tadlock followed along. He shared his page’s source code and the joy and frustrations along the way.
\n\n\n\nHuge W. Roberts introduces you to the Five Photo Editing Tools Available To Use On The Block Editor and explains in detail how to crop, resize and zoom and other features of the Image block.
\n\n\n\nSpeaking of which, WordPress 5.8 will bring a new feature to the image and cover block: Coloring Your Images With Duotone Filters, created by Alex Lende. Details about this wonderful new feature are now available on the WordPress News site. Using the Gutenberg plugin, you don’t have to wait until July 20, 2021 for WordPress 5.8 to come out. You can use today!
\n\n\n\nBlockbase “This block theme attempts to make all the common theme styles configurable in theme.json, and provides the CSS needed to make them work until the blocks themselves support these settings.” wrote Ben Dwyer The Blockbase themes is available via GitHub. Justin Tadlock at WPTavern kick the tires of it. He concluded: “It is the modern-day Underscores (_s) for blocks, and the WordPress theme design community will need such a project moving forward. They will need a starting point and educational tool, and Blockbase is just that.” You’d be interested in more details.
\n\n\n\nHector Pietro published What’s new in Gutenberg 10.7? The release notes for this week’s Gutenberg plugin release. This is the last version of Gutenberg features that will be coming to WordPress core. What didn’t make it? Navigation screen and block, Post Author Block and the Refactor of the Gallery Block. The latter is a bit disappointing as I was very much looking forward to building galleries with image blocks. Ah, well.
\n\n\n\nThe new Widget screen made it and could use some major testing round: Use the WordPress Beta Tester plugin, enable the nightly stream on the bleeding edge channel and start testing specially for backwards compatibility with existing themes and plugins and configuration. Pantheon gives Developer 2 free testing sites, and has a powerful migration tool for cloning existing sites for testing. It’s what we will use for our long-time client sites. If you feel you don’t have enough times, but also don’t want to see any surprises, you can install the Classic Widgets plugin by core contributors Tonya Mork and Andrew Ozz.
\n\n\n\nAllison Rivers wrote Why WordPress Agencies Are Embracing Gutenberg for the Torque Magazine. Rivers interviewed 15 Agency leaders in the WordPress space who shared why they are slowly moving away from 3rd party page builders favoring the block editor and the rich ecosystem around it, with Generate Blocks, Kadence Blocks, Toolset, Stackable, Genesis Blocks and more.
\n\n\n\nThe above article was a nice palate cleanser after the rather lively debate on This Week in WordPress #164 with Nathan Wrigley and Spencer Forman. The reasoning from the agency leaders might also explain why hard-core Elementor fans get so agitated. Big “Thank You” to Nathan Wrigley for having me on the show. 🤟 It was quite entertaining, to say the least.
\n\n\n\nIn case you missed it, I thoroughly enjoyed Nathan Wrigley’s interview with Benjamin Intal, of Stackable on the WP Tavern Jukebox podcast, and Why he is betting his business on blocks.
\n\n\n\nEric Karkovack did a deep dive into the plugin Block Visibility by Nick Diego and shared his insights in his article An Easy Way to Edit Block Visibility in the WordPress Gutenberg Editor .I mentioned the plugin multiple times before. If you didn’t get a chance to test it on one of your projects, Karkovack’s article gives you definitely more insight in how it works, and what use cases are suitable for it.
I also discovered the plugin Conditional Blocks by Morgan Hvidt with a slightly different approach. Both plugins also provide pro versions via their respective websites.
June 7 – 9th, 2021
WordCamp Europe
A virtual event and contributor day. Call for sponsors is open.
🎉 Gutenberg Times is a media partner of WordCamp Europe 2021
\n\n\n\nJune 10th, 2021
WordPress “Mega Meetup”: Plugins That Keep Websites Running
June 20 – 26, 2021
WordCamp Japan
The schedule has been posted. Most sessions will be in Japanese, with exceptions, I think…
June 24, 2021
WPEngine Summit 2021
The digital breakthrough conference
June 24 – 26, 2021
WordCamp Cochabama (Colombia)
July 17 + 18th, 2021
WordCamp Santa Clarita
Calls for speakers was extended to June 5th, 2021.
July 23, 2021
WordFest Live – The festival of WordPress
September 21 + 22, 2021
WPCampus 2021 Online
“A free online conference for web accessibility and WordPress in higher education.” Call for Proposal is up and proposal are due May 26, 2021
On the Calendar for WordPress Online Events you can browse a list of the upcoming WordPress Meetups, around the world, including WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.
\n\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nFeatured Image: Photo by Ravi Palwe on Unsplash
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 29 May 2021 18:23:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"WPTavern: The Automattic Theme Team Announces Blockbase, Its New Block Parent Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=117361\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:209:\"https://wptavern.com/the-automattic-theme-team-announces-blockbase-its-new-block-parent-theme?utm_source=rss&utm_medium=rss&utm_campaign=the-automattic-theme-team-announces-blockbase-its-new-block-parent-theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6504:\"Blockbase WordPress theme as seen from the site editor.\n\n\n\nAny WordPress company that builds and maintains themes worth its salt is already doing at least some preliminary work as WordPress inches ever closer to bundling its upcoming block theme system. Automattic’s Theme Team is no exception. Ben Dwyer announced the team’s new Blockbase parent theme on the Theme Shaper blog yesterday. It includes support for global styles and block templating.
\n\n\n\nThe theme is based on the classic, block-editor-ready Blank Canvas project that Automattic launched in January. Until a few days ago, it was even named Blank Canvas Blocks. I have been checking in on the team’s work in the past couple of months, waiting to see how Blockbase and Mayland Blocks, a child theme based on the team’s original Mayland, were coming along.
\n\n\n\nThe team has built a well-rounded system that should keep them from overhauling each block theme they create for WordPress.com every time there is a change. For theme authors who have yet to dip their toes into the block-theme pond, it might also be the starting point they need.
\n\n\n\nThe Holy Grail of some block theme designers will be creating a project with little more than a theme.json
file. The goal: let WordPress generate all the CSS via setting and style configurations. It will never be possible for all theme authors to achieve their design goals through this — most will need at least some custom CSS. And, whether such a goal is A Good Thing remains to be seen.
Nevertheless, the future of theme design will lean on JSON-configured and generated styles. Blockbase leverages this system to create a standardized set of guideposts for its eventual child themes. This ensures that creators are not continually updating their themes as block styling rapidly evolves.
\n\n\n\nBlockbase serves as a bridge between what is currently possible to configure via a theme.json
file and what will be possible in the future.
It is the modern-day Underscores (_s) for blocks, and the WordPress theme design community will need such a project moving forward. They will need a starting point and educational tool, and Blockbase is just that.
\n\n\n\nThe latest version of the Gutenberg plugin only covers a fraction of what it and, eventually, WordPress will handle in the coming months and years. However, it does allow theme authors to add custom settings via the settings.custom
key, creating their own CSS variables that are automatically output in the site’s head. The Theme Team used this feature to their advantage. Where Gutenberg does not currently support a setting, Blockbase has a custom theme.json
parameter. The theme then uses the generated CSS variables in its stylesheet. As Gutenberg and WordPress eventually support more of these settings out of the box, the team can simply remove unneeded code.
The theme is not altogether unopinionated. “Blockbase is intended to be a representation of all the theme style settings that we believe should eventually live in Global Styles and be configurable by users,” wrote Dwyer. Block theme development could still change in unexpected ways as the system continues to be refined, and the theme will need to change along with it. Bumps in the road should be expected.
\n\n\n\nIt is a project that soon-to-be and current block themers can learn from. While it is currently available via GitHub, Dwyer said the team can investigate making it a npm package if there is enough interest.
\n\n\n\nOne of the most unique things the theme does is work with the theme.json
settings via PHP. In Blockbase’s functions.php
file, it plucks out font-family names registered in the JSON file. It then automatically loads their associated stylesheets from the Google Fonts API. While it is not documented in the code (it should be), I am taking an educated guess that the goal is to allow child theme authors to declare fonts in their own theme.json
files and for Blockbase to handle the loading.
The code is relatively simple. It is the technique that matters.
\n\n\n\nAs developers grapple with the changing nature of WordPress theme architecture, they will need to find new solutions for some of the old problems they previously solved in a PHP-only world. With most theme configuration moving to JSON and templates to HTML, it can be easy to feel like they are losing that dynamic nature of PHP. It was something reliable, and developers have spent years honing custom systems around the old WordPress.
\n\n\n\nThe new WordPress delivers a more robust set of design tools out of the box, but it can seem a bit foreign. That is why seeing real-world code examples of how others are handling these features is a vital step in transitioning more theme authors to block-based development.
\n\n\n\nThis may be a small code sampling, but I am impressed by the clever thinking. In my journey to learn more about how block themes work, I often find myself hitting a brick wall, fighting against the system. This code works with it instead of against it.
\n\n\n\nI do not often write several paragraphs about one function that spans a mere 21 lines of code, but I am still a developer at heart and love seeing elegantly simple solutions. It is not about the font-loading technique; it is about solving problems. This code will undoubtedly be copied many thousands of times over in the coming years and modified for many more thousands of uses. If you are a theme developer and do not see it yet, you will.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 29 May 2021 00:00: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:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:11:\"\n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"HeroPress: Yoast Pivots Diversity Fund\";s:7:\"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:29:\"https://heropress.com/?p=3632\";s:7:\"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://heropress.com/yoast-pivots-diversity-fund/#utm_source=rss&utm_medium=rss&utm_campaign=yoast-pivots-diversity-fund\";s: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:2606:\"\nFor the last three and a half years, Yoast has offered a “diversity fund”, which funded WordCamp attendance for underrepresented people in tech. The goal was to increase the diversity at WordCamps. It worked very well. According to a recent blog post:
\n\n\n\n\n\n\nDuring 2018, 2019, and 2020:
\n\n
\n- We were able to sponsor 70 people,
\n- To join a total of 56 events,
\n- That were all around Asia, Africa, North America, South America, Europe, and Australia.
\n
The problem is that in 2020 all that came to a screeching halt when WordCamps stopped happening. But rather than throw up their hands and say “Oh well!”, the good folks at Yoast came up with a new plan.
\n\n\n\nThe new plan is to sponsor the same group of people, but to fund their WordPress projects, rather than travel to an event. To quote the same blog post from above:
\n\n\n\n\n\n\n\nSo what kind of projects are we looking for? It can be a short-term project, like fixing a simple bug, or a longer-term project like creating a new WordPress theme. That being said, we are looking for projects that aim to be no longer than one WordPress release cycle of three months.
I particularly love this new direction because it feels like a more substantial contribution. Don’t get me wrong, I think WordCamps are great and important, but supporting someone financially for three months while they build something that the entire world gets to use just feels like a bigger thing.
\n\n\n\nDiversity is very important to us here at HeroPress. We’ve striven for diversity across multiple metrics, from gender to age, culture, geography, and language. I think that’s why this project speaks to me more than others.
\n\n\n\nSo many thanks to Yoast for making this happen.
\n\n\n\nIf you’d like more information about the program, check out this blog post, and if you’d like to apply for the fund click here.
\nThe post Yoast Pivots Diversity Fund appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 28 May 2021 13:03:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:46:\"BuddyPress: BuddyPress 8.0.0 Release Candidate\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=319009\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://buddypress.org/2021/05/buddypress-8-0-0-release-candidate/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3107:\"The first release candidate for BuddyPress 8.0.0 is now available!
\n\n\n\n \n\n\n\n\n\n\n\n“Release Candidate” means that we think the new version is ready for release, but with more than 200,000 active installs, hundreds of BuddyPress plugins and Thousands of WordPress themes, it’s possible something was missed. BuddyPress 8.0.0 is slated for release on June 7, 2021, but your help is needed to get there — if you haven’t tried 8.0.0 yet, doing it now is a great idea!
\n\n\n\nYou can test the 8.0.0-RC pre-release in 4 ways :
\n\n\n\nsvn co https://buddypress.svn.wordpress.org/trunk/
git clone git://buddypress.git.wordpress.org/
A detailed changelog will be part of our official release note, but you can get a quick overview by reading the post about the 8.0.0 Beta1 release.
\n\n\n\n\n\n\n\nPlease test your plugins and themes against BuddyPress 8.0.0. If you find compatibility problems, please be sure to post to this specific support topic so we can figure those out before the final release. We strongly advise you to have a look at the 8.0.0 developer notes to figure out what to focus on during your testing.
\n\n\n\n\n\n\n\nDo you speak a language other than English? Help us translate BuddyPress into as many languages as possible! This release also marks the string freeze point of the 8.0.0 release schedule.
\n\n\n\nIf you think you’ve found a bug, you can share it with us replying to this support topic or if you’re comfortable writing a reproducible bug report, file one on BuddyPress Trac.
\";s: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, 28 May 2021 04:30: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:23;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"WPTavern: Happy 18th Birthday, WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=117346\";s:7:\"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:123:\"https://wptavern.com/happy-18th-birthday-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=happy-18th-birthday-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4396:\"WordPress is celebrating 18 years today since the first release of the software to the general public. That release post, titled, “WordPress Now Available,” kicked off an exciting era in the history of the blogosphere where WordPress emerged as an unofficial successor to the abandoned b2/cafelog software. Reading the comments on the first release, you can feel the energy of that time when loyal b2 users were thrilled to have a smooth migration to a new blogging engine that would be maintained.
\n\n\n\nOne line in that post may have had even more impact on WordPress’ trajectory than the features contained in the first release:
\n\n\n\n“WordPress is available completely free of charge under the GPL license.“
\n\n\n\nThe license it inherited from b2 empowered the WordPress community to make it the powerful CMS that it is today. WordPress now underpins a multi-billion dollar economy of creators, publishers, and merchants who can build just about anything with the world of GPL-licensed extensions available. WordPress’ vibrant ecosystem has grown to include more than 58,000 free plugins to extend core, and thousands of commercial plugins and services, including hosting companies that cater specifically to its users.
\n\n\n\nWordPress was instrumental in making publishing software accessible to those with no coding experience, and it is now doing the same for e-commerce, facilitating billions of dollars in sales for businesses and independent stores. The pandemic created unprecedented opportunities for WordPress-powered stores to succeed as traditional brick-and-mortar businesses were forced to close their doors.
\n\n\n\nDespite weathering some profound, once-in-a-lifetime challenges over the past year, WordPress has continued to grow at a phenomenal rate. In February, the CMS passed 40% market share of all websites, up from 35.4% in January 2020, as measured by W3Techs. WordPress’ project lead and co-founder Matt Mullenweg noted this milestone in a post on his blog, marking the 18th anniversary:
\n\n\n\n\n\n\n\nWho could have imagined that our nights and weekends hacking on blogging software, a fork of b2/cafelog, could turn into something powering over 40% of the web? Or that nearly twenty years in, it would be getting better faster than it ever has been?
WordPress.org is celebrating with a new history timeline that logs 40 major milestones along the path to 40% market share. Scrolling through it reads like a story, highlighting some of the most salient moments in WordPress’ history, like the launch of the plugin repository, major interface improvements, and the first WordCamp. There are some interesting notes about how WordPress was able to outpace its contemporaries in the early days, doubling its downloads after Moveable Type 3.0 introduced licensing restrictions. The software had several turns of fortune along the way that have bolstered its market dominance.
\n\n\n\nFor many who have contributed to WordPress’ success, it’s the smaller points that don’t make this official timeline which have been the glue for this community. Friendships are forged in working together and celebrating small wins but also in weathering the friction, conflict, and human failures that come part and parcel with working on an open source project.
\n\n\n\n18 years of growth is a milestone worth recognizing on the web. Congratulations to the code contributors, translators, community organizers, WordPress leadership, and everyone else who has helped make this beloved publishing platform that continues to surprise the world.
\";s: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, 28 May 2021 03:29: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: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:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"WPTavern: Gutenberg 10.7 Integrates With the Pattern Directory, Introduces New Block Design Controls\";s:7:\"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=117350\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:243:\"https://wptavern.com/gutenberg-10-7-integrates-with-the-pattern-directory-introduces-new-block-design-controls?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-10-7-integrates-with-the-pattern-directory-introduces-new-block-design-controls\";s: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:7306:\"Gutenberg 10.7 landed yesterday. Within a few hours, the development team also released version 10.7.1 of the plugin with a few bug fixes. The latest update primarily focuses on work expected to land in WordPress 5.8 this July.
\n\n\n\nThe feature freeze deadline for the current WordPress development cycle passed on Tuesday. This should mean that no new features beyond Gutenberg 10.7 will make it into the core platform. WordPress 5.8 Beta 1 is slated for June 8.
\n\n\n\nThis release feels like the team has polished the interface and experience for the better. Users can also look forward to several enhancements, such as additional block design options.
\n\n\n\nGutenberg now serves its default block patterns via the pattern directory on WordPress.org. This moves their development outside of the plugin and core WordPress, which means designers can iterate on them without a user needing to update. They will always have the latest version available from the editor.
\n\n\n\nInserting a pattern into the content canvas.\n\n\n\nThe pattern directory will be a handy tool for end-users. For many, it will likely serve as a path toward building more complex layouts in the WordPress editor. At the moment, it only houses 10 patterns. This will change after it is opened to community submissions.
\n\n\n\nShaun Andrews shared some of the ongoing design work for the directory, and it is beautiful. I am eager to see the final result when it launches.
\n\n\n\nRecent work on the block pattern directory.\n\n\n\nA side note about block patterns: there is currently a bug that may cause some of those bundled with themes to not appear in the inserter.
\n\n\n\nVersion 10.7 introduces several new design controls for blocks. The most exciting feature for many will be margin controls for more precise control over spacing. Theme authors must set the settings.spacing.customMargin
key to true
in their theme.json
files to enable this.
Currently, only the Site Title and Site Tagline blocks support margin controls. However, now that the initial feature has landed, we should expect others to follow suit in future versions.
\n\n\n\nSpacing and typography controls for title and tagline\n\n\n\nThe Site Title block also has letter case typography controls.
\n\n\n\nThe development team upgraded the Column block with a couple of new options. Users can now customize the padding and colors for individual columns.
\n\n\n\nCustomizing individual columns.\n\n\n\nOne of the more low-key enhancements happens to be one of my favorite changes. The Media & Text block received a new “media width” block option in the sidebar. This makes getting the correct width a far better experience than using the drag handle in the content canvas.
\n\n\n\nAdjusting the media width in the Media & Text block\n\n\n\nI may begin using this block more now. I had been shying away from it for any use case beyond the default width settings.
\n\n\n\nAnother welcome enhancement is Cover being added as a transform option for the Group block. It will only appear if the block has a background.
\n\n\n\nTemplate-editing mode will be one of the most highlighted features for WordPress 5.8. It allows users to switch from content to template editing while never leaving the post screen. Therefore, users will need a welcome guide to explain the new feature.
\n\n\n\nCurrently, the message reads:
\n\n\n\n\n\n\n\nWelcome to the template editor
Templates express the layout of the site. Customize all aspects of your posts and pages using the tools of blocks and patterns.
It is a solid starting point, but it does not fully explain what this mode is about. I expect the development team to smooth it out a bit, maybe add an extra slide or two, or even link to a dedicated documentation page on WordPress.org. Helping users set off on the right foot with this new feature should mitigate confusion and lower the support burden.
\n\n\n\nThere is currently an open call for volunteers to provide feedback on the template editor while building a portfolio-type landing page (see my results). Make sure to get involved if you can spare half an hour or more.
\n\n\n\ncolumn-gap
This is more of a theme developer note, but some users may have noticed lines of buttons not extending to the edge of their container. In certain situations, at least.
\n\n\n\nEssentially, the space between individual Button blocks used a bit of a hacky, old-school CSS margin solution to create the gutter space between each. In the modern world of flex and grid layouts, it is something most designers dread seeing. It overcomplicates things and makes for more bloated CSS, particularly if you want to make adjustments based on screen size.
\n\n\n\nI am highlighting this change because it is one of those stages where the block system is becoming more polished under the hood. And, it could be the start of more exciting things to come for theme authors.
\n\n\n\n“This is great, this is beautiful, themers are going to love it,” wrote Joen Asmussen in the ticket. “At some point once the dust settles, we should see if this gap could become a global styles property; since it’s so easy to change and resilient, it would be nice to handle in such a neat way.”
\n\n\n\nIt is a welcome sight to see the use of column-gap
land in the plugin. Of course, it could use row-gap
for vertical spacing instead of margins in those cases where Buttons extend beyond a single row.
Now, can we do the same for the Columns, Gallery, and Query Loop blocks? Normalizing the system for gutters/gaps between flex items can save dozens upon dozens of lines of code in the long term.
\";s: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, 28 May 2021 00:41: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:25;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Matt: WordPress 18\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=54256\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://ma.tt/2021/05/wordpress-18/\";s: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:1446:\"\n\n\n\nToday marks eighteen years since the very first release of WordPress. I consider myself so lucky to have co-founded the project alongside Mike Little. Who could have imagined that our nights and weekends hacking on blogging software, a fork of b2/cafelog, could turn into something powering over 40% of the web? Or that nearly twenty years in, it would be getting better faster than it ever has been?
\n\n\n\nI blogged these anniversaries when WordPress was five, ten, fifteen, and last year at seventeen, but as the project reaches an age that, if it were a child, it would be heading off to college, I’m uncharacteristically at a loss for words.
\n\n\n\nThe overwhelming feeling is one of gratitude, so I want to say thank you to every person who has ever been involved with making WordPress as a contributor, a community organizer, or as an end-user of the software. It’s amazing what we can accomplish when we work together.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 27 May 2021 22:31:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"WordPress Foundation: 18 years of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://wordpressfoundation.org/?p=187010\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wordpressfoundation.org/2021/18-years-of-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4064:\"On this very day 18 years ago (May 27th), the first version of the WordPress open source software came out. WordPress has come a long way in the past 18 years. At the time of writing this blog post, WordPress has surpassed 40 releases and powers more than 40% of the web!
\n\n\n\nCheck out these 40 key milestones in the WordPress journey towards 40% of the web!
\n\n\n\n \n\n\n\nOne of the critical milestones in this journey is the establishment of the WordPress Foundation in January 2010. The foundation aims to ensure free access, in perpetuity, to WordPress and the software projects we support. People and businesses may come and go, so it is essential that the source code for these projects will survive beyond the current contributor base. This will ensure that we have a stable platform for web publishing for generations to come. As part of this mission, the Foundation will protect WordPress, WordCamp, and related trademarks.
\n\n\n\nA 501(c)3 non-profit organization, the WordPress Foundation pursues a charter to educate the public about WordPress and related open source software. We regularly host educational programs like charity hackathons and open source educational events. These programs are made possible through the help of generous donations from our donors.
\n\n\n\nIf WordPress has helped you in any way during the past 18 years, kindly consider donating to the WordPress Foundation. Money raised by the WordPress Foundation will be used to ensure free access to supported software projects, protect the WordPress trademark, and fund various programs. In short – your donations will go a long way in helping the WordPress project. You can either make a one-time donation or choose to donate annually. If you sign up for any one of the four annual subscription plans, you will be featured on our Donors page – as a token of our gratitude for supporting education programs about WordPress and open source.
\n\n\n\n \n\n\n\nWordPress would not exist without its team of global contributors that help build the software. The best way to give back to WordPress is to help us build it! You need not be a developer to give back to WordPress – some other ways to contribute to the project include translations, support, community, documentation, and marketing, to name a few. In other words – anyone and everyone can contribute to WordPress, and we strongly encourage you to do so!
\n\n\n\nThank you for your support of WordPress over the past 18 years. Your continued patronage will ensure that WordPress will keep going for the next 18 years and beyond!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 27 May 2021 10:57:41 +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:27;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress.org blog: WordPress at 18\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10380\";s:7:\"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:51:\"https://wordpress.org/news/2021/05/wordpress-at-18/\";s: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:1022:\"Today marks the 18th anniversary of WordPress’ launch, a day that I fondly refer to as WordPress’ birthday, which means WordPress is 6,575 days old. To celebrate another turn around the sun, the community has had parties, we have shared data, and we have told our story.
\n\n\n\nSince our last birthday we developed our 40th release and now also support over 40% of the web. So it seems fitting that this year’s celebration should be a list of 40 milestones that have helped us get there.
\n\n\n\n \n\n\n\nGrab a slice of cake or festive beverage and give it a scroll!
\";s: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, 27 May 2021 06:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:28;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"WPTavern: Joomla Blocks FLoC by Default, Drupal Moves to Block FLoC in Upcoming 9.2 Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=117217\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:225:\"https://wptavern.com/joomla-blocks-floc-by-default-drupal-moves-to-block-floc-in-upcoming-9-2-release?utm_source=rss&utm_medium=rss&utm_campaign=joomla-blocks-floc-by-default-drupal-moves-to-block-floc-in-upcoming-9-2-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:7349:\"Joomla has announced plans to block Google’s Federated Learning of Cohorts (FLoC) by default going forward. The 3.9.2.7 security update, released yesterday, added a Permissions Policy header to disable FLoC. Users can now find a new setting in Global configuration on the Site tab in the Site Settings area, where they can toggle FLoC on if desired. This change will also affect existing sites updated from older versions.
\n\n\n\nThe Joomla Developer Network blog outlined a few concerns contributors have about fingerprinting, the technology Google uses to gather information from a user’s browser to create a unique, stable identifier. They also highlighted cross-content exposure as another concern:
\n\n\n\n\n\n\n\nThe technology will share new personal data with trackers who can already identify users. For FLoC to be useful to advertisers, a user’s cohort will necessarily reveal information about their behavior.
This means every site you visit will have a good idea about what kind of person you are on first contact, without having to do the work of tracking you across the web.
If you visit a site to buy a jumper they will have access to your cohort identifying number. This could also give them your political thinking or reveal that you are also in certain defined medical groups. There is nothing to stop these groups being backward engineered and your movement between the cohorts will reveal a lot about you over time.
A similar permissions policy header was added to Drupal 9.2.0-beta1 on May 14, after a lengthy discussion with overwhelming consensus to block FLoC. It is expected to be part of Drupal core on June 16, 2021, when 9.2 is scheduled to be released.
\n\n\n\n“I’d love to see this added to core and enabled by default,” Drupal founder Dries Buytaert commented on the implementation discussion. “We should provide an option/mechanism to disable it though.” He said he has already added a Permissions-Policy header on his personal blog.
\n\n\n\nDrupal makes disabling it a bit more of a hurdle than Joomla, as it requires setting block_interest_cohort
to FALSE in the settings.php file.
Although FLoC is still in the experimental stage, many other frameworks and tools have blocked it or are planning to block it. The DuckDuckGo Chrome extension has been reconfigured to block FLoC’s tracking, in addition to DuckDuckGo Search opting users out. GitHub is also blocking FLoC on GitHub Pages and all sites served from the github.io domain. Although Chrome is the market leader by a wide margin, Google has not yet been able to sway any other major browsers to get on board. At this time, Microsoft Edge, Safari, and Firefox do not plan to adopt FLoC.
\n\n\n\n“It is disappointing to see Google, instead of taking the present opportunity to help design and build a user-first, privacy-first Web, proposing and immediately shipping in Chrome a set of smaller, ad-tech-conserving changes, which explicitly prioritize maintaining the structure of the Web advertising ecosystem as Google sees it,” Brave CEO and co-founder Brendon Eich and senior privacy researcher Peter Snyder wrote in a statement on the company’s blog. “The worst aspect of FLoC is that it materially harms user privacy, under the guise of being privacy-friendly.”
\n\n\n\nBrave has disabled FLoC and the company recommends that all sites do the same, advising that “any new privacy-risking features on the web should be opt-in.” The post concludes that FLoC will not be an improvement on current ad tech:
\n\n\n\n\n\n\n\nOverall, FLoC, along with many other elements of Google’s “Privacy Sandbox” proposal, are a step backward from more fundamental, privacy-and-user focused changes the Web needs. Instead of deep change to enforce real privacy and to eliminate conflicts of interest, Google is proposing Titanic-level deckchair-shuffling that largely maintains the current, harmful, inefficient system the Web has evolved into, a system that has been disastrous for the Web, users and publishers.
What the Web desperately needs is radical change, one where “would users want this?” is the most important question asked for each new feature. Instead, FLoC and “Privacy Sandbox” ask “how can we make this work for ad-tech, in a way that users will tolerate or not notice.”
The open source Umbraco CMS is taking a more hands-off approach to the controversial issue. In response to a PR suggesting suggesting Umbraco block FLoC, Umbraco project manager Sebastiaan Janssen said, “We feel it’s not our place or task to enforce this kind of blocking, we believe site implementers should be free to use whatever services they think make sense for their sites (as well as block them when they want).”
\n\n\n\nAt this point in Google’s Chrome’s Origin Trial, Chrome representatives do not yet know how the FLoC API will be finalized for determining which pages will be included in FLoC calculations. WordPress has not yet made a determination about whether to block FLoC or leave it site owners to decide. Multiple FLoC blocking plugins are already available to users who want to opt out now. After a lengthy and heated discussion on a proposal to block FLoC by default, WordPress core leadership moved the conversation to Trac where contributors are monitoring Google’s experiment.
\n\n\n\nThe ticket has not yet received much feedback as WordPress is taking a more cautious approach that will depend on how Google decides to implement its FLoC API. Without the support of any major browsers, WordPress’ support or opposition may be critical to the success or failure of FLoC adoption on the web. Once more information from the FLoC trial becomes available, WordPress contributors will be in a better position to decide a course of action.
\";s: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, 27 May 2021 02:25:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"WPTavern: FSE Outreach #7: Building a Portfolio in the Upcoming Template-Editing Mode\";s:7:\"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=117293\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:211:\"https://wptavern.com/fse-outreach-7-building-a-portfolio-in-the-upcoming-template-editing-mode?utm_source=rss&utm_medium=rss&utm_campaign=fse-outreach-7-building-a-portfolio-in-the-upcoming-template-editing-mode\";s: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:6494:\"Feedback for round #7 of the FSE Outreach Program opened today. Like round #6, the focus is once again on template-editing mode, a feature that is slated to ship with WordPress 5.8. All hands need to be on deck for it to have a chance of a successful landing.
\n\n\n\nI have been eager for this round of testing. FSE Outreach lead Anne McCarthy asked volunteers to follow a 16-step plan for building a portfolio template. Unlike the previous six tests, this one gives users more leeway, room to explore template editing.
\n\n\n\nAs usual, the base set of tools is the latest version of the Gutenberg plugin and the TT1 Blocks theme.
\n\n\n\nFor my portfolio, I decided to approach it as a hypothetical photographer who wanted to drum up some new clients and show off his latest work. The following screenshot is the end result:
\n\n\n\n\n\n\n\nAnyone is welcome to grab the HTML block code for this template. I saved it as a GitHub Gist. The image URLs are to my local machine, so you will need to update those if you decide to give it a spin.
\n\n\n\nI had a lot of fun with this. And frustration. Some more fun. And…you guessed it…some more frustration.
\n\n\n\nThe editor and I got off to a rough start. After adding my Cover block, I wanted to add a Columns block inside. Error. The dreaded invalid block message. I switched over to the code view to see if there was anything odd. It was empty. After switching back to visual, the Columns block seemed to be working. I was able to inconsistently reproduce this issue in template-editing mode.
\n\n\n\nI used a Columns block because it is the only way that I know how to create a left-aligned container covering 50% of its containing element. It is a bit of a hack, but you can set the block to one column and adjust its width to whatever size you need. Ideally, users would be able to do this with the Group block.
\n\n\n\nIt was the underpinning of my template header area. I went with the traditional hero/cover intro that spanned the width of the page.
\n\n\n\nHeader section of template using Cover block.\n\n\n\nAdding a site logo and navigation is where I hit my second snag. The navigation worked fine, mostly. On mobile, the responsive menu overlay is partially covered by the WordPress toolbar on the front end. However, I already knew this. Responsive nav menus are a work in progress.
\n\n\n\nI was unable to use the Site Logo block. Whenever I attempted to add it, it had a continual spinner icon that never went away. So, I opted for an Image block — you make do with the tools you got or the ones that are working.
\n\n\n\nSecond test of adding a site logo in different section.\n\n\n\nThe next section of template testing consisted of adding a Query pattern and customizing it. I have a love/hate relationship with queries in Gutenberg right now. The Query block itself works well. It has a solid balance between advanced usage and simplicity for the most part. I am amazed at what the development team has done over months upon months of iteration.
\n\n\n\nThe downfall is that the Query block is merely a wrapper. It is only as good as its weakest sub-block. Most of its nested blocks are for post-related data, and the weakest among them is Post Featured Image. It limits everything that can be truly fun about building queries. It does not even cover a basic sub-set of the Image, Cover, and Media & Text options.
\n\n\n\nIt is frustrating because users and theme authors cannot build out their visions. I know it will get there someday. Today, we are limited to the basics without any themes offering highly customized Query patterns.
\n\n\n\nIt is tough to go wrong with a simple grid, so that is what I did.
\n\n\n\nGrid-style portfolio layout (first image is out of line in editor)\n\n\n\nI followed that section with two Columns blocks nested inside another Columns block for a testimonials group. Then, I wrapped it up with a basic footer, running into the same issue with uploading a site logo. The most prevalent problems in these sections were inconsistent spacing.
\n\n\n\nSome of the limitations with these tests are not from the template editor in Gutenberg. Instead, they are from the TT1 Blocks theme. However, I suppose that depends on your philosophy about what the future of theme development should be. If most front-end styles should come from WordPress/Gutenberg, it is not a theme issue.
\n\n\n\nVertical alignment is inconsistent in the best of times. Liberal use of the Spacer block is not ideal in real-world projects to align blocks. It can be a handy tool when needed, but it should not be a crutch for correcting foundational issues. The block system adds a few potholes in the road, but a well-rounded and tested theme can mitigate most of these problems. And, TT1 Blocks just does not do this. It relies almost exclusively on the core block styles without swerving left or right when it needs to.
\n\n\n\nThe current padding controls for a few blocks like Group help with this. However, most users are not going to micromanage every pixel of every page on their sites. The same can be said for the margin controls when they become available. Again, both are useful and necessary tools, but users should not lean on them too heavily to correct design issues. In the long run, it will create more problems as site owners eventually swap themes.
\n\n\n\nMismatched output in the editor versus the front end can become a headache at times. This is a known issue and noted in the call for testing, so I won’t harp on it.
\n\n\n\nI enjoyed the process — yes, I revel in both the fun and frustration. Aside from everything that I think is broken, the overall system is pretty dang sweet. There are far more things that the development team has nailed down than there are that feel janky. However, calls for testing are all about finding the problems. I encourage all Tavern readers to join in and report your feedback.
\";s: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, 27 May 2021 01:04:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:157:\"HeroPress: WordPress – The Source Of My Satisfaction And Joy – વર્ડપ્રેસ – સંતોષ અને આનંદ નો સાધન\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=3609\";s:7:\"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:168:\"https://heropress.com/essays/wordpress-the-source-of-my-satisfaction-and-joy/#utm_source=rss&utm_medium=rss&utm_campaign=wordpress-the-source-of-my-satisfaction-and-joy\";s: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:23359:\"આ નિબંધ ગુજરાતીમાં પણ ઉપલબ્ધ છે
\nMy adventure with WordPress started back in the year 2017. Till then there were many ups and downs and I was clueless which field I will enter into. Right until the end of 2016, I was giving my exams to become a Chartered Accountant (CA) equivalent to CPA. I also love baking cakes and pastries. So, in the first half of 2017, I had started a small homegrown bakery for making donuts. It was interesting but it didn’t give me a sense of satisfaction. I also hosted some small exhibitions of fabrics and fashion apparels.
\n\nIn short, I tried many different fields but I still wasn’t happy from within.
So, after giving up on CA (for which I spent a few years) and trying out hands on baking I still did not have the sense of satisfaction and wanted to do something that would give me an identity of myself and happiness. One casual day, my husband Dhruvin asked me to get involve with WordPress in some way or the other. But, I wasn’t sure whether I would get a place in the technical world or not. This was a completely different challenge for me.
\nAfter giving a serious thought I decided to get started with WordPress. I spent the initial 6-8 months exploring WordPress, learning the basics about the Web, making myself comfortable with it & deciding if this is something I would love to work on or not. I then participated in WordCamp Mumbai 2018. That was one of the few WordCamps I have attended. This WordCamp gave me enough confidence that WordPress is the new sky for me where there is no limit.
\nNow, that I got familiar with WordPress, the next question for me was what kind of role or a job I would best fit into?
\nI started interacting with a few people in WordCamp (which I miss very badly these days), I understood that I like interacting and engaging with people a lot. So, I thought that the Customer Support role would fit perfectly with my personality.
\nOnce I was convinced about this, I got an opportunity to work with Tyche Softwares. They are a plugin development company focussing on niche WooCommerce plugins.
\n\nThis was the first step of my professional journey in WordPress, something that I never imagined I would step into.
I started enjoying it more as I would gain immense satisfaction when I helped customers solve their problems.
\nI also tried my hand at the Business Development and Analytics part. I used to analyze customer feedback. The analysis involves creating the processes to improve the customer satisfaction and looking at how to automate a certain task using the tools at our hand. These things help in taking some important decisions on companies’ plugins with regards to new features.
\nI love attending WordCamps. I began attending WordCamps in 2018 and my very first WordCamp was WC Mumbai 2018. Since then, I’ve been going to as many as would fit in my schedule every year. I learn something new at every WordCamp, we deepen existing relationships and start new ones.
\nMy first major Wordcamp was WCEU 2019 held in Berlin. It was a memorable one which will be in my mind for ages. I realized that it’s so much fun getting to meet people in real life whom you have only known on social media. WordCamps have also been a great chance for me to learn from others and collaborate on ideas surrounding WordPress.
\n\nWordCamps have also been a great opportunity for me to travel and/or meet up with old friends, and make new ones. Of course, I also love the learning aspect of WordCamps. I look forward to learning new things and to speakers challenging my way of thinking, and seeing if there are ways I can improve my workflow or productivity or as a person.
\nThe WordPress community has taught me that it’s ok if I don’t know everything, nobody does. We are all good at certain things and that’s totally fine!
\nThe other memorable WordCamp for me was WordCamp Vadodara that happened in October 2019. I applied as a volunteer & the organizing team was kind enough to give me that opportunity. That entire day, I was taking video bytes of the attendees, helping with registrations, and running around just trying to talk to as many people as I could. I barely got time for my lunch or time to spend time at the Tyche sponsors booth. Trust me, at the end of the day, I felt like I am just made for this! I enjoyed every bit of this experience.
\n\nAfter volunteering a few more WordCamps, I applied to volunteer at the first-ever WordCamp Asia, which was to be held in Feb 2020 & my application was accepted as well. Unfortunately, COVID-19 struck just at that time & the event couldn’t take place.
\nI am definitely looking forward to helping the community in all the ways I can.
\nI love traveling and meeting new people. The idea of travel, packing my bags and disappearing to someplace, lives inside my brain all the time.
\nWhenever I meet someone for the first time or even encounter an old friend, I instantly want to talk about their own adventures.
\n\nAs a kid I was always curious about the lifestyle of people living in the other part of the world.
Till date, I love exploring such things. I deeply believe travel makes you richer, not in your wallet, but in your intelligence and compassion.
\nI also love dancing, cooking new dishes and spending time on social media. I love watching cartoons too ;)
\nThe year 2020 has been a year full of surprises. Virus, lockdowns, travel restrictions to many such things. Through all these things was a moment of joy for me and my family. I was going to be a mother :) I was really happy but deep inside I was also having a feeling that I would loose my career and will not stay updated with WordPress and I would need to start again with everything. But, I am glad nothing of that sort happened. I was able to keep up with the trends via Twitter and other channels.
\nI really appreciate the support and the remote work policy of Tyche Softwares enabling me to work throughout my pregnancy. The policies at the organization have always been employee friendly.
\nDhruvin and I become proud parents in November 2020.
\nI am enjoying this new phase of mine as much as I miss my involvement in the WordPress ecosystem.
\nI had taken an indefinite break until I felt that I would be able to dedicate time. Now, I am planning to resume my professional career. I would be taking my career ahead with Imaginate Solutions. Imaginate Solutions is also plugin development company focusing on niche WooCommerce plugins.
\nI am excited for the future ahead!
\nવર્ડપ્રેસ સાથેનું મારું સફર વર્ષ 2017 માં શરૂ થયું. ત્યાં સુધી મારા જીવનમાં ઘણા ઉતાર-ચડાવ આવ્યા હતા અને હું કશું જાણતી ન હતી કે હું કયા ક્ષેત્રમાં પ્રવેશ કરીશ. 2016 ના અંત સુધી હું ચાર્ટર્ડ એકાઉન્ટન્ટ (CA) બનવા માટે મારી પરીક્ષા આપી રહી હતી. મને કેક અને પેસ્ટ્રી બેકિંગ નો પણ શોક છે. તેથી, 2017 ના ફર્સ્ટ હાફમાં, મેં ડોનટ્સ બનાવવા માટે એક નાની હોમ-બેકરી શરૂ કરી હતી. તે રસપ્રદ હતું, પરંતુ તે મને સંતોષ ની ભાવના આપતું ન હતું. મેં ફેબ્રિક્સ અને ફેશન એપેરલ ના એકઝીબીશન પણ હોસ્ટ કર્યા હતા.
\n\nટૂંકમાં, મેં ઘણાં વિવિધ ક્ષેત્રો અજમાવ્યાં પરંતુ હું હજી પણ અંદરથી ખુશ નહોતી.
તેથી, CA (જે માટે મારા થોડા વર્ષો ગયા છે) છોડી દીધા પછી અને બેકિંગ પર પણ હાથ અજમાવ્યા પછી મને હજી પણ સંતોષની ભાવના નહોતી અને એવું કંઈક કરવા માંગતી હતી જે મને મારી ઓળખ પણ આપે અને આનંદ પણ આપે. એક કેઝ્યુઅલ દિવસે, મારા પતિ ધ્રુવિન એ મને વર્ડપ્રેસમાં ઇન્વોલ્વ થવાનું સજેસ્ટ કર્યું. પરંતુ, મને ખાતરી નહોતી કે મને તકનીકી વિશ્વમાં સ્થાન મળશે કે નહીં. મારા માટે આ એક સંપૂર્ણપણે અલગ પડકાર હતું.
\nથોડું ગંભીરતા થી વિચાર કર્યા પછી મેં વર્ડપ્રેસ શું છે એ જોવાનું પ્રારંભ કર્યું. મેં પ્રારંભિક 6-8 મહિના વર્ડપ્રેસની શોધખોળમાં, વેબ વિશેની મૂળભૂત બાબતોને જોવામાં, મારી જાતને તેનાથી comfortable બનાવવામાં ગાળ્યા. મારે એ નક્કી કરવાનું હતું કે આ કામ કરવામાં મને રસ છે ક નહિ. મેં વર્ડકેમ્પ મુંબઈ 2018 માં પણ ભાગ લીધો હતો.આ વર્ડકેમ્પે મને પૂરતો વિશ્વાસ આપ્યો કે વર્ડપ્રેસ મારા માટે નવું આકાશ છે જ્યાં કોઈ મર્યાદા નથી.
\nહવે, જ્યારે હું વર્ડપ્રેસથી પરિચિત થઈ ગઈ ત્યારે મારો આગળનો પ્રશ્ન એ હતો કે હું કયા પ્રકારની ભૂમિકા અથવા નોકરીમાં શ્રેષ્ઠ રીતે ફિટ થઈ શકું?
\nમેં વર્ડકેમ્પમાં થોડા લોકો સાથે વાતચીત કરવાનું શરૂ કર્યું (જે હું આ દિવસોમાં ખૂબ જ યાદ કરું છું). એ વાતચીત થી હું સમજી ગઈ કે મને લોકો સાથે વાર્તાલાપ કરવાનું અને વ્યસ્ત રહેવું ગમે છે. તેથી, મેં વિચાર્યું કે કસ્ટમર સપોર્ટ રોલ મારા વ્યક્તિત્વમાં સંપૂર્ણ રીતે ફિટ થશે.
\nએકવાર મને આ વિશે ખાતરી થઈ ગઈ પછી, મને Tyche Softwares સાથે કામ કરવાની તક મળી. તેઓ વિશિષ્ટ WooCommerce plugin પર ધ્યાન કેન્દ્રિત કરતી એક plugin કંપની છે.
\n\nઆ વર્ડપ્રેસમાં મારી વ્યાવસાયિક મુસાફરીનું પહેલું પગલું હતું, જેની કલ્પના મેં ક્યારેય કરી નહોતી.
મેં જ્યારે ગ્રાહકોને તેમની સમસ્યાનો હલ કરવામાં મદદ કરી ત્યારે મને ખૂબ સંતોષ અને આનંદ નો અનુભવ થયો.
\nમેં બિઝનેસ ડેવલપમેન્ટ અને એનાલિટિક્સ પર પણ હાથ અજમાવ્યો છે. હું કસ્ટમર ફીડબેક નું એનાલીસીસ કરતી હતી. કસ્ટમર ને વધુ સંતોષ મળે એના માટે જે સુધારો લાવવાની જરૂર હોય અને જે કાર્ય માં ઓટોમેશન લાવી શકાય એ બધાનું એનાલીસીસ કરતી હતી. આ એનાલીસીસે કંપનીના ઘણા મહત્વપૂર્ણ નિર્ણયો લેવામાં મદદ કરી છે.
\nમને વર્ડકેમ્પ્સમાં ભાગ લેવાનું ખુબ જ પસંદ છે. મેં 2018 માં વર્ડકેમ્પ્સમાં ભાગ લેવાનું શરૂ કર્યું અને મારો પ્રથમ વર્ડકેમ્પ WC મુંબઇ હતો. ત્યાર પછી, હું દર વર્ષે મારા સમયપત્રકમાં ફિટ થાય તેટલા વર્ડકેમ્પ્સમાં ભાગ લવ છું. હું દરેક વર્ડકેમ્પ માં કંઇક નવું શીખું છું. વર્ડકેમ્પ્સ જુના સંબંધોને વધુ ઘાડા બનાવે છે અને નવા સંબંધોની શરૂઆત કરવામાં મદદ કરે છે.
\nમારી પ્રથમ મુખ્ય વર્ડકેમ્પ બર્લિનમાં યોજાયેલી WCEU 2019 હતી. તે યાદો મારા મગજમાં યુગો સુધી રહેશે. મને સમજાયું કે વાસ્તવિક જીવનમાં એવા લોકોને મળવાનું ખૂબ જ આનંદની છે, જેને તમે ફક્ત સોશિયલ મીડિયા પર જાણતા હતા. વર્ડકેમ્પ મારા માટે અન્ય લોકો પાસેથી શીખવાની એક શ્રેષ્ઠ તક છે.
\n\nવર્ડપ્રેસ community મને શીખવ્યું છે કે બધાને બધું ના આવડે. એટલે કોઈ વસ્તુ જો મને નથી ખબર તો તે ઠીક છે. એમાં સંકોચ અનુભવ કરવાની જરૂર નથી. બધા અલગ અલગ વસ્તુ માં માહિર હોય છે અને તે ઠીક છે!
\nમારા માટે બીજું યાદગાર વર્ડકેમ્પ હતું WC Vadodara જે October 2019 માં થયું હતું. મેં એક Volunteer તરીકે અરજી કરી હતી અને મને આયોજક ટીમે તે તક આપી હતી. તે આખો દિવસ, હું ઉપસ્થિત લોકોના વિડિઓ બાઇટ્સ લઈ રહી હતી, રજીસ્ટ્રેશન માં મદદ કરી રહી હતી અને શક્ય તેટલા લોકો સાથે વાત કરવાનો પ્રયાસ કરી રહી હતી. Tyche સ્પોન્સર્સ બૂથ અને મારા બપોરના ભોજન માટેનો પણ સમય મે જેમ તેમ નીકળ્યો હતો. એ દિવસે મને લાગ્યું કે હું આજ કામ માટે બની છું! મેં આ દરેક અનુભવનો આનંદ માણ્યો.
\n\nથોડા વધુ વર્ડકેમ્પ્સમાં મેં volunteering કરી પછી, મેં Asia ની પહેલી વર્ડકેમ્પ્ WC Asia માં પણ Volunteer ની અરજી કરી, જે ફેબ્રુઆરી 2020 માં યોજાવાની હતી અને મારી અરજી પણ સ્વીકારી લેવામાં આવી. દુર્ભાગ્યે, COVID-19 ત્રાટક્યું અને ઇવેન્ટ થઈ શકી નહીં.
\nહું community ને જે રીતે કરી શકું તે બધી રીતે મદદ કરવા માટે ચોક્કસપણે રાહ જોઈ રહી છું.
\nહું મુસાફરી અને નવા લોકોને મળવાનું પસંદ કરું છું. મુસાફરી નો વિચાર અને મારી બેગ પેક કરી ક્યાંક અદ્રશ્ય થઈ જવું એવો જ વિચાર મગજની અંદર આખો સમય રહે છે.
\nજ્યારે પણ હું કોઈને પ્રથમ વખત મળું છું અથવા કોઈ જૂના મિત્રને મળું છું, ત્યારે હું તરત જ તેમણે પોતાના adventure વિશે વાત કરું છું.
\n\nએક બાળક તરીકે હું હંમેશાં વિશ્વના બીજા ભાગમાં રહેતા લોકોની જીવનશૈલી વિશે ઉત્સુક હતી.
આજની તારીખમાં પણ મને આવી વસ્તુઓનું અન્વેષણ કરવું ગમે છે. હું માનું છું કે મુસાફરી તમને તમારા wallet માં નહીં, પણ તમારી બુદ્ધિ અને કરુણામાં સમૃદ્ધ બનાવે છે.
\nમને નૃત્ય કરવું, નવી વાનગીઓ રાંધવી અને સોશિયલ મીડિયા પર સમય વિતાવવાનું પણ ગમે છે. મને કાર્ટૂન જોવાનું પણ ગમે છે;)
\nવર્ષ ૨૦૨૦ સૌ માટે આશ્ચર્યથી ભર્યું વર્ષ રહ્યું. જેમ કે વાયરસ, મુસાફરી માં લોકડાઉન અને ઘણી બીજી એવી બાબતો. આ બધી મુશ્કેલી વચ્ચે મારા અને મારા પરિવાર માટે એક આનંદ ની વાત હતી. હું માતા બનવા જઈ રહી હતી :) હું ખરેખર ખુબ જ ખુશ હતી પણ અંદરથી મને એક વાત સતાવતી હતી. મને એમ થઈ રહ્યું હતું કે હું મારી કારકિર્દી ગુમાવી દઈશ અને વર્ડપ્રેસ સાથે અપડેટેડ નહીં રહી શકું અને મારે બધું ફરી શરૂ કરવું પડશે. પરંતુ, મને આનંદ છે કે આ પ્રકારનું કંઈ થયું નથી. હું Twitter અને અન્ય ચેનલો દ્વારા trend સાથે updated રહી સાકી છું.
\nહું ખરેખર Tyche Softwares ની રિમોટ policy ની પ્રશંસા કરવા માંગુ છું. જેની મદદ થી મે pregnancy ના ૯ મહિના કામ કરી શક્યું. Tyche ની નીતિઓ હંમેશાં employee friendly રહી છે.
\nધ્રુવિન અને હું નવેમ્બર 2020 માં ગૌરવપૂર્ણ માતા પિતા બન્યા. હું જેટલી આ મારા નવા તબક્કાની મજા માણી રહી છું, એટલી જ હું વર્ડપ્રેસ ઇકોસિસ્ટમમાં મારુ સ્થાન miss કરી રહી chu.
\nજ્યાં સુધી મને લાગતું નતું કે હું યોગ્ય સમય સમર્પિત કરી શકીશ ત્યાં સુધી મેં અનિશ્ચિત વિરામ લીધો હતો. હવે, હું મારી વ્યવસાયિક કારકિર્દી ફરી શરૂ કરવાની યોજના બનાવી રહી છું. હું મારી કારકિર્દીને Imaginate Solutions સાથે આગળ લઈ જઈશ. Imaginate Solutions પણ વિશિષ્ટ WooCommerce plugin બનાવનાર plugin કંપની છે.
\nહું મારા આગળના ભવિષ્ય માટે ઉત્સાહિત છું!
\nThe post WordPress – The Source Of My Satisfaction And Joy – વર્ડપ્રેસ – સંતોષ અને આનંદ નો સાધન appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 26 May 2021 13:38: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:10:\"Dhara Shah\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"WordPress.org blog: Coloring Your Images With Duotone Filters\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10349\";s:7:\"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:77:\"https://wordpress.org/news/2021/05/coloring-your-images-with-duotone-filters/\";s: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:4380:\"Created by Alex Lende
\n\n\n\nBeginning with WordPress 5.8, you can colorize your image and cover blocks with duotone filters! Duotone can add a pop of color to your designs and style your images to integrate well with your themes.
\n\n\n\nDuotone doesn’t work in quite the same way as Instagram filters. Whereas Instagram filters do color adjustments (color levels/curves and sometimes a vignette for the photo editors among us), the new duotone filters entirely replace the colors of your images.
\n\n\n\nPhoto by Charles Pragnell.You can think of the duotone effect as a black and white filter, but instead of the shadows being black and the highlights being white, you pick your own colors for the shadows and highlights.
\n\n\n\nFor example, a grayscale filter can be created by selecting black and white as shadow/highlight colors, and a sepia filter by choosing brown and tan.
\n\n\n\n\n\n\n\nAnalogous colors can add a subtle effect and work well for cover backgrounds where the overlaid text still needs to stand out.
\n\n\n\n\n\n\n\nMuch more vibrant and interesting effects can be made with complementary colors.
\n\n\n\n\n\n\n\nThe duotone effect works best on high-contrast images, so start with an image with a lot of large dark and light areas. From the block toolbar, use the filter button and choose a preset:
\n\n\n\n\n\n\n\nYou can also choose colors from your theme’s palette, or a custom color of your choice.
\n\n\n\nIn addition to the image block, duotone can be applied to both images and video in the cover block.
\n\n\n\n\n\n\n\nImages and videos in your media library will remain unchanged. The duotone effect works using SVG filters and the CSS filter property, so the image or video is never modified in your library. On the one hand, this means that you can apply a filter to an image that you link to that doesn’t exist in your media library. On the other hand, this means that the filter won’t show up in RSS feeds or places that use the image URL directly.
\n\n\n\nThe API for adding duotone colors to blocks is experimental in Gutenberg v10.6. Still, the documentation for using it in your own blocks can be found and will be updated under Supports Color in the Block Editor Handbook. Themes can add duotone presets with theme.json. More information can be found under Global Settings & Styles Presets in the Block Editor Handbook.
\n\n\n\nThe duotone feature was released in version 10.6 of the Gutenberg plugin, so you can try it out now prior to the WordPress 5.8 release in July.
\n\n\n\nThanks to @joen and @mkaz for assistance writing and reviewing this post.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 26 May 2021 12:17:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: The Price of Admission: WordPress Users Get To Hold Creators Accountable\";s:7:\"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=117214\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:207:\"https://wptavern.com/the-price-of-admission-wordpress-users-get-to-hold-creators-accountable?utm_source=rss&utm_medium=rss&utm_campaign=the-price-of-admission-wordpress-users-get-to-hold-creators-accountable\";s: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:4479:\"When I reported on the WP User Avatar plugin’s rebranding and repurposing last week, it came as no surprise that users were angry. However, I did not expect pushback against those user complaints from a subset of commentators and others in the community.
\n\n\n\nThere were a few points, each boiled down to the argument that free plugin users have a sense of entitlement.
\n\n\n\nThese points focused either on the concept of plugin authors needing to make a living or the GPL, a license that offers no warranty on the code the user receives. Both of these arguments led the conversation astray at times. The focus of the user complaints was not on upsells or about code they grabbed from the wild. No, the backlash was about logging into their websites and finding things had changed with no warning. It was about a plugin installed from an official, presumably trustworthy, source being replaced with a different plugin.
\n\n\n\nWhat I see is not a group of people complaining about an advert. What I see is not a long list of users disliking feature changes.
\n\n\n\nThe issue of maintaining free plugins and user entitlement was never the point.
\n\n\n\nEven David Bisset of Post Status followed that rabbit down the hole. There are good points to be made on free plugin development being a labor of love — and sometimes just a headache from a support perspective –, but this conversation was never about a commercial upsell. It was about the ethics of wholesale swapping the codebase of one plugin with a different one.
\n\n\n\nWill some users complain about a new advert in a plugin? Undoubtedly.
\n\n\n\nWill nearly 200 users leave one-star reviews in that case? Unlikely.
\n\n\n\nMany users have a sense of entitlement. They grab a free theme or plugin and expect developers to answer their every whim. I would argue that it is a small percentage of total users based on personal experience, but that vocal minority can give the whole group a bad rep. They can be a drag on a developer’s motivation to continue with a project.
\n\n\n\nI get it. I have been doing this whole free software thing for nearly as long as WordPress has been around. It is easy to feel underappreciated for work that you pass on to the community. And, if you have no benefactor funding all of this free work, you must find some means of putting food on the table.
\n\n\n\nUsers of free software are not owed free customizations. They are not owed free technical support. They are not even owed a promise that a developer will not swap in a new codebase that does something different. They are owed nothing.
\n\n\n\nHowever, the price of admission for playing in this market, regardless of whether it is free or commercial software, is that every plugin’s success or failure rests in the hands of those who use it.
\n\n\n\nMaybe we, those of us who build free plugins, do not owe users anything. But, we have a responsibility to be trustworthy stewards of our sub-communities in the WordPress ecosystem. We have a responsibility to behave ethically, rightness and wrongness as defined by our users.
\n\n\n\nWhether it is commercial or free software, the goal is to have users — is it really software if no one is using it? They are the lifeblood of every project. Ultimately, developers who want people to use their code must answer to those who would.
\n\n\n\nOn the flip-side, developers are not owed glowing reviews on their projects. Users have a right to complain, even about a plugin that they acquired for free. It is not about them wanting special privileges or treatment. It never was. If you treat them fairly, do right by them, and communicate, you can build a living and breathing community around your software.
\n\n\n\nPlease send virtual hugs to developers who are building the plugins and themes you use. They are a vital part of WordPress’s success. Five-star ratings and donations never hurt either.
\";s: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, 26 May 2021 00:35: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:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: My Codeless Website App Detects Site Builder Tools\";s:7:\"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=114023\";s:7:\"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:165:\"https://wptavern.com/my-codeless-website-app-detects-site-builder-tools?utm_source=rss&utm_medium=rss&utm_campaign=my-codeless-website-app-detects-site-builder-tools\";s: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:3010:\"My Codeless Website is a new tool that detects if a site was built using a website builder. The app can detect more than 50 different tools that people use to create sites, including WordPress-powered ones like Beaver Builder, Elementor, and Divi, as well as Drupal, Squarespace, Shopify, Wix, and others. It was built using PHP and an AJAX call to fetch the website builder. The app’s detection capabilities extend to site builder tools that represent more than 2 billion websites, as measured by Built With.
\n\n\n\nAfter speaking with the app’s creators, who are based in Utrecht, I encouraged them to add Gutenberg to the list. The site is designed to be used by people who spot a cool website and want to quickly see what tool was used to build it.
\n\n\n\n\n\n\n\nOne place to find inspiring WordPress sites is the Websites category of the Webby Awards for 2021. In the Government & Civil Innovation category, WhiteHouse.gov won with its Gutenberg-powered site. The State of Tennessee COVID-19 Dashboard, another WordPress site nominated in the category, also used the block editor for its builder. Checking back through the WordPress-powered nominees and winners, nearly every one has a site that was built using Gutenberg. I did not find one page builder among them. This seems to indicate that most of the sites recognized with Webby awards for excellence on the web are building their designs on top of the block editor.
\n\n\n\n\n\n\n\n\n\n\n\nIn 2014, we featured a service called What Theme that detects WordPress, Ghost, Drupal, and Shopify templates. It was later moved to be maintained by CodeinWP. At that time, the main thrust of a design came through a site’s theme and its options. Over the past seven years, plugins have played an increasingly more important role in how WordPress users create their website designs, whether it’s page builders or block libraries. Simply checking for a theme will no longer give you the full picture.
\n\n\n\nMy Codeless Website is a handy tool worth bookmarking that enables you to check through a list of sites quickly to see what site builders they are using. It’s meant to appeal to entrepreneurs who need to take their businesses online so the rest of the site is geared towards client services. It would be valuable if this tool or another new tool could expand to detect the block plugins and libraries that a site is using so that visitors could get even more information on the website they find inspiring.
\";s: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, 25 May 2021 04:56:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:79:\"WPTavern: Bricks: Laying Down a Foundation in the WordPress Page Builder Market\";s:7:\"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=114867\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:201:\"https://wptavern.com/bricks-laying-down-a-foundation-in-the-wordpress-page-builder-market?utm_source=rss&utm_medium=rss&utm_campaign=bricks-laying-down-a-foundation-in-the-wordpress-page-builder-market\";s: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:7318:\"In a mature and ever-growing market of WordPress page builders, Thomas Ehrig decided to bring a new product to the ecosystem. Joined by Luis Godinho, the initial team launched Bricks in March. Unlike most other builder plugins, the project is bundled as a theme.
\n\n\n\nAs a small, 100% bootstrapped company, the team decided against going the freemium route. Pricing currently starts at $59 for a lifetime license, but that could change as the business model evolves. Potential customers are encouraged to test the product out via the open playground demo site.
\n\n\n\nCreating a restaurant menu via the Bricks demo site.\n\n\n\n“Bricks aims to provide an all-in-one site-building platform that empowers you to create beautiful, fully-fledged, and responsive sites that rank,” said Ehrig. “Without having to buy and rely on dozens of expensive and disjointed plugins.”
\n\n\n\nOne of the problems that the team wanted to avoid was end-users trying to find a Bricks-compatible theme. Instead of offering a default or placeholder, Bricks serves as an all-in-one bundle.
\n\n\n\nThe difference between a theme and a plugin is mostly a semantic one in WordPress. Aside from a few small things, a theme can do anything a plugin can do and vice versa.
\n\n\n\n“The main advantage I see providing it as a plugin is from a marketing perspective,” said Ehrig. “Elementor has done a fantastic job in this department. As you can see on the many free and premium themes that it comes bundled with. This greatly helped boost its exposure in the early days.”
\n\n\n\nAside from a few users trying to install it as a plugin, he said the team has been happy serving Bricks as a theme.
\n\n\n\nHe described the builder as a “theme that aims to tame the plugin madness.” The focus is on customization, design, and performance, but the development process is user-driven. All of this is done in the open via the project’s idea board, forum, and Facebook group. Users can submit feature requests, which others can vote and comment on. The team builds its development roadmap from this foundation.
\n\n\n\nVoting systems like this often work well in a project’s early history. However, they can become unruly as audiences grow. We will have to check in with Bricks a year or two down the road to see how their feedback system has evolved.
\n\n\n\n“We don’t build in secret,” said Ehrig. “Our public roadmap makes sure everyone knows at all times what to expect and what’s next. It also keeps us accountable. If you are not only looking for a beautiful builder that is fun to work with, but where you have an actual say about its development, I think you should take Bricks for a spin.”
\n\n\n\nBricks is bringing in its third team member to develop predesigned templates. However, they are already looking to grow the team more. Their current need is for a Vue.js and WordPress developer.
\n\n\n\nElementor has become the de facto standard for third-party page builders. Others have made dents, and WordPress is launching several sub-components of its Full Site Editing experience in version 5.8. It is getting crowded, but Ehrig believes there is plenty of seats left at the table.
\n\n\n\n“The WordPress builder market is well established,” he said. “This actually gave me the confidence to start this project in the first place. It’s been heavily validated, and it’s not going away anytime soon.”
\n\n\n\nNot wanting to launch a half-baked builder, he said the team forwent a deadline for their version 1.0. They wanted to create an MVP with all the essentials and hit the ground running. Based on the initial feedback in the past couple of months, he said it is clear there is still space in the market.
\n\n\n\n\n\n\n\nPersonally, I think there is always going to be space. After all, we are talking about tens of millions of WordPress sites that need to be launched, re-built, managed, and constantly optimized. It’s also not a winner-takes-all market, which is nice.
Your users’ trust and loyalty have to be earned every single day. If not, many move on to a different solution. As the web design and development landscape evolves, so has your product.
All those moving pieces ensure that no single player can rest on his/her laurels for long. Meaning there are always going to be opportunities if you take the time to look out and execute on them.
While the builder is somewhat of a competitor against the core platform it is built upon, it works alongside WordPress. Users can convert their block-built pages into Bricks data. This data conversion works the other way around too.
\n\n\n\n“So there is no lock-in effect,” said Ehrig of the feature, which his team made available from Day 1. “Which I think is really important. If someone decides to move away from Bricks, we don’t want him/her to be tied to our platform.”
\n\n\n\nThe team is also exploring the concept of creating blocks visually within Bricks. The goal is to enable more integration between the two, but they must wait to see how Full Site Editing evolves in the coming months to know what that might look like.
\n\n\n\nLast week, the Bricks team launched version 1.2 of its builder. It is touting its new “Container” element, which is essentially a box to put other items in. Users can control its display settings, and it already supports flex layouts, which many designers will welcome. Grid layouts are forthcoming, according to Ehrig.
\n\n\n\n“After that, I am currently very excited about the upcoming visual WooCommerce builder,” he said. “It’s a very challenging integration to get right. Not just code-wise, but also from a UI/UX perspective.”
\n\n\n\nOf the several things he thinks the team has gotten right, he mentions data integration with popular plugins like Advanced Custom Fields, Meta Box, Pods, and CMB2. He also said the version-1.0 features like global theme styles, responsive editing modes, and color palettes were things the team nailed down.
\n\n\n\n“But the one thing we are most proud of is not even a feature and something no one has really any control over,” said Ehrig. “And that’s the community that has formed around Bricks and its cause.”
\n\n\n\nIn two months, its Facebook community has grown to 2,000+ members. “Very active, positive, and helpful,” he said. “You can’t put a price tag on that.”
\";s: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, 24 May 2021 23:36:41 +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: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:72:\"WordPress.org blog: WP Briefing: Episode 9: The Cartography of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=10373\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wordpress.org/news/2021/05/episode-9-the-cartography-of-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:12609:\"In this episode, Josepha Haden Chomphosy provides a map of how to navigate WordPress teams and communication channels, along with her small list of big things.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nJosepha Haden Chomphosy 00:10
\n\n\n\nHello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Joseph Haden Chomphosy. Here we go!
\n\n\n\nJosepha Haden Chomphosy 00:40
\n\n\n\nAlmost every episode of this podcast, you can hear me invite you to join in the WordPress project, to contribute back, to get involved. And I’m sure that every time I say that there’s at least one of you who’s like “Yes. Challenge accepted!” And you wade in sight unseen, to immerse yourselves in the cheerful cacophony of open source at scale that is WordPress. You see before you all 158 ways you can start contributing and you are exhilarated by this lostness. This you think, is the lostness of infinite possibility. And for you, I’m really thankful. My work here today would not be possible if it weren’t for the brave souls who leap into something with hope as their primary plan and tactic. You are heroes, and I thank you very much for your service. For everyone else, I’m going to give you a quick tour of where WordPress collaborates and a little bit of how they collaborate. We’ll cover the Make network, the Making WordPress Slack, events for WordPress, and a rundown of the teams.
\n\n\n\nFirst, the Make network. The Make network of sites can be found at make.wordpress.org. That page includes information on most of our teams. Teams like Core and Design and Community. All of those teams require some technical skills since we’re a project built around a piece of software. However, some require a little more than others. You can think of this set of sites as the desk of each team in the WordPress project. It’s where they update each other, where they host discussions, where they refine proposals, and where they coordinate admin tasks. Contributors can write posts on most sites in the network as long as they follow the guidelines and best practices. And anyone with a wordpress.org profile can join in discussions in the comments. Most work on the Make network is asynchronous, and discussions stay open for a long enough time to allow anyone in the world to weigh in when they have the time. It’s how we try to remember that we are a globally-minded project.
\n\n\n\nThe second area is the Making WordPress Slack instance. The Making WordPress Slack instance can be found at wordpress.slack.com, and it requires an account that is associated with your wordpress.org profile. Each team in the project has a channel, although not all channels in that Slack instance, represent a standalone team. You can think of this Slack instance as a set of conference rooms. It’s where contributors connect, gain a more nuanced understanding of problems that we’re trying to solve. They host synchronous meetings and also coordinate working groups.
\n\n\n\nJosepha Haden Chomphosy 03:31
\n\n\n\nContributors can post in most channels, although there are a few that are restricted. We don’t have any social channels in this Slack instance, but most WordPress-ers do tend to find friends that they connect with. The work done here is synchronous, and most meetings last about an hour. There are about 35+ meetings a week, so you can basically always find someone around.
\n\n\n\nThe last area we work is actually at WordPress events. Word Camps and WordPress meetups happen all over the world. Unless there’s a global pandemic, then they’re kind of all over the computer and at all times of day and night. You can keep track of those on wordcamp.org or on WordPress’s meetup page, which I’ve linked in the notes below. These events bring together all sorts of facets of the WordPress project. And they are an event where local WordPress communities aim to connect, inspire and educate each other. There’s always someone at these events, who knows a little bit more about WordPress than you do. If you’re headed to want to learn more about contribution, look out for any that have a contributor day or are hosting a contribution drive. These are clearly synchronous events. And when we do get back to doing them in person, they’re also tied to physical locations. When we get back to them, I encourage you to find one that’s close to you. They are incredibly valuable.
\n\n\n\nOkay, so that’s the map of the area. Those are the three big places where we get this stuff done. Let’s do a quick map of the teams themselves. If you’re a developer and you’re looking to work inside the technology space, work with code a bit, then your best chances for teams are Core and all of its related components. They’re like 50 components, including core editor and various other things. There’s also the Mobile team WP CLI, the Tide team, Security, our brand new team, Openverse, and Meta. Those all take a fairly high amount of code knowledge to contribute there.
\n\n\n\nIf you’re more into design and product work, then we have a few teams for that as well. There’s of course, the Design team, but we also have Accessibility, Test, Triage, Polyglots kind of falls in there for me. But if you are a programs person, and we’re talking like programs, getting people together programs, not programs, as in programming or code. So if you’re a programs person, you’re looking more at the Community team, at the Themes team, the Plugin team, Polyglots, again, Training support, probably a number of others that have like program components in it as well.
\n\n\n\nIf you are really interested in learning more about contributor experience, which is how we build tools, and again, programs for all of the contributors who are showing up, then the teams for you will be teams like Meta and Documentation, Hosting, the Community team, the Training team, arguably any team that has a program as part of it is considered contributor experience because that’s how we help our contributors know what to do, what not to do, how to help them get onboarded, find their way, stuff like that.
\n\n\n\nAnd if you’re more in the communications area of things, we have quite a few teams there as well. We do have Marketing, of course, but also I think that Support ends up in our communications area, WordPress TV, obviously ends up in communications. But I think Training, Meta, Documentation, and arguably, maybe also Testing ends up in that space as well.
\n\n\n\nI realize that there are a handful of teams that I mentioned multiple times, especially Polyglots, Support, Test, Triage, Meta, Community. The reason they end up in a number of different places is that all of those teams also have a fair amount of admin and infrastructure stuff that goes into the WordPress project and community as a whole. So it touches a lot of other teams, and so they get a lot of mentions. All right. So WordPress adventurers, you now have a beginner’s map. I hope it helps, and I hope we see you around the community.
\n\n\n\nJosepha Haden Chomphosy 07:54
\n\n\n\nIf you’re still with me, that brings us today to my small list of big things. I’ve got four things for you, and I’m excited about all of them. The first two are events actually. WordCamp Europe is coming up from June seventh through the ninth. It will include a presentation from the WordPress project co-founder, Matt Mullenweg, so I encourage you to hop over, grab a ticket to check out the rest of the sessions that are happening while you’re there. The next one is WordCamp, Japan, which is happening June 20th through the 26th. And you heard that right that is seven whole days of WordCamp. It’s a little bit of a different format than we normally take, but it’s five days actually of contribution on ten specific projects. Then that’s bookended on either side of those contribution days, with full days of sessions. There’s some in English, but it’s primarily in Japanese. But either way, I think it’s going to be a really excellent event, and I encourage everyone to check it out.
\n\n\n\nThe rest of my list is not events. We have opened our sixth call for testing, it’s specifically looking at the template editing mode for Full Site Editing. It is an iteration on one of our earliest tests for the Full Site Editing outreach program. And so it has incorporated a lot of the feedback that we got in that test the first time around. So if you look at that test, which by the way, are all guided, if you’ve never tested anything before, don’t let this scare you. It’s really well written, it’s got a good guide on it and, and also allows for a little bit of exploration. But if you participated in the landing page test that we did early on, this is the follow-up to that. It incorporates a lot of the feedback that we got, so this is closing that feedback loop and I encourage you to stop by and participate in that test. It will be linked in the show notes and also I tweet about it a bit so you can run over there and find it also.
\n\n\n\nWordPress is dropping support for Internet Explorer 11. That’s happening over the summer, so around the middle of July is when that’s going to happen. If you’ve been using WordPress for a while you’ve been getting notifications. If you happen to get to WordPress with IE11, letting you know that that this particular browser is reaching the end of its life for support in general on the web, but now WordPress also is making the choice to drop support for that. And so there’s a post out on wordpress.org/news, which I will also link to in the show notes in case you have not heard about this yet. It shouldn’t have any immediate and noticeable effects on anyone who’s visiting a site that’s built using WordPress. There might be a few things in the dashboard that don’t work if you are administering a WordPress site from IE11. So there’s a lot of good information in that post. Give it a read and if you have questions, always feel free to stop by the Core chat and ask those as we go.
\n\n\n\nAnd that my friends is your smallest of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks!
\";s: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, 24 May 2021 11:55:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:109:\"Gutenberg Times: Getting Started with Themes for Full-site Editing and Block Plugins – Weekend Edition #170\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=17881\";s:7:\"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:115:\"https://gutenbergtimes.com/getting-started-with-themes-for-full-site-editing-and-block-plugins-weekend-edition-170/\";s: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:15809:\"Howdy,
\n\n\n\n\n\nI am getting really excited about the WordPress 5.8 release. It’s still about eight weeks away, but there is a lot of work in front of us. We are coming up to Feature Freeze on May 25, 2021. The Gutenberg team has a release candidate for 10.7, the last version of the plugin, that will make it into WordPress Core.
\n\n\n\nHow can you help? Test, test test!
\n\n\n\nOn the team working on the block-editor end user documentation, we have a preliminary list of relevant user-facing changes in Google Doc. We are looking for more contributors to not only get through the latest task list but also update some documentation pages with 5.6 and 5.7 changes. If you have a few hours, and want to take a deep dive into the block-editor features, let me know by joining the #docs channel or DM me on the Make Slack.
\n\n\n\nWishing everyone lots of patience. We are still in a pandemic, and all good things take time.
\n\n\n\nYours 💕,
Birgit
PS: Did a deep dive into the wp.data package to learn more about state management for the block-editor. Do you know of any resources that helped you get the hang of it? The usual metaphors don’t seem to help much.
\n\n\n\nAnne McCarthy posted about Hallway Hangout: Discussion on Full Site Editing Issues/PRs/Designs (20 May). This was the fourth Hallway Hangout, a series of information meetings, that started in April. They are all available on YouTube. Sometimes it is much easier to talk through a feature, an interface, or bugs, when you can ask questions and screen share. If you missed them, they are available on YouTube and summary posts are available on the Make block of the Test Team.
\n\n\n\nAlthough, I long for in-person WordCamps, they are still not safe in many regions. For now, connections to my WordPress friends are still virtual: pick-up Hallway Hangouts, Meetups meetings and WordCamps and conferences.
\n\n\n\nSpeaking of which: Next week WordSesh is taking place May 24 – May 27, with Workshops starting on May 28. Well, depending on where you are in the world, it will start tomorrow night.
\n\n\n\nOn the schedule a five session around Gutenberg:
\n\n\n\n\n\n\n\nFind a list of more upcoming WordPress events further below.
\n\n\n\nEight Gutenberg Tips and Tricks in eight minutes – Learn how to start developing WordPress sites with Gutenberg blocks with Bill Erickson and Gabriel A. Mays from GoDaddy. Take a look at the YouTube video and the links resources, if you are just starting out working with the block-editor in your WordPress development.
\n\n\n\nEdward Bock shared how to Properly add modern JavaScript to Gutenberg. In his article, he helps you transition from the conventional programming on PHP to adding JavaScript to your tools set
\n\n\n\nHerb Miller shared recording from his presentation: Guide to WordPress Full Site Editing, blocks and themes at the Meetup in Portsmouth. Now the Herb went beyond the template editor bits that are coming to WordPress 5.8. He demonstrated the full Site Editor, which isn’t slated to come to WordPress until 5.9 or even 6.0. To follow along you would need a block-based theme and the latest Gutenberg version (for now 10.6.2). After a tour around the Site Editor, Herb Miller, shared with the audience how he built a block-based theme.
\n\n\n\nCarolina Nymark published here full-site editing theme “Armando” in the theme directory on WordPress.org. Carolina also is a contributor to the Gutenberg repository and published a Full Site Editing course for developers. Recently, she also published a VS Code extension WordPress Block Markup with autocomplete snippets to add blocks to your templates faster.
\n\n\n\nFränk Klein of WPDevelopment Courses is getting ready to open his Building Block-Based Themes course. He already shared quite a few insights in his learnings with the articles: What I Learned Building a Full-Site Editing Theme and Implementing Global Styles in Block-Based Bosco. The Block-based Bosco Theme is also available in the WordPress.org repo.
\n\n\n\nThe theme.json settings structure is now finalized and is not experimental anymore. The Documentation is available in the Gutenberg Handbook. Riad Benguella wrote an Introduction to WordPress’s Global Styles and Global Settings to get you started on the new era of Theme development in WordPress. (Yes, I shared this before. I just want to make sure you find it again )
\n\n\n\nA few days ago, Ari Stathopoulos started working on a Theme.JSON parser to make it possible for conventional themes to take advantage of the settings file as well.
\n\n\n\nAna Segota, Ariel Design, an early adopter of Gutenberg blocks in her themes she published in 2018 and 2019, came out with her first theme embracing full-site editing, and global styles with here new Theme “Naledi”. Justin Tadlock took the theme for a spin. Once the theme is available at WordPress.org, it will be the sixth theme for full-site editing.
\n\n\n\nWhen will we see yours?
\n\n\n\nSarah Gooding has the story of Blocksy Theme Expands Free Starter Site Collection, Plans to Create New Suite of Blocks. Blocksy embraced the block-editor wholeheartedly and grew it’s business rapidly, it seems. They also integrate well with the blocks by Stackable.
\n\n\n\nBenjamin Intal, of Stackable was this week’s guest of the WP Tavern Jukebox podcast, and he discussed with Nathan Wrigley the Why He’s Betting His Business on Blocks. Intal and his team were an early adopter of the Block-editor and publish their plugin already in 2018 before the block-editor made it into WordPress Core. Since them Stackable has been an often recommended plugin for content creators, and it has grown quite a bit in features and reach. It’s certainly worth a listening, considering another wave of creativity and opportunities is coming to WordPress. This time for themes.
\n\n\n\nAlexandra Yap of Stackable recently posted the Introducing Dynamic Content. They wrote: “We’ve received a huge number of requests to display content from ACF’s custom fields in Stackable blocks, and now you can! Most ACF field types are supported as well as ACF Options Pages.”. They also integrate with Toolset.
\n\n\n\nJustin Tadlock reviewed a newly published pricing block and found You Might Not Need That Block. “With WordPress’s base blocks and a decent theme, many custom solutions are possible via patterns.”, he wrote, and he went ahead and recreated a three column pricing table with the core blocks and different themes, Twenty-Twenty, Eksell, and a full-site editing theme, too. I strongly agree with Tadlock that block patterns would provide an easier path. I can see that plugins like Easy-digital downloads, Woo Commerce and other ecommerce plugins would offer such patterns together with their Gutenberg blocks extensions to get store owners up and running quickly.
\n\n\n\nJamie Marsland shared the 10 Big Updates to PootlePress WooCommerce Gutenberg plugins Storefront Blocks and WooBuilder Blocks.
\n\n\n\nJune 7 – 9th, 2021
WordCamp Europe
A virtual event and contributor day. Call for sponsors is open.
🎉 Gutenberg Times is a media partner of WordCamp Europe 2021
\n\n\n\nJune 20 – 26
WordCamp Japan
The schedule has been posted. Most sessions will be in Japanese, with exceptions, I think…
July 17 + 18th, 2021
WordCamp Santa Clarita
Calls for speakers (May 30th), sponsors, volunteers and organizers are open.
June 24 – 26, 2021
WordCamp Cochabama (Colombia)
July 23, 2021
WordFest Live – The festival of WordPress
Call for Speakers is now open and submissions are due on May 24th, 2021
September 21 + 22, 2021
WPCampus 2021 Online
“A free online conference for web accessibility and WordPress in higher education.” Call for Proposal is up and proposal are due May 26, 2021
On the Calendar for WordPress Online Events you can browse a list of the upcoming WordPress Meetups, around the world, including WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.
\n\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nAs I was perusing the WordPress plugin directory this morning, I noticed a new block plugin, which is always one of the highlights of my week. It was a simple pricing block. Of course, I installed it and began playing around with its features. It was a version-1.0 product, so I was not going to fault it for not exceeding any expectations I might have had.
\n\n\n\nI have little doubt the plugin will meet many users’ needs. However, it did not bring much to the table that users could not already do with stock WordPress. And, as the block system continues to mature with more block options, end-users will gain more design control over every aspect of the existing core blocks.
\n\n\n\nThis is not a knock at this particular plugin. I see less and less need for many third-party blocks the more I browse and test them. With WordPress’s base blocks and a decent theme, many custom solutions are possible via patterns.
\n\n\n\nTo test the plugin’s block, I added it to a Columns block and duplicated it a couple of times to create pricing columns.
\n\n\n\n\n\n\n\nThe structure of an individual pricing block is straightforward. It contains the equivalent of the following core blocks:
\n\n\n\nSince I had the structure, I tried recreating it while using the Twenty Twenty-One theme. I kept everything nearly the same other than a couple of font sizes and colors.
\n\n\n\n\n\n\n\nThe result was not particularly impressive, but it was mostly on par with what the plugin was doing. The biggest letdown with Twenty Twenty-One is that there are no vertical spacing controls to tighten up some of the text. This is more of a limitation of WordPress than the theme. Plus, margin and padding controls are coming.
\n\n\n\nAside from one-click insertion into the content canvas, the benefits the Pricing Block plugin brings are rounded borders, box shadows, and list icons. However, these items would fit more into a site’s design if they were controlled by the theme.
\n\n\n\nKnowing that the Eksell theme solved the vertical alignment issue with a custom block style, I decided to try it. Again, I mostly stuck with the same structure.
\n\n\n\n\n\n\n\nMuch better. However, Eksell is such a beautifully designed theme that it will upgrade the appearance of nearly anything. It almost isn’t fair.
\n\n\n\nKicking things up a notch, I gave the pattern an overhaul. I moved some things around, changed a few colors, and tried to have a little fun with it.
\n\n\n\n\n\n\n\nThe noteworthy thing here is that I had far more control over the placement and design — within the current WordPress limitations. This was not possible with the plugin’s block.
\n\n\n\nThere are more robust pricing blocks. This is not a comparison of all the available options out there. However, many blocks share these problems. Often, what they need to do is take advantage of WordPress’s “inner blocks” system and nest core blocks, which provides access to existing design options.
\n\n\n\nWanting to take this experiment just a bit further, I activated a development version of the Gutenberg plugin and a block-based theme I have been tinkering with. With the right tools in hand, I had control over spacing, borders, typography, and far more — features that users will have in the coming months.
\n\n\n\n\n\n\n\nI like it, but I would also like to see professional designers take over from here. I want to see various pricing columns/tables available as patterns in themes and in the upcoming block directory.
\n\n\n\nThe next level of pricing columns would be integrating with plugins like WooCommerce, Easy Digital Downloads, and other eCommerce solutions. For example, users could insert a product’s price or buy-now button into a pre-built pattern inserted into the editor canvas. That way, the data stays updated.
\n\n\n\nHowever, this is not specifically about pricing columns. It is about the blocks ecosystem altogether. Nearly every time I see a testimonial block, for example, I just see it as another pattern that could be registered.
\n\n\n\nFor end-users, the quick solution will often be to activate an extra plugin. This requires more resources in the editor and, usually, the front end. It also ties them to another third-party tool, one which they may not necessarily need.
\n\n\n\nUltimately, most webpage sections can be broken down to the individual blocks that exist in WordPress. They simply need to be arranged in a specific order and grouped together. Our community of theme authors can start providing these solutions by doing the legwork of this grouping and register them as patterns.
\n\n\n\nThe most useful blocks do something that WordPress is incapable of doing alone or adding elements that do not exist.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 22 May 2021 00:26:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:24:\"Matt: 2021 Streaming Kit\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=54177\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://ma.tt/2021/05/2021-streaming-kit/\";s: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:5094:\"\n\n\n\nMy streaming setup post last year got an amazing reception — there are similar setups being used by executives across the board, from companies fundraising to several I know of with 100B+ valuations. Since that original setup, I’ve updated my own usage of hardware and software combinations to achieve similar or better results for about a quarter of the cost. So here’s the latest and greatest, and below I’ll talk about why the changes.
\n\n\n\n\n\n\n\n\n\n\n\nVideo: Camlink, cable, and tripod are still the same, but the camera goes from an A7R IV and a separate lens to an A7C with a kit lens, which saves about $3,000. You also don’t need the dummy battery because the A7C runs great off USB-C.
\n\n\n\nLighting: More is more, so I usually use two Key Light Airs (linked above) instead of one. If I’m on the road I’ll pair two Aputure RGB lights with two Lume Cube monopods.
\n\n\n\nAudio: My best audio advice is to upgrade to an M1 Macbook Pro so your computer is fast and the fan is never on, and position the laptop out of camera view but close to you so the built-in three-mic array picks up pretty good audio from you with no cables or earpieces. (Here’s a singer recording a song on the pre-M1 16-inch version, and note she has to remove fan noise in post-processing.) For bonus points add Krisp.ai ($60/yr) so you get background noise and room echo magically eliminated in real-time.
\n\n\n\nTeleprompter: The Glide Gear is much easier to set up and way cheaper than my old recommendation. Instead of an external monitor, I use an iPad and the MacOS Sidecar feature. I still don’t have a great way to reverse the screen; in the comments, I’ll share some of what folks have recommended to me.
\n\n\n\nThe above setup removes 75% of the cost without sacrificing any quality.
\n\n\n\nI’ve gone through every permutation on audio, including using a MixPre-3, NoiseAssist plugin, and a MKH416 shotgun mic ($2k+ total), but I never use that setup unless I’m recording a fancy audio-only podcast.
\n\n\n\nWhy am I using the Sennheiser SC30 in the above photo? Well it was an unusual situation…I was on the side of the road, next to an RV, with logging trucks rumbling by. Sometimes you don’t always know where you need to do a broadcast.
\n\n\n\nBehind the scenes! We were recording what became this panel.\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 21 May 2021 23:29:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:90:\"WPTavern: Open Source Maintainer Week Begins June 7 with Activities, Events, and Resources\";s:7:\"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=117041\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:221:\"https://wptavern.com/open-source-maintainer-week-begins-june-7-with-activities-events-and-resources?utm_source=rss&utm_medium=rss&utm_campaign=open-source-maintainer-week-begins-june-7-with-activities-events-and-resources\";s: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:2487:\"GitHub, in partnership with Tidelift, has set aside June 7-12, 2021, as Maintainer Week, a time for open source maintainers to share knowledge and experiences through a series of planned activities and events.
\n\n\n\nTidelift plans to kick off Maintainer Week on June 7 with a virtual event called Upstream, featuring 30+ sessions that attendees can watch live or access following the event. This event will focus on some of the bigger problems and trends in the open source ecosystem. For example, Sarah Novotny from Microsoft will be speaking about open source as an innovation engine. Simon Phipps, OSI Director of Standards and Policy, will be presenting on “spotting the rights ratchet model early,” a hot topic in the recent open source relicensing controversies. Attendees will also have the opportunity to meet the maintainers and experts behind many popular open source tools that are used at scale.
\n\n\n\nGitHub will be hosting its inaugural Global Maintainer Summit on June 8-9 as part of the week’s activities. It is billed as more of a gathering or “group therapy session” for maintainers, with lightning talks featuring different projects’ approaches to common problems. WordPress lead developer Helen Hou-Sandí will be presenting a session called “You Can’t Have a Solution Without a Problem.” GitHub emphasized that attendees do not have to be open source maintainers to attend, as many of the the best practices and skills discussed pertain to other aspects of life.
\n\n\n\nIn between sessions, maintainers will have the chance to build collaborative relationships with others and add skills that will help them avoid burnout. GitHub will be hosting a virtual hallway experience using Gather. This will allow attendees to talk with those standing closest to them and have smaller, more personal conversations.
\n\n\n\nOpen source maintainers who want to connect with others who share some of the same challenges, will want to add Maintainer Week’s activities to the calendar. All of the upcoming events are free but registration is required on the Upstream site.
\";s: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, 21 May 2021 20:37:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:116:\"WPTavern: Google Aims to “Revitalize RSS” and Recapture Users’ Trust with Experimental Follow Button in Chrome\";s:7:\"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=116905\";s:7:\"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:259:\"https://wptavern.com/google-aims-to-revitalize-rss-and-recapture-users-trust-with-experimental-follow-button-in-chrome?utm_source=rss&utm_medium=rss&utm_campaign=google-aims-to-revitalize-rss-and-recapture-users-trust-with-experimental-follow-button-in-chrome\";s: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:6568:\"The internet was set abuzz yesterday after Google officially confirmed that it has been testing a Follow button for websites in Chrome. In February, the publishers of Chrome Story spotted the button on Canary for Android, and speculated that it may be integrated with Google’s Discover feature. Chrome announced that it is building on RSS to allow users to follow websites. The latest content from these sites will show up chronologically on the New Tab page as it is published.
\n\n\n\n\n\n\n\nAt this time it does not look like Follow would be integrated with Discover, which is focused on surfacing content based on user-selected topics and a user’s search activity. The Follow feature appears that it will function almost like a bare bones “Chrome Reader,” if you will.
\n\n\n\nIn 2013, Google blithely closed down its Google Reader product in a post titled “A second spring of cleaning,” saying its usage had declined. Younger internet users may not realize what a slap in the face this was, and how devastating it was to the ecosystem of RSS-based tools.
\n\n\n\nIn response to a Twitter user’s suggestion to stick with open standards, a Google representative replied, “We intend to revitalize RSS, and from a product perspective, give users and creators a new, direct way to connect.” Presenting this as a new way to make RSS “mainstream consumer” friendly is a bit baffling for those who lost trust in Google’s willingness to recognize how critical RSS was for the information ecosystem in 2013.
\n\n\n\nWhile some are optimistic that Chrome’s experiment may bring visibility to RSS feeds, others are skeptical that Google may be trying to revitalize RSS for its own commercial interests and not in service of the open web. Dave Winer, who pioneered the development of weblogs and RSS syndication, gives voice to that skepticism in a reaction on his blog:
\n\n\n\n\n\n\n\n“The memory of Google Reader may have faded so much that Google appears ready to try again. Even the headline of this TechCrunch article is disturbing. Google did so much damage to RSS, the thought of them ‘reviving’ it is analogous to Exxon reviving the site of some huge oil spill, one that they didn’t contribute to cleaning up. Even worse, browser vendors have no place trying to provide the user interface for RSS. Another toxic dump site.”
Winer has a suggestion for Google that is more in the spirit of keeping things open and preserving portability for subscription lists. He recommends Google steer clear of providing any kind of a reader and instead focus on making it easy to share the subscription list:
\n\n\n\n\n\n\n\n“If Google wants to help RSS, great — here’s how. Do the subscribe button, that’s a good thing. But the result should be a dynamic OPML subscription list, that the user can provide to any reader app they want. It’s dynamic in that the contents can change, and the readers should periodically check to see if feeds have been added or removed. This way, if someday Google abandons RSS, again, everything can keep on ticking, more or less. Inviting users to rely on them shows that they have no sense of responsibility for the trust they betrayed in the past. Perhaps users can refuse to go on this ride? That might be too much to hope for.”
Google developer advocate Paul Bakaus said the Follow button experiment is “only the beginning of a bigger exploration” and the company is looking for feedback from publishers. Hopefully this exploration also includes improving how feeds are displayed in the browser. It’s not clear yet whether Google has plans to monetize the New Tab page with ads, promoted content, or through some other means.
\n\n\n\nAt this time, Google’s only recommendation to publishers is to keep their sites’ RSS up-to-date. WordPress users have nothing to worry about here, as all WordPress sites have built-in support for RSS feeds by default. If the Follow feature graduates out of the experimental stage, Google will provide more guidance to web publishers.
\n\n\n\nThis experiment does not exactly contain the decentralized feed aggregator capabilities that RSS fans might hope for, but if Google can build in an easy way to export users’ subscription lists then it might have a chance at contributing something truly useful. Users could then take their subscriptions to feed readers that will have more capabilities than Chrome’s basic reader. In this sense Chrome’s Follow button could make it easy for users to actively curate their RSS subscriptions based on their interests, promoting a more healthy and conscious consumption of news and other content.
\n\n\n\nThe landscape of RSS tools has changed over the past decade but Google has the opportunity to play a meaningful role in revitalizing RSS if they put users first this time. The biggest hurdle will be recapturing their trust after snuffing out Reader in 2013.
\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 21 May 2021 02:16:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:82:\"WPTavern: Upgrade Your Publishing Flow with the Post Descriptions WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=116996\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:209:\"https://wptavern.com/upgrade-your-publishing-flow-with-the-post-descriptions-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=upgrade-your-publishing-flow-with-the-post-descriptions-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3691:\"
Tom de Visser, a developer from Amsterdam, released the Post Descriptions plugin last week. It was his first submission to the WordPress.org plugin repository. It allows users to write short descriptions on a per-post basis, which are then displayed on the post-management screen.
\n\n\n\nFor an initial outing, it already seems to be a hit with its small user base. It has already racked up several five-star reviews and over 100 active installs. Granted, one of those reviews is from his employer, Mediaversa. While that might not seem like much from the outside looking in, anyone who has created plugins knows that it is a successful launch for an individual developer’s first plugin submission.
\n\n\n\nThe plugin’s goal is simple: leave small notes, reminders, to-dos, or longer descriptions for posts. It could be an ideal solution for a small team, but lone bloggers might need it too.
\n\n\n\nPost Descriptions works with both the regular WordPress post editor or the classic editor by adding a meta box to the side of the editing screen. Currently, it only allows descriptions for posts or pages. Maybe the developer will add a post-type-support flag or filter hook for custom post types in the future.
\n\n\n\nPosts Descriptions plugin meta box.\n\n\n\nAside from the description input box, users can tick the “Make your description important” checkbox to highlight a particular note. This option gives the text’s display a red color and turns it bold when viewed.
\n\n\n\nDescriptions are viewable via the post or page management screens. By default, they appear as a “state,” similar to how pending or draft states next to the title. The plugin also displays them under a “Description” column. Users can turn off the state display via the plugin’s settings screen and toggle the extra column via WordPress’s built-in Screen Options tab.
\n\n\n\nDescriptions as post “states.”\n\n\n\nOne of my favorite features of this plugin is the flexibility of selecting where the notes appear on the post-management screen. Those who prefer one or two words can choose to display them as states. Those who prefer lengthier descriptions can show them in a separate column. Or, do both.
\n\n\n\nColumn for displaying post descriptions.\n\n\n\nUsers can also add descriptions via the Quick Edit link on the post-management screen.
\n\n\n\nFrom a user-experience standpoint, it hits some of those sweet spots of usability and simplicity. Under the hood, the code is solid. The developer does not seem to be overthinking things and making the plugin more complicated than necessary.
\n\n\n\nFor small teams, I envision building a labeling system around this plugin that could address workflow issues. Adding short notes like Editor Review, SEO Review, and similar would alert the right team members to sign off on a post.
\n\n\n\nWhile the flexibility of displaying notes as either states or descriptions is welcome, it does not account for a third type of user. My ideal workflow would be to have separate inputs for both states and descriptions. I could create a shorter state that gets my team’s attention. Then, if more information is needed, I could add a longer description.
\n\n\n\nIdea: Separate state and description text.\n\n\n\nThe downside in such a system is that it puts yet another input field in front of the end-user. Sometimes the route with the least effort is best. And, for a quick post note plugin, it is tough to beat the plugin’s current solution.
\";s: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, 21 May 2021 00:25:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"BuddyPress: BuddyPress 8.0.0-beta2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=318656\";s:7:\"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:54:\"https://buddypress.org/2021/05/buddypress-8-0-0-beta2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4249:\"Hello BuddyPress contributors!
\n\n\n\nIf you haven’t tested our first 8.0.0 beta release, here’s another opportunity to help us give the final touches to our next major release so that we make sure it will fit perfectly into your WordPress / BuddyPress specific configuration. Beta testing is very important and we need you all, whether you’re a regular or advanced user, a theme designer or a plugin author: please contribute!
\n\n\n\n \n\n\n\n\n\n\n\nFirst we applied to ourselves the advice we just gave you into the first paragraph of this post: we’ve tested BuddyPress on WordPress 5.8-alpha and on latest stable WordPress & Gutenberg’s plugin. Our goal was to check the very promising Widgets Block Editor that is announced to be part of the WordPress 5.8 release. This helped us anticipate some deprecation notices and prevent an issue to happen into the new Widgets Block Editor Administration screen. If you were worried about losing your favorite BuddyPress widgets once WordPress 5.8 is released: be reassured, we can tell you there’s a back-compatibility mechanism into the Widgets Block feature making sure legacy widgets can still be managed from the new Widgets Block Editor Administration screen. If you’re wondering if we have a plan about migrating these widgets as blocks, we confirm we do and we actually started building these next BP Blocks!
\n\n\n\nWe also tested the Full Site Editing feature. For now, there’s a breaking change preventing our BP Theme Compat API to behave as expected but we’re on it and we’ll make sure BuddyPress is Full Site Editing ready before this feature is merged into WordPress core.
\n\n\n\nWe started documenting the new features arriving in BuddyPress 8.0.0, you can already learn about the selectable signup xProfile fields and the CheckBox Acceptance xProfile field.
\n\n\n\nFinally we’ve polished the very promising BP Members Invitations feature and made sure it was easier to extend the BP Messages UI into the BP Nouveau template pack.
\n\n\n\nThe final release is slated to early June and we need you to get there: do test this beta release of BuddyPress .
\n\n\n\nYou can test BuddyPress 8.0.0-beta2 in 4 ways :
\n\n\n\nsvn co https://buddypress.svn.wordpress.org/trunk/
git clone git://buddypress.git.wordpress.org/
Thanks in advance for your contributions
\";s: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, 20 May 2021 20:00: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: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:32:\"Matt: Squarespace Direct Listing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=54194\";s:7:\"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:49:\"https://ma.tt/2021/05/squarespace-direct-listing/\";s: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:2783:\"Squarespace filed their S-1 last month, and went a direct listing route for their stock today under the ticker SQSP, so I’ve been getting lots of questions on my thoughts on their business. It’s easier to share here in a blog than individually.
\n\n\n\nSquarespace’s CEO Anthony Casalena is a thoughtful, creative leader. It’s amazing what he’s built since 2003, and he obviously has many decades ahead of him. From our conversations I know how seriously he takes the craft not just of designing great products, but designing great organizations that will stand the test of time.
\n\n\n\nSquarespace is a customer-centric company, that has reliable, well-designed services, great support, and puts their customers first by allowing things like standards-based export. I’ve always observed them to behave and compete with the highest of ethics.
\n\n\n\nTheir products work well, and they’ve been strategic in their acquisitions, including recently Tock which I’m a big fan of.
\n\n\n\nTheir metrics are great, and there’s huge opportunity still. If you add up all the companies (including Automattic) in the independent web space it’s still only tens of millions of subscribers. I truly believe the eventual audience is every business in the world, and a good chunk of the 7 billion individuals, so there is so much room for everyone to grow.
\n\n\n\nHow about the stock? Some of my favorite investing advice comes from Charlie Munger:
\n\n\n\n\n\n\n\n“I could improve your ultimate financial welfare by giving you a ticket with only twenty slots in it so that you had twenty punches representing all the investments that you got to make in a lifetime. And once you’d punched through the card, you couldn’t make any more investments at all. Under those rules, you’d really think carefully about what you did and you’d be forced to load up on what you’d really thought about.”
If I had to pick between Squarespace or Wix, I’d pick Squarespace every time. They’re a company you could punch the card with. They’ve built a great brand through their marketing and rightly earned trust with their customers and within the community as a good business, and they have a founder-led path to success for many years to come. I’m wishing them the best in their next chapter as a public company.
\";s: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, 20 May 2021 02:37:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:110:\"WPTavern: No More Accidental Custom Plugin Overrides, WordPress 5.8 To Allow Developers To Set Plugin Hostname\";s:7:\"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=116798\";s:7:\"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:263:\"https://wptavern.com/no-more-accidental-custom-plugin-overrides-wordpress-5-8-to-allow-developers-to-set-plugin-hostname?utm_source=rss&utm_medium=rss&utm_campaign=no-more-accidental-custom-plugin-overrides-wordpress-5-8-to-allow-developers-to-set-plugin-hostname\";s: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:4281:\"Almost since the dawn of the plugin and theme upgrade mechanisms inclusion in core over a decade ago, third-party developers have asked for an easy way to bypass the system. WordPress 5.8 will finally deliver on this feature request.
\n\n\n\nWhile it has long been possible to filter the update system, methods for doing so were more complex than needed. They also required the plugin itself to be active on a site. A simple flag for enabling/disabling the feature on a per-plugin basis is long overdue.
\n\n\n\n“The utility is that this is an abstracted API that allows two things,” wrote Dion Hulse in a GitHub pull request that patched the code:
\n\n\n\nWordPress 5.8 will have a new Update URI
plugin header field. If its value matches anything other than https://wordpress.org/plugins/{$slug}/
or w.org/plugin/{$slug}
, WordPress will not attempt to update it.
Beyond that, developers can roll their own solutions if they want to handle updates for non-WordPress.org plugins. That is where the new update_plugins_{$hostname}
filter comes into play. WordPress will parse the URL included in the plugin’s Update URI
header and use the hostname as the value. Developers can then hook into it and do whatever they need.
Plugin authors with extensions hosted by WordPress.org will not need to worry about adding this new header. Rule #8 of the plugin guidelines already disallows sending executable code via third-party systems. The following sub-section covers this scenario more specifically:
\n\n\n\n\n\n\n\nServing updates or otherwise installing plugins, themes, or add-ons from servers other than WordPress.org’s
The discussion picked up some steam 13 months ago on a six-year-old ticket. “I’ve now had a plugin unceremoniously deleted from a client’s website when scheduled plugin automatic-update have run,” wrote a contributor with the username apedog. “This is actually the second time I’ve encountered this naming-conflict problem for a plugin of mine. In both cases, I had chosen a plugin name with no apriori naming conflict. However, at some later point, someone else had also written a plugin with the same generic name and submitted that to the wp.org repository. From that point on my plugin’s proper functioning is broken.”
\n\n\n\nWhile the deletion issue turned out not to be an issue on WordPress’s end, perhaps it was the spark needed to keep the conversation going.
\n\n\n\nAn active discussion is not always indicative of a feature getting the green light. Nor does it mean someone will write the code. Many such tickets have had months or years of conversation, only to eventually languish and die. This ticket seemed to have fit that bill too. It was opened in 2015. However, new features are sometimes more about timing, just pure randomness, or a developer with core commit access simply getting the job done.
\n\n\n\nThe ticket for plugins has been accepted and committed to WordPress. However, there is still the question of whether this will land for themes. The movement in the 11-year-old theme ticket indicates that it could happen.
\";s: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, 19 May 2021 23:49:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:76:\"WPTavern: #3 – Benjamin Intal on Why He’s Betting His Business on 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:48:\"https://wptavern.com/?post_type=podcast&p=116749\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:189:\"https://wptavern.com/podcast/3-benjamin-intal-on-why-hes-betting-his-business-on-blocks?utm_source=rss&utm_medium=rss&utm_campaign=3-benjamin-intal-on-why-hes-betting-his-business-on-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:51536:\"On the podcast today we have Benjamin Intal. He’s the founder of Stackable, which is a suite of custom blocks.
\n\n\n\nBenjamin decided early on that his company was going to take the possibilities that Gutenberg offered seriously. They had previously developed a page builder plugin, but felt that the opportunity presented by blocks was something that they could not overlook.
\n\n\n\nDuring the conversation, we talk about why Benjamin decided to devote so much time and energy towards creating blocks, at a time when there was almost no certainty about the status of blocks, and the block editor. Indeed, there was no clarity on whether blocks would become a core feature in WordPress.
\n\n\n\nAs we now know, blocks are an increasingly important topic in WordPress, and so Benjamin’s decision, with a little hindsight, appears to have been a wise one.
\n\n\n\nWe talk about some of the difficulties that have presented themselves over the last three years, and how they overcame them. These ranged from having to develop in the absence of documentation, to creating bespoke solutions to problems which were later handled by WordPress Core.
\n\n\n\nWe also discuss how they went about iterating their product in a technology space which was new. What methods the team used to ensure that they were building features which their users really needed.
\n\n\n\nWe also get into whether the block system is now fully mature and ready to support a growing ecosystem of developers. Is it a good idea to create ‘smaller’ blocks with a limited use case, or a large suite of blocks which work in harmony with one another? Are we entering a future in which the ‘there’s a block for that’ mentality might lead to sites with ‘block bloat’; sites with multiple blocks, with overlapping features.
\n\n\n\nIt’s an interesting chat and gives an insight into a transitional moment in the history of WordPress. A moment in which blocks are taking on much of the heavy lifting in a WordPress website. A moment in which reputations are being made.
\n\n\n\nWelcome to the third edition of the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast and transcript for people who are interested in WordPress and the WordPress community. It’s happening once per month for now, and if you wanted to be updated when new episodes are published, you can sign up at wptavern.com forward slash feed forward slash podcast. If you have any feedback about the podcast, then please head over to wptavern.com forward slash contact forward slash jukebox and there you’ll find a contact form for you to complete and thanks in advance if you do. Okay, so the podcast today features Benjamin Intal. He’s the founder of Stackable, which is a suite of custom blocks. Benjamin decided early on that his company, we’re going to take the possibilities that Gutenberg offered very seriously. They had previously developed a page builder plugin, but felt that the opportunities presented by blocks was something that they could not overlook. During the conversation we talk about why Benjamin decided to devote so much time and energy towards creating blocks at a time when there was almost no certainty about the status of blocks and the block editor. Indeed, there was no clarity on whether or not blocks would become a core feature in WordPress. As we now know, blocks are an increasingly important topic in WordPress, and so Benjamin’s decision, with a little hindsight, appears to have been a wise one. We talk about some of the difficulties that have presented themselves over the last three years and how they overcame them. They ranged from having to develop in the absence of documentation to creating bespoke solutions to problems which were later handled by WordPress Core. We also discuss how they went about iterating their product in a technology space which was new. What methods the team used to ensure that they were building features, which their users really needed. We also get into the topic of whether or not the block system is now fully mature and ready to support a growing ecosystem of developers. Is it a good idea to create smaller blocks with a limited use case, or a large suite of blocks, which work in harmony with one another? Are we entering a future in which the ‘there’s a block for that’ mentality might lead to sites with block bloat. Sites with multiple blocks, with overlapping features. It’s an interesting chat and gives an insight into a transitional moment in the history of WordPress. A moment in which blocks are taking on much of the heavy lifting in a WordPress website. A moment in which reputations are made. If any of the points raised here resonate with you, be sure to head over to the post at wptavern.com forward slash podcast and leave us a comment there. And so without further delay, I bring you Benjamin Intal. I am joined by Benjamin Intal. Hi, Benjamin. How are you doing?
\nHey, Nathan. Thanks for having me here.
\nYou’re very welcome. I think as with all podcasts like this, it’s a really good idea to get some perspective on who you are and where you have been in the WordPress space. Although it’s a bit of a generic question, I am going to ask it regardless. Would you just tell us what your relationship is with WordPress? How many years you’ve been using WordPress, how you got involved and so on and so forth.
\nYeah. So I started with WordPress development in 2010, and I stumbled into WordPress at first to create freelance websites. And I became a fan of WordPress. So I was surprised that you can extend it so much to create themes and plugins that did all manner of things. So I created my first theme, set it for sale. And then I moved into plugins, created actually a bunch of them. And now I had a development team here in the Philippines and our main focus is on building Stackable page builder Gutenberg blocks.
\nThank you very much indeed. Now, as the title of this podcast will no doubt reflect. You’ve really thrown all of your weight behind the whole Gutenberg block system. I’m just curious about why it is that you’ve done that as we speak, there are a few packs of blocks, which are similar to what you offer. You jumped on board very early and therefore you must have been fairly confident in Gutenberg and what was going to be offered. So I’m just interested in that really? Why is it that you decided that blocks were going to be the future for you, your business, your company, and all of that?
\nActually, when we started building Stackable, I think we released it early February, 2018, and Gutenberg was still in very early beta back then. And back then it wasn’t yet certain if it would get included into WordPress core, but we were doing other things related to page builders during that time as well. And we thought that it wouldn’t hurt to try building blocks for a Gutenberg. So it was something very innovative and new. So previously WordPress was all about PHP and this one, it was more about JavaScript and more about React. So it was a chance to learn new technologies. So we built actually just an MVP, minimum viable product. So we turned that into a free plugin that added blocks, uploaded it to the plugin directory, and then see what would happen. So if it works then great. If it didn’t, then at least we still had fun and got the good learning experience from it. So that’s how we got started.
\nYeah. I am curious about that. That’s quite a big commitment in terms of time and energy, and moving the assets around in your company in order to make that all happen. And I guess at that time it was a bit of a gamble. Were you prepared at that time to accept that perhaps Gutenberg wouldn’t be making it into core and that your endeavors might end up just as time spent in development, but nothing would actually come out of it. Were you in some way hopeful that it would come into Core and we’re banking on that happening?
\nIt had something to do with timing actually, before diving into Gutenberg, we actually attempted to make our own page builder before using our own resources. In the middle of it Gutenberg suddenly popped out of nowhere. And then people were talking about that it would be a page builder killer in the future. So you had kind of a crossroads. So do we continued trying to build our page builder, or should we jump into the Gutenberg bandwagon if you say, if you can say that. So what we decided was, what if we just come out with something, and then while Gutenberg is still brewing, let’s just continue what we’re doing, the page builder. And then if Gutenberg gets merged into Core, then we can maybe focus our efforts more on that. But if not, then we can continue doing what we were originally doing.
\nProbably at various points dip into the suite of blocks that you have, which is called Stackable. I’m just curious as to what the difficulties have been over the last, roughly three years or so building this, because if you’re building something into a fully mature platform where the documentation is excellent and the roadmap is clear and everybody knows how to build things. That’s one thing, but you were building into the dark really into an area of it almost like shifting sand, something that was certain today could be removed tomorrow. It was complete state of flux. The documentation probably wasn’t as fleshed out as it could be. And the roadmap wasn’t necessarily clear. So I’m just wondering if there were any difficulties which you’ve encountered over the last three years, which meant that you had to perhaps rewrite things undo things that you’d already done or indeed find new opportunities in innovations that you didn’t expect to come, which did come.
\nYeah, I guess to start off, I didn’t realize it’s been three years already. Oh my gosh. So some of the components that we can use, especially at the start, we’re a bit barebones. So we had to invent a lot of our own. So that’s fun actually. Some parts now are getting better. So like now Gutenberg has the focal point picker and the gradient color picker. So before there weren’t any of those controls, and I’m actually excited to use these new things and Stackable as well. So that’s one difficulty. About the documentation, I think it’s okay, especially if you’re just starting out, there are a lot of examples to get you started now. But a lot of the time we had to explore the code and go inside GitHub to study how things are done and how the components are used. Although even if we did that, it was still really helpful checking the code base. Since I think it’s very well written. It’s well segregated and well-maintained, there are hundreds of people who have contributed to the code. Most of whom are more knowledgeable in Gutenberg and React than me. So I also get to learn a lot of things from it. As for the roadmap, there’s a higher overview roadmap that Matt Mullenweg brought up before, the four phases. Phase one replace the classic editor and then phase two is full site editing, phase three and four are collaboration and multi-lingual. So we go around that. But what we do is we have some big assumptions, that we mainly use as our guide on the direction on what we do. So in our minds, one of the main goals of Gutenberg is to have it replace the classic editor. So it’s not meant to be a replacement for page builders per se. So if there’s no more classic editor, Gutenberg would be the best experience for writing content in WordPress. So we work around that assumption. And also, we always anticipate whatever new feature is coming. So for example, full site editing is coming in the future. So instead of creating our own solutions like that, instead of providing the ability to edit templates and headers ourselves, we just wait for the future improvements so that we can build on top of it instead of reinventing on our own.
\nDuring the last three years, have there been blind alleys where you’ve begun doing something only to figure out a) it couldn’t be done possibly or b) it was going to become a part of Core? You mentioned something just there, but I’m just wonderingh how the communication from the team that are building it has impacted what you’ve been able to do. In other words, have you always felt that there’s enough information coming downstream toward you, that you could confidently put your team to work building certain things or has the last three years been a bit of a stop-start… well we didn’t know that was going to happen? I realize that we’re at a point now where things are certainly better than they were, but just because of the fact that you are one of the few people who’s done this right from the start, I’m just wondering how that process has been over the last three years.
\nI’m not sure whether the communication has changed and I don’t think there’s something necessarily wrong with it. I treat the Gutenberg updates like normal WordPress updates. So what I mostly do is just good old fashioned research. So to be honest, I check WP Tavern on what’s new every now and then. And read the articles in there, although I’m more of a lurker in the comments than a commenter. What I also do is I used to check managewp.org before they shut down, actually. I occasionally also try out the Gutenberg plugin to see what’s new. So that’s, I think one of the main sources of my information on what’s coming, I read the change log rather actually try and read it since sometimes it can be quite technical. Make WordPress is also a very good resource for me on what’s coming. So some of the entries in there go into great detail on what’s new. Maybe there’s an API or a large change, and they sometimes have links to videos and show what’s actually new. And then actually there’s this video and Gutenberg times. So it’s like a news site, all about Gutenberg, by Birgit Pauli-Haack, where they demo the status of Full SIte editing before. So that was really helpful as well.
\nI know that the team themselves are very conscious that when Gutenberg was announced that there was real division in the WordPress community. There were many people who didn’t want to have anything to do with it and felt that it had been more or less forced upon them, shall we say? And there were many people who embraced it. It did bifurcate the community a bit, split it in two. And there was also the concern that, because it was a new project and there weren’t as many eyeballs and it hadn’t reached maturity that it was difficult to get involved. Like you said earlier, you’ve got to learn a whole bunch of new skills and many people who are quite happy using PHP, and that was as far as they wish to go, and all of a sudden there’s new requirements to learn new programming techniques and so on and so forth. But you obviously decided it was worth the investment. So that’s great. Well done to you. I’m just curious as to, because you’re shooting in the dark and inventing something new, I’m interested to know how it is that you discover from your growing audience, what it is that they would wish you to iterate on in Stackable. So obviously if we go back three years ago, there was very little that you had to show. If we go now and look at what it is that you’re offering, you’ve got a whole suite of different things with multiple complicated options. And I’m very curious to know if a plugin developer was keen to build their own block, what have you found to be a good way to discover from your audience, your memberships, your community, what it is that they wish you to build?
\nCommunication is something that we feel that is very important because while we use Stackable ourselves for some of our own projects, I feel that there are a lot of scenarios and use cases that we haven’t taken into consideration yet, and that our users would know more about. So first in communication, there’s our support. Some customers email in just to request some feature that they really need. Then there’s our Facebook community. So this is something that we started early on. So we try and foster sharing in the community. We try to be as transparent as we can. We try and share what we’re currently doing. We share GIFs and screenshots and we get feedback on those. So whether it’s a good idea or whether to continue or whether it lacks something more. And actually now it’s a bit difficult catching up with the number of requests. And we’ve discovered that what we wanted to build and what our users want, can sometimes be a bit different from each other. What’s important is to remember who you’re building for. They are the ones who tell us, what’s a good idea. So for example, we have this role manager feature where you can lock up the inspector, and it would only allow you to edit the block text, which was actually suggested by a few of our users who had clients and those clients wanted to perform edits on their site themselves, but they didn’t want them to accidentally change the design. So we wanted to add features geared towards agencies, but this was something that we didn’t even think about. So it was a good match. So that’s why we added that in.
\nI wondered if there were any things that you wish you were able to build, but you are constrained by the Gutenberg project thus far, are there any limitations that you’ve run up against? What I’m imagining here is there’s a whole bunch of people out there in the community who never use page builders, and there’s a whole bunch of people who write template files, and there’s a whole bunch of people who really embrace page builders and it’s become their modus operandi, that’s how they interact with WordPress these days. And the level of sophistication that has been built into some of these tools is pretty incredible. They can do some fairly amazing things and their team have worked very hard. But they’re in their own little silo. So as an example, page builder A over here, they’ve got their team and they’ve built all of these fantastic features and page builder B over here, they’ve built there’s and they’re completely separate, and they’re not interoperable, but we’re trying to build it a system here where everybody can bolt on top of it, Gutenberg the block editor. But I’m just wondering at the moment, if there are things which you see in third-party tools that you wish to build, but it’s simply not available to you yet. There are constraints within what’s possible.
\nI think something that fits that very well, is that the ability to edit page templates. Every now and then we get this request. Would I be able to edit headers? Can I edit my footers in all of my pages? But unfortunately we can’t do something like that in Gutenberg yet. That’s probably one of the main limitations that we have right now. And for that, there’s an answer that Gutenberg has, although it’s still in the pipeline, so we just have to wait for it, and then we can dive in and add features on top of it so that people can start creating their own page templates.
\nI think people give Guttenberg flack because it’s not entirely clear unless you really go out of your way to discover what’s coming down the pipeline and so on. It can be quite a confusing experience. And the idea that it’s in the future, going to be able to do these things, and these things. It’s a fairly drawn out process and it’s taking a long time and we had Anne McCarthy on the podcast last time talking about why that was and why that’s intentionally a fairly slow rollout because they’ve got 40 plus percent of the web to protect. But I’m just interested in whether any of that. Is a cause of frustration. If you’d have been building this yourself you may be, could have advanced things quicker, but your users are asking for the ability to, like you say, alter page templates and so on, and you can’t provide it for them, but it’s not your fault. And it may be, there’s a bit of you, which is thinking, do you know, I wish they’d hurry up and get this thing finished.
\nYeah, I think that’s really something. So it’s not really a frustration, but more of something that we always have to keep in mind is that we are quite dependent on Gutenberg’s progress. So really have to time things right most of the time. So like Full Site Editing, there was a hint that it would maybe come out late last year. And there was another hint again, that it will come out earlier this year. But fortunately that didn’t happen. So we always have to be on the tip of our toes when it comes to what’s going to be released, and what can we do about it? One funny thing, but not really funny, but maybe unfortunate since we’re building something that’s tightly intertwined with Gutenberg is that some people mix up what’s with Stackable and what’s in Gutenberg. So for example, they recently changed how reusable blocks worked. And we got some emails from users asking us why we changed the behavior, a few usable blocks, but actually that wasn’t us. It was part of the WordPress update.
\nFrom the outside that would feel like a point of frustration because suddenly something that you have got no control over is causing you to have to spend time answering support tickets and so on. Something that, that you didn’t do is consuming your time. And while it’s not a frustration, I guess that’s just the fallout of jumping in early with this. If you’d have waited to create this for another three or four years, when everything was much more mature than it is now, you would have probably had a great deal of a smoother road, but you would have missed that opportunity to become one of the people that jumped in early and made a name for themselves. So I guess as a company, you’ve just got to accept a bit of that. That goes with the territory. You’ve done this early. There’ll be a benefit to that down the road, but there’s also going to be moments right now where things don’t go as smoothly as you’d wish.
\nI think you said it quite right. So it’s just part of the territory. We just really have to accept it that way. Since if you really jump in early, there’s going to be a lot of changes, especially in Gutenberg. Where everything isn’t certain yet. So you have to keep on adjusting on what’s out there, what the people want. So I think it’s just really part of the territory. And it’s just something that you have to accept.
\nSpeaking of which let’s gaze into the crystal ball a little bit and think about what it is that you’re planning to build in the near future. Now, obviously, anything that you say now, may have to go under the microscope of what Gutenberg actually allows you to do in the way that we’ve just discussed. I’m just interested to know what it is that you’re hoping to build in the future, given what the project is hoping to provide for you.
\nSo right now we’re busy with the version three of Stackable. So currently we’re at version two, but in the middle of adding new features and listening to feedback from the users, we realized that there were some things that we weren’t able to do with how our blocks work right now. Cause right now what we did was every block, that we have, we try and make it so that you can turn any block into a whole section of your website. So while that’s good. So that also gives us a few limitations on what we can do. So in version three, we want to make things more flexible. So for example, we want to add more dynamic content stuff and also better responsive editing. So things like, adjusting how columns would collapse in tablets and mobile. So for example, if you can specify your four column layout to be a two column layout in tablet, we want people to have that ability as well, so much more advanced editing capabilities, similar to what some page builders already have. Probably down the road, maybe towards the end of the year, we hope to be able to provide starter websites, a fully package website that you can just import and start from there and probably a design system, so you can change what all your Stackable blocks would look like. Something like that. Although that’s just something we’re currently thinking right now.
\nIn terms of what you can do at the moment compared to one of the proprietary page builders that you could go and seek out in the WordPress space. Is there still a big disconnect with what they can do? So for example, you just mentioned a certain feature that page builders can currently do that you’re hoping to bring. How long into the future, and obviously again, we are crystal ball gazing. Do you see that sort of feature parity there being equal amounts of features in page builders, which you can purchase and download from the repo and what Gutenberg will provide? How far in advance do you think it’s going to be before they’re feature equal?
\nOh, I think probably around maybe two years or so, because right now, Gutenberg is still quite new. So we’re still in the area where we can just edit the contents of single pages. We’re not yet there in terms of editing the whole website in just Gutenberg and nowhere else. So I think we’re maybe around two years from that
\nIn a couple of years time in two years’ time say when maybe there’ll be many more features that people require to build full sites. Do you think that there’ll ever be a point where the people who build page builders currently need to be concerned about there being a business left for them? In other words, Do you feel that Gutenberg will replace page builders? Or is it more a case of that’ll be one option, but there’ll still be a completely viable business for people who sell their page builder software.
\nYeah. So you’re asking if Gutenberg will ever replace themes and page builders? For that, I don’t think so. I think if it replaces anything Gutenberg probably just replaces the classic editor, but with the plugins that extend Gutenberg, it can be a great alternative to page builders. Yeah. But I think in the future you can just get Gutenberg and then with the power of other plugins, it can be a viable page builder. So it can just be an alternative because there’s always going to, it’d be some people that would want an alternative version. Another way of building things.
\nI also feel it’s a bit of a case of a rising tide carries all boats. What I mean by that is that as WordPress’s market share seems to keep going up, a few years ago, it was in the mid thirties and then it became late thirties. And now we’re into the early forties percent of the top 10 million websites. You feel like the market is just getting bigger. And so even if you were wedded to a particular page builder and you’ve been using it for many years, it feels like the market’s just going to get bigger for them all. So there’s nothing to be particularly concerned about. It’s just going to be one option. You’re going to be able to do all sorts of different things with that option, but you’ll also be quite able to just carry on using the existing stack that you’ve got. If you’re happy with it. Speaking of developments in the future, there are some lovely initiatives in the WordPress space to make the creation of content, much more straightforward. And I know in your case, you can drop pre-configured blocks in and you can style them and make them look however you like. And there’s all sorts of options in there. I just wondered what you thought about some of the new developments, things like block patterns and reusable blocks, which allow us to save time by creating content, squirreling away somewhere, and whether you’re intending to use any of these features in the future within Stackable.
\nYeah. So reusable blocks are great for repeated content that you want to be consistent across your entire website. So something like a signup form for your newsletter that you can add in the middle or at the end of your blog posts, those are really helpful. So if you wanted to change something, you won’t have to go through every single blog post to update it. Block patterns on the other hand are great also, but I feel that they’re a bit under utilized. So they’re like reusable blocks, but unlike reusable blocks, if you’re the user, you can’t add block patterns on your own, and it’s up to the theme developer to add them. So I found that a lot of our users use reusable blocks like block patterns. So they add their designs as reasonable blocks, but when they add it into their pages, they just convert it back to regular blocks so that they can use that as a starting point and then customize them. So it’s like an unofficial way to save your own block designs or patterns. So I think that’s a use case that the Gutenberg developers can take into account and maybe add that in as a future update.
\nThere are so many awkward problems with the Gutenberg UI at the moment, in terms of exposing those things to us, I feel that sometimes the proprietary page builders, I feel they do a really good job of showing you what all of that looks like with their overlays and things. I’m not sure yet that, the Gutenberg project has hit upon the perfect UI. We’ve got the bar over to the left, we’ve got the bar over to the right and the fact that they’re fixed in width and you’re not really, you’re not really able to moderate them. It feels like there’s a lot of work to be done there to improve the UI, to discover all these things, and particularly in the case of reusable blocks, and block patterns. Nice ways of seeing, not just as a tiny little thumbnail, but something, large and full screen. So you can get a real idea of what it is you’re about to drop into the page. So really a conversation about, where the UX could be improved if you’ve got any thoughts on that.
\nYeah. Yeah. I think there are a lot of things that we can still improve on. Although I think it will only just take time because right now, even if it feels like there are a lot of stuff being added to Gutenberg, and there are also a lot of things that are being studied and adjusted. So I think as an example of something that can be improved, like I mentioned a while ago, I think block patterns, I think a lot of people have, can have a good use by having the ability to add block patterns or their own block patterns. Oh, actually one of the good improvements that we can do in Gutenberg, because one of the hard things to do in Gutenberg is to know where you are, in the current page. Cause it’s if you check out the block editor, if you check out Gutenberg, it’s basically a tree of a lot of blocks and then blocks inside of other blocks. So it can easily be hard to know what you’re editing. Although the, I forgot what it’s called, the navigator button on the top. The one where you, when you click it, it’s going to show you a bullet list of the blocks. So I think that can be improved. I think that can be transformed into something that you can use to actually manipulate the blocks that where you can, for example, if you want this heading to be moved into inside another container, you can just click the navigator, and then you can move it around from there directly. So I think something like that can be a good way or a good alternative for you to be able to move around blocks and figure it out where you are. Cause it’s actually sometimes hard to click on something, especially if you’re inside a columns block because inside a columns block, there’s two column blocks, and inside that you have your other blocks inside. So it’s hard to master or it’s a bit hard to make sure that people can click around and figure out where they actually are. Actually, I think the difficulty here is that there’s a balance between building a what is what you get, editor, and then also making it spacious enough that you can click around and easily figure out where you are, because if you add spaces everywhere and add outlines. So I think that’s a solution. If you add outlines everywhere, that’s going to be easier to know what’s going on in the screen. So for example, if you have the columns block and then maybe an outline block to signify that you’re inside the column. So that’s going to be easier than if you didn’t have any spaces and they don’t have any outlines. That’s going to be way easier than what we have right now. Although it’s a delicate balance because now if you have outlines and lots of spacings, it’s not going to be a, what you see is what to get builder, no matter what you do, it’s going to be, you’re going to have people who don’t want what’s going on right now. You’re going to have people who don’t like this change, or you’re going to have people that would prefer the other way around. It’s just finding the balance on the what works.
\nOne of the most fantastic features that ever I suppose, came to WordPress was the ability to add in plugins to extend what WordPress could do with extra functionality, and in the near future, we’re going to have the block directory will be available to everybody and we’ll be able to search for blocks that we don’t have yet installed and install them on our website. I’m curious about whether you think this is a good development. What I mean by that is I just wonder if there’s a concern that we need to have about people wanting to have a block for every little thing, and then downloading a ridiculous amount of blocks, most of which they don’t need, which will be consuming up resources on their website and so on and so forth. I’m just wondering what your thoughts are on this block directory, whether it’s something that you’re going to be involved in, whether you’re going to do anything like that become involved in installing directly one of your blocks at a time as opposed to selling it as a whole suite.
\nTo be honest, I was initially excited about the block directory. And I think it’s already live right. It’s working right now, except that, although I thought it was going to work more like the plugin and team directory, where there’s an actual directory that you can go to and browse, I think right now the current behavior is that you have to search for a block inside the inserter, the plus sign that you click on to add blocks. And if what you type doesn’t show a result. If you don’t have any block that matches that keyword, then that’s the only time the block directory shows up. So I think that process can be improved. I think it’s a bit off since you can only see the block directory, if you type in a search term that doesn’t match anything. So you’ll have a lot of instances when the block directory won’t show up at all. So for example, it won’t trigger. If you type in text like the t e x t since that’s the keyword of the native paragraph and heading block. So I think that’s something that can be improved on and they hope they’ll improve on. And I think if you have a lot of blocks turned on from the block directory, like a block bloat. So I think it’s just the same as with plugin bloat. So it’s like the notion of having just too many plugins installed. I think it depends on the plugins that you have in your setup. And they think with blocks, it’s going to be the same thing. So it’s quite possible to have this block bloat by installing lots of individual plugins. Especially if you add in lots of blocks that load their own style sheets, their own Javascript files, but they think this depends on how the blocks were made. So like with plugins, it depends on how the plugins were made. If you activate a lot of plugins that just loaded a lot of their stuff, every time. So that’s going to be a bad experience. So I think it’s going to be just the same. It’s going to be up to the block developers. It’s going to be the responsibility of the block authors to make everything optimized so that everything would load up properly.
\nI can see a future in which individual little blocks become a nice commodity. So at the moment, we’ve obviously got a very full free WordPress repository, and we’ve also got a very healthy paid for plugin and theme marketplace. And I can imagine a future where blocks also in the same way that Stackable is, you pay for the premium version of Stackable and that’s great, but I can see almost like on your Android or iPhone device where you are prepared to pay a smaller amounts of money for a smaller thing. It’s not a windows app or a Mac app, it’s just the Android app, you’re going to pay less for it. Just wonder if there’s a marketplace for. Individual little blocks and, you pay, I don’t know, $2, $3, $5 for a block that does this one thing. And does it well, and whether or not you’re interested in that marketplace, or if you’re going to keep your Stackable suite as one big thing, instead of lots of little things,
\nI think maybe it might be a good idea for other blocks that provide a very large functionality in just one block. So maybe a store locator block, or maybe a contact form block, but I don’t think that’s an option for us because one benefit though, with doing things as a collection is that you get everything in one go, so you get all the blocks. Maybe you can turn some of them off if you don’t need them. But if there’s an update that adds one more block in the future, then you won’t have to pay extra. So there’s that. And going back to block bloat, I think it depends on how the blocks were made. So for example, in Stackable we have optimizations in place that affect all of our blocks. So if we add another block in their roster, the plugin won’t necessarily feel any bulkier. That’s one of the benefits of a collection. So I don’t think we’re going to offer individual blocks. I don’t know right now we’re thinking maybe not, but we don’t know sometime, maybe in the future. But right now, I don’t think so.
\nI’m just curious about this sort of slight disconnect in the way that things look in the backend of Gutenberg. So if you’re doing something Gutenberg, you’ve made it and you’ve given it the correct padding and so on, but the UI kind of gets in the way a little bit. And I’m wondering if that’s a problem for you. Do you get feedback from people saying it doesn’t look the same over here as it does when I finally publish my website. Is that a problem that you’ve had to overcome and explain to people, look, it’s just parts of the UI, you’re just going to have to cope with it. How have you overcome all of that?
\nSurprisingly, we don’t have that much concerns over that. That it’s not a direct, what you see is what you get. I think it’s totally okay. Especially in desktop because technically it’s really hard to make things identical while adding all of the bits and pieces that make the content editable, like the inspector or the toolbar, but it’s easier for people to just accept that they’re not going to be identical. And they’re just going to be close enough. I think people have accepted that already, so it’s okay. And after a few edits, I think it’s easy to get the handle of it, of what your edits would look like in the front end, because basically you just ignore the sides of your website, essentially. Yeah. As I said, this is easier for desktops for mobile and tablet though, this is harder since right now, you can only do previews in Gutenberg. And all the times we see that people want to take control of how things get smooshed and how things collapse as the screen size gets smaller. So if you just keep on doing previews in Gutenberg, it’s going to be harder since, just like before you have to keep on pressing preview to view in the front end and resize your browser. So I think it’s more essential for a tablet and mobile. So first Stackable, we addressed this issue since when you do a previous in tablet or mobile our blocks would also change and you can set how they can look like on that specific screen size. Yeah, but I think it’s up to the block developers one way or they’d handle these cases as well, because Gutenberg already has some things in place. If you want to implement that in your own blocks.
\nIt’s pretty clear that you’re very bullish about where this is going. I’m guessing that you are, you as a company are all in on keeping this going and supporting this and making sure that Stackable is something which is going to be around for the future.
\nYeah, definitely, definitely. I think it’s going to be a very good future for Gutenberg.
\nBen just before we go, is there anywhere where people could contact you if they wanted to find out a little bit more about what it is that you guys are doing?
\nOh yeah. If you want to contact me, I am in Twitter. So that’s at @bfintal and I’m also in Facebook. So just search for me, Benjamin Intal, and I’m usually actually more there in Facebook than Twitter. If they want to check out Stackable, our website is wpstackable.com and we also have a Stackable community and Facebook, so you can join that as well.
\nOkay, Ben, thank you very much for joining us today.
\nInternet Explorer 11 (IE11) was released over 7 years ago and is currently used by less than 1% of all users on the Internet with usage rapidly declining. A large majority of popular websites have already stopped supporting IE11 (including Microsoft Teams in 2020), and even the Microsoft 365 apps and services will be dropping support later this year.
\n\n\n\nWhen WordPress 5.8 is released in July of this year, Internet Explorer 11 will no longer be supported.
\n\n\n\nIf you are currently using IE11, it is strongly recommended that you switch to a more modern browser, such as Google Chrome, Mozilla Firefox, Safari, or Microsoft Edge. IE11 users have been shown a warning that IE11 is considered outdated in the WordPress dashboard for the last 17+ months.
\n\n\n\nIf you are already using one of the more modern browsers above, you will only be positively impacted by this change, as there are performance benefits to dropping IE11 support. However, if any other users of your site are still using IE11, it’s possible they will be affected.
\n\n\n\nWhen support for a browser is removed from WordPress, new features are no longer tested on those browsers and are not guaranteed to function optimally.
\n\n\n\nAutomated tools that generate parts of the WordPress Core source code are also updated to exclude unsupported browsers. This means that any feature relying on these generated files will likely have bugs or stop working for users of those browsers.
\n\n\n\nThe block editor will be the area of WordPress most heavily impacted by this change because almost all of the files related to the block editor are compiled using these automated tools. Other areas of the WordPress dashboard also use CSS built with these tools and their appearance will potentially be impacted when using IE11.
\n\n\n\nAll other areas of the code base that are IE11 specific will need to be identified, evaluated, and removed on a case-by-case basis as the rest are manually maintained. This process will begin in the WordPress 5.9 release, and will likely happen gradually over several major releases. Additionally, any bugs which are reported for IE11 will not be fixed.
\n\n\n\nNo changes will be made to any of the default bundled themes as a result of this plan. No code related to IE11 support (or any other browser that may have been supported when each theme was released) will be removed from default themes. However, any new features added going forward will not be tested in IE11.
\n\n\n\nIf you are not using a default theme, it’s still unlikely that your theme will be affected by this change. Themes typically have their own browser support policies, and changes in WordPress Core do not affect those. It’s possible that your theme author may have removed support for IE11 already.
\n\n\n\nIf IE11 support is important to you and you are unsure whether your theme supports IE11, it is recommended that you reach out to your theme’s developer to confirm.
\n\n\n\nMore information on this change can be found on the Making WordPress Core blog.
\";s: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, 19 May 2021 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Jonathan Desrosiers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}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:97:\"WPTavern: Blocksy Theme Expands Free Starter Site Collection, Plans to Create New Suite of 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=116383\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:237:\"https://wptavern.com/blocksy-theme-expands-free-starter-site-collection-plans-to-create-new-suite-of-blocks?utm_source=rss&utm_medium=rss&utm_campaign=blocksy-theme-expands-free-starter-site-collection-plans-to-create-new-suite-of-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:4546:\"When Sergiu Radu and Andrei Glingeanu launched their free Blocksy theme nearly two years ago, they were surprised by how quickly their business grew during a global pandemic without any investment in marketing. Blocksy is now active on more than 20,000 WordPress sites and its commercial version, launched in October 2020, has grown to where both founders are now working full-time on the project.
\n\n\n\nApart from inadvertently gaining a few mentions on some blogs and YouTube channels, Radu said his team has done nothing to market the theme. Users have most often been referred by word of mouth and many have gotten linked into the community through Blocksy’s Facebok group, which has grown to more than 2,200 members. Users join the group to discuss the theme and share their knowledge with each other.
\n\n\n\nThree months ago, Blocksy’s founders hired two more teammates to assist with support and manage the theme’s Facebook community. Radu said he thinks support has been the most important factor in the theme’s growth. His team offers support to free users as well as those those who opt to pay for Blocksy Pro. The ticketing system is open for everyone using the theme. This might explain why Blocksy has maintained a perfect 5-star rating on WordPress.org with 455 reviews.
\n\n\n\nAnother factor in the theme’s success is its free starter sites that enable users to get going right away. In the past month, the Blocksy team has released three new starter sites, bringing the total to 10 (double the number available this time last year). Yogi, the latest release, is based on the block editor and was designed to showcase Blocksy’s capabilities for customizing and managing custom post types. These are registered with the help of WP Meta Box.
\n\n\n\nIn April, the team released Tasty, a starter site that uses the Recipe Card Blocks plugin by WPZOOM. If you’re looking for a recipe theme and plugin combination that supports the block editor, these two work seamlessly together. The team also launched Homi, a block-based WooCommerce starter site built with Stackable.
\n\n\n\nThe starter themes can be imported with one click and users get exactly what they see in the demo without having to figure out how to arrange it. An onboarding wizard guides the user through setting up a child theme and installing any necessary plugins. It imports all the posts, pages, comments, navigation menus, custom fields, terms and custom posts that are seen in the demos.
\n\n\n\n\n\n\n\nRadu said the team plans to release 3-4 more starter sites in the near future, targeting different niches, including blogger, agency, lawyers, wedding, and music/bands.
\n\n\n\nBlocksy’s developers are currently working on adding some new WooCommerce features in the next update, along with a portfolio extension. They are also working on a plan to make it easier to create starter sites.
\n\n\n\n“It’s very hard at the moment to create our starter sites,” Radu said. “Almost all Gutenberg plugins out there lack design options or other things that we may need in order to create a nice starter site. So we were feeling very limited and thought why not create our own suite of blocks that are going to meet all our needs?”
\n\n\n\nBlocksy currently uses Stackable blocks to create the demo sites. Radu said that although his team may eventually transition to using their own suite of blocks exclusively, they may also continue making starter sites with Stackable since their users like that particular block library so much. The team plans to begin building their own suite of Gutenberg blocks after the next update, beginning with a free version, followed by a pro version with some more advanced blocks.
\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 19 May 2021 04:24:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:132:\"WPTavern: ProfilePress Rebrands and Repurposes WP User Avatar, Now a Membership Plugin, Users Revolt via the WordPress Review System\";s:7:\"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=116746\";s:7:\"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:305:\"https://wptavern.com/profilepress-rebrands-and-repurposes-wp-user-avatar-now-a-membership-plugin-users-revolt-via-the-wordpress-review-system?utm_source=rss&utm_medium=rss&utm_campaign=profilepress-rebrands-and-repurposes-wp-user-avatar-now-a-membership-plugin-users-revolt-via-the-wordpress-review-system\";s: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:5971:\"Less than two weeks after publishing about the broken user experience of the former Dark Mode plugin being renamed and repurposed, another plugin development company decided to do the same. The consensus seems to be that this is a bad idea. However, the ProfilePress Team forged ahead and repurposed the WP User Avatar plugin.
\n\n\n\nInstead of a simple, single-purpose custom avatar solution, it is a full-fledged user registration, profile, login, and membership management plugin.
\n\n\n\nIt is now called ProfilePress. But, let’s call it ProfilePress Lite because there is a commercial component where you can upgrade to the actual ProfilePress premium plugin. We need to differentiate the two. Plus, the plugin itself uses that term, at least once, in the admin.
\n\n\n\nThe difference between the Dark Mode switcheroo and this one is that WP User Avatar has over 400,000 active installs, and users are voting with their feet. And their ratings. In the past 48 hours, the plugin has received a staggering 60+ one-star reviews — and counting. The WordPress.org support team has already had to close two forum topics. A review titled “Unexpected changes, expected reactions” sums up the situation.
\n\n\n\nOver 400,000 users can do a lot of damage in a little bit of time.
\n\n\n\nA fraction of a fraction of a fraction of those 400,000 users can knock a respectable 4.4 rating down to 3.6 in two days.
\n\n\n\nWhen no one from the company responds to any of the 60+ reviews, it looks like you have something to hide. Those are 60+ opportunities to at least attempt to smooth things over.
\n\n\n\nPre-3.0, WP User Avatar was a simple plugin for managing how avatars were handled on the site and allowing custom photo uploads on a per-user basis. In the plugin’s eight-year history, users had come to expect a solid plugin that handled one thing and handled it well.
\n\n\n\nSettings screen for pre-3.0 WP User Avatar\n\n\n\nIn April 2020, the plugin changed ownership. ProfilePress had taken over from Flipper Code, the project’s only contributor since 2014. Bangbay Siboliban was listed as the plugin owner from 2013-2014. It is unclear if this was an acquisition or a simple transfer. Neither the former nor the current owner has responded to a request for comment at this time.
\n\n\n\nUnder new ownership and its version 2.2.5 – 2.2.9 plugin upgrades in the past year, everything seemed to be status quo. ProfilePress kept the plugin going, fixing bugs for multiple releases. Until two days ago, users were likely unaware that a tidal wave of change was roaring their way. No announcements on the ProfilePress blog. No sticky topics in the WordPress.org support forum. Just, here’s your new membership plugin that you didn’t ask for.
\n\n\n\nUsers were greeted with a new settings screen and much more, an admin that was barely recognizable.
\n\n\n\nProfilePress (formerly WP User Avatar) settings screen.\n\n\n\nAs one user put it, “What the heck? Updated plugin and suddenly I have a full membership solution.”
\n\n\n\n“You had the plugin WP User Avatar that did one specific function — added an avatar to users like when they leave comments on the blog,” wrote another reviewer. “Now I go to update it, and BOOM, a 100% completely different plugin takes its place. “
\n\n\n\nProfilePress, the premium plugin, launched in 2015. It is a known product with an existing userbase. I cannot imagine any scenario that makes sense where the company takes a separate plugin that it acquired and implants a lite version of its premium product inside.
\n\n\n\nExcept to capitalize on the 400,000+ active installs for a quick and easy profit.
\n\n\n\nThe knee-jerk reaction is usually to demand the WordPress.org Plugin Review Team implement a rule against it. Some scenarios are less egregious than others. Drawing a subjective line in the sand can be a tough ask of them.
\n\n\n\nI am coming around to the idea of putting this decision into the hands of users. They are using the review system in the way it was meant to be used. Let them rain down all manner of hell on plugin authors who do this. Let them prop up another plugin with their numbers and hand out glowing five-star reviews for it. WP User Avatars (with an ‘s’) was a decent alternative the last I tried it.
\n\n\n\nStill, I wonder how much this hurts the plugin with its active install total. The owner might simply weather the storm and capitalize on the users left standing when the dust settles. Even if they lost an unlikely quarter or half of their install count, they are still in a position to profit from premium upgrades. Then, build a new base from users who are unaware of this current debacle.
\n\n\n\nThe more companies that do it without repercussions, the more likely it becomes a trend. But, WP User Avatar’s, ProfilePress’s, ahem, ProfilePress Lite’s users are in open rebellion. Maybe the market will simply decide.
Over the weekend, Anariel Design co-founder Ana Segota tweeted that she was nearly ready to submit the company’s first block theme into the WordPress directory. There are only five such experimental themes available for download in the repo right now, and I have been patiently awaiting more.
\n\n\n\nThe Naledi theme is in the review queue, but those who want to give it a spin can grab a copy of the ZIP file from its ticket. Or, just peruse the theme’s demo.
\n\n\n\nBlock, block-based, or FSE themes are built entirely out of blocks, not just the post content. This includes the header, footer, and everything else in between — literally, everything is a block. Such themes are the future of WordPress and need more user testing.
\n\n\n\nLike most block themes at the moment, Naledi is not meant for use on a production site. The goal is to build upon the site editor and templating systems in the Gutenberg plugin. The earliest that stable iterations of these FSE sub-components could land in WordPress would be in version 5.9 later this year, but there is no guarantee of that yet.
\n\n\n\nThe WordPress.org Themes Team allows block themes in the directory. However, a team lead must grant permission using the “special case” system in place. There is still a six-month-old ticket awaiting closure before anyone can upload block themes without special access.
\n\n\n\nOn the whole, Naledi is a well-rounded theme given the limitations of block templating right now. It has plenty of personality and is a good representation of how themers should be building on top of the system. There are miles to go, but the Gutenberg development team is driving fast.
\n\n\n\nOne of the most revealing items was how little CSS Naledi needed (roughly 20 kb). It is almost entirely built upon the theme.json
style system. Most of the code is merely modifications for custom block styles and adjustments to the core blocks.
The theme currently has nine block styles. Most of the concepts are around adding borders. Eventually, these border-related styles may be unnecessary. Border settings are coming to more and more blocks out of the box. Users will be able to directly make border changes on nearly anything, and theme designers can package their old styles as custom patterns instead.
\n\n\n\nOf the theme’s block styles, my favorite is the framed image. I have been on a bit of a frame kick as of late, so I like seeing what others are doing with the idea.
\n\n\n\nFrame style on the Image block.\n\n\n\nNaledi also bundles eight-block patterns. Most include the Columns block, but others incorporate the Media & Text and Cover blocks, such as a full-width page header.
\n\n\n\nThe Testimonials pattern uses the theme’s Overlap style for the Columns block. It shifts the left column to the right and the right column in the opposite direction, creating an overlap.
\n\n\n\nTestimonials block pattern.\n\n\n\nThere is a similar pattern named Overlapping Images that uses the same technique.
\n\n\n\nOverlapping Images block pattern.\n\n\n\nWhat Naledi does that I have not seen with many block themes yet is add several custom page templates. It technically registers only two of them via its theme.json
configuration. However, six exist in total, and the Gutenberg plugin automatically picks them all up on a per-page level — not sure if that is a bug or a feature.
Because Naledi is a block theme, users can make direct changes to any of the templates, putting their own coat of paint over the default or overhauling them entirely.
\n\n\n\nNaledi theme in the site editor.\n\n\n\nAs always, it is a welcome sight to see another block theme headed for the official directory. It is by no means perfect — working in an imperfect system. However, experiments like Naledi give me more hope that we are heading in the right direction.
\";s: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, 17 May 2021 21:42:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:\"Tue, 08 Jun 2021 02:35:43 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Tue, 08 Jun 2021 02:15:11 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:\"20201016172007\";}','no'),(142,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1623162943','no'),(143,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1623119743','no'),(144,'_transient_timeout_dash_v2_5f25301ca0145abac6dfc3a0899dc43b','1623162943','no'),(145,'_transient_dash_v2_5f25301ca0145abac6dfc3a0899dc43b',' ','no'),(146,'_site_transient_update_themes','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1623119744;s:7:\"checked\";a:3:{s:14:\"twentynineteen\";s:3:\"2.0\";s:12:\"twentytwenty\";s:3:\"1.7\";s:15:\"twentytwentyone\";s:3:\"1.3\";}s:8:\"response\";a:0:{}s:9:\"no_update\";a:3:{s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"2.0\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.2.0.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"1.7\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.1.7.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentytwentyone\";a:6:{s:5:\"theme\";s:15:\"twentytwentyone\";s:11:\"new_version\";s:3:\"1.3\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentytwentyone/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentytwentyone.1.3.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"5.6\";}}s:12:\"translations\";a:0:{}}','no'),(147,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1623119745;s:7:\"checked\";a:2:{s:19:\"akismet/akismet.php\";s:5:\"4.1.9\";s:9:\"hello.php\";s:5:\"1.7.2\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:2:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:5:\"4.1.9\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.1.9.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:59:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272\";s:2:\"1x\";s:59:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:61:\"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904\";}s:11:\"banners_rtl\";a:0:{}}s:9:\"hello.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:5:\"1.7.2\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855\";s:2:\"1x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:66:\"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855\";}s:11:\"banners_rtl\";a:0:{}}}}','no'); /*!40000 ALTER TABLE `wp_options` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_postmeta` -- DROP TABLE IF EXISTS `wp_postmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; 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_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_postmeta` -- LOCK TABLES `wp_postmeta` WRITE; /*!40000 ALTER TABLE `wp_postmeta` DISABLE KEYS */; INSERT INTO `wp_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default'); /*!40000 ALTER TABLE `wp_postmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_posts` -- DROP TABLE IF EXISTS `wp_posts`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; 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_ci NOT NULL, `post_title` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_excerpt` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'publish', `comment_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', `ping_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', `post_password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `post_name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `to_ping` text COLLATE utf8mb4_unicode_ci NOT NULL, `pinged` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_parent` bigint(20) unsigned NOT NULL DEFAULT 0, `guid` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT 0, `post_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT 0, 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=5 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_posts` -- LOCK TABLES `wp_posts` WRITE; /*!40000 ALTER TABLE `wp_posts` DISABLE KEYS */; INSERT INTO `wp_posts` VALUES (1,1,'2021-06-08 03:35:34','2021-06-08 02:35:34','\nWelcome to WordPress. This is your first post. Edit or delete it, then start writing!
\n','Hello world!','','publish','open','open','','hello-world','','','2021-06-08 03:35:34','2021-06-08 02:35:34','',0,'https://localhost/wordpress/?p=1',0,'post','',1),(2,1,'2021-06-08 03:35:34','2021-06-08 02:35:34','\nThis is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:
\n\n\n\n\n\n\n\nHi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)
...or something like this:
\n\n\n\n\n\n\n\nThe 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.
As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!
\n','Sample Page','','publish','closed','open','','sample-page','','','2021-06-08 03:35:34','2021-06-08 02:35:34','',0,'https://localhost/wordpress/?page_id=2',0,'page','',0),(3,1,'2021-06-08 03:35:34','2021-06-08 02:35:34','Suggested text: Our website address is: https://localhost/wordpress.
Suggested text: When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
An anonymised 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.
Suggested text: 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.
Suggested text: If you leave a comment on our site you may opt in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Suggested text: Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Suggested text: If you request a password reset, your IP address will be included in the reset email.
Suggested text: If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
Suggested text: 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.
Suggested text: Visitor comments may be checked through an automated spam detection service.
','Privacy Policy','','draft','closed','open','','privacy-policy','','','2021-06-08 03:35:34','2021-06-08 02:35:34','',0,'https://localhost/wordpress/?page_id=3',0,'page','',0),(4,1,'2021-06-08 03:35:41','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2021-06-08 03:35:41','0000-00-00 00:00:00','',0,'https://localhost/wordpress/?p=4',0,'post','',0); /*!40000 ALTER TABLE `wp_posts` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_term_relationships` -- DROP TABLE IF EXISTS `wp_term_relationships`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; 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_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_term_relationships` -- LOCK TABLES `wp_term_relationships` WRITE; /*!40000 ALTER TABLE `wp_term_relationships` DISABLE KEYS */; INSERT INTO `wp_term_relationships` VALUES (1,1,0); /*!40000 ALTER TABLE `wp_term_relationships` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_term_taxonomy` -- DROP TABLE IF EXISTS `wp_term_taxonomy`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; 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_ci NOT NULL DEFAULT '', `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `parent` bigint(20) unsigned NOT NULL DEFAULT 0, `count` bigint(20) NOT NULL DEFAULT 0, 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_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_term_taxonomy` -- LOCK TABLES `wp_term_taxonomy` WRITE; /*!40000 ALTER TABLE `wp_term_taxonomy` DISABLE KEYS */; INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,1); /*!40000 ALTER TABLE `wp_term_taxonomy` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_termmeta` -- DROP TABLE IF EXISTS `wp_termmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; 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_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL, PRIMARY KEY (`meta_id`), KEY `term_id` (`term_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_termmeta` -- LOCK TABLES `wp_termmeta` WRITE; /*!40000 ALTER TABLE `wp_termmeta` DISABLE KEYS */; /*!40000 ALTER TABLE `wp_termmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_terms` -- DROP TABLE IF EXISTS `wp_terms`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_terms` ( `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT 0, PRIMARY KEY (`term_id`), KEY `slug` (`slug`(191)), KEY `name` (`name`(191)) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_terms` -- LOCK TABLES `wp_terms` WRITE; /*!40000 ALTER TABLE `wp_terms` DISABLE KEYS */; INSERT INTO `wp_terms` VALUES (1,'Uncategorised','uncategorised',0); /*!40000 ALTER TABLE `wp_terms` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_usermeta` -- DROP TABLE IF EXISTS `wp_usermeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; 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_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL, 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_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_usermeta` -- LOCK TABLES `wp_usermeta` WRITE; /*!40000 ALTER TABLE `wp_usermeta` DISABLE KEYS */; INSERT INTO `wp_usermeta` VALUES (1,1,'nickname','djonker'),(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:\"a3a05ced4dfefaa7ea79df0370927a613723c665c5b0a51019e591db597d5f16\";a:4:{s:10:\"expiration\";i:1623292540;s:2:\"ip\";s:10:\"172.17.0.1\";s:2:\"ua\";s:68:\"Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0\";s:5:\"login\";i:1623119740;}}'),(17,1,'wp_dashboard_quick_press_last_post_id','4'),(18,1,'community-events-location','a:1:{s:2:\"ip\";s:10:\"172.17.0.0\";}'); /*!40000 ALTER TABLE `wp_usermeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_users` -- DROP TABLE IF EXISTS `wp_users`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_users` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_login` varchar(60) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_pass` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_nicename` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_url` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT 0, `display_name` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', 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_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_users` -- LOCK TABLES `wp_users` WRITE; /*!40000 ALTER TABLE `wp_users` DISABLE KEYS */; INSERT INTO `wp_users` VALUES (1,'djonker','$P$BR9po1c3EaL5xVTIx/4AVywiYNyHpr0','djonker','djonker@student.codam.nl','https://localhost/wordpress','2021-06-08 02:35:34','',0,'djonker'); /*!40000 ALTER TABLE `wp_users` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2021-06-08 4:40:28