We bid goodbye to 2020 in style with the release of WordPress 5.6 and the launch of Learn WordPress. But these weren’t the only exciting updates from WordPress in December. Read on to learn more!
\n\n\n\nThe latest major WordPress release, version 5.6 “Simone”, came out on December 8. The release ships with a new default theme called Twenty Twenty One. It offers a host of features, including:
\n\n\n\nIn addition, WordPress 5.6 is now available in 55 languages. You can find more information about the release in the field guide, and you can update to the latest version directly from your WordPress dashboard or by downloading it directly from WordPress.org. A total of 605 people hailing from 57 different countries contributed to the development of WordPress 5.6. @audrasjb has compiled many more stats like that, showing what a tremendous group effort this was—they’re well worth a read!
\n\n\n\nWant to contribute to upcoming WordPress releases? Join the WordPress #core channel on the Make WordPress Slack and follow the Core team blog to learn the latest on WordPress 5.7, which is slated to be out by March 9, 2021. The Core team hosts weekly chats on Wednesdays at 5 a.m. and 8 p.m. UTC.
\n\n\n\nState of the Word 2020, the annual keynote address delivered by WordPress co-founder Matt Mullenweg, was streamed online for the first time on December 17. It was followed by a live Q&A from community members all across the world. You can find the stream recording on YouTube, Facebook, and Twitter. The State of the Word video and the Q&A session are also available on WordPress.tv.
\n\n\n\nLearn WordPress, a new free, on-demand WordPress learning resource, launched officially on December 15. It offers workshops, lesson plans, quizzes, and courses for anyone interested in publishing with, building for, or contributing to WordPress. WordPress enthusiasts can also participate in discussion groups focused on specific topics to learn with and from each other.
\n\n\n\nWant to participate in Learn WordPress? Here are four ways you can do so! Additionally, contributors have launched a discussion on the future of Learn WordPress—feel free to share your thoughts in the comments. To help promote Learn WordPress, check out the Marketing Team’s materials, which detail a range of fun and creative ways to share this new resource.
\n\n\n\nContributor teams have kicked off the Full Site Editing (FSE) outreach program for anyone who is building or maintaining a WordPress site so that they can give feedback on the upcoming FSE feature that will be part of Gutenberg Phase 2. Your feedback will go a long way in improving FSE user flows. To participate, check out the initial testing call on the Make/Test blog and join the #fse-outreach-experiment Slack channel.
Want to follow updates on the FSE project? Check out this blog post. You can find 2020 updates to the FSE project in the Make/Core blog.
BuddyPress version 7.0 went live on December 9. Its features include:
\n\n\n\nA BuddyPress maintenance release (version 7.1) launched on December 21.
\n\n\n\nWant to provide feedback or suggestions for BuddyPress? Share your comments on the announcement posts for 7.0 or 7.1. If you find a bug, please report it in the support forums.
\n\n\n\nThe Core team launched version 9.5 and 9.6 of Gutenberg last month. Both versions include several improvements to FSE flows, bug fixes, and feature upgrades. Version 9.5 introduces features like full height alignment and support for font sizes in the code block. Version 9.6 includes features like the ability to drag blocks from the inserter and a vertical layout for buttons.
\n\n\n\nWant to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.
\n\n\n\n
Have a story that we should include in the next “Month in WordPress” post? Please submit it using this form.
Learn WordPress is a learning resource providing workshops, quizzes, courses, lesson plans, and discussion groups so that anyone, from beginners to advanced users, can learn to do more with WordPress. Learning how to use, build for, and contribute to WordPress is essential for anyone wanting to dive deeper into the software and its community.
\n\n\n\n \n\n\n\nThis cross-team initiative is part of the WordPress.org network and features content from contributors from the global community. It will be updated weekly and will help connect new and existing WordPress users with the broader community while they learn.
\n\n\n\nOn Learn WordPress you can find a range of material and opportunities to use at the time which works for you.
\n\n\n\nWorkshops are practical, skills-based videos that show viewers how to do new things with WordPress, whether you publish, manage, develop with, or contribute to WordPress. Most workshops include quizzes for you to test your newly gained knowledge.
\n\n\n\nDiscussion groups provide an opportunity for further collaborative learning with participants meeting together to discuss the workshop content – they take place online, either in video calls or Slack and accommodate all time zones.
\n\n\n\nLesson plans are guides for facilitators to use while presenting at events or within educational environments. Facilitators will find learning objectives (telling people what they are going to learn), any prerequisite skills, assets such as screenshots and slide decks, and learning assessments.
\n\n\n\nCourses are a series of interconnected lesson plans to be presented by a facilitator that will strategically focus on defined learning outcomes. Participants can go through these courses individually or as part of a group. After completing the learning, attendees should be able to apply their skills in the real world.
\n\n\n\nIn addition to the wealth of valuable content available on Learn WordPress, the platform provides an opportunity for individuals to learn alongside other community members and become connected with a global network of WordPress users, developers, and contributors.
\n\n\n\nWhy you should use Learn WordPress – videos from our community.
\n\n\n\nLearn WordPress is an open-source platform available for anyone to contribute content in any areas mentioned above. Find out more about how you can get involved with this initiative.
\n\n\n\nTake part in our fun promotion campaigns on social and with your local community.
\n\n\n\nHundreds of people spanning a number of years have contributed to the development of learning materials. Thanks to everyone who worked so hard to make Learn WordPress a reality.
\n\n\n\nParticular thanks to:
\n\n\n\nTraining: @courane01, @azhiyadev, @geheren, @webtechpooja, @jessecowens, @onealtr, @rastaban, @evarlese, @manzwebdesigns
Meta: @coreymckrill, @dufresnesteven, @jonoaldersonwp
Community: @hlashbrooke, @camikaos, @harishanker, @angelasjin, @nao, @courtneypk, @andreamiddleton, @rmarks, @sippis
Marketing: @webcommsat, @oglekler, @lmurillom, @yvettesonneveld, @meher, @nalininonstopnewsuk, @megphillips91, @marks99, @marybaum, @antialiasfactory, @herculespekkas, @chaion07
Design: @melchoyce
For a fuller list of the contributors who have been involved in training and Learn WordPress, visit the initial beta launch post. Thanks to everyone who has been involved to date and will be in the future.
\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9444\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"WordPress 5.6 “Simone”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://wordpress.org/news/2020/12/simone/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 08 Dec 2020 19:46:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a: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:3:\"5.6\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9325\";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:206:\"Meet Simone, our latest and greatest WordPress release. Named for the legendary performer Nina Simone. Fire up a playlist with her best work and read on to discover what WordPress 5.6 has in store for you. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:63925:\"\nMeet Simone, our latest and greatest WordPress release. Named for 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\nWelcome to WordPress 5.6
\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\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\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 specialized 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 color palettes in pastel, all of which conform to AAA standards for contrast. You can also choose your own background color for the theme, and the theme chooses accessibility-conscious text colors for you — automatically!
\n\n\n\nNeed more flexibility than that? You can also choose your own color palette from the color picker.
\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. Customize the patterns to your liking with the copy, images, and colors that fit your story or brand.
\n\n\n\nThanks to the API’s new Application Passwords authorization 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 ( e.g. 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.”
\nThe WordPress 5.6 release comes to you from an all-women and non-binary identifying 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.
\n\n\n\nÖ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, alexstine, allancole, Allie Nimmons, ambienthack, Amit Dudhat, Amol Vhankalas, Amy Kamala, Anand Upadhyay, Anchen le Roux, Anders Norén, André Maneiro, 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, Anyssa Ferreira, 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, Bet Hannon, Beth Soderberg, bgermann, Bhagvan Mangukiya, bhautikvirani, Billy S, Birgir Erlendsson (birgire), Birgit Pauli-Haack, bobbingwide, BoldGrid, Boone Gorges, Boy Witthaya, Brady Vercher, Brandon Kraft, Brandon Payton, Breann McDede, 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, Charalampos Papazoglou, 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, 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 Bajgorić, Enrique Sánchez, epiqueras, Erik Betshammar, erikjandelange, Erin \'Folletto\' Casali, eringoblog, 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, Hong Nga Nguyen, 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, Joel Yoder, joelclimbsthings, 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, Karthik Bhat, 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 Byrne, Laura Nelson, Laxman Prajapati, 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, Marin Atanasov, 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, Neil James (lcyh78), nendeb, net, Netravnen, nicomollet, Nidhi Jain, Niels Lange, Nik Tsekouras, Nikola, Nikolay Bachiyski, njbrown, nlpro, Noah Allen, noahshrader, nourma, 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, tracy apps, 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\n\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:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9325\";s: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:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"State of the Word 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpress.org/news/2020/12/state-of-the-word-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Dec 2020 22:55:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9296\";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:110:\"State of the Word will be streamed on Facebook, YouTube, and Twitter on Thursday, Dec 17th, 2020 at 1600 UTC.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:1225:\"\nState of the Word is an annual keynote address delivered by the project co-founder, Matt Mullenweg. Catch this year’s keynote in the video below!
\n\n\n\nIf this is your first time hearing of this talk, you’re in luck! Check out previous recordings below.
\n\n\n\nNovember 2020 saw several updates to the WordPress 5.6 release. Read on to follow all the latest news from the WordPress world!
\n\n\n\nThe Core team released WordPress 5.6 Beta 3 on Nov. 2, Beta 4 on Nov. 12, release candidate 1 on Nov. 17, and release candidate 2 on Dec. 1. You can test the Beta versions and the release candidates by downloading them from WordPress.org or by using the WordPress Beta Tester plugin. Check out the WordPress 5.6 field guide to understand the features of WordPress 5.6 and learn how you can incorporate them into your websites. WordPress 5.6 will be out by Dec. 9, 2020.
\n\n\n\nBut our work is never done: You can submit feature suggestions for WordPress 5.7 by Dec. 15.
\n\n\n\nWant to contribute to upcoming WordPress releases? Join the WordPress Core dev chats on Wednesdays at 5 a.m. and 8 p.m. UTC in the #core channel on the Make WordPress Slack, and catch up with recaps on the Core team blog. If you would like to help with WordPress 5.6 outreach, contact the WordPress Marketing team on the #marketing channel.
\n\n\n\nContributor teams released Gutenberg Version 9.3 on Nov. 4 and Version 9.4 on Nov. 18. Both versions include several improvements to Full Site Editing (FSE) flows, in addition to bug fixes and feature upgrades. Version 9.3 is the first release that isn’t included entirely in WordPress 5.6; the version automatically enables FSE experiments when a block-based theme is active. Version 9.4 introduces some new features like percentage width for button blocks, block variation transformations, social icon support, and font size support for the list block. You can find out more about the Gutenberg roadmap in the What’s next in Gutenberg blog post.
\n\n\n\nWant to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.
\n\n\n\nWordPress contributor teams are all set to launch Learn WordPress in December. Community members can now watch video workshops to learn about various WordPress topics, participate in discussion groups, and use lesson plans for organizing their own workshops. Contributor teams have launched quizzes and are also working on setting standards for workshops.
Want to contribute to Learn WordPress? You can now submit a workshop application (submissions in languages other than English are welcome!), apply to become a discussion group leader, organize discussions for your local WordPress meetup group, or help fix issues with existing lesson plans.
\n\n\n\nWordPress 5.6 is ready to be translated and is now at hard string freeze. If you would like to contribute, check out these instructions and ensure that your locale is ready for an automated release. The Polyglots team has also kicked off its translator research survey. Please participate in the survey, share the survey link with members of your locale, and help amplify the Facebook, Twitter, and LinkedIn posts about it.
\n\n\n\nWant to help WordPress speak your language? Follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group.
\n\n\n\nHave a story that we should include in the next “Month in WordPress” post? Please submit it here.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9283\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 5.6 Release Candidate 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2020/12/wordpress-5-6-release-candidate-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 01 Dec 2020 22:09:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.6\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9274\";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:388:\"The second release candidate for WordPress 5.6 is here! WordPress 5.6 is slated for release on December 8, 2020, and we need your help to get there—if you haven’t tried 5.6 yet, now is the time! You can test WordPress 5.6 release candidate 2 in two ways: Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” option). Or download the 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2249:\"\nThe second release candidate for WordPress 5.6 is here!
\n\n\n\nWordPress 5.6 is slated for release on December 8, 2020, and we need your help to get there—if you haven’t tried 5.6 yet, now is the time!
\n\n\n\nYou can test WordPress 5.6 release candidate 2 in two ways:
\n\n\n\nThank you to all of the contributors who tested the Beta releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.
\n\n\n\nPlease test your plugins and themes against WordPress 5.6 and update the Tested up to version in the readme file to 5.6. If you find compatibility problems, please be sure to post to the support forums. That way, those can be figured out before the final release.
\n\n\n\nFor a more detailed breakdown of the changes included in WordPress 5.6, check out the WordPress 5.6 beta 1 post. The WordPress 5.6 Field Guide is also out! It’s your source for details on all the major changes.
\n\n\n\nDo you speak a language other than English? Help translate WordPress into more than 100 languages!
\n\n\n\nThink you found a bug? Post it to the Alpha/Beta area in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible bug report you can file one on WordPress Trac. Don’t forget to check the list of known bugs!
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9274\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"WordPress 5.6 Release Candidate\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2020/11/wordpress-5-6-release-candidate/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 17 Nov 2020 22:43: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:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.6\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9258\";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:49:\"WordPress 5.6 Release Candidate is now available!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3349:\"\nThe first release candidate for WordPress 5.6 is now available!
\n\n\n\nThis is an important milestone in the community’s progress toward the final release of WordPress 5.6.
\n\n\n\n“Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.6 is slated for release on December 8, 2020, but we need your help to get there—if you haven’t tried 5.6 yet, now is the time!
\n\n\n\nYou can test the WordPress 5.6 release candidate in two ways:
\n\n\n\nThank you to all of the contributors who tested the Beta releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.
\n\n\n\nThe final release of 2020 continues the annual tradition of a new default theme that is custom built to showcase the new features and functionality of the software. Continued progress on the block editor is especially clear in this release, which brings more blocks to more places, and fewer clicks to implement your layouts.
\n\n\n\nWordPress 5.6 also has lots of refinements to polish the developer experience. To learn more, subscribe to the Make WordPress Core blog and pay special attention to the developer notes tag for updates on those and other changes that could affect your products.
\n\n\n\nPlease test your plugins and themes against WordPress 5.6 and update the Tested up to version in the readme file to 5.6. If you find compatibility problems, please be sure to post to the support forums, so those can be figured out before the final release.
\n\n\n\nThe WordPress 5.6 Field Guide, due very shortly, will give you a more detailed dive into the major changes.
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages! This release also marks the hard string freeze point of the 5.6 release schedule.
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9258\";s: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:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.6 Beta 4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2020/11/wordpress-5-6-beta-4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 12 Nov 2020 23:49:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.6\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9249\";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:363:\"WordPress 5.6 Beta 4 is now available for testing! This software is still in development, so we recommend that you run this version on a test site. You can test the WordPress 5.6 beta in two ways: Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” option). Or download the beta here (zip). The current target for the […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5658:\"\nWordPress 5.6 Beta 4 is now available for testing!
\n\n\n\nThis software is still in development, so we recommend that you run this version on a test site.
\n\n\n\nYou can test the WordPress 5.6 beta in two ways:
\n\n\n\nThe current target for the final release is December 8, 2020. This is just over three weeks away, so your help is needed to ensure this release is tested properly.
\n\n\n\nThank you to all of the contributors that tested the beta 3 development release and provided feedback. Testing for bugs is an important part of polishing each release and a great way to contribute to WordPress.
\n\n\n\nSince beta 3, 42 bugs have been fixed. Here is a summary of a few changes included in beta 4:
\n\n\n\nTo see all of the features for each Gutenberg release in detail, check out the release posts: 8.6, 8.7, 8.8, 8.9, 9.0, 9.1, 9.2, and 9.3.
\n\n\n\nWordPress 5.6 has lots of refinements to the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers’ notes for updates on those and other changes that could affect your products.
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you!
\n\n\n\nIf you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nProps to @tonyamork, @audrasjb for technical notes and @angelasjin, @yvettesonneveld, @cguntur, @cbringmann for final review.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9249\";s: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:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.6 Beta 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2020/11/wordpress-5-6-beta-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 02 Nov 2020 21:23: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:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.6\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9234\";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:379:\"WordPress 5.6 Beta 3 is now available for testing! This software is still in development, so we recommend that you run this version on a test site. You can test the WordPress 5.6 beta in two ways: Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” option). Or download the beta here (zip). The current target for the […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5206:\"\nWordPress 5.6 Beta 3 is now available for testing!
\n\n\n\nThis software is still in development, so we recommend that you run this version on a test site.
\n\n\n\nYou can test the WordPress 5.6 beta in two ways:
\n\n\n\nThe current target for the final release is December 8, 2020. This is just five weeks away, so your help is needed to ensure this release is tested properly.
\n\n\n\nThank you to all of the contributors that tested the beta 2 development release and provided feedback. Testing for bugs is an important part of polishing each release and a great way to contribute to WordPress.
\n\n\n\nSince beta 2, 20 bugs have been fixed. Here is a summary of a few changes included in beta 3:
\n\n\n\nAuthorization
header is working as expected for Application Passwords (see #51638).To see all of the features for each Gutenberg release in detail, check out the release posts: 8.6, 8.7, 8.8, 8.9, 9.0, 9.1, 9.2, and 9.3.
\n\n\n\nWordPress 5.6 has lots of refinements to the developer experience as well. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers’ notes for updates on those and other changes that could affect your products.
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you!
\n\n\n\nIf you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nProps to @hellofromtonya for help and @chanthaboune for final review.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9234\";s: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:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"The Month in WordPress: October 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2020/11/the-month-in-wordpress-october-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 02 Nov 2020 18:14:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9225\";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:329:\"October 2020 was a notable month for WordPress lovers, thanks to the release of several products and updates. Read on to keep up with all the latest news! The 2020 WordPress Annual Survey is out The team published the 2020 WordPress Annual survey — to help those who build WordPress to understand more about our […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Hari Shanker R\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11855:\"\nOctober 2020 was a notable month for WordPress lovers, thanks to the release of several products and updates. Read on to keep up with all the latest news!
\n\n\n\nThe team published the 2020 WordPress Annual survey — to help those who build WordPress to understand more about our software usage and our contributors’ experience. The Annual Survey will be open for at least 6 weeks and is available in French, German, Japanese, Russian, and Spanish. The survey results (once complete) will be posted on WordPress.org/news. The 2019 survey results have also been released and can now be viewed as slides or downloaded in PDF format.
\n\n\n\nThe last week of September and most of October were focused on recruiting and encouraging polyglot contributors to the WordPress translation project. What was originally envisioned as a single-day event lasted 24 days! The Polyglots and Marketing Teams are exploring how future mini-events can be supported to continue building the momentum. Recordings of the live talks and interviews with contributors are available on YouTube. Write-ups from the different events are on the WPTranslationDay website.
\n\n\n\nWant to help WordPress speak your own language? Follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group.
\n\n\n\nThe Core team released WordPress 5.5.3 on Oct. 31, following the release of Version 5.5.2 on Oct. 29. Both releases fix several bugs and security issues with WordPress. You can update to the latest version directly from your WordPress dashboard or download it now from WordPress.org. The team also released WordPress 5.6 Beta 1 on Oct. 20, followed by Beta 2 on Oct. 27. When ready, the final release will include improvements to the editor, auto-updates for major releases, PHP 8 support, and the Twenty Twenty One theme. You can test the Beta versions by downloading them from WordPress.org or using the WordPress Beta Tester plugin.
Want to be involved in the next release? Follow WordPress 5.6 updates on the development cycle and sign-up for the code review/commit office hours. You can help build WordPress Core by following the Core team blog and joining the #core channel in the Making WordPress Slack group. If you would like to help out with WordPress 5.6 outreach, contact the WordPress Marketing team on the #marketing channel.
\n\n\n\nVersion 9.2 of the Gutenberg plugin came out on Oct. 21. This release offers support for video subtitles, the ability to transform selected blocks into the columns block, background patterns in cover blocks, along with several exciting features such as improvements to the widget screen, as well as bug fixes. You can find out more about the Gutenberg roadmap in the What’s next in Gutenberg blog post.
\n\n\n\nWant to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.
\n\n\n\nThe Learn WordPress initiative, which offers WordPress video workshops followed by interactive discussions, is aiming to put out two courses by the end of the year as part of its full launch. The team is working on creating courses and is requesting feedback from community members on the planned list of courses.
Want to contribute to Learn WordPress? You can now submit a workshop application (submissions in non-English languages are welcome), apply to become a discussion group leader, organize discussions for your local WordPress meetup group, or update screenshots on existing lesson plans.
Have a story that we should include in the next “Month in WordPress” post? Please submit it here.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9225\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Mon, 11 Jan 2021 03:33:06 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:25:\"strict-transport-security\";s:11:\"max-age=360\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Tue, 05 Jan 2021 10:55:57 GMT\";s:4:\"link\";s:63:\"WordPress’ Community Team has been discussing the return to in-person events since early December 2020, and has landed on an idea that would allow local meetup organizers to determine readiness using a COVID-19 risk-assessment checklist. This would enable organizers to restart meetups when it is safe for their communities, instead of applying a blanket global policy.
\n\n\n\nCountries like Australia, New Zealand, The Bahamas, Iceland, and Vietnam, are a few examples of locations that are doing a decent job containing the virus. In contrast, the United States logged more than 4,000 coronavirus deaths in a single day this week, pushing the daily average to over 2,700. While the situation remains bleak for many areas of the world, vaccines are rolling out to vulnerable populations, albeit slowly and with a few snags.
\n\n\n\nIn the previous discussion that happened in early December, WordPress lead developer Dion Hulse shared some feedback from Australian organizers who have been eager to restart their meetups.
\n\n\n\n“One of the problems faced in Australia (and probably NZ & Taiwan too) has been the blanket worldwide restrictions companies have put in place,” Hulse said. “Australia/NZ have been lucky, the pandemic has been successfully contained – Australia has seen less than 30k cases this year, and NZ 2k cases. To put that in context, the USA has recorded more (detected) cases in 3 hours today than Australia did all year, and more in 30 minutes than NZ.”
\n\n\n\nHulse said a few Australian meetup groups were denied the go-ahead for restarting because of the global restrictions, which has “led to the abandonment of meetups once again (as online meetups have simply not worked here, as most people can still go out in person, so there’s been no major push from most Australians to the online platforms like elsewhere).”
\n\n\n\nThe Community Team’s proposal for a checklist takes these more unique situations into consideration and allows organizers to move forward in areas where public health measures have adequately curbed the spread of the virus. A few example checklist items include the following:
\n\n\n\nContributor feedback so far includes recommendations for dealing with violations of the guidelines and assessing the need for contact tracing in case meetup attendees are exposed during an event. Cami Kaos recommended that the team share a list of locations that have already been vetted using the checklist and have not met requirements.
\n\n\n\n“My hope is that this would reduce a lot of duplicated time and effort for areas that we already know aren’t yet, by the standards we’re setting, safe,” Kaos said. “It would save time and disappointment for organizers hoping to meet in person and also contributor time and energy for those deputies who will vet the applications to hold in-person events.”
\n\n\n\nSince the virus is mutating and countries are adapting in different ways, the situation can change rapidly, so organizers would need to be prepared to roll back to online events if conditions for safe meetups deteriorate. WordCamps are still out of the question for the time being, but the Community Team is seeking feedback on the proposal by January 15, 2021, including additions to the checklist and recommendations for public health resources that could aid in guiding the process.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 09 Jan 2021 16:50:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"Matt: Autonomous and Beautiful Home Devices\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53404\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"https://ma.tt/2021/01/autonomous-and-beautiful-home-devices/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1532:\"Of all the smart home upgrades I’ve made, replacing all my regular smoke detectors with Nest Protects (Google’s smoke detector) has been the one that I regret the most.
\n\n\n\nI don’t really need a smart smoke detector. It doesn’t need to talk, connect to wifi, and cost hundreds of dollars. I don’t need it integrated with my Google account which is impossible to share, so I need to be personally involved to replace one.
\n\n\n\nBut other smoke detectors are just so unsightly, and the Nest is light years ahead of the competition from a design standpoint.
\n\n\n\nThere’s such an opportunity for something that looks as good as the Nest, but doesn’t require two-factor authentication to replace. I didn’t want to call it dumb but beautiful, so let’s say “autonomous and beautiful” appliances and home devices. I still want it to be smart, but if you’re going to have the risk profile of a device that connects to the internet, it needs to be worth it, like Brilliant, Sonos, smart TVs, or connected cameras.
\n\n\n\nI’m becoming more wary of any hardware that requires an app, just because of the natural decay of non-SaaS and non-open source software. Van Moof bikes are beautiful, but will they still connect well when iOS 24 is out and Bluetooth has been removed from iPhones for security reasons?
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 08 Jan 2021 23:45:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:94:\"WPTavern: Blocked-Based Version of Twenty Twenty-One Nearing Readiness for the Theme Directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=110087\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:233:\"https://wptavern.com/blocked-based-version-of-twenty-twenty-one-nearing-readiness-for-the-theme-directory?utm_source=rss&utm_medium=rss&utm_campaign=blocked-based-version-of-twenty-twenty-one-nearing-readiness-for-the-theme-directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5300:\"Twenty Twenty-One Blocks, now renamed to TT1 Blocks, is inching its way toward the WordPress theme directory. Kjell Reigstad mentioned the prospect in this week’s block-based themes meeting. Contributors to the theme, which is part of the Theme Experiments project, have pushed some much-needed code updates to the repository.
\n\n\n\nTT1 Blocks is the block-based version of the Twenty Twenty-One theme. Its goal is to provide a version of the original theme that works with Full Site Editing (FSE), currently only available through the Gutenberg plugin.
\n\n\n\nFSE needs more testers. And, testers need themes that will enable the site editor in Gutenberg. Currently, there are only two WordPress themes, Q and Block-Based Bosco, in the directory that support the site editor. Armando should join them shortly. If a user attempts to find one via the FSE filter, they will get no results, as pointed out by Gary Taylor in a recent comment. This seems to be an oversight by the theme authors and should be corrected.
\n\n\n\nWith most block-based themes relegated to a few GitHub repositories, it does not bode well if no one can find themes to test the most important set of features coming to WordPress in 2021. Users should be able to easily install an FSE-ready theme today.
\n\n\n\n“It has been brought up that it may be easier for people to test and contribute to full site editing if Twenty Twenty-One blocks was available in the WordPress theme directory,” wrote Themes Team representative Carolina Nymark in a ticket about renaming TT1 Blocks.
\n\n\n\nTT1 Blocks is something that feels more official. While third-party block-based themes are needed, the officialness of something from core contributors gives more users a sense of trust. Plus, it would be easy for someone with .ORG administrator privileges to stick it to the top of the theme directory’s featured page to get more eyes on it. Doing this with a third-party theme would unleash a hoard of developers who want the same treatment for their themes.
\n\n\n\nThe prospect of the theme coming to the directory is something the WordPress project needs.
\n\n\n\nThe volunteers who have been chipping away at this TT1 Blocks have turned a bare-bones theme into something closer to the original Twenty Twenty-One. There are still some leaps remaining to get it to where it needs to be. Much is this rests in the Gutenberg development team’s hands. There are currently over a dozen blockers identified by the Theme Experiments project that need to be resolved in the Gutenberg plugin first.
\n\n\n\nThere are multiple open tickets on the project board for theme developers who are looking for a way to contribute. This is an opportunity to learn more about block-based themes and pay it forward.
\n\n\n\nAt the moment, I am not-so-patiently awaiting the release of TT1 Blocks to the theme directory.
\n\n\n\nThere are days when I wonder if there is a final destination, some light at the end of this never-ending tunnel that leads to block-based themes being the norm. I get overexcited about each new project. I quickly test pull requests and updates on the handful of repositories I am watching, hoping for a glimpse of something spectacular.
\n\n\n\nPart of this excitement is because I designed and developed WordPress themes for around 15 years in some form or fashion. Today, I am no longer in the design and development game. I must live vicariously through the people who are putting untold hours into this grand experiment. I get to tell their stories, which has its own rewards.
\n\n\n\nI also know that this sort of development is a slog. Everyone has big ideas, but the real world calls for slow, steady, and dedicated work. Often it is thankless.
\n\n\n\nWhen I saw the mere mention of TT1 Blocks potentially coming to the theme directory, it added a bit of spark to an otherwise rough few days. I wanted to end this particular week with something hopeful. And, testing out the latest work those volunteers have put into TT1 Blocks has done just that.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 08 Jan 2021 23:12:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:74:\"WPTavern: JetBrains Denies Being Under Investigation for SolarWinds Attack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=110028\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/jetbrains-denies-being-under-investigation-for-solarwinds-attack?utm_source=rss&utm_medium=rss&utm_campaign=jetbrains-denies-being-under-investigation-for-solarwinds-attack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4847:\"JetBrains, makers of Phpstorm, one of the most popular IDEs for PHP developers, has published a statement denying any involvement in the SolarWinds attack, which compromised multiple US federal agencies and private companies. The company stated that it has not been the subject of an official investigation:
\n\n\n\n\n\n\n\nJetBrains has not taken part or been involved in this attack in any way. SolarWinds is one of our customers and uses TeamCity, which is a Continuous Integration and Deployment System, used as part of building software. SolarWinds has not contacted us with any details regarding the breach and the only information we have is what has been made publicly available.
This statement contradicts a recent New York Times article that claimed unspecified officials were investigating the company’s TeamCity continuous integration software as a possible entry point for the attack:
\n\n\n\n\n\n\n\nBy compromising TeamCity, or exploiting gaps in how customers use the tool, cybersecurity experts say the Russian hackers could have inconspicuously planted back doors in an untold number of JetBrains’ clients. Because TeamCity is so widely deployed, experts said, it is imperative to determine whether its software contains a vulnerability, or if attackers exploited TeamCity customers via stolen passwords or gaps in unpatched, outdated software.
The New York Times did not specify which officials and “cybersecurity experts” were the source for this information but claimed that SolarWinds was also investigating the software internally. A previous version of the article referred to JetBrains as “an obscure software company,” which ruffled the feathers of the company’s most ardent customers. SolarWinds told both the Times and The Wall Street Journal that it has not confirmed a definitive link between JetBrains and the breach of its own software.
\n\n\n\nA joint statement from the FBI, the Cybersecurity and Infrastructure Security Agency (CISA), the Office of the Director of National Intelligence (ODNI) and the National Security Agency (NSA) released this week points to Russia as the origin of the attacks:
\n\n\n\n\n\n\n\nThis work indicates that an Advanced Persistent Threat (APT) actor, likely Russian in origin, is responsible for most or all of the recently discovered, ongoing cyber compromises of both government and non-governmental networks. At this time, we believe this was, and continues to be, an intelligence gathering effort. We are taking all necessary steps to understand the full scope of this campaign and respond accordingly.
Phpstorm is widely used among WordPress developers, especially since version 8 added official support for WordPress in 2014. JetBrains users took to Twitter with questions and concerns about claims that the company was under investigation. Today, JetBrains published another update that clarifies its previous statement. It states that the company’s IDEs are standalone tools with no relation to TeamCity and that there is no evidence that any of their servers or tools have been tampered with.
\n\n\n\nJetBrains is organizing an independent security audit of TeamCity and has promised a transparent report of any vulnerabilities found that may have led to a breach.
\n\n\n\n“For over 20 years, one of our pillars has been to be transparent, honest, and truthful with our customers, and nothing hurts us more than seeing unfounded allegations that damage our reputation and instill doubt on our customers,” JetBrains CEO Maxim Shafirov said.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 07 Jan 2021 23:12:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:114:\"WPTavern: Gutenberg 9.7 Improves User Experience, Updates Reusable Blocks, and Brings Page Templates to FSE Themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=110018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:269:\"https://wptavern.com/gutenberg-9-7-improves-user-experience-updates-reusable-blocks-and-brings-page-templates-to-fse-themes?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-9-7-improves-user-experience-updates-reusable-blocks-and-brings-page-templates-to-fse-themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7906:\"Gutenberg 9.7 landed yesterday with several updates and improvements. Users should expect to see changes to the interface for block variations, transforms, and patterns. Reusable blocks are being worked on after what seemed to be a hiatus. Developers can also now add custom page templates to their block-based WordPress themes.
\n\n\n\nThis release had the fewest number of bug fixes I have seen in a while. The development team only pushed eight fixes into the update, which could signal that things were more stable than usual after the 9.6 release a couple of weeks ago.
\n\n\n\nMost of the work in 9.7 dealt with new features and enhancements. As expected, Full Site Editing got its fair share of time. However, even this seemed dialed back a bit for this release. Many of the updates are to the post-editing interface.
\n\n\n\nThe team pushed out several updates to how features work in the editor. Some of them might seem minor but improve the overall editor experience.
\n\n\n\nBlock variations received a welcome enhancement. Variations are when one underlying block is used to create multiple variations of the same block. For example, the Embed block has YouTube, Twitter, and other variations. In past versions, the block inspector in the sidebar and block navigation would show the generic name, icon, and description. However, Gutenberg 9.7 will now show the details for the variation in use.
\n\n\n\nWhen transforming a block, users can see a preview of what the block will look like. This is a small improvement. However, it might save a few headaches when before deciding to transform one block into another.
\n\n\n\nGutenberg 9.6 introduced a drag-and-drop feature for blocks in the inserter. The team has now extended that feature to block patterns. This is just another rung on the ladder for those looking for more drag-and-drop capabilities.
\n\n\n\nIt has been a while since I tested reusable blocks. The feature has seemingly taken a backseat to other, newer features in the past year or so. It never felt much better than an initial prototype. There is still no way to easily manage them unless you know where to look. However, it appears the Gutenberg development team is actively developing this almost-forgotten feature.
\n\n\n\nUsers can expect more in future releases. “Based on these changes, the UI for reusable blocks is most likely going to see some iterations on the upcoming weeks,” wrote Riad Benguella in the announcement post.
\n\n\n\nI ran an initial test to see what the feature looked like in Gutenberg 9.7. After clicking the “Add to reusable blocks” button, the editor did a quick flash. Then, a notification appeared at the bottom of the screen that the reusable block had been created. Because I did not have my block options sidebar panel open at the time, I saw no way to edit the reusable block’s title. My immediate thought was that the team took an already half-baked feature and made it exponentially worse.
\n\n\n\nUpon further digging, I found that users can edit the reusable block’s title in the block options sidebar. However, the team did not stop there. They added several improvements to the feature.
\n\n\n\nReusable blocks are now editable within the post editor itself. Users can drag an image out of the block, for example. The inspector sidebar is available for the inner blocks. Reusable blocks now look and feel like any other part of the editor. Any edits will reflect across all instances of the reusable blocks on the site.
\n\n\n\nThe big difference is in how they are saved.
\n\n\n\nReusable blocks are now a part of the “multi-entity” save system. When clicking the editor’s update button, users will have an option to save the entire post and/or individual reusable blocks.
\n\n\n\nBlock-based themes now support what has been traditionally known as page templates. All post types are technically supported with the feature. However, the team seems to be sticking with the “page” terminology after some discussion.
\n\n\n\nIt took some digging because there is no existing documentation and the original example in the ticket did not reflect the end result of the code that passed. However, I managed to suss out how the feature works. For theme authors who want to test this feature, use the following example code of adding a “contact” template. Place it at the root level of your theme’s experimental-theme.json
file. You will also need to accompany this with a block-templates/contact.html
template in your theme.
\"pageTemplates\": {\n \"contact\": {\n \"title\": \"Contact\",\n \"postTypes\": [\n \"page\"\n ]\n }\n}
\n\n\n\nThis feature does not do anything particularly groundbreaking right now. It merely adds the custom template to the drop-down select on the edit post/page screen. It is the equivalent of the current page template system available to traditional themes.
\n\n\n\nWhile this is a nice development, traditional page templates may not make much sense in the block theming paradigm. There is no way to change the visual output of the page in the editor based on the selected template — users must still view the page on the front end to see the result of its application. The block system is about instant visual feedback. Page templates need to be rethought for the new era.
\n\n\n\n“In terms of UI and integration with the template mode, we can do a lot more than the old select box,” said Benguella, who was the developer behind the pull request. “We can show a preview for templates and offer a modal or something like that for folks to pick from…We’d need some design thinking and explorations there. This PR just sets the technical requirements to make it work.”
\n\n\n\nMuch, but not all, of what page templates were needed for in the past decade can now be replaced by block patterns.
\n\n\n\nIn the long term, I would rather see page templates that behaved more like predesigned block layouts. This is how block templates for custom post types work today. However, that is on the post-type level rather than the level of the individual post.
\n\n\n\nTraditional page templates are dated. Themes rarely offer more than a few. One to remove the sidebar. One to move the sidebar to the left or right. Another to make the page content area wider.
\n\n\n\nWhat is clear is that we need more exploration on what page templates of the future will look like. Are they necessary in the block system? Are there better ways of handling what traditional themes are using them for? How will they work in an interface that needs visual feedback?
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 07 Jan 2021 22:34:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:123:\"WPTavern: All in One SEO Plugin Turns on Automatic Updates without Notifying Users, Removes Functionality in Latest Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109933\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:289:\"https://wptavern.com/all-in-one-seo-plugin-turns-on-automatic-updates-without-notifying-users-removes-functionality-in-latest-release?utm_source=rss&utm_medium=rss&utm_campaign=all-in-one-seo-plugin-turns-on-automatic-updates-without-notifying-users-removes-functionality-in-latest-release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4960:\"Buried in the changelog of a series of minor releases that dropped before the Christmas holiday, All in One SEO plugin users were given the surprise gift of automatic updates. After a seemingly endless run of releases (12 updates during a span of six weeks at the end of 2020), the plugin’s developers decided to change its auto update policy so that it defaults to “on.” The plugin is installed on more than 2 million WordPress sites.
\n\n\n\nVersion 4.0.8, released December 21, 2020, flipped on automatic updates without notifying users of the change. Despite having auto updates turned off for the plugin, many users discovered the change when they were notified by email that their sites had been updated without permission.
\n\n\n\nFrustrated users took to the plugin’s support forums to report the issue and find out how it was possible.
\n\n\n\n“Multiple sites have updated to 4.0.11 without my permission and while all auto updates are disabled,” one user said. “I/we do not want to hear that ‘it shouldn’t happen’ and we are looking into.
\n\n\n\n“Your once reliable plugin has destroyed hundreds of pages of social meta data on multiple sites, broken layout (and this after I fixed the problems and told you last week, I will be disabling all updates).”
\n\n\n\nOthers commented on the issue, citing problems with a previous major release as the source of many bugs that followed.
\n\n\n\n“The rollout of version 4, and auto-updating without any chance to backup first was a blunder by AIOSEO,” plugin user Derek Haines said. “It has cost me hours, days, and now weeks to fix the problems caused.”
\n\n\n\nThe All in One SEO plugin team apologized for the inconvenience users experienced but said they could not reproduce it on their end. The plugin’s settings page has a toggle for auto updates but it is just a wrapper for WordPress’ auto updater.
\n\n\n\n“I just wanted to give you an update and let you know that we’ve decided to remove our own auto-update functionality all together since this issue seems to be happening on a limited amount of websites and we aren’t able to reproduce it on our end,” Arnaud Broes said.
\n\n\n\nThe problem was also discussed in the Advanced WordPress Facebook group.
\n\n\n\n“All In One SEO Pack apparently turned auto updates on, and in a few cases I found sites where those updates failed,” Eric Karkovack reported. “I had no idea they were turned on and in one case a site was inaccessible.”
\n\n\n\nKarkovack noted that there was only a small mention in the changelog, despite the plugin liberally using the dashboard notification UI for sales.
\n\n\n\nWilliam Earnhardt, WordPress core contributor and developer at Bluehost, offered some insight as someone who has worked on core as well as plugins installed on a massive scale.
\n\n\n\n“In my experience if you are weighing the two options, auto-updates prevent significantly more issues and support requests than they create,” Earnhardt said. “So I’m strongly in the camp of enabling them by default, with a mechanism for preventing or disabling for those who prefer (core makes this possible with filters and now with per-plugin UI).
\n\n\n\n“I think when making these decisions, we as developers have to consider what is best for the broadest number of users and be realistic about the type of users we have. If a user is already not updating plugins regularly, it is unlikely they are going to have the awareness to flip a toggle to turn auto-updates on. So opt-in makes them mostly useless.”
\n\n\n\nEarnhardt agreed that notifying users of the change would have been a good idea, but admin notices are already “frequently abused and quite noisy.”
\n\n\n\n“It would likely be missed if not persistent, but really should only show after the update and then go away,” he said. “Is that enough when combined with a note in the changelog? Probably for most, but I’m sure some would disagree.”
\n\n\n\nAs promised nine days ago, All in One SEO’s developers have now removed the functionality from the plugin in its first update of 2021, version 4.0.12 released today. It is noted in the changelog: “Fixed: Completely remove auto updates wrapper to let WordPress handle updates.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 06 Jan 2021 23:47:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:84:\"WPTavern: Liquid Web Acquires The Events Calendar WordPress Plugin From Modern Tribe\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109909\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:213:\"https://wptavern.com/liquid-web-acquires-the-events-calendar-wordpress-plugin-from-modern-tribe?utm_source=rss&utm_medium=rss&utm_campaign=liquid-web-acquires-the-events-calendar-wordpress-plugin-from-modern-tribe\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4092:\"Liquid Web announced today via the iThemes blog that it acquired The Events Calendar from Modern Tribe. The acquisition gives them ownership of the plugin, its suite of event-related plugins, and the team behind it all.
\n\n\n\n“We’ve acquired all the associated plugins, including Event Tickets, etc.,” said Matt Danner, the COO at iThemes. “They identify under the single umbrella of The Events Calendar as a team, so we’ve continued to position the team that way.”
\n\n\n\nAs part of the acquisition, the 50+ employees from The Events Calendar plugin team are now a part of the Liquid Web family. They will continue working on the plugin and its related products. Zach Tirrell announced on The Events Calendar blog that he would remain at the helm and that the team structure was not changing.
\n\n\n\nThe remaining 74 employees of Modern Tribe will continue working on the agency’s other projects, including clients like Microsoft and Harvard University. Reid Peifer, the Creative Director at Modern Tribe, teased potential future projects in his announcement post. “We can’t help but make things, so you may see a few surprises from us in the coming months as well.”
\n\n\n\nThe Events Calendar plugin on WordPress.org currently has over 800,000 active installs with an average rating of 4.4 out of 5 stars. Modern Tribe launched the plugin in 2011 and has continued to build a larger product line and customer base around it over the last decade.
\n\n\n\nFor existing customers, it should be business as usual. Nothing has changed about who is currently developing The Events Calendar. The website is still a separate entity, and billing will remain the same.
\n\n\n\nThe acquisition is mere months after iThemes, owned by Liquid Web, purchased Restrict Content Pro (RCP), a membership plugin. While RCP continues to have an independent site, users can snag it with one of the plugin bundles directly from the iThemes website.
\n\n\n\nHowever, The Events Calendar will be wholly independent of iThemes. Customers hoping to see a similar bundle with The Events Calendar will be out of luck.
\n\n\n\n“The RCP acquisition was done under the iThemes brand,” said Danner. “We brought that team into our team, and the membership product is a key part of how we’re positioning iThemes. The Event Calendar’s acquisition was done under the larger Liquid Web brand. Their team is coming into Liquid Web alongside iThemes as part of the bigger software division. While we definitely think there are future opportunities to collaborate between our teams (which could include bundles of products from both teams), their products are not going to become part of the iThemes product line.”
\n\n\n\nOne of the biggest remaining questions is whether the separate teams will eventually create integrations between The Events Calendar and RCP. There are multiple reasons event organizers might want to restrict content based on memberships, especially when it comes to virtual events. Danner did not give up any specific plans in his response.
\n\n\n\n“We’re very excited to explore all the opportunities to integrate our products,” he said. “I think there are some great opportunities for RCP and TEC to work more closely together, and both customer bases have requested deeper integration between the two. This acquisition was a perfect fit from so many angles. The people, the values of the team, and the products all align with what we’re building at Liquid Web.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 06 Jan 2021 22:21:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"Akismet: Version 4.1.8 of the Akismet WordPress Plugin is Now Available\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"http://blog.akismet.com/?p=2109\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://blog.akismet.com/2021/01/06/version-4-1-8-of-the-akismet-wordpress-plugin-is-now-available/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:667:\"Version 4.1.8 of the Akismet plugin for WordPress is now available. It contains the following changes:
\nTo upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins 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:\"Wed, 06 Jan 2021 17:01:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Christopher Finke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:33:\"Matt: Farnam Street and Postlight\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53384\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"https://ma.tt/2021/01/farnam-street-and-postlight/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2137:\"I recorded two interviews very far apart from each other, but which have surprisingly both come out today. The first is for one of my favorite sites on the web, Farnam Street. I was honored to be episode 100 on their Knowledge Project podcast. Knowledge Project is probably one of the podcasts I’ve listened to the most since it started. Please check out their other guests as well, they really do have the most interesting conversations with the most interesting folks.
\n\n\n\nShane and I cover turnarounds, how environment affects performance, pros and cons of distributed work, uncovering your lacuna, mental models, and patterns of decision making.
\n\n\n\n \n\n\n\nOn a completely different vein, I did a deep geek-out on technology and content management systems with Gina Trapani and Paul Ford, two of my favorite technologists, on the Postlight podcast. We covered a lot of tech history, my thoughts on Chromium and Mozilla’s Gecko engine, structured data, Gutenberg, and a lot more. If you’re a developer or a long-time WordPress community member you’ll enjoy this one, but it might be esoteric or technical if you’re not immersed in this world. Here’s a Spotify embed of the episode:
\n\n\n\n \n\n\n\nIn both we do touch on my idea that, on a long enough timeline, the survival rate for all proprietary software drops to zero. (Hat tip to Fight Club.) Proprietary software is an evolutionary dead end. You can think of open source packages like genetic alleles that have a higher fitness function, and eventually become the fittest organism. The longer I spend watching mega-trends in technology, the more I see that pattern everywhere, from encyclopedias to cryptocurrencies.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Jan 2021 23:51:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:92:\"WPTavern: Block System Will Create More Commercial Opportunities for WordPress Theme Authors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109904\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:229:\"https://wptavern.com/block-system-will-create-more-commercial-opportunities-for-wordpress-theme-authors?utm_source=rss&utm_medium=rss&utm_campaign=block-system-will-create-more-commercial-opportunities-for-wordpress-theme-authors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6978:\"Ten years ago, a potential WordPress theme buyer might stumble upon a site like ThemeForest. The themes on the site would primarily tout the hundreds of shortcodes they included. These shortcodes would allow the user to build anything they wanted with simple BBCode-like brackets around some tag or another.
\n\n\n\nThe practice was not limited to ThemeForest. Nearly every theme development company at the time — and they were sprouting up by the dozens a decade ago — needed to compete in the same arena. Despite all their faults (never mind that no user could reasonably remember hundreds of them), shortcodes topped the list of features.
\n\n\n\nToday, the landscape is much different. In part powered by page builders like Elementor and Beaver Builder, themes are more apt to offer pre-built design options. Gone are the days when users must painstakingly fill their pages with shortcode soup manually. At the click of a button, their theme will automate the design of their homepage for them. The user merely needs to fill in the content. At the click of another button, the user gets a contact or services page. A restaurant owner might get a fully-laid out food menu. A new online shop owner can get a full set of pre-built WooCommerce products by importing their theme’s demo content.
\n\n\n\nCustomizability is the name of the game. This has not really changed over the years, but the methods for getting there have.
\n\n\n\nWhen perusing commercial theme shops today, the common thread is the multitude of demos. These demos showcase the various layouts the user can have if they just fork over the $50 or $60 for access. There are themes with over 500 demos.
\n\n\n\nSome themes market hundreds of templates or dozens of pre-built, one-click website designs. At the end of the day, it is all about making the user’s site look a certain way without the hassle of hours of work.
\n\n\n\nThe problem with traditional theming is that all of these themes are built with non-standard solutions. This is no fault of the theme authors. They had to build or use third-party systems where WordPress had failed. Elementor has standardized this to some degree — many commercial theme shops fully support it, often as the default experience. However, it still only represents a fraction of the market and is not a part of the core platform.
\n\n\n\nWordPress is still catching up to the dream that the premium marketplace has already been capitalizing on.
\n\n\n\nHowever, WordPress can do this better in the long term and level the playing field for many other theme developers. We are on the verge of true one-click solutions from the core platform. It will be a tough run for the next year, but the theme shops that adopt the block system the soonest stand the most to gain.
\n\n\n\nIf you have ever installed themes that offered dozens of header designs, the experience has likely been hit or miss. Most such themes require users to go through dozens of options fields in the customizer or — yikes! — a custom-built options page that looks nothing like the WordPress interface. While there are simpler solutions that some theme authors have created, WordPress has never had a built-in way of allowing users to do this.
\n\n\n\nEnter template parts made out of blocks.
\n\n\n\nThemes Team rep Carolina Nymark showcased just how simple this is with the upcoming site editor. Her Armando theme offers three custom header templates.
\n\n\n\nThe system is far from ready. There are missing features that we will likely not see for a while. For example, there’s currently no way to categorize or otherwise group all the header templates just yet. Users can just as easily replace the header with a footer template.
\n\n\n\nHowever, this is an important step forward. The theme author did not write any complicated PHP or JavaScript. There was no need to build a custom options panel or fields. No third-party system was warranted. The developer created the templates, and they became instantly available through the site-editing interface. The theme author’s responsibility went back to simply designing. The user has access through a standardized interface.
\n\n\n\nIf theme authors want to offer hundreds of switchable templates, they can. If they want to add two or three while upselling the others, they can do that too.
\n\n\n\nNow, expand upon this idea with other types of templates. These can be a footer, sidebar, homepage, or any template. The commercial applications are endless. Theme authors can offer commercial themes or upsells with far less work than ever before.
\n\n\n\nThe possibilities do not end with templates. Block patterns are another viable feature to commercialize. As shown with the Genesis Blocks plugin, its “layout selector” offers various patterns to quickly insert into the post content.
\n\n\n\nGenesis Blocks even offers collections of these patterns that share a similar design aesthetic. In other words, these are essentially pattern categories.
\n\n\n\nThis is an easy path forward for theme authors who are looking to upsell. Build one or two categories of patterns. Periodically bring in new groups of patterns for users who want a fresh look without changing themes.
\n\n\n\nGutenberg Hub already provides hundreds of templates and patterns, filling a void that is currently missing from the theme ecosystem. The site offers convenient solutions, but something is missing: they are not tied into the theme’s design. Forward-thinking theme authors should already be building competing solutions that offer all the same templates and patterns that match their themes.
\n\n\n\nA year or two ago, there was some rumbling about the block editor leading to the death of WordPress theming. Traditional theming will trickle into nonexistence in the coming years. Of course, there will be pockets of holdouts, but the future is about one-click solutions. And, WordPress is setting the stage for all users to have this ability at their fingertips. The theme shops that recognize this the soonest will profit from it the most. Everyone else will be fighting for the scraps they leave behind.
\n\n\n\nIt is not time to abandon traditional theming or forgo page-builder support. However, it is time for themers to begin rolling out block patterns and to start outlining, testing, and building block-based themes.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Jan 2021 22:34:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:57:\"WordPress.org blog: The Month in WordPress: December 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9508\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2021/01/the-month-in-wordpress-december-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11600:\"We bid goodbye to 2020 in style with the release of WordPress 5.6 and the launch of Learn WordPress. But these weren’t the only exciting updates from WordPress in December. Read on to learn more!
\n\n\n\nThe latest major WordPress release, version 5.6 “Simone”, came out on December 8. The release ships with a new default theme called Twenty Twenty One. It offers a host of features, including:
\n\n\n\nIn addition, WordPress 5.6 is now available in 55 languages. You can find more information about the release in the field guide, and you can update to the latest version directly from your WordPress dashboard or by downloading it directly from WordPress.org. A total of 605 people hailing from 57 different countries contributed to the development of WordPress 5.6. @audrasjb has compiled many more stats like that, showing what a tremendous group effort this was—they’re well worth a read!
\n\n\n\nWant to contribute to upcoming WordPress releases? Join the WordPress #core channel on the Make WordPress Slack and follow the Core team blog to learn the latest on WordPress 5.7, which is slated to be out by March 9, 2021. The Core team hosts weekly chats on Wednesdays at 5 a.m. and 8 p.m. UTC.
\n\n\n\nState of the Word 2020, the annual keynote address delivered by WordPress co-founder Matt Mullenweg, was streamed online for the first time on December 17. It was followed by a live Q&A from community members all across the world. You can find the stream recording on YouTube, Facebook, and Twitter. The State of the Word video and the Q&A session are also available on WordPress.tv.
\n\n\n\nLearn WordPress, a new free, on-demand WordPress learning resource, launched officially on December 15. It offers workshops, lesson plans, quizzes, and courses for anyone interested in publishing with, building for, or contributing to WordPress. WordPress enthusiasts can also participate in discussion groups focused on specific topics to learn with and from each other.
\n\n\n\nWant to participate in Learn WordPress? Here are four ways you can do so! Additionally, contributors have launched a discussion on the future of Learn WordPress—feel free to share your thoughts in the comments. To help promote Learn WordPress, check out the Marketing Team’s materials, which detail a range of fun and creative ways to share this new resource.
\n\n\n\nContributor teams have kicked off the Full Site Editing (FSE) outreach program for anyone who is building or maintaining a WordPress site so that they can give feedback on the upcoming FSE feature that will be part of Gutenberg Phase 2. Your feedback will go a long way in improving FSE user flows. To participate, check out the initial testing call on the Make/Test blog and join the #fse-outreach-experiment Slack channel.
Want to follow updates on the FSE project? Check out this blog post. You can find 2020 updates to the FSE project in the Make/Core blog.
BuddyPress version 7.0 went live on December 9. Its features include:
\n\n\n\nA BuddyPress maintenance release (version 7.1) launched on December 21.
\n\n\n\nWant to provide feedback or suggestions for BuddyPress? Share your comments on the announcement posts for 7.0 or 7.1. If you find a bug, please report it in the support forums.
\n\n\n\nThe Core team launched version 9.5 and 9.6 of Gutenberg last month. Both versions include several improvements to FSE flows, bug fixes, and feature upgrades. Version 9.5 introduces features like full height alignment and support for font sizes in the code block. Version 9.6 includes features like the ability to drag blocks from the inserter and a vertical layout for buttons.
\n\n\n\nWant to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.
\n\n\n\n
Have a story that we should include in the next “Month in WordPress” post? Please submit it using this form.
WordPress.com launched a new website building service today with prices starting at $4,900. Automattic has been beta testing the service since the last quarter of 2020. The product announcement invites customers to let WordPress.com’s professional team “translate your vision into a compelling and modern website” but does not specify pricing for more customized websites:
\n\n\n\n\n\n\n\nWhether you need a fast and performant eCommerce store for your products and/or services, a polished website for your professional services firm, or an educational website for your online courses, our experts can build it for you on WordPress.com, the most powerful platform for businesses and enterprises large and small.
Initial reactions from the WordPress developer and freelance community were mixed. Some see the competition as good and others perceived it as a threat to WordPress consultants and small agencies, because a product from WordPress.com carries the full weight of the official WordPress brand.
\n\n\n\n“Whether this succeeds or not there are a lot of folks with a sick stomach today because of it,” WordPress developer Chris Wiegman said.
\n\n\n\nAutomattic stepping into the $5k website market came as a surprise to many, after years of keeping to the enterprise space with its WordPress.com VIP service. (Sometime in 2019 the service started going by “WordPress VIP” without the “.com” appended to it.) Freelancers haven’t had to worry too much about competing against a large company like Automattic when trying to attract clients. It’s also an interesting move because the company seemed stretched thin when it came to maintaining plugins used by VIP clients in 2019, despite seeing “demand for WordPress in the enterprise market like never before,” according to Nick Gernert, head of VIP.
\n\n\n\n“Can’t say I’m surprised by this announcement, but it doesn’t bode well for the community, to be honest,” WordPress consultant Joshua Nelson said. “Freelancers will be hurt the most. A for instance: My custom built sites start at $3k. Once you factor in a designer that $4.9k rate looks very competitive.”
\n\n\n\nIn response to community concerns on Twitter, Automattic CEO Matt Mullenweg said the product is targeted at people who have a difficult time getting started with WordPress.
\n\n\n\n“I would be extremely surprised if this impacts anyone’s consulting business, if you do have a current or potential client leave for it please let me know — it should be all new-to-WP users who wouldn’t have been successful getting started,” Mullenweg said. He also confirmed that the new service was set up for “referring business out” and referenced a previous experiment in 2018 where WordPress.com partnered with Upwork to refer clients for custom development.
\n\n\n\n \n\n\n\nThe product launch lacked this information and some noted the copy was confusing with phrases like “Built by us” and “Our experts can build it for you.”
\n\n\n\nWordPress professionals took to Post Status‘ Slack to discuss the implications of Automattic’s new offering. Mullenweg responded to them, saying he is “100% certain this will drive more up-market consulting in the future” to consultants who handle larger projects and potentially bring more business to plugin and theme developers. He also noted that Bluehost’s full service product is a similar solution and that services like Web.com have been competing in this space for awhile.
\n\n\n\n“Typically these are called DIFM (do it for me) vs DIY (do it yourself),” he said.
\n\n\n\nAutomattic must be witnessing a strong demand for DIFM, as participants in the discussion at Post Status referenced Mullenweg’s comments on the topic during his most recent State of the Word address delivered in December 2020:
\n\n\n\n\n\n\n\nLots of people lost their jobs. Lots of people were looking to supplement their income. This drove an incredible amount of entrepreneurship, so people who were looking for people who knew WordPress. And on the other side of that, normal folks who knew or learned WordPress found that they had a lot to demand for their work, so they were able to supplement or replace their income, essentially for folks who have a do it for me mentality, so someone who is looking for someone else to build a website. It’s never been a better time to learn and invest in improving your WordPress skills.
The idea behind this product is to help those who get stuck with WordPress before they turn to competitors that market website creation to beginners. It indicates that WordPress still has a long road ahead before it is truly an approachable tool for beginners embarking on their first site building experience.
\n\n\n\nAutomattic has not published a pricing structure for the features included in a basic $4900 website. Based on images on the landing page, the sites do not seem extensively customized beyond what existing themes offer. It seems like more of a website setup service and does not explicitly promise custom development.
\n\n\n\nWhen asked how agencies can apply to be put into the pipeline for referrals from WordPress.com’s new service, Mullenweg indicated that the product is still in the experimental stage.
\n\n\n\n“It’s unclear if anyone wants this yet, so for this experiment don’t have that yet,” Mullenweg said. “If it works then definitely we will try to open it up.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Jan 2021 04:40:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:47:\"WPTavern: 2021: Reshaping the Tavern Experience\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109489\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:137:\"https://wptavern.com/2021-reshaping-the-tavern-experience?utm_source=rss&utm_medium=rss&utm_campaign=2021-reshaping-the-tavern-experience\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4025:\"Resolutions. Goals. Guidelines for the year ahead. Call them what you want. Not everyone takes part, but I am a firm believer in having a vision for the coming months. That vision can be malleable, flowing with the changes of time, yielding to new ideas as they are birthed. However, some large, beaming guideposts help when setting foot into the wild of a new year.
\n\n\n\nOur team at WP Tavern has gotten a bit of a breather over the holidays. We have an exciting project we are just getting off the ground. We set some things in motion months ago. Now, it is time to push forward.
\n\n\n\nWithout going into all of the details, which are currently in flux, the following are the big goals for the site in 2021.
\n\n\n\nThe biggest goal of 2021 is to add a fresh coat of paint to the website. Going hand in hand with that goal is to launch this new design 100% on blocks. To effectively write about WordPress’s upcoming changes, we need to be ahead of the game. That means living a bit on the bleeding edge, running a block-based theme, and testing the site editor. It means sharing what we love and airing our frustrations.
\n\n\n\nChanging designs is not simply about slapping on some fresh colors. Design is about functionality. At the center of such a change is providing more tools for engagement.
\n\n\n\nWe are thinking over multiple ideas about what this might look like, and we have a generous third-party team standing by to help us implement much of this. Some of those ideas are things like showing the top comments and trending forum topics. Feedback from our readers is more than welcome in this regard. Ultimately, this is the part of the Tavern experience that belongs to you.
\n\n\n\nThe keen-eyed among you may have noticed I slipped in something about forum topics in the preceding paragraph. That was no accident. The return of the Tavern forums is a distinct possibility in 2021. There are many considerations we must make before going down this road around how it is moderated. The goal would be to provide an inviting atmosphere where people could freely talk about our beloved content management system. Again, this would be a feature of the site that is primarily about you.
\n\n\n\nWhile many of you are avid readers of our content, we know some of you have asked us to bring back a podcast in some form. Some of you want to listen to WordPress-related news on your drive to work or while you unwind at the end of a busy day.
\n\n\n\nWe heard you loud and clear.
\n\n\n\nOur team is actively pursuing adding a podcast. This is a project that we have been working on for a while now. It is something we genuinely want to happen.
\n\n\n\nBefore exploring this project, I had no idea of the amount of work necessary for producing a professional podcast. If you had put me behind the mic a few months ago, I would just be shooting from the hip, hoping to hit a target, any target. I have a newfound respect for anyone who produces a podcast today.
\n\n\n\nIf we get a new podcast off the ground in 2021, it will be a professionally-produced show. The goal is to have planned topics and guests representative of the diversity of the WordPress community. I am excited about the possibility.
\n\n\n\nA new design and potential podcast are big-ticket items. They are not features we can launch overnight. When we do them, we want to do them right.
\n\n\n\nThere are other items on the checklist we will likely get to throughout the year too. But, this is a point in the year where we should sit back and listen. Are there things you want to see changed about the Tavern experience? Are there topics we missed last year that you want to see us cover more?
\n\n\n\nAs always, our team looks forward to bringing you our regular news, reviews, and opinions throughout the year. Stay tuned in for more.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 04 Jan 2021 21:36:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:30:\"Matt: What’s In My Bag, 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53341\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://ma.tt/2021/01/whats-in-my-bag-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:15521:\"Instead of sharing what’s in my backpack this year, I want to share the apps and pandemic purchases that were meaningful to me, along with a few words on each. Something I haven’t shared with you yet on this blog is… I went down a #vanlife rabbit hole and ended up camping and working remotely a decent chunk of the year. I learned a ton and feel much more resilient. So this is a phoneful and truckful update of my year.
\n\n\n\nFirst I’ll start with apps, these all link to Apple’s app store but almost all have Android equivalents that I also use:
\n\n\n\nWhen on road trips I found Android Auto running off the Pixel 5 much more reliable than CarPlay, which would frequently freeze up on me. Things have improved with iOS 14, but I still always use the Pixel when I’m on a longer drive.
\n\n\n\nI also have been living with my Mom since July, including her two cats and new Coton du Tulear puppy. Pets are humbling! It’s been great to learn how to support them best, as I last lived with animals when I was in high school and wasn’t that conscious of the responsibility then.
\n\n\n\nAmazon says I made over 850 orders this year, more than double from any previous year. Here are the non-tech purchases that ended up having a big impact on me:
\n\n\n\nClothing and wearables, like much of the world I trended toward comfort and away from normal shoes and socks:
\n\n\n\nElectronics:
\n\n\n\nThere you have it. As always, if you’ve tried something here and found an alternative that’s better, let me know in the comments!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 03 Jan 2021 04:37:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:39:\"WPTavern: 2020: Step Away From the Fire\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109487\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://wptavern.com/2020-step-away-from-the-fire?utm_source=rss&utm_medium=rss&utm_campaign=2020-step-away-from-the-fire\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11328:\"If there was a common theme that held humanity together in 2020, it was that most of us agreed that the year was nothing short of a dumpster fire. That and sweatpants.
\n\n\n\nAs people learned to cope with a new reality in the Covid-19 era, the WordPress community has been a beacon of hope. When other industries needed to learn how to work remotely, we were already ahead of the pack and willing to help. As people dealt with the stress of not having meetups in person, the WordPress community thrived with online events.
\n\n\n\nThe early year was tough. From toilet paper shortages to being unable to work from a favorite coffee shop, the pandemic took its toll.
\n\n\n\nHowever, we have learned to cope throughout the year. We used new ways to communicate from a distance. Created new circles of friends. Found extra time for long-forgotten hobbies online and off.
\n\n\n\nWe continued to create art, which is the thing that makes our species so undeniably unique.
\n\n\n\nMaybe it is all the lessons we have learned through the past several months. Perhaps it is that a new year is upon us. The winds of change feel like they are gently nudging us forward.
\n\n\n\nOver the past couple of months, I have noticed a new calmness. A new hopefulness. A feeling that we will continue to rise above any challenges that come our way. While death and illness are still a part of our daily reality, we must continue to lean on the people within communities like WordPress for support. We will continue marching ahead together.
\n\n\n\nI always like to take stock of the past year. This helps keep me grounded and remain optimistic about the future. The following is a look back at 2020 for WP Tavern and WordPress.
\n\n\n\nWe have had a solid year of publishing here at the Tavern. Our team, including guest authors, wrote 401 posts. In 2019, we knocked out 382. Next year, I expect that figure to increase.
\n\n\n\nOur word count average soared. This year, we averaged 790 words per post. In 2019, that number was 589. While word count is not a testament to quality writing, we did have opportunities to dive deeper into topics than before. In total, we wrote over 315,000 words. That is about 80,000 words shy of Brandon Sanderson’s The Way of Kings. You could say that we wrote enough to fill an epic fantasy novel.
\n\n\n\n“Likes” were up this year too. We went from an average of 7.0 likes per post in 2019 to 8.7 in 2020.
\n\n\n\nFor comments, it is hard to gauge. The WordPress.com Stats feature does not seem to be accurately tracking our comment counts. The figure is nowhere close to correct. By my rough estimate (counting in hundreds), we have at least twice as many published comments as the data shows.
\n\n\n\nThere were a few days scattered throughout the year in which we came within a hair’s breadth of surpassing the site’s all-time daily view count. But, alas, we fell just shy of the mark. Maybe next year.
\n\n\n\nThe following is a list of the 10 most-viewed posts published this year. They are not necessarily representative of our best work. However, they do represent what folks were reading. Everything beyond this was pretty close in terms of stats.
\n\n\n\nFor some reason, Sarah’s piece on adding subscript and superscript characters from 2014 always sneaks its way into the most-viewed posts of the year. It was technically #6 on the list, but it wasn’t published in 2020.
\n\n\n\nIt was the year that saw the rise of online-only WordCamps. What started with WordCamp Asia canceling its inaugural event in February ended with Matt Mullenweg giving the annual State of the Word virtually, a first. WordCamp Europe took its massive event online for 2020 while WordCamp U.S. canceled its planned virtual get-together after months of pandemic stress and online event fatigue.
\n\n\n\nWe saw the community rise up and tackle problems from the beginning. Companies like Wordfence, Yoast, and GoDaddy provided help for those who were not refunded travel expenses after cancellations. At the end of the day, that is what the WordPress community is all about: people helping other people.
\n\n\n\nWordPress kept chugging along, despite the stressful year. The big highlights were three major releases of the software:
\n\n\n\n\n\n\n\nWordPress also turned 17 this year. Its step into adulthood next year should be an adventure.
\n\n\n\nRather than focusing too much on the work that Sarah and I have put into the Tavern this year, I want to say thank you to our contributing writers. They managed to fill some gaps when we were unable to throughout the past 12 months. They have added viewpoints outside of our own, enriching the content that our site offers. If anything, I want to see further contributions from a wider range of the WordPress community in the future.
\n\n\n\nI do not typically like to play favorites with our guest writers, but Francesca Marano’s piece titled A Non-Technical Release Lead’s Journey to Becoming a Mentor for WordPress Core Development was one of my favorite reads of the year. Her backstory is a good intro to the article. Her depth of knowledge and insight into the room where it happens makes it a must-read for anyone unfamiliar with how WordPress gets made.
\n\n\n\nChris Maiorana’s WordPress University Was Always Online is a reminder that the education we need to excel in the online business market is but at our fingertips. It also touches on how the pandemic has allowed more people to realize that the traditional college experience is not the only path forward. It is a great piece that forces us to explore alternatives. And, these alternatives have always been available in the WordPress ecosystem.
\n\n\n\nMaiorana’s piece on the State of the Meetup Under Lockdown explores how the virtual realm has changed meetups. Bringing Back Blogs in the Age of Social Media Censorship is a look into how blogs are the answer in the age of censorship, even when we disagree with a person’s position on a subject.
\n\n\n\nOn the technical end of things, Jonathan Bossenger wrote an in-depth piece for Getting Your WordPress Plugins and Themes Ready for PHP 8. He goes through everything that developers need to know to get their projects updated. The article also provides tools and resources to make things easier.
\n\n\n\nWhile the year might not have been ideal in many ways, there were some great moments. As I reflect upon the events of the last 12 months, I do not see a complete dumpster fire. There was a lot of good that came out of it. The world has changed in some large ways. Our societies have undergone some subtle reshaping. I do not know what 2021 holds, but I remain optimistic.
\n\n\n\nI look forward to another year covering the events surrounding WordPress. I hope you continue down this journey with the WP Tavern team.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 31 Dec 2020 22:44:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:43:\"Matt: Jack Dorsey and Running Two Companies\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53328\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"https://ma.tt/2020/12/running-two-companies/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1808:\"I had the pleasure of interviewing Jack Dorsey for the Distributed podcast, a conversation that ended up going a bit deeper and longer than previous episodes.
\n\n\n\nIn preparation for the interview I kept coming across people critical about the fact that Jack is the CEO of two companies simultaneously, Twitter and Square, each having over 5,000 employees.
\n\n\n\nI think what people miss is that at that scale, running a company is not that different from running a large division of a company. No one asks Jeff Bezos how he’s CEO of both a retail company and a cloud computing one (AWS), or Tim Cook how he’s CEO of a hardware business and a services business, and of course with both of those examples the breadth of what the companies cover is much wider. Also as an added benefit, shareholders can choose to invest in Square and Twitter together or not.
\n\n\n\nAll of that said, I think having a CEO-level seat at two of the most influential technology companies today does allow for accelerated learning, as organizational experiments will naturally happen at each company and then the best practice can be shared to the other. Jack wasn’t aware how much peer executives at each company meet with each other to share learnings, but that seems like an obvious win.
\n\n\n\nReaders of this blog will especially appreciate how much we talked about open source and cryptocurrencies, and his view on the three things he’s responsible for as CEO. Give it a listen and let me know what you think.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 31 Dec 2020 03:18:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WPTavern: Understanding the Query Block and Its Importance in Site Editing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109593\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/understanding-the-query-block-and-its-importance-in-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=understanding-the-query-block-and-its-importance-in-site-editing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5285:\"\n\n\n\nI really don’t understand this Query block even though it’s been mentioned in several Tavern posts. My eyes seem to gloss over when reading about it – ha!
Is it important that regular WordPress users understand this block, or is it really a block for developers?
I have given the Query block a lot of attention as of late. On occasion, I may have even called it one of the largest hurdles the Gutenberg development team has needed to jump before block-based themes become a reality. However, the “query” WordPress term is not something all users or Tavern readers are familiar with. It is a concept as old as WordPress and generally something that only developers needed to familiarize themselves with. When Full Site Editing lands in WordPress, the new block will expose the Query to far more users as part of the site editor interface.
\n\n\n\nIt is a block that is currently a part of the Gutenberg plugin but not WordPress core. However, at some point in 2021, more and more end-users and developers will be working with it.
\n\n\n\nIn WordPress terminology, we are really talking about two things, the Query and the Loop. The Query is defined by a set of arguments or options that determine what posts to display. The Loop is the part of the machine that “loops” through the queried posts and displays them, one after another. The Query asks for posts; the Loop cycles through them.
\n\n\n\nTraditionally, theme authors were responsible for adding the Loop code to their templates, which used the global Query that WordPress supplied. Themes could also create custom queries, such as adding a posts list widget, categorized homepage post sections, or anything. And, “posts” can be anything from normal blog posts to WooCommerce products to the latest topics from the bbPress plugin.
\n\n\n\nThe Query may be one of the single most important aspects of WordPress. In essence, it is the engine behind displaying the content of every page on the site. Without it, all WordPress sites would simply be a header and a footer.
\n\n\n\nThe Gutenberg plugin provides two blocks for the Query:
\n\n\n\nCurrently, users can select between four fairly standard variations when first adding the Query block. They are combinations of the post featured image, title, date, and excerpt.
\n\n\n\nThese can be further customized via the block options panel in the sidebar. Users can also find “view” options in the toolbar for selecting between List and Grid views. The List view is the traditional list of posts flowing vertically down the page. The Grid view displays posts in two to six columns.
\n\n\n\nThe Query block has a basic set of options for which post types to display and how to order them. It has filters for categories, tags, authors, and keywords. The block is not as robust as what is possible with code yet. It is missing some basic options like a post number limit and nearly all of the more advanced parameters. However, it is a promising starting point.
\n\n\n\nThe more exciting aspects of this feature for end-users may not be the Query block at all. It is customizing the blocks that go inside, which display things like the featured image, post title, and more.
\n\n\n\nAs a former theme author, I cannot count the number of times users have asked me about customizing some aspect of the posts layout. Having them dive into code to make minor changes, such as removing the post author name or displaying the category in a different place, was not an ideal experience. The site editor will put this power directly into each user’s hands.
\n\n\n\nThe comment by Marcus was on the Tavern’s post covering Gutenberg 9.6. The latest version of the plugin introduced global query inheritance for the Query block. This means that theme authors can now replicate the content layer in block-based themes. Previously, pages like archives and search results would simply display the latest posts when a theme used the Query block. Now, each of those pages can display the correct posts.
\n\n\n\nHowever, the Query block is so much more than that. In the hands of users, it can be a powerful tool for creating custom output on a homepage — think newspaper-style categorized sections. Users can also create post lists in a sidebar, such as the latest forum replies or products. Theme authors can offer templates or block patterns with unique designs or as starting points for end-users to modify. There is no shortage of possibilities.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 30 Dec 2020 23:05:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:158:\"WPTavern: GitHub’s 2020 State of the Octoverse Report Highlights: Developers are Working More Hours but Turning to Open Source Projects for Creative Outlets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109613\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:353:\"https://wptavern.com/githubs-2020-state-of-the-octoverse-report-highlights-developers-are-working-more-hours-but-turning-to-open-source-projects-for-creative-outlets?utm_source=rss&utm_medium=rss&utm_campaign=githubs-2020-state-of-the-octoverse-report-highlights-developers-are-working-more-hours-but-turning-to-open-source-projects-for-creative-outlets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3644:\"GitHub has published its annual Octoverse report for 2020. The code hosting platform currently serves more than 56 million developers who created 60+ million new repositories this past year. The volume of work pumping through GitHub’s pipes and its preeminence as the world’s largest developer platform gives the company access to a trove of data on how people have been working during the pandemic.
\n\n\n\nThe Productivity report shows that developers have been putting in longer hours as compared to the previous year. It includes data on what time of day people seem to be more productive, as well as minute changes in the volume of work across various time zones and countries with different COVID-19 responses. The graph below tracks the US Pacific Time Zone, showing a spike in the push window and work volume beginning in mid-March with lockdowns. The volume of work remained consistently higher than the previous year.
\n\n\n\nGitHub recorded 35% more repositories created than last year and 7.5 hours faster pull request merge times in teams’ most productive and collaborative weeks.
\n\n\n\nDevelopers seem to be getting more done and GitHub attributes this to people using automation to accelerate their work, improved development practices, and the flexibility of blurring the lines between work and life. The report also cautions that this high volume of work may not be sustainable long-term should be tempered with regular breaks and conscious energy management practices.
\n\n\n\nThis collection of reports also highlights a few trends in the wider open source community. Alongside a general jump in work volume, GitHub tracked an increase in open source activity on weekends and holidays, at the same time that Enterprise developer activity dropped. Open source project creation is also up by 25% year over year since April 2020.
\n\n\n\nThe data suggests that even when developers conclude their regular work, they are turning to open source projects for creative outlets. These projects often provide meaningful connections and community while the world is stuck at home.
\n\n\n\nBased on these findings, GitHub recommends that organizations recognize the importance open source projects hold for employee wellbeing and enrichment when they are contributing outside of work.
\n\n\n\nThe State of the Octoverse also includes reports on Community and Security. GitHub found that 17% of the vulnerabilities hosted on its platform were explicitly malicious but triggered just 0.2% of alerts. The remaining 83% of vulnerabilities were the result of mistakes. The company found that vulnerabilities are fixed 1.4x faster when repositories are set up to automatically generate a pull request when a patch is available.
\n\n\n\nIn 2020, the average time for vulnerabilities to go undetected before being identified is four years for GitHub-hosted repositories. On average, it takes 4.4 weeks for the community to code and release a fix, and 10 weeks to alert the community on the availability of a security update. Once notified, users generally apply the update within one week.
\n\n\n\nGitHub reports that its community is becoming more diverse as those who identify as developers have decreased from 60% in 2016 to 54% in 2020. Profiles related to education are growing (up from 17% in 2016 to 23% in 2020), followed by users working in data. The platform is becoming more approachable for collaborators who do not come from a development background.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 30 Dec 2020 07:08:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:94:\"WPTavern: Armando WordPress Theme Provides Insight Into the Current State of Full Site Editing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109503\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:233:\"https://wptavern.com/armando-wordpress-theme-provides-insight-into-the-current-state-of-full-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=armando-wordpress-theme-provides-insight-into-the-current-state-of-full-site-editing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5271:\"As we inch closer to a year in which WordPress’s primary focus will be on Full Site Editing, it is fortunate timing that Themes Team representative Carolina Nymark publicly announced her latest theme, Armando. It is a blogging theme that makes use of the latest features from the Gutenberg plugin.
\n\n\n\nThe theme is currently awaiting review for the WordPress theme directory. It is also available via GitHub.
\n\n\n\nThe news of Armando came moments after Nymark announced a redesign of her Full Site Editing website. The site is a resource for WordPress users and developers to learn more about upcoming features. It is built entirely out of blocks. It is also one of the few sites in the wild running a block-based theme in production.
\n\n\n\nArmando is one of the better themes for testing Full Site Editing. This should come as no surprise. Nymark is a veteran of the Themes Team. She tends to cover all the bases and has done so with this theme. There are even notes in the code where she intends to change things as site editing improves.
\n\n\n\nThe theme is a solid starting point for theme authors who have yet to dip their toes into block-based theme development. It is also usable enough for end-users who want to experience the current state of Full Site Editing.
\n\n\n\nThe theme does not have a particular artistic flair. It is simple. It is a basic blogging theme that showcases each element the Gutenberg team has covered thus far in its journey toward the new block-based design system.
\n\n\n\nArmando also uncovers some of the current problems with the system. As Nymark noted in her stylesheet, “Date and categories are all block elements, we need to adjust them to align them better next to each other.” On the front end, the theme’s CSS adjusts these block-level elements to correctly line up with each other. However, as seen in the site editor view, they are separated as blocks. Post metadata like the author, date, and category often need to be inline. This choice for aligning basic elements of theme design also needs to exist in the site editor. That is if we ever want theme authors to adopt it. And, we haven’t even gotten to the complicated stuff yet.
\n\n\n\nArmando is one of the first block-based themes I have seen to include a 404 template. This is important because it is one reason the site editor needs to exist in WordPress. Throughout all of the platform’s history, there was no standard way for users to edit their 404 page, which is the page visitors see when they travel to an invalid URL on a site.
\n\n\n\nLanding on a 404 page on most WordPress sites is one of the worst user experiences a site visitor can have on the web. Traditionally, themes might have added some unhelpful text, a search box, and maybe a list of recent posts. But, most users had no control over it unless they directly edited their theme’s code. They could not add a bit of pizzazz, personalized messages, or more meaningful directions for the visitor who stumbled upon the page through no fault of their own. Some themes have provided workarounds for this over the years. Such solutions have included allowing users to assign a private page or adding customizer options. However, changing themes meant losing that 404-page customization because it was a non-standard solution.
\n\n\n\nFull Site Editing changes that. Users will have direct access to creating a custom 404 page that best suits their site. It is nice that the Armando theme already includes a template to start from.
\n\n\n\nThe Armando theme also includes three different header templates for users to switch between. This could offer some insight into how theme authors may tackle design choices in the future. Traditional themes often have numerous checkboxes, input fields, and dropdowns for changing such design elements. Selectable template parts could be the alternative.
\n\n\n\nI lean more toward seeing theme authors using block patterns rather than templates for this. However, WordPress needs to add a method for designating patterns on specific editing screens (e.g., post editor vs. site editor). In the long run, the patterns UI feels like it will be a better place. That is assuming it ever receives an expanded view or overlay option. There may be solutions where patterns and template parts merge as well.
\n\n\n\nEither way, this type of experimentation is what we need to see in the WordPress theme development world at the moment. I welcome more of it.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Dec 2020 22:37:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:64:\"WPTavern: AMP Under Fire in New Antitrust Lawsuit Against Google\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109265\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:173:\"https://wptavern.com/amp-under-fire-in-new-antitrust-lawsuit-against-google?utm_source=rss&utm_medium=rss&utm_campaign=amp-under-fire-in-new-antitrust-lawsuit-against-google\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6515:\"AMP (Accelerated Mobile Pages), an open source initiative that originated with Google, is coming under greater scrutiny at the tail end of 2020, as the company is facing a rash of antitrust lawsuits beginning in October. The second suit is the one most pertinent to the AMP project. (A third suit brought by 38 state attorneys general alleges that Google is operating an illegal monopoly for online search and search advertising.)
\n\n\n\nThe second suit is led by Texas Attorney General Ken Paxton and nine other state attorneys general. It alleges that AMP was created for the purpose of pushing publishers away from “header bidding,” an advertising mechanism that allows sites to route their ad inventory through several ad exchanges and sell the space to the highest bidder. Header bidding requires JavaScript and therefore doesn’t play well with AMP.
\n\n\n\nThe complaint claims that “Google’s program secretly let its own
exchange win, even when another exchange submitted a higher bid.” It also alleges that “Google ad server employees met with AMP employees to strategize about using AMP to impede header bidding, and how much pressure publishers and advertisers would tolerate:”
\n\n\n\nFirst, Google restricted the code to prohibit publishers from routing their bids to or sharing their user data with more than a few exchanges a time, which limited AMP compatibility with header bidding. At the same time, Google made AMP fully compatible with routing to exchanges through Google. Google also designed AMP to force publishers to route rival exchange bids through Google’s ad server so that Google could continue to peek at rivals’ bids and trade on inside information. Third, Google designed AMP so that users loading AMP pages would make direct communication with Google servers, rather than publishers’ servers. This enabled Google’s access to publishers’ inside and non-public user data. AMP pages also limit the number of ads on a page, the types of ads publishers can sell, as well as enriched content that publishers can have on their pages.
There are many more claims about collusion with Facebook and other anti-competitive practices, but the section regarding AMP may be of particular interest to publishers who are considering implementing it:
\n\n\n\n\n\n\n\nGoogle falsely told publishers that adopting AMP would enhance load times, but Google employees knew that AMP only improves the [redacted] and AMP pages can actually [redacted] [redacted] [redacted]. In other words, the ostensible benefits of faster load times for cached AMP version of webpages were not true for publishers that designed their web pages for speed. Some publishers did not adopt AMP because they knew their pages actually loaded faster than AMP pages.
Google also [redacted] of non-AMP ads by giving them artificial one second delays in order to give Google AMP a [redacted] [redacted] slows down header bidding, which Google uses to turn around and denigrate header bidding for being too slow.
The complaint references internal documents that demonstrate how AMP is an inferior product when compared to the options previously available to publishers:
\n\n\n\n\n\n\n\nGoogle gave publishers a Faustian bargain: (1) publishers could lose more money by using header bidding because Google Search would suppress their search rankings and send traffic to competing AMP-compatible publishers; or (2) publishers could lose less money by using AMP pages and forgoing exchange competition in header bidding. Either option was far inferior to the options available to publishers before AMP was introduced. Just how inferior? [redacted] [redacted] [redacted] according to internal Google documents.
Just 48 hours after this lawsuit was filed, AMP Advisory Committee member Terence Eden resigned from his position as a non-corporate representative.
\n\n\n\nThe goal of the AMP AC is to “Make AMP a great web citizen,” but Eden declined to nominate a replacement candidate, because he is concerned that “Google has limited interest in that goal.”
\n\n\n\n“Google’s thesis is that the mobile-web is dying and people prefer to use apps – therefore making the web faster and more app-like will retain users,” Eden wrote. “Google doesn’t publish data about this, so I can’t directly criticize their motives. But I do not think AMP, in its current implementation, helps make the web better.
\n\n\n\n“I remain convinced that AMP is poorly implemented, hostile to the interests of both users and publishers, and a proprietary and unnecessary incursion into the open web.”
\n\n\n\nIn a follow-up email to The Register, Eden said, “I don’t know what Google’s motives are. But AMP has not been responsive to the needs of users, publishers, or the web community. We need an open, standards based approach to the web.”
\n\n\n\nWhere will AMP go in 2021? Publishers have already invested a lot of resources in order to comply with its proprietary subset of HTML. Smaller sites often lack the resources to support AMP, which may be one reason why Google began investing heavily in developing WordPress plugins that make its products easier to use. More than 500,000 WordPress site are now using the official AMP plugin.
\n\n\n\nGoogle has spent years clawing for greater AMP adoption, despite widespread criticism that the project is a threat to the open web. Every last bit of that effort is now in jeopardy if the complaints in the antitrust lawsuits and their supporting documents are found to be true.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Dec 2020 05:43:57 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:84:\"WPTavern: Navigate the Content Canvas With the Block Editor Outline WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109480\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:213:\"https://wptavern.com/navigate-the-content-canvas-with-the-block-editor-outline-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=navigate-the-content-canvas-with-the-block-editor-outline-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4173:\"Last week, Kalimah Apps released its Editor Block Outline plugin to the WordPress plugin repository. The idea is simple. The plugin adds a bordered outline to each block in the document along with their associated labels. For some users, this will help them navigate more complex layouts.
\n\n\n\nThere is little information available about Kalimah Apps through the usual WordPress-related channels. However, this is its second plugin in the directory. Its first plugin, which has not been updated in four years, was a massive library of over 40 shortcodes, 1,000s of icons, and dozens of animations. Editor Block Outline is much more scaled back and lean.
\n\n\n\nThe plugin adds a new sidebar panel to the editor. Its icon, located in the upper right of the screen, looks like a picture frame. It has several options to allow users to personalize the experience, such as what contexts to show the outline and whether to show the block name. The latter option is sometimes best disabled when inserting blocks with many inner blocks. Otherwise, the interface may look a bit cluttered.
\n\n\n\nUsers can also select an outline color, border style, and opacity. I recommend knocking opacity down below 50% for more of a guideline look, something that is visible but does not feel like it is a part of the content.
\n\n\n\nAll of the settings are stored as user metadata. Using this data storage method means that each user can decide how they want to use this plugin. Or, they can even disable it altogether. Because it is stored this way, settings will carry over from one post to the next.
\n\n\n\n“Do you want to know the feeling of driving while drunk, or to move around with blinders on? Then use Gutenberg without this plugin!!!” That is how one user reviewed this plugin. While I may not describe the default editor quite so — ahem — eloquently, this plugin does solve some problems, particularly when you need to more easily click around the interface.
\n\n\n\nAs Brian Gardner joked on Twitter, selecting some blocks like Columns is tedious work or a fun game of whack-a-mole:
\n\n\n\n \n\n\n\nOf course, there are ways around that, such as using the navigation tree, breadcrumbs, or keyboard commands. However, the block editor is meant to be a visual interface that allows end-users to simply point and click on the elements they wish to edit. Selecting specific blocks has generally improved over time, but users still run into issues. Editor Block Outline makes it a much simpler affair.
\n\n\n\nIn Full Site Editing (FSE) mode with the Gutenberg plugin enabled, the plugin did not hold up quite as well. Depending on the theme in use, the blocks’ text labels were sometimes huge or did not match across the canvas. The plugin’s icon was also not available on the site editor screen.
\n\n\n\nFSE is still in beta. The plugin cannot be expected to work with it yet. However, this is where I imagine the plugin will make the most sense for many users. In the post editor, it would get in the way of writing long-form posts. However, the plugin could become an invaluable tool for navigating complex layouts in both the post and site editors.
\n\n\n\nMore than anything, the reason I like Editor Block Outline is its dedication to a singular purpose. It adds a simple feature that enhances the editor without taking on too large of a role.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 28 Dec 2020 21:05:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:46:\"BuddyPress: BuddyPress in 2020, it’s a wrap!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=316282\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://buddypress.org/2020/12/buddypress-in-2020-its-a-wrap/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9203:\"Hello dear members of the BuddyPress community,
\n\n\n\nFor this last day of 2020, we are inaugurating our very first End of Year wrap-up post. We believe it’s a good way to congratulate ourselves (the whole BuddyPress community) about the free & priceless hard work we’ve all put together into our open source project.
\n\n\n\nThere are many ways we are getting involved into BuddyPress and we all know the best way to maintain BuddyPress in the long term is to give some of our spare time to carry on bringing that little piece to the project. Every contribution makes a difference.
\n\n\n\nLet’s thank us all, the users, the support forum moderators, the documentation writers, the translators, the theme designers, the plugin developers & the BuddyPress Core committers team. We have built great community features all along the 2020 year.
\n\n\n\nMaking BuddyPress available in as many languages as possible is very important to ensure the best user experience of the plugin features. We are always trying to improve how we credits translators and ease their tasks. During the 6.0.0 release, we’ve reviewed all the strings needing translators comments to explain the meaning of the placeholders we use (e.g.: %s
, %d
, %1$s
, etc.).
We’ve also decided to include, from now on, into major release credits the translation contributor names that have given their times to make sure the development (Trunk) translation is 100% ready once our major releases final string freeze step is over. This work is strategic to BuddyPress users as they will be able to get the new strings translation as soon as they upgrade or install the plugin.
\n\n\n\n\n\n\n\nAt the end of 2019, we’ve made available a new plugin to ease beta-testing, this year we’ve added the @wordpress/env
package to our development version (Trunk) and wrote a tutorial about how you can easily set up a development environment to play with BuddyPress code thanks to it. We believe it’s an important step towards making contributing to BuddyPress easier and we hope it will increase the number of people getting involved into BuddyPress source code improvements.
Before starting the 7.0.0 development cycle and just like the WordPress Core team does before each major milestone, we’ve published our first “Call for tickets”. We’ll do it before each major release so that you can share with the BuddyPress Core committers the tickets you think should be fixed for the next development cycle. The priorities of the BuddyPress community matter, we encourage you to use this call for tickets to make your voice heard.
\n\n\n\n\n\n\n\nDuring the 6.0.0 development cycle we (re)started to take the time to write developer notes as soon as possible. We also organized these notes into categories according to the version number of the release being built.
\n\n\n\n\n\n\n\nOur goals doing so is to limit the risk of “breaking” your active theme or plugins keeping their authors aware of changes they should check before a major release is published. It can also help developers to start working early on extending BuddyPress new features. Please do read these notes and share them with your networks to increase their audience and contribute to cover this risk.
\n\n\n\n\n\n\n\nBuddyPress surveys are back! BuddyPress is about users: we are very happy we could organize the 2020 survey to get you inputs about your BuddyPress usage and about the specific directions for the plugin we are thinking of for its future.
\n\n\n\n\n\n\n\nIf one of these projects is interesting you, don’t hesitate to contribute to it.
\n\n\n\n\n\n\n\nBased on the discussions the Core Team had during our development meetings (every other Wednesday at 19:00 UTC in #BuddyPress), here’s a list of directions we mostly agree on about:
\n\n\n\nLet’s try to make them concrete in 2021!
\n\n\n\n\n\n\n\nThanks for reading this post and for your involvement in contributing to BuddyPress in 2020. Let’s wish us all a great new year’s eve . Bye 2020 and Happy 2021, full of great contributions, to the BuddyPress community.
This tumultuous year, two things really helped me get through it: my colleagues at Automattic and the community of WordPress.
\n\n\n\nAt the end of the year I usually deliver a speech to the WP community we call the State of the Word, that celebrates what we accomplished the previous year and shines a light on what we could focus on in the coming year. There’s always a great energy in the room and I love mixing with the audience before and after the talk. This year we did it online, which meant we could produce the talk a little more, and we made extra time for the Q&A afterward with answers not just from me but folks across the community.
\n\n\n\nOne thing I’ll call out WordPress 5.6 had an all women and non-binary release squad of over 50 people, a first for WordPress and probably any large open source project. Also the market share of WordPress grew more in 2020 than it has in any year since it started being tracked!
\n\n\n\nIf you’re curious about what’s next for WordPress, check it out:
\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:\"Sun, 27 Dec 2020 22:55:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:115:\"WPTavern: Google to Migrate Structured Data Testing Tool to New Domain after Backlash from Deprecation Announcement\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109332\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:275:\"https://wptavern.com/google-to-migrate-structured-data-testing-tool-to-new-domain-after-backlash-from-deprecation-announcement?utm_source=rss&utm_medium=rss&utm_campaign=google-to-migrate-structured-data-testing-tool-to-new-domain-after-backlash-from-deprecation-announcement\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2781:\"Google’s Rich Results Test came out of beta in July with support for all Google Search rich result features like carousels, images, or other non-textual elements. At that time, Google announced it would be deprecating the Structured Data Testing Tool, which SEOs, developers, and site owners have relied on for testing structured markup and troubleshooting schema issues.
\n\n\n\nThe SEO community reacted strongly to this change, because the Rich Results Test only validates structured data that is supported by Google. It also does not provide much useful feedback on errors.
\n\n\n\n“This is awful,” SEO consultant Barry Adams said in response to the change. “The SDTT is a tool that validates ALL schemas and helps make the web a semantically richer place. The RR test only supports a tiny narrow subset of Google-approved schemas. You’re downgrading the web with this move.”
\n\n\n\nWhen Google announced the Structured Data Testing Tool’s deprecation on Twitter, comments from various web professions indicated widespread disappointment in the decision.
\n\n\n\n“The new tool is painfully slow,” digital marketing consultant Ian Lurie said. “The old tool showed a structured data result for the URL tested above. It provided useful feedback and supported industry-wide standardization. The truth is, you’re replacing a great structured data tool for an inferior Google-specific one.”
\n\n\n\nAfter taking note of all the negative feedback, Google announced last week that it will no longer be deprecating the tool. Instead, the company plans to migrate it to a new domain:
\n\n\n\n\n\n\n\nTo better support open standards and development experience, we’re refocusing the Structured Data Testing Tool and migrating it to a new domain serving the schema.org community by April 2021. The main purpose of the tool will be to check syntax and compliance of markup with schema.org standards.
Google is making some changes to the tool to differentiate it from the Rich Results Test. The Structured Data Testing tool will not be able to check for Google Search rich result types. It will be refocused to validate only schema.org properties, and is recommended for validating types that Google Search doesn’t yet consume.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Dec 2020 23:56:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:61:\"WPTavern: Learn WordPress Launches Trac Introductory Workshop\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109334\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:167:\"https://wptavern.com/learn-wordpress-launches-trac-introductory-workshop?utm_source=rss&utm_medium=rss&utm_campaign=learn-wordpress-launches-trac-introductory-workshop\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2230:\"Jonathan Desrosiers, a WordPress core committer and software engineer at Bluehost, has published a new workshop titled “How to Use Trac” on the Learn WordPress platform. The 20-minute video offers a crash course on the ticket tracking software that WordPress relies on to manage core development. Trac is also used for contributing to WordPress’ meta component, which includes WordPress.org sites and API, directories, support areas, and other projects.
\n\n\n\nTrac’s antiquated UI can be intimidating for newcomers, posing another barrier to contribution. Even experienced WordPress contributors are eager to move core development to GitHub or some other platform. It can get confusing since bugs related to the editor need to be reported on GitHub instead of Trac. Until WordPress adopts another platform, the ability to navigate Trac remains an important skill.
\n\n\n\nDesrosiers’ workshop covers topics like searching for pre-existing tickets before reporting a new issue, how to write a good bug report or feature request, how to identify component maintainers, attaching patches, and how proper classification of the ticket can help other teams get involved. He also helps workshop students understand ticket resolutions so they can frame their expectations accordingly. This video includes a full walkthrough of creating a new ticket where Desrosiers explains each field on the form.
\n\n\n\nOnce you get up to speed on learning Trac and start contributing, you may also want to follow the WordPress Trac on Twitter. New contributors may also want to explore WPTracSearch, an unofficial project that provides an alternative Elasticsearch-powered interface for searching WordPress Trac tickets. WPTracSearch delivers more accurate results, even for basic queries, that can be filtered based on milestone, component, focuses, usernames, and more criteria.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Dec 2020 21:38:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:98:\"WPTavern: Gutenberg 9.6 Introduces Drag-and-Drop Blocks and Global Inheritance for the Query Block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109323\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:241:\"https://wptavern.com/gutenberg-9-6-introduces-drag-and-drop-blocks-and-global-inheritance-for-the-query-block?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-9-6-introduces-drag-and-drop-blocks-and-global-inheritance-for-the-query-block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5098:\"For some people, Christmas arrived a couple of days early. Gutenberg 9.6 launched with its first iteration of drag-and-drop blocks from the inserter. There are some other enhancements like vertical buttons, heaps of bug fixes, new APIs, and other improvements. But, let’s be real. The ability to drag blocks from the inserter into the content canvas is the highlight of this release.
\n\n\n\nAnother key feature is that the Query block, which is only available when Full Site Editing is enabled, now inherits from the global query arguments. As has been usual as of late, much of the work in the Gutenberg plugin has focused on improving the site editor.
\n\n\n\nPerhaps the Gutenberg development team has seen your comments and your other comments. If there is one common thread among the comments on our Gutenberg-related posts, it is that a segment of the WordPress user base wants more drag-and-drop capabilities.
\n\n\n\nThe new feature only works with blocks right now. Users cannot yet drag and drop patterns from the inserter.
\n\n\n\nAfter several tests since Gutenberg 9.6 Release Candidate 1 landed last week, I have had no issues with it. For the most part, the experience felt smooth and easy to use.
\n\n\n\nI have never seen the allure of drag-and-drop features in a content editor. If I am not typing in Markdown, I am in the WordPress editor and using keyboard shortcuts. Throughout my career, I have either been writing code or writing words daily. Picking up my fingers from the keyboard only serves to waste time.
\n\n\n\nSometimes I forget that the block editor already has some drag-and-drop capabilities available, which allow end-users to move blocks from one position to another in the canvas. I tend to work with the top toolbar enabled, so I rarely see the feature.
\n\n\n\nNevertheless, I do see how dragging and dropping blocks could be useful to some users. I use them in other types of editors, such as Gimp or Photoshop, at times. The one thing I like about those is the toolset is always available in the sidebar. This is not the case with the block inserter. While it will stay open for users to drag multiple elements into their content, it disappears once users begin working elsewhere. That could become irritating if the user is in more of a visual-design workflow instead of a content-editing mode.
\n\n\n\nDragging blocks from the inserter would make more sense for my workflow in the upcoming site editor rather than the post editor. The feature works great in that context too.
\n\n\n\nThe low-key star of this release is an update to the Query block, which is only available when using a block-based theme. The update is one of the most important breakthroughs for Full Site Editing, a pivotal moment in the history of the Gutenberg project.
\n\n\n\nIn previous iterations, the Query block required that themes via their block templates or end-users via the site editor define which posts to display. While that is a necessary function of the block, the missing piece was the global query support.
\n\n\n\nIn the simplest terms, whatever URL a visitor lands upon tells WordPress which posts to load. The data for loading these posts is all stored in a global set of query arguments. Themes can then loop through these posts to display them.
\n\n\n\nIn Gutenberg 9.6, the Query block can now inherit these query arguments. This means that things like the blog posts page, category archives, search results, and more will display the correct posts when someone visits one of those specific URLs.
\n\n\n\nOn the surface, this change merely adds a single option to the interface. However, under the hood, it is a achievement that clears a gaping path for developing block-based themes.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Dec 2020 20:16:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:79:\"WPTavern: Exploring Photo Blocks, an Experimental FSE-Ready Photoblogging Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109274\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:201:\"https://wptavern.com/exploring-photo-blocks-an-experimental-fse-ready-photoblogging-theme?utm_source=rss&utm_medium=rss&utm_campaign=exploring-photo-blocks-an-experimental-fse-ready-photoblogging-theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4979:\"Kjell Reigstad announced the Photo Blocks theme on December 9. It is a part of an ongoing set of experimental work from the WordPress Theme Experiments repository on GitHub. It is essentially a testbed of ideas that are helping to propel the upcoming block-based theming era.
\n\n\n\nIn the past few months, I have covered the repository’s Carrd-like landing page theme, Twenty Twenty-One Blocks, and the Full Site Editing (FSE) Theme Generator. There is a lot of movement happening in the repository that theme developers would be remiss to overlook.
\n\n\n\n“I built a new block-based photoblog theme in the experiments repo,” Reigstad tweeted just a couple of weeks ago. “It’s refreshing to see how well this works just with existing FSE tools.”
\n\n\n\nLike most FSE-capable themes currently making the rounds, it is simple. There are miles left before block-based themes and the upcoming site editor reach maturity. Photo Blocks showcases yet another step in the evolution of the system.
\n\n\n\nThe theme uses the Query block’s new grid view, which was added in Gutenberg 9.5. The Query block is one of the most important pieces of the Full Site Editing system. Like in traditional themes, the query and “the loop” output posts on the front end.
\n\n\n\nThe addition of the grid view allows themes to output their posts in columns. This is a nice addition for Photo Blocks and other photoblogging or portfolio themes. Currently, the Query block supports only a second type of view, the default list of posts. It all seems to limit design possibilities right now, but the grid option does provide some hope that more robust tools are coming.
\n\n\n\nThe Query block is undoubtedly one of the most complex features the Gutenberg team is building, and it is a crucial block for the upcoming site editor.
\n\n\n\nThere is also no posts pagination or navigation at the moment. That is because the Gutenberg team is still ironing out the details of such a block. This is another Herculean task given the near-limitless variations on designing posts navigation. The block will need to provide theme authors the flexibility they are accustomed to when writing code.
\n\n\n\nThe development of Photo Blocks exposed some missing features in Gutenberg. Without community feedback from building and testing block-based themes, it is tough for the development team to identify such issues.
\n\n\n\nCurrently, the only way to have same-height images in the Photo Blocks theme’s post grid is to manually crop and upload images with the same aspect ratio. Reigstad opened a ticket to set a consistent crop for the Post Featured Image block. I would also recommend an image-size option similar to how it is handled in the Image block.
\n\n\n\nTraditionally, themes that output a grid of featured images would fall back to a default image or use the first image from the post content if one was not set. There is currently no way to do this with the Post Featured Image block — another missing key feature. Reigstad opened a new ticket that proposed taking the idea further.
\n\n\n\n“In the past, the featured image was a single image, added and managed separately from the rest of the post content,” he wrote. “For block-based sites however, that restriction is largely unnecessary. Rather than just an image, we should consider making it possible to set a video or audio embed as the ‘Featured’ block. Also, since posts are made up of structured data, it’s theoretically possible to signify any block from within post content as a ‘Featured’ block.”
\n\n\n\nThe idea of featured media is not new. Many themes have had featured audio and video in the past. However, the concept of marking any type of block as featured is worth exploring. Even if not every block lends itself well to this, surely some do beyond images.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Dec 2020 00:35:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:57:\"WPTavern: Shutterstock Launches Official WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=108844\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:159:\"https://wptavern.com/shutterstock-launches-official-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=shutterstock-launches-official-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2130:\"Shutterstock has released an official plugin for WordPress. The 17-year old company is as old as WordPress itself but this is the first time it has provided convenient access to its library inside the admin.
\n\n\n\nSeven years ago, Shutterstock released a plugin for affiliates using a third-party development company, but it failed to gain much traction and is no longer updated. The new block-based plugin applies more broadly to WordPress site owners looking for commercial stock photography. It provides a block that allows users to search Shutterstock’s library of 340 million images and get suggestions based on the text content. Users can place preview images on pages and posts, license with one click, download, and publish images and editorial content.
\n\n\n\nShutterstock’s plugin respects WordPress’ user roles and permissions system, so organizations can restrict image licensing to editors and administrators while still allowing authors to insert image previews. The plugin also has access to the user’s license history so they can download any content that has been previously licensed on Shutterstock.
\n\n\n\nA couple weeks after launching, the plugin is active on fewer than 10 WordPress sites. It’s not clear if that is due to its customers not knowing about it or the endless variety of free images that WordPress users have access to through other services. Since the plugin only offers access to a limited library by default, it is primarily aimed at Shutterstock customers who have an existing subscription to connect for the full collection.
\n\n\n\nAlong with the official plugin release, Shutterstock also announced a new partnership with WordPress.com VIP. It is now one of the service’s “Featured Technology Partners,” streamlining the publishing workflow for Automattic’s enterprise customers.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 22 Dec 2020 23:32:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:86:\"WPTavern: What Is Full Site Editing and What Does It Mean for the Future of WordPress?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109217\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:215:\"https://wptavern.com/what-is-full-site-editing-and-what-does-it-mean-for-the-future-of-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=what-is-full-site-editing-and-what-does-it-mean-for-the-future-of-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:10892:\"As I said last week, 2021 will be the year of the site editor. Matt Mullenweg’s State of the Word confirms it. WordPress 5.7’s release planning is focused on it. It has been a long journey getting to this point, and it will be a much longer adventure afterward. The ultimate promise of the work that began nearly four years ago is nigh.
\n\n\n\nThe Gutenberg project was never just about editing content. WordPress was aging software by late 2016. It needed to cater to modern audiences who may be less tech-savvy than the platform’s existing user base. It needed to capture a younger generation of developers who were looking at the greener grass of JavaScript-heavy software. It needed to offer an experience on par with modern web applications. WordPress had a lot of boxes it needed to check or face irrelevance.
\n\n\n\nThe one thing that has truly kept the platform afloat is its large and diverse ecosystem of third-party developers.
\n\n\n\nOne of the most popular types of plugins? Page builders. Those such as Elementor, which launched in early 2016, were filling in the experience gaps that WordPress was missing. While it was a testament to the platform’s extendibility for such third-party projects to arise, it was also a failure that the core platform could not offer a better experience to both users and developers out of the box. Far too many theme authors were forced into supporting third-party builders to remain relevant. They were focusing more and more on compatibility with plugins than simply designing.
\n\n\n\nThe shortcomings of the widgets, shortcodes, meta boxes, and settings systems meant that developers had to either rely on non-core frameworks or reinvent the wheel. Every new API brought with it a new method for adding basic form fields. At best, it was inelegant, a platter of spaghetti that had been thrown at the wall, some of it managing to stick.
\n\n\n\nWordPress was beginning to show its wrinkles. It needed to revolutionize itself. It needed to feel fresh again. For better or worse, the developers behind the Gutenberg project have been putting in the work to do just that.
\n\n\n\nIt is slow work. But, it is promising work.
\n\n\n\nWhile the term “Gutenberg” is often used interchangeably with “block editor,” the two are not one and the same. Gutenberg is a project. A plugin. An idea. A new way of thinking about publishing on the web. As the opening lines of the description of the plugin read:
\n\n\n\n\n\n\n\n“Gutenberg” is a codename for a whole new paradigm in WordPress site building and publishing, that aims to revolutionize the entire publishing experience as much as Gutenberg did the printed word.
The project has four phases:
\n\n\n\nWordPress users who have not been testing the Gutenberg plugin have only experienced Phase 1 of the project. The launch of the block editor in WordPress 5.0 and its continued work set the stage for the phases to follow. The underlying block system is what will fuel the next decade or longer of WordPress.
\n\n\n\nToday, we are firmly in the midst of Phase 2. And, this is where things will get interesting.
\n\n\n\nPhase 2 of Gutenberg, which began in late 2018, promised to bring blocks outside of the post content. In an introduction to this next step, Mel Choyce-Dwan outlined the three main focuses:
\n\n\n\npost_content
.Since then, those core concepts have remained the same. However, the full picture, the shape of what those concepts would look like, has changed in the last two years. If there is one thing anyone on the development team has learned, it is probably that it is hard to launch such drastic changes.
\n\n\n\nFull Site Editing is a mix of concepts. It is one part transition from tradition and one part full overhaul of how users and developers design the front end of WordPress sites.
\n\n\n\nNav menus and widgets, which are a part of the old paradigm, have been set to relaunch under the block system for the past two major WordPress releases. They were not ready. Users should expect to see them in WordPress 5.7. However, these feature upgrades are merely stepping stones to true the true Full Site Editing feature. They offer a way for end-users who are still using classic WordPress themes to get a taste of blocks outside of the post-editing screen.
\n\n\n\nFor the users who take the next step, widgets and nav menus — at least the traditional admin screens — will disappear. The customizer, which was once touted as the future of theme development, is also getting the ax. Site customization via a system where everything is a block will reign supreme.
\n\n\n\nOnce the switch flips, the world will be looking at a whole new WordPress.
\n\n\n\nWordPress 5.7 and beyond will be about the site editor and block-based themes. The site editor is the visual representation of block templates that theme developers offer to users. Templates are infinitely customizable by the user from the WordPress admin. While themers will create custom configurations and set defaults, the power to decide what the front end of the site will look like will ultimately reside in the user’s hands.
\n\n\n\nSince the launch of Phase 1, the block editor has been a love/hate affair. Expect the site editor to be no less controversial.
\n\n\n\nUnderneath it all, a theme’s code and the site editor will be talking in the same language. This essentially means that users could transition to theme authors if they have a knack for design or simply want to give it a go. They should be able to do this without leaving the comfort of the trusty site editor, which already allows exporting templates.
\n\n\n\nBecause the post editor and the site editor both work on the same, underlying block-based foundation, there is no reason for users to not be able to seamlessly switch between the two. There is currently a ticket for adding such a toggle on the post-editing screen. It will allow users to switch to a template-editing mode while never leaving the post editor.
\n\n\n\nThis is not a newly-introduced concept. Josepha Haden, who led the WordPress 5.6 release, touched on this earlier this year. “I think one of the problems that we’re trying to solve with Gutenberg has always been a more consistent experience for editing elements across the WordPress interface,” she said. “No user should have to learn five different workflows to make sure their page looks the way they imagined it when it’s published.”
\n\n\n\nOne of the larger goals is reducing the number of workflows into a single interface. We are likely years away from seeing the whole of WordPress site management reduced that far. However, the site editor is the next step toward that potential user experience.
\n\n\n\nWhile the last few years may have felt like a whirlwind of changes to our beloved platform, you ain’t seen nothing yet. We were just getting our bearings in Phase 1. The development team was building the foundation while also launching the user-facing block editor. With that foundation in place, the team can focus more on features. This will especially be true as the G2 Components project overhauls and standardizes how core and third-party developers build upon the block system.
\n\n\n\nThe big Phase 2 changes this year means that theme authors will need to get up to speed. Traditional WordPress themes will still be necessary for a while. However, any theme author who is not already tinkering with block-based themes is already months behind. This is the time to be exploring and helping to shape the system. It is time to be filing bug reports and feature requests.
\n\n\n\nIf possible, theme authors should be attending the twice-monthly block-based themes meetings. If time does not allow for attendance, you should at least be reading and participating on the Make Themes blog.
\n\n\n\nIt is also important to check out projects like the Q theme or follow the Theme Experiments repository.
\n\n\n\nFor end-users, this entire project is about you. Your feedback is crucial. If you are not already testing your site with the Gutenberg plugin, you should be. It is sometimes weeks or months ahead of what you are getting with WordPress alone. Try out an FSE theme like Block-Based Bosco. Consider joining the FSE Outreach Program. You can test and provide feedback directly on upcoming features.
\n\n\n\nFSE brings with it the promise of major changes in 2021. Many of these changes will uproot old methods of managing your WordPress websites. Those methods will be replaced with one of the largest overhauls to the platform in its history. It is time to get prepared.
\n\n\n\nIt is going to be an interesting new 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:\"Tue, 22 Dec 2020 00:56:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:77:\"WPTavern: WordPress 5.7 Development Kicks Off with Focus on Full Site Editing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109212\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:199:\"https://wptavern.com/wordpress-5-7-development-kicks-off-with-focus-on-full-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-7-development-kicks-off-with-focus-on-full-site-editing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3662:\"If the 2020 State of the Word address was any indication, WordPress is moving full steam ahead to land full site editing in 2021. The 5.7 release cycle kicked off this week with the proposed scope centered around full site editing via Gutenberg. Matt Mullenweg will be leading the release and the rest of the team leadership is still being rounded up. Bug scrubs for early tickets that require more time or early testing are already underway.
\n\n\n\nWordPress 5.7 contributors anticipate working on the following features in the next release:
\n\n\n\n“We might add more items in the upcoming weeks, and we will reconfirm the above-proposed list after the end-of-Gregorian year holidays,” Francesca Marano said in a planning roundup post. She said core development is not “closing up shop” for the holidays, and volunteers plan to run bug scrubs and dev chats. Those who cannot attend a meeting but want to advocate for a ticket can always comment on the dev chat agenda post to have it included in the discussion.
\n\n\n\nMatias Ventura created a GitHub issue in August for contributors to track the progress of full-site editing milestones. Some of the infrastructure and UI is already in place, as well as the ability to navigate through pages, templates, parts, and know which is area is active. Styling, theme blocks, the Query block, and the Navigation block are still in progress.
\n\n\n\nThere are a lot of moving pieces to make full-site editing features cohesive and ready for prime time. In Ventura’s most recent status update on the project he reported that all of the features outlined are “in advanced stages” and can be used in the Gutenberg plugin already.
\n\n\n\n“The main hurdle to include the work in major WordPress releases are the various dependencies between each project when it comes to ensuring a great user experience,” Ventura said. “The immediate focus is then on completing the milestones, stabilizing the work, and doing as much testing with different kinds of users as possible.”
\n\n\n\nWordPress contributors are planning four releases in 2021, allowing for multiple opportunities to introduce new features.
\n\n\n\nBeta 1 for 5.7 is planned for early February and the general release is expected March 9, 2021.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Dec 2020 23:18:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:48:\"BuddyPress: BuddyPress 7.1.0 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=316287\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://buddypress.org/2020/12/buddypress-7-1-0-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1204:\"Immediately available is BuddyPress 7.1.0. This maintenance release fixes two bugs related to issues introduced in the 7.0.0 release.
\n\n\n\nFor details on the changes, please read the 7.1.0 release notes.
\n\n\n\nUpdate to BuddyPress 7.1.0 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.
\n\n\n\n\n\n\n\nMy question to you is how you see the future (or even the present) of integrating software with WordPress and when you should make the distinction of going the integration vs. native approach.
In other words, with the vast ecosystem of WordPress plugins out there, how can a website owner discern which responsibilities WordPress the software should handle and whether that functionality is actually better to plug another software or service into instead?
Alex
There was a time when I would have said build all the things in WordPress. I was younger then, a bit more naive. I was optimistic about using WordPress as a framework to build anything. There is a part of me that still leans in this direction. Mostly, this is because I want to see what developers in the WordPress ecosystem can achieve. I applaud anyone who pushes the platform beyond its current limits.
\n\n\n\nFew people would have guessed that WordPress would become an eCommerce powerhouse. However, WooCommerce has proven it can be done. I still remember when nearly every WordPress theme and plugin author was selling their commercial products via E-junkie. Now, Easy Digital Downloads is the go-to solution, and AffiliateWP handles the affiliate side of things.
\n\n\n\nSome of the best products from the WordPress plugin market arose from issues with third-party app integration. Their creators bucked the system and brought useful tools directly into WordPress. Many of these are now multi-million dollar products and companies that employ dozens, hundreds, or even thousands of people. They have their own ecosystems that allow even more third-party developers to make a living. And this is all done on top of WordPress.
\n\n\n\nI will always root for the home team, for the developers in our community to build native solutions.
\n\n\n\nHowever, the reality is that WordPress is not the best solution for everything. Depending on the application, the development team has likely put years of work into it, creating a specialized system that caters to that application’s users. The experience can often be far better than something available for WordPress.
\n\n\n\nI cannot imagine using WordPress as the backbone of a social video site like YouTube, even if it was a small site. The hosting costs would be astronomical. It is far easier and cheaper to rely on integration with YouTube rather than trying to rebuild it.
\n\n\n\nIn Alex’s original correspondence, he also brought up a specific case about integrating with a third-party forum. This is a far more realistic quandary than an average user trying to build the next YouTube. It is also a question that does not have a single answer.
\n\n\n\nFor users who are creating forums on their site for the first time, my advice would be to go with bbPress. It is a plugin that brings native forums to WordPress. While it is not nearly as powerful as some third-party forum applications, its best feature is that it works directly with the built-in user, role, and capability systems in WordPress. These are some of the more complex APIs in WordPress, and trying to sync user accounts between applications can often be a headache. It is also a complex technical topic that goes beyond the scope of this post. If starting from scratch, I would recommend bbPress or another WordPress forum plugin.
\n\n\n\nOn the other hand, if a user already has an existing forum with a large amount of content, I would lean toward integrating it and WordPress, particularly if the site owner plans to keep user registrations strictly within the forum software. Much of that will come down to what the end-user feels comfortable with. If they have a strong history with their existing application, making a change may simply not be the best route. There are other items to consider, such as whether sharing a single theme across both platforms is necessary. bbPress can also import content from many existing forum applications.
\n\n\n\nThe answer to the question is that it depends. Each use case is different.
\n\n\n\nShould a popular seller on Etsy move everything to WooCommerce? Probably not. That user might want to install the Etsy Shop integration plugin. Eventually, they might expand their brand enough to no longer rely on the Etsy platform. At that point, WooCommerce could be the answer.
\n\n\n\nIt comes down to time, cost, research, and testing. Even when a plugin brings a native solution to WordPress that is ideal for most people, it might not be the best answer for an individual. Specifics matter, and I am always happy to talk those over.
\n\n\n\nThis is the second post in the Ask the Bartender series. Have a question of your own? Shoot it over.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 18 Dec 2020 20:50:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:74:\"WPTavern: State of the Word 2020: WordPress Moves Toward Full Site Editing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109009\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:191:\"https://wptavern.com/state-of-the-word-2020-wordpress-moves-toward-full-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=state-of-the-word-2020-wordpress-moves-toward-full-site-editing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6819:\"WordPress enthusiasts around the world tuned into Matt Mullenweg’s annual State of the Word address this week, delivered virtually for the first time. Mullenweg recognized the community’s efforts in working together during a global pandemic, without the benefit of periodic in-person events that have traditionally re-energized collaboration on the project.
\n\n\n\nDuring a most unusual year that has warped the passage of time and slowed it to the speed of molasses, WordPress’ release schedule kept a steady, reassuring pace in contrast. The first part of the State of the Word highlighted the three major releases shipped in 2020, which introduced improvements to the block editor, a new default theme, application passwords for the REST API, and new, game-changing features like block patterns, to name just a few.
\n\n\n\nWordPress continues to grow its dominant market share and is currently sitting at 39.3% of the Alexa top 10 million sites. Mullenweg attributed that growth to three major contributing factors: the lockdown, e-commerce, and economic uncertainty. The lockdowns put in place to mitigate the virus’ spread had the effect of giving people the space and time to connect online. It also drove an uptick in entrepreneurship and e-commerce. Mullenweg reported that WooCommerce facilitated more than $20 billion in sales.
\n\n\n\nGutenberg design contributor Joen Asmussen joined by video to unveil a sneak peek of the progress on the Full Site Editing (FSE) project with a demo of the Site Editor beta. The Site Editor allows users to edit a theme’s template outside of the post’s content. It introduces new blocks for things like the query loop, navigation, site title, tagline, and other aspects of editing templates.
\n\n\n\nThe block list view shows all the different areas of the page, such as the header, footer, columns, and site title, so the user can jump to the section for quick access. Block patterns can also be used within template designs to speed up page layout or match a demo design. Given the current complexity of creating a template design from a blank canvas, block patterns have the potential to become even more indispensable when WordPress users finally get the reins for editing theme templates.
\n\n\n\n“This is the culmination of several ongoing projects to expand upon and improve the customization possibilities in WordPress,” Asmussen said. The demo offers a quick overview of how the FSE project is coming together. The reality of “everything becoming a block” is finally materializing. Gutenberg will soon be capable of providing a consistent editing experience across all aspects of site customization.
\n\n\n\n“By creating this common framework that every theme and plugin can build on, we’re reducing the balkanization within WordPress from people who are solving these problems lots of different ways, and providing what I believe is the basis for the next decade of WordPress’ growth,” Mullenweg said.
\n\n\n\nThe number of questions during the Q&A related to multilingual capabilities underscores the fact that WordPress is undeniably a global community. More than 50% of WordPress sites are not using English. Better multilingual support could be key to the next era of WordPress’ growth. Nevertheless, multilingual features are at the tail end of the four-phase roadmap for the project’s immediate future.
\n\n\n\nMullenweg said WordPress is about “two years into a 10-year project,” with good chunks of phase 1 and phase 2 done. Phase 1 includes editing inside the post/page content, creating the fundamental building blocks and also bringing them to the mobile apps. Phase 2 is centered around editing outside the content, using blocks to create the site’s templates.
\n\n\n\nPhase 3 will introduce new collaboration features and workflow for real-time co-editing. Phase 4, which Mullenweg said is “just in the imagination stage right now,” covers multilingual features. He said he expects this phase to likely “be taken underway pretty vigorously in 2022.”
\n\n\n\nMatías Ventura answered a question about a phase 4 roadmap, confirming that there is no specific plan for its multilingual implementation right now. He said there have been some initial conversations regarding the implications of localization, specifically around patterns and block themes, and how those can be built. Nothing substantial has emerged yet but the team will be creating a more detailed overview of what is needed. Fallback languages is one feature that several community members brought up in the Q&A time.
\n\n\n\nWhen asked whether some existing multilingual solutions could be reused for core, Mullenweg was hesitant to prescribe a specific approach at this time. He said he is anxious to get better multilingual support in Gutenberg and offered what I believe is the most candid explanation thus far for why multilingual capabilities fall further down the the list of priorities:
\n\n\n\n\n\n\n\nWhether we do it as part of core or as part of an official plugin is to be decided. Part of the reason we made it phase 4 is that we can only do so many things well at a time. It is supremely important that we execute super well on these first phases of Gutenberg blocks. If we don’t get phase 1 and phase 2 to be the best experiences in the world for editing bar none, of any open source or proprietary competitors or builders, phase 3 and 4 just won’t matter because WordPress won’t be relevant a decade from now. I do believe that is the most important problem we’re facing. I don’t want to dilute the core contributors’ focus away from the initial phases of Gutenberg because that’s how important I think they are.
Mullenweg said there is nothing stopping the community from investing more in multilingual plugins and exploring different approaches to see what will get core most of the way there. The next official step would be figuring out a framework that will work well with plugins and themes.
\n\n\n\nDepending on your interest and involvement in the community, there is a lot more to explore in the Q&A. Check out the whole presentation in the video below.
\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, 18 Dec 2020 09:21:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:100:\"WPTavern: Contact Form 7 Version 5.3.2 Patches Critical Vulnerability, Immediate Update Recommended\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109081\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:241:\"https://wptavern.com/contact-form-7-version-5-3-2-patches-critical-vulnerability-immediate-update-recommended?utm_source=rss&utm_medium=rss&utm_campaign=contact-form-7-version-5-3-2-patches-critical-vulnerability-immediate-update-recommended\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1899:\"Contact Form 7 has patched a critical file upload vulnerability in version 5.3.2, released today by plugin author Takayuki Miyoshi. The plugin is installed on more than five million WordPress sites.
\n\n\n\n“An unrestricted file upload vulnerability has been found in Contact Form 7 5.3.1 and older versions,” Miyoshi said. “Utilizing this vulnerability, a form submitter can bypass Contact Form 7’s filename sanitization, and upload a file which can be executed as a script file on the host server.”
\n\n\n\nThe vulnerability was discovered by Jinson Varghese Behanan from Astra Security on December 16, 2020, and Miyoshi released a fix less than 24 hours later. Behanan highlighted a few ways this vulnerability might be exploited:
\n\n\n\nAstra Security plans to publish more details on the vulnerability in two weeks after the plugin’s user base has had more time to update to the patched version.
\n\n\n\nVersion 5.3.2 removes control, separator, and other types of special characters from the filename to fix the unrestricted file upload vulnerability. At the time of publishing, more than a million Contact Form 7 updates have been downloaded today. Approximately 20% of the plugin’s user base is protected from the vulnerability. Now that it has been patched and published, Contact Form 7 users who do not update will be more at risk of having the vulnerability exploited.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Dec 2020 22:32:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:73:\"WPTavern: Help Steer the Future of WordPress via the FSE Outreach Program\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109083\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:191:\"https://wptavern.com/help-steer-the-future-of-wordpress-via-the-fse-outreach-program?utm_source=rss&utm_medium=rss&utm_campaign=help-steer-the-future-of-wordpress-via-the-fse-outreach-program\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4280:\"All hands on deck. 2021 will be the year of the Site Editor.
\n\n\n\nAnne McCarthy announced the official start of the Full-Site Editing (FSE) Outreach Program last Friday on the Make Core blog. The program is primarily geared toward end-users. With few channels for average users to communicate with the development team, this offers an opportunity for them to provide direct feedback.
\n\n\n\nThis announcement comes on the heels of Matias Ventura’s full overview of the FSE project. In the post, he laid out where specific FSE features currently stand and what needs to happen to bring the project to fruition.
\n\n\n\nThe FSE Outreach Program was expected to begin earlier in the year. Josepha Haden announced it on May 1. However, there was no movement for most of 2020. An early version of FSE was also expected to land in WordPress 5.6, but that was too lofty of a goal for a feature that will essentially change everything about front-end development on the platform.
\n\n\n\nThe official launch of the program should coincide with the release of Gutenberg 9.6, which is expected to ship within the next week. The program will focus on specific features and flows related to full-site editing. According to the program FAQs, participants could be asked to volunteer for up to three hours per week. However, it will also be flexible enough for anyone to participate, regardless of their available hours.
\n\n\n\nThe program is also starting small, limiting feedback to more common user experiences. It is still experimental at this stage. Easing participants into such a testing program seems like a smart approach.
\n\n\n\nRight now, the Site Editor can sometimes be a painful user experience. While it is already possible to put together some interesting layouts, at least as a labor of love, there are many missing pieces. Workflows are odd. Expected features for a design tool are nowhere to be found. Someone might look at it today and think there is no way it could be a viable core feature next year, but the development team continues to polish the experience with each Gutenberg update. The Site Editor is not production-ready yet, but it is time to get serious about testing and feedback.
\n\n\n\nThose interested in volunteering for the program should have a WordPress Slack account and join the #fse-outreach-experiment channel. McCarthy said she will also post an update on the Make Test blog with further details for participants once Gutenberg 9.6 is released.
\n\n\n\nThe first feature up for discussion is a new template editing mode inside the post editor. It adds a new “Template” option in the post-editing sidebar that will allow users to jump between editing their post and editing the template that outputs that post. It is a marriage of the post and site editors. Underneath, both are run by the block system, so there is little difference in the experiences.
\n\n\n\nLong-term, it makes sense that users should be able to switch seamlessly between both editors. I worry that we may be jumping the gun a bit on this feature since the Site Editor is still at a rough beta stage. However, it does not hurt to get some early feedback on what the workflow should look like.
\n\n\n\n“Please keep in mind that this is the program’s first iteration,” wrote McCarthy in the post. “We’re starting with this first item and expecting the outcome to be a comprehensive list of issues that the Gutenberg team can work on as capacity allows.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Dec 2020 22:09:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:81:\"BuddyPress: How BuddyX made its way to the official WordPress.org theme directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=316229\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://buddypress.org/2020/12/how-buddyx-made-its-way-to-the-official-wordpress-org-theme-directory/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14561:\"We use to feature BuddyPress usage case studies. These are great ways to share with you how BuddyPress can help you achieve your community site projects reading how other buddies did it. The case study you are about to read now is a bit different. It’s about the steps the lovely BuddyX BuddyPress theme had to take to be widely and freely available from the official WordPress.org theme directory. I’m very happy Varun Dubey took the time to write this guest post to share his experience with all of us. My secret hope is that it will inspire as many BuddyPress Theme authors as possible to do the same .
Varun Dubey is a full-stack WordPress & BuddyPress developer. He’s the co-founder of Wbcom Designs, a WordPress themes and plugins development agency in India. He’s also a regular BuddyPress contributor, we often talk with him about the BuddyPress project during our development meetings (every other Wednesday at 19:00 UTC on Slack), he contributes to our development tasks (testing, reporting issues, patching, documenting, etc..) and he still manage to find time to help you regularly replying to your support topics (661 replies so far!). So, once again, many thanks to him for getting involved with BuddyPress .
So let’s learn more from his experience, here’s what he wanted to share with you about it!
\n\n\n\n\n\n\n\n\n\n\n\n \n\n\n\nI submitted my first theme at WordPress.org, and now it’s live.
@vapvarun
We, at Wbcom Designs, are excited about our achievement to present a full-fledged community theme powered by BuddyPress and WordPress. It took almost a year to work on BuddyX and make it stable enough to submit at WordPress.org.
\n\n\n\nThe approval process was surprisingly short, approx 6-7 weeks to get it approved after initial submission. We usually had heard that it might take 6-9 months to get the theme live.
\n\n\n\nSubmitting the theme at WordPress.org will increase your reach to all sites which are using WordPress. The WordPress theme directory is used by millions of WordPress users all over the world. The directory themes are available for download from WordPress.org, and WordPress users can also install them directly from their administration screens.
\n\n\n\nBy hosting your theme on WordPress.org, you’ll get:
\n\n\n\nWe have learned a lot about code reviews, code quality, and theme lifecycle during the approval process. I will give a quick glimpse of how it was for BuddyX; it might help others get the theme approved quickly.
\n\n\n\n\n\n\n\nLots of developers begin the development of a theme from scratch. There are articles and tutorials available on how to start theme development from scratch, and the WordPress Themes development handbook also has a detailed step guide on this topic.
\n\n\n\nAfter comparing _s, roots, and other starter themes, we decided to start with the WP rig. WP rig helped get a basic skeleton of the BuddyX using the latest tools, best practices, and coding standards. It helped integrate lazy-loading, async/defer JavaScript enqueueing, component-level pre-loaded CSS, optimized Web Font loading, modular extensions, and a full-featured list of optional template hierarchy files at day one.
\n\n\n\nAlong with WordPress Code Quality Testing, WordPress Coding Standards integration was also part of it. After getting initial help for the WP rig, we only have to focus on design improvement for BuddyPress Community features.
\n\n\n\n\n\n\n\nAfter the design part gets ready, we have released our theme on our website and make it available for free download to get initial feedback as a soft launch. It received a good response from the community, and we have got some feature requests and feedback on initial versions. It helped us to gain the confidence to submit BuddyX at WordPress.org.
\n\n\n\nYou can follow these steps to check your theme against WordPress requirements before submitting it for review.
\n\n\n\n1- Code Quality Check- To make sure your theme code is secure ( using proper escaping functions ), it meets WordPress Coding Standards.
\n\n\n\n2- Theme Check by plugin- The WordPress Theme review team checks your theme using the Theme Check plugin. It will be useful to double-check your theme against it first before uploading it.
\n\n\n\n\n\n\n\n3- Theme Requirement Checklist- WordPress Theme review team has published Theme Requirements. You also have to make sure you have gone through all items one by one.
\n\n\n\nEssential points you have to double-check with Theme requirements are
\n\n\n\n5- Theme Unit Test XML – You will also have to check with Unit Testing XML data. It will help get proper labels and layout testing on various templates like 404, comments on pages, comments on the post, post format testing, layout, and alignment testing.
\n\n\n\n6- Screenshot- It should not contain any branded logo or visible human face.
\n\n\n\n7- Keyboard Navigation- Keyboard-dependent navigators are also mandatory features now. You can find details at the Keyboard Navigation section of the theme development handbook.
\n\n\n\nConsider the following non-coding points before submission:
\n\n\n\nYou can upload the theme using https://wordpress.org/themes/upload/, any new revision, and the theme updates.
\n\n\n\nAfter uploading the theme files, it will create a ticket, and you will have to wait for a couple of days before any developer requests to review your theme. All reviewers are volunteers. You can also get an idea of the current theme review team member from the codex page.
\n\n\n\nYou can also check current themes waiting in the queue at https://themes.trac.wordpress.org. It will also be useful to join the Slack theme review channel to discuss review issues in the open channel.
\n\n\n\n\n\n\n\nTry to be proactive for any comments and points made related to your theme and submit fixes actively to keep your ticket reviewer.
\n\n\n\n\n\n\n\nBuddyX is a community membership theme with BuddyPress support. It is a lightweight, fully responsive, SEO optimized, RTL & Translation ready theme. It is a multipurpose theme perfect for all niches, be it membership, social community, corporate, e-commerce, LMS, etc.
\n\n\n\nThe theme also provides support for WooCommerce, WC Vendor, LearnDash, LearnPress, and GamiPress plugins. It is highly customizable and works perfectly with page builders such as Elementor and Gutenberg. BuddyX is perfect for creating social learning, marketplace, and blogging websites using BuddyPress integrations.
\n\n\n\nBuddyX has the latest best practices for progressive web content and optimization. We have tested it with the latest BuddyPress version and popular BuddyPress addons. BuddyX is developed, maintained, and supported by Wbcom Designs.
\n\n\n\nWe have worked on the following features
\n\n\n\nWithin the theme, we have overridden several template files to make the above changes.
\n\n\n\n\n\n\n\nbuddypress/activity/entry.php\nbuddypress/activity/single/home.php\n\n\n\n\n\n\n\n
buddypress/members/members-loop.php\nbuddypress/members/single/cover-image-header.php\nbuddypress/members/single/home.php\nbuddypress/members/single/friends/requests-loop.php\nbuddypress/members/single/groups/invites.php\n\n\n\n\n\n\n\n
buddypress/groups/groups-loop.php\nbuddypress/groups/single/cover-image-header.php\nbuddypress/groups/single/home.php\nbuddypress/groups/single/members-loop.php\n\n\n\n\n\n\n\n
rtmedia/main.php\n\n\n\n\n\n\n\n
We have picked the Nouveau template for BuddyX for various reasons as following.
\n\n\n\nSummarizing features for BuddyX, you can check a detailed overview at buddyxtheme.com.
\n\n\n\nWe have prepared a couple of demos; you can try the BuddyX demo as a member login.BuddyX is available at WordPress.org for download to create your community; we will appreciate any feedback to improve BuddyX features.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Dec 2020 18:54: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: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:47:\"WPTavern: Mapbox GL JS Is No Longer Open Source\";s:7:\"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=108948\";s:7:\"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:139:\"https://wptavern.com/mapbox-gl-js-is-no-longer-open-source?utm_source=rss&utm_medium=rss&utm_campaign=mapbox-gl-js-is-no-longer-open-source\";s: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:9008:\"Mapbox GL JS, formerly an open source JavaScript library for interactive, customizable vector maps, has adopted a proprietary license in its recent version 2 update:
\n\n\n\nVersions 1.x remain under the 3-Clause BSD license, but Mapbox will only be investing in developing new features for the proprietary licensed version 2.0+. This news came as a surprise to many engineers who have built products on top of this previously open source library.
\n\n\n\n“This move has produced shockwaves in the geospatial industry,” Javier de la Torre wrote on the CARTO blog. “Many organizations are using Mapbox GL JS directly or fork from it. This library is responsible for the visualization of the so-called basemap, the cartography layer that underpins most maps. Previously Open Source, MapboxGL is a great solution, and could be used with many different data sources, so it became the de facto way to render basemaps.”
\n\n\n\nMapbox powers all sorts of maps for high profile websites like CNN, The New York Times, Ancestry, Strava, Shopify, Facebook, and more. It is also used by WordPress.com and Jetpack for the Map block. The library is used in many plugins on WordPress.org, some with tens of thousands of users. Developers using versions 1.x will want to be aware of the future of the Mapbox GL JS library.
\n\n\n\n“Mapbox’s decision this week to release a brand new version of Mapbox GL JS and keep it proprietary stunned me,” Azavea product specialist Joe Morrison wrote on his personal blog. “Not only was v1 already a wildly popular open source library, but Mapbox’s reputation as a prolific creator of open source software is a cornerstone of their whole identity. Describing what makes Mapbox special without mentioning ‘open source’ is like trying to describe chocolate milk to an alien without using the word ‘liquid.\'”
\n\n\n\n \n\n\n\nMapbox hasn’t formally clarified why it went proprietary with the library so speculation abounds. Morrison theorizes that cloud providers are killing the open core business model of software companies. Crunchy Data Geospatial Engineer Paul Ramsey responded to Morrison’s article, contending that Mapbox is not an “open core” company and that the business of selling location based services may not be panning out for them:
\n\n\n\n\n\n\n\nBut like Google, the value proposition Mapbox sells isn’t in the software, so much as the data and the platform underneath. Mapbox has built a unique, scalable platform for handling the huge problem of turning raw OSM data into usable services, and raw location streams into usable services. They sell access to that platform.
Mapbox has never been a software company, they’ve always been a data and services company.
Mapbox employee Saman Bemel Benrud said the company is finally moving to make its products sustainable:
\n\n\n\n \n\n\n\nThis change has the potential to negatively impact the developers and companies that built products on top of Mapbox GL JS, thinking its open source licensing was set in stone.
\n\n\n\n“The change says nothing about ‘open source’ in the large as a model, and everything about ‘single vendor projects’ and whether you should, strategically, believe their licensing,” Ramsey said.
\n\n\n\n“I (and others) took the licensing (incorrectly) of Mapbox GL JS to be a promise, not only for now but the future, and made decisions based on that (incorrect) interpretation. I integrated GL JS into an open source project and now I have to revisit that decision.”
\n\n\n\nSome community members have already forked Mapbox GL JS to maintain the 1.x version, but the vast majority of contributors to the original library were sponsored by Mapbox. The immediate future of the MapLibre GL fork may not include many new features, as the initial roadmap’s stated goal is “consistency and backwards-compatibility with previous releases and continued bug-fixes and maintenance going forward.”
\n\n\n\n \n\n\n\nA lengthy discussion on Hacker News drew a response from former Mapbox engineer Tom MacWright, who wrote the company’s open source policy as a founding member of the team.
\n\n\n\n“I won’t get into all the context, but I think we should consider whether a community without contributors is a community,” MacWright said. “GL JS never had major active contributors outside of the company, and there are no self-funded webgl experts with lots of time who are ready to maintain a fork.
\n\n\n\n“OSS, we hoped, was about enabling people and unlocking people’s ability to collaborate. It turns out that in 2020, it’s mostly helping companies and getting nothing in return. That’s not a dynamic you can build a sustainable business on.”
\n\n\n\nThe MapLibre GL fork may gain some momentum and emerge as a viable alternative to Mapbox’s closed source library, but it will take time to see how well it is maintained. In the meantime, the existing version 1.x can meet most users’ needs. Mapbox has burned through a lot of good will with this controversial licensing update, which some perceive as a “bait and switch” offense. Rebuilding community trust, after removing the freedoms granted by the previous license, will be an uphill battle.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Dec 2020 04:45:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"WPTavern: Jump Start Block-Based Theme Development With the FSE Theme Generator\";s:7:\"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=108900\";s:7:\"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:203:\"https://wptavern.com/jump-start-block-based-theme-development-with-the-fse-theme-generator?utm_source=rss&utm_medium=rss&utm_campaign=jump-start-block-based-theme-development-with-the-fse-theme-generator\";s: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:4913:\"Block-based themes are not complicated. Their structure is almost simple enough that developers are unlikely to need a tool to generate a blank theme. However, for those unfamiliar with how themes are built for the upcoming full-site editing (FSE) feature, a boilerplate is a good place to start.
\n\n\n\nThe Theme Experiments repository now has a new Empty Theme. Alongside it is a command-line tool to generate a copy of that theme with a custom name, author, and URI.
\n\n\n\nThe idea is not new. There are tons of such tools for generating a theme in the wild. However, it is time for new tools that focus on block-based theming.
\n\n\n\nFor theme authors who want to generate a new block-based theme, they must clone a copy of the Theme Experiments repository. Then navigate to that folder via their command-line tool and type the following command:
\n\n\n\nphp new-empty-theme.php
\n\n\n\nFrom that point, it is a simple matter of answering a few questions and letting the tool do the work of creating a new theme folder.
\n\n\n\nThe generated theme is not much to look at. However, it is a theme that works within the new full-site editing system. After activation, theme authors can begin tinkering with the theme via the Site Editor screen (requires the Gutenberg plugin).
\n\n\n\nThere is one exception to it being a working theme. Loading the header template part is currently broken. Of course, I opened a ticket for that issue, which should be easy for the development team to resolve.
\n\n\n\nThe file and folder structure is slim in comparison to traditional themes. It contains the bare-bones to get a theme up and running in the Site Editor. The following files and folders are included:
\n\n\n\n/assets
alignments-front.css
/block-template-parts
header.html
/block-templates
index.html
singular.html
experimental-theme.json
functions.php
index.php
readme.md
style.css
Even those are likely to be trimmed down in the future. The experimental-theme.json
file will eventually be renamed to theme.json
.
The current alignments-front.css
is nearly 80 lines of boilerplate code for handling the various block alignments. There is no need for every theme author to recreate all of this code, which should not change much between themes. That is why there is an open ticket for Gutenberg to provide alignment styles on the front end. Theme authors will be able to overwrite this. However, the fewer files and lines of code theme authors need to contend with, the better.
The standard index.php
template is empty. It will no longer be useful for building themes now that block-based templates are stored in the /block-templates
and /block-template-parts
folders. style.css
just houses the theme information. FSE themes will mostly use theme.json
to configure default styles.
In the coming months and years, theme authors will be working primarily in the theme.json
file and block template folders. The jury is still out on whether the theming ecosystem will readily accept this change. At the same time, it feels refreshing to see the untangling of theme development. Traditional theming today has created behemoth codebases in an attempt to keep up with features that users want. A shift in how developers build themes was inevitable and necessary.
My one nit-pick with the generated theme is the inclusion of the pluggable theme setup function in the functions.php
file, which has somehow become a mainstay of core-developed themes over the years. There are APIs for enabling or disabling everything in such setup functions, and there is no reason for child themes to overwrite them wholesale.
If things go according to plan, even the standard theme setup function may be on the chopping block. These functions are generally a list of calls to add_theme_support()
. The long-term plan is for the current theme-supported features to either be enabled by default for block-based themes or configurable via the theme.json
file.
When I was asked to write an essay for HeroPress, I humbly accepted due to my desire to help others. HeroPress needs a post and perhaps something I say could have a positive impact on another person. Little did I realize that having to write as a “marginalized” individual would cause me to want to retreat.
\nThe word “marginalized” stirs up a lot of emotion in me and thoughts such as “am I marginalized enough”, “what if I offend someone”, and “will I be attacked” tend to come to mind. Interestingly, I worry that I’ll be attacked by more women than men. I could easily write the story of my woes because I’ve had plenty but I like solutions, perseverance and resilience better. Some of these solutions may help you realize why I could be seen as “marginalized” but perhaps we’ll find a new label such as human and worthy of kindness, trust, inclusion, and a seat at the decision table.
\nI have been in the WordPress space since 2005 and tech since 2003. My team realized early on that WordPress was actually a CMS. We ranked #2 in google for web design back when SEO was easy. I was answering phones, marketing, and doing billing at that time. I would ask about budgets when potential clients would call and I had to turn away a lot of business because they couldn’t afford us. The worst part was that I didn’t have a trusted company that I could refer them to at the time. While focusing on web design I couldn’t understand why it took so long to create a website and why we couldn’t create our own less expensive solution to offer them.
\nLong story short, a prototype was made, then refined and rebranded as Pagely, and the term “Managed WordPress Hosting” was created. It was about 2 years later that our next competitor arrived and another 2 years for the behemoths to create their own managed WordPress solutions. Sounds grand right? Being the first and the originator of a multi-billion dollar industry had its challenges and these are problems that our competitors didn’t have to face. Now, let’s add being a female.
\nI feel that I need to preface these next parts of my life story mainly because I’m a female and it’s what I’ve been trained to do even subconsciously. I’m joking, sort of.
\nUsually if I use a word that doesn’t resonate with certain males, I’ll get mansplained to instead of searching for clarity. Their initial jump to assume that “I don’t know” instead of “they don’t understand” astounds me. That’s not to say I am infallible, didn’t say something ridiculous, or am unwilling to learn/self-reflect. It’s unnerving when Captain Obvious brings forth the basics.
\nThat being said, first, I understand that my labels include female, white, American, founder, wife, mother, wealthy, privileged and more depending on who I’m talking with. It took years of therapy to take my own traumas seriously because I didn’t have it as bad as others. It caused me to repress my own experiences and put others before myself even when they didn’t deserve space in my kind mind. Now, I’m more resilient and realize that I can’t be everything to everybody but I can include everyone with exception of the unhinged.
\nSecond, this is my story. It may not be similar to your own, and I don’t have all the answers. I’m not competing with anyone’s troubles. We can both exist.
\nThird, I’m very grateful because I have been surrounded mostly by successful women and men willing to help Josh and I accomplish our shared goals. Josh is my husband and co-founder of Pagely.
\nWhen Pagely first started, hate mail ensued along with many people signing up. I went to a WordCamp and a prominent figure in the WordPress community asked me where the person was that came up with Pagely because they really liked it. They were alluding to my husband Josh. This happened even when Josh said repeatedly that I had come up with the idea. It was at that moment that I realized that most people would not associate me with the idea or company I co-founded.
\nI had to make the conscious choice to decide if I wanted to be right or be successful. I chose to focus on success and also I didn’t get here alone. Many wonderful men and women helped. I had to laser focus on my goal which was to provide the best hosting experience regardless of minor annoyances along the way.
\nMany times I was not invited to join various non-Pagely meetings. Josh tried to include me even when men told him to uninvite me. Luckily, when I wasn’t allowed in the room, Josh shared the agenda with me and many times was my voice to get things done. Now, if I’m not included, I find a table that will have me, find allies, or I create my own group. I shouldn’t have made getting in that room a big priority. My solution was to remove obstacles, find the win/win to achieve my goal, and not take or make it personal.
\nThis type of scenario happened often and what’s interesting is that the people that were saying these “sexist” remarks were good people. The problem was so prevalent and complex that I had a hard time communicating what I was experiencing.
\nI asked other women how they handled sexism. I asked a brilliant and well respected female entrepreneur in Phoenix how she handled what I was experiencing. She told me that she saw it all the time and just treated men like her children and gave accolades. She was included because she could stroke their egos. Another friend said that she would wear short skirts so she wouldn’t have to explain and defend why her ideas deserved merit. Another friend would wear business attire daily while her male cohorts wore hoodies. Her brain didn’t change but their outlook did. There were also some that claimed that they didn’t experience it but when the #metoo movement arrived, they were the most vocal. Of course, this is an extremely small subset of people I asked but this was the reality of the time.
\nWhat’s striking is that my experience in other fields was worse. At least in tech we’re open to talk about and acknowledge the issue. It’s a start, it’s getting better, and tech attracts early adopters. When I was in healthcare, I graduated college with summa cum laude honors. I had the highest board scores in the state for my field, yet one employer told me I was only hired because I was pretty, another place said that they prefer to hire Mexicans because they work harder, and another place claimed that they like to hire females that didn’t plan on having children.
\nSo many check marks to obtain which can cause females to compete with each other because of a feeling of lack of abundance and no defined rules.
\nThese learnings from the places I worked happened over a period of time and some of my friends experienced sexism and abuse weekly. They were used to being treated poorly and considered less than. They accepted the situation and were grateful for the opportunity to work. Some were afraid to have or share their brilliant ideas because their paycheck was more important than their voice. Also, some were content and had other areas of their life that fulfilled them or they were ultra-resistant. The vast differences we have with one another are amazing, beautiful, and inspiring.
\nI still have mixed feelings about being the token female. I was asked to speak on a SXSW panel a couple of times because I was the only tech female the person knew. I’m trying to get comfortable using my gender to get through the guarded gates but I can’t tell if I’m fostering inspiration, adding to the separation, or devaluing my accomplishments. Therefore I tend to stay private and stay focused on creating my ideal work environment that waterfalls over into giving the best hosting experience for our clients. Also, when I ask other women to speak at Pressnomics or work with me at Pagely, I don’t want it to be because I’m trying to hit a quota.
\nI choose to work with women because they are qualified. Our engineering team is 50% female and our largest teams are run by women because they were the most qualified candidates. Period. (pun intended). What makes this even more gratifying for me is that the entire team participates in the hiring process and it feels like we have an environment for equality that is natural due to the character of the people we hire.
\nHowever, we have hired men and learned that they are triggered by assertive females. My solutions in these instances include making sure they realize the issue, what’s at stake if they don’t change, and I leave my door open to conversation. They are still good people. They chose to have a female employer. My general causation theory is the stigma around therapy especially for men, lack of resources to provide a public mental health safety net, repressed feeling of childhood powerlessness from a female, and myriad other possibilities.
\nThe flip side to this is aggressive females which also afflicts me at certain times. My progression to aggression looks something like the following. I start with casual understanding, then I ask questions for full understanding. Then I assert, re-evaluate, assert or accept. If I don’t accept, I assert again. If my assertions don’t work, aggression can happen followed by reflection. This may lead to a desire to remove the obstacle and find another solution or evaluate the origin of my aggression. This doesn’t happen often. I’ve learned that I’m triggered by feeling unseen or unreciprocated respect when I have a strong desire for an outcome that seems heavily challenged. I accept these feelings and understand that I’m not always right. The awareness allows me to seek clarity, speak up with vulnerability, heal, and choose a healthier approach that humanizes the relationship.
\nMy ideal solution is to remind myself that everyone has a story, listen to their story, find clarity, and let them know they are safe and don’t need to carry the trauma anymore. Open communication with mutual respect is key. You get what you give. Also, burning bridges serves no one and neither does passively laying on train tracks.
\nAnother one of my theories is that women are considered safe. During our Pressnomics conference, Josh will receive more praise and while I do get praise, I tend to get more (or all) of the criticism. This is not about getting praise; although appreciated, it’s not the point. It’s about why people feel more comfortable expressing negative emotions to females. I believe the reason why is because women seem safer and they are more likely to ask about experiences.
\nUnfortunately, this can open a floodgate from people with varying levels of passion which can cause female entrepreneurs to retreat from taking more active roles. I crave feedback for Pagely because it’s something we want to give to the world. However, Pressnomics is an invitation into my proverbial house and if they don’t like it, there’s a lot of other conferences they can attend or make their own. I’ll gladly attend their conference, especially if it’s run by another “marginalized” human and aligns with my goal. I will listen to people who “get” what Pressnomics is (it’s more of a feeling) but nitpicking my font and color choice for the website is where I draw the line.
\nI had to get to this place because people were not going to decide my worth or determine if my creations were good enough. When I create, I come from love and a deep desire to help with the golden rule in mind. I’ve been to other conferences, where Josh leaves my side and men have said “I’m creating a Pagely killer”, “We’re going to destroy you”, and competitors that are actively trying to debate with me while my only intention was to be kind.
\nMy goal with Pressnomics is to inspire great minds to work together, share information, and energize the WordPress ecosystem in a safe and caring atmosphere for all who attend.
\nMy ideal solution when dealing with negative people is to not take it personally. Their truth does not need to be my truth and words from jerks no longer have an affect on me. Sadly, most jerks delve out disdain regardless of the recipient which means they might be miserable and lack empathy.
\nWhat does WordPress mean to me? It’s a business foundation that allows ALL people the initial building blocks for success. The barrier to entry is low and inclusion is high. Also, the majority of people in the community look past stereotypes and generalizations and want to share and lift all tides. I am very grateful to the community, our supporters, the dreamers, and to the outstanding core contributors.
\nWhat do all of us “marginalized” people have in common? We showed up and worked around obstacles. If there’s not room for you at a table, figure out something else. Perhaps, kindly discuss the observation, or create your own table. Life’s too short to be unhappy in someone else’s world. Create your own and invite others. WordPress is a great place to do that.
\nLast, being underestimated is a gift. They’ll never see you coming until they can’t help but notice. If you’re with the right people while that’s happening, there’s no better feeling.
\nThe post Marginalized 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, 16 Dec 2020 10:02:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sally Strebel\";s: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: Learn WordPress Platform Launches with Free Courses, Workshops, and Lesson Plans\";s:7:\"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=108957\";s:7:\"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/learn-wordpress-platform-launches-with-free-courses-workshops-and-lesson-plans?utm_source=rss&utm_medium=rss&utm_campaign=learn-wordpress-platform-launches-with-free-courses-workshops-and-lesson-plans\";s: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:3567:\"WordPress.org has officially launched its new “Learn WordPress” platform, a free educational resource that includes courses, workshops, quizzes, lesson plans, and discussion groups. The material spans the spectrum of WordPress experience from beginners to advanced, and and allows users to learn asynchronously at their own pace. After a successful beta launch in August, the platform is now ready for the public.
\n\n\n\nTraditionally, most WordPress learning opportunities have been in-person at WordCamps and local meetups. Since large gatherings have been put on pause this year due to the pandemic, the Learn WordPress platform offers a new way for users to stay connected. The discussion groups are a new event format similar to a virtual event that brings learners together at the same time to discuss a topic. Discussion groups are scheduled through Meetup.com and most of them center around workshop material.
\n\n\n\n“In addition to the wealth of valuable content available on Learn WordPress, the platform provides an opportunity for individuals to learn alongside other community members and become connected with a global network of WordPress users, developers, and contributors,” WordPress community manager Hugh Lashbrooke said.
\n\n\n\nLearn WordPress is launching with two courses: “Publishing with WordPress” and “Unleashing the Power of WordPress,” which covers basic customization topics. The project is open to contributions and anyone can submit an idea for a workshop.
\n\n\n\nThe platform also includes more than 85 lesson plans that the Training team has been working on for the past few years. They are available as resources for people who want to run their own workshops.
\n\n\n\nLearn WordPress has several lesson plans and workshops on the topic of creating new blocks, such as Intro to Gutenberg Block Development. Many WordPress developers have yet to get on board with creating for the block editor and topics like this seems ripe for launching a discussion group with a series facilitated by an experienced block developer.
\n\n\n\n“The work on Learn WordPress has been a strong cross-team collaboration between the Community and Training teams, with the Marketing and TV teams also being really involved in making things happen,” WordPress community manager Hugh Lashbrooke said. “It’s been super encouraging to see such excellent work across so many teams to make this ambitious project a reality.”
\n\n\n\nAnyone can contribute to lesson plans and workshops, as well as facilitate discussions. If you want to get more involved in expanding and promoting the platform, you can join WordPress’ Training team for meetings on Fridays at 11:00 UTC and Tuesdays at 17:00 UTC in the #training channel on Slack.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Dec 2020 23:30:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"WPTavern: Record and Track Past Events With the LifePress Calendar 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=108962\";s:7:\"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/record-and-track-past-events-with-the-lifepress-calendar-plugin?utm_source=rss&utm_medium=rss&utm_campaign=record-and-track-past-events-with-the-lifepress-calendar-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:4784:\"Two weeks ago, Ashan Jay released LifePress to the WordPress plugin directory. It is an interactive, front-end calendar for tracking past events — a journal of sorts. For a version 1.0 launch, it has enough features with just the right touch of simplicity to show promise.
\n\n\n\nThis is not Jay’s first rodeo when it comes to calendar-based plugins. He is also the creator of EventON, a virtual event calendar for WordPress.
\n\n\n\nThe goal of the plugin is simple. As its description reads, “LifePress is a calendar based journal recorder that will allow you to track back progress and review past events to learn from the past and make positive progress in the future.”
\n\n\n\nWatch an introduction video to the plugin:
\n\n\n\n \n\n\n\nCall me a fan. The ease of use of this plugin is spot-on. LifePress creates a page called “LifePress Dashboard” upon activation, which allows individual users of the site to see and manage life events on the front end on a per-user basis. It feels much like Google Calendar, except in WordPress.
\n\n\n\nAnd that is the plugin’s main selling point — it allows end-users to store all of their data in their own database instead of on a third-party server.
\n\n\n\nOn the front end, users are presented with a weekly calendar view by default. However, there is a button for switching between weekly and monthly views.
\n\n\n\nA simple “+” button lets users create new calendar entries. After clicking it, an overlay appears for adding a date, title, optional description, and tag. Most users should pick up the system quickly and without documentation.
\n\n\n\nThe tag system allows users to group different types of entries with custom colored backgrounds. Colored dots for each tag adorn the left sidebar, allowing users to toggle specific entry types on and off, which is one of my favorite features of the plugin. It is a simple thing, but it adds to the overall user experience.
\n\n\n\nThe design is, for the most part, great. The interface is uncluttered and simple to use. However, the plugin is not without some flaws, which is to be expected with a version 1.0. The plugin’s various overlays, such as from the new-entry popup, butt against the top of the page. Some spacing at the top would help with the layout.
\n\n\n\nBackend management could use a little work. There is no way to edit a tag’s color after it has been created. This feature also does not appear to be available on the front end.
\n\n\n\nThe monthly-calendar view was consistently off by one day of the week when I first installed LifePress in my testing environment. For example, today is Tuesday, December 15, 2020. However, the plugin had the 15th listed under Monday. I managed to track this issue down to the “week starts on” setting in WordPress. The plugin will only work if this option is set to Sunday (the WordPress default sets this to Monday). Every other day of the week pushes the calendar back another day.
\n\n\n\nThis is a non-issue with the default, weekly calendar view. However, it should be addressed by the plugin author for the monthly layout.
\n\n\n\nWhile LifePress is geared toward being a journal and tracking calendar, it would be nice if it could pull double-duty and behave like a simple event calendar too. The plugin already allows end-users to add items to future dates, so the core of scheduling events is already in place. To extend this already-existing feature, the plugin could have a notification system. Users should be able to at least get custom emails as a reminder for upcoming events on the schedule. This could make it worthwhile enough for some users to ditch Google Calendar, depending on their use case.
\n\n\n\nIf the plugin wants to continue focusing on being a great journal and tracking calendar, it should have a progress-tracking mechanism built in. It is great to see that I put in my daily 30-minute jog on the calendar, for example. However, it would be even better if I could see that I am hitting my exercise goals on a weekly, monthly, or yearly basis.
\n\n\n\nThat sort of application is not just relevant to personal exercise regimens. It can be applied to other facets of life or used in business environments.
\n\n\n\nOverall, it is a good first outing for the plugin. However, there is a lot of potential for more features in the future.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Dec 2020 21:48:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:47:\"WordPress.org blog: Introducing Learn WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9444\";s:7:\"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://wordpress.org/news/2020/12/introducing-learn-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9012:\"Learn WordPress is a learning resource providing workshops, quizzes, courses, lesson plans, and discussion groups so that anyone, from beginners to advanced users, can learn to do more with WordPress. Learning how to use, build for, and contribute to WordPress is essential for anyone wanting to dive deeper into the software and its community.
\n\n\n\n \n\n\n\nThis cross-team initiative is part of the WordPress.org network and features content from contributors from the global community. It will be updated weekly and will help connect new and existing WordPress users with the broader community while they learn.
\n\n\n\nOn Learn WordPress you can find a range of material and opportunities to use at the time which works for you.
\n\n\n\nWorkshops are practical, skills-based videos that show viewers how to do new things with WordPress, whether you publish, manage, develop with, or contribute to WordPress. Most workshops include quizzes for you to test your newly gained knowledge.
\n\n\n\nDiscussion groups provide an opportunity for further collaborative learning with participants meeting together to discuss the workshop content – they take place online, either in video calls or Slack and accommodate all time zones.
\n\n\n\nLesson plans are guides for facilitators to use while presenting at events or within educational environments. Facilitators will find learning objectives (telling people what they are going to learn), any prerequisite skills, assets such as screenshots and slide decks, and learning assessments.
\n\n\n\nCourses are a series of interconnected lesson plans to be presented by a facilitator that will strategically focus on defined learning outcomes. Participants can go through these courses individually or as part of a group. After completing the learning, attendees should be able to apply their skills in the real world.
\n\n\n\nIn addition to the wealth of valuable content available on Learn WordPress, the platform provides an opportunity for individuals to learn alongside other community members and become connected with a global network of WordPress users, developers, and contributors.
\n\n\n\n \n\n\n\nWhy you should use Learn WordPress – videos from our community.
\n\n\n\nLearn WordPress is an open-source platform available for anyone to contribute content in any areas mentioned above. Find out more about how you can get involved with this initiative.
\n\n\n\nTake part in our fun promotion campaigns on social and with your local community.
\n\n\n\nHundreds of people spanning a number of years have contributed to the development of learning materials. Thanks to everyone who worked so hard to make Learn WordPress a reality.
\n\n\n\nParticular thanks to:
\n\n\n\nTraining: @courane01, @azhiyadev, @geheren, @webtechpooja, @jessecowens, @onealtr, @rastaban, @evarlese, @manzwebdesigns
Meta: @coreymckrill, @dufresnesteven, @jonoaldersonwp
Community: @hlashbrooke, @camikaos, @harishanker, @angelasjin, @nao, @courtneypk, @andreamiddleton, @rmarks, @sippis
Marketing: @webcommsat, @oglekler, @lmurillom, @yvettesonneveld, @meher, @nalininonstopnewsuk, @megphillips91, @marks99, @marybaum, @antialiasfactory, @herculespekkas, @chaion07
Design: @melchoyce
For a fuller list of the contributors who have been involved in training and Learn WordPress, visit the initial beta launch post. Thanks to everyone who has been involved to date and will be in the future.
\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Dec 2020 13:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s: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:62:\"WPTavern: Fast Brings One-Click Checkout to WooCommerce Stores\";s:7:\"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=108895\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:169:\"https://wptavern.com/fast-brings-one-click-checkout-to-woocommerce-stores?utm_source=rss&utm_medium=rss&utm_campaign=fast-brings-one-click-checkout-to-woocommerce-stores\";s: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:7203:\"Fast, a startup backed by Stripe, has just added WooCommerce support to its new Fast Checkout experience. The company was co-founded in March 2019, by Domm Holland and Allison Barr Allen, with investment from Stripe, Index Ventures, Susa Ventures, and Global Founders Capital. It has received $22.5M in funding to reduce the friction that remains deeply embedded in login and checkout experiences.
\n\n\n\nOnline shopping almost always involves a lengthy checkout form where customers have to enter passwords, addresses, and payment information nearly every time. This tedious experience is magnified when gift-giving holidays roll around. Fast’s founders have set out to solve this problem with products aimed at modernizing the checkout experience to enable one-click purchasing.
\n\n\n\nFast Checkout launched in September 2020, so if you haven’t seen it around yet it’s because it is relatively new and was previously limited to a handful of platforms. Expanding support to WooCommerce was a strategic move, as WordPress accounts for 39.3% of the Alexa top 10 million websites. WooCommerce is running on 18% of the WordPress sites W3techs can detect. Fast CEO Domm Holland said the product’s availability to WooCommerce increases the company’s addressable market by over 2,500%.
\n\n\n\n \n\n\n\n“We’ve received inquiries from thousands of sellers asking to add Fast on a variety of e-commerce platforms, including WooCommerce sellers,” Fast CCO Jason Alderman said. “We prioritized WooCommerce as it automatically gives millions of new sellers access to Fast.”
\n\n\n\nThe company has seen a strong uptick in Fast Login adoption since launch, and Fast Checkout has had a promising debut.
\n\n\n\n“For Fast Checkout, the value of merchandise purchased on the platform has more than tripled each month since launching in September,” Alderman said. “Although not WooCommerce sellers, Fast merchants such as Gerard and Hardwood Lumber are seeing up to 30% (and rising) adoption rates since deploying Fast Checkout and up to a 10% increase in order volume within just 30 days of implementation.”
\n\n\n\nIn order to gain all the benefits of Fast login and checkout, users have to sign up with a new service, which seems like it would be hurdle. Fast has embedded this process within the normal checkout flow so that it doesn’t feel like the consumer has to sign up for something new. The first time a shopper makes a purchase on a site using Fast Checkout, they enter their contact information. and payment details as they normally would.
\n\n\n\nAfter that purchase, their details are stored and every subsequent checkout experience on any website using Fast Checkout will only require one click. It works regardless of the device or browser used and does not require a password, the same as the Fast Login product.
\n\n\n\nAlthough Fast Checkout and Login are free to use for buyers, getting store owners on board is going to be the primary challenge for Fast. It charges US sellers 2.9% + 30c per transaction. Fast’s fees are not quite as steep as the 5% per shipment that Instagram will be charging for the new Shopping Checkout feature that WooCommerce is testing. However, it may still be prohibitive for stores with narrow profit margins. Fast also has competition from the multiple one-click checkout extensions available for WooCommerce that do not charge transaction fees.
\n\n\n\nFast claims that the one-click checkout button “increases conversion, boosts sales, and delights customers” If the checkout experience can deliver on those claims, then some store owners may be willing to part with the 2.9% fee in order to capture a larger percentage of the potential customers that are already arriving at their stores, instead of risking cart abandonment with a frustratingly long checkout process. Store owners are looking for any edge in an increasingly competitive landscape where the online retail giants continue to dominate.
\n\n\n\nThe pandemic has caused radical shifts in the retail industry, creating unprecedented opportunities for independent stores. Many WooCommerce developers and store owners have sought help for optimizing their stores after the pandemic caused business to increase exponentially overnight. A product like Fast Checkout is landing at the right time, as consumer spending habits have become forever altered by the rapid acceleration of the essential role of e-commerce for homebound people across the globe.
\n\n\n\n“E-commerce giants have heightened consumers’ expectations for online shopping,” Alderman said. “And with the COVID-19 pandemic this year, more people than ever opted to shop online, but many independent businesses were not prepared to prioritize the online experience. By adding Fast Checkout to their stores, businesses of all sizes can access one-click checkout that offers the seamless experience consumers expect (and eliminates shopping cart abandonment that happens to up to 80% of potential purchases).”
\n\n\n\nFast is planning to expand its Checkout support to multiple new platforms in the coming months but did not have any details to share at this time. In addition to providing one-click checkout, Fast centralizes purchases across stores so that users can manage transactions, track shipments, and handle returns through a unified dashboard. Long term, the company is working on launching a universal subscription manager, which Alderman said is currently in development.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Dec 2020 06:18:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:75:\"WPTavern: G2 Components, a From-Scratch Reimagining of WordPress Components\";s:7:\"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=108342\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/g2-components-a-from-scratch-reimagining-of-wordpress-components?utm_source=rss&utm_medium=rss&utm_campaign=g2-components-a-from-scratch-reimagining-of-wordpress-components\";s: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:7356:\"Update some of the things.
\n\n\n\nThat was the goal that Jon Quach, a Principal Designer at Automattic, laid out in the roadmap for integrating the G2 Components project into Gutenberg and, eventually, core WordPress. The project is a reimagining of the pieces that make the block editor, a “from-scratch” overhaul of the component system. Updating all of the things or even many of the things at once runs the risk of breaking everything.
\n\n\n\n“Ideally, what should happen is you should update just some of the things in a very controlled and intentional manner,” wrote Quach in the post. He likened it transitioning a city, section by section, to solar power until the traditional power factory could be shut down. You convert one piece, test, find problems, and correct them before moving to the next section.
\n\n\n\nThat is the plan for integrating G2 Components into Gutenberg.
\n\n\n\n“G2 Components is a project that embodies the idea of making user interfaces and user experiences better for others,” said Quach. “At the moment, it’s materialized as a Component System designed to work within the context and environments of Gutenberg and WordPress.”
\n\n\n\nThe goal is to provide the resources to improve the Gutenberg project’s UI. Components should make it easier to create newer UIs without hacking together code. Quach said the consistency and experiences of the Component System should scale and have a ripple effect throughout the WordPress platform. This will also extend to third-party block developers.
\n\n\n\n“The code components are just the starting point,” he said. “My ultimate goal is for this to transcend code and influence and elevate design as well — creating a unified Design System that enables and empowers folks to craft cohesive and feature-rich UI experiences within the world of WordPress.”
\n\n\n\nQuach believes that platforms have benefited from having similar approaches. He mentioned Material Design by Google as having elevated the Android platform and bringing cohesion across the company’s products.
\n\n\n\nThe Gutenberg team has already started integrating the G2 Components into the project. This integration replaces WordPress components (@wordpress/components) in a controlled manner that should not break existing implementations within the core editor or third-party projects. New components will be swapped in as they become ready. “Like flipping on a switch,” said Quach.
\n\n\n\nThe following video is an hour-long walkthrough of G2 Components that Quach posted on YouTube:
\n\n\n\n \n\n\n\nHe routinely posts updates on the G2 Components blog. Alongside those are deeper dives into his design thinking on the project. He also talks about the project on his Twitch stream almost daily.
\n\n\n\nComponents are everything from buttons to toggles to checkboxes. They are standardized pieces that make up the UI of the block editor. They are available for both core and third-party developers to create what end-users see and interact with. However, there was a problem with how the original component system was built.
\n\n\n\n“The current components aren’t built with a system in mind, but rather, to fulfill an immediate need,” said Quach. “This particular design detail is crucial. A systems-first approach more easily supports the addition of new features, and more importantly, customization!”
\n\n\n\nThe new approach is about building a native design system for WordPress. Such a system would allow anyone to build on top of it and create native experiences.
\n\n\n\nQuach said one of the easiest ways to look at this is from a backend theming perspective — the Component System also has a theming sub-system. “Instead of the traditional method of writing CSS as a ‘skin’ to layer on top, UI aesthetics can be adjusted through configuration values — similar to how WordPress can be configured with definitions in the wp-config.php
file,” he said. “This distinction is important as these values tap directly into the Style system, allowing the styles to load correctly at the right place and at the right time. All without affecting the current environment’s styles, and more importantly, not being affected by the current environment’s styles.”
He was responding to my question on why the component system should be rebuilt from scratch. The idea is to have components that “just work” in an environment such as the WordPress admin, such as making sure the existence of a WordPress theme’s stylesheet does not break components simply by being loaded.
\n\n\n\n“Why rethink, rebuild, and enhance Inputs, Buttons, Modals, Dropdowns, and others?” countered Quach in response. “So that you the developer don’t have to.”
\n\n\n\nRespecting backward-compatibility is something Quach said he took incredibly seriously when designing the architecture of the G2 Components project. He also said it was a part of the integration strategy he proposed.
\n\n\n\n“I had mentioned that this project ’embodies the idea of making user interfaces and user experiences better for others,\'” he said. “Accounting for backward compatibility and supporting third-party migration absolutely falls under the category of user experience.”
\n\n\n\nAs the Gutenberg team continues integrating new components, it should not change what developers have already been doing. However, it could open up some new possibilities.
\n\n\n\n“The new Component System will definitely help in the UI department,” said Quach. “One area I’m particularly excited about is the rapid-development/prototyping space. Because these Components are self-contained units, they can be brought into platforms like CodeSandbox and they…just…work. You can hit the ground running and rapidly construct and share prototypes (ranging from tiny-yet-mighty to large and in-charge).”
\n\n\n\nHe said he has had success in testing component designs and demonstrating ideas for quick feedback. He has also worked from the opposite direction, building complex components in CodeSandbox and bringing them back into the Component System.
\n\n\n\n“As a designer and front-end developer, I cannot stress how efficient, effective, and creatively liberating this ‘micro building’ workflow is,” he said. “It’s something I’m excited for others to experience as well.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 14 Dec 2020 21:10: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: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:99:\"WPTavern: BuddyPress 7.0.0 Adds 3 New Blocks and Admin Screens for Member and Group Type Management\";s:7:\"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=108753\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:239:\"https://wptavern.com/buddypress-7-0-adds-3-new-blocks-and-admin-screens-for-member-and-group-type-management?utm_source=rss&utm_medium=rss&utm_campaign=buddypress-7-0-adds-3-new-blocks-and-admin-screens-for-member-and-group-type-management\";s: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:3149:\"BuddyPress 7.0.0 “Filippi” was released this week, following WordPress 5.6 to ensure compatibility. This version was named for Filippi’s Pizza Grotto in California. It requires WordPress 4.9+, but sites that are not using the block editor will miss out on many of the new features that make BuddyPress websites easier to customize.
\n\n\n\nThe first set of community blocks was introduced earlier this year, allowing site owners to insert a specific Member or Group into any post or page. Version 7.0.0 adds three new blocks that make it easy to feature a list of members, a list of groups, or embed a public activity post.
\n\n\n\nBlocks make customizations easier for non-technical community managers. Years ago, you would have to write a custom query to display members, groups, or activities anywhere on a page or post. The other option was to install a plugin to do it and use a widget or shortcode to place it somewhere in the content.
\n\n\n\nThe Groups block, for example, lets you select any number of groups using auto-complete, to create a custom list. The block’s toolbar has an option for displaying the groups in a list or a grid. In the block settings, users can show or hide group names, select full or thumbnail versions for avatars, and include extra information about the group.
\n\n\n\nBuddyPress’ member types and group types are a feature similar to WordPress’ custom post types. They now have their own management screens in the admin, making them more accessible to community managers who would not be comfortable creating and modifying types without a UI. Member and group types can now be added, edited, and deleted directly in the admin.
\n\n\n\n Source: BuddyPress.org 7.0.0 release announcement\n\n\n\nVersion 7.0.0 introduces the capability to add a default profile image for sites in a multisite network as part of the Site Tracking component. This can improve the appearance for the sites directory or the activity stream, when networked sites have not added a custom profile image.
\n\n\n\nA few other notable improvements in 7.0.0 include the BP Nouveau template pack updated to be compatible with the new Twenty Twenty-One default theme, improvements to the BP REST API, and BuddyPress CLI commands expanded to cover more aspects of community management. Check out the release notes for a full list of changes.
\";s: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, 12 Dec 2020 04:09: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: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:82:\"WPTavern: EditorPlus 2.4 Released, Builds Upon Its ‘Extend Core Blocks’ 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=108825\";s:7:\"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:195:\"https://wptavern.com/editorplus-2-4-released-builds-upon-its-extend-core-blocks-system?utm_source=rss&utm_medium=rss&utm_campaign=editorplus-2-4-released-builds-upon-its-extend-core-blocks-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:5285:\"On Tuesday of this week, Munir Kamal released version 2.4 of his EditorPlus plugin. Aside from a few bugs and making sure the plugin was compatible with WordPress 5.6, he added an icon selector for the Button block and SVG shape overlays for the Image block. This is on top of a new “Extend Core Blocks” system he added in the previous version.
\n\n\n\nI last dove into the plugin in early November. In Kamal’s world, that may as well have been a lifetime ago. At an almost dizzying pace of development, he has since released three major updates to the plugin with several new features. I continue wondering where he not only finds the time to dedicate to the project for free but also where he keeps getting new ideas. Surely, some of them are coming from his growing user base. The plugin is still relatively young, and it has now passed 2,000 active installs.
\n\n\n\nWhen Kamal first built EditorPlus, the idea was to create additional styling options for the WordPress core blocks. Essentially, the plugin allowed end-users to set custom values for CSS properties from an interface in the editor. This can get the average user pretty deep into customization. However, it is still somewhat limiting. There are things that web developers can do with code that go beyond what such a basic interface can do. The question then becomes: how do you provide those advanced methods to users?
\n\n\n\nAt the heart of the Extend Core Blocks system, which can be disabled from the plugin’s settings screen, the plugin author wanted to push the limits of what is possible with WordPress’s existing blocks.
\n\n\n\n“There are different extensions in EditorPlus that offer different features that you can toggle on or off,” said Kamal. “Like the styling, animations, custom CSS, etc., and now this new one. This extension will offer additional functionalities/features for the core Gutenberg blocks. For example, the ‘list block’ extended with the option to include icons, split into columns, and more. Similarly, the plan is to extend other core blocks with additional missing features as well.”
\n\n\n\nIn version 2.3, he created the first set of options with the new system. Starting with the List block, he added columns, options, icons, and several other options. Users can pick and choose from a range of icons from the Font Awesome and Icon Moon libraries.
\n\n\n\nMy favorite new feature is the custom “blob” styles Kamal has added to the Image block. “I’ve simply added 10 SVG shape masks as block styles for the core Image block,” he said while also sharing a demo video.
\n\n\n\nWhile I am unsure if I have any immediate uses for blob-shaped images, I am excited about the possibility of other SVG shape masks landing in the future. I am sure there are many potential applications in design where they would be useful. If nothing else, they are fun to tinker around with.
\n\n\n\nPerhaps a bit more practical, Kamal added new icon options for the Button block. Like the List block, users can choose from both the Font Awesome and Icon Moon libraries. They can also select left or right alignment, change the background and foreground colors, round out the background with a border-radius option, and control the spacing.
\n\n\n\nThere are a couple of other block-related plugins with similar icon options. However, having them baked into EditorPlus was a good decision. Most of the plugin’s users will likely find themselves ditching other block plugins with so much available through one.
\n\n\n\nKamal remained tight-lipped about any specific upcoming features in 2.5 and beyond. However, he did say that he would be continuing to build upon the Extend Core Blocks system. If his work thus far is any indication, it will be interesting to see what new options he brings to the other WordPress blocks.
\n\n\n\nWhile the new Extend Core Blocks system has been the focus of the last couple of releases, Kamal has added several other features. One of the biggest that he has pushed out is a set of new background options for every core block, which includes the following:
\n\n\n\nAt this point, with EditorPlus, users can nearly do anything they need to do with backgrounds. The biggest boost of customizability comes with the image URL option, which means that users can even input a data URI for SVG patterns. Hero Patterns has a ton of options to choose from for anyone who wants to give it a spin.
\";s: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, 11 Dec 2020 21:35: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:46;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"WPTavern: GitHub Introduces Darkmode, Discussions for Public Repositories, and Dependency Review\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=108775\";s:7:\"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/github-introduces-darkmode-discussions-for-public-repositories-and-dependency-review?utm_source=rss&utm_medium=rss&utm_campaign=github-introduces-darkmode-discussions-for-public-repositories-and-dependency-review\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3026:\"GitHub Universe, the company’s annual marquee product and community event, took place this week, bringing users a flurry of new features. Dark mode is now in public beta and can be activated under the Settings menu or set to follow system preferences.
\n\n\n\nDiscussions is a new feature that GitHub unveiled at its Satellite event in May to facilitate questions and open-ended conversations. The company has been testing it with open source communities like Gatsby and Laravel to iron out bugs ahead of the public launch. Discussions currently allows users to customize categories, transfer and pin discussions, and convert issues into discussion threads. Mobile support is coming soon.
\n\n\n\nParticipants on Discussions can search or sort conversations by newest, top, answered, and unanswered. Threads can be upvoted for better exposure and a sidebar widget displays the “most helpful” users. Discussions are essentially a modernized forum, with a little bit of gamification sprinkled in. for good measure.
\n\n\n\nProject maintainers for WordPress plugins, themes, and tools hosted on GitHub may want to explore Discussions to see if it could benefit their communities. The format is more approachable for less technical participants who may not be familiar with GitHub issues.
\n\n\n\nBuilding on the existing dependency graph and security alerts features, GitHub is introducing dependency review as a way to help developers catch vulnerable code before it gets added to their projects. Dependency review displays the following information for each pull request:
\n\n\n\nThe beta for the dependency review feature is now open to all public repositories and will be gradually rolled out across GitHub in the next few weeks.
\n\n\n\nOther notable announcements include the ability to auto-merge pull requests when using protected branches, improvements to continuous delivery support, and GitHub Sponsors for companies, which allows organizations to use their existing billing to donate to open source developers and projects. Check out the full details in the announcement summary from the event.
\";s: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, 11 Dec 2020 04:42:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"BuddyPress: BuddyPress 7.0.0 “Filippi”\";s:7:\"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=316067\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://buddypress.org/2020/12/buddypress-7-0-0-filippi/\";s: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:13194:\"This major release introduces new administration screens to manage your Member & Group Types
We are very excited to announce the immediate availability of BuddyPress 7.0.0 code-named “Filippi“. You 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\n If 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.
You can review all of the changes in this 7.0.0 release in the release notes. Below are a few of the key features we believe you are going to love!
\n\n\n\n\n\n\n\nPlaying with BP Types just became much easier! The Member Types and Group Types were primarily introduced in BuddyPress as features for advanced users, just like the WordPress Custom Post Type feature. Thanks to the two new WordPress Administration Screens, adding, editing and deleting Member & Group Types has never been so easy! Now you can set up BP Types using custom code or by simply using the Administration interfaces.
\n\n\n\nLet’s watch a demo about how it looks like for Member Types!
\n\n\n\nFullscreen\n\n\n\n\n\n\n\n3 new BP Blocks are now available via your WordPress Editor. From the BuddyPress blocks category of the WordPress Block Inserter, you can pick a BP Block to feature a list of members, a list of groups or embed a public BuddyPress Activity into your post or page. Read more about it in this development note.
\n\n\n\nHere’s a quick video showing you how to insert a list of Members profile images into your home page.
\n\n\n\nFullscreen\n\n\n\n\n\n\n\nThe Site Tracking component now has a default profile image it can use to make your Sites loop prettier if some of them have not customized their WordPress Site Icon. Multisite WordPress configurations will be able to find it when displaying the Sites directory. Read more about it in the development note.
\n\n\n\n\n\n\n\nYou love the latest default WordPress Theme, so do we! It’s important for us to make sure the BP Nouveau template pack looks great in the default themes included in the WordPress package. This is the first of the many improvements we are bringing to our default Template Pack.
\n\n\n\n\n\n\n\nThe Developer documentation has been updated according to the latest improvements we’ve brought to the BuddyPress REST API.
\n\n\n\nTo name two: get the groups the logged in user is a member of, and create a blog when BuddyPress is activated on a network of WordPress sites. Read this development note to learn about all the others.
\n\n\n\n\n\n\n\nWP-CLI is the command-line interface for WordPress. You can update plugins, configure multisite installs, and much more, all without using a web browser. In 7.0.0, you will be able to use new BuddyPress CLI commands to manage BuddyPress Group Meta, BuddyPress Activity Meta, activate or deactivate the BuddyPress signup feature and create BuddyPress-specific testing code for plugins.
\n\n\n\nDiscover more about it from this developer note.
\n\n\n\n\n\n\n\n7.0.0 includes more than 70 changes such as image lazy loading support, multiple Member Type assignment, a Docker ready development environment to improve your BuddyPress experience as users, and as contributors to our project.
\n\n\n\n\n\n\n\nAdil Oztaser (oztaser), Boone B Gorges (boonebgorges), Brajesh Singh (sbrajesh), corsky, Dan Caragea (dancaragea), David Cavins (dcavins), devnik,Dilip Bheda, Dion Hulse (dd32), dragoeco,Erik Betshammar (kebbet), etatus, Didier Saintes (ExoGeek), 诗语 (f2010525),George Mamadashvili, Giuseppe (mociofiletto), Hareesh,iamthewebb, Javier Esteban (nobnob), Jb Audras (audrasjb), John James Jacoby (johnjamesjacoby), Joost Abrahams (joost-abrahams), k3690, Knut Sparhell (knutsp), Laxman Prajapati, Lidia Pellizzaro (lidialab), marbaque, Marcel Claus (geckse), marioshtika,Mark Robson (markscottrobson), Mathieu Viet (imath), mercime, Meet Makadia, Michael Beckwith, Morteza Geransayeh (man4toman), morenolq, N33D, oddev56, Paul Gibbs (DJPaul), Petter Walbø Johnsgård (walbo), Peter Smits (psmits1567), Pooja N Muchandikar (pooja1210), Raruto, r-a-y, Renato Alves (espellcaste), scipi, Scott Bolinger (scottopolis), shanebp, shawfactor, sjregan, Stephen Edgar (netweb), tharsheblows, Tor-Bjorn Fjellner (tobifjellner), Varun Dubey (vapvarun) & wp24.cz (podporawebu).
\n\n\n\n\n\n\n\n7.0.0 is code-named “Filippi” after Filippi’s Pizza Grotto in lovely San Diego, California, USA. The “Grotto” is in the back room of an Italian grocery and butcher shop in Little Italy. Tall pizza lovers will have to watch out for the Chianti bottles hanging from the ceiling, but the red-and-white-checked-tablecloth atmosphere and piled-high pizza is worth it!
\n\n\n\n\n\n\n\nReceiving your feedback & 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:\"Thu, 10 Dec 2020 22:00: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: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: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:80:\"WPTavern: State of the Word 2020 Scheduled for December 17, with Virtual Q&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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=108628\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/state-of-the-word-2020-scheduled-for-december-17-with-virtual-qa?utm_source=rss&utm_medium=rss&utm_campaign=state-of-the-word-2020-scheduled-for-december-17-with-virtual-qa\";s: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:5941:\"WordCamp US 2020, previously scheduled for October, was cancelled due to pandemic stress and online event fatigue. Organizers did not opt for running it as an online event, but Matt Mullenweg’s annual State of the Word address will be delivered virtually this year. It will be streamed on Facebook, YouTube, and Twitter on Thursday, Dec 17th, 2020 at 1600 UTC.
\n\n\n\nIn previous years, the State of the Word has been one the most highly anticipated keynotes at WordCamp US. Attendees pack into the venue’s auditorium in anticipation of hearing about all of the highlights and milestones the WordPress community has achieved over the past year. Mullenweg often uses the time to recast his vision for the project and deliver important announcements.
\n\n\n\nThis year has been unlike anything we have experienced before, but one thing has remained constant – WordPress’ phenomenal growth continues, as other major open source CMS’s are slowly declining. It is currently sitting at 39.3% of the Alexa top 10 million, 4.2% higher than November 2019, according to Joost de Valk’s biannual analysis of the CMS market share. de Valk attributes much of that growth to WooCommerce, which accounts for more than 18% of all the WordPress sites W3techs can detect.
\n\n\n\nDespite the global upheaval caused by the coronavirus, WordPress’ development has remained steady. More than 605 people contributed to the last major release (5.6) and there were 805 for the previous release (with 38% of them being new contributors.) In addition to reinventing WordCamps for the new virtual event frontier, the community team has also launched the Learn WordPress platform to make educational resources more globally available, placing a new emphasis on training. The platform is cracking open a world of WordPress knowledge that was previously relegated to more limited in-person audiences.
\n\n\n\n“Since we’ve collectively come to the realization that talks and training content can be delivered and consumed asynchronously, there will be less need to use the high-bandwidth time of physical events to passively watch a talk where we aren’t actively engaging with others,” WordPress community manager Hugh Lashbrooke said in a post with predictions on post-COVID community building. “The focus of these valuable meetings will rather be on interpersonal connection and mutual learning through active participation.”
\n\n\n\nLashbrooke’s predictions recognize a friction that has always existed at WordCamps: the “hallway track” is more engaging and more popular than most of the talks given at events. It’s the interpersonal connection that people crave more than turning up for sessions that are usually being recorded anyway.
\n\n\n\nTo those who have been homebound for the better part of this year, it may feel as though the world is standing still. But the WordPress community has put many meaningful changes in motion in response to the pandemic’s unique challenges. Despite all the uncertainty, WordPress is moving forward like a steady ship, with reliable improvements to the software and the community, thanks to the goodwill and cooperation of its unwavering base of contributors. This stability is worthy of commendation among this year’s milestones and is a testament to the maturity of the project.
\n\n\n\nMatt Mullenweg will be running the Q&A portion of his address virtually this year, with pre-recorded videos of questions from the audience. WordPress Executive Director Josepha Haden Chomphosy outlined the instructions for participating:
\n\n\n\n\n\n\n\nTo take part, record a video of you asking your question to Matt on your computer or phone (landscape format, please). Don’t forget to include your name and how you use WordPress! Try to keep your video to under a minute so Matt can answer as many questions as possible.
There are some positive aspects of this method but also a few drawbacks. It can create a more polished and efficient experience of Q&A where the audience is less likely to have to sit through long, rambling questions. It also allows equal opportunity for people living in all time zones to submit a question.
\n\n\n\nOn the other hand, the questions will be screened and pre-selected, allowing more preparation time for the answers. A live Q&A offers the opportunity to catch the person off guard and get answers that might not be delivered the same way in a different format. Pre-recorded videos have a few trade-offs but they may be the best option we have for this event.
\n\n\n\nThe deadline to submit video questions is Friday, December 11, 2020. Haden recommends participants upload their videos to YouTube as “unlisted” and send a link to ask-matt@wordcamp.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, 10 Dec 2020 05:57: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:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"WPTavern: WordPress 5.6 “Simone” Includes New Twenty Twenty-One Theme and Improved 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=108446\";s:7:\"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:219:\"https://wptavern.com/wordpress-5-6-simone-includes-new-twenty-twenty-one-theme-and-improved-editor?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-6-simone-includes-new-twenty-twenty-one-theme-and-improved-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:9657:\"WordPress 5.6 “Simone,” named in honor of American performer and civil rights activist Nina Simone, was released today and is now available for download. The release was led by an all-women release squad, a first in WordPress history. The new version includes many enhancements for the block editor, accessibility improvements, application password support for the REST API, and a new default theme.
\n\n\n\nThis release saw contributions from 605 volunteers who were involved with almost 350 Trac tickets and over 1,000 pull requests on GitHub.
\n\n\n\nThe following women formed the release squad for the 5.6 release:
\n\n\n\nAt times, the 5.6 development cycle felt a bit rocky. Block-based widgets and nav menus, features expected to ship, were punted for a second time to a future release. These were hard decisions, but good leadership means making tough calls to hold off on features that are not ready for production.
\n\n\n\n“You know, I was really hopeful for it too, and that last-minute call was one I labored over,” said Josepha Haden after pushing block-based widgets back. “When I last looked, it did seem close to ready, but then more focused testing was done and there were some interactions that are a little rough for users. I’m grateful for that because the time to discover painful user experiences is before launch rather than after!”
\n\n\n\nDespite dropping what would have been major transitional features from the classic WordPress theming paradigm in preparation for WordPress 5.7’s expected site editor, the release still has a lot to offer.
\n\n\n\nThe Gutenberg plugin development team continues to make small but vital improvements to the block editor. They have also tacked on many new features in the past few months. Features from Gutenberg versions 8.6 – 9.2 are included in the update, along with bug fixes and performance improvements from 9.3 and 9.4.
\n\n\n\nMuch of the work this development cycle has been focused on the upcoming site editor. There was some initial hope that a beta version of it would land in the 5.6 release. It was a part of the proposed scope. However, the feature is still months away from being ready. This is not a bad thing. It needs more time to mature, and there should be no rush in integrating a feature that affects so many pieces of the platform.
\n\n\n\nWhat end-users will see with this update is a more polished editor. Whether it is extra options for blocks or a dropdown select for block pattern categories, hundreds of minor changes have all led to a better overall experience.
\n\n\n\nWP Tavern has covered nearly every major Gutenberg plugin release this cycle — looks like we missed 8.8, sorry. Catch up with anything you missed about editor changes from the following posts:
\n\n\n\nTwenty Twenty-One, the new default theme for the upcoming year, takes full advantage of all the latest and greatest features of the block editor. While last year’s Twenty Twenty theme had a successful launch, the development team behind the new default has had more time to explore building themes in the block era.
\n\n\n\nThe theme makes use of more visual artistry. It will not be for everyone. It offers a wide range of color schemes for end-users, but it lends itself best to bloggers and other creators who prefer a bit of flair with their website’s design.
\n\n\n\nThe best thing is that it pushes the envelope with the block patterns feature, which was not available when Twenty Twenty landed a year ago. Older default themes will be getting the block-pattern treatment. However, Twenty Twenty-One will be the first default built with custom patterns in mind from the get-go.
\n\n\n\nFor users who cannot wait for the site editor to land in WordPress, expected in some form in the 5.7 release, there is an alternate Twenty Twenty-One Blocks theme to tinker with.
\n\n\n\nDespite being a part of the core platform since 2015, the REST API has lacked support for application passwords. Such a feature is vital for third-party applications to communicate with WordPress. Previously, requests had to be run through cookie and nonce-based authentication. Else, they would need to use the legacy XML-RPC API. This limitation has also affected the mobile WordPress development teams, making it tough to support the block editor, which relies on the REST API.
\n\n\n\nThe application passwords feature will make it easier for applications to make API requests as well as request and revoke credentials.
\n\n\n\nThe REST API promised a future for all types of applications built upon and around WordPress. However, this vision has not panned out over the years on a broad scale. With a major limiting factor removed, perhaps there is still hope for robust applications in the coming years.
\";s: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:07: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:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Mon, 11 Jan 2021 03:33:06 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Mon, 11 Jan 2021 03:30:08 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:\"20201208221211\";}','no'),(142,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1610379187','no'),(143,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1610335987','no'),(144,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1610379187','no'),(145,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b',' ','no'),(146,'theme_mods_twentytwentyone','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(149,'auth_key','n|YpJ7{$}+_qq7JD*GUn=Uk=jQrfJ^dg*?7(/Mjb].&NG32nI2/r~l:}UD ;)J?>','no'),(150,'auth_salt','BRiyV.*:!.w`,Ea~zD9!!>c.3rJWelcome to WordPress. This is your first post. Edit or delete it, then start writing!
\n','Hello world!','','publish','open','open','','hello-world','','','2021-01-11 03:32:29','2021-01-11 03:32:29','',0,'https://172.20.0.10:5050/?p=1',0,'post','',3),(2,1,'2021-01-11 03:32:29','2021-01-11 03:32:29','\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-01-11 03:32:29','2021-01-11 03:32:29','',0,'https://172.20.0.10:5050/?page_id=2',0,'page','',0),(3,1,'2021-01-11 03:32:29','2021-01-11 03:32:29','Our website address is: https://172.20.0.10:5050.
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
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.
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.
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.
If you request a password reset, your IP address will be included in the reset email.
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
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.
Visitor comments may be checked through an automated spam detection service.
Block patterns are pre-designed groups of blocks. To add one, select the Add Block button [+] in the toolbar at the top of the editor. Switch to the Patterns tab underneath the search bar, and choose a pattern.
\nTwenty Twenty-One includes stylish borders for your content. With an Image block selected, open the "Styles" panel within the Editor sidebar. Select the "Frame" block style to activate it.
\nTwenty Twenty-One also includes an overlap style for column blocks. With a Columns block selected, open the "Styles" panel within the Editor sidebar. Choose the "Overlap" block style to try it out.
\nNeed help?
\n \n\n \n \n \n\n \nYou might be an artist who would like to introduce yourself and your work here or maybe you’re a business with a mission to describe.
\n','About','','auto-draft','closed','closed','','','','','2021-01-11 03:35:58','0000-00-00 00:00:00','',0,'https://172.20.0.10:5050/?page_id=6',0,'page','',0),(7,1,'2021-01-11 03:35:58','0000-00-00 00:00:00','\nThis is a page with some basic contact information, such as an address and phone number. You might also try a plugin to add a contact form.
\n','Contact','','auto-draft','closed','closed','','','','','2021-01-11 03:35:58','0000-00-00 00:00:00','',0,'https://172.20.0.10:5050/?page_id=7',0,'page','',0),(8,1,'2021-01-11 03:35:58','0000-00-00 00:00:00','','Blog','','auto-draft','closed','closed','','','','','2021-01-11 03:35:58','0000-00-00 00:00:00','',0,'https://172.20.0.10:5050/?page_id=8',0,'page','',0),(9,1,'2021-01-11 03:35:58','0000-00-00 00:00:00','{\n \"nav_menus_created_posts\": {\n \"starter_content\": true,\n \"value\": [\n 5,\n 6,\n 7,\n 8\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu[-1]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Primary menu\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu_item[-1]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"custom\",\n \"title\": \"Home\",\n \"url\": \"https://172.20.0.10:5050/\",\n \"position\": 0,\n \"nav_menu_term_id\": -1,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu_item[-2]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 6,\n \"position\": 1,\n \"nav_menu_term_id\": -1,\n \"title\": \"About\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu_item[-3]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 8,\n \"position\": 2,\n \"nav_menu_term_id\": -1,\n \"title\": \"Blog\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu_item[-4]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 7,\n \"position\": 3,\n \"nav_menu_term_id\": -1,\n \"title\": \"Contact\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"twentytwentyone::nav_menu_locations[primary]\": {\n \"starter_content\": true,\n \"value\": -1,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu[-5]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Secondary menu\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu_item[-5]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Facebook\",\n \"url\": \"https://www.facebook.com/wordpress\",\n \"position\": 0,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu_item[-6]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Twitter\",\n \"url\": \"https://twitter.com/wordpress\",\n \"position\": 1,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu_item[-7]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Instagram\",\n \"url\": \"https://www.instagram.com/explore/tags/wordcamp/\",\n \"position\": 2,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"nav_menu_item[-8]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Email\",\n \"url\": \"mailto:wordpress@example.com\",\n \"position\": 3,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"twentytwentyone::nav_menu_locations[footer]\": {\n \"starter_content\": true,\n \"value\": -5,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"show_on_front\": {\n \"starter_content\": true,\n \"value\": \"page\",\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"page_on_front\": {\n \"starter_content\": true,\n \"value\": 5,\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n },\n \"page_for_posts\": {\n \"starter_content\": true,\n \"value\": 8,\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2021-01-11 03:35:58\"\n }\n}','','','auto-draft','closed','closed','','b941c2ea-6f9e-4be2-8152-0a891c22505e','','','2021-01-11 03:35:58','0000-00-00 00:00:00','',0,'https://172.20.0.10:5050/?p=9',0,'customize_changeset','',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,'Uncategorized','uncategorized',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=51 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','wordpress'),(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'),(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\";}'),(19,2,'nickname','blabla'),(20,2,'first_name','blabla'),(21,2,'last_name',''),(22,2,'description',''),(23,2,'rich_editing','true'),(24,2,'syntax_highlighting','true'),(25,2,'comment_shortcuts','false'),(26,2,'admin_color','fresh'),(27,2,'use_ssl','0'),(28,2,'show_admin_bar_front','true'),(29,2,'locale',''),(30,2,'wp_capabilities','a:1:{s:10:\"subscriber\";b:1;}'),(31,2,'wp_user_level','0'),(32,2,'dismissed_wp_pointers',''),(34,2,'community-events-location','a:1:{s:2:\"ip\";s:10:\"172.17.0.0\";}'),(36,1,'session_tokens','a:1:{s:64:\"486c3669af441ee69e36691ce9fa61bc970f6dec4149dc3b34cf592f20fac3ed\";a:4:{s:10:\"expiration\";i:1610509275;s:2:\"ip\";s:10:\"172.17.0.1\";s:2:\"ua\";s:76:\"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0\";s:5:\"login\";i:1610336475;}}'),(37,3,'nickname','blabla2'),(38,3,'first_name','blabla2'),(39,3,'last_name','blabla2'),(40,3,'description',''),(41,3,'rich_editing','true'),(42,3,'syntax_highlighting','true'),(43,3,'comment_shortcuts','false'),(44,3,'admin_color','fresh'),(45,3,'use_ssl','0'),(46,3,'show_admin_bar_front','true'),(47,3,'locale',''),(48,3,'wp_capabilities','a:1:{s:10:\"subscriber\";b:1;}'),(49,3,'wp_user_level','0'),(50,3,'dismissed_wp_pointers',''); +/*!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=4 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,'wordpress','$P$BdIhBfl12IlctyZonfO6Y7FesJzxt.0','wordpress','wordpress@wordpress.fr','https://172.20.0.10:5050','2021-01-11 03:32:29','',0,'wordpress'),(2,'blabla','$P$BsQru42u9Y19P9JejR3OeoMwbg7P/b/','blabla','blabla@blabla.fr','','2021-01-11 03:35:08','1610336108:$P$B2CWhI5qp0HWT/rc3ucgzwAh0Zc2fC/',0,'blabla'),(3,'blabla2','$P$BCFJlTzs94ugiuvUusTUmU70sHymuC1','blabla2','blabla2@blabla.fr','','2021-01-11 03:55:13','1610337313:$P$Bw2gdhXn2P0EBj0dbPHv3Z37j9gukd/',0,'blabla2 blabla2'); +/*!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-01-11 3:57:09 diff --git a/srcs/images/grafana/data_backup/grafana.db b/srcs/images/grafana/data_backup/grafana.db deleted file mode 100644 index 310f755..0000000 Binary files a/srcs/images/grafana/data_backup/grafana.db and /dev/null differ diff --git a/srcs/k8s_objects/wordpress.yaml b/srcs/k8s_objects/wordpress.yaml index de53cd7..8c3ff27 100644 --- a/srcs/k8s_objects/wordpress.yaml +++ b/srcs/k8s_objects/wordpress.yaml @@ -57,6 +57,9 @@ spec: - name: workdir-persistent-storage persistentVolumeClaim: claimName: wp-pv-claim + - name: wordpress-db-config + configMap: + name: wordpress-db-config containers: - name: nginx image: my-nginx @@ -113,6 +116,37 @@ spec: image: alpine command: ['sh', '-c', ' until nslookup mysql.$(cat /var/run/secrets/kubernetes.io/serviceaccount/namespace).svc.cluster.local; do echo waiting for myservice; sleep 2; done'] + - name: restore-wordpress-db + image: alpine + command: ['sh', '-c', + 'set -e; + apk add mysql-client; + database_exist="$(echo "select 1 from wp_users"|mysql -h mysql -u $MYSQL_USER -p$MYSQL_PASSWORD $MYSQL_DATABASE || true)" + + if [ "$database_exist" ]; then echo "database already exist"; exit 0; fi; echo "No database $MYSQL_DATABASE. Restoring db..."; + + mysql -h mysql -u $MYSQL_USER -p$MYSQL_PASSWORD $MYSQL_DATABASE < /script_sql/wordpress.sql; + echo "Done." + '] + volumeMounts: + - mountPath: /script_sql + name: wordpress-db-config + env: + - name: MYSQL_DATABASE + valueFrom: + secretKeyRef: + name: mysql-secrets + key: MYSQL_DATABASE + - name: MYSQL_USER + valueFrom: + secretKeyRef: + name: mysql-secrets + key: MYSQL_USER + - name: MYSQL_PASSWORD + valueFrom: + secretKeyRef: + name: mysql-secrets + key: MYSQL_PASSWORD --- apiVersion: v1 kind: ConfigMap