In the thirty-second episode of the WordPress Briefing, WordPress Executive Director Josepha Haden Chomphosy shares her open source reading list for that post-WordCamp Europe downtime.
Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Santana Inniss and Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- Producing Open Source Software, Karl Fogel
- Working in Public: The Making and Maintenance of Open Source Software, Nadia Eghbal
- Collaborative Ownership and the Digital Economy, ed Rishab Aiyer Ghosh, Roger F. Malina PhD, Sean Cubitt
- Humble Inquiry, Edgar H. Schein (Author), Peter A. Schein
- WordPress Milestones
- WordCamp Europe 2022
- 2022 Annual Meetup Survey
Transcript
\n\n\n\n\n\n\n\n[Josepha Haden Chomphosy 00:00:00]
\n\n\n\nHello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it. As well as get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nWith the approach of various mid-year breaks and the prospect of wandering off for some safe, restorative travel, I’ve been updating my to-read and re-read list. As I was looking at the queued books for my Northern hemisphere summer, there were some common threads, mostly around leadership, but there’s also like a chunk that’s about cross-cultural group theory and economics, and then like some beach reads, but there’s one group in particular that you all might find interesting.
\n\n\n\nAnd that’s a group that’s sort of like a back-to-FOSS basics list. So I’ll share my top few with you in case you want to pack a copy for your next getaway.
\n\n\n\nThe first one on our list is called Producing Open Source Software by Karl Fogel. I think everyone who contributes to FOSS projects has received this as one of their first recommendations. Like, y’all are building open software? Excellent, you need to read Producing Open Source Software. Like, that is just a sentence that comes out of everyone’s mouths. So this was one of the first open source books that was recommended to me when I joined the WordPress community. It was freshly revised in 2020, and I haven’t given it a read since then, which is why it is on my reread list this year.
\n\n\n\n[Josepha Haden Chomphosy 00:01:54]
\n\n\n\nHowever, it shaped the early days of the WordPress project’s leadership, and their lead developers, and some of WordPress’s basic philosophies. It’s all available online, under a creative commons, ShareAlike license. And so it’s worth the read. I’ll put a link to it in the show notes so it’s easy for everyone to find in the event that is your preferred beach read.
\n\n\n\nThe second one on this list is a book from Nadia Eghbal. She wrote the excellent Roads and Bridges report that also is probably not light beach reading, but you know, this one is on my list to read this summer because Eghbal always delivers truths about the reality of maintaining popular software, popular, open source software, in a way that’s easy for me to access and process rather than getting paralyzed by the enormity of it all.
\n\n\n\nFor what it’s worth your mileage may vary on that. I realized that, like, I live and breathe open source stuff. And so just because I am not paralyzed by the enormity of her explanations of things doesn’t necessarily mean that you will have a similar experience. And so I’m just going to claim that elephant in the room for all of us.
\n\n\n\nHowever, if you only read one book on this list this year, I think that this should be the one that you read.
\n\n\n\n[Josepha Haden Chomphosy 00:03:14]
\n\n\n\nThe third one is called Code: Collaborative Ownership and the Digital Economy. It was edited by Rishab Aiyer Ghosh. I am certain that I butchered that name. And so I apologize on my own behalf to everyone that knows whether or not I said it correctly.
\n\n\n\nThis book focuses on intellectual property rights and the original purpose of having anything like copyright in the world. So, right up my alley! The writers who contributed to this work promise exploration of the plight of creativity in the commons, the role of sharing in creative advancement, and a concept of what it would look like if intellectual property were to mean the second closing of an ecosystem versus a triumph of the commons.
\n\n\n\nI mean, obviously, this one is very light reading. You can take this topic to high tea and everyone will not know what you’re talking about. However, this one looks like a really interesting book to me and I am just super ready to read it.
\n\n\n\n[Josepha Haden Chomphosy 00:04:19]
\n\n\n\nThe second to last one on the list is a book called Humble Inquiry.
\n\n\n\nThis is a new-to-me book that seems right in line with one of my favorite books to recommend to leaders in the open source space. From reviews of it, I have gathered that it takes a hard look at the value of listening and asking for clarification in a world that puts a high value on an unsolicited hot take.
\n\n\n\nIt puts the importance of high trust relationship building, which is at the heart of any cross-culturally aware organization. And for folks who’ve been working with me for a while, you know, that relationship building is an important part of my leadership expectations for myself. So it puts relationship building at the front and center with a promise of practical applications for everyday life.
\n\n\n\nAnd if you ever have tried to tackle a complicated topic like this, you know that practical applications are really hard to come by and it’s often hard to understand it if you don’t have those practical applications. And so that is why this one is on my read and reread list this year.
\n\n\n\n[Josepha Haden Chomphosy 00:05:24]
\n\n\n\nAnd then finally the WordPress Milestones book.
\n\n\n\nSo this sounds like a shameless plug for WordPress. And on the one hand, this whole podcast is about WordPress. And so, yes! But on the other hand, I actually am reading this for two specific reasons. I’m rereading this actually. I read it when I first joined Automattic. And so the first of the two reasons that I’m rereading it this year is that volume two of this is, like the second decade of WordPress currently, being researched and written in preparation for WordPress’s 20th birthday next year.
\n\n\n\nSo I am rereading this to kind of get that all back in my mind as that work is getting done. And the second reason is that I honestly like to remind myself of how far we’ve come sometimes. I talk about our work frequently. And I talk about what we’re working on right now, all the time.
\n\n\n\nI talk about what we’re looking at three years from now, five years from now. The biggest concerns of today, tomorrow, and the future-future. And it’s very easy to forget how much success WordPress has had and how much growth the contributors that support us have had over the course of our long and storied history.
\n\n\n\n[Josepha Haden Chomphosy 00:06:40]
\n\n\n\nAnd so I like to go back to that just to kind of give myself some grounding in our progress, as well as get some concept for how we can move forward together. So that one is also available online. Also under a creative commons ShareAlike license and it is also worth the read. I will share a link to that with the other one in the show notes as well.
\n\n\n\nThat brings us now to our small list of big things. Let’s see what we got in the old lineup today.
\n\n\n\nSo, firstly WordCamp Europe is happening this week and it’s possible to watch the live stream from the comfort of your own home. There are some smart and talented speakers at the event. So I encourage you to catch a few if you have the time. I’ll include a link to the live stream information in the show notes below, and then also you can always keep an eye out on Twitter.
\n\n\n\nThere will be a lot of discussions, a lot of conversation there. And so you can engage with folks that are there at the time and catch up on those conversations, catch up on those presentations in your own time, as it fits into your day.
\n\n\n\n[Josepha Haden Chomphosy 00:07:50]
\n\n\n\nThe second thing is that WordPress’s community team is preparing the annual meetup survey right now. So if you participate in meetup events, keep an eye out for that because your feedback helps us to make plans to improve that program so that it works better for you. And it helps you to learn WordPress better and feel more confident with what you are taking out into the world that way.
\n\n\n\nBut, if you are wanting to use this as a chance to contribute, we actually will need folks who are able to translate the surveys as well. So I’ll leave a link to some information about that in the show notes. If all of that stuff about contribution didn’t make any sense, then just like keep an eye out from your meetup organizer and they will make sure that you have that survey so that you can have your voice heard.
\n\n\n\n[Josepha Haden Chomphosy 00:08:33]
\n\n\n\nAnd then item three is less of an item. I mean, it’s an item cause it’s in this list, but it’s less of, like, a thing to know and more of a general thing to be aware of. It’s a general awareness item. There’s a lot going on in WordPress right now. I can see how hard it is to keep track of some of these things these days.
\n\n\n\nAnd I know as someone who’s looking at this all day every day that, yeah, it’s a lot. And it’s hard to get your bearings. So if you have a team that you contribute to already, don’t forget to reach out to each other, just to check-in. Sometimes we don’t think to ask for help. Sometimes we don’t think to offer help and you know, if no one needs any help from you at that moment, a little hello also can brighten someone’s day.
\n\n\n\nAnd that, my friends, is your smallest of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy. And I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12940\";s: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: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:26:\"WordPress 6.0 “Arturo”\";s:7:\"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/2022/05/arturo/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 24 May 2022 20:01:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{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:\"6.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12879\";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:278:\"Say hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, Arturo O’Farrill. With nearly 1,000 enhancements and bug fixes, the second major release of 2022 is here. Download it now! As of today, WordPress powers more than 42% of websites worldwide.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:56842:\"\n![\"WordPress](\"https://i2.wp.com/wordpress.org/news/files/2022/05/Main-image-News-post.png?fit=4161%2C2822&ssl=1\")
Welcome to “Arturo”
\n\n\n\nSay hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, Arturo O’Farrill. Known for his influence on contemporary Latin jazz, Arturo has pressed more than 15 albums spanning a body of work across five decades.
\n\n\n\nTake some time to explore WordPress 6.0, built to help you unlock your creative aspirations and make your site-building experience more intuitive. And check out some of Arturo’s inspirational sounds that span Afro Cuban jazz, contemporary Latin jazz, and so much more.
\n\n\n\nWith nearly 1,000 enhancements and bug fixes, the second major release of 2022 is here. Download it now! As of today, WordPress powers more than 42% of websites worldwide.1
\n\n\n\nSite owners and administrators should upgrade to take full advantage of the many stability, performance, and usability enhancements today. WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.
\n\n\n\n\n\n\n\nExpanding Gutenberg into a full site editing experience in WordPress means that all of the problems the community had to address were complex and far-reaching. WordPress 6.0 is an example of the community’s commitment to tackling these tough challenges together. With thoughtful updates to the writing experience, building better block functionality, and adding a new intuitive style switcher, I’m really proud of the work that’s been done in this release to make a great site editing experience.
Josepha Haden Chomphosy, Executive Director
What’s Inside
\n\n\n\n![\"Selecting](\"https://i2.wp.com/wordpress.org/news/files/2022/05/Writing-Improvements-1.png?fit=1204%2C700&ssl=1\")
Enhanced Writing Experience
\n\n\n\nWriting improvements abound, whether you’re writing a brand new post or adding elements to an existing page. Explore more ways to streamline your content creation process, including:
\n\n\n\n- Select text across multiple blocks for easier copying and pasting.
- Type two open brackets `
[[` to quickly access a list of recent posts and pages. - Keep existing styles when you transform some blocks from one kind to another—from a Paragraph block to a Code block, for instance.
- Create customized buttons and any new buttons you make will retain the style customizations automatically.
- Make tag clouds and social icons even more appealing with updated settings and controls, and a new outline style for the tag cloud.
![\"Style](\"https://i0.wp.com/wordpress.org/news/files/2022/05/Style-switcher-big.gif?fit=1204%2C700&ssl=1\")
Style Switching
\n\n\n\nBlock themes now include the option to contain multiple style variations. This expands the new Style system even further and enables shortcuts to switch the look and feel of your site all within a single theme. In block themes that support this feature, you can change both the available settings, like the font-weight, and the style options, like the default color palette. Change the look and feel of your site with just a few clicks.
\n\n\n\n![\"Popover](\"https://i2.wp.com/wordpress.org/news/files/2022/05/Expanded-templates.png?fit=1204%2C700&ssl=1\")
More Template Choices
\n\n\n\nWordPress 6.0 includes five new template options for block themes: author, date, categories, tag, and taxonomy. These additional templates provide greater flexibility for content creators. Tailor each with the tools you already know or with the following new options in this release:
\n\n\n\n- Featured images can be used in the cover block.
- New featured image sizing controls make it easier to get the results you want.
- While editing a template, at the root, or between blocks, the quick inserter shows you patterns and template parts to help you work faster and discover new layout options.
- The query block supports filtering on multiple authors, support for custom taxonomies, and support for customizing what is shown when there are no results.
![\"Browsing](\"https://i1.wp.com/wordpress.org/news/files/2022/05/Integrated-Patterns.png?fit=1204%2C700&ssl=1\")
Integrated Patterns
\n\n\n\nPatterns will now appear when you need them in even more places, like in the quick inserter or when creating a new header or footer. If you’re a block theme author, you can even register patterns from the Pattern Directory using `theme.json`, enabling you to prioritize specific patterns that are most helpful to your theme’s users.
Additional Design Tools
\n\n\n\nDesign tools grow more powerful and intuitive with each release. Some highlights for 6.0 include:
\n\n\n\n- A new color panel design saves space, but still shows your options at a glance.
- New border controls offer a simpler way to set your border exactly as you like it.
- Transparency levels for your colors allow for even more creative color options.
- Control gaps, margins, typography, and more on a collection of blocks, all at once, in the Group block.
- Switch between stack, row, and group variations to position groups of blocks with more layout flexibility.
- Use the gap support functionality in the Gallery block to create different looks – from adding spacing between all images, to removing spacing altogether.
![\"Selecting](\"https://i0.wp.com/wordpress.org/news/files/2022/05/List-view.png?fit=1204%2C700&ssl=1\")
Better List View
\n\n\n\nNew keyboard shortcuts enable you to select multiple blocks from the list view, modify them in bulk, and drag and drop them within the list. List View can be opened and closed easily; it comes collapsed by default and it automatically expands to the current selection whenever you select a block.
\n\n\n\n![\"Unlocking](\"https://i1.wp.com/wordpress.org/news/files/2022/05/Block-Locking-Controls.png?fit=1204%2C700&ssl=1\")
Block Locking Controls
\n\n\n\nNow you can lock your blocks. Choose to disable the option to move a block, remove a block, or both. This simplifies project handover, allowing your clients to unleash their creativity without worrying about accidentally breaking their site in the process.
\n\n\n\nImproved Performance in WordPress 6.0
\n\n\n\nThis release includes several updates focused on improving the performance of WordPress. These enhancements cover a range of performance areas including improving the page and post-load speed, reducing the execution time of various query types, caching, navigation menus, and much more. The performance team working group is an important focus area of the core development team. For more information on this group’s work, please follow their work on Making WordPress with the #performance hashtag.
\n\n\n\nEnhancing WordPress 6.0 Accessibility
\n\n\n\nAccessibility is an integral part of the WordPress mission of fostering an inclusive community and supporting users of all types around the world. With this in mind, WordPress 6.0 includes more than 50 updates specifically focused on enhancing the accessibility of the platform. You can read about these updates and learn more about the accessibility initiatives that are ongoing.
\n\n\n\nLearn More About WordPress 6.0
\n\n\n\nSee WordPress 6.0 in action! Watch a brief overview video highlighting some of the major features debuting in WordPress 6.0.
\n\n\n\nExplore learn.wordpress.org for quick how-to videos and lots more on new features in WordPress. Or join a live interactive online learning session on a specific WordPress topic.
\n\n\n\nDevelopers can explore the WordPress 6.0 Field Guide. It is overflowing with detailed developer notes to help you build with and extend WordPress.
\n\n\n\nRead the WordPress 6.0 Release Notes for more information on the included enhancements and issues fixed, installation information, developer notes and resources, release contributors, and the list of file changes in this release.
\n\n\n\nThe WordPress 6.0 Release Squad
\n\n\n\nThe group listed below tirelessly supported the release, from conception to ship date, and beyond:
\n\n\n\n- Release Lead: Matt Mullenweg
- Release Coordinators: Héctor Prieto and Anne McCarthy
- Core Tech Lead: Peter Wilson
- Editor Tech Leads: Adam Zieliński and Greg Ziółkowski
- Core Triage Leads: Ahmed Chaion and Colin Stewart
- Editor Triage Lead: Nick Diego
- Documentation Leads: Birgit Pauli-Haack, Milana Cap, and Abha Thakor
- Marketing & Communications Lead: Dan Soschin
- Test Leads: Piotrek Boniu and Brian Alexander
- Design Lead: Channing Ritter
Thank you to 500+ Contributors
\n\n\n\nWordPress 6.0 would not have been possible without the contributions of more than 500 people in at least 58 countries. Their asynchronous coordination to deliver hundreds of enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\nAaron Jorbin · Aaron Robertshaw · Abdullah Ramzan · Abha Thakor · Adam Silverstein · Adam Zielinski · adi64bit · Adil Ali · agepcom · Ahmed Chaion · Aki Hamano · Akira Tachibana · Alain Schlesser · Alan Jacob Mathew · alansyue · Albert Juhé Lluveras · albertomake · Alefe Souza · Aleksandar Kostov · Alex Concha · Alex Lende · Alex Mills · Alex Stine · aliakseyenkaihar · Alkesh Miyani · Alok Shrestha · Amanda Giles · Andrea Fercia · Andrei Draganescu · Andrei Surdu · Andrew Dixon · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrey \"Rarst\" Savchenko · André · Andy Fragen · Angelika Reisiger · Anh Tran · Ankit K Gupta · Anne McCarthy · Anoop Ranawat · Anthony Burchell · Anthony Ledesma · Anton Vlasenko · antonrinas · Antony Booker · arcangelini · Ari Stathopoulos · Arne · Arpit G Shah · artdecotech · ArteMa · Arthur Chu · Asaquzzaman mishu · atomicjack · Aurélien Joahny · Aurooba Ahmed · Barry · Barry Ceelen · Bartosz Gadomski · Beda · Ben Dwyer · Benachi · Bernhard Reiter · BettyJJ · Bhrugesh Bavishi · binarymoon · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Blair Williams · BlogAid · Boone Gorges · Brandon DuRette · Brandon Kraft · Brian Alexander · bronsonquick · Brooke Kaminski · Brooke. · Bruno Ribaric · caraya · Carlos Bravo · Carlos Garcia · Carolina Nymark · cbigler · Chad Chadbourne · Channing Ritter · charleyparkerdesign · charlyox · Chintan hingrajiya · Chloe Bringmann · Chouby · Chris Lubkert · Chris Van Patten · chriscct7 · clonemykey · Colin Stewart · conner_bw · Cory Hughart · Courtney Robertson · Crisoforo Gaspar · Dan Soschin · Daniel Bachhuber · Daniel Richards · danieldudzic · darerodz · Dat Hoang · Dave Smith · David Baumwald · David Biňovec · David Calhoun · David Gwyer · David Herrera · David Shanske · Deb Nath Utpol · Delowar Hossain · denishua · Dennis Claassen · Dennis Snell · Dhanendran · Dharmesh Patel · dhusakovic · Dilip Bheda · Dion Hulse · Dominik Schilling · donmhico · drago239 · Drew Jaynes · dromero20 · Eddy · ehtis · Eliezer Peña · Ella van Durpe · Emmanuel Hesry · Enrico Battocchi · eric3d · Erik Betshammar · espiat · Estela Rueda · etaproducto · EverPress · Fabian Kägy · Fabio Blanco · Faison · Felipe Elia · Felix Arntz · Femy Praseeth · Florian Brinkmann · Florian TIAR · FolioVision · Francesca Marano · Francisco Vera · frankei · furi3r · gadhiyaravi · Garrett Hyder · Garth Mortensen · Gary Jones · Gary Pendergast · genosseeinhorn · George Hotelling · George Mamadashvili · George Stephanis · Gerardo Pacheco · Glen Davies · Grégory Viguier · Grant M. Kinney · Greg Ziółkowski · gregoiresailland · Guido Scialfa · gumacahin · gvgvgvijayan · Hareesh · Hasanuzzaman · Hasnain Ashfaq · Hauwa Abashiya · Haz · Helen Hou-Sandi · HelgaTheViking · Henry Wright · Hilay Trivedi · Hitendra Chopda · HristoK · Hugh Lashbrooke · Héctor Prieto · Ian Belanger · Ian Dunn · ianatkins · ianmjones · ImanGM · imokol · Isabel Brison · ishitaka · itsamoreh · Iulia Cazan · Ivan Lutrov · jadpm · Jake Spurlock · jakeparis · James Koster · Jamie VanRaalte · Jan Weiss · janh2 · Jarret · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Arce · Javier Prieto · Jay Trees · jazbek · Jean-Baptiste Audras · Jeff Bowen · Jeff Matson · Jeff Ong · Jeff Paul · Jenny Dupuy · Jenny Wong · Jeremy Felt · Jeremy Herve · Jeremy Yip · Jez Emery · jhned · jhnstn · jigar bhanushali · jiteshdhamaniya · Joe Dolson · Joe McGill · Joen Asmussen · Johannes Kinast · John Blackbourn · John James Jacoby · John Regan · John Watkins · Jon Brown · Jonathan Champ · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Jorge · Jorge Costa · José Arcos · Josepha · Josepha Dambul · Joshua Fredrickson · Joy · jrivett · jsnajdr · juanlopez4691 · JuanMa Garrido · Juliette Reinders Folmer · Junaid Ahmed · Justin Ahinon · Justin Busa · Justin Tucker · KafleG · Kai Hao · Kajal Gohel · kapacity · Kapil Paul · karolinakulinska · Kaspars · kbatdorf · Kelly Choyce-Dwan · Kemory Grubb · Kerry Liu · Kev Provance · Kharis Sulistiyono · Kirtan Gajjar · Kjell Reigstad · KMix · Knut Sparhell · Konrad.K · Konstantin Obenland · kpegoraro · kubiq · Kukhyeon Heo · Lauren · Lena Morita · lenasterg · leskam · Lew Ayotte · linux4me2 · Lisa Schuyler · lkraav · Louis · Lovekesh Kumar · Lucas Karpiuk · Luis Felipe Zaguini · luisherranz · Luke Cavanagh · Lukman Nakib · M. van Dam · macbookandrew · Maciej · Maggie Cabrera · maguijo · Mahbub Hasan Imon · malthert · manfcarlo · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marin Atanasov · Marius L. J. · Mark Jaquith · Markus Kosmal · marv2 · Mary Baum · Mat Lipe · Mathieu · Matias Ventura · matiasbenedetto · Matt Chowning · Matt Martz · Matt Mullenweg · Matt Royal · Matt Stoney · Matt Wiebe · maur · Mauriac AZOUA · Max Kellermann · Mehedi Foysal · Meher Bala · mgol · Michael Burridge · Michal Czaplinski · Miguel Fonseca · Mike Auteri · Mike Schroder · miken32 · Milan Dinić · Milana Cap · Minal Diwan · Mirco Babini · MMDeveloper · Mohadese Ghasemi · Mohammad Ahsan Habib · Mohammad Rockeybul Alam · MohammadJafar Khajeh · Morten Rand-Hendriksen · moushik · mqudsi · Muhammad Faizan Haidar · Mukesh Panchal · Mustaque Ahmed · Nabil · Nagesh Pai - a11n · Nalini Thakor · Nathan · Nayana Maradia · Nicholas Garofalo · Nick Ciske · Nick Diego · Nicolas Juen · nidhidhandhukiya · Nik Tsekouras · Nil · nmschaller · Noah Allen · oakesjosh · oguzkocer · Oliver Campion · Omar Alshaker · opr18 · Otshelnik-Fm · overclokk · ovidiul · Paal Joachim Romdahl · Pablo Honey · Paolo L. Scala · Paragon Initiative Enterprises · Pascal Birchler · Paul Bearne · Paul Biron · Paul Ryan · Paul Von Schrottky · paulkevan · Pavan Patil · Pavlo · pbking · Pedro Mendonça · Petar Ratković · Peter Smits · Peter Westwood · Peter Wilson · petrosparaskevopoulos · Petter Walbø Johnsgård · pgpagely · Phil Johnston · Pieterjan Deneys · pikamander2 · Piotrek Boniu · Pooja Derashri · Pooja N Muchandikar · Pravin Parmar · Presskopp · presstoke · Priyank · pypwalters · r-a-y · Rachel Baker · Rafi Ahmed · Ramanan · Ramon Ahnert · Ramon James · Ramona · Ravi Vaghela · ravipatel · Razvan Onofrei · Rehan Ali · Remy Perona · Riad Benguella · Rian Rietveld · Rich Tabor · Richard B. Kreckel · ricomoorman · Rob Scott · Robert Anderson · Rolf Allard van Hagen · Rolf Siebers · Rostislav Wolný · Rufus87 · Ryan Boren · Ryan Fredlund · Ryan McCue · Ryan Welcher · Sébastien SERRE · Sören Wrede · Sabbir Ahmed · Sabbir Hasan · Sami Falah · Sanjeev Aryal · santosguillamot · Sarah Norris · Sarah Snow · sarayourfriend · Sathiyamoorthy V · Sayedul Sayem · sbossarte · sclayf1 · Scott Buscemi · Scott Reilly · Scott Taylor · Segayuu · Sergey Biryukov · sheepysheep60 · Shital Marakana · Shreyas Ikhar · siddharth · Siddharth Thevaril · silb3r · Simon Blackbourn · Simon Prosser · simonhammes · Siobhan · Smit Rathod · snapfractalpop · socalchristina · Spencer Cameron-Morin · stacimc · stefanfisk · Stefano Lissa · Stefano Minoia · Stefanos Togoulidis · Stephen Bernhardt · Stephen Edgar · Stephen Harris · Steve Grunwell · Subrata Sarkar · Sumit Singh · Sumit Singh · Sumon Sarker · SunilPrajapati · sunyatasattva · Sven Wagener · Sybre Waaijer · Synchro · Takashi Kitajima · Tammie Lister · tharsheblows · Theo H · Thimal Wickremage · Thomas McMahon · Thomas Patrick Levy · Thomas Pike · Till Krüss · Tim Blankenship · Tim Nolte · Timothy Jacobs · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tomasz Tunik · Tomek · Tomoki Shimomura · Tony Tahmouch · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Tracy · trex005 · tszming · tumas2 · twstokes · Tynan Beatty · tzipporahwitty · Uday Kokitkar · ugljanin · Ugyen Dorji · Ulrich · Utkarsh · valer1e · versusbassz · Vicente Canales · Vishal Kumar · vlad.olaru · Volodymyr Kolesnykov · vortfu · WebMan Design | Oliver Juhas · Wendy Chen · Wes Theron · Weston Ruter · whoisnegrello · Will Skora · wpmakenorg · wpsoul · WraithKenny · wslyhbb · Xidorn Quan · Yui · Yunus Ertuğrul · Zebulan Stanphill · znuff · Česlav Przywara
\n\n\n\nBy release day, 76 locales had translated 90-percent or more of WordPress 6.0 into their language. Community translators continue after a release ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in 205 languages.
\n\n\n\nMany thanks to all of the community volunteers who contribute to the support forums by answering questions from WordPress users around the world.
\n\n\n\nIf contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to Make WordPress and explore the product roadmap on the core development blog.
\n\n\n\nThe WordPress Mission & You
\n\n\n\nWordPress is software designed for everyone, emphasizing accessibility, performance, security, and ease of use. The project believes great software should work with minimum setup, so you can focus on sharing your story, product, or services freely. The basic WordPress software is simple and predictable so you can easily get started. It also offers powerful features for growth and success.
\n\n\n\nWordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a large community of people collaborating on and contributing to this project. The WordPress community is welcoming and inclusive. Our contributors’ passion drives the success of WordPress which, in turn, helps you reach your goals.
\n\n\n\nLearn more about WordPress and how you can join our community to help shape the future of the world’s most popular website platform.
\n\n\n\n\n\n\n\n
A Release Haiku
\n\n\n\nSix-point-oh is here
Time to download and upgrade
Let’s pause, celebrate
\n\n\n\n
1 According to W3Techs as of May 5, 2022.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12879\";s: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:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WordPress 6.0 Release Candidate 3 (RC3) Now Available for Testing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-3-rc3-now-available-for-testing/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 17 May 2022 16:39:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a: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:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12866\";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:166:\"WordPress 6.0 Release Candidate 3 is now available for testing! You can download and help test RC3 in three ways. 6.0 is planned for general release on May 24, 2022.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s: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:4240:\"\nWordPress 6.0 is scheduled for release next week on May 24, 2022! This RC3 release is the final opportunity for you to test and help contribute to making the 6.0 release great.
\n\n\n\nYou can view changes since the RC2 release via Gutenberg and Trac.
\n\n\n\nInstalling RC3
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you install RC3 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 RC3 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the release candidate (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, RC1, or RC2 on a case-insensitive filesystem, please use the following command:
\n\n\n\nwp core update --version=6.0-RC3
Plugin and Theme Developers
\n\n\n\nAll plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.0 RC3 and update the “Tested up to” version in their readme file to 6.0 this week. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24.
\n\n\n\nReview the WordPress 6.0 Field Guide, for more details on this release.
\n\n\n\nReview additional information on the full 6.0 release cycle.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail upcoming changes.
\n\n\n\nTranslate WordPress
\n\n\n\nDo you speak a language other than English? Help translate WordPress into more than 100 languages.
\n\n\n\nHow to Help Test WordPress
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\n\n\n\n\n
RC3, An (Almost) Final Haiku
\n\n\n\nIt’s near time for six
The reward is the journey
Just one week to go
\n\n\n\n
Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12866\";s: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:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:127:\"WP Briefing: Episode 31: Open Source & Accessibility– Celebrating Global Accessibility Awareness Day With Guest Joe Devon\";s:7:\"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:140:\"https://wordpress.org/news/2022/05/episode-31-open-source-accessibility-celebrating-global-accessibility-awareness-day-with-guest-joe-devon/\";s: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, 16 May 2022 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=12855\";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:392:\"In the thirty-first episode of the WordPress Briefing, GAAD Co-Founder Joe Devon joins WordPress Executive Director Josepha Haden Chomphosy to discuss Global Accessibility Awareness Day and the role of open source in accessibility. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Guest: Joe […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/05/WP-Briefing-031.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:33186:\"\nIn the thirty-first episode of the WordPress Briefing, GAAD Co-Founder Joe Devon joins WordPress Executive Director Josepha Haden Chomphosy to discuss Global Accessibility Awareness Day and the role of open source in accessibility.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
Credits
\n\n\n\n- Guest: Joe Devon
- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Santana Inniss and Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- About GAAD
- GAAD Foundation Pledge
- World Health Organization on Disability
- The Dress Phenomenon
- The Guardian on Yanny or Laurel
- Empathy vs. Altruism in Modern Leadership, Josepha Haden Chomphosy
- The WebAim Million 2022 Report
- WordPress 6.0 Development Cycle
- WordCamp Europe 2022
Transcript
\n\n\n\n\n\n\n\n[Josepha Haden Chomphosy 00:00:00]
\n\n\n\nHello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nY’all, we’ve got an absolutely jam-packed couple of weeks in WordPress. We’ve got events happening and releases shipping and contributor days being coordinated (I almost said contributor days being contributed). That’s also what they’re doing. I’ll share some of those highlights in today’s small list of big things, but I did want to specifically call out something that’s coming up this week on Thursday (May 19, 2022), and that something is Global Accessibility Awareness Day.
\n\n\n\nThe team of contributors over on the Accessibility team has participated in the Global Accessibility Awareness Day in the past. So I thought it would be interesting to hear from one of the co-founders of this particular day of awareness.
\n\n\n\n[Josepha Haden Chomphosy 00:01:27]
\n\n\n\nAll right. And with that, Joe Devin, would you like to tell us a little bit more about yourself?
\n\n\n\n[Joe Devon 00:01:34]
\n\n\n\nSure. So I am the co-founder of Global Accessibility Awareness Day, which is a day that goes viral every year on the third Thursday of May. We typically have the Twitter reach on the GAAD hashtag on Twitter of 200 million users, which is, I think, pretty much their active user count. We stopped counting once we hit their daily active user count.
\n\n\n\nAnd then, I am Chair of the GAAD Foundation, which we launched last year. And then I have a day job too, where I’m CEO and co-founder of Diamond, which is an inclusive digital agency that builds software accessibly by default.
\n\n\n\n[Josepha Haden Chomphosy 00:02:15]
\n\n\n\nWonderful. Well, we are so excited to have you today. I said we like it’s me and the mouse in my pocket—we in the WordPress community that’s going to listen to this. Super excited to have you today. So you mentioned GAAD, Global Accessibility Awareness Day. Last year was your 10th anniversary, which is very exciting, but like with so many good things, I hear it all started with a blog post and a blog post on WordPress, no less.
\n\n\n\nSo I’d love to hear about how GAAD evolved from that, with, as I understand it, your co-founder of Jennison (Asuncion). That must be where you met him, I assume.
\n\n\n\n[Joe Devon 00:02:51]
\n\n\n\nYes. Yes. So what happened was I started a WordPress blog called My SQL Talk. So it’s a database blog, and I just thought it was a brilliant name. I mean, My SQL Talk, like that, should be super popular.
\n\n\n\nAnd it probably had maybe ten people who ever looked. Um, and then my dad was getting older, and my dad was a survivor of the concentration camps, and he was a genius. He spoke ten languages. It, he was one of those people. That, when he walked into a room, he just commanded respect. You knew that there was history. I don’t know how to explain it really, but it was special when my dad walked into the room. And considering all of this that he suffered in his life, watching him get older and struggle, particularly with his banking, was very painful to see. And the bank wasn’t accessible, so I wrote this blog post proposing that we create a Global Accessibility Awareness Day.
\n\n\n\nSometimes I get these visions, and they never turn into anything. But while I think about it, I’m like, “all right, let’s write this blog post and this can definitely work. Right?” And then you finish the blog post to hit send, and you’re like, “this is not going to work.”
\n\n\n\nBut I wasn’t even smart enough to do social media on it. But fortunately, WordPress had an auto-tweet feature, and it tweeted it out, and Jennison Asuncion, my co-founder, happened to be around and not out that Saturday night. And he read the blog post, and he said, “this is a great idea. Let’s make it happen.”
\n\n\n\nAnd we had two busy people, but we both had a community. He had the accessibility community, and I was building a tech scene in Los Angeles. And what I discovered is if you combine a great idea with the community, great things can happen.
\n\n\n\n[Josepha Haden Chomphosy 00:04:49]
\n\n\n\nOh man, you’re speaking my language over here, helping people find their communities, knowing that community is the thing that is the lifeblood of society.
\n\n\n\nThat sounded like a tautology. It is not a tautology. You can have a society with an attempt to not have any sort of community around it, but I bet it doesn’t work very well. Well, that’s, that’s very interesting. And so you all just kind of talked through what that would look like, I assume in confidence, or that would have to take place, right? Or was it on Twitter in those days?
\n\n\n\n[Joe Devon 00:05:24]
\n\n\n\nOh, you could still look in the comments and see the back and forth of Jennison and a bunch of other people that got pretty involved with GAAD that are some legendary folks in there. It’s kind of mind-blowing because I dunno how, how you feel, but for me, when I used to code, uh, three months later, I’d look back at old code and be like, “oh, I suck,” you know, or write an email even and you look back on it a day later and are like “what a stupid email, how stupid am I?” You know? But I look back on that one after ten years; I was scared to look at it because I’m like, it must’ve been really bad. But you know, it kind of held up, and exactly what I wrote in there happened – to my utter shock.
\n\n\n\n[Josepha Haden Chomphosy 00:06:06]
\n\n\n\nBut also, it’s kinda nice, though, to look back and be like, “oh, I used to be much dumber.”
\n\n\n\nCause then you’re like, look how far I’ve come. I’m no longer that dumb. I’m a different kind of dumb now; good for me. I always hope to be a different kind of dumb as I go forward.
\n\n\n\nSo then, okay, so that was your ten-year anniversary last year. GAAD, in general, now has been going on for 11 years, and at the time of this recording, in a couple of weeks, but then probably a week when it finally publishes, you have your next, your next round of that going.
\n\n\n\nI think it seems safe to assume that awareness of the need for accessibility has increased during that time, but we all know that the work of accessibility is ongoing. And so, I’m just curious to hear from your perspective if the awareness of the need for accessibility has generally started to permeate developer communities.
\n\n\n\nAnd are you seeing more developer awareness around the need for accessibility in tech in general?
\n\n\n\n[Joe Devon 00:07:12]
\n\n\n\nYeah. You know, it’s not enough. It’s certainly improved a lot. I keynoted a conference probably four years after GAAD started, maybe five, and I kind of assumed nobody would have heard of accessibility, and I was taken aback when I asked who had heard of it, and a good chunk of the room had. So even then, there had been a difference, and I’d say now I see accessibility mentioned a lot more in conferences and stuff. But when it comes to actually building it, there’s a tremendous amount of ignorance. There, there still needs to be a lot more awareness.
\n\n\n\nAnd I think partially people are a little bit scared to dip their toe because they’re scared that they’re going to be told that “no, it’s not accessible,” or that they’re going to say the wrong word or offend somebody. So I’d say that there’s some degree of trepidation, but also developers, and it’s not just developers, designers, and product people. There’s so much to learn, and it’s like, “oh God, there’s another piece that I have to learn.”
\n\n\n\nAnd I’m so glad that you invited me on this podcast because it’s the developers that, you know, I am a developer, not anymore, I haven’t touched code in years, but that’s where I came from. Right? This is my peach, right? Particularly WordPress folks, because I had done a fair bit of WordPress before I moved on to some other things. And, I think we have to talk about usability and understand that accessibility is so much more than how we look at disability.
\n\n\n\nAnd if you don’t mind, I’m going to ask you a question. How do you think the typical WordPress developer or designer would define disability?
\n\n\n\n[Josepha Haden Chomphosy 00:09:05]
\n\n\n\nin the kinds of conversations that I’ve had over the years, it frequently has to do with visual things. Because it’s just screens all day, right? And that’s a primary area where our designers and developers really have made some effort.
\n\n\n\nBut my personal favorite sort of, of example, for like, when you’re looking at how to make sure that your products are accessible is, what, if you have to use your website, or you have to build your website using only one arm. Because that gives you an opportunity to kind of look at disability from a permanent standpoint.
\n\n\n\nLike if you have lost permanent use of one arm, but also gives you an opportunity to look at the temporary options for that sort of lack of mobility. Like you’re a mother with an infant, and so you have to be able to, you know, get your stuff done with one arm. And so I know that we paid a bunch of attention to screen readers and what works in not way back in 2018 and 2019 did a lot of work with. Literally zero screen. And can you still do the thing that you need to do, which was incredibly difficult. And I was really excited to see what our developers came up with around that. But I think that that is quite a bit of that discussion as we’re going through it from the beginning to the end.
\n\n\n\n[Joe Devon 00:10:27]
\n\n\n\nYeah. I mean, that’s a great answer, and you definitely understand some of the nuances way better than I think that the average creator, digital product creator, I’m including the, you know, the product people, the designers, and the developers.
\n\n\n\n[Josepha Haden Chomphosy 00:10:42]
\n\n\n\nWe’re very fortunate to have more than just developers in WordPress.
\n\n\n\n[Joe Devon 00:10:50]
\n\n\n\nThe reason I bring this up is that the WHO (World Health Organization) had to; they’re the ones that did massive research across the globe. And they had to, they had to come up with a definition, and in their definition, they needed to draw a line. Typically, I don’t remember the exact thing cause it’s a 350-page report, and I kept looking for where they defined it again.
\n\n\n\nIt was a little hard to find, but essentially it’s if there’s a major disability or a disability that impacts some significant portion of your day-to-day activities. And that’s really great when you’re trying to do a report on how many disabilities there are out there; what percentage of the population has a disability?
\n\n\n\nAnd their figures are something like 15% of the population has a disability, which is a huge number. But at the same time, they also mentioned that 2.2 billion people have a visual impairment. And we also know that over 33% of the population is over 50, and I’m included in that population. And I can say that when you’re over 50, you know, I’ve got clouds in my eyes.
\n\n\n\nI don’t know where they came from, but they definitely make it harder to see. When I’m in a restaurant, I can’t focus on the person across from me the same way. My hearing is not the same, and anybody over 50 is going to have certain impairments and won’t see as well; color contrast issues are a big deal.
\n\n\n\nBeing able to raise the font is a big deal. And I think that accessibility is connected in most people’s minds with disability. And they’ll attach that to something like being blind or being deaf or hard of hearing or having a missing limb or having some other kind of disability.
\n\n\n\nAnd, as a result, they’re like, “well, I don’t even know any people in that category possibly,” and as a result, they’re like, “well, how important is this?” Yes. They might feel guilty. I should do the right thing. This is the right thing to do. But honestly, like how much money should I spend on it? How much, what percentage of my time should I spend on it?
\n\n\n\nAnd it’s because they don’t realize that everybody has different abilities. And so, I’m starting to go away from even talking about disabilities and asking people to remember that all of us perceive things differently.
\n\n\n\nDo you remember the gold dress where they were trying to say, what color is this dress? Is it gold and white or blue and black? And it is blue and black, but to me, all I see is gold and white. And then there was Laurel or Yanny. Do you remember that?. And some people heard it, and typically older people heard it as Laurel, and I’ve, and I do this in some of my presentations. I play that, that sound. And usually, it’s Laurel for me, but sometimes it’s Yanny. Even personally, it changes.
\n\n\n\nAnd so, we have a totally different perception. Now think about memory. There’s a different kind of blindness. If you try and remember, let’s say a relative or a friend that is no longer. How well do you see that picture?
\n\n\n\nBecause for me, it is very, very vague, but for some people, they say, and I’ve been asking people, and I’d love your answer as well. How vivid is it? And some people say, I can read the, I can see the pattern on the shirt. It’s as vivid as if I see with opening my eyes, seeing, you know, the regular in front of me, and I can even read a name tag in the memory.
\n\n\n\nAnd I’m like, Woah, so maybe I’m blind in a way. Right? So how do you see it? How do you remember things?
\n\n\n\n[Josepha Haden Chomphosy 00:14:42]
\n\n\n\nOh, I’m a, I’m a real visual person and a tactile person. And so, like if I interacted with someone, I’m very likely to be able to picture, like, recreate that mental picture pretty well in my mind. I recently, very recently, met some of my first people in that executive leadership space who were like, yeah, I don’t, I don’t visualize things.
\n\n\n\nAnd I was like, what are you, how do you do this work? Because like, you have to be able to do that. And they were like, no, I don’t have mental pictures.
\n\n\n\n[Joe Devon 00:15:13]
\n\n\n\nSome people don’t have an inner dialogue.
\n\n\n\n[Josepha Haden Chomphosy 00:15:17]
\n\n\n\nI don’t understand that either,
\n\n\n\n[Joe Devon 00:15:19]
\n\n\n\nMe either. So accessibility studies all of these differences with respect to how you’re presenting all of this information.
\n\n\n\nAnd if you don’t pay attention to accessibility, you’re really just missing out. And then there’s colorblindness. If you’re creating something like slack that has an online/offline indicator, and you only use red and green for people who are colorblind, they see gray and gray. And so what I’m trying to teach the community with digital product creators is that no, you cannot ignore it.
\n\n\n\nYou can ignore accessibility, but then you’re not good at your job. I mean, I don’t mean to say it in an offensive way, but you’re not good at your job if you’re unaware. If you break a rule on purpose, great. But if you don’t know the rule, it’s just a lack of craft, and you absolutely should make it a priority.
\n\n\n\nAnd you’re not doing it as a charity. You’re doing it because you care about your users, and you care about your craft, and you want to build things well, and it’s a necessity. And I think that this is the kind of message that our community needs to hear.
\n\n\n\n[Josepha Haden Chomphosy 00:16:31]
\n\n\n\nI want to touch on something that you sort of brought up a bit, um, at the start of the answer there.
\n\n\n\nSo you brought up the concept of usability. And in the last time that I did a podcast about accessibility, I defined accessibility as a subset of usability. Do you think that if we were to consistently draw that line for people so that it’s not just like accessibility is this thing that you should do outside of usability?
\n\n\n\nIf we were to more consistently draw that line, do you think that that would help people to see and understand better that its shades of existence, usability, and accessibility?
\n\n\n\n[Joe Devon 00:17:10]
\n\n\n\nOh, 100%, a hundred percent. And in my company, we kind of realized that that’s exactly what we have to do. We have to see this as usability.
\n\n\n\nAnd I don’t, we talk about accessibility a lot, but I don’t want to. It’s part of the plumbing for us. We’ve made it part of the plumbing, and I can tell you it’s a struggle to take accessibility and make it part of an organization, even when you’re bringing it top-down, believe it or not. For our teams, particularly the designers, they are blown away by what they’re learning because they’re improving their craft.
\n\n\n\nAnd design is typically where there’s a struggle to get accessibility accepted because there seems to be a very strong idea of what a design should look like. And I think it’s really about the approach because UX and design it’s all about empathy for people. And when you approach it, not as, even though empathy should mean that, that, you know, do the right thing at the same time, it’s more about empathy for your user, and your user includes so much more than just people with disabilities that you haven’t run into somebody that has that disability and therefore you build it better, and it’s, it’s completely blown their mind. They love it. They love doing it. And I’m not hiring people with accessibility coming in. We’re training them to work accessibly.
\n\n\n\n[Josepha Haden Chomphosy 00:18:34]
\n\n\n\nSo I think it’s interesting that you talk about empathy as part of being able to make sure that you’re creating something that’s accessible because I actually feel like empathy is. Like it’s being considered this gold standard for many, many things right now. And I think it actually is more harmful in the long run than instead making altruistic choices.
\n\n\n\nAnd so, I have a blog post that I will link in our show notes that will kind of help everybody see more fully my concept there. But when you rely on empathy, you do kind of have to rely on one, being able to run into all of the issues you were mentioning. You have to know people who have problems in order to know that the problems exist.
\n\n\n\nAnd then you also kind of have to assume that once you have willingly put yourself into the discomfort of that kind of disability, whatever, wherever it exists on that spectrum, your experience of that discomfort is the same as someone who lives with it. And I just don’t think that we can necessarily do that.
\n\n\n\nI always think that trying to do the altruistic thing, like doing your research and figuring out what it is and trying to make decisions on behalf of other people as best you can, which is a terrible thing. Still, like decisions that take into account the experiences that people are sharing with you and then going to them and saying, “does this make that experience better or worse?” is the more sustainable option from my perspective, this is specifically leadership. Still, I think it’s true for accessibility as well, and probably product design as a whole, but it’s very difficult. Like people really feel like they understand the concept of empathy right now. And I do think that sometimes that leads us down the wrong path for things.
\n\n\n\nWhat’s your thought on that? I think you kind of agree based on what your answer was
\n\n\n\n[Joe Devon 00:20:33]
\n\n\n\nOh, no, absolutely. And you know, we, you, can’t never about us without us, as the common saying, and we’ve gathered a group of a hundred people with a wide variety of disabilities for research. Whenever we do any UX and research, and sometimes we’re asked to just do research projects, we go out and ask the users.
\n\n\n\nWe had some really interesting companies approach us to do innovation and accessibility, and they had strong assumptions. We looked at the assumptions and agreed with it, but we’re like, all right, they were smart. They said, “vet this with users for us, please,” because they didn’t want to gather their own group.
\n\n\n\nWe vetted with users, and we’re blown away, always blown away because there are so many things you just don’t know unless you’ve lived with a particular disability. You can’t guess, and you’ve got to speak to your users and a wide variety of them.
\n\n\n\n[Josepha Haden Chomphosy 00:21:30]
\n\n\n\nYes, absolutely. Absolutely. What role does open source play in expanding accessibility, either in specifically the digital space or just accessibility in general?
\n\n\n\n[Joe Devon 00:21:42]
\n\n\n\nI guess if the question is, what role does it play? I would say the role it plays is it is, unfortunately, it makes accessibility worse because, for the most part open source is not very accessible. And it’s a personal passion of mine, so I’m really glad that you brought that up.
\n\n\n\nYou know, it is so bizarre. You write a blog post and then it goes viral, and it goes viral every year to a degree that you can’t even believe it, that all these companies that you know are running events. Privately, publicly talking about it. And then you get all these people thanking you for what you’ve done year after year.
\n\n\n\nAnd then one year, you read on Twitter, The Blind Onion; I’m sure you’re familiar with The Onion, the satirical clip, there’s the Blind Onion. And they tweet out, “Now that Global Accessibility Awareness Day is over, we look forward to 364 days of global accessibility oblivion.” And that really hurt at the time, but at the same time, and I was told to ignore it, don’t worry about it, but I’m like, no, this is coming from a place of pain.
\n\n\n\nAnd the point of GAAD was to make a difference. It wasn’t too to just give everybody an opportunity to say, “Hey, look at what we’re doing,” and then not make a difference. So, as a result of that, I started to think about, well, where are we with this? And, and so I’ve created a state of accessibility report that through my company, we’re able to run for a few years, and it’s not, you know, the state is not great.
\n\n\n\nAnd I’m like, well, what can we do to change things? So, as a result of all of this, I really wanted to figure out, well, what can we do to make sure that GAAD does make a difference? And so, I came up with the idea of the GAAD pledge, which is specifically meant for open source frameworks.
\n\n\n\nAnd the idea of the GAAD pledge is that an open source framework, when they are ready, takes the pledge to make accessibility a core value of the framework. Now, terms of what that actually entails are different for every single project because every project is unique. We did create a bit of a framework, which had the idea of saying, okay, you’re going to, first of all, create an accessibility statement that says that this framework is going to conform to whatever, WCAG, which is Web Content Accessibility Guidelines, to whatever WCAG level is decided and is appropriate for the framework. That there’s going to be documentation for anybody that is downloading this piece of open source project and trying to implement it, that there should be guidelines for them, that all of the examples should be accessible.
\n\n\n\nIt’s really important because even the frameworks that try to pay attention to accessibility. You’ll often see that people from the community will provide examples, and they’re inaccessible. And it’s really sad when you see that because so many people are just copy-pasting. That’s typically how it works, and they’re going to copy-paste something bad. So putting a statement around it, I think, would be really great.
\n\n\n\nAnd what we’re hoping to see is that lots and lots of big open source communities decide to take the pledge. And then it’ll sort of be table stakes that any new open source projects as well look, all of these frameworks that made it, they took the pledge and therefore we should take the pledge as well.
\n\n\n\nAnd so the very first year, we had React Native take the pledge, and they put a lot of effort into their accessibility. The second group to take it was Ember.js, and they always put a lot of effort into their accessibility, and they continued that effort. We’re about to announce the next one, but we’re still two weeks away.
\n\n\n\nSo I can’t say anything yet, but yeah, we’re, uh, we’re hoping for a lot more uptake on, on the gap pledge because it, it affects so many people downstream. WordPress’s what percent of the web right now? 43%? So there you go. That’s so many people.
\n\n\n\n[Josepha Haden Chomphosy 00:25:57]
\n\n\n\nSo many people. Yeah, fun fact Gutenberg, our current rewriting of the editing experience in WordPress, primarily uses React. And so, I’m glad to hear that they have taken that pledge as well.
\n\n\n\nAs with any good cooking, it starts with good ingredients.
\n\n\n\n[Joe Devon 00:26:12]
\n\n\n\nYou said it. That was great. I wish I was a cook, though.
\n\n\n\n[Josepha Haden Chomphosy 00:26:23]
\n\n\n\nI love it. All right. Let’s what keeps you up at night when it comes to the state of accessibility?
\n\n\n\n[Joe Devon 00:26:29]
\n\n\n\nWhat keeps me up at night is how to move the needle. It is such a big thing to change. And there are so many angles that you can approach this with, but at the end of the day, it’s, it’s a monster.
\n\n\n\nIt’s a monster. There are so many legacy sites out there. If you look at WebAIM, they do a yearly report on the state of accessibility as well. They call it the WebAIM Million, and they’re typically seeing 97% inaccessible, 98%. It goes up and down a little bit every year. And that’s, that’s just a huge boat to move.
\n\n\n\nI think we need to at least get the newer, uh, newer websites and mobile apps to move. And what we’ve seen in our state of accessibility report is that only the very top companies seem to put in the effort to make their products accessible. There is a big push with the enterprise companies to do it.
\n\n\n\nThe CEOs are starting to talk about it, but what we need is the entire culture of software development to change. Or I should even say digital product development change and to move that boat is massive. And that’s I put it in my tagline in my email like that’s my mission in life, and I hope to achieve it before I die.
\n\n\n\nSo that keeps me up at night.
\n\n\n\n[Josepha Haden Chomphosy 00:27:52]
\n\n\n\nI think that would keep me up at night as well. I mean, it seems like you are really just personally mission-driven and impact-driven. Do you feel like, in the event that the work that you’ve accomplished so far is what you accomplish, you feel still like you’ve had an impact?
\n\n\n\nI feel like you have had an impact.
\n\n\n\n[Joe Devon 00:28:13]
\n\n\n\nI’m not one of those people that tries to have a legacy or like tries to focus on what my impact is and all of that. I just try and do good work. And hopefully, it just shows at the end of the day. I’m just trying to have the impact without the accolades.
\n\n\n\n[Josepha Haden Chomphosy 00:28:34]
\n\n\n\nI get it. Well, Joe, thank you so much for joining us here on this episode of WP Briefing. You have been a delight to chat with.
\n\n\n\n[Joe Devon 00:28:42]
\n\n\n\nLikewise, it’s really been a pleasure to meet you, and uh, and I appreciate the opportunity.
\n\n\n\n[Josepha Haden Chomphosy 00:28:54]
\n\n\n\nAnd now it’s time for our smallest of big things. As I mentioned at the start, it is packed. Number one tomorrow, May 17th, RC3. So one of the final RCs that we’re going to have for the WordPress 6.0 release, unless something goes horribly, horribly wrong, which I don’t think it will.
\n\n\n\nAnd then, two days after that, Global Accessibility Awareness Day, as I mentioned, will be on May 19th. So, this coming Thursday.
\n\n\n\nAnd then next week, we have the 6.0 release. We have the WordPress 6.0 release on May 24th.
\n\n\n\nThree days after that, WordPress turns 19 on May 27th, starting its final teenage year before we turn twenty in 2023. So that was the rapid-fire dance card for the next two weeks.
\n\n\n\nThe stuff that is happening with and around WordPress for everyone to know. As a heads up, also, many people are headed to WordCamp Europe in Porto(, Portugal). The first week of June, I am going to do a live from WordCamp Europe episode. It will not be live. I’ll just record it live. And so. You know you’ll get to hear me with my hoarsest voice and maybe singing to my computer. Cause that almost always happens at these things.
\n\n\n\nAnd that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy. And I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12855\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WordPress 6.0 Release Candidate 2 (RC2) Now Available for Testing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-2-rc2-now-available-for-testing/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 10 May 2022 18:06:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a: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:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12840\";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:171:\"WordPress 6.0 Release Candidate 2 is now available for testing! You can \ndownload and help test RC2 in three ways. You can also help translate WordPress to 100+ languages.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s: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:4830:\"\nThe next release candidate for WordPress 6.0 is now available!
\n\n\n\nWordPress 6.0 is scheduled for release on May 24th, 2022 – just two weeks from today.
\n\n\n\n“Release Candidate” means that this version of WordPress is ready for release! Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone within the WordPress community check to see if anything was missed along the way. That means the project would love your help.
\n\n\n\nThank you to everyone who has contributed towards testing and logging issues to help make WordPress 6.0 stable (and awesome). WordPress still needs your help testing, especially theme and plugin developers.
\n\n\n\nSince the RC1 release on May 3rd, 2022, there have been approximately 40 issues resolved in Gutenberg and Trac.
\n\n\n\nInstalling RC2
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you RC2 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 RC2 in three ways:
\n\n\n\n- Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
- Option 2: Direct download the release candidate version here (zip).
- Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, or RC1 on a case-insensitive filesystem, please use the following command:
wp core update --version=6.0-RC2
Additional information on the full 6.0 release cycle is available here.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks, which will detail all upcoming changes.
\n\n\n\nPlugin and Theme Developers
\n\n\n\nAll plugin and theme developers should test their respective extensions against WordPress 6.0 RC2 and update the “Tested up to” version in their readme file to 6.0. If you find compatibility problems, please be sure to post detailed information to the support forums so that these items can be investigated further prior to the final release date of May 24th.
\n\n\n\nReview the WordPress 6.0 Field Guide for more details on this release.
\n\n\n\nTranslate WordPress
\n\n\n\nDo you speak a language other than English? Help translate WordPress into more than 100 languages.
\n\n\n\nHow to Help Test WordPress
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\n\n\n\n\n
An RC2 Haiku for You
\n\n\n\nAnticipation
Sprinting toward G/A now
Please — test, translate — thanks!
\n\n\n\n
Thank you to the following contributors for collaborating on this post: @dansoschin, @priethor.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12840\";s: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: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:37:\"The Month in WordPress – April 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2022/05/the-month-in-wordpress-april-2022/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 05 May 2022 15:01: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:22:\"the month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12816\";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:\"This past month saw a lot of preparation work for WordPress 6.0, due to release on 24 May 2022. This major release brings exciting improvements – read on to find out more about the latest happenings in the WordPress project. WordPress 6.0 Release Candidate 1 The first release candidate (RC1) for WordPress 6.0 is now […]\";s: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:\"rmartinezduque\";s: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:10556:\"\nThis past month saw a lot of preparation work for WordPress 6.0, due to release on 24 May 2022. This major release brings exciting improvements – read on to find out more about the latest happenings in the WordPress project.
\n\n\n\n\n\n\n\n
WordPress 6.0 Release Candidate 1
\n\n\n\nThe first release candidate (RC1) for WordPress 6.0 is now available for download. Help improve the project by testing and translating this version to non-English languages. Check out the RC1 release post to learn what’s new and how to contribute. For a more in-depth look at the upcoming changes, you can refer to the WordPress 6.0 Field Guide.
\n\n\n\nWordPress 6.0 is packed with all kinds of improvements for everyone. It brings new blocks, accessibility enhancements, refined design tools, the ability to switch theme styles easily, multi-block partial text selection, and a new block locking interface, to name a few of its highlights.
\n\n\n\nGutenberg releases: Versions 13.0 and 13.1 are here
\n\n\n\n- Gutenberg 13.0 shipped on April 14, 2022, and introduced the final updates that will be part of WordPress 6.0. These include an improved editor experience (with the ability to select text across blocks), better responsive blocks, and prominently exposed block patterns.
- Gutenberg 13.1 landed on April 27, 2022. This version adds border support to the Columns block and accessibility and Comment block improvements.
Team updates: Updated guidelines for in-person events, redesign of the Gutenberg page, and more
\n\n\n\n- The Community team announced updated Covid-19 guidelines for official WordPress events.
- The redesign of the Gutenberg landing page on WordPress.org is nearing completion.
- #WPDiversity announced new meeting times for Asia-Pacific (APAC) areas. You can express your interest in this post.
- The Training team plans to migrate the Contributor Training materials to Learn WordPress. This move will help consolidate all the community-based training content in one place.
- All learners on Learn WordPress can now enjoy using a live WordPress demo site as they go through courses on the site.
- The first stable version 1.0.0 of the Performance Lab plugin was released.
- Read the latest edition of the Meetup Organizer Newsletter.
- Everyone is welcome and encouraged to join the new Photo Directory team meetings. They are held on the first Friday of every month at 14:00 UTC in the #photos channel of the Make WordPress Slack.
- The Performance team published a follow-up post with the next steps on the WebP proposal.
- Check out the projects the Design team contributed to over the past couple of weeks.
- Official Featured and Beta plugins now limit ownership and committer changes.
- The April 2022 edition of the Polyglots Monthly Newsletter was published.
- The latest edition of People of WordPress features Meher Bala, a frontend web developer and community builder from India.
- The #props channel of the Make WordPress Slack is now connected to the WordPress.org profile activity! This way when you give props, it will be included on your WordPress.org profile and the profile of those you mention. This change is part of a larger project that will help credit more non-code contributions.
Open feedback/testing calls
\n\n\n\n- Following this proposal for a WordPress Project Contributor Handbook, Executive Director Josepha Haden opened a round of discussions to share feedback on the various handbook sections.
- Version 19.8 of WordPress for Android and iOS is available for testing.
- Join the 14th testing call of the Full Site Editing (FSE) Outreach program – “Rallying Recipe Reviewers.” This call focuses on testing blocks that help recipe authors make their recipe blogs more interactive. Leave your feedback by May 18, 2022.
Get ready for WordCamp Europe in Porto
\n\n\n\n- We are four weeks away from WordCamp Europe. After being postponed twice due to the pandemic, the WordPress event is taking place in Porto, Portugal, on 2-4 June 2022. Check out the schedule and get your tickets if you haven’t yet!
- WordCamp US announced a new program to support underrepresented speakers.
- WordCamp Irun (Spain) is happening this month on May 21 and 22, 2022.
\n\n\n\n
Have a story that we could include in the next issue of The Month in WordPress? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this Month in WordPress: @rmartinezduque, @cbringmann, @dansoschin.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12816\";s: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:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 6.0 Release Candidate 1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-1/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 03 May 2022 17:18: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:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a: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:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12799\";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:171:\"WordPress 6.0 Release Candidate 1 is now available for testing! You can \ndownload and help test RC1 in three ways. You can also help translate WordPress to 100+ languages.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s: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:7242:\"\nThe first release candidate (RC1) for WordPress 6.0 is now available!
\n\n\n\nThis is an important milestone on the 6.0 release cycle journey. “Release Candidate” means that this version of WordPress is ready for release! Before the official release date, time is set aside for the community to perform final reviews and help test. Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone within the WordPress community check to see if anything was missed along the way. That means the project would love your help.
\n\n\n\nWordPress 6.0 is planned for official release on May 24th, 2022, three weeks from today.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you RC1 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 RC1 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the release candidate version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, or 4, on a case-insensitive filesystem, please use the following command:wp core update --version=6.0-RC1
Additional information on the full 6.0 release cycle is available here.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.
\n\n\n\nWhat’s in WordPress 6.0 RC1?
\n\n\n\nSince Beta 4, various items have been addressed, including (but not limited to):
\n\n\n\n- Backport updates of Comment blocks tests (#55643)
- Backport a bugfix of Comment Template block pagination (#55658)
- Editor: Backport bug fixes for WordPress 6.0 from Gutenberg (#55567)
WordPress 6.0 is the second major release for 2022, following 5.9 which became generally available in January. This release includes nearly 1,000 fixes and enhancements spanning most areas of the WordPress platform. Some key highlights within the content creation and site-building feature sets include:
\n\n\n\n- Style Switching: switch up the look and feel of your site, all in one block theme. No need to change themes!
- More template options: use blocks to edit five more templates (author, date, categories, tag, and taxonomy).
- Multi-select: Easily select text across multiple blocks. Edit to your liking.
- Retain Styles: Keep your custom styles in place, whether transforming between blocks or creating new buttons.
- More patterns in more places: the Quick Inserter surfaces patterns that might work well for the condition you’re in, baking in relevant patterns for template parts and pages you’re working on.
- List View improvements: New keyboard shortcuts (shift + click) let you select multiple blocks to modify in bulk (reposition, delete, etc.), see your content at a glance with a collapsed by default view, and more.
- Refined design tools: Explore a new color panel, transparency options, more group block variations to create new layout options (Stack, Row), the ability to set your featured image in a Cover block, control the exact size of your featured image, gap support for the Gallery block, and more.
- New blocks: Various Post Comments, Read More, No Results in Query Loop, Post Author Biography, Avatar blocks.
- Block Locking: Choose to disable the option to remove a block, move it, or both, right in the editor.
- Export block themes: Explore the improved block theme export tool, as WordPress heads closer to codeless visual block theme building.
Plugin and Theme Developers
\n\n\n\nAll plugin and theme developers should test their respective extensions against WordPress 6.0 RC1 and update the “Tested up to” version in their readme file to 6.0. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24th.
\n\n\n\nReview the WordPress 6.0 Field Guide, for more details on what’s contained in this release.
\n\n\n\nTranslate WordPress
\n\n\n\nDo you speak a language other than English? Help translate WordPress into more than 100 languages. This release also marks the hard string freeze point of the 6.0 release cycle.
\n\n\n\nHow to Help Test WordPress
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\n\n\n\n\n
Haiku Fun for RC 1
\n\n\n\nRelease candidate
Our journey nearly done
Get ready, WordPress
\n\n\n\n
Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat, and @annezazu.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12799\";s: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:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 6.0 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/2022/05/wordpress-6-0-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:\"Mon, 02 May 2022 16:46:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a: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:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12787\";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:103:\"WordPress 6.0 Beta 4 is now available for testing! You can download and help test Beta 4 in three ways.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s: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:5813:\"\nWordPress 6.0 Beta 4 is now available for testing!
\n\n\n\nBeta 4 was not part of the originally published development cycle. It is aimed at providing an opportunity for testing some specific issues that were resolved since Beta 3. WordPress will continue with the regularly scheduled release milestones on May 3rd, 2022, with the RC1 release.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you test Beta 4 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 Beta 4 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: Use WP-CLI to test: wp core update –version=6.0-beta4.
Do not use this option if your filesystem is case-insensitive.
The current target for the final 6.0 release is May 24, 2022, which is in less than a month!
\n\n\n\nAdditional information on the full 6.0 release cycle is available.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.
\n\n\n\nExplore What’s in Beta 4
\n\n\n\nSince Beta 3, various items have been addressed, including (but not limited to):
\n\n\n\n- Update post content placeholder (#40177)
- Comments block: Fix glitches found while backporting (#40628)
- Show add pattern label when patterns are being prioritised (#40598)
- Fix regression with featured images in latest posts (#40662)
- Navigation Link: Avoid unnecessary re-renders (#40696)
- Navigation: Improve selector performance (#40700)
- Comments Title: Count toggle working in ‘Singular’ editing mode (#40728)
- [Writing Flow]: Try to fix multi-selection with shift+click (#40687)
- Fix alignment issue with comment author name (#40610)
- Comment Content: Show moderation message (#40612)
- Display paragraph breaks in comment contents block (#40667)
- Fix style comment awaiting moderation indentation (#40681)
- Fix: Page patterns don’t show when only one pattern is available (#40707)
- Update the placeholder for post excerpt (#40178)
- REST API: Fix regression in the Pattern Directory endpoint. (#55617)
- REST API: Fix the scheme for the Block Directory search endpoint. (#53621)
- Show comments previews in the Comment Query Loop. (#55634)
- Avoid DB error in comment meta queries. (#55218)
How to Help
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\n\n\n\n\n
Another Haiku, Just for You
\n\n\n\nBeta four, surprise!
Iterating all day long
Time to share and test
\n\n\n\n
Thank you to the following contributors for collaborating on this post:
@dansoschin, @annezazu, and @costdev
In the thirtieth episode of the WordPress Briefing, Executive Director Josepha Haden Chomphosy and special guest Channing Ritter give listeners a sneak peek into the WordPress 6.0 release ahead of the Release Candidate 1 (RC1).
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Special Guest: Channing Ritter
- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Santana Inniss
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- Twenty Twenty-Two Theme
- Block Locking
- Beginner’s Guide to Contributing, Josepha Haden Chomphosy
- WordSesh
- Social Learning Spaces
- WordCamp Europe Contributor Day
Transcript
\n\n\n\n\n\n\n\n[Josepha Haden Chomphosy 00:00:00]
\n\n\n\nHello everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nTomorrow’s a big day. It marks the beginning of what is called the RC period, or release candidate period, for the current major release of the WordPress CMS. If you’re not super familiar with the way release cycles work, this is the point in the process where the code should pretty much be done changing.
\n\n\n\nThat way you can call in your designers, developers, and anyone else who builds things for others using your software. And they can either start testing their products on it, or they can figure out what new things they need to be able to teach their clients, whichever is most relevant to them. That is generally true for WordPress as well, but in true open source fashion, there is a caveat built in that helps us to get in last-minute, vital changes from contributors.
\n\n\n\nWe have a two-person sign-off rule that’s been around for about as long as I can remember, but lets things be added late in the release cycle, as long as there are two sign-offs from qualified contributors. Most of the time, those qualified contributors are lead developers of the project, but not always. We have a good group of people who are around helping us make sure that this is doable and the best thing that we can offer to all of our users.
\n\n\n\n[Josepha Haden Chomphosy 00:01:50]
\n\n\n\nAnd so, yeah, two-person sign-off, that is the little bit of release process trivia that you never knew you needed. And since we’re looking at a release trivia, kind of hidden bits of how software is made, I actually have a guest with me today, Channing Ritter. So Channing is a product and visual designer based in Brooklyn, New York.
\n\n\n\nShe’s a design director at Automattic and has been working on the WordPress project as a full-time sponsored contributor since January, 2021. She is joining us to share some behind the scenes intel on what’s going into the 6.0 release, her role in that process, and then we’ll just kind of see how the conversation goes from there.
\n\n\n\n[Josepha Haden Chomphosy 00:02:40]
\n\n\n\nWell, and with that, I’d like to welcome Channing to the WordPress Briefing. Hi Channing!
\n\n\n\n[Channing Ritter 00:02:45]
\n\n\n\nHey Josepha. Thanks so much for having me.
\n\n\n\n[Josepha Haden Chomphosy 00:02:48]
\n\n\n\nI’m excited to have you here. If I understand, you are working on the design side of things with the release. So why don’t you tell me a little bit about the role you’ve played?
\n\n\n\n[Channing Ritter 00:02:59]
\n\n\n\nI am. I am the design release lead for the 6.0 release. And if I understand correctly, this is a position that has been unfulfilled for the past few release cycles. So I’m kind of the first person to step in over the past few releases. And I think that’s really exciting, especially because design has started to play such a more important role in the WordPress project over the past few years.
\n\n\n\nSo it makes sense that design would have a seat at the table, and I’m really excited to be helping advocate for the design team and learning from other folks on the release squad. Who’ve been doing this for a while.
\n\n\n\n[Josepha Haden Chomphosy 00:03:33]
\n\n\n\nSo. First big question about 6.0, what is the feature that you are most excited about?
\n\n\n\n[Channing Ritter 00:03:39]
\n\n\n\nI’m most excited about the style switcher within the global styles panel. Um, so if folks still don’t know what I’m talking about there, it’s the ability to change between different variations of the theme.json without actually switching the theme.
\n\n\n\nSo this is a way to get a drastically different look and feels across your site with just a single click. And I see it as a really fun place to experiment and kind of get inspired for the different ways your site could appear without ever having to change your theme.
\n\n\n\nAnd in terms of the Twenty Twenty-Two variations, they’re just really gorgeous and all so diverse. Like you have the main default theme that has the deep green and kind of peachy colors and this really elegant type treatment with a really thin Serif typeface. But then the variations are so different from that. And I think my favorite one is the Swiss variation.
\n\n\n\n[Josepha Haden Chomphosy 00:04:36]
\n\n\n\nThe Swiss variation?
\n\n\n\n[Channing Ritter 00:04:38]
\n\n\n\nYeah, every graphic design nerd loves Swiss design.
\n\n\n\n[Josepha Haden Chomphosy 00:04:42]
\n\n\n\nOh, ok! Now I know!
\n\n\n\n[Channing Ritter 00:04:38]
\n\n\n\nReally awesome things found in there. It’s a really high contrast, bold variation. It’s kind of black and white with red accents. I just love how different it is from the default style and how easy it is to change up your site and just get a whole drastically different look and feel.
\n\n\n\n[Josepha Haden Chomphosy 00:05:00]
\n\n\n\nThat’s excellent. So for folks who do not know what we’re referring to, when we talk about the Twenty Twenty-Two variation, that is the default theme, Twenty Twenty-Two. I’ll put a link to both the classic and block-based versions in our show notes, but you’ll want to use the block-based version to look at these style variations that Channing has mentioned here.
\n\n\n\n[Channing Ritter 00:05:24]
\n\n\n\nYou know, we’re really excited that the first-ever default block theme was released with 5.9, which is when Twenty Twenty-Two first went out and was bundled with 5.9.
\n\n\n\nBut now, with 6.0, I think even more so it’s starting to showcase the real power of block themes and what can actually be done there. And style variations is a huge kind of first step into this new world of block themes and starting to really open up the possibilities and all the flexibility that you have there.
\n\n\n\n[Josepha Haden Chomphosy 00:05:55]
\n\n\n\nYeah, absolutely. So when we’re talking about the Twenty Twenty-Two default theme, when we’re talking about switching these variations inside the theme itself, that seems to me to be a very user-focused kind of feature. And when we talk about users in WordPress, there’s a lot of room for interpretation. Like if we look at it kind of in a framework of three types of users of WordPress, you have, like end-users. So people who are site owners using it as a site to, like, enable their business.
\n\n\n\nBut you also have mid-end users—people who use it to build sites for others. And what I like to call back-end users, people who are using WordPress as a framework. And of course at the start of the Gutenberg project, way back in forever, a million years ago, one of the big calls to action that we had around even, like, trying to do this, was that we wanted to make WordPress easier for users. Just plain users.
\n\n\n\nAnd, and to me, that means making WordPress easier for those mid-end users, people who are creating WordPress sites for other people. But also should give some power and autonomy back to those end-users, the people who are using sites to enable their business or are site owners.
\n\n\n\n[Josepha Haden Chomphosy 00:07:14]
\n\n\n\nAnd so in that context, between 5.9 and 6.0, do you feel like we have features that are really giving that kind of power and agency back to our end-users? Do you feel like we have some features that are really focused on those mid-end users, as opposed to our backend users? For a long time, we focused heavily on enabling our backend users, and now Gutenberg kind of moves us into those other two areas.
\n\n\n\nAnd so do you think that things like being able to switch between your style of variations, other things like that are moving us closer to that particular goal of Gutenberg?
\n\n\n\n[Channing Ritter 00:07:51]
\n\n\n\nThat’s a great question. I think it’s both. I think some of the features being released in 6.0 are absolutely going to empower that end-user.
\n\n\n\nParticularly in terms of improvements around design tools and some of the quality of life improvements. For example, partially selecting across multiple blocks and being able to partially select texts there. That’s the type of thing that really brings the writing experience in the editor to be on par with how you would expect a text editing experience to work.
\n\n\n\nAnd there are tons of small quality of life improvements in this release that I think are really gonna help those end-users. But there are also improvements around what we might call the maintainers who are building sites for others. I think block locking in particular is something that is really going to start filling a gap between people who build the sites and then people who do the day-to-day maintenance within a site.
\n\n\n\nFor example, in 6.0, we’re introducing some interface UI around block locking, but also there’ll be control around the ability to lock user roles.
\n\n\n\n[Josepha Haden Chomphosy 00:09:03]
\n\n\n\nWhich I think makes a lot of sense. I mean, we have all of these user roles in the CMS itself, and for a long time, we’ve just been like free for all on blocks, which was great and is great and should be available to people.
\n\n\n\nBut also if we are saying, like, it makes sense to have this gradient of users and their abilities for the CMS itself, and we are saying that we want to move control of the website and the content to be at the base layer in these blocks, then it also makes sense that we should be able to provide that same sort of granular level of access in the blocks.
\n\n\n\nSo I think that’s a great thing. If you all, if dear listeners, you do not know what we mean by “block locking,” I’m sure that I can find a link for us in our show notes below as well. If for anyone who’s been talking through Gutenberg things with me for a while, you know that this is one of the primary use cases that I think has been a long time coming.
\n\n\n\n[Josepha Haden Chomphosy 00:10:05]
\n\n\n\nIt was one of the first examples that I offered to folks when we had that question of like, who is this being built for? In what way is this beneficial to that mid-end user, as opposed to just giving all of the power and autonomy to users in a way that maybe is not the best for their visitors?
\n\n\n\nThis is one of those use cases that made the most sense to me being able to say, okay, well, the opportunity to, as somebody who runs an agency and is building websites for people to be able to say, yeah, ‘You can do anything that is possible in this instance of WordPress and all the things that you are allowed to do will not break your instance. It won’t break your website’.
\n\n\n\nAnd so it gives a lot of time back to agencies to focus on their client’s most important problems, as opposed to not knowing how to update the hours in their footer or something like that. And so I’m very excited about that particular feature.
\n\n\n\n[Channing Ritter 00:11:01]
\n\n\n\nIt’s such a long-requested feature. I mean, we’ve been hearing requests around this particular feature for years and, you know, often when something gets requested over a span of years like that, it’s because there are some complexities to figure out how it works.
\n\n\n\nAnd that’s definitely been the case with moving forward with block locking. And there are a lot of nuances there. But I think what you were saying, I totally agree with. There’s always a push and pull. And as we enable more and more flexibility for end-users, there needs to be a little bit of push from the other side to kind of give more granular controls, more locking options, and make sure that everything can still be easily maintained.
\n\n\n\n[Josepha Haden Chomphosy 00:11:43]
\n\n\n\nYeah, we mentioned in that answer the concept of maintainers. If you are a contributor, it’s not that kind of ‘maintainer.’ So if you’re a WordPress contributor and we said maintainers there, um, just know that that’s not what we’re referring to. If you don’t know what I’m talking about when I say ‘contributor,’ there is a whole community of open source people and maintainers are people who specifically take care of a particular part of the WordPress software or the WordPress project, um, that makes all this possible.
\n\n\n\nSo there’s, ya know….
\n\n\n\n[Channing Ritter 00:12:19]
\n\n\n\nSo true! The maintainer has another meaning in this context.
\n\n\n\n[Josepha Haden Chomphosy 00:12:20]
\n\n\n\nYeah, we have a mix in our audience and I love it, but it also makes me frequently spend like 10% of my podcast being like, by the way, when I said this, I didn’t mean you, but I did mean you, which makes it harder. I know.
\n\n\n\nSo. You’ve been with the project for a little bit, but if I recall correctly, this is the first time that you were, like, leading part of a release.
\n\n\n\nSo what would you say was the most challenging part of that?
\n\n\n\n[Channing Ritter 00:12:52]
\n\n\n\nAnother great question. This is my first time being this closely involved with the release. Although I was involved with the 5.9 release, but mostly in a release assets capacity. So I helped with the About Page and the welcome banner that goes on the dashboard.
\n\n\n\nSo I did get some insight in the last release cycle. Which was great preparation for being more involved as a release lead on this cycle. From the design perspective, one of the hardest things is always going to be figuring out what exactly goes into the release and what needs more time. In the sense, you know, that there might be some features that need to stay in the Gutenberg plugin for a while and get more testing before they get released to a much wider audience in a major WordPress release.
\n\n\n\nSo I think on the design side, we definitely have some goals that are big, long-term projects that are likely going to span across, you know, many releases, maybe even over many years. And I think the full site editor is a great example of that in a sense that it’s not something that you just were gone in one release and then it all gets released and then it’s all good to go.
\n\n\n\n[Channing Ritter 00:14:06]
\n\n\n\nIt’s something that has to be staggered across many releases, and there’s a lot of thought that goes into it; does this make sense in this more limited capacity, and what else needs to go in in order for this feature to go in? And the most complex things about the WordPress project is how interconnected things are.
\n\n\n\nSo when you start making those decisions about what should go in, what should get pulled out, often there’s sort of a domino effect of like, well, that would affect this feature and then, well, maybe they shouldn’t go in, or maybe this does need to go in. And that is really one of the most challenging, but also one of the most fascinating aspects of the release process.
\n\n\n\n[Josepha Haden Chomphosy 00:14:46]
\n\n\n\nYes. It is very, very true that there are kind of no small problems left in WordPress. *laughs* Yeah, when we, when we first started with this like bigger release squad, cause that has not been routine for the history of the project. When we first started with that, I know that expanding out the exposure to like how much one change affects 25 different things was really, it was really good for all of us to be reminded.
\n\n\n\nAnd as I mentioned at the top of our episode today, tomorrow begins the RC period. It begins the release candidate period, which is when it’s supposed to be, as locked down as possible. But if you all have been following along with our release process in general, which if you’re listening to this, you probably have, you know that last week or a couple of weeks ago, we had this whole question about the Webfonts API, and we had that conversation in a public space as best we could,
\n\n\n\nLike, there are always things that you can’t, like, fully disclose in public spaces, but we had a very open and transparent conversation about, like, who is most affected by putting it in, in the state that the API was in. And, who’s most affected if we take it out. And where can we make compromises on either side so that both sides are a little happy and a little unhappy?
\n\n\n\n[Josepha Haden Chomphosy 00:16:09]
\n\n\n\nAnd, like, that is all so hard to do. Not only in general. We have a 20-year-old code base and a five-year-old code base. And it’s all a big, big undertaking to understand what is happening and where it happens. And so there’s this moment always when we are trying to decide, like, is this baked enough? Did we put it in too early? Should we pull it out? How, if we pull it out, did we ask people to do too much work before we decided to pull it out anyway?
\n\n\n\nLike, you always have those kinds of questions about it. And honestly, I think that most of us weren’t around the last time, that WordPress was, was this experimental in public, like it’s always been open source. It’s always been experimental and iterating publicly, which is just the hardest way to work on anything. We like, we shipped our best guesses. Don’t be mad. It’ll be… we’re coming for it. We’re going to fix it. Like, that’s always hard, but the last time around, when it was this substantial a change was, like, 2008 or something, like, it was ages and ages ago.
\n\n\n\n[Josepha Haden Chomphosy 00:17:14]
\n\n\n\nAnd we were smaller than, we had a smaller number of contributors. We had a smaller group of people actually using the CMS. And so over time it has gotten more and more complicated. And, and I don’t think that we can ever understate the complexities of that. And so for you, you had a little bit of exposure to it in 5.9 and then showed up for like really doing it in 6.0.
\n\n\n\nHas it been a surprising change? Like, were you surprised much more by how complicated it was when you were closer to it?
\n\n\n\n[Channing Ritter 00:17:47]
\n\n\n\nYeah, definitely. It’s been a real learning process, especially coming to understand how much there really are no easy answers. I think a lot of us are in the release squad are real problem solver types of people and, and want it to, you know, be a really neat, tidy answer.
\n\n\n\nAnd it’s not always the case. You know, sometimes parts of the feature might go in, or some contingency plan might get put into place and things didn’t go exactly as planned. But what you said of being an experiment and being on kind of the cutting edge of trying out new things, I think there is a lot of passion around that in the WordPress project.
\n\n\n\nRight now, we’re in such a transitional period for the project, you know, moving from classic themes to block themes and really changing the ideas of how we approach designing sites. And because of that, I think there is a lot of momentum and energy around getting new features, as many new features as possible into each release. But there’s also, you know, a lot of testing and stuff that needs to happen.
\n\n\n\nAnd to make sure that, like you said, these things aren’t going out too early.
\n\n\n\n[Josepha Haden Chomphosy 00:19:01]
\n\n\n\nWell, and there’s always that difficulty, we’re going to just leap right into open source areas now. There’s always that difficulty around, like, there’s this concept that when, like, we always want to ship something that doesn’t break backward compatibility when possible, we don’t want to ship vulnerabilities. Like, that’s always true, but we are in an open source project, and open source projects are necessarily kind of tolerant of like, that’s not our best, but like it skates, right?
\n\n\n\nThis was, we aimed for Ferrari and got a skateboard because sometimes you got to start with a skateboard, right? *laughter* Like if it gets you from one place to another, that’s kind of where we’ve got to aim some days.
\n\n\n\n[Channing Ritter 00:19:45]
\n\n\n\nTotally.
\n\n\n\n[Josepha Haden Chomphosy 00:19:46]
\n\n\n\nAnd that’s always so, so difficult, especially cause, like, for the big change that 5.0 represented, and that 5.9 represented– 6.0 is not as big a shock as 5.9 was. But, like, as big a change as those represented, it still skates. And that’s, I think what makes the work especially hard, especially nuanced. And like, we haven’t gotten together as human beings in two years. And so sometimes people just kind of forget there’s a human being back there.
\n\n\n\nWe’re humans. Everyone be nice. Yeah. I don’t know that part of running a release definitely was surprising to me. My first release that I ran was 5.0 and…
\n\n\n\n[Channing Ritter 00:20:31]
\n\n\n\nOh, wow!
\n\n\n\n[Josepha Haden Chomphosy 00:20:32]
\n\n\n\nYeah, it was, like, that was 2018. And then I became the executive director at the top of 2019. And I distinctly remember one core chat where I showed up and just was like the most transparent, vulnerable person we’ve ever experienced in life.
\n\n\n\nThat’s not true. We have very vulnerable people in the project and very transparent people, but I told everyone like, there are a million of you and one of me, and it’s kind of terrifying that you’re leaping on me in this—like you’re scaring me a lot right now. And that was quite a thing to say to like, all these… it’s terrifying! Right?
\n\n\n\n[Channing Ritter 00:21:12]
\n\n\n\nI love when you see that type of vulnerability in the project. I think it takes… it takes a degree of comfort and familiarity with the project to even be able to admit to that. And to me, that’s a real sign of growth in the project. Like when I first started contributing, I don’t think I ever would have just said, like, ‘How is the feature supposed to work? I have no idea.’ That’s something that I say all the time now.
\n\n\n\n*Laughter*
\n\n\n\nAnd you know, that is completely fine and more than okay. It’s a massive project. There are folks who have done deep thinking about a feature over the course of years. You know, and there are experts who can help shed light on various problems that maybe you just haven’t had a chance to dive into yet and really understand the nuances of yet.
\n\n\n\nSo that’s the amazing thing about open source is that you can lean on folks who do have expertise in that particular area. You’re not expected to be an expert-expert in every single domain. It’s okay to say, I don’t really have a good idea or a good concept of this feature. I don’t have a good feeling for it. What do other folks think?
\n\n\n\n[Channing Ritter 00:22:24]
\n\n\n\nAnd even people who have been in the project for a long time, decade plus, still say that all the time. You know, or you might just say, like, I have a really rough idea of how this works, are other people seeing this the same way? Or did other people have a different, you know, mental picture of how this might work?
\n\n\n\nEven if, sometimes it feels like you’re over-communicating, it’s really helpful because often people do have really dramatically different ideas about how a feature might take shape.
\n\n\n\n[Josepha Haden Chomphosy 00:22:49]
\n\n\n\nAnd I hope that’s one of the things that we never lose in the project. Like we are an old, old project now and we support a bunch of the web with a tiny, tiny group of people compared to the amount of the web that we support.
\n\n\n\nAnd I hope that we always have that opportunity as senior leaders, which I am, and all of our upcoming leaders to all of us, just at some point, be like, can we stop the train? I don’t understand. I don’t understand that. Um, and not necessarily feel that that has made us a worse contributor. Cause I think that it’s when we are transparent about our lack of understanding.
\n\n\n\nThat’s when we have the opportunity to make what we’re offering to the world more solid and always better.
\n\n\n\n[Channing Ritter 00:23:35]
\n\n\n\nI love it. I think it’s the, one of the most lovely things about the WordPress community. There’s really low judgment around those types of questions and people are really inclusive and more than happy to take a moment to explain something to you or shed some light on an issue you might not have thought that much about.
\n\n\n\nI think that’s one of the best things you can always reach out for help. And folks are always willing to provide guidance or context or even historical information about, you know, whether it’s been tried in the past or previous explorations and that sort of thing.
\n\n\n\n[Josepha Haden Chomphosy 00:24:10]
\n\n\n\nAll right. Well, that covers all of my questions for you. Do you have a final thought about the release that you would like to share with everyone you don’t have to, if you don’t want to, not everyone has like a final sign off.
\n\n\n\n[Channing Ritter 00:24:25]
\n\n\n\nYeah. One of the things I’m most excited about for this 6.0 release is all of the improvements around design tools.
\n\n\n\nAnd these are just small improvements around a ton of different things, like the color panel, border controls, gap support, typography options, flexible container blocks, etc. These are the types of tools that are a designer’s dream. You know, they really make the difference between being able to make a really crisp, finished looking final product and having something that’s a little rough around the edges.
\n\n\n\nAnd as a designer, like those are the things that your eye goes straight towards. And all of these nuanced new tools, they really allow designers to have that fine detailed control to create really pixel perfect sites. And I think that’s something that, you know, myself and a lot of others on the design team are just so beyond excited about.
\n\n\n\n[Josepha Haden Chomphosy 00:25:25]
\n\n\n\nExcellent. Well, Channing, thank you so much for joining us today on the WordPress Briefing; it has been an absolute delight.
\n\n\n\n[Channing Ritter 00:25:32]
\n\n\n\nThank you for having me.
\n\n\n\n[Josepha Haden Chomphosy 00:25:41]
\n\n\n\nAnd now it is time, woohoo, for the small list of big things. My favorite part of this podcast, that’s not true. I have a lot of things that I love about this podcast. I just, in particular love being able to share like three things that are coming up in the next couple of weeks that everybody should be aware of. And I really particularly like the list I have this week.
\n\n\n\nFirst as of today, we are two weeks away from WordSesh. If you’re looking forward to your first in-person WordPress event, but feel like you could use a little foundation information, a little bit of a WordPress primer, then this event has a lot of excellent thought leaders in the project that you can learn from.
\n\n\n\nIf you’re looking for more practical or hands-on opportunities, uh, you can also check out social learning spaces. All of those are free for anyone. So I will include links to both of them in the show notes.
\n\n\n\n[Josepha Haden Chomphosy 00:26:30]
\n\n\n\nSecond, as of today, we are four weeks away from WordCamp Europe. This is one of our flagship events. So it also includes a contributor day, which I encourage you to look into. If you have never heard of one before. I will be there to meet some of the contributors that have joined the project since the end of 2019. And hopefully, I will see you there as well. If you’ve never heard of a contributor day, then I’ll include a link to the beginner’s guide to contributions, a little talk that I gave in 2017 in the show notes that should help you get your bearings or at the very least know what questions to ask yourself to figure out if a contributor day is right for you.
\n\n\n\nAnd then the third thing as of today, it has been one week since Ian Dunn and the Meta developers… Um, that sounds like a band… Ian Dunn and the Meta developers connected the props channel in the community Slack to WordPress.org profile activity. I’m really excited about this. It’s the first in a long list of changes that are part of a larger project to credit more non-code contributions, more contributions that are not specific to a major release or event.
\n\n\n\nAnd also to set us up to be able to provide more quality checks and balances for our growing Five for the Future program. If you’ve not been over there lately, if you’re not super sure what I’m talking about, there’s a link to the discussion post that we had about it, but also you can wander right over into the Making WordPress Slack and check out the props channel to just kind of see a running list of contributors that people are really grateful for. Which, frankly, if you ever are having a bad day, that is a wonderful place to just kind of wander in and see all of the positive vibes that people are sending around to each other.
\n\n\n\nUh, yeah, so the props channel, is always good. Uh, and that my friends is your small list of big things. Thank you for tuning in today for the WordPress Briefing.
\n\n\n\nI’m your host, Josepha Haden Chomphosy. And I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12742\";s: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:75:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"People of WordPress: Meher Bala\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2022/04/people-of-wordpress-meher-bala/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 30 Apr 2022 09:20:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:7:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:9:\"HeroPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:15:\"WordCamp Mumbai\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:6;a:5:{s:4:\"data\";s:16:\"wptranslationday\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12706\";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:106:\"This month\'s People of WordPress feature shares the story of developer and e-commerce builder Meher Bala. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"webcommsat AbhaNonStopNewsUK\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:16652:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a Indian-based WordPress developer and long term contributor on how it helped her find a career and a local and global community to belong to.
\n\n\n\n![\"Meher](\"https://i2.wp.com/wordpress.org/news/files/2022/04/meher-1.jpg?resize=1024%2C515&ssl=1\")
WordPress is an inspiration to Meher Bala, a frontend web developer and community builder from India. From using the software as a basic website tool to helping entrepreneurs and good causes around the world fulfill their aspirations, she has overcome personal barriers and now aims to inspire others.
\n\n\n\nMeher found her vocation and learned new skills through WordPress. She also discovered a way to encourage other women to consider careers in IT.
\n\n\n\nOpening the doors to a career in technology
\n\n\n\nAs a child, Meher was diagnosed with dyslexia (difficulty in reading the written word) and dyscalculia (difficulty in comprehending numbers and mathematical functions). With the support of her parents and a tutor, she was able to overcome this learning obstacle. She developed coping techniques and a determination to work to overcome challenges as they appeared later in life.
\n\n\n\nIn school, she got an opportunity to replace one subject with computer studies as an alternative. This proved to be an eye-opener to future career possibilities.
\n\n\n\nShe began to research not only what the internet had to offer but also how it worked, including the new and fascinating concepts of email and websites. Her father bought the family’s first desktop computer so she could do her research at home.
\n\n\n\nMeher’s father wanted to turn her love for computers into something that would serve her well in the future. In 2005, he enrolled her in a short computer course from a global IT training provider. The course tutor was so impressed with her performance, she was advised to enroll in a four year software development course.
\n\n\n\nThat meant she had studied the software development course alongside her higher education college course. Looking back, she enjoyed the dual challenge of the degree course in commerce, and the experience prepared her well to keep learning software while working as a developer. Within three years, she had learned C#, C, C++, HTML, Java, and .NET.
\n\n\n\nAfter graduation, she was in a dilemma to choose between commerce and IT. What to choose? She had a compulsory one-year technology internship to complete, and her choice of focus for that year would prove to be a defining moment.
\n\n\n\nIn 2009, on her birthday, Meher was offered an internship. On the first day of the internship, she was introduced to WordPress. Her initial assignment was to change the look and feel of the WordPress dashboard — in just six hours. But there was a problem – she had never worked with WordPress before!
\n\n\n\n\n\n\n\n“I stared at the whiteboard and thought that task given was impossible and difficult to meet the deadline. I wondered if my boss was joking and did not know then what you could do with WordPress as a developer and how it could slot into your toolbox. It opened my eyes.”
Meher Bala
Meher used her research skills to know more about using WordPress. She found a plugin that would help her achieve her task. She met the deadline and it ingrained an interest that she would never lose.
\n\n\n\nRe-discovering WordPress
\n\n\n\nFive years after her initial WordPress experience, Meher was assigned to lead an international project in WordPress. She was hesitant — she had lost touch with the CMS during that five years, but the project was a great opportunity to become a team leader and lead from the front.
\n\n\n\nShe decided to update her WordPress skills, relying again on the strength of her research skills and determination. In the process, she also taught her team all about WordPress, inspiring many of those members to continue to develop their WordPress skill set.
\n\n\n\nThe success of that project was a pivotal moment for Meher and a new dawn as a developer specializing in WordPress.
\n\n\n\nAs a team lead, Meher soon found it was not possible to always have all the answers straight away. She found internet searches gave practical solutions—but rarely explained the theory behind it.
\n\n\n\nSo she went looking for a WordPress group to help her expand the scope and depth of her knowledge.
\n\n\n\nFinding the community and its developer learning opportunities
\n\n\n\n![\"Meher](\"https://i2.wp.com/wordpress.org/news/files/2022/04/dsc_00345.jpg?resize=999%2C667&ssl=1\")
In 2015, while browsing Facebook, Meher came across an advertisement for something called WordCamp Mumbai, an event that had taken two days before. She did a little digging to learn what a WordCamp was, and about the people behind it. She took the plunge and joined the WordPress Mumbai Meetup group.
\n\n\n\nHer first Meetup experience was not love at first sight. She felt the topics were for advanced users, and the timing late in the evening made it difficult to attend.
\n\n\n\nBut a few months later, the Meetup addressed a topic that could help her resolve an issue in one of her current projects. She made the effort to show up and came away with a number of important tips. The speaker had taken the time to speak to individual attendees. When he came to Meher, she took the opportunity to ask a couple of questions about her project issues.
\n\n\n\nThereafter she went to more Meetups and got to know the people behind this group, just as they started talking about WordCamp Mumbai 2016.
\n\n\n\nA WordCamp adventure
\n\n\n\n![\"Meher](\"https://i1.wp.com/wordpress.org/news/files/2022/04/wcm16.jpg?resize=600%2C800&ssl=1\")
Meher expressed interest in being a part of the coming WordCamp Mumbai and started in an entry-level role with basic responsibilities.
\n\n\n\nAt first, she thought WordCamp was a formal conference with about 100 people. So on the first day of WordCamp Mumbai 2016, she was surprised to see so many WordCamp enthusiasts attending and enjoying such a relaxed and friendly conference.
\n\n\n\nAfter that great experience, Meher went to many more meetups and did more volunteering. She started taking on responsibilities in the coming WordCamps and getting to know the different aspects of the camp.
\n\n\n\nIn the following years, at each WordPress, she took up a new role like speaker vetting, sponsors, and volunteer coordination. This allowed her to know more about what an organizer needs to do, from planning to execution, to make WordCamp a successful event.
\n\n\n\n![\"WordCamp](\"https://i2.wp.com/wordpress.org/news/files/2022/04/wcmumbai-17.jpg?resize=900%2C600&ssl=1\")
Meher is grateful for her WordPress journey which was fostered in the Mumbai community. It has been filled with beautiful surprises.
\n\n\n\nWhen people ask why she’s chosen to specialize professionally in WordPress, Meher says WordPress is easy to teach a non-technical person, yet it is still highly customizable. Being a WordPress developer has given her the opportunity to work remotely for global web development companies that let her think out of the box. And she learns new skills with every release.
\n\n\n\nThe community makes WordPress special
\n\n\n\nMeher says that some of her most memorable WordPress moments have revolved around special friendships, trying new things, and participating in community building.
\n\n\n\nWordPress has let her explore different parts of India, make new friends locally and internationally, and encourage women to be a part of meetup groups and events across India.
\n\n\n\nOne of Meher’s biggest dreams was to lead WordCamp Mumbai as a lead organizer and show others what could be achieved by working together in open source. In 2019, she did just that and has volunteered at international WordCamps and meetups since.
\n\n\n\n![\"Meher](\"https://i0.wp.com/wordpress.org/news/files/2022/04/wc-19.jpg?resize=1024%2C515&ssl=1\")
As part of her enthusiasm for sharing the opportunities WordPress can give people, especially women, she has given time to co-organize two global WordPress Translation month long events and contributor events in India.
\n\n\n\nMeher said: “I was first introduced to translation at one of the meetups which was organised to support the WordPress Translation Day. I realized this was another way to support my local communities and bring the power of WordPress to them by contributing in Gujarati and Hindi. I did not imagine I would a few years later be a global organizer for the event itself!”
\n\n\n\nWith her commitment to ongoing learning as a developer and to model what she believes about the value and community growth opportunities of open source, Meher has given time and energy to the Marketing Team, where she has been a Team Rep, to the Training Team, and to the Core Team contributing to multiple releases.
\n\n\n\nThe developer adventure with WordPress is unlimited
\n\n\n\n\n\n\n\nAt the start of my software developer journey, I always thought the C++ and Java were the only skills you required to excel in your career. From the time I started exploring WordPress in depth, I realized the potential and the power of WordPress in web development.
Meher Bala
Being a part of the WordPress community, Meher learned that there is so much more than just building blogs on WordPress. She started exploring different features of WordPress, created her first theme, and eventually specialized as a frontend specialist.
\n\n\n\nMeher now works as a consultant and front end developer with an international agency specializing in WordPress. Asked what she thought was the best thing about being a WordPress developer, Meher replied: “Through WordPress, I have an opportunity to build unique out of the box websites and work remotely for global web development companies that encourages you to think out of the box. There is always opportunity to continuously advance my coding skills and learn new techniques with every release.”
\n\n\n\nShe believes that there is no limit to where using the software can take you and what you can combine it with to find solutions to projects big and small.
\n\n\n\nIf you earn a living from WordPress, her advice is from the heart: try to give back to the WordPress community.
\n\n\n\n“I am sure you will learn or teach something new and definitely make friends across the world. There is no shame in making mistakes, as you can learn from them and develop your skills further. You can also help others as they build their skills.”
\n\n\n\nMeher added: “Don’t let the things you find difficult get in the way of your success.”
\n\n\n\nShare the stories
\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nContributors
\n\n\n\nThanks to Abha Thakor (@webcommsat), Larissa Murillo (@lmurillom), Mary Baum (@marybaum), Chloé Bringmann (@cbringmann), and Meg Phillips (@megphillips91) for interviews, writing and image work on this story. Thank you to Meher Bala (@meher) for sharing her experiences and to Josepha Haden Chomphosy (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support of the series.
\n\n\n\n![\"HeroPress](\"https://i1.wp.com/wordpress.org/news/files/2020/03/heropress_logo_180.png?resize=180%2C135&ssl=1\"){kind=logo}
This People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress
\nWordPress 6.0 Beta 3 is now available for testing!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress production or mission-critical websites. Instead, it is recommended that you test Beta 3 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 Beta 3 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: Use WP-CLI to test: wp core update --version=6.0-beta3.
Do not use this option if your filesystem is case-insensitive.
The current target for the final 6.0 release is May 24, 2022, which is in less than a month!
\n\n\n\nAdditional information on the full 6.0 release cycle is available here.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.
\n\n\n\nSee What’s in Beta 3
\n\n\n\nSince Beta 2, various items have been addressed, including (but not limited to):
\n\n\n\n- Twenty Twenty-Two: Implement alternate json files #55433
- Fix duotone rendering in site editor #37727
- Create Comments Title block with simple styling #40419
- Navigation block: After choosing an option from Select Menu, focus after block render #40390
- Add comment id to all comments inside comments query loop #40268
- Add post-comments-form block to comments template #40256
- Elements: Add styles to the footer before the block is rendered #37728
- Add default comment status to discussion settings #55567
- Fix styles for nested elements (link color) #55567
- Move
wp_enqueue_block_style()towp-includes/script-loader.php, for better consistency #55182, #55148 - Move administration related hooks to admin-filters.php #54795
Update on the Webfonts API and Style Variations in Twenty Twenty-Two
\n\n\n\nA prior announcement for WordPress 6.0 Beta 1 included a reference to “Webfonts API: Manage local fonts with PHP or theme.json”, as a feature that would be included in the release. WordPress 6.0 Beta 3 will allow theme authors to use webfonts in theme.json, with a public API for plugins to register and enqueue webfonts available in a future version for WordPress. Beta 3 will also include three new style variations to the Twenty Twenty-Two default theme.
\n\n\n\nHow to Help
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\n\n\n\n\n
Thank you to the following contributors for collaborating on this post: @dansoschin @webcommsat, @audrasjb
\n\n\n\n\n\n\n\n
And now another WordPress haiku:
\n\n\n\nRelease day is near
6.0 abounds with joy
New features soon here
WordPress 6.0 Beta 2 is now available for testing!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you test Beta 2 on a test server and site.
\n\n\n\nYou can test the WordPress 6.0 Beta 2 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: Use WP-CLI to test: wp core update --version=6.0-beta2
Do not use this option if your filesystem is case-insensitive.
The current target for the final release is May 24, 2022, which is about five weeks away.
\n\n\n\nAdditional information on the full 6.0 release cycle is available.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks, which will detail all upcoming changes.
\n\n\n\nWhat’s New In Beta 2
\n\n\n\nAs a reminder, contributors have fixed 209 tickets in WordPress 6.0, including 110 new features and enhancements. Each beta cycle focuses on bug fixes, and more are on the way with your help through testing. Here are a few of the changes you will find in Beta 2 specifically:
\n\n\n\n- Block Editor: Prevent styles from being added to the site editor (#55567)
- Patterns REST API: Add ‘inserter’ to the schema (#55567)
- Don’t load remote patterns twice in WP_REST_Block_Patterns_Controller::get_items (#55567)
- Add the ability to filter the whole notification email in retrieve_password (#54690)
- Avoid translating empty plugin headers (#54586)
Note on Webfonts API
\n\n\n\nLast week’s announcement for WordPress 6.0 Beta 1 includes a reference to “Webfonts API: Manage local fonts with PHP or theme.json,” as a feature that would be included in the release. This specific functionality was not included in Beta 2 but may be available at RC.
\n\n\n\nHow to Help
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\n\n\n\n\n
Thank you to the following contributors for collaborating on this post: @dansoschin, @annezazu, @costdev, @priethor
\n\n\n\n\n\n\n\n
And now a WordPress Haiku:
\n\n\n\nWe code fervently
\n\n\n\nA breathless pause for the test
\n\n\n\nKey tapping resumes
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12666\";s: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:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"WP Briefing: Episode 29: How to Make a WordPress Blog\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wordpress.org/news/2022/04/episode-29-how-to-make-a-wordpress-blog/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 Apr 2022 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=12658\";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:150:\"Join our host Josepha Haden Chomphosy as she takes us back to WordPress basics. Learn everything you need to know about how to make a WordPress blog! \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/04/WP-Briefing-029.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Santana Inniss\";s: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:16764:\"\nIn the twenty-ninth episode of the WordPress Briefing, Executive Director Josepha Haden Chomphosy reminds us of our WordPress roots — blogging — and discusses the basics of starting your first blog on WordPress.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Santana Inniss
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- Getting Started with WordPress: Get Setup
- 6.0 Product Walkthrough
- How to Make a WordPress Blog Social Learning Space Event
- Upcoming WordPress Events
- WordPress Meetup Groups
Transcript
\n\n\n\n\n\n\n\nJosepha Haden Chomphosy [00:00:00]
\n\n\n\nHello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy.
\n\n\n\nHere we go.
\n\n\n\nJosepha Haden Chomphosy [00:00:39]
\n\n\n\nAll right. So you’ve been listening to this podcast for a while. You may be one of these contributors I keep mentioning; you may be an agency owner or freelancer. Maybe you’ve wondered how to make a WordPress blog for your big idea. Or, maybe you’re one of the many people who use WordPress for their project or business. Before WordPress was known as a content management system, as a way to get sites online fast, it was a blogging tool.
\n\n\n\nWe have long since outgrown that, but even 19 years into our journey, blogging is still a key part of what WordPress enables you to do. That’s because even after those 19 years, the mission of WordPress is still the same. And that is to democratize publishing, to help people have a place online where they can tell their stories or share their projects or set up their businesses.
\n\n\n\nIf you’ve ever tried to set up a blog, you know that there isn’t a lot of information about what to know before you get going at all. So I’m going to talk about that a little bit today. And just by the way, if you heard the word blog right now and thought, oh, Josepha, how old fashioned? I think it’s important to remember that there’s a business advantage to having well-written, relevant content on your website.
\n\n\n\nJosepha Haden Chomphosy [00:01:59]
\n\n\n\nAnd if you’re not blogging for business, because not all of us are, then the benefits are a little different but still important to my mind. Things like the cathartic benefits of journaling, a chance to build community, and the general importance of preserving wisdom for the ages. Anyway, back to the topic at hand. Before we can get to any of the fancy things that WordPress can do nowadays, it’s important to know a few things as you get ready to set up your first ever website.
\n\n\n\nSo let’s dive in. Here is how you need to get yourself started. First, have an idea and a plan. So have an idea for what you’re doing, the concept of your content, who you want to reach, and some concept of a domain name. I would encourage you to not necessarily get your heart set on a domain name at first. Cause, like, if you want the domain name, wordpress.org, like we own that, you can have that! But if you know that you want a domain like WordPressbloggingforthefuture.com, like that one might be more available. And if you know the kind of words you want in your domain, you can be a bit flexible about what is there.
\n\n\n\nJosepha Haden Chomphosy [00:03:09]
\n\n\n\nThe second thing that you need to do is that if you are just getting started, ask yourself the question, what sort of host do I want? We kind of mentioned all along the WordPress process that, like, you need a good host, but it’s not always clear where that decision has to happen. It happens right here at the start, before you even know what WordPress is most of the time.
\n\n\n\nSo, the earliest question that you have to answer for yourself is what sort of host do I want? Where do I want my site to live? So ask yourself how much you want to get into the maintenance and configuration of your website and the hardware that it lives on versus creating content or keeping your shop up to date.
\n\n\n\nThere’s this whole spectrum of hosting options, and they range from full service where they will keep your WordPress software up to date, provide daily backups, and have customer support if something goes really wrong. So it ranges all the way from full service like that all the way down to essentially zero services, just kind of hands-off.
\n\n\n\nJosepha Haden Chomphosy [00:04:11]
\n\n\n\nThey give you a space to keep your WordPress software, to keep your WordPress site. But they leave everything else up to you. They leave the backups up to you. They leave updating up to you, things like. So that’s the first thing you have to ask yourself. And the first question you have to be able to answer. Most of the time, you will want to start with one of the full-service options. That way, you know that your software is set up correctly and safely from the start. And as you learn more about the software and what you want and what you need, and you have the ability to learn in the time that you have, the more that you can add on either service with the existing hosts that you chose or moving to a different host; however that works out for you.
\n\n\n\nSo if that one sounds like the right option, then you choose a host, go to their site, and actually most of them will have a way to walk you through how to set up a WordPress site inside their system. Most of the time, it’s just one click and then they ask you some questions to get some configurations right.
\n\n\n\nJosepha Haden Chomphosy [00:05:10]
\n\n\n\nThe other option that on the like zero, zero service side, that’s not quite fair, but you know, the other side of that spectrum that probably will be appealing to you if you are already familiar with code or already know how to manage a server or, or you know how to work in this thing called c-panel, et cetera.
\n\n\n\nSo if you already have a lot of information on how all of that works, you can, if you want to, head over to wordpress.org/download, and you can download a zip file of the WordPress software and set that up in your own environment.
\n\n\n\nOkay, quick check here. If this all sounds roughly doable to you, or at least it feels like we’re in the right starting point, but you find yourself thinking, gosh, I just wish she would slow down a little.
\n\n\n\nI’ve got you covered. In the show notes, you’ll find a link to one of the Learn WP courses for getting started with WordPress. There’s a section on choosing a host as well as various other early steps of this process. So if you felt like I blazed through all of that, which honestly I kind of did, you can work through those lessons in that course, at your own pace, and it’s, and it’s really a very good guide.
\n\n\n\nJosepha Haden Chomphosy [00:06:24]
\n\n\n\nAll right. Let’s pretend we did all of that. Now you’ve got yourself a website. The thing that you will want to do next, or rather the first thing that you’ll notice once you get your site up and running, is that there’s this ‘Hello World’ post– there’s a post that already exists in there. The Hello World post is a placeholder for the common features of a blog post.
\n\n\n\nThere, you can find your featured image, your title, your content, and even some fake comments. You can either edit this post so that you can see how your writing will look from the start, and you can kind of compare like, okay, the Hello World part over here on this page, exists in this field over here on this page. So you can kind of see where everything works, how it all looks together. Or, if you’re more familiar with WordPress or CMS in general, you can simply remove that and start fresh.
\n\n\n\nJosepha Haden Chomphosy [00:07:17]
\n\n\n\nSo we’ve got now a website, we know, kind of, how to look at our posts and create posts, where comments are, where they can kind of be moderated and stuff. And so, the most fun task for everyone is choosing a theme. But if it’s not a fun task, if it doesn’t sound like a fun task to you, I can help you kind of do some, choose your own adventure guiding questions here.
\n\n\n\nFirstly, you can ask yourself how you want the site to look. Do you want it to mostly be a lot of photos or entirely words, mostly animations? You can head to the theme directory and search for a theme with most of the features that you want. There’s like a filtering system where you can put in, like, you want three columns so that you can have three columns of text if you want it to look kind of like an old school newspaper kind of layout and things like.
\n\n\n\nJosepha Haden Chomphosy [00:08:12]
\n\n\n\nThere’s also a way to look for themes inside your instance, your WordPress site, but like, if you haven’t set that up yet, but you do still want to see kind of what your theme options are, you can go to wordpress.org/themes and and take a look at what’s out there. Just as a quick side note, if you get to that theme directory, if you get to wordpress.org/themes, and it feels overwhelming, which I can understand, I recommend starting with a theme that is designed for blogging specifically so that you can see how things look right away.
\n\n\n\nAnd there’s actually a theme that does come with every WordPress site. So if you’re not ready, you can skip this thing entirely and just work with the theme that’s already there. Every word, press instance ships with a theme and it is fully functional when you, when you get your site up and running. So you don’t need to choose a theme right now if you don’t feel ready.
\n\n\n\nAnd then the other very fun thing that people do with their WordPress sites is to add plugins to them. So plugins are these little pieces of software that you add on to the WordPress software that lets it do additional things. It adds additional functionality. The questions that you can ask to kind of guide yourself through what sorts of plugins you might want, what sorts of functionality you might want to add to your site are a little similar to the ones that you want to ask for figuring out which theme.
\n\n\n\nJosepha Haden Chomphosy [00:09:36]
\n\n\n\nSo figure out if there are tasks that you need visitors to do. Do you need them to contact you? Do you want them to watch a video? Should they review and respond to questions?
\n\n\n\nIf you have a concept of the things that you want users to do on your website, then you can head to the plugin directory and search for a plugin with features that you need. Also, there are just endless lists of recommended plugins out there; if that is something that you find valuable as part of your research, those are also easy to find.
\n\n\n\nAnd as a general side note here, there are even more plugins than there are themes. So if you have gotten to this point and feel like you don’t quite know the answers to the questions that I shared, and, and it’s going to be a while until you feel like you can know what those answers are. That’s totally fine.
\n\n\n\nI’ll tell you this. I have never seen a site without a contact form. So feel free to begin your journey there. There are a lot of great plugins for contact forms and it can kind of help you figure out how to work with plugins in that way. So yeah, I made it sound like you can get a WordPress website built in like seven minutes and on the one hand you definitely can.
\n\n\n\nJosepha Haden Chomphosy [00:09:36]
\n\n\n\nAnd on the other hand, it’s still a little bit more complicated. So here I have a final note for everyone. You will hear around the WordPress ecosystem. And obviously, here, are some things that could make you feel a little nervous about doing this for the first time. Things like the five-second installation, which WordPress has been famous for years.
\n\n\n\nBut also about how easy and simple it all is. And as somebody who was once in the position of learning WordPress for the first time, like I first encountered a WordPress site in 2009 and I started learning how to use WordPress in 2010. So I can say with confidence that once you learn it, it’s easy.
\n\n\n\nWe are the easiest of the hard options for CMS. Like content management systems are just complicated, but we are the easiest one out there. And so, as you’re learning, I want to just remind you to celebrate your small wins along the way. If you feel like you’re late to this blogging game, like you should have had a website for years. I mean, sure that could be true. And yes, the best time to plant a tree was 20 years ago. But the second-best time to plant that tree is today.
\n\n\n\nWordPress didn’t start out powering over 40% of the web, and your first site can’t be immediately measured in the millions of readers. So, what will your small beginning lead you to?
\n\n\n\nJosepha Haden Chomphosy [00:12:25]
\n\n\n\nAnd now that brings us to our small list of big things.
\n\n\n\nThe first one, the next release of WordPress, WordPress 6.0, has reached its beta phase. That means the full focus is on finding and fixing the bugs we accidentally created during this development cycle. Beta two comes out tomorrow and you can follow along in the core channel in the Making WordPress Slack.
\n\n\n\nIf you’ve never seen how those releases get packaged, and if you just want to keep an eye on what everybody’s doing so that you can be the first to know, yeah, Making WordPress Slack is the way to go.
\n\n\n\nThe second thing on our small list is that speaking of WordPress 6.0, we had the public walk through a couple of weeks ago, which means that in a few weeks, I’ll do a WordPress 6.0 sneak peek. I’ll share some highlights of the release features and why I think they are super important for you to take a look. Sooner rather than later.
\n\n\n\nJosepha Haden Chomphosy [00:13:22]
\n\n\n\nAnd then the final, big thing, if you are new to WordPress and this episode has you all fired up to start your blog, we have a bunch of contributors over on the Learn WP team that have just the thing for you.
\n\n\n\nYou can join the online social learning space called How to Make a WordPress Blog. It’s a free online event that will help you get started. I’ll link the information in the show notes below. And I’ll also share in the show notes, a list of WordPress Meetup groups, where you can find more opportunities to learn and get support from other people locally who are also doing things with WordPress.
\n\n\n\nBut you can also find a list in the dashboard of your newly installed WordPress blog you no doubt have after this podcast.
\n\n\n\nAnd that my friends is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12658\";s: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: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 6.0 Beta 1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2022/04/wordpress-6-0-beta-1/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Apr 2022 19:08:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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:\"6.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12644\";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:63:\"WordPress 6.0 Beta 1 is now available for download and testing.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s: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:7809:\"\nWordPress 6.0 Beta 1 is now available for download and testing.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you test Beta 1 on a test server and site.
\n\n\n\nYou can test the WordPress 6.0 Beta 1 in three ways:
\n\n\n\n- Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
- Option 2: Direct download the beta version here (zip).
- Option 3: Use WP-CLI to test:
wp core update --version=6.0-beta1.
Do not use this option if your filesystem is case-insensitive.
The current target for the final release is May 24, 2022, which is about six weeks away.
\n\n\n\nAdditional information on the full 6.0 release cycle is available.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.
\n\n\n\nKeep WordPress Bug Free – Help with Testing
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute. If you have never tested a beta release before, this detailed guide will walk you through how to get started.
\n\n\n\nTesting helps make sure that this and future releases of WordPress are as stable and issue-free as possible. And anyone can do it – especially great WordPress community members just like you.
\n\n\n\nWant to know more about testing releases like this one? Read about the testing initiatives that happen in Make Core. You can also join a publicly-accessible channel on the Making WordPress Slack workspace.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\nTo review features in the Gutenberg releases since WordPress 5.9 (the most recent major release of WordPress), access the What’s New In Gutenberg posts for 13.0 (release pending), 12.9, 12.8, 12.7, 12.6, 12.5, 12.4, 12.3, 12.2, 12.1, and 12.0.
\n\n\n\nBeyond the noted changes, which include more than 400 updates and 500 bug fixes for the editor, contributors have fixed 189 tickets for the WordPress 6.0 core, including 91 new features and enhancements. More fixes are on the way.
\n\n\n\nSome Highlights
\n\n\n\nWant to know what’s new in version 6.0? Read on for some highlights.
\n\n\n\nThe WordPress 6.0 release will be packed with all kinds of improvements. Here are just a few:
\n\n\n\n- Style Switching: switch up the look and feel of your site, all in one block theme. No need to change themes!
- More template options: use blocks to edit five more templates (author, date, categories, tag, and taxonomy).
- Multi-select: Easily select text across multiple blocks. Edit to your liking.
- Retain Styles: Keep your custom styles in place, whether transforming between blocks or creating new buttons.
- More patterns in more places: the Quick Inserter surfaces patterns that might work well for the condition you’re in, baking in relevant patterns for template parts and pages you’re working on.
- List View improvements: New keyboard shortcuts (shift + click) let you select multiple blocks to modify in bulk (reposition, delete, etc.), see your content at a glance with a collapsed by default view, and more.
- Refined design tools: Explore a new color panel, transparency options, more group block variations to create new layout options (Stack, Row), the ability to set your featured image in a Cover block, control the exact size of your featured image, gap support for the Gallery block, and more.
- New blocks: Comments, Read More, No results in Query Loop, Post Author biography, Avatar blocks.
- Block Locking UI: Choose to disable the option to remove a block, move it, or both, right in the editor.
- Export block themes: Explore the improved block theme export tool, as WordPress heads closer to codeless visual block theme building.
- Webfonts API: Manage local fonts with PHP or theme.json.
\n\n\n\n
Thank you to the following contributors for collaborating on this post: @annezazu, @chanthaboune, @marybaum, @priethor, and @webcommsat.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12644\";s: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: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:35:\"WordPress 5.9.3 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2022/04/wordpress-5-9-3-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Apr 2022 19:50:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s: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.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12575\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"WordPress 5.9.3 is now available! This maintenance release features 9 bug fixes in Core and 9 bug fixes in the block editor.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"Jb Audras\";s: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:3896:\"\nWordPress 5.9.3 is now available!
\n\n\n\nThis maintenance release features 9 bug fixes in Core and 10 bug fixes in the block editor.
\n\n\n\nWordPress 5.9.3 is a short-cycle maintenance release. The next major release will be version 6.0.
\n\n\n\nYou can download WordPress 5.9.3 from WordPress.org, or visit your Dashboard → Updates and click “Update Now”.
\n\n\n\nIf you have sites that support automatic background updates, they’ve already started the update process.
\n\n\n\nFor more information, browse the full list of both Trac and GitHub changes in the release candidate post, or check out the changelog of version 5.9.3 on HelpHub.
\n\n\n\nThanks and props!
\n\n\n\nThe 5.9.3 release was led by Jb Audras and George Mamadashvili.
\n\n\n\nSpecial props to Sergey Biryukov for running mission control.
\n\n\n\nThank you to everyone who helped make WordPress 5.9.3 happen:
\n\n\n\nAki Hamano, Alex Stine, aliakseyenkaihar, Anton Vlasenko, binarymoon, Carlos Bravo, Colin Stewart, David Baumwald, Dion Hulse, George Mamadashvili, glendaviesnz, Greg Ziółkowski, ironprogrammer, Iulia Cazan, Jb Audras, Joe Dolson, Joen A., Jorge Costa, jsnajdr, Marius L. J., Nick Diego, Paul Biron, Peter Smits, pgpagely, Rafi Ahmed, Richard B. Kreckel, Robert Anderson, Rufus87, Sergey Biryukov, Tor-Bjorn Fjellner, Tonya Mork, Abha Thakor, Oliver Juhas, and Weston Ruter.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12575\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"The Month in WordPress – March 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2022/04/the-month-in-wordpress-march-2022/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Apr 2022 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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:22:\"the month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12583\";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:325:\"We hope that you and your beloved ones are staying safe during these difficult times. If you’re looking for a way to support the humanitarian crisis in Ukraine, you can refer to this episode of WP Briefing. There you will find a list of Non-Governmental Organizations (NGOs) that can help. In parallel to the work […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"rmartinezduque\";s: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:13171:\"\nWe hope that you and your beloved ones are staying safe during these difficult times. If you’re looking for a way to support the humanitarian crisis in Ukraine, you can refer to this episode of WP Briefing. There you will find a list of Non-Governmental Organizations (NGOs) that can help.
\n\n\n\nIn parallel to the work the community is doing in preparation for the next major release, WordPress 6.0, March has seen the launch of some exciting projects and proposals. Read on to find out more about the latest updates and how to get involved.
\n\n\n\n\n\n\n\n
The Pattern Directory is open for public submissions
\n\n\n\n![\"View](\"https://i2.wp.com/wordpress.org/news/files/2022/04/home-patterns.png?ssl=1\")
The WordPress Pattern Creator is live! This new tool allows anyone with a WordPress.org user account to build, edit and submit their best block patterns to the Pattern Directory.
If you’ve used patterns in WordPress, you’ll know that they make it easy to add unique layouts to your website. These include galleries, testimonials, pricing tables, and more. Opening the directory to public submissions enables any WordPress user to enjoy a wider variety of patterns to use on their sites.
WordPress 6.0 Walkthrough scheduled for April 5, 2022
\n\n\n\nA few updates to the WordPress 6.0 planning were published last month. In case you missed them, today (April 5) at 15:00 UTC there is a live and interactive WordPress 6.0 walkthrough hosted by contributors of the release squad.
\n\n\n\nThe event will take place via Zoom and include a discussion on the new features, potential blockers, and a Q&A session with the community. Attendance is open to anyone who wants to know more about what’s coming in WordPress 6.0.
\n\n\n\nGutenberg releases: Versions 12.8 and 12.9 are here
\n\n\n\nVersions 12.8 and 12.9 of the Gutenberg plugin were released last month. With them, some new exciting features and updates.
\n\n\n\n- Gutenberg 12.8 includes a new Webfonts API, iterative UX enhancements, and bug fixes to increase the editor’s stability.
- Gutenberg 12.9 introduces the new block locking UI and support for spacing between Gallery images. Also, many other improvements to give you more control over what is editable and presented to users.
Team updates: Team Reps for the Photo Directory team, community proposals, and more
\n\n\n\n- WordPress 5.9.2 is available for download. This security and maintenance release features one bug fix and three security fixes.
- The Team Representatives for the Make Photo Directory team for 2022 have been announced. Congrats to Marcus Burnette (@mdburnette), Katie Richards (@katiejrichards), and Topher DeRosia (@topher1kenobe)!
- The Community team considered revisiting the existing guidelines for in-person regional WordCamps. Conclusions and next steps will be shared soon.
- On a similar note, Cate DeRosia (@mysweetcate) is looking for ideas on how to support organizers who are trying to restart in-person events in their communities. Share yours by April 13, 2022.
- The Training team published new lesson plans, workshops, and social learning spaces on Learn WordPress. Check out what’s new in March 2022.
- How has WordPress helped grow your story? The Make Marketing team wants to hear about your experience!
- The Performance Lab plugin, a set of modules that aim to improve performance in WordPress, was released last month.
- Openverse released new updates in March. They include a redesigned content reporting flow and new image detail pages.
- WordPress Executive Director Josepha Haden Chomphosy posted a public statement on the removal of the Zamir plugin a few weeks ago.
- The March 2022 editions of the Meetup Organizer Newsletter and the Polyglots Monthly Newsletter were published.
- The latest edition of People of WordPress features the contributor story of the Argentinian web developer and product manager Juanfra Aldasoro.
- WordPress community members launched the Museum of Block Art (MOBA). This initiative seeks to inspire creativity and push the limits around what can be done with WordPress. All the art curated in this virtual museum is built using the block editor.
Testing requests: WebP feature, template for author pages
\n\n\n\n- The Performance Team published a proposal to integrate the WebP image format by default into WordPress core. Your feedback on this feature is appreciated.
- Version 19.6 of WordPress for iOS is available for testing.
The first flagship WordCamp Asia is looking for organizers
\n\n\n\n- WordCamp Asia is tentatively scheduled for February 2023. After two years since the organizing team announced that the first flagship WordCamp Asia was canceled due to the pandemic, they are back together and looking for more members to join them in planning the event.
- The Call for Speakers for WordCamp US 2022 is now open. You can submit your application by April 17, 2022.
- Three in-person WordCamps are happening this month:
![\"??\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f1e8-1f1ed.png\")
WordCamp Genève, Switzerland on April 9, 2022![\"??\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f1ec-1f1f7.png\")
WordCamp Athens, Greece on April 9-10, 2022![\"??\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f1e6-1f1f9.png\")
WordCamp Vienna, Austria on April 23-24, 2022
- Check out the latest episodes of WordPress Briefing with Josepha Haden:
\n\n\n\n
Have a story that we could include in the next ‘Month in WordPress’ post? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this Month in WordPress: @rmartinezduque, @mysweetcate, @anjanavasan.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12583\";s: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:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"WP Briefing: Episode 28: Coming to a WordCamp Near You: A Return to In-Person WP 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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wordpress.org/news/2022/04/episode-28-coming-to-a-wordcamp-near-you-a-return-to-in-person-wp-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 04 Apr 2022 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=12506\";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:172:\"Curious about returning to WordPress events safely? Tune in as WordPress Executive Director Josepha Haden Chomphosy discusses guidelines for returning to in-person events. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/03/WP-Briefing-028.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Santana Inniss\";s: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:11997:\"\nIn the twenty-eighth episode of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy discusses returning to in-person WordPress events.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann & Santana Inniss
- Song: Fearless First by Kevin MacLeod
- Special thanks to: Angela Jin
References
\n\n\n\n- Event Safety Checklist
- WordCamp Asia Call for Organizers
- Open Discussion: Returning to In-Person Events
- Open Discussion: Returning to Regional Events
Transcript
\n\n\n\n\n\n\n\nJosepha Haden Chomphosy [00:00:00]
\n\n\n\nHello everyone! And welcome to the WordPress Briefing: the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\nJosepha Haden Chomphosy [00:00:40]
\n\n\n\nI was checking the list of upcoming events recently as part of just my regular work and saw that the call for organizers for WordCamp Asia is open. On the one hand, it made my heart skip a beat with excitement. That event is six years or so in the making. And on the other hand, it reminded me of February 10th, 2020, the day that Matt told me that we had to proactively cancel WordCamp Asia. That week was truly heartbreaking for me as well as I think the entire organizing team.
\n\n\n\nBut it also, fortunately, was prescient. As I think back over the two years since then, I’m grateful for our community wranglers and deputies who have consistently hosted important discussions about how to return to in-person events safely. And with two of our major flagship events returning this year, I’m here to summarize, sort of, what the rules and guidelines are.
\n\n\n\nBut certainly I hope that you come away from this with an idea of what’s being done to keep everyone safe as we are best able.
\n\n\n\nJosepha Haden Chomphosy [00:01:44]
\n\n\n\nFirstly, before we dig into specifics, I want to be clear upfront that the guidelines for COVID-aware events are mandatory, unless otherwise stated. For folks who’ve been attending WordPress events, or participating in the community for a long time, this is a change. As a program, we have always done our best to be flexible with guidelines so that we can prioritize local knowledge. But our responsibility is to the long-term success of this community and this program. So moving forward with in-person events that risk the health of our community members poses risks to the program itself. So with that in mind, let’s learn what we’re going to see at events for the rest of the.
\n\n\n\nJosepha Haden Chomphosy [00:02:28]
\n\n\n\nFor any WordPress event that is gathering more than 50 people, the new mandatory guidelines are:
\n\n\n\nNumber one, follow local laws and guidelines. If your area has suggested guidelines on top of the mandatory ones, follow those.
\n\n\n\nSecond, is if you are in a location where laws or guidelines require or permit venues to limit admission based on a person’s vaccination status and masking, then events can only happen in venues that are willing to provide staff to check for vaccination status at the door. And then also to remind participants to wear masks during the event.
\n\n\n\nAnd the third thing is if your area or venue legally cannot check vaccination status, your area must pass the in-person checklist, which I will link in the show notes below. But that in-person checklist has to be passed at the time of the application and then again at the time of the event. And in addition to that, the venue must be willing to provide staff who will remind participants to wear masks and check for temperature during the event.
\n\n\n\nJosepha Haden Chomphosy [00:03:33]
\n\n\n\nOrganizers in these areas must be prepared to move online or cancel if the region fails the safety checklist, which again, will be linked in the show notes below. So those are the three things and they are pretty dense, but also I think allow for a fair amount of flexibility. There is also a tidy flow chart linked in the sidebar of make.wordpress.org/community that will help you to decide what sort of event your own area can support right now.
\n\n\n\nSo those are the mandatory guidelines for WordPress events in general right now, but you probably also have a few specific questions. So I’ve got the three most common questions ready to go with answers from Angela Jin who helped me to kind of pull together the information for this particular podcast props to Angela. Thank you.
\n\n\n\nJosepha Haden Chomphosy [00:04:25]
\n\n\n\nSo, first question, anything specific to know about WordCamp Europe? WordCamp Europe will be following these guidelines as well. All attendees and participants are expected to wear a mask while they are at the event and catering will be offered outside so people can remove their masks to eat.
\n\n\n\nThe second common question is how will these guidelines change as countries and local governments begin deescalating restrictions and safety measures? We should consider these guidelines to be subject to evolution based on what the team is hearing and seeing from the community. But right now we intend to keep these stricter guidelines in place until we see how the loosened rules play out elsewhere.
\n\n\n\nAnd then a third frequent question is what’s going to happen to all these online events?
\n\n\n\nThe community team will continue to support online events right now. So if your community doesn’t feel ready to have an in-person event, but still wants to kind of get everyone together that is still allowed, and still encouraged. And finally the community team will continue to keep a close eye on situations around the world.
\n\n\n\nIf it becomes safe to do so, and your community is interested, they of course will be happy to chat with you about a WordCamp. There is an application that I will share the link to in the show notes below as well. In case that is something that your community is wanting to look into.
\n\n\n\nJosepha Haden Chomphosy [00:05:54]
\n\n\n\nOh, and I have a little postscript also. I know I was like finally, and now I’m doing a finally, finally. That’s what postscripts are about. P.S. If you have not stopped by the community team’s site or any of their meetings, they’ve been doing a really great job of keeping things moving through two years of unpredictable changes. If you are a community team member, I want to offer you a huge thanks. Thank you so much for helping us to stay aware and able to move forward.
\n\n\n\nIf you are an organizer, pat yourself on the back. I want to thank you for pivoting with us, moving through online events, even though they are not at all the same as in-person events and certainly they don’t share the reasons that we get people together sometimes.
\n\n\n\nAnd finally, if you are an end to end attendee, if you go to WordPress meetups or you go to any sort of WordPress online events or WordCamps, anything like that, thank your local organizer. They have been doing this probably for a while, and I’m sure that they are looking forward to getting back to in-person events themselves, but even, so they have been putting in a lot of volunteer hours to help make sure that we all know how to use WordPress.
\n\n\n\nAnd so find them, thank them, and I’m sure that they’ll appreciate it.
\n\n\n\nJosepha Haden Chomphosy [00:07:20]
\n\n\n\nAnd with that, it is time for our small list of big things. Number one, WordCamp Asia has a call for organizers open! This event will be in 2023. And I think that we all simply cannot wait. So I’ll link the call for organizers in the show notes. And then of course you can follow that whole site to stay up to date on what’s happening there.
\n\n\n\nThe second thing is, while we’re on the topic of events, there’s also an open discussion about how we can best support organizers who are getting back to in-person events. We’d like thoughts from both organizers and attendees. So feel free to drop by and leave a note in the comments section. And while you’re over there, the third thing in my small list of big things, there’s also an open discussion about regional events. So go over there, get all your thoughts about WordPress events together. Get them all sorted out in one go. Just leave comments, boom, boom, boom, boom, boom. All over the place.
\n\n\n\nAnd that my friends is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host Josepha Haden Chomphosy.
\n\n\n\nAnd I’ll see you again in a couple of weeks.
\n\n\n\nJosepha Haden Chomphosy [00:08:54]
\n\n\n\nSo my most embarrassing WordCamp story actually has to do with where I was supposed to be versus where people thought I was supposed to be. This was early on in my time with WordPress, with Automattic. And I had convinced someone, I had convinced a colleague and friend of mine to go to my home WordCamp, WordCamp Fayetteville over there in Arkansas.
\n\n\n\nAnd then I didn’t go. But I knew I wasn’t going, I knew I was going to WordCamp Boston, but he did not know that I was not going to go. And so he arrived at WordCamp Fayetteville, WordCamp Northwest Arkansas. I can’t remember what it was called at the time. And immediately was confused about where I was and why I wasn’t there.
\n\n\n\nAnd so there was this excellent moment of mass confusion among states where the folks at WordCamp Fayetteville started tweeting about how I had convinced this contributor to go to that event and then didn’t show up. And then the folks at WordCamp Boston, we’re looking at all of those tweets, because if you are a WordCamp organizer, you are always looking at the tweets from all the other WordCamps happening in your weekend.
\n\n\n\nAnd people got very confused about why I was in Boston while they were thinking that I was in Fayetteville, even though the tweets were talking about how, like, I wasn’t in Fayetteville. They probably didn’t say that it was probably more along the lines of like, “Hey, let’s share a photo with Josepha” to, like, make fun of the fact that I wasn’t there.
\n\n\n\nAnd so I caused mass confusion in multiple states. That’s probably my most embarrassing WordCamp story. You’re welcome. Bye!
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12506\";s: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:75:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"People of WordPress: Juan Aldasoro\";s:7:\"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/2022/03/people-of-wordpress-juanfra-aldasoro/\";s: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 Mar 2022 21:42:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:7:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:9:\"HeroPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:20:\"Polyglot Contributor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:6;a:5:{s:4:\"data\";s:12:\"Support Team\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12512\";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:120:\"The People of WordPress feature this month shares the story of web and plugin developer Juanfra Aldasoro from Argentina.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"webcommsat AbhaNonStopNewsUK\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:19968:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a website developer and product manager from Argentina, who found in the software a way to live his life in the way he dreamed.
\n\n\n\n![\"Juan](\"https://i2.wp.com/wordpress.org/news/files/2022/03/Juanfra_2333.jpg?resize=1024%2C768&ssl=1\")
WordPress offers something to everyone. For Juan Aldasoro, a developer and product manager for a large distributed company, it provides an opportunity to combine his different interests and skills to live the type of life he wanted.
\n\n\n\n“I like visual, creative and technical things. The joy of WordPress is that you can do all of these things, you don’t have to limit yourself to any one aspect . You can also do this from almost anywhere in the world!”
\n\n\n\nFrom working in products since 2012, Juan sees WordPress as a major part of his skillset and toolbox. He said: “It gives you an opportunity to be part of building a product which could potentially be used by thousands of people and more on your site. It encourages you to think about different languages and how you can make it accessible. It allows you to work on different platforms. Working in WordPress gives you this broad approach. Working this way on products ended up pushing me into learning about all these different things. Only in open source can you really do this and use your creative side to find solutions.”
\n\n\n\nLearning about being part of a community
\n\n\n\n![\"Juan](\"https://i0.wp.com/wordpress.org/news/files/2022/03/Juanfra_2813.jpeg?resize=1024%2C924&ssl=1\")
Born in a mid-sized city in Argentina, Juan was raised in a family in which music, arts and sports were always an essential part of everyday life.
\n\n\n\n“These activities encourage human beings to be creative and participative, and at the same time they are highly formative when it comes to mould people in order to become part of a group, a team, a community.”
\n\n\n\nThe youngest of five siblings, Juan became highly motivated, trying to follow the steps of his siblings. Having a computer at home, he started to make connections that laid the foundation for his career as a developer. His interest in computers grew through that access to a machine running MS-DOS – the one with the black screen command line! Mastering this became a challenge to him and something to share with others. Through doing this, he found a way to more social interaction and new friendships.
\n\n\n\n\n\n\n\nWithout being conscious of it, my friends and I were sharing pieces of code.
He said: “I started learning some super easy stuff that made me feel like Houdini at that time. I could save a game play, something intangible, on a floppy disk and carry that piece of plastic and magnetic material back home. I was saving the play or game in a square object and then loading that back at home. I now realize, those were my first interactions with computer commands. Without being conscious of it, my friends and I were sharing pieces of code in a unique way.”
\n\n\n\nThis interest grew further through computer magazines and experimenting as “there was always something new to learn.” Although sport became a big part of Juan’s life in his teens, he kept up his computer learning. Taking a new direction, he found online tutorials enabling him to learn how to play the guitar. This led to setting up a punk rock band with his friends.
\n\n\n\n“Education has always been important in my family, and thanks to my parent’s efforts, I attended a school where I learned to express myself in another language.” The school had hired a satellite internet connection in the mid-nineties and had HTML on the computer studies program. These facilities were not that common in Argentina or many other countries either at that time. Also, his parents had the foresight to secure a rare internet connection at the house in 1997.
\n\n\n\nJuan recalled: “Browsing around the Internet opened a new universe in my mind. This new universe was extremely fantastic but also extremely expensive. I needed to make the most of every second online.”
“It was a whole new world and one thing led to the other. I started learning a bit of everything, editing graphics, scripting and so on. I still remember my first website in the fantastic sunset strip, Geocities.”
Trying to go pro
\n\n\n\nAfter high school, Juan moved to the city along with his brother and began to study IT at University. When he was asked by a friend to work at a software company, he decided to try that whilst continuing his studies. Through his job he had the chance to explore web-related opportunities, and with a friend from university, they started managing teams and projects across Latin America and Spain.
Juan describes this experience as one of the most fulfilling in his life. He was able to travel abroad for work, experience remote working, manage teams, present projects and speak formally in front of senior people. As the company grew at a fast pace, they learned how to set up and run a large organization. Eventually, he decided to drop out of his university program and focus on the opportunity of learning first hand.
![\"Juan](\"https://i0.wp.com/wordpress.org/news/files/2022/03/juanfra.jpg?resize=600%2C600&ssl=1\")
One of the key early learning from working internationally was that business and web development could be just as fast-moving and successful in Argentina as in other places. “I realized there’s no such thing as a secret sauce for success. Projects are backed by people’s talent and time, and you can find that in any latitude.”
By his mid-20s, Juan decided he wanted to try building something from scratch. He created a social network for photo sharing in Latin America, which was used by more than 30,000 people across Latin America and Spain in its time. Through this, he discovered that other people had a blog and he did not want to be left behind. The discovery of WordPress was to change the focus of his life.
Hello to WordPress
\n\n\n\nSpending some time traveling around Europe, Juan found himself ‘surrounded by uncertainty’ and worried about what the future could bring. “I had some clues, but under uncertainty, the more you ask the less you answer. I started thinking about embracing the following philosophy: I didn’t want to be part of a large company, I didn’t want to continue studying and I wanted to travel as much as I could.” He did not realize at that time how this vision for his life was to mirror what he would find in WordPress.
\n\n\n\nHe started using WordPress for a few sites in 2005. By 2007 he was using it for almost everything. He was struck by the magnitude and range of what the software could do, from a simple tool used to create a blog in the blink of an eye through to complex projects.
\n\n\n\nHis first problem-solving project was simple and saved data received through a contact form plugin. “To complete this project I discovered the Codex and I learned how easy and intuitive it is to create a plugin. I had fallen in love with WordPress.”
\n\n\n\n\n\n\n\nI was truly amazed by how I could learn from others.
As he explored the options with the software, Juan was unsure of how intellectual property worked and wanted to be respectful of other people’s work. “I didn’t understand open source yet, and I wasn’t sure if I was stealing from others. That was my first interaction with GPL and open source. I was truly amazed by how I could learn from others and improve things created by others or by myself.”
\n\n\n\nHe realized: “WordPress was the way to go if I wanted to pursue a dream of traveling, skipping winter, and working at the same time; what we now call a digital nomad. I already knew how to work remotely, I could work for companies located anywhere, as long as they could communicate in English or Spanish.”
\n\n\n\nJuan started his own web agency, where he provided services to small and medium-sized companies abroad in the USA, UK, and Australia. He built his reputation and developed strong relationships in WordPress. “The experience couldn’t be better. I was learning, having fun, making a living out of it, and at the same time exploring the world.”
\n\n\n\nIn mid-2012, he discovered the full power of the WordPress community firsthand. In his spare time he started developing themes and from all he heard, wanted to attend a major event with lots of others in WordPress, a WordCamp. He took the plunge and booked for WordCamp in Edinburgh, in the UK. He said: “I got to meet many super talented people, and the atmosphere of the event was awesome. A place where competitors were also colleagues. Seeing the humility of somebody like Mike Little, the co-founder of WordPress, was amazing.”
\n\n\n\nHe added: “While there, unconsciously, I started dreaming of holding something like that in Argentina – the joy of hosting the WordPress community in my home country.”
\n\n\n\nBack home, while browsing the Codex, he happened to see that WordPress was turning 10. A lot of meetups were going to be organized worldwide to celebrate the birthday. But there was nothing organized in Argentina. This was a catalyst for starting a local meetup. Together with a colleague, he organized an Argentinian 10th birthday meetup.
\n\n\n\nMore than 20 people showed up. “There was a common denominator. We all loved WordPress, it was part of our day-to-day life. We wanted to share experiences, make new friends and continue growing from what we could learn from others. That day we were a group of people with shared interests. That’s the simplest way to define a community, isn’t it?” This early meetup led to the formation of what is now called WordPress Argentina.
\n\n\n\nIn his desire to skip winters and do more traveling, his next adventure was to take him to visit family working in the US and attend one of the biggest WordCamps in the world in San Francisco. His interest kept growing and he traveled across Europe to be part of the first edition of WordCamp Europe in the Netherlands in 2013.
\n\n\n\nHe said: “There’s almost nothing I could write to fully express what you experience in such events. They are the main WordPress events worldwide. The best part: I made a lot of good friends from many different places. I’m glad I have more excuses to continue traveling.”
\n\n\n\nOnce again in Argentina, our organization started growing thanks to the energy of the whole group, we started hosting formal meetups. In May 2015, we crowned all these efforts with a new WordCamp in Buenos Aires, Argentina.
\n\n\n\n![\"Juan](\"https://i0.wp.com/wordpress.org/news/files/2022/03/Juanfra-WCBA15-51.jpg?resize=1024%2C683&ssl=1\")
“Organizing such an event in my home country with many of the contributors I had met from the very first meetup was an experience I will always keep with me.”
\n\n\n\nJuan believes one of his biggest contributions to open source was as part of being able to expand the community in Argentina and to share this with other Latin American and Spanish speaking countries. He also contributes as a volunteer translator in the Polyglots Team, to the Make WordPress Support team, and contributes to code blocks and Gutenberg. “I am really excited about seeing the future of Gutenberg as it is the future of WordPress.”
\n\n\n\nThroughout his time contributing, Juan believes in helping to set the foundations and encouraging others to give their time and talents. He is keen to share that contributing does not have to be the same all the time and that you can have breaks and focus on one area in a particular period too. He gives the example of how in his spare time he watches Trac, where tickets about the software are logged, and looks where he might be able to help or think of solutions.
\n\n\n\nHe said: “Anytime I find I can contribute to or make improvements in code-related areas, I will do as it is important to keep giving to the community. I enjoy crawling over meta, trac, GitHub and the different places that are requesting help. There is always somewhere you can help. At the moment, my focus is code and translations. I always try to save time to help these two areas. It is like you give and you get, you learn things. You meet amazing people and opportunities arrive.”
\n\n\n\nFinding your path in WordPress
\n\n\n\n![\"Juan](\"https://i1.wp.com/wordpress.org/news/files/2022/03/Juanfra_1505.jpeg?resize=768%2C1024&ssl=1\")
“Life is about experiences, it is about the people you surround yourself with and trying to do what you love. What you can find in an open source project like WordPress is an environment full of people who work with a tool they love. An environment that is ready to help and to give advice. Follow what makes you happy, try to be surrounded by people who make you better, try to empower others, try to give back. Try. Make your own path.”
\n\n\n\nShare the stories
\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nContributors to this feature
\n\n\n\nThank you to Juan Aldasoro (@juanfra) for sharing his story.
\n\n\n\nInterviews and feature by Abha Thakor (@webcommsat) and Surendra Thakor (@sthakor). Reviews by Mary Baum (@marybaum), Chloe Bringmann (@cbringmann), Meher Bala (@meher), Anjana Vasan (@anjanavasan) and Yvette Sonneveld (@yvettesonneveld).
\n\n\n\nThanks to Josepha Haden Chomphosy (@chanthaboune) and Topher DeRosia (@topher1kenobe) and others for their support of this initiative.
\n\n\n\nThis People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress
\nIt’s been less than a year since the WordPress Pattern Directory was launched, and we already have more exciting news to share. The Pattern Creator is live! You can now build, edit, and submit your best block patterns to the Pattern Directory—submissions are open to all with a WordPress.org user account!
\n\n\n\n![\"Pattern](\"https://i0.wp.com/wordpress.org/news/files/2022/03/patterns.png?resize=2800%2C3000&ssl=1\")
![\"View](\"https://i0.wp.com/wordpress.org/news/files/2022/03/community-pattern-3-1-1.png?resize=2800%2C2841&ssl=1\")
The WordPress Pattern Directory includes attractive, handy patterns created by designers that can make your experience building a stunning site much easier. Patterns can save you a significant amount of time and also give you greater freedom when you’re building your site. With patterns, you can make or replicate complex layouts with just a few clicks, and using them is as simple as copy and paste.
\n\n\n\nCreate Your Own Bold, Beautiful Patterns Built Entirely with Blocks
\n\n\n\n![\"Pattern](\"https://i1.wp.com/wordpress.org/news/files/2022/03/submission-2.png?ssl=1\")
As the name implies, the Pattern Creator allows anyone, from designers to content creators, to make custom patterns: a collection of blocks arranged in any way, for any purpose intended by the creator. Like most things in WordPress, these are available for public use once it’s submitted to the WordPress Pattern Directory. Have a look at these guidelines to learn more about what makes a pattern suitable for listing in the directory.
\n\n\n\nSo what are you waiting for? Check out all the patterns already available or better yet, make your own!
\n\n\n\nWho is WordPress actually made for? Join our host, WordPress Executive Director Josepha Haden Chomphosy, as she explores this controversial question and three things that can help find the answer.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nHosts: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Beatriz Fialho
Production: Santana Inniss
References
\n\n\n\n- WordCamp Europe call for volunteers
- WordPress Photo Directory team
- UNICEF
- Médecins Sans Frontieres
- International Committee of the Red Cross
- International Rescue Committee
- UN Refugee Agency
- World Central Kitchen
- Tech For Ukraine
- #WP4Ukraine
Transcript
\n\n\nRead more\n\n\nEpisode 27
\n\n\n\nJosepha Haden Chomphosy [00:00:00]
\n\n\n\nHello everyone, and welcome to the WordPress Briefing: the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nToday, we’re talking about who WordPress is built for. I was talking to a group of contributors last week and we encountered some questions around just who WordPress is built for. And it’s a question that you’ll find any time that you’re working on user testing or on triaging tickets, and especially when that comes up when you look at the big picture, roadmap sorts of things. The easiest answer for this question is, of course, everyone because WordPress’ mission is to democratize publishing and that should be available to everyone.
\n\n\n\nJosepha Haden Chomphosy [00:01:11]
\n\n\n\nHowever, everyone is a really big target and certainly doesn’t help get your mind around the people that you’re wanting to actually build it for, the people that you actually want to be able to use your product, your software on a day-to-day basis. So let’s take a look at the one question that can help us figure out who it’s built for today and how we get it to being something that’s built forever.
\n\n\n\nFirstly, there’s a basic premise of open source that informs this thought. And that premise is that we are citizens of a community of contributors therefore the decisions are made by the people who show up. In general, I believe that to be true, though, I also believe that some basic qualifications are needed.
\n\n\n\nJosepha Haden Chomphosy [00:01:50]
\n\n\n\nSo with that in mind, the one question that can help us figure out who a software is built for is this: how do your active contributors see themselves? I would bet that most contributors to open source software projects, like WordPress, are developers of some sort, it is sort of written right into the definition of the project.
\n\n\n\nIf you work on software, then you need developers. And what I love about WordPress, in particular, is that we do work to include contributors who are not developers. Yet it still remains true that there is a fairly high level of technical knowledge required to actively contribute.
\n\n\n\nJosepha Haden Chomphosy [00:2:25]
\n\n\n\nWhich kind of brings us to the second half of the original question of how can we make sure that WordPress can be something that’s built for everyone? The answer to this one is easy to say, hard to do, and that is to make sure to include them as co-creators in the development process.
\n\n\n\nWe’ve talked about co-creators in open source before. It’s this idea that people who use the software every day are likely to know the biggest pain points. So if you want your software to be used by people who don’t know HTML, talk to a bunch of people who don’t know HTML about how it is to use your software.
\n\n\n\nIf you want your software to be mostly used by enterprise agencies, talk to enterprise agencies, but also ask them what their clients hate, because everyone has more than one stakeholder. And I know that I said this already, but it bears repeating that, obviously, this is all very easy to say and hard to do.
\n\n\n\nJosepha Haden Chomphosy [00:3:20]
\n\n\n\nSo what is my best guess for the how-to-do part for WordPress? There are three things.
\n\n\n\nThe first is testing. This not only helps bring in new contributors and helps train future contributors, which I’ve talked about on the podcast before. But testing also gives us a higher chance of actionable feedback from folks who don’t necessarily spend time directly in the WordPress project.
\n\n\n\nFrequently the feedback that we do get that is just kind of undirected and ad hoc is exactly that– it is undirected and ad hoc and is then hard to follow up on and make sure that we understand what was wrong and how we can help fix it. And so testing is important for that. And testing it turns out is important for a bunch of things. When you’re working in open source.
\n\n\n\nThe next thing is support. So checking in with support teams at hosts, as well as the hardworking support teams in the project. And that can really help us to get early indications of what difficulties exist now. They have routinely seen problems and issues that are raised in support forums, and from their everyday users that they are providing support to.
\n\n\n\nThat probably could be fixed in WordPress if we had a good understanding of just what was not going right, how many people really needed it to go better, and what our targets were to fix that particular problem.
\n\n\n\nJosepha Haden Chomphosy [00:4:45]
\n\n\n\nAnd the third thing is communication. I know that I’ve gone on record in many places as saying that most of our problems at the end of the day are communication problems. And I’m going on record about it again here in this podcast, establishing better communication patterns with users is key.
\n\n\n\nThat can be a multi-year project in itself. And even after that, it’s going to be an ongoing journey. But it is one of the many things that WordCamps and other WordPress events have given to us over the years, an opportunity to really hear from and see the struggles that people who are not building with WordPress every day, or literally building WordPress every day are actually having.
\n\n\n\nJosepha Haden Chomphosy [00:5:34]
\n\n\n\nSo now that you’ve heard my small list of way too big things, that brings us to our regular small list of big things. The first thing is that WordCamp Europe is still looking for volunteers. If you’ve never done that before, I think it’s quite fun. You get to meet a lot of people and the team of organizers is super fun, but I’ll leave a link for you in the show notes.
\n\n\n\nWe also have a new code-free way to contribute through the photo directory. That team is just getting started and still is working toward building out its programs. So now’s a good time to drop in and just kind of see what they are up to. And finally, a reminder that we do have contributors who are affected by the war in Ukraine right now. I will reshare the list of humanitarian organizations in case you missed them a couple of weeks ago as well.
\n\n\n\nJosepha Haden Chomphosy [00:6:21]
\n\n\n\nAnd that my friends is your small list of big things. Thank you for tuning in today for this WordPress Briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12451\";s: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: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:48:\"WordPress 5.9.2 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wordpress.org/news/2022/03/wordpress-5-9-2-security-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 11 Mar 2022 02:24:13 +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:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Security\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12421\";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:367:\"WordPress 5.9.2 is now available! This security and maintenance release features 1 bug fix in addition to 3 security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated. WordPress 5.9.2 is a security and maintenance release. The next major 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:9:\"Jb Audras\";s: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:3697:\"\nWordPress 5.9.2 is now available!
\n\n\n\nThis security and maintenance release features 1 bug fix in addition to 3 security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated.
\n\n\n\nWordPress 5.9.2 is a security and maintenance release. The next major release will be version 6.0.
\n\n\n\nYou can download WordPress 5.9.2 from WordPress.org, or visit your Dashboard → Updates and click “Update Now”.
\n\n\n\nIf you have sites that support automatic background updates, they’ve already started the update process.
\n\n\n\nThe security team would like to thank the following people for responsively reporting vulnerabilities, allowing them to be fixed in this release:
\n\n\n\n- Melar Dev, for finding a Prototype Pollution Vulnerability in a jQuery dependency
- Ben Bidner of the WordPress security team, for finding a Stored Cross Site Scripting Vulnerability
- Researchers from Johns Hopkins University, for finding a Prototype Pollution Vulnerability in the block editor
For more information, browse the full list of changes on Trac, or check out the version 5.9.2 HelpHub documentation page.
\n\n\n\nThanks and props!
\n\n\n\nThe 5.9.2 release was led by Jb Audras, with the help of Jorge Costa on package updates, Sergey Biryukov on mission control, and David Baumwald on backport commits.
\n\n\n\nIn addition to the release squad members and security researchers mentioned above, thank you to everyone who helped make WordPress 5.9.2 happen:
\n\n\n\nAlan Jacob Mathew, Alex Concha, André, Anton Vlasenko, David Baumwald, ehtis, Jb Audras, Jorge Costa, Peter Wilson, Sergey Biryukov, Tonya Mork, and ironprogrammer.
\n\n\n\nProps @davidbaumwald and @sergeybiryukov for peer review.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12421\";s: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:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WP Briefing: Episode 26: Matt Mullenweg on Ukraine, Community, and WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"https://wordpress.org/news/2022/03/episode-26-matt-mullenweg-on-ukraine-community-and-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Mar 2022 21:39:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=12415\";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:384:\"Matt Mullenweg speaks to WordPress contributors worldwide on this special edition of the WP Briefing podcast with Josepha Haden Chomphosy. Join us to hear Matt’s thoughts on Ukraine. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Hosts: Josepha Haden Chomphosy and Matt Mullenweg […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:62:\"https://wordpress.org/news/files/2022/03/WP-Briefing-026-1.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6361:\"\nMatt Mullenweg speaks to WordPress contributors worldwide on this special edition of the WP Briefing podcast with Josepha Haden Chomphosy. Join us to hear Matt’s thoughts on Ukraine.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Hosts: Josepha Haden Chomphosy and Matt Mullenweg
- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann & Santana Inniss
How You Can Help
\n\n\n\n\n\n\n\n\n\n\n\nInternational Committee of the Red Cross
\n\n\n\nInternational Rescue Committee
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nTranscript
\n\n\n\n\n\n\n\nJosepha Haden Chomphosy 00:00
\n\n\n\nHello, everyone, and welcome to a special edition of the WordPress Briefing. I have Matt here with me today because we want to acknowledge that we are once again at the start of a very difficult time. Neither of us would presume to know what it’s like to be at the heart of such massive disruption in our lives. But who would we be if we didn’t stop and check in with you all, the project that we hold so dear? And with that, I’ll hand it right over to you, Matt.
\n\n\n\nMatt Mullenweg 00:27
\n\n\n\nHello everyone. First, I want to thank Josepha for inviting me to join the WordPress Briefing to share what’s been on my mind in light of recent global events.
\n\n\n\nMatt Mullenweg 00:37
\n\n\n\nI’ve been listening and watching events escalate in Ukraine, often in a state of shock. The scale alone is hard to take in. I mean, in the last 7 days, more than 500,000 people have fled their homes, more refugees are expected every day. The downstream humanitarian crises of the invasion are unimaginable.
\n\n\n\nMatt Mullenweg 00:56
\n\n\n\nAnd seeing destruction in the world we live in is confusing, disconcerting, and difficult. In my experience, open source and WordPress bring people together; people from other countries and cultures, people that we know as friends and colleagues. Technology connects us, regardless of where we are. Nothing can negate the bad things happening in the world, but when I see how this community of contributors collaborates, regardless of borders, you all remind me of the good in the world every day.
\n\n\n\nMatt Mullenweg 01:30
\n\n\n\nI firmly believe that the web can be an equalizer and a force for good in the world. To me, the WordPress project is the epitome of goodness—everyone has a voice, a platform, and a community. You have the power to make your corner of the world, and the web, a sanctuary for those who need it—especially now.
\n\n\n\nMatt Mullenweg 01:45
\n\n\n\nIf you or someone you know is affected by this war, I encourage you to be present as the ramifications unfold. While we may all feel fatigued and have a sense of languishing from the past two years of the Covid pandemic, the gift of time and support for one another cannot be overstated. I’m confident that every single person in the WordPress community will approach the situation in Ukraine with sensitivity and understanding.
\n\n\n\nMatt Mullenweg 02:07
\n\n\n\nI invite you to join me in standing with those in the world working to end conflict and working toward a world of peace, promise, and opportunity. If you’re looking for a way to help support the humanitarian crisis in Ukraine, I will offer some suggested NGOs, or Non-Governmental Organizations, that provide assistance to local peacebuilders in the region.
\n\n\n\nMatt Mullenweg 02:26
\n\n\n\nIn closing, please know that my thoughts are with everyone in our community. I know that my words here can’t change anything there, but I hope that we all remember that words of support are never unwelcome. And we can never know when a little human kindness can help someone share the invisible heaviness in their heart.
\n\n\n\nJosepha Haden Chomphosy 02:44
\n\n\n\nThanks for that, Matt. My friends, there are links in the show notes to some of the groups that Matt referenced. And that is it for this special edition of the WordPress Briefing. I’m your host, Josepha Haden Chomphosy. Be safe, be kind to yourself and others, and I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12415\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s: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:40:\"The Month in WordPress – February 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2022/03/the-month-in-wordpress-february-2022/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Mar 2022 17:40:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:22:\"the month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12411\";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:332:\"There’s a lot going on in the world right now, and safety is top of mind for everyone in the WordPress community. If you don’t know where to begin, or how to support your peers, Executive Director Josepha Chomphosy’s advice to the global community is to start small. Overall, February has been a busy month […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Anjana Vasan\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:11940:\"\nThere’s a lot going on in the world right now, and safety is top of mind for everyone in the WordPress community. If you don’t know where to begin, or how to support your peers, Executive Director Josepha Chomphosy’s advice to the global community is to start small.
\n\n\n\nOverall, February has been a busy month for WordPress. To begin with, it was thrilling to see the enthusiasm for the release of WordPress 5.9 Joséphine from January continue last month, and that’s not all.
\n\n\n\nWe have many exciting updates to share, so keep reading to learn about the latest achievements from the WordPress community.
\n\n\n\n\n\n\n\n
WordPress 6.0: May 24, 2022 is the proposed release date
\n\n\n\n- The proposed release schedule for WordPress 6.0, the second major release of 2022, has been published.
- While we’re waiting for 6.0, check out the WordPress 5.9.1 maintenance release which was released on February 22, 2022.
Gutenberg releases: Versions 12.5, 12.6, and 12.7 were released
\n\n\n\nThe Core Team launched three new versions of Gutenberg last month. All come with new features, code quality improvements, and bug fixes.
\n\n\n\n- Gutenberg 12.7 is available to download. This version improves the Patterns experience, allows you to add border styles to column blocks, and includes other new features.
- Gutenberg 12.6 was launched on February 16, 2022. This release includes a new color panel, updated color controls, a new Post Author Biography block, Read More block, and plenty of other exciting updates!
- Gutenberg 12.5 was released on February 2, 2022. This version allows switching theme styles variations, custom taxonomies filtering, and more.
WordPress News gets a new look
\n\n\n\nThe redesign of WordPress News, which was first announced by Matt Mullenweg, Co-Founder of WordPress, in State of the Word 2021, went live on February 16, 2022.
\n\n\n\nTeam updates: #WP Diversity, a new blog for developers, and more
\n\n\n\n- The #WPDiversity working group, which is part of the Community Team, hosted an open Zoom meeting with volunteers on February 23, 2022. If you’re interested in contributing, read the recap of the meeting to view available roles.
- The Core Team shared a proposal to start a blog on developer.wordpress.org to share news and updates relevant to developers.
- The first Gutenberg Developer Hours session hosted on February 8th by the Core Team was successful. Head over to this page to learn more about the participants’ feedback.
- The Core Team published “Feature Project: Plugin Dependencies,” where they identified the problems with plugin dependencies and suggested potential solutions to improve the plugin experience.
- The WordPress Photo Directory has a new Make team. There is currently an open call for team reps and collaboration is happening at the new #photos channel of the Make WordPress Slack.
- The Polyglots Team shared a proposal for a milestone template for the Polyglots Locale Teams.
- The Community Team published a proposal for refurbishing camera kits.
- The Global Community Sponsors for 2022 have been announced.
- The February 2022 edition of the monthly Meetup Organizer Newsletter has been published.
- The latest edition of People of WordPress highlighting Tonya Mork was published on February 28, 2022. Read Tonya’s story to learn more about how WordPress helped her find herself again after a health crisis.
- The February 2022 edition of the Polyglots Monthly Newsletter has been published.
Feedback/Testing requests: WordPress iOS 19.3 and Android 19.3
\n\n\n\n- WordPress for iOS 19.3 beta is available for testing, along with WordPress for Android 19.3
WordCamp Europe 2022 announces steps to ensure a diverse, inclusive, and welcoming event
\n\n\n\n- WordCamp Europe 2022 announced a plan to ensure more diversity and inclusion in events moving forward.
- The WordPress Foundation published a post on how open source software is good for business.
- In a recent episode of WP Briefing titled “Five Cents on Five for the Future,” Executive Director Josepha Haden Chomphosy talks about future-proofing the WordPress project with the Five for the Future pledge.
- The Training Team is hosting several WordPress Social Learning Meetups in March 2022.
- Don’t miss the following upcoming WordCamps:
- WordCamp Genève, Switzerland on April 9, 2022 (in person)
- WordCamp Athens, Greece between April 9 and 10, 2022 (in person)
- WordCamp Vienna, Austria from April 23 to 24, 2022 (in person)
![\"??\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f1ea-1f1fa.png\")
WordCamp Europe in Porto, Portugal from June 2 to 4, 2022 (in person)![\"??\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f1fa-1f1f8.png\")
WordCamp Montclair in New Jersey, USA June 25 (in person)- WordCamp US in San Diego, California from September 9 to 11, 2022 (in person)
\n\n\n\n
Have a story that we could include in the next ‘Month in WordPress’ post? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this Month in WordPress: @anjanavasan @harishanker @rmartinezduque @mysweetcate
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12411\";s: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:78:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"People of WordPress: Tonya Mork\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2022/02/people-of-wordpress-tonya-mork/\";s: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 Feb 2022 23:55:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:8:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:3:\"5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:4:\"core\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:9:\"HeroPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:6;a:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:7;a:5:{s:4:\"data\";s:9:\"Test Team\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12151\";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:98:\"The People of WordPress feature this month shares the story of engineer and developer Tonya Mork. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"webcommsat AbhaNonStopNewsUK\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:14131:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a website developer and engineer from the US, who found the software and its community provide the impetus to keep her going forward.
\n\n\n\nWordPress gave Tonya Mork a new lease of energy after a health crisis from which she nearly died. She had spent two decades as an electrical and software engineer in high tech automated manufacturing. But when she discovered the WordPress software, teaching it to others became her new purpose. Through this discovery, she has gone on to help thousands of developers understand and build code in great depth.
\n\n\n\nAs part of her WordPress journey, she has shared her skills in the roles of Release Coordinator and the Core Tech Editor for the most recent major WordPress release, 5.9 Joséphine.
\n\n\n\n![\"Tonya](\"https://i0.wp.com/wordpress.org/news/files/2022/02/featured-img-tonyamork.jpg?resize=1024%2C515&ssl=1\")
Life takes an unexpected turn
\n\n\n\nFor the first 22 years of Tonya’s life, she rose through the ranks from enlisted personnel in the US Navy to a highly sought after chief engineer with a multi million-dollar industrial automation engineering firm.
\n\n\n\nHowever, while she was working in engineering, her life was to change dramatically. In 2007, Tonya started to face health challenges that had an impact on all that she had known.
\n\n\n\n\n\n\n\n“My career defined me. It was my canvas and my art. When it was gone, I did not recognize myself.
Tonya Mork
One day, she woke up at home ready to visit a client’s facility where her firm was building a robotic system. She said: “As I headed for the door, I fell to my knees, as this wave of pain crushed down on my chest.”
\n\n\n\nDoctors diagnosed her with a very rare heart disease that caused her blood vessels to spasm, cutting off blood to whatever was downstream of the blockage.
\n\n\n\nA few months later, she was diagnosed with a second rare and more serious condition, related to the migraines from which she had been suffering. Combined with her heart condition, this made every migraine attack life-threatening.
\n\n\n\nFor nearly seven years, the unexpected changes to her health left her mostly homebound and constantly monitored. This meant she had to close her engineering firm and say goodbye to staff and clients.
\n\n\n\n“My career defined me. It was my canvas and my art. When it was gone, I was lost. I didn’t recognize myself.”
\n\n\n\nBut in her darkest hour, she found her strength. Tonya made a choice to move forward, and make the most of her life.
\n\n\n\n“When you are at rock bottom, you have to make a decision or else it will consume you. My decision was that I chose to be happy,” said Tonya.
\n\n\n\nOne of Tonya’s first steps was to start writing a blog using WordPress. In this she shared insights on how to find peace and joy in any situation. She wrote about kindness and helping one another.
\n\n\n\nThe joy of making solutions through WordPress became a way for Tonya to accept her new life and not feel as limited by her health. She wanted purpose, and in WordPress, she found just that.
\n\n\n\nTonya felt she could do something worthwhile in the virtual world.
\n\n\n\nA ray of hope for Tonya
\n\n\n\n![\"\"](\"https://i1.wp.com/wordpress.org/news/files/2022/02/tonya.jpg?resize=1000%2C750&ssl=1\")
In 2013, Tonya’s health deteriorated further. She was admitted into intensive care and was diagnosed with a third rare disease, this time related to her autoimmunity. She was not expected to survive this time.
\n\n\n\nFollowing what she describes as a ‘miraculous recovery,’ she became stronger and was able to stop relying on a wheelchair. She used the energy from working on websites to keep going. “WordPress kept my mind alive,” said Tonya.
\n\n\n\nShe had first used WordPress for her engineering firm’s intranet. But when she discovered the software’s full potential and the collaborative opportunities of open source, it opened a new world.
\n\n\n\n“Finding WordPress helped me to find myself again”
Tonya Mork
During the years which followed, she donated her time to build some WordPress websites and plugins. She said: “Through giving my time, I was able to do something other than sit in isolation.”
\n\n\n\nTonya was amazed by the sharing in open source in general and in WordPress in particular. She said: “I was amazed to see people sharing so much information freely with one another. In my former engineering world, information was proprietary. Throughout my career, I had worked to break down those silos and help anyone to understand complex systems. I was drawn to this open community.”
\n\n\n\nShe also became aware that WordPress developers were hungry to learn more about development. She wanted to be part of the solution with her passion for teaching and the knowledge she had gained in industry.
She said: “Finding WordPress helped me to find myself again. Here in this community, I was able to feel like a person again, not a sick one, but a professional with something to give.”
As her interest in the software grew, Tonya decided to start a non-profit where she turned to WordPress to build the websites. This re-sparked her interest in programming. She said: “I wanted to really know the code and understand what made it tick.”
\n\n\n\nThe realization led Tonya to start the WP Developers’ Club, which in turn spawned Know the Code, to help educate individual developers, and is still used today.
\n\n\n\nFrom helping WordPress companies to working on WordPress Core
\n\n\n\n![\"Tonya](\"https://i0.wp.com/wordpress.org/news/files/2022/02/tonya-with-dog.jpg?resize=300%2C300&ssl=1\")
Tonya went on to work with big and medium size WordPress companies helping their developers and supporting them in raising their firms’ leverage with WordPress.
\n\n\n\nBy late 2020, she knew she wanted to do even more with WordPress.
\n\n\n\nIn February 2021, Tonya joined an international firm in the ecosystem and began working closely on WordPress Core.
\n\n\n\nAt that time, WordPress Core was pulling together a new Triage team. Tonya started volunteering on that team to find collaborative solutions, and help others do so. In 2020 for WordPress 5.6 Simone, she became the release’s Triage lead, and again for WordPress 5.7 Esperanza.
\n\n\n\nIn 2021, she became a Test Team Rep and helped to expand the team and is an advocate for the value of testing and feedback in the release development process.
\n\n\n\nA new, successful chapter with WordPress 5.9
\n\n\n\n![\"Tonya](\"https://i1.wp.com/wordpress.org/news/files/2022/02/WP59-thumbnail-jb.png?resize=1024%2C480&ssl=1\")
Tonya’s passion for the software and getting people involved in its growth continued. For the WordPress 5.9 release in 2021, she took on the role of both the Core Tech Lead and the Release Coordinator. As this was a big release and included the first major implementation of Full Site Editing, it had many moving parts and hundreds of contributors. She was able to share the skills she had learned in communication and project management from her days streamlining and documenting engineering software and processes.
\n\n\n\nIn the first 24 hours of WordPress 5.9 landing, it had more than 10 million downloads—and 17 formally reported bugs.
\n\n\n\nGiving back to open source
\n\n\n\nNow in what Tonya describes as her third chapter. She said: “I’m a very different person from the engineer I used to know. What really matters in this world is when you reach out and make a difference in someone’s life.”
\n\n\n\nShe feels she has found her purpose in this life. “I’m on a mission to give back and make a difference. Teaching is how I will do it. And in WordPress I have found my professional home, and I have all this software knowledge that I just want to share.”
\n\n\n\nShare the stories
\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nContributors to this feature
\n\n\n\nThank you to Tonya Mork (@hellofromtonya) for sharing her story.
\n\n\n\nInterviews and feature by Abha Thakor (@webcommsat) and Mary Baum (@marybaum). Reviewed by Chloe Bringmann (@cbringmann), Nalini Thakor (@nalininonstopnewsuk), Meher Bala (@meher), and Anjana Vasan (@anjanavasan). Photo editing Reyez Martínez (@rmartinezduque) and Jean Baptiste Audras (@audrasjb).
\n\n\n\nThanks to Josepha Haden Chomphosy (@chanthaboune) and Topher DeRosia (@topher1kenobe) and others for their support of this initiative.
\n\n\n\nThis People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress
\nWordPress 5.9.1 is now available!
\n\n\n\nThis maintenance release features 82 bug fixes in both Core and the block editor.
\n\n\n\nWordPress 5.9.1 is a short-cycle maintenance release. The next major release will be version 6.0.
\n\n\n\nYou can download WordPress 5.9.1 from WordPress.org, or visit your Dashboard → Updates and click “Update Now”.
\n\n\n\nIf you have sites that support automatic background updates, they’ve already started the update process.
\n\n\n\nFor more information, browse the full list of both Trac and GitHub changes in the release candidate post, or check out the version 5.9.1 HelpHub documentation page.
\n\n\n\nThanks and props!
\n\n\n\nThe 5.9.1 release was led by Jb Audras and George Mamadashvili.
\n\n\n\nSpecial props to @sergeybiryukov for running mission control.
\n\n\n\nThank you to everyone who helped make WordPress 5.9.1 happen:
\n\n\n\nAlbert Juhé Lluveras, Alex Lende, alexstine, André, Anton Vlasenko, Ari Stathopoulos, ArteMa, Ben Dwyer, BlogAid, Carolina Nymark, Channing Ritter, Chris Van Patten, Colin Stewart, Daniel Richards, David Biňovec, David Smith, Dion Hulse, Dominik Schilling, Eddy, Ella van Durpe, Erik, Fabian Kägy, Flinim Asso, gadhiyaravi, George Hotelling, George Mamadashvili, glendaviesnz, Greg Ziółkowski, ianatkins, Ian Belanger, ironprogrammer, itsamoreh, Jb Audras, Jeff Ong, Jeremy Herve, Joe Dolson, Joen A., John Blackbourn, Jonathan Desrosiers, Jorge Costa, Juliette Reinders Folmer, KafleG, Kapil Paul, Kjell Reigstad, linux4me2, Lukman Nakib, manfcarlo, Marius L. J., mgol, nidhidhandhukiya, Nik Tsekouras, Omar Alshaker, Paolo L. Scala, Pascal Birchler, Paul Bearne, Pavlo, Petar Ratković, Peter Wilson, Petter Walbø Johnsgård, Phil Johnston, Piotrek Boniu, ravipatel, Riad Benguella, Robert Anderson, Rolf Siebers, Sergey Biryukov, stacimc, Stephen Bernhardt, Sven Wagener, Team Staatic, Tim Nolte, Tonya Mork, webcommsat AbhaNonStopNewsUK, WebMan Design | Oliver Juhas, wpcharged, wpsoul, Yunus Ertuğrul, and Rafi Ahmed.
\n\n\n\nThanks to @estelaris, @pbiron, @ironprogrammer, @bph, @abhanonstopnewsuk and @threadi for their help to test the release package.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12266\";s: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:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"WP Briefing: Episode 25: Five Cents on Five for 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:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wordpress.org/news/2022/02/episode-25-five-cents-on-five-for-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:\"Mon, 21 Feb 2022 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=12288\";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:450:\"In this twenty-fifth episode of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy discusses future-proofing the WordPress project with the Five for the Future pledge. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho Production: Chloé Bringmann & Santana Inniss Song: […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/02/WP-Briefing-025.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:10286:\"\nIn this twenty-fifth episode of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy discusses future-proofing the WordPress project with the Five for the Future pledge.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann & Santana Inniss
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- Five for the Future, on ma.tt circa 2014
- Governing the Commons, Elinor Ostrom
- Five for the Future White Paper
- 6.0 Planning Roundup
- Part I: Full Site Editing Course
- Part II: Full Site Editing Course
- Part III: Full Site Eiditing Course
Transcript
\n\n\n\n\n\n\n\nEpisode 25
\n\n\n\nJosepha Haden Chomphosy [00:00:00]
\n\n\n\nHello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project. Some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy – here we go!
\n\n\n\nJosepha Haden Chomphosy [00:00:42]
\n\n\n\nI have a non-mailbag mailbag question that I would like to answer for y’all today. Non-mailbag because no one actually emailed me about it and mailbag because Twitter is basically like a giant mailbag. And I do get a lot of DMS about this particular topic. If you want to send something to my actual WP Briefing mailbag, you can send it to wpbriefing@worpress.org.
\n\n\n\nJosepha Haden Chomphosy [00:01:06]
\n\n\n\nBut the question that I frequently get asked in my DMS on Twitter is: what is Five for the Future? It’s not always that tidy the question, but that still is the question we’re answering today. So if you take a casual survey of active contributors to the WordPress project, the high-level answer that you’re likely to get to that question is “a way to remind people to give back to the project.” Or, if you run in more business-y circles, you might hear that it is an initiative that encourages companies to give back 5% of their resources.
\n\n\n\nJosepha Haden Chomphosy [00:01:40]
\n\n\n\nAnd both of those answers are true. So a quick mini-history lesson; the original concept of Five for the Future came from Matt Mullenweg in 2014. There’s a lovely blog post on it that I will link in the notes below, but it was essentially a call to any companies experiencing success with WordPress to contribute back to the project and make sure that the project was a success.
\n\n\n\nJosepha Haden Chomphosy [00:02:07]
\n\n\n\nThe initial program then included outreach recognition, et cetera, proposed in 2017 by Tracy Levesque and Ian Dunn. Then that was defined and formalized with the help of the WordPress community in 2018. And then, in 2019, we had our first trial run with entire dedicated teams sponsored by companies inside the WordPress ecosystem.
\n\n\n\nJosepha Haden Chomphosy [00:02:36]
\n\n\n\nSo that’s the mini-history lesson chronology of this program. The intentions that informed the work of building the program in 2017 have become a bit lost to the ages. So I’m here to share it with you. The basic heart and soul of the Five for the Future program is to make sure that there is a way to refresh the commons of the WordPress community and ecosystem.
\n\n\n\nJosepha Haden Chomphosy [00:03:00]
\n\n\n\nAnd as a result, ensure that the common resources of WordPress are available long after we have stopped being available to care for them. If you are familiar with the concept of the tragedy of the commons, Five for the Future was created to help avoid that tragedy. There were two original goals for formalizing the program.
\n\n\n\nJosepha Haden Chomphosy [00:03:22]
\n\n\n\nThe first one was to acknowledge companies that participated in Five for the Future by sponsoring contributors to work on the WordPress project. And the second was to motivate more companies to sponsor more volunteers. Either by hiring them and paying them to contribute or by assigning their existing employees to contribute to the WordPress project.
\n\n\n\nJosepha Haden Chomphosy [00:03:46]
\n\n\n\nOf course, it’s hard to quantify participation and hard to qualify what should be seen as an impactful contribution, which is why when the program was originally created, it was in partnership with team reps and community members who were active at the time. There are many posts around that discuss the next steps for this program.
\n\n\n\nJosepha Haden Chomphosy [00:04:07]
\n\n\n\nAnd as I’m looking through them, the next steps revolve around some of the hardest and most important questions that we have to answer as a project and as stewards of open source. Those questions are things like:
\n\n\n\n- How do we remain true to these gloriously subversive values of WordPress and open source while also finding a way to thoughtfully secure our organization’s future?
- Does contributing without the expectation of reciprocity hold up when we are looking at how to acknowledge contributors who sustain us?
Josepha Haden Chomphosy [00:04:40]
\n\n\n\nAnd if you’re familiar with Elinor Ostrom’s award-winning work, Governing the Commons, you may also be wondering how this particular program aligns with her eight principles designed to sustain organizations like ours.
\n\n\n\nJosepha Haden Chomphosy [00:04:57]
\n\n\n\nAs an aside to that last question, this particular program does not have all eight principles accounted for, but among WordPress’s many programs, we do account for most of them. Although imperfectly, as is the way with human beings, that’s probably a whole episode unto itself, I did want to quickly answer that particular question.
\n\n\n\nJosepha Haden Chomphosy [00:05:16]
\n\n\n\nSo to get back to my non-mailbag, mailbag question, if I had to tell you in the span of an elevator ride what Five for the Future was, this would be my answer. It is a v1 program with a dual goal of boldly declaring the need to refresh the shared resources of WordPress and offering the ways and means for communities and individuals alike to participate in refreshing those resources.
\n\n\n\nJosepha Haden Chomphosy [00:05:45]
\n\n\n\nIf you want to learn more about the Five for the Future initiative, you can check out wordpress.org/5. Like literally just the number five. Or, if you want to learn more about the program that has grown from the Five for the Future initiative, you can check out the white paper that’s linked in the notes below.
\n\n\n\nJosepha Haden Chomphosy [00:06:11]
\n\n\n\nAnd that brings us now to our small list of big things. Number one on my small list, the planning post for WordPress 6.0 is out. I’ve included a link in my massive list of links below. But it includes our best guess at timing, features that we intend to include, and a call for volunteers as well. So if you are looking for ways to give back, that is a clear and immediate option.
\n\n\n\nJosepha Haden Chomphosy [00:06:38]
\n\n\n\nThe second thing on the list is if you are a team rep, don’t forget that we have daylight saving time ending and starting depending on your hemisphere within the month. If you move meetings, if you’re in a team that moves your meetings, discuss it now so that folks have time to adjust their calendars.
\n\n\n\nJosepha Haden Chomphosy [00:06:55]
\n\n\n\nAnd the third thing on my small list of big things is that there’s a suite of Full Site Editing courses that are now available on learn.wordpress.org. I will add that to my giant list of links below, but I encourage you to wander on over and see what all the fuss is about. I think the courses are excellent. They’re great for folks who don’t quite know what Full Site Editing is yet, but then also they give you a few intermediate tips and tricks as you’re getting your legs underneath you.
\n\n\n\nJosepha Haden Chomphosy [00:07:27]
\n\n\n\nSo, that my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12288\";s: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: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:\"A New WordPress News\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2022/02/a-new-wordpress-news/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 16 Feb 2022 17:56:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:6:\"Design\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:4:\"Meta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12244\";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:385:\"In June 2021, @beafialho in collaboration with @pablohoney floated the idea of giving WordPress News a new look. Today, those ideas become a reality—we’re excited to share that redesign of WordPress News is live! The new design leans on the aesthetics of jazz, intrinsically connected to WordPress and which ultimately translates its uniqueness, historic significance […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Kelly Hoffman\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5727:\"\n![\"\"](\"https://i1.wp.com/wordpress.org/news/files/2022/02/news_responsive_sizes-scaled.jpg?resize=2560%2C1605&ssl=1\")
In June 2021, @beafialho in collaboration with @pablohoney floated the idea of giving WordPress News a new look. Today, those ideas become a reality—we’re excited to share that redesign of WordPress News is live!
\n\n\n\nThe new design leans on the aesthetics of jazz, intrinsically connected to WordPress and which ultimately translates its uniqueness, historic significance and future potential. Among other improvements, the new design leaves more space for content and includes new typefaces for better readability. It also uses a color palette intended to reflect the evolving Gutenberg language.
\n\n\n\n![\"\"](\"https://i0.wp.com/wordpress.org/news/files/2022/02/news_postpages-scaled.jpg?resize=2560%2C1605&ssl=1\")
![\"\"](\"https://i2.wp.com/wordpress.org/news/files/2022/02/news_communitypodcast-scaled.jpg?resize=2560%2C1605&ssl=1\")
The revamp of the WordPress News page includes the header and footer of the page. We also shipped those two global elements to all pages of WordPress.org. However, there’s more work to do within the header to improve the information architecture. This new design is just the first, small step to modernize and improve the site iteratively. Any further discussion on future redesigns will occur in the #design channel on Slack.
\n\n\n\n![\"\"](\"https://i1.wp.com/wordpress.org/news/files/2022/02/news_mobile_menu-scaled.jpg?resize=2560%2C1605&ssl=1\")
Take a look around and subscribe to WordPress News if you haven’t already. If you see something in the design that doesn’t look right, please submit an issue on GitHub.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12244\";s: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:58:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"WP Briefing: Episode 24: Three Goals in 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2022/02/episode-24-three-goals-in-2022/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 07 Feb 2022 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=12176\";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:413:\"In episode 24 of the WordPress Briefing, the Project’s Executive Director reviews three big-picture goals for the year: Increased Gutenberg adoption, support of all open source alternatives, and stewarding the open source ethos. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Editor: Dustin Hartzler […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/02/WP-Briefing-024.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s:0:\"\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:9160:\"\nIn episode 24 of the WordPress Briefing, the Project’s Executive Director reviews three big-picture goals for the year: Increased Gutenberg adoption, support of all open source alternatives, and stewarding the open source ethos.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- Big Picture Goals 2022
- Preliminary Roadmap for 6.0 (Gutenberg Phase 2)
- A New News Design
- Making WordPress: Unofficial aggregator for all Making WordPress blogs
Transcript
\n\n\n\n\n\n\n\nEpisode 24
\n\n\n\nJosepha Haden Chomphosy 00:00
\n\n\n\nHello everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project. Some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nJosepha Haden Chomphosy 01:07
\n\n\n\nA couple of weeks ago, I published a post about the big picture goals for the WordPress project in 2022. As I was thinking through our planned releases for the year and looking out toward what would spell success for WordPress over the next three years, three things really lined up in both sets of answers for me.
\n\n\n\nJosepha Haden Chomphosy 01:23
\n\n\n\nI provided some detail on how we can work toward these goals in the post, which I will link for you in the show notes, but I also wanted to take some time to explain why I feel we have to work toward these goals this year. So these all build on one another. To refresh your memory of the three big focuses, they are one to drive adoption of the new editor in WordPress, support open source alternatives for site building necessities, and three, open source stewardship.
\n\n\n\nJosepha Haden Chomphosy 01:52
\n\n\n\nSo the first one; is driving the adoption of the new WordPress editor. Early on in the start of the Gutenberg Project, folks could not go two days without hearing me talk about the phases of adoption and how those line up with the phases of Gutenberg, and who would need our support the most in each of those phases.
\n\n\n\nJosepha Haden Chomphosy 02:09
\n\n\n\nI have always believed that what we would be shipping at this point in our project would prove the plausible promise of what we were doing in phase one. That’s definitely what I’m seeing from what was shipped in 5.9, as well as what we plan to ship in May with 6.0. And the people who need the most support right now are absolutely our users, your clients, no matter whether they were not keeping up with WordPress developments or simply were waiting to see what all the fuss was about.
\n\n\n\nJosepha Haden Chomphosy 02:37
\n\n\n\nThere will be people who look to you as someone who has been here a while to help them make sense of what they’re seeing. And what I find so exciting about this adoption, sort of, work in the WordPress project is that this is the time when we as practitioners of WordPress, no matter whether you are a designer or a developer or builder, business coach. This is the time when we get to guide others through the hardest parts of our learning processes.
\n\n\n\nJosepha Haden Chomphosy 03:07
\n\n\n\nThe process of helping people to learn new technologies relies not only on your hard-won expertise but also on the belief that the future is worth fighting for. Enabling someone’s success is an investment in the future and investment for that person or for WordPress or your community. All investments are welcome here.
\n\n\n\nJosepha Haden Chomphosy 03:28
\n\n\n\nFortunately, table stakes are just that you care. And speaking of future investments, the second focus is open source alternatives for site building necessities. So things like images, forms, stores, themes, etc. It literally just things you need to build a site. I would like to start by saying that I am completely aware of the fact that 99% of WordPress users will never care about open source freedoms and philosophies in the same way that WordPress maintainers and contributors care about open source freedoms and philosophies.
\n\n\n\nJosepha Haden Chomphosy 04:04
\n\n\n\nYou could substitute the name of any other open source project right there, and the statement would still be true. And yet, I will always believe that people should have the rights and freedoms that open source brings to them even if they do not know they are there. And so it makes all the sense in the world to me that as a project and open source community, we should strive to make choosing Open Source as easy as possible.
\n\n\n\nJosepha Haden Chomphosy 04:33
\n\n\n\nAnd finally, open source stewardship is one of the focuses for this year. This one is obviously about supporting open source as a concept and maintaining WordPress as a project. But I also think that it is relevant to our current global circumstances. Open Source suddenly became very visible to the public eye last year following the Log4J vulnerability, and ever since then, I’ve been hearing consistent concern over how We make sure that WordPress is sustainable moving into the future. Fortunately, this is a topic that’s near and dear to my heart. And I have been delighted to see so many community members bringing that conversation to the forefront.
\n\n\n\nJosepha Haden Chomphosy 05:14
\n\n\n\nThere is a lot that is done in the WordPress project to keep us from the tragedy of the commons. But that work honestly never ends. Not only does it not end, but as we get bigger, there is more and more that we can and should be doing to keep us around for the long term. And, of course, for the keen readers of my posts, there’s a bonus focus.
\n\n\n\nJosepha Haden Chomphosy 05:39
\n\n\n\nThe bonus focus is, of course, that WordPress turns 20 years old next year. This year, we will also be seeing some preparatory work for that major milestone as well.
\n\n\n\nJosepha Haden Chomphosy 05:56
\n\n\n\nSo that brings us today to our small list of big things. There is a redesign of the News Page coming. We’ve been talking about this over on make.wordpress.org/design for a bit since like June of last year or something. But it’s coming in the next few weeks. I’ll share a link to the GitHub repo in case anyone has any specific things that they see as they are reading through all of our many news stories that come out on that particular page. I think it’s beautiful, and I’m very excited to take a look at it.
\n\n\n\nJosepha Haden Chomphosy 06:30
\n\n\n\nThe second thing is that planning is underway for WordPress 6.0; that release that we’re doing in May. I’ll add the project page link to the show notes. I’ve had a few raised hands for that release squad. But if you’re interested in participating in the release, I encourage you to keep an eye out on make.wordpress.org/core for updates and any news about how to get involved.
\n\n\n\nJosepha Haden Chomphosy 06:53
\n\n\n\nAnd my third thing is actually that, in general, there are a lot of opportunities to contribute right now. There are discussions about projects, goals, and dreams happening all over the place. I’ll link in the show notes below the unofficial project “firehose” where you can see all the headlines and quickly find discussions that might be interesting to you.
\n\n\n\nJosepha Haden Chomphosy 07:18
\n\n\n\nAnd that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12176\";s: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: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:39:\"The Month in WordPress – January 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2022/02/the-month-in-wordpress-january-2022/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Feb 2022 19:41:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12180\";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:335:\"There are a few significant moments in the history of the WordPress project. January 2022 is one of them, with the release of WordPress 5.9! But that’s not all. Read on to learn more about the latest updates and achievements from the community. WordPress 5.9 Joséphine is here Meet WordPress 5.9 Joséphine. Named in honor […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Anjana Vasan\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:12751:\"\nThere are a few significant moments in the history of the WordPress project. January 2022 is one of them, with the release of WordPress 5.9! But that’s not all. Read on to learn more about the latest updates and achievements from the community.
\n\n\n\n\n\n\n\n
WordPress 5.9 Joséphine is here
\n\n\n\n![](\"https://lh3.googleusercontent.com/Iq09sZdu0Npal6XWBF6Bbfqb8AWizWVPCUtCqxgU4T-1E3uWM1bmZ7cDEHA0RJlEaFTPN5jAAXwHfx-x52rIC2Gac55j96fhUSdFlHyEmFtooRM9_NmuLyRJ-_ujotnKAAYzBEBh\")
Meet WordPress 5.9 Joséphine. Named in honor of the acclaimed jazz singer, Joséphine Baker, this is one of the much-awaited releases. Version 5.9 brings full site editing to WordPress, among other exciting updates! Download WordPress 5.9 and try the new features!
Check out the WordPress 5.9 Field Guide to learn more. Lastly, everyone’s invited to participate in a retrospective of the WordPress 5.9 Joséphine release!
\n\n\n\nAre you interested in contributing to WordPress core? Join the #core channel, follow the Core Team blog, and check out the team handbook. Also, don’t miss the Core Team’s weekly developer chat on Wednesdays at 8 PM UTC.
Gutenberg releases: Versions 12.3, 12.4, and 12.5 are here
\n\n\n\nThe Core Team launched three new versions of Gutenberg since last month’s edition of the Month in WordPress.
\n\n\n\n- Gutenberg 12.5 brings global styles variations and Query Loop block enhancements, along with the Code Editor view to the Side Editor. Moreover, inserting new buttons is now easier than ever!
- Gutenberg 12.4 was released on January 19, 2022. This version includes accessibility improvements, suggestions for assigning categories, keyboard shortcuts for the Site Editor, and more.
- Gutenberg 12.3 was released on January 5, 2022. This release brings new blocks, like the Author Name, Comments Next Page, and Comments Previous Page blocks, and many other cool updates!
\n\n\n\nWant to get involved in developing Gutenberg? Follow the Core Team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Make WordPress Slack. Follow the #gutenberg-new tag for details on the latest updates.
Team updates: Proposals, announcements, and more for 2022
\n\n\n\n- Executive Director Josepha Haden shared a proposal on 2022 major release timing.
- In the latest episode of WP Briefing, Josepha Haden Comphosy reviews the three major areas of focus for the WordPress project in 2022. She also shared the big-picture goals for 2022.
- The Core Team made a proposal regarding proper attributions for contributions to WordPress on GitHub. Although the proposal has since then been withdrawn, it’s still a discussion and comments are welcome.
- Check out the preliminary roadmap for WordPress 6.0 (Gutenberg Phase Two).
- Core Team members proposed improvements to the Core Editor chat agenda and format.
- The Accessibility Team made some major goal proposals for WordPress 6.0.
- The Polyglots Team shared a proposal for a milestone template for polyglots locale teams.
- The January 2022 edition of the Polyglots monthly newsletter is out!
- The Community Team shared an open invitation for the Diverse Speaker Training group Zoom call.
- Although the WordPress Photo Directory hasn’t fully launched yet, you can now submit your images. You can also contribute in other ways, as there’s currently a call for volunteers.
- Openverse has now a redesigned user interface and includes support for audio files. Check out this post to learn what’s new.
- The Community Team will be hosting open discussion sessions to collaborate on its goals for 2022.
- The January 2022 edition of the Meetup Organizer Newsletter was published.
- The Community Team shared a proposal for mandatory safety measures for in-person WordPress events taking place this year.
- The Training Team published its February 2022 Team Sprint.
\n\n\n\nTake the course on Learn WordPress to learn about the full site editing features in WordPress 5.9! Also, help spread the word about social learning spaces on Twitter!
Feedback/Testing requests: Share your thoughts on WordPress 5.9 Joséphine
\n\n\n\n- There’s currently a call for testing WordPress for Android 19.1 and iOS 19.1, along with Android 19.0 and iOS 19.0.
\n\n\n\nShare your feedback on the release of WordPress 5.9 Joséphine.
WordCamp Europe 2022 wants volunteers, photographers and media partners
\n\n\n\n- WordCamp Birmingham, Alabama has been postponed until April or May.
- The WordPress Foundation published a post explaining more about the nonprofit’s mission and why it exists.
- Don’t miss the following upcoming WordCamps:
![\"??\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f1e8-1f1ff.png\")
WordCamp Prague, Switzerland on February 26, 2022 (online)- WordCamp Genève, Switzerland on April 9, 2022 (in person)
- WordCamp Athens, Greece between April 9 and 10, 2022 (in person)
- WordCamp Vienna, Austria from April 23 to 24, 2022 (in person)
- WordCamp Europe in Porto, Portugal from June 2 to 4, 2022 (in person)
- WordCamp US in San Diego, CA USA from September 9-11, 2022 (in person)
\n\n\n\nWordCamp Europe 2022 opened a new call for volunteers, photographers, and media partners!
\n\n\n\n
Have a story that we could include in the next ‘Month in WordPress’ post? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to January 2022’s Month in WordPress: @anjanavasan @harishanker @rmartinezduque @lmurillom @webcommsat and @nalininonstopnewsuk
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"12180\";s: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: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:29:\"WordPress 5.9 “Josephine”\";s:7:\"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:45:\"https://wordpress.org/news/2022/01/josephine/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 25 Jan 2022 16:17: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: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.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12089\";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:90:\"WordPress 5.9 is available thanks to more than 600 contributors who helped make it happen.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:64524:\"\n![\"\"](\"https://i1.wp.com/wordpress.org/news/files/2022/01/5-9-inline-v2.png?resize=1024%2C694&ssl=1\")
Welcome to Joséphine!
\n\n\n\nIntroducing 5.9, “Joséphine”. Named in honor of acclaimed international jazz singer Joséphine Baker, this latest, most versatile WordPress release is here: download it or update it directly from your dashboard.
As a lifelong civil rights campaigner, Joséphine Baker believed that all people could live in harmony together, just as different instruments in a jazz band blend together to make a whole piece. Turn on a playlist from your favorite music service and enjoy her famous renditions of “You are the greatest love”, “Sans Amour”, and “Love is a Dreamer” as you discover all the features of this brand-new WordPress release.
\n\n\n\n
Full site editing is here.
\n\n\n\nIt puts you in control of your whole site, right in the WordPress Admin.
\n\n\n\n\n\n\n\n![\"\"](\"https://i2.wp.com/wordpress.org/news/files/2022/01/5-9-release-1.png?resize=1204%2C903&ssl=1\")
Say hello to Twenty Twenty-Two.
\n\n\n\nAnd say hello to the first default block theme in the history of WordPress. This is more than just a new default theme. It’s a brand-new way to work with WordPress themes.
\n\n\n\nBlock themes put a wide array of visual choices directly in your hands, from color schemes and font combinations to page templates and image filters, all from the Site Editor. So in one place, you can give Twenty Twenty-Two the same look and feel as your organization’s other materials—or take your site’s look in another direction.
\n\n\n\nYou already have the Twenty Twenty-Two theme—it came installed with WordPress 5.9. You will find it with your other installed themes.
\n\n\n\n\n\n\n\n![\"\"](\"https://i2.wp.com/wordpress.org/news/files/2022/01/5-9-release-2.png?resize=1204%2C903&ssl=1\")
Your personal paintbox awaits
\n\n\n\nTwenty Twenty-Two is not the only theme built for full site editing. More block themes are in the Themes directory, and the number will grow.
\n\n\n\nWhen you use any of those new themes, you no longer need the Customizer. Instead, you have all the power of the Styles interface inside the Site Editor. Just as in Twenty Twenty-Two, you build your site’s look and feel there, with the tools you need for the job in a fluid interface that practically comes alive in your hands.
\n\n\n\n\n\n\n\n![\"\"](\"https://i0.wp.com/wordpress.org/news/files/2022/01/5-9-release-3.png?resize=1204%2C903&ssl=1\")
The Navigation block
\n\n\n\nBlocks come to site navigation, the heart of user experience.
\n\n\n\nThe new Navigation block gives you the power to choose: an always-on responsive menu or one that adapts to your user’s screen size. And your choices are remembered! In 5.9, the block saves menus as custom post types, which get saved to the database.
\n\n\n\n\n\n\n\nMore improvements and updates
\n\n\n\nDo you love to blog? New tweaks to the publishing flow help you say more, faster.
\n\n\n\n\n\n\n\n![\"\"](\"https://i1.wp.com/wordpress.org/news/files/2022/01/5-9-release-5.png?resize=1204%2C903&ssl=1\")
Better block controls
\n\n\n\nWordPress 5.9 features new typography tools, flexible layout controls, and finer control of details like spacing, borders, and more—to help you get not just the look, but the polish that says you care about details.
\n\n\n\n\n\n\n\n![\"\"](\"https://i2.wp.com/wordpress.org/news/files/2022/01/5-9-release-4.png?resize=1204%2C903&ssl=1\")
The power of patterns
\n\n\n\nThe WordPress Pattern Directory is the home of a wide range of block patterns built to save you time and add to your site’s functionality. And you can edit them as you see fit. Need something different in the header or footer for your theme? Swap it out with a new one in a few clicks.
\n\n\n\nWith a nearly full-screen view that draws you in to see fine details, the Pattern Explorer makes it easy to compare patterns and choose the one your users need.
\n\n\n\n\n\n\n\n![\"\"](\"https://i2.wp.com/wordpress.org/news/files/2022/01/5-9-release-6.png?resize=1204%2C903&ssl=1\")
A revamped List View
\n\n\n\nIn 5.9, the List View lets you drag and drop your content exactly where you want it. Managing complex documents is easier, too: simple controls let you expand and collapse sections as you build your site—and add HTML anchors to your blocks to help users get around the page.
\n\n\n\n\n\n\n\n![\"\"](\"https://i2.wp.com/wordpress.org/news/files/2022/01/5-9-release-7.png?resize=1204%2C903&ssl=1\")
A better Gallery block
\n\n\n\nTreat every image in a Gallery Block the same way you would treat it in the Image Block.
\n\n\n\nStyle every image in your gallery differently, or make them all the same, except for one or two. Or change the layout with drag-and-drop.
\n\n\n\n\n\n\n\n\n\n\n\n
WordPress 5.9 for developers
\n\n\n\nTheme.json for child themes
\n\n\n\nIn 5.9, theme.json supports child themes. That means your users can build a child theme right in the WordPress Admin, without writing a single line of code.
\n\n\n\nThis dev note has all the details. Take a look!
\n\n\n\nBlock-level locking
\n\n\n\nNow you can lock any block (or a few of them) in a pattern, just by adding a lock attribute to its settings in block.json—leaving the rest of the pattern free for users to adapt to their content.
\n\n\n\nMultiple stylesheets in a block
\n\n\n\nNow you can register more than one stylesheet per block, which lets a given block load only the styles its markup requests, and not a whole sheet. Read the details in this dev note.
\n\n\n\nA refactored Gallery Block
\n\n\n\nThe changes to the Gallery Block listed above are the result of near-complete refactor. Have you built a plugin or theme on the Gallery Block functionality? Be sure you read this dev note. It tells you what you need to do for compatibility.
\n\n\n\n\n\n\n\n\n\n\n\n
Learn more about the new features in 5.9
\n\n\n\nWant to dive into 5.9 but don’t know where to start? Check out this free course about Simple Site Design from Learn WordPress. There are a variety of learning materials including short how-to video tutorials and resources on new features in WordPress 5.9, with much more planned.
\n\n\n\n\n\n\n\n\n\n\n\n
Check the Field Guide for more!
\n\n\n\nCheck out the latest version of the WordPress Field Guide. It has lots of useful information with links to detailed developer notes to support you building in WordPress for everyone you serve. WordPress 5.9 Field Guide.
\n\n\n\n\n\n\n\nThe Squad
\n\n\n\nThe WordPress 5.9 release was led by Matt Mullenweg, and supported by this highly enthusiastic release squad:
\n\n\n\n- Release Lead: Matt Mullenweg
- Core Tech and Release Coordinator: Tonya Mork
- Triage Leads: Jb Audras and Ahmed Chaion
- Editor Tech: Robert Anderson and George Mamadashvili
- Theme Leads: Kjell Reigstad and Jeff Ong
- Technical Writer: Jonathan Bossenger
- Documentation Leads: Marcus Kazmierczak and Milana Cap
- Marketing & Communications Leads: Mary Baum, Abha Thakor, and Josepha Haden Chomphosy
- Test Leads: Piotrek Boniu and Anne McCarthy
WordPress 5.9 also reflects the hard work of 624 generous volunteer contributors. Collaboration occurred on 370 tickets on Trac and more than 1900 pull requests on GitHub.
\n\n\n2linctools · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · abesell132 · Abha Thakor · acosmin · Adam - WPMU DEV Support · Adam Bosco · Adam Morgan · Adam Silverstein · Adam Zielinski · Addie · Adil Ali · aduth · Aezaz Shekh · Ahmed Chaion · ajotka · Akash Soni · Aki Hamano · Akira Tachibana · Alain Schlesser · Alan Jacob Mathew · Albert Juhé Lluveras · Alex Concha · Alex Lende · Alexandru Vornicescu · alexeydemidov · Alexis Lloyd · alexstine · AlGala · aliakseyenkaihar · allilevine · almendron · Amanda Riu · Anand Upadhyay · André · Andrea Fercia · Andrei Draganescu · Andrew Nacin · Andrew Nevins · Andrew Ozz · Andrew Serong · André · Andy Fragen · Andy Peatling · Andy Schmidt · andynick · Angelika Reisiger · Anjana Vasan · Ankit K Gupta · Ankit Panchal · Anne McCarthy · Anthony Burchell · Anthony Eden · Anthony Ledesma · Anton Vlasenko · Antonis Lilis · Antony Booker · arena · Ari Stathopoulos · ArteMa · Arthur Chu · Ashfame · Ayesh Karunaratne · baelx · Bartlomiej · Beatriz Fialho · Beau Lebens · Beda · Ben Dwyer · Benachi · benitolopez · Benjamin Denis · Benjamin Gosset · benjamin.anakena · Bernhard Reiter · Bijay Yadav · BinaryKitten · binarymoon · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · BlogAid · bobbingwide · Boone Gorges · Brad Jorsch · Brad Parbs · Bradley Taylor · Brandon Kraft · bravokeyl · Brennan Goewert · Brian Gardner · Brian Richards · bronsonquick · Bruno Ribaric · Brylie Christopher Oxley · Caleb Burks · calebwoodbridge · carepsules · Carike · Carlos Bravo · Carlos Garcia · Carolina Nymark · cdyerkes · Ceyhun Ozugur · Chad Chadbourne · Channing Ritter · Chiaki · Chintan hingrajiya · Chip Snyder · Chloe Bringmann · Chouby · Chris Klosowski · Chris Van Patten · chriscct7 · Christian Tamayo · Christina Workman · Christopher Churchill · clucasrowlands · Colin Stewart · Collieth Clarke · Collins Agbonghama · Copons · Corey · Cory Hughart · Courtney Robertson · craigfrancis · Crisoforo Gaspar · Csaba (LittleBigThings) · Dávid Szabó · Daisy Olsen · Damon Cook · Dan Farrow · Dan Soschin · Daniel Bachhuber · Daniel Post · Daniel Richards · Daniel Shaw · danieldudzic · Daniele Scasciafratte · darerodz · Daria · Daschmi · datagutten · datainterlock · Dave Page · David Anderson · David Baumwald · David Biňovec · David Calhoun · David Gwyer · David Herrera · David Kryzaniak · David Mosterd · David Rozando · David Ryan · David Smith · davidwebca · Deb Nath Utpol · Debabrata Karfa · Deepak Lalwani · Denis Yanchevskiy · Denis Žoljom · Dennis Snell · Dhanendran · dhusakovic · DiedeExterkate · Dilip Bheda · Dion Hulse · dlt101 · Dominik Schilling · donmhico · Donna Botti · dontgo2sleep · Doug Wollison · dpegasusm · Dr. Ronny Harbich · dratwas · Drew Jaynes · drosmog · dustinrue · ecotechie · Eddy · ehtis · EkoJR · Ella van Durpe · Emmanuel Hesry · empatogen · Enchiridion · Enej Bajgorić · Enrique Sánchez · erayalakese · Eric Malalel · Erick Hitter · Erik Betshammar · etoledo · Evan Mullins · Fabian Kägy · Fabian Todt · Faisal Alvi · fedepia · Felipe Elia · Felipe Santos · Felix Arntz · Florian TIAR · FPCSJames · fperdaan · Francesca Marano · Francesco · gadhiyaravi · Gal Baras · Garrett Hyder · Gary Jones · Gary Pendergast · gazchap · generosus · Gennady Kovshenin · George Hotelling · George Mamadashvili · George Stephanis · Gerardo Pacheco · Gilbert Pellegrom · Glen Davies · goldsounds · Govind · Grant M. Kinney · Greg Rickaby · Greg Ziółkowski · Guillaume TURPIN · Héctor Prieto · Hans-Christiaan Braun · haosun · Hareesh · Hasanuzzaman · Hauwa Abashiya · Haz · Henry Wright · herbmiller · Herm Martini · Herre Groen · Hilay Trivedi · hirofumi2012 · Hitendra Chopda · Hossein Farahani · htmgarcia · Hudson Atwell · Hugh Lashbrooke · hugod · Ian Belanger · Ian Dunn · ianatkins · ianhayes94 · ianmjones · Ignat Georgiev · Igor Benic · ilovecats7 · infected · Ipstenu (Mika Epstein) · ironprogrammer · Isaac · Isabel Brison · ismaeld · itsamoreh · Iulia Cazan · J.D. Grimes · Jack Reichert · Jake Spurlock · jakub.tyrcha · Jam Viet · James Huff · James Koster · Jan Thiel · janw.oostendorp · Jason Johnston · Jason R. Johnston · Javier Arce · Javier Casares · Jay Upadhyay · Jean-Baptiste Audras · Jean-Philippe · Jeff Bowen · Jeff Ong · jeffpaul · Jenny Dupuy · Jeremy Felt · Jeremy Herve · Jeremy Scott · Jeremy Yip · Jesús Amieiro · Jesper van Engelen · Jessica Lyschik · Jignesh Nakrani · Joe Dolson · Joe McGill · joegasper · Joel James · Joen Asmussen · John Blackbourn · John Espiritu · John Godley · John James Jacoby · john zenith · JohnRDOrazio (CLPTE) · Jonathan Bossenger · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Joost de Valk · Jorge Costa · Jos Klever · Joseph Dickson · Josepha Haden · Joy · jsnajdr · Juan Ruitiña · JuanMa Garrido · Juhi Saxena · Juliette Reinders Folmer · Junaid Bhura · Junko Nukaga · Justin Ahinon · Justin DoCanto · Justin Tadlock · K. Adam White · KafleG · Kai Hao · kallookoo · Kalpesh Akabari · kaneva · Kapil Paul · Kelly Choyce-Dwan · Kelly Hoffman · keoshi · Keramot UL Islam · kero · Kerry Liu · Kevin Fodness · keyur5 · Kharis Sulistiyono · Kjell Reigstad · Knut Sparhell · Koen Van den Wijngaert · Konstantin Obenland · Konstantinos Xenos · kurudrive · kwisatz · Kyle Nel · KZeni · lalitjalandhar · laurelfulford · Laxman Prajapati · leemon · Lena Morita · leogermani · Liam Gladdy · liammitchell · Linkon Miyan · linux4me2 · Loïc Antignac · Loran A. Rendel · Lucas Karpiuk · lucasw89 · lucatume · Luis Felipe Zaguini · Luke Carbis · Luke Cavanagh · Lukman Nakib · luovalabs · lynk · M Asif Rahman · Madalin Gorbanescu · Madison · Maggie Cabrera · Mai · Malae · malthert · manfcarlo · Manisha Makhija · Manzoor Wani · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marek Hrabe · Marin Atanasov · Marius L. J. · Mark-k · Mary Baum · Mateus Machado Luna · Matias Ventura · Matt · Matt Chowning · Matt Mullenweg · Matt Wiebe · mattoakley · Mauriac AZOUA · Max · MaxD · Maxime Culea · mclaurent · MEDUSOR · Meg Phillips · Meher Bala · Mel Choyce-Dwan · mgol · Micah Wood · Michael Adams (mdawaffe) · Michael Beckwith · Michael Burridge · Michael Nelson · Michal Czaplinski · Michel - xiligroup dev · Miguel Fonseca · mikaelmayer · Mike Jolley (a11n) · Mike Schroder · Milan Dinić · Milana Cap · Minal Diwan · mjaschen · mjulian7 · mmxxi · moch11 · Mohammad Rockeybul Alam · Monika Rao · moto hachi · mqudsi · mreishus · mrjoeldean · mtoensing · Muhammad Arslan · Muhammad Faizan Haidar · Mukesh Panchal · Musab Shakeel · Mustaque Ahmed · Nadir Seghir · Nalini Thakor · Namith Jawahar · Naoko Takano · NateWr · Ned Zimmerman · NettSite · Nicholas Garofalo · Nick Diego · Nick Halsey · nickcernis · Nico · Nidhi Jain · nidhidhandhukiya · Niels Lange · Nik Tsekouras · Nikhil Chavan · nlpro · ockham · Olga Gleckler · Oliver Campion · Omar Alshaker · Omar Reiss · opr18 · Outzen Larkin · Ov3rfly · ovann86 · ovidiul · Paal Joachim Romdahl · Pablo Honey · page-carbajal · palmiak · Pankaj Mohale · Paolo L. Scala · Pascal Birchler · Patrick Boehner · Paul Bearne · Paul Biron · Paul Bunkham · Paul Kevin · Paul Schreiber · Paul Von Schrottky · Paulo Pinto · Pavlo · pbking · Pedro Mendonça · pepe · Petar Ratković · Peter Smits · Peter Wilson · Petter Walbø Johnsgård · pgpagely · Phil Johnston · Philip Jackson · Pierre Gordon · Pieterjan Deneys · Piotrek Boniu · Pooja Derashri · powerbuoy · praem90 · Pramod Jodhani · Presskopp · presstoke · procodewp · psealock · psufan · pwtyler · Rachel Baker · Radixweb · Rafi Ahmed · Rahul Mehta · ralucastn · Ramon Ahnert · ramonopoly · ravipatel · Rehan Ali · Renatho (a11n) · retrofox · Riad Benguella · Rian Rietveld · Rich Tabor · Richard B. Kreckel · Richard Foley · richards1052 · Rick Curran · Rishabh Budhiraja · Riyadh Ahmed · rmartinezduque · Robert Anderson · robertght · robtarr · Rodrigo Arias · Rohan Rawat · Rohan Sharma · Rolf Siebers · Ronak Ganatra · Roxy Kohilakis · Rufus87 · Ruslan · rviscomi · Ryan Welcher · S Page · Sébastien SERRE · Sören Wrede · Sabbir Hasan · Sabri Bouchaala · Safirul Alredha · Samir Shah · Samuel Wood (Otto) · Sandip Mondal - a11n · Sanket Chodavadiya · Sarah Norris · sarayourfriend · Sathiyamoorthy V · savicmarko1985 · Sayedul Sayem · Scott Buscemi · scribu · Sean McMillan · Sebastian Pisula · Segayuu · Sergey Biryukov · Sergio Cinos · SergioEstevao · Shaharyar Afzal · shaunandrews · Shazahanul Islam Shohag · shimon246 · Shital Marakana · Shiva Poudel · siddharth · Siddharth Thevaril · siliconforks · simonhammes · Siobhan · Siobhan · sirreal · sjlevy · skunkbad · Smit Rathod · snapfractalpop · Sourov Roy · spytzo · ssergei · stacimc · Stefano Minoia · Stefanos Togoulidis · Stephen Bernhardt · Stephen Edgar · Stephen Rider · Steve Dufresne · Steve Henty · stevegs · Storm Rockwell · Sven Wagener · Sybre Waaijer · Synchro · szaqal21 · Taco Verdonschot · Takahashi Fumiki · Tammie Lister · Tara King · Tarei King · Team Staatic · Tellyworth · terraling · Terri Ann · theMikeD · Thierry Muller · Thijs Hulshof · Thimal Wickremage · thisiswilliam · Thomas Patrick Levy · Tim Lappe · Tim Nolte · Timothy Jacobs · titsmaker · tjcafferkey · tmatsuur · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tomek · Tomoki Shimomura · Tony G · Tony Tahmouch · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Tracy · Travis Northcutt · tubys · Tung Du · twstokes · Udit Desai · Umesh Gupta · Venkat Raj · versusbassz · verybg · Vicente Canales · Viktor Szépe · Vishit Shah · Vlad T · Vondelphia.com · vortfu · wb1234 · WebMan Design | Oliver Juhas · Wes Theron · Weston Ruter · WFMattR · Will Skora · William Earnhardt · williampatton · wojsmol · woodyhayday · wp_kc · wpnomad a11n · wpsoul · wpweaver · Yagnik Sangani · Yui · Yunus Ertuğrul · Yvette Sonneveld · Zebulan Stanphill · zoiec
\n\n\n\nBy release day, 71 locales had translated 90 percent or more of WordPress 5.9 in their language. Community translators are hard at work ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in 205 languages.
\n\n\n\nMany thanks to all of the community volunteers who contribute in the support forums. They help to answer questions from people across the world. The success of releases, from the first one in 2003, owes much to the efforts of the support contributors.
\n\n\n\nIf contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to Make WordPress website and find out the latest plans on 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:5:\"12089\";s: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, 30 May 2022 23:28:10 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:\"Mon, 30 May 2022 22:17:52 GMT\";s:4:\"link\";s:63:\"What is the Post and Page Builder by BoldGrid?
\nThe Post and Page Builder is an intuitive drag and drop editor plugin and the easiest way to create and edit pages for any theme. Whether you are new to WordPress or consider yourself a pro, BoldGrid solutions will make your WordPress life better. Stop dealing with site-breaking shortcodes and theme restricted editors. You are going to love just how fast and easily you can create beautiful websites now.
\nTry out the BoldGrid Demo on Cloud WordPress to see for yourself!
\n\nFeatures
\n- \n
- Drag and Drop Editing – Create simple or complex layouts with our unique editing experience \n
- BoldGrid Blocks – Hundreds of professional layout designs to work from \n
- 100% Mobile-friendly – Responsive layouts and controls to change the design per device \n
- Google Fonts – Change font family, font size, font color, letter spacing, line height and more \n
- Theme Compatibility – Our WordPress Page Builder is designed to work with any WordPress Theme \n
- Custom Backgrounds – Add background images, gradient backgrounds, patterns, overlays, and background colors \n
- Fast and Free Support – Growing Community and knowledge base \n
- Animations – Add effects as the user scrolls down the page with Animate.css or background parallax scroll effects \n
- Advanced Controls – Add margin, padding, box shadows, borders, alignment and more to almost any element \n
- Bootstrap Grid – Drag and drop controls for bootstrap rows and columns elements \n
- Add Custom CSS Classes – Complete control over any element \n
- Clean, Simple Markup – Easily create a professionally coded template without experience \n
- Google Maps – Embed and customize maps into your post or page \n
- Web Components – High quality reusable and customizable HTML elements \n
- Font Awesome Icons – Insert and customize any Font Awesome icons \n
- CSS Grid – Full width, column and row based layouts \n
- Image Editing – Apply image filters and automatically crop images \n
- Button Designs – Fully customizable button designs \n
- Custom Post Types – Save and reuse full page layouts or BoldGrid Block designs \n
- WordPress Editor Integration – Integrated into TinyMCE so you can keep the same workflow \n
- No Need for Shortcodes! – Faster page loads by saving your custom HTML5 elements \n
Additional Features when used with other BoldGrid plugins:
\n- \n
- Dozens of free layout templates \n
- Integrated with professional image banks \n
- Contact Forms \n
- On-page SEO recommendations for targeted search phrase \n
Visit our website to learn more about additional BoldGrid plugins to further improve your WordPress experience!
\nPeople Love BoldGrid
\n“It’s really the perfect starting point for just about any web project, allowing users to get their site up and running in very short time. ” – Digital.com
\n“BoldGrid is a great extension to WordPress that will make my job a lot easier and faster while creating custom layouts and pages.” – Webhostingmedia.net
\n“Well, I have seen many site builders but this is the only one that provides so many features.” – Woblogger.com
\nA Post and Page Builder That Works With Your Theme and Plugins
\nThe Post and Page Builder by BoldGrid is designed to work with almost any WordPress theme. Add it to your existing website today, or try a BoldGrid theme for your new website. Alternatively, consider upgrading and using the powerful BoldGrid framework theme (available in Premium subscription) as an excellent time saver for agencies and developers.
\nA Post and Page Builder Stuffed With Pre-Designed Templates & Blocks
\nCreate layouts and pages faster and easier than ever with Blocks by BoldGrid. Blocks are pre-built page sections consisting of various layouts of rows and columns prepopulated with content that can be edited visually or with HTML and CSS. Blocks utilize a wide variety of content that can be completely customized to fit your needs such as icons, buttons, free and premium images, font packs, and more.
\nA Post and Page Builder That Is Faster Than The Rest
\nThe Post and Page Builder by BoldGrid is designed to create pages that load fast. BoldGrid ditches shortcodes in favor of clean markup that can be served quickly. That also means BoldGrid code is easy to assess and customize.
\nComing Soon / Maintenance Page
\nGreat for making “under construction” or “coming soon” pages. You can create a simple page within minutes by using free professionally designed WordPress Blocks.
\nBootstrap WYSIWYG Post & Page Builder for WordPress
\nOur drag and drop system is built on the Bootstrap Grid. You can drag columns, rows, and containers around your pages to make quick updates to pages. Advanced CSS controls allow you to make pixel perfect designs.
\nCreate Custom Color Palette
\nChoose your brand’s colors and we’ll help your design stay unified. Our unique color palette system is built with SASS and allows you to change all the colors on your site. You don’t have to choose from a few presets anymore!
\n\";s:12:\"installation\";s:679:\"Minimum Requirements
\n- \n
- PHP version 5.4 or greater \n
- WordPress 4.7 or greater \n
From within WordPress
\n- \n
- Visit ‘Plugins > Add New’ \n
- Search for ‘Post and Page Builder by BoldGrid’ \n
- Activate Post and Page Builder from your Plugins page. \n
Manually
\n- \n
- Upload the entire post-and-page-builder folder to the /wp-content/plugins/ directory. \n
- Activate the plugin through the Plugins menu in WordPress. \n
You will find a ‘Post and Page Builder’ menu in your WordPress admin panel and find most features within the
\nWordPress Editor.
\n
If you have any questions on getting started with the BoldGrid Post and Page Builder, please visit our Getting Started Guide.
\nWe also suggest joining our Team Orange User Group community for free support, tips and tricks.
\n
Yes; the Post and Page Builder is compatible with any theme. We recommend using BoldGrid themes which provide additional features and are optimized for use with the Post and Page Builder.
\n\n\n
Bugs can be reported either in the WordPress support forum or in the BoldGrid Support Center.
\n\n\n
The Post and Page Builder is open source software. Join in on our GitHub repository.
\n\n\n\";s:9:\"changelog\";s:26747:\"1.19.1
\n- \n
- Update: Added filters to premium urls. \n
- Update: Updated Boldgrid/Library to 2.13.7 \n
1.19.0
\n- \n
- New Feature: Add Inner Borders on Columns and Column Shapes #311 \n
- New Feature: Allow for Full Width Rows to work with row backgrounds #388 \n
- New Feature: Add Responsive Alignment Controls #375 \n
- Bug Fix: Fix z-index for dropdown menus in FWRs #389 \n
- Bug Fix: Button gets deleted when trying to replace the text #282 \n
1.18.0
\n- \n
- New Feature: [FEATURE] Add drag and drop support for col-lg #257 \n
- New Feature: Add Hover Boxes to Nested Rows #346 \n
- New Feature: Add ‘Full Width Row’ Control #359 \n
=1.17.1=
\n* Bug Fix: Custom Classes option missing in 1.17.0 #357
\n* Bug Fix: Cannot work with icons #356
1.17.0
\n- \n
- New Feature: Ability to use multiple colors in headings #260 \n
- New Feature: Add wave / swirl designs between sections or as column separators [#306] (https://github.com/BoldGrid/post-and-page-builder/issues/306) \n
- New Feature: Add Image Backgrounds on Column Shapes #304 \n
- New Feature: Hover Boxes #297 \n
- Feature Update: Update PPB and Crio Google Fonts #276 \n
1.16.0
\n- \n
- New Feature: Include Custom Primary & Secondary buttons in button selector \n
- Bug Fix: Block Library blocks do not load “below the fold” #174 \n
1.15.3
\nRelease Date: January 24, 2022
\n* Bug Fix: WP 5.9 – difficulty dragging and dropping blocks on Add Block screen #324
1.15.2
\nRelease Date: December 28, 2021
\n* Bug Fix: Fatal Error implode(): Argument #1 ($pieces) must be of type array #322
1.15.1
\nRelease Date: December 22, 2021
\n* Bug Fix: MCE is “squished” when additional controls are added #305
\n* Bug Fix: fixed console warning in PPB when loading submenus in Custom Page Headers.#303
\n* Enhancement: Add Menu Direction options.#313
1.15.0
\nRelease Date: November 17, 2021
\n* New Feature: Full Screen Editing.
1.14.2
\nRelease Date: September 14th, 2021
\n- \n
- Bug Fix: Visual bug when adding links to text #139 \n
- Bug Fix: Review prompt prevents admins from deleting other user accounts #192 \n
- Bug Fix: Google Map option in Add Media #198 \n
1.14.1
\nRelease Date: August 26th, 2021
\n- \n
- Bug Fix: Allow PPB visual editing tools to load for Author and Contributor level user roles #197 \n
- Bug Fix: Render the weForms form in the editor #199 \n
- Bug Fix: Fatal Error fetching Saved Blocks #195 \n
- Bug Fix: Gray background on panels is same as gray in default palette #200 \n
- Bug Fix: Update ‘Add Block’ buttons to pass accessibility contrast #183 \n
1.14.0
\nRelease Date: December 17th, 2020
\n- \n
- New Feature: Added new components to support Crio Pro’s Custom Page Headers. \n
1.13.6
\nRelease Date: December 8th, 2020
\n- \n
- Fix: BoldGrid library loading issue. \n
1.13.5
\nRelease Date: December 8th, 2020
\n- \n
- Fix: WordPress 5.6 compatibility issues. \n
1.13.4
\nRelease Date: August 28th, 2020
\n- \n
- Fix: Issue causing editor selection to switch back to Post and Page Builder after loading WordPress Editor. \n
1.13.3
\nRelease Date: August 10th, 2020
\n- \n
- Fix: WP 5.5 – Issue with causing color picker to fail updating after selecting class color \n
1.13.2
\nRelease Date: July 27th, 2020
\n- \n
- Fix: Compatibility issues with php 7.4 \n
- Fix: Compatibility issues with WordPress 5.5 \n
1.13.1
\nRelesae Date: June 24th, 2020
\n- \n
- Update: Updated BoldGrid Library. \n
1.13.0
\nRelease Date: March 31st, 2020
\n- \n
- New Feature: Added template without header and footer. \n
1.12.2
\nRelease Date: February 19th, 2020
\n- \n
- Update: Updated BoldGrid Library. \n
- Update: Added premium component options for each component. \n
1.12.1
\nRelease Date: November 12th, 2019
\n- \n
- Fix: Compatibility issues with latest twentytwenty release. \n
1.12.0
\nRelease Date: November 11th, 2019
\n- \n
- Feature: Default editor styles now applied in post and page builder. \n
- Feature: Added button to remove background image. \n
- Feature: Shortcodes can now be edited from visual mode. \n
- Update: Horizontal lines now use div tag to prevent conflicts with themes. \n
- Update: Improved support for twentytwenty theme. \n
1.11.2
\nRelease Date: September 18th, 2019
\n- \n
- Update: Added premium links in menu, plugins page and settings page. \n
- Fix: Added composer hook for library build. \n
1.11.1
\nRelease Date: September 5th, 2019
\n- \n
- Update: Update BoldGrid Library – Dashboard Updates. \n
1.11.0
\nRelease Date: August 22nd, 2019
\n- \n
- Feature: Shortcodes now rendered in editor. \n
- Feature: 10 new Block designs. \n
1.10.6
\nRelease Date: August 1st, 2019
\n- \n
- Update: Update BoldGrid library version. \n
1.10.5
\nRelease Date: July 18th, 2019
\n- \n
- Fix: Compatibility with tinymce Advanced. \n
1.10.4
\nRelease Date: July 9th, 2019
\n- \n
- Update: Added a filter to disable buttons component. \n
1.10.3
\nRelease Date: May 21st, 2019
\n- \n
- Fix: Undefined constant warning logged \n
1.10.2
\nRelease Date: May 21st, 2019
\n- \n
- Fix: Child themes of BoldGrid themes not recognized \n
1.10.1
\nRelease Date: May 8th, 2019
\n- \n
- Update: Verbiage update within Custom Classes section \n
- Update: Update BoldGrid library version \n
- Fix: Section wrappers not deleted within add blocks \n
- Fix: Issue where animations not removed from column shapes \n
1.10.0
\nRelease Date: February 14, 2019
\n- \n
- Fix: Block preview size on theme twentynineteen \n
- Fix: ACF Plugin compatibility issue \n
- Update: Links to User community group \n
- Update: Intermittent feedback requests \n
1.9.2
\nRelease Date: December 11th, 2018
\n- \n
- Fix: Issue saving blocks from page builder interface \n
1.9.1
\nRelease Date: December 5th, 2018
\n- \n
- Fix: Automatic image cropping fails to open \n
1.9.0
\nRelease Date: December 4th, 2018
\n- \n
- New Feature: Users can now switch between editors \n
- New Feature: A default editor can be specified \n
- New Feature: Builder can be enabled on custom post types \n
- Update: Lengthened timeouts on block generating \n
1.8.1
\nRelease Date: November 21st, 2018
\n- \n
- Bug Fix: Deleting plugin caused issues with BoldGrid Library. \n
1.8.0
\nRelease Date: October 16th, 2018
\n- \n
- New Feature: Column and Row backgrounds are now supported \n
- New Feature: Add Components and Widgets \n
- New Feature: Upgraded typography controls \n
- New Feature: Layout component \n
- New Feature: Anchors have individual font control \n
- New Feature: Rows can be added from the section popover \n
- New Feature: Pre tags are now supported for drag and drop \n
- New Feature: Added BoldGrid Connect Page \n
- New Feature: Support for Premium Extension \n
- New Feature: Row resize pixel preview \n
- Update: A notice will be displayed if an incomplete Github version of the plugin is active. \n
- Update: Minimum PHP/WP Version changed to 5.4 and 4.7 respectfully. \n
- Update: After first time setup page template will update for current page. \n
- Bug Fix: Fix display issues when viewing saved blocks on BoldGrid Themes. \n
- Bug Fix: Duplicate fonts displayed within font selection. \n
- Bug Fix: Some theme fonts not available for selection. \n
- Bug Fix: Block alignment issues saving to front end. \n
- Bug Fix: Captions within blocks not translated when inserted. \n
1.7.4
\nRelease Date: May 17th, 2018
\n- \n
- Bug Fix: BoldGrid DropTab not visible after 4.9.6 update. \n
1.7.3
\nRelease Date: May 3rd, 2018
\n- \n
- Bug Fix: Some fonts not loaded into block previews. \n
- Bug Fix: Used blocks will now include fonts in previews. \n
1.7.2
\nRelease Date: April 2nd, 2018
\n- \n
- Bug Fix: Fixed display issues of Blocks when toggle back and forth between filters. \n
- Bug Fix: Introduction steps displayed on Save Block. \n
1.7.1
\nRelease Date: March 8th, 2018
\n- \n
- Bug Fix: Fixed compatibility issues on older WordPress Versions. \n
- Bug Fix: Fixed default category displayed for users with inspiration installs. \n
- Bug Fix: Typo in Connect Key prompt. \n
1.7.0
\nRelease Date: March 7th, 2018
\n- \n
- New Feature: Most elements now support animation controls. \n
- New Feature: CSS ID’s can now be specified via customization controls. \n
- New Feature: Users can now specify a Connect Key. \n
- New Feature: Support audio and video blocks in Blocks. \n
- New Feature: Shortcodes now display in block previews. \n
- New Feature: Blocks can now be requested by industry. \n
- New Feature: Blocks now display full height in previews. \n
- Bug Fix: Blockquote elements now have the text control available to them. \n
- Bug Fix: Warning thrown while listing posts in admin. \n
- Bug Fix: HEX input field missing from color picker. \n
- Bug Fix: Undo/Redo no longer change scroll position. \n
- Bug Fix: Getting started displayed after switching to text tab. \n
- Bug Fix: Fixing iframe heights in editor. \n
- Bug Fix: Duplicate font families in drop down. \n
- Bug Fix: Saving existing blocks to library missing section wrapper. \n
1.6.3
\nRelease Date: January 17th, 2018
\n- \n
- Bug Fix: Issue causing editor to fail when an empty block is saved to your block library. \n
- Bug Fix: Editor width is set incorrectly if front end of site is inaccessible. \n
1.6.2
\nRelease Date: December 26th, 2017
\n- \n
- Bug Fix: Edit links displayed when not logged in. \n
1.6.1
\nRelease Date: December 19th, 2017
\n- \n
- Bug Fix: Remove old plugin name (boldgrid-editor) from BG themes recommendations. \n
- Bug Fix: Fix compatibility issues with Advanced Custom Fields plugin. \n
- Bug Fix: Disable margin control on columns. \n
- Bug Fix: Fixed error when activating old plugin name. \n
- Bug Fix: Advanced Control -> Box shadow switch unclickable. \n
- Bug Fix: Fix JS error when adding Blocks on text tab. \n
- Update: SASS compiler updated. \n
1.6
\nRelease Date: November 14th, 2017
\n- \n
- New Feature: Advanced controls and Custom Design UI updates. \n
- New Feature: Added new Post Type – Block. \n
- New Feature: Users can now save Blocks and reuse them. \n
- New Feature: New pages will now be prompted to install a new Block. \n
- New Feature: Control for hiding and showing page titles. \n
- New Feature: Escape now closes an open panel. \n
- New Feature: Allow customization of HR element. \n
- New Feature: Added information about the icons in the DropTab. \n
- New Feature: Added color palette control. \n
- New Feature: Added first time intro choices. \n
- New Feature: Added custom class inputs for buttons, backgrounds, hr, images and icons. \n
- Bug Fix: Image crop issue with http vs https. \n
- Bug Fix: Issue with masonry layout on box designs. \n
1.5
\n- \n
- Update: Bump version. \n
1.4.9
\n- \n
- Bug Fix: Fix notices thrown when installing Blocks. \n
1.4.8
\n- \n
- Bug Fix: Remove image content type checking. \n
- Update: Added filter for allowed_post_types for loading editor. \n
- Update: Improving timing of Block loading message. \n
- Update: Improving performance of Blocks on sites with a lot of content. \n
- Update: Updating background image urls. \n
- Update: Updating Font Awesome icon selections. \n
- Update: Adding alternative image request methods. \n
- Update: Use latest version of shared assets. \n
- Bug fix: Fixing an error on attachment page. \n
- Bug fix: Adding filter for posts to be excluded from My Blocks. \n
1.4.7
\n- \n
- Bug fix: Misc. bug fixes for Dynamic Blocks. \n
- New Feature: Delete Block button added to Block UI. \n
1.4.6
\n- \n
- New Feature: Integrating new Dynamic Blocks. \n
- Update: Updated plugin URI. \n
1.4.5
\n- \n
- Update: Updated for WordPress 4.8. \n
1.4.4
\n- \n
- New Feature: Added support for WPForms. \n
1.4.3
\n- \n
- Bug fix: Fixed auto plugin update. \n
1.4.2
\n- \n
- Bug fix: Added check and load before using get_plugin_data() for updates. \n
- Update: Removing btn-flat default class. \n
1.4.1
\n- \n
- Update: Updating plugin description. \n
1.4.0.1
\n- \n
- Bug Fix: Replaced section background image 404. \n
- Bug Fix: Google maps not replaced on edit. \n
- Bug Fix: Disable mce inline_boundaries. \n
1.4
\n- \n
- Bug fix: Fixed issue when installing plugins from the Tools Import page. \n
- Bug fix: Crop image screen closes immediately. \n
- Bug fix: Updating section background image URLs. \n
1.3.4
\n- \n
- Bug Fix: Fixing chrome drag auto scroll. \n
- Bug fix: Fixed plugin update checks for some scenarios (WP-CLI, Plesk, etc). \n
- Bug fix: Error thrown while resizing. \n
- Bug fix: Column Drag outline is the wrong color. \n
- Bug fix: Blocks not vertically centered. \n
- Update: Prioritize Post Blocks when viewing posts. \n
1.3.3
\n- \n
- Update: Add Underline to tinymce toolbar. \n
- Update: Set default section background image position to center. \n
- Bug fix: Fixing an issue where column popover would disappear. \n
- Bug fix: Fixing an issue where swapping images was not working correctly. \n
- Bug fix: Fixing adding icons to empty areas. \n
- Bug fix: Fixing issue with system fonts displaying in editor dropdowns. \n
- Bug fix: Replace more than one image bug. \n
1.3.2
\n- \n
- Bug fix: Fixing issue adding Blocks. \n
- New feature: Added a new UI for Blocks. \n
- Testing: Tested on WordPress 4.7. \n
1.3.1
\n- \n
- Misc: Added plugin requirements to readme.txt file. \n
- Update: Crop Image Screen – update source image options. \n
- Bug fix: Prevent duplicate ‘Add Block’ buttons. \n
1.3
\n- \n
- Update: Added neutral colors to section background colors. \n
- Update: Removed duplicate maps types. \n
- Update: Added Google maps edit link. \n
- Update: Updating Dependencies. \n
- Bug fix: Fixed issue with text color and section backgrounds. \n
- Bug fix: Fixing issue with update notice blocking user interaction on loading failure. \n
1.2.13
\n- \n
- Update: Fixing panel issue after first time notice. \n
1.2.12
\n- \n
- Update: Added update notice for users updating to 1.3. \n
- Update: Adding a conversion method from static maps to embed maps. \n
- Bug fix: Allow users to drag into empty sections. \n
- Bug fix: Fixed issue with system fonts used in themes. \n
1.2.11
\n- \n
- Bug Fix: Fixing issue with popover panel items. \n
1.2.10
\n- \n
- Update: Smoothing auto scroll during drag. \n
- Update: Hide popover font control when not applicable. \n
- Update: Setting default text color for column backgrounds. \n
- Update: Added default to font selection. \n
- Update: Add Media now in Drop Tab > Add new. \n
- Bug fix: Fixing issue with column popover at the edge of the screen. \n
- Bug fix: Fixing z-index issue withe section popover. \n
- Bug fix: Image being cloned after pressing enter. \n
- Bug fix: Nested columns allowed for parent column backgrounds. \n
- Bug fix: Fixing issue with row resize cursor. \n
- Bug fix: Hide button color if multiple buttons in a paragraph. \n
- Bug fix: Staging colors and buttons will now be enqueued correctly. \n
- Update: WBP-2426 Adjust the way crop modal hides router tabs. \n
1.2.9
\n- \n
- Bug Fix: Added cache busting for colors and button files. \n
1.2.8
\n- \n
- Misc: Added EOF line breaks. \n
- Update: Fix issue with direction of section popover menu. \n
- Bug fix: Fixed issue where section border did not show. \n
- Bug fix: Fixed issue where change icon does not appear. \n
- Bug fix: Fixed issue causing missing image toolbar. \n
- Bug fix: Fixed issue causing button customization to disappear. \n
- Bug fix: Reset class controls when opening customizer. \n
- New feature: Change image added to BG menu bar. \n
- New feature: Add my button designs to button panel. \n
- New feature: Track my designs for images as the user makes changes. \n
- New feature: Add Button Primary & Button Secondary to Button Panel. \n
- Bug fix: Wrapping content elements not contained, in theme default containers. \n
1.2.7
\n- \n
- Misc: Updated readme.txt for Tested up to 4.6.1. \n
- Bug fix: Load BoldGrid settings from the correct WP option (site/blog). \n
- Update: Setting version constant from plugin file. \n
- New feature: Buttons, Fonts and text backgrounds will now track usage on other pages. \n
- Update: Appearance of drag element has been modified. \n
- New feature: Added Section dragging & zoomed out view. \n
1.2.6
\n- \n
- Bug fix: Rebuilding JS assets. \n
1.2.5
\n- \n
- Bug fix: Added wrapper to handle mb_convert_encoding() if mbstring is not loaded. \n
- Bug fix: Issue where popovers did not comeback after drag drop. \n
- New feature: Overlays color for background images. \n
- New feature: Added column dragging to empty areas within row. \n
- New feature: Added column resizing from first column on the left boundary. \n
- New feature: Empty columns will be automatically deleted while resizing within a row. \n
- New feature: Added border color control to boxes. \n
- New feature: Row resizing now works in nested rows. \n
- New feature: Add theme section fonts to font selection. \n
- New feature: Added customization options for gradients. \n
- Bug fix: Bug fixes for towards undo and redo actions. \n
- Bug fix: Fixed issues with tripple click to delete. \n
- Bug fix: Fixed issues with editor height. \n
- Bug fix: Fixed issues with color control preselecting. \n
1.2.4
\n- \n
- Bug fix: Fixing issue with default container class. \n
- Bug fix: Fixing JS error when gallery plugin is missing. \n
- Bug fix: Fixing issue breaking font family selection. \n
1.2.3
\n- \n
- Misc: Updated readme.txt for Tested up to: 4.6. \n
- New feature: Added customization of Icons. \n
- New feature: Added customization of Backgrounds. \n
- New feature: Added customization for widths of rows. \n
- New feature: Added customization for padding on rows. \n
- New feature: Added customization of Buttons. \n
- New feature: Added customization of Fonts. \n
- New feature: Introduced customization and new component “Text Backgrounds”. \n
- New feature: Users can now add border to images. \n
- New feature: Users can now apply filters to images. \n
- Rework: Formatting. \n
1.2.2
\n- \n
- Bug fix: Issue causing parent row to be deleted when removing icon or anchor. \n
1.2.1
\n- \n
- Bug fix: Issue with pressing enter on an empty .row > .column. \n
- Bug fix: Fixed issue with Blocks getting images updated. \n
1.2
\n- \n
- Bug fix: Fixing issue with column popover size when zooming out. \n
- Bug fix: Sporadic issue, images load but then disappear within editor. \n
1.1.5
\n- \n
- New feature: Added capability for auto-updates by BoldGrid API response. \n
- Testing: Tested on WordPress 4.5.3. \n
- Bug fix: Adding a new row was not allowing you to type in it. \n
1.1.4
\n- \n
- Bug fix: Fixed issue with non BG themes and Blocks modal. \n
- New Feature: Adding font family and font size controls to customizer widgets. \n
1.1.3
\n- \n
- Update: Changing borders to outline for draggable objects. \n
- Update: Passed WordPress 4.5.1 testing. \n
- Bug fix: Javascript error in console after loading Blocks. \n
- Bug fix: JS Error when going to ‘Google Map’ tab. \n
1.1.2
\n- \n
- Bug fix: Addressing issues with drag and drop in Safari and Microsoft Edge w/ WP 4.5. \n
1.1.1.2
\n- \n
- Bug fix: Addressing issues with drag and drop in Chrome and FF w/ WP 4.5. \n
1.1.1.1
\n- \n
- Bug fix: Fixed update class interference with the Add Plugins page. \n
1.1.1
\n- \n
- Bug fix: Fixed undefined index “action” for some scenarios. Optimized update class and addessed CodeSniffer items. \n
1.1
\n- \n
- Bug fix: Fixing flexbox issue on safari \n
1.0.9
\n- \n
- Misc: Added license file. \n
- New feature: Suggest crop: Add ‘size’ dropdown menu when cropping an image. \n
- New feature: Suggest crop: default selection should be as wide as it could be. \n
- New feature: Suggest crop: Center the default selection. \n
- New feature: Drag and drop enabled state is now remembered per theme. \n
- Update: Suggest crop: Do not trigger on ‘Add Media’. \n
- Update: Suggest crop: Remove feature switch. \n
1.0.8
\n- \n
- New feature: Change button opens ‘Replace Image’ media modal. \n
- New feature: Suggest image crop when replacing images of different aspect ratios. \n
1.0.7
\n- \n
- Rework: Updated require and include statements for standards. \n
1.0.6
\n- \n
- New feature: Serve static Blocks via API \n
1.0.5.1
\n- \n
- Bug fix: Fixed PHP version check condition (<5.3). \n
1.0.5
\n\n- \n
- New feature: Adding Icons for draggable tools \n
- Usability: Improved popover hover responsiveness \n
- Bug fix: Added support for DIR in PHP <=5.2. \n
- New feature: Enable fontsize and family selection in tinymce \n
- New feature: Columns will now extend to the full height of row. \n
- New feature: Updating the loading graphic \n
- Misc: Updated readme.txt for Tested up to: 4.4.1 \n
- New feature: Standardize Drag Menu order \n
- New feature: Add wp-image-## class to images when adding Blocks. \n
1.0.4
\n- \n
- Bug fix: Fixing compatibility issues with IE 11, 12 and 13 \n
1.0.3
\n- \n
- New feature: Added unit tests \n
- Bug fix: Insert media will now be the default tab when changing an image \n
- Bug fix: Fixing issue causing tinymce height to be too large to too small \n
1.0.2
\n- \n
- New feature: Updated readme.txt for WordPress standards. \n
- Usability: Adding cache query args for tinymce styles \n
1.0.1
\n- \n
- Bug fix: Fixing error experienced in non BG themes in editor \n
1.0
\n- \n
- Initial public release. \n
![\"Section](\"https://ps.w.org/post-and-page-builder/assets/screenshot-1.png?rev=1781425\")
Section Background settings.
![\"Editing](\"https://ps.w.org/post-and-page-builder/assets/screenshot-2.png?rev=1781425\")
Editing Color Palettes.
![\"Creating](\"https://ps.w.org/post-and-page-builder/assets/screenshot-3.png?rev=1781425\")
Creating a new page.
![\"Adding](\"https://ps.w.org/post-and-page-builder/assets/screenshot-4.png?rev=1781425\")
Adding Blocks to your page.
![\"Edit](\"https://ps.w.org/post-and-page-builder/assets/screenshot-5.png?rev=1781425\")
Edit Page view.
![\"Text](\"https://ps.w.org/post-and-page-builder/assets/screenshot-6.png?rev=1781425\")
Text Settings view.
![\"Adding](\"https://ps.w.org/post-and-page-builder/assets/screenshot-7.png?rev=1781425\")
Adding Icons.
Easy to use once you know what you're doing
\n \n\n By 
Easy to use, powerful and enjoyable.
\n \n\n By 
Great product
\n \n\n By 
Excellent.
\n \n\n By 
Works great but really annoying begging for reviews
\n \n\n By 
impossibile delete account
\n \n\n By 
Muy útil!
\n \n\n By 
Great !
\n \n\n By 
Simple to Use
\n \n\n By 
Super Easy
\n \n\n By 
Automatically Optimize Your SEO with BoldGrid Easy SEO and Rank Higher in the Search Engines
\nBoldGrid Easy SEO will help you create better content and rank higher in the search engines. It analyzes your page content in real-time and makes recommendations that will help you maintain best SEO practices. Simply set a target keyword or phrase and the BoldGrid Easy SEO dashboard will automatically give you easy-to-follow suggestions on improving your on-page SEO. Regardless of your SEO skill level or knowledge, BoldGrid Easy SEO provides simple, yet powerful tools for website search engine optimization. Get automatic assistance with:
\nOptimal Keyword Density
\nBoldGrid Easy SEO will analyze your content in real-time to ensure your targeted keyword appears at the optimal frequency, as well as in the right places on the page.
\nPage Titles and Descriptions
\nControl and optimize how your pages appear in Google rankings pages with the title and description editor. BoldGrid Easy SEO will also make sure your target keyword is included.
\nHeader Tags and Content
\nBoldGrid Easy SEO will automatically analyze your header tags and give you recommendations on their proper usage, as well as assisting you with including relevant content.
\nImage Alt Tags
\nBoldGrid Easy SEO automatically checks your images for alt tags to help you identify areas for SEO improvement.
\nContent Length
\nKeyword rich content is a prime factor when search engines determine rankings. BoldGrid Easy SEO will assist you in writing better content by tracking your progress and alerting you when you’ve reached the sweet spot.
\nSearch Engine Indexing
\nAllow (or disallow) search engines from indexing pages with a single click.
\nFollow/No Follow Links
\nChoose whether your links are visible to search engines and count toward your SEO, or hide them if necessary.
\nCanonical URLs
\nAvoid duplicate content penalties by indicating a canonical URL where applicable.
\n\";s:12:\"installation\";s:503:\"Minimum Requirements
\n- \n
- PHP version 5.3 or greater \n
- WordPress 4.4 or greater \n
From within WordPress
\n- \n
- Visit ‘Plugins > Add New’ \n
- Search for ‘BoldGrid Easy SEO’ \n
- Activate BoldGrid Easy SEO from your Plugins page. \n
Manually
\n- \n
- Upload the entire boldgrid-easy-seo folder to the /wp-content/plugins/ directory. \n
- Activate the plugin through the Plugins menu in WordPress. \n
\n
If you have any questions on getting started with BoldGrid Easy SEO, please visit our Getting Started Guide.
\nWe also suggest joining our Team Orange User Group community for free support, tips and tricks.
For general questions check out our Frequently Asked Questions page.
\n\n\n
Bugs can be reported either in the WordPress support forum or in the BoldGrid Support Center.
\n\n\n
The BoldGrid Easy SEO plugin is open source software. Join in on our GitHub repository.
\n\n\n\";s:9:\"changelog\";s:2561:\"1.6.10
\nRelease Date: February 24, 2021
\n- \n
- Bug Fix: Use Post Thumbnail for og:image tag [#41] (https://github.com/BoldGrid/boldgrid-seo/issues/41) \n
1.6.9
\nRelease Date: December 7th, 2020
\n- \n
- Bug fix: JS Console error in WordPress 5.6 [#37] (https://github.com/BoldGrid/boldgrid-seo/issues/37) \n
1.6.8
\nRelease Date: August 26th, 2020
\n- \n
- Bug fix: SEO dashboard was not loading in WordPress 5.5 \n
1.6.7
\nRelease Date: August 10th, 2020
\n- \n
- Bug fix: Yoast Conflict: JavaScript Error Prevents PPB Blocks and Interface from Loading [#29] (https://github.com/BoldGrid/boldgrid-seo/issues/29) \n
1.6.6
\nRelease Date: August 6th, 2020
\n- \n
- Bug fix: Fixed PHP 7.4 Deprecated implode calls. \n
1.6.5
\nRelease Date: March 19th, 2020
\n- \n
- Update: Register meta values. \n
1.6.4
\nRelease Date: December 17th, 2019
\n- \n
- Bug fix: Fixed empty robots tag. \n
- Update: Added filter to allow meta robots to be skipped and controlled via filter. \n
1.6.3
\nRelease Date: August 20, 2019
\n- \n
- Bug fix: Fixed situations where markup for canonical URLs can be ouput multiple times. #9. Props @jessecowens \n
- Bug fix: Titles with markup should now be properly parsed. #8 \n
- Bug fix: Titles with commas had the commas turned into pipe seperators. #7 \n
- Update: Added missing translation string for archives with paginated pages. #12 \n
1.6.2
\nRelease Date: February 14, 2019
\n- \n
- Bug fix: Conflict with Yoast SEO on classic editor \n
1.6.1
\nRelease Date: January 29th, 2019
\n- \n
- Bug fix: Post image count not correct. \n
1.6.0
\nRelease Date: December 4th, 2018
\n- \n
- New Feature: Added Gutenberg and WordPress 5 compatibility. \n
- Update: Max length for meta descriptions was updated to 300. \n
- Bug Fix: Save special chars for meta fields. \n
1.5.1
\nRelease Date: November 14th, 2017
\n- \n
- Initial Release. \n
![\"Post](\"https://ps.w.org/boldgrid-easy-seo/assets/screenshot-1.png?rev=1800507\")
Post and Page analysis.
![\"Page](\"https://ps.w.org/boldgrid-easy-seo/assets/screenshot-2.png?rev=1800507\")
Page titles and descriptions.
![\"Search](\"https://ps.w.org/boldgrid-easy-seo/assets/screenshot-3.png?rev=1800507\")
Search Visibility.
Does Not work well with Gutenberg
\n \n\n By 
Very GOOD
\n \n\n By 
Total Upkeep is more than just a “backup plugin.” It can help stop website crashes before they even happen.
\nWebsite data loss can happen even if you’re doing everything “right,” like keeping your WordPress and plugins updated or having a backup plugin installed. There’s so many things outside of your control that could totally wipe out your website without any warning.
\nTo keep your website safe, you’ll need more than just a “backup plugin.” You need a backup solution that helps prevent catastrophic data loss in the first place, and if the worst occurs, provides you with the tools to easily, quickly and painlessly get your site up and running again.
\nTotal Upkeep is a full 360 solution that keeps your data safe and protects your website from catastrophic data loss. Features include:
\n- \n
- Automated and manual backups \n
- Full file and database backup or customize settings based on your needs \n
- Remote backups via FTP / SFTP, Amazon S3 and Google Drive (Premium) \n
- Total Upkeep checks to ensure that your webserver has the necessary features to properly create backup archives, which protects the integrity of your backups \n
- Clone, duplicate and/or migrate your site with just a few clicks \n
- Site Check monitors your site for issues that could lead to site crashes, provides a toolset to restore your site even if your WordPress installation is inaccessible \n
- Auto rollback feature creates a backup before updates, restores your site to the last backup if an update fails \n
- Create staging sites to test new plugins or themes with Total Upkeep + Cloud WordPress \n
I’m Intrigued! Tell Me More About Your Features…
\nSupports Both Automated and Manual Backups
\nSimply select a date and time for automatic backups and Total Upkeep will create a backup archive of your entire WordPress installation and its database. If a full website or database backup isn’t required, you can choose to backup only certain files, folders and database tables.
Remote Backups
\nSafely store backups remotely via FTP / SFTP. The premium version of Total Upkeep allows you to automatically upload archives to Amazon S3 or Google Drive.
Easy Site Restoration and Website Migration
\nDownload, restore, or delete backups with a single click from the Total Upkeep Dashboard.
Restore Your Website Even If WordPress Is Down
\nUse our restoration script to restore a backup from outside of WordPress in the event WordPress itself has been corrupted.
Restore Entire Backup Archive or Single Files
\nNeed to restore only one file from a backup? Total Upkeep Premium gives you the option to restore a single file within the backup browser.
Historical Versions
\nDo you have a file that needs to be restored, but not sure which backup it’s in? The Historical Versions feature allows you to view a list of all of your backups containing that file and provides an easy way to restore the file.
Easily Clone or Migrate Your Websites
\nTotal Upkeep allows you to easily clone a website and migrate it to another WordPress installation with just a few clicks. Install Total Upkeep on both WordPress sites, create a backup archive on the first site, then restore that backup on your second site using a protected link – simply copy and paste the link! It’s the easiest and fastest way to duplicate / clone your website.
Site Check
\nSite Check monitors your site at specified intervals for errors that could lead to catastrophic data loss. If Site Check detects an error, it will send you an email alert and auto restore your website using your latest backup.
Built-in Diagnostic Tools
\nSite Check keeps a running historical error log, allowing you to easily diagnose and troubleshoot website issues.
Powerful Website Restoration Functionality
\nYou can configure Site Check’s settings from the Total Upkeep settings page, or via command line. If your site is totally non-functional, you can use the command line to easily restore your website from the last full backup archive.
Auto Rollback
\nYou can set Total Upkeep to automatically backup your site before updates, and automatically rollback your site to the last backup if an update fails. Automatic updates can be set for WordPress core, plugins, and themes individually.
Create Staging Sites with Total Upkeep + Cloud WordPress
\nCloud WordPress allows you to create a fully functional free WordPress demo (with or without BoldGrid) in just a few clicks. Use Total Upkeep to clone and migrate your website to a Cloud WordPress installation, where you can test themes, plugins and other website changes without fear of breaking your live site.
Try out the Total Upkeep Plugin on Cloud WordPress to see for yourself!
\n\";s:12:\"installation\";s:641:\"Minimum Requirements
\n- \n
- PHP 5.4 or higher. PHP 7.3 or higher is recommended. \n
- At least one of the following PHP execution functions enabled: “popen”, “proc_open”, “exec”, “shell_exec”, “passthru”, or “system”. \n
- A Cron system with the “crontab” utility, or WP Cron. \n
- A WP_Filesystem FS_METHOD being “direct”. \n
Manually
\n- \n
- Upload the entire boldgrid-backup folder to the /wp-content/plugins/ directory. \n
- Activate the plugin through the Plugins menu in WordPress. \n
\n
Total Upkeep is more than just a “backup plugin.” It’s a full 360 solution with tools and features that helps prevent website crashes from happening in the first place. In addition to all the features you’ve come to expect from a plugin with website backup functionality, Total Upkeep also offers:
\n- \n
- Site Check monitors your site for issues that could lead to site crashes, provides a toolset to restore your site even if your WordPress installation is inaccessible \n
- Auto rollback feature creates a backup before updates, restores your site to the last backup if an update fails \n
- Create staging sites to test new plugins or themes with Total Upkeep + Cloud WordPress \n
\n
Total Upkeep Premium gives you extra tools to prevent website crashes, as well as additional troubleshooting and diagnostic tools.
\n- \n
- Additional remote backup options (Amazon S3, Google Drive) \n
- Single file restoration \n
- Historical versions \n
- Search for recently modified files \n
- Save a copy of a file before updating \n
- Comprehensive update history \n
\n
Have a problem? First, take a look at our Getting Started guide. If that doesn’t answer your question, you can receive support for Total Upkeep at the support forum, the Team Orange User Group, our comprehensive support library, or our official questions portal.
\n\n\n\";s:9:\"changelog\";s:25905:\"1.15.2
\nRelease date: May 27th, 2022
\n- \n
- Updpate: Updated dependencies. \n
1.15.1
\nRelease date: May 18th, 2022
\n- \n
- Bug fix: Fixed bad rewrite rules on restorations due to cached permalink settings. \n
1.15.0
\nRelease date: March 15th, 2022
\n- \n
- New feature: REST API calls for backup and settings management. \n
- Bug fix: posix_getpgid availability check. \n
- Update: Updated dependencies. \n
1.14.14
\nRelease date: February 24th, 2022
\n- \n
- Update: Only show “backup in progress” notices for admins. \n
- Security fix: Permissions check added to heartbeat_received for backup progress. \n
1.14.13
\nRelease date: July 22nd, 2021
\n- \n
- Update: Added a live log to the in progress bar. \n
- Update: Added a “cancel backup” link to the in progress bar. \n
- Update: Added “who / what triggered backup” to the in progress bar. \n
- Update: The in progress bar can now detect when a backup process has been killed. \n
1.14.12
\nRelease date: April 13th, 2021
\n- \n
- Update: Improved output buffering when downloading a backup via ajax. \n
- Update: Added a download log. \n
- Update: Extra .git directories removed from vendor directory. \n
1.14.11
\nRelease date: February 16th, 2021
\n- \n
- Bug fix: Improved check for available execution functions and disabled functions. \n
- Bug fix: Fixes js handling file / db backup filters on settings page. \n
- Update: Changed “download backup” feature to send chunked. \n
- Update: Fixed uasort usage. \n
- Update: Added “Dismiss” verbiage to “Please rate us!” notice. \n
1.14.10
\nRelease date: December 14th, 2020
\n- \n
- Update: Added transfer log. \n
- Security fix: Fixes for restore-info.json file and cli/env-info.php script. \n
1.14.9
\nRelease date: December 8th, 2020
\n- \n
- Bug fix: Fixed reset link for backup all tables. \n
- Bug fix: Fixed pagination buttons for file exclusion tool. \n
- Bug fix: Fixed several html escaping issues. \n
- Bug fix: Fixed file exclusion preview filter input. \n
- Bug fix: Fixed various jqmigrate warnings. \n
1.14.8
\nRelease date: November 13th, 2020
\n- \n
- Update: Rebuild with composer 1. \n
1.14.7
\nRelease date: November 12th, 2020
\n- \n
- Update: Prevent easy apache cache files in backups. \n
- Bug fix: Fixed nonce errors when downloading remote archives. \n
1.14.6
\nRelease date: October 13th, 2020
\n- \n
- Update: Updated dependencies. \n
- Update: Added additional logged and filesystem analysis log. \n
- Bug fix: Fixed ftp bug. \n
1.14.5
\nRelease date: September 22nd, 2020
\n- \n
- Update: Optimized functionality tests. \n
- Update: Optimized plugins and themes init in auto updates. \n
1.14.4
\nRelease date: August 26th, 2020
\n- \n
- Bug fix: Invalid nonce when one click uploading to remote storage providers. \n
- Bug fix: Escaping / translation of “Remote Storage” help text on Archive Details page. \n
- Update: Allow auto update notice on updates page to be permanently dismissible. \n
1.14.3
\nRelease date: August 12th, 2020
\n- \n
- Update: Updated Auto Update features to utilize the WordPress 5.5+ Auto Update UI. \n
1.14.2
\nRelease date: July 22nd, 2020
\n- \n
- Bug fix: Fixed array_key_exists() warings from auto-updates class. \n
- Bug fix: Fixed several invalid nonce errors. \n
- Bug fix: Fixed markup escaping in rating prompt. \n
- Bug fix: Fixed “backup site now” on archive page. \n
1.14.1
\nRelease date: July 7th, 2020
\n- \n
- Bug fix: Auto Update Translation filter causes fatal error with JetPack active [#50]((https://github.com/BoldGrid/boldgrid-backup-premium/issues/50) \n
1.14.0
\nRelease date: July 7th, 2020
\n- \n
- New feature: Timely Auto Updates – auto update WordPress, Plugins, and Themes after a set number of days. \n
- New feature: SystemZip Compression ratio – Modify System Zip process to address issues with exceeding php memory_limit and add option to set compression ratio. \n
- New feature: Added ‘Backup Now’ and ‘Upload Backup’ buttons to each Total Upkeep page. \n
- New feature: Added video guides to Premium Features page. \n
- Bug fix: Non Backup files should not be uploaded. \n
- Bug fix: Ensure user can CREATE VIEWS before restoring views. \n
1.13.12
\nRelease date: July 6th, 2020
\n- \n
- Bug fix: Site check emails sent regardless of user preference. \n
1.13.11
\nRelease date: July 1st, 2020
\n- \n
- Bug fix: Resolved file name conflict with certain security plugins. \n
1.13.10
\nRelease date: June 23rd, 2020
\n- \n
- Update: Updated dependencies. \n
- Bug fix: Avoid fatal Boldgrid\\Library\\Library\\Ui\\Card on dashboard. \n
1.13.9
\nRelease date: June 15th, 2020
\n- \n
- Update: Updated retention logic for pre auto update backups. \n
- Bug fix: Fixed “get all cron jobs” call for large crontabs. \n
1.13.8
\nRelease date: June 9th, 2020
\n- \n
- Update: Added orphaned file cleanup system. \n
1.13.7
\nRelease date: June 4rd, 2020
\n- \n
- Update: Create log file for local retention. \n
1.13.6
\nRelease date: June 1st, 2020
\n- \n
- Bug fix: Adjust the charset used when dumping database (derived from WordPress DB_CHARSET). \n
1.13.5
\nRelease date: May 28th, 2020
\n- \n
- Update: Create a restore log (like the backup log). \n
- Update: Updated dependencies. \n
- Bug fix: Avoid fatals on library issues. \n
- Bug fix: Be more specific with data-toggle-target attribute. \n
1.13.4
\nRelease date: May 21st, 2020
\n- \n
- Update: If backup email fails, debug info written to log file. \n
- Update: Definition added to allow for skipping email headers. \n
1.13.3
\nRelease date: April 2nd, 2020
\n- \n
- Bug fix: Database backups not working when using port other than 3306 (the Robert bug). \n
1.13.2
\nRelease date: Februrary 21st, 2020
\n- \n
- Bug fix: Resolved activation bug during BoldGrid Inspirations deployment. \n
1.13.1
\nRelease date: February 18th, 2020
\n- \n
- Update: Added “Find modified files” card to Premium Features page. \n
- Update: Allow error messages to be shown for remote storage providers. \n
- Update: Updated dependencies. \n
1.13.0
\nRelease date: February 6th, 2020
\n- \n
- Update: Added new “Premium Features” dashboard page. \n
- Update: Added support for system zip for generating backups. \n
- Update: Updated dependencies. \n
1.12.6
\nRelease date: January 16th, 2020
\n- \n
- Update: Open logs full screen. \n
- Update: Added additional info to the logs. \n
- Update: Logs now listen for signals, can log when a script is killed. \n
1.12.5
\nRelease date: January 14th, 2020
\n- \n
- Update: Adding logging system. \n
- Update: Updated dependencies. \n
1.12.4
\nRelease date: January 10th, 2020
\n- \n
- Bug fix: Escape table prefix when getting tables. \n
- Bug fix: Include views when dumping the database. \n
1.12.3
\nRelease date: December 19th, 2019
\n- \n
- Bug fix: Only show plugin rename notice to active users. \n
- Update: Updating link to admin page for entering BoldGrid Connect Key. \n
1.12.2
\nRelease date: December 13th, 2019
\n- \n
- Bug fix: Fixed filtering of archive attributes. \n
1.12.1
\nRelease date: November 26th, 2019
\n- \n
- Bug fix: Fixed sanitizing of ftp hostnames. \n
1.12.0
\nRelease date: November 21th, 2019
\n- \n
- Update: Renamed plugin from “BoldGrid Backup” to “Total Upkeep”. \n
- New feature: Added support for database dump file encryption. \n
1.11.8
\nRelease date: October 11th, 2019
\n- \n
- Update: Updated dependencies to resolve possible pluggable function
wp_rand()errors. \n
1.11.7
\nRelease date: October 10th, 2019
\n- \n
- Update: Updated backup directory suffix creation. \n
- Update: Updated dependencies. \n
1.11.6
\nRelease date: October 8th, 2019
\n- \n
- Bug fix: Prevent fatals during activation when library classes are missing. \n
- Bug fix: Fixed escaping of html on archives page when backup only exists remotely. \n
- Bug fix: Don’t show “Make your first backup” message while a backup is in progress. \n
- Bug fix: Make notices on the Settings page dismissible. \n
- Bug fix: Don’t show “Update Protection” notice if we just updated something. \n
- Update: Be default, have local storage enabled in remote settings. \n
- Update: Avoid showing activation notice if users is redirected to the archives page. \n
1.11.5
\nRelease date: October 1st, 2019
\n- \n
- Update: Allow BoldGrid Backup Premium to define minimum free version. \n
- Update: Updates to inform users DreamObjects is now available. \n
1.11.4
\nRelease date: September 26th, 2019
\n- \n
- Bug fix: Improve logic that checks if scheduled backups are enabled. \n
1.11.3
\nRelease date: September 26th, 2019
\n- \n
- Bug fix: Prevent warnings when user is logged in as a non admin. \n
1.11.2
\nRelease date: September 17th, 2019
\n- \n
- Update: Allow activation notice to be filtered. \n
- Update: Reworked much of the js for “Backup site now” and “In progress”. \n
1.11.1
\nRelease date: September 10th, 2019
\n- \n
- Bug fix: Fixed crontab entry removal on cancel of rollback from updating from version <=1.10.6 to >=1.11.0. \n
- Update: Updated dependencies. \n
1.11.0
\nRelease date: August 29th, 2019
\n- \n
- New feature: Added a transfers page. \n
- Bug fix: Fixed “Use of undefined constant STDERR” warning for bgbkup-cli. \n
- Update: Updated auto-rollback to use the CLI restoration process. \n
- Update: Updated dependencies. \n
- Bug fix: Fixed database table exclusion when none are selected. \n
- Bug fix: Avoid zip close error by checking files before write/close. \n
- Bug fix: Prevent the web server from killing the archive process. \n
1.10.6
\nRelease date: August 1st, 2019
\n- \n
- Update: Updated dependencies. \n
1.10.5
\nRelease date: July 30th, 2019
\n- \n
- Update: FTP mode detection taking too long; now saving mode. \n
- Bug fix: Replaced cbschuld/browser.php with a custom solution to avoid class conflicts. \n
- Update: Updated dependencies. \n
1.10.4
\nRelease date: July 17th, 2019
\n- \n
- Bug fix: Fixed get_execution_functions method so that disable_functions are properly removed. \n
1.10.3
\nRelease date: July 2nd, 2019
\n- \n
- Update: Moved BoldGrid RSS feed to the library. \n
1.10.2
\nRelease date: July 1st, 2019
\n- \n
- Bug fix: Fixed format of the Site Check cron entry. \n
1.10.1
\nRelease date: Jun 18th, 2019
\n- \n
- Update: Added helpful links to the plugin’s row on Plugins > Install Plugins. \n
- Update: Updating verbiage in several places to help inform user of Google Drive support. \n
- Update: Show a getting started message to users after they’ve activated the plugin. \n
- Update: Improved usability on “Backup Archives” page when there are no backups. \n
- New feature: Added a subpage for support. \n
- Update: Updated Travis CI config and dev dependencies. \n
- Update: Moved auto-rollback setting to the auto-updates page. \n
1.10.0
\nRelease date: June 10th, 2019
\n- \n
- New feature: Added settings section, logging, and email notifications for Site Check (bgbkup-cli). \n
- Bug fix: Ensure archive exists before attempting to upload via ftp. \n
- Update: Updated dependencies. \n
- Update: Updated content for the failed Site Check email notification message. \n
- Update: Removed duplicate build for toggles dependency. \n
1.9.3
\nRelease date: Apr 30th, 2019
\n- \n
- Bug fix: Avoid “Cannot close ZIP archive file” error by skipping files that are unreadable. \n
- Bug fix: Ensure adequate permissions before attempting any restoration. \n
- Update: Add source to Get Premium nav item. \n
- Update: Fixed FTP support (when using FTPES: Explicit FTP over SSL/TLS). \n
1.9.2
\nRelease date: Apr 16th, 2019
\n- \n
- Bug fix: Prevent duplicate emails when backups are made before an auto update. \n
1.9.1
\nRelease date: Apr 2nd, 2019
\n- \n
- New feature: Users can now specify a custom folder name for FTP uploads. \n
- Update: Increased precision of “Archive file size” value within progress bar to better show a backup is still occurring and didn’t freeze. \n
- Bug fix: Honor bgbkup-cli method argument. \n
1.9.0
\nRelease date: Mar 26th, 2019
\n- \n
- New feature: Added emergency/standalone restoration CLI process. \n
- Update: When storing backups in wp-content dir, make “boldgrid_backup” dir name more unique. \n
- Bug fix: Ensure library’s activity class is available before using it. \n
1.8.0
\nRelease date: Feb 14th, 2019
\n- \n
- New feature: Added WP-CLI support for backup schedule. \n
- Update: Change thickbox background color to inform user something is loading. \n
- Update: Misc updates required for next version of BoldGrid Backup Premium. \n
1.7.2
\nRelease date: Jan 15th, 2019
\n- \n
- Update: Improved journey for downloading the premium plugin. \n
- Update: Reduced the number of FTP connections made on the settings page. \n
- Update: Overhauled this readme file, added more info on features and added screenshots. \n
- Update: New system that asks user for bug fixes / new features, or requests plugin rating. \n
1.7.1
\nRelease date: Dec 18th, 2018
\n- \n
- Update: Added PHP version to compatibility checks. \n
- Bug fix: Hide certain update notices in storage configuration modal. \n
1.7.0
\nRelease date: Dec 4th, 2018
\n- \n
- New feature: Added auto-update settings for individual plugins and themes. \n
- New feature: Added limited-lifetime download links for archive files. \n
- New feature: Added import backup archive from URL address. \n
- New feature: Added progress bar to show the status of backups. \n
- New feature: Adding the ability to set and title and description to a backup. \n
- New feature: Adding the ability to flag a backup as being protected (excluded from retention). \n
- Update: Update protection is now valid for 1 hour after a full backup from the WordPress Updates or Plugins page. \n
- Update: Made the Backup Archives page the default page in the admin menu. \n
- Bug fix: Set a default backup directory if the path in settings is not valid. Remove filters before fixing home and siteurl on restore. \n
- Bug fix: Some HTML was caught in translations. \n
- Bug fix: Duplicate emails were sent when a backup was complete, fixed. \n
- Bug fix: Preserve timestamp on ftp/sftp uploads. \n
- Bug fix: Fixed CLI support detection on some EA4 servers. \n
- Update: Save settings and reload to the current section. \n
- Update: Reorganized settings sections. \n
1.6.5
\nRelease Date: July 31st, 2018
\n- \n
- New feature: Preflight test to see if server time zone matches cron time. \n
- Bug fix: argv variables missing, Enabled register_argc_argv within cron command. \n
- Bug fix: Failed crons now write to log. \n
1.6.4
\nRelease Date: July 17th, 2018
\n- \n
- Bug fix: Fixed and improved php-cli detection. \n
- Bug fix: Fixed “Undefined index ‘plugins\'” bug. \n
- Update: Cleaned up codebase to pass PHP CodeSniffer. \n
1.6.3
\nRelease Date: June 11th, 2018
\n- \n
- Bug fix: System Cron detection failed in some environments. \n
- Update: Clarified verbiage on setting up Premium connect key. \n
1.6.2
\nRelease Date: May 25th, 2018
\n- \n
- Update: Detect and use available resources to trigger cron tasks. Added cURL support. \n
1.6.1
\nRelease Date: May 24th, 2018
\n- \n
- Update: Ran PHPCBF to beautify PHP code. \n
- Update: $_POST sanitization \n
- Update: Cron system updated to avoid calling core files directly \n
1.6.0
\nRelease Date: April 11th, 2018
\n- \n
- New feature: Archive browser, the ability to see what’s in a backup. \n
- New feature: Database browser, the ability to see at a high level what’s in a backup. \n
- New feature: 1 click restore database only. \n
- New feature: FTP / SFTP support added. \n
- New feature: Control which files and database tables are backed up. \n
- Compatibility: PclZip support added for creating archives. \n
- Compatibility: WP Cron support added for scheduled backups. \n
- Compatibility: PHP Script used to backup the database, rather than system commands. \n
- Improvement: Update admin pages to use WP UI/UX standards. \n
- Improvement: Improved UI in regards to time zones. \n
- Improvement: Failed items on Preflight Check page are highlighted in red. \n
- Improvement: Send an email if a backup fails via cron. \n
- Improvement: More details in Preflight Check to help with troubleshooting. \n
- Bug fix: Bug fixed with auto restoration feature. \n
1.5
\nRelease Date: August 8th, 2017
\n- \n
- Update: Bump version. \n
1.3.12
\nRelease Date: July 20th, 2017
\n- \n
- Update: Updated plugin URI. \n
Release Date: June 27th, 2017
\n1.3.11
\n- \n
- New feature: Added auto-update settings for plugins and themes. \n
- Bug fix: Skip node_modules paths when creating archives. \n
1.3.10
\nRelease Date: May 16th, 2017
\n- \n
- Bug fix: Fixed undefined property when the pre-flight test fails. \n
- Bug fix: Fixed an undefined index when home dir is not writable. \n
- Bug fix: Fixed auto plugin update. \n
1.3.9
\nRelease Date: May 2nd, 2017
\n- \n
- Bug fix: Added check and load before using get_plugin_data() for updates. \n
1.3.8
\nRelease Date: April 4th, 2017
\n- \n
- Bug fix: After migrating a site via boldgrid-backup, the backup directory was not updated if invalid. \n
1.3.7
\nRelease Date: February 20th, 2017
\n- \n
- Bug fix: Fixed issue when installing plugins from the Tools Import page. \n
- Bug fix: Fixed check for system tar and zip. \n
- Bug fix: Fixed method of locating the home directory. \n
1.3.6
\nRelease Date: February 9th, 2017
\n- \n
- Update: Show how long the site was paused for. \n
- Update: Auto show move backups message. \n
- Bug fix: Fixed plugin update checks for some scenarios (WP-CLI, Plesk, etc). \n
1.3.5
\nRelease Date: February 7th, 2017
\n- \n
- Bug fix: Fixed plugin update checks for some scenarios (WP-CLI, Plesk, etc). \n
- Bug fix: Backing up fails after 5 minutes. \n
1.3.4
\nRelease Date: January 10th, 2017
\n- \n
- Update: Update support URLs. \n
- Update: Close session on gathering disk space API call. \n
- Bug fix: Fixed missing link in an email template. \n
- Bug fix: Uncaught TypeError: wp.template is not a function. \n
- Testing: Tested on WordPress 4.7. \n
1.3.3
\nRelease Date: December 20th, 2016
\n- \n
- Update: Show backup limits to users. \n
- Update: Misc notices. \n
- Update: Disable backup now button. \n
- Update: Prevent backup if the account is too large. \n
1.3.2
\nRelease Date: December 6th, 2016
\n- \n
- Update: Move backups when changing backup directory. \n
- Update: Improve time to calculate disk space. \n
- Bug fix: Added double-quote encapsulation to the password in the mysqldump defaults file. \n
- Bug fix: Typo fix. \n
1.3.1
\nRelease Date: November 15th, 2016
\n- \n
- Update: Modify ‘last created archive’ message with a link to archives. \n
- Update: Modify backup success message with a link to settings. \n
- Update: Modify BoldGrid Backup menus. \n
- Update: Adjust display of preflight check. \n
- Update: Free limitations to days of the week. \n
- Update: Free limitations to retention. \n
- Update: Standard tooltips. \n
- Update: Add intro message to the Archive page. \n
- Update: Modify backup id section on the archives page. \n
- Update: Modify Backup Site messages. \n
- Update: Cache disk space data. \n
- Update: Add free / premium messages next to disk / database sizes. \n
- Misc: Added plugin requirements to readme.txt file. \n
1.3
\nRelease Date: October 12th, 2016
\n- \n
- Update: Bump version. \n
1.2.3
\nRelease Date: September 20th, 2016
\n- \n
- Bug fix: Added handling for restoration if site URL changed. Fixed upload button in Chrome. \n
- Bug fix: Load BoldGrid settings from the correct WP option (site/blog). \n
- Bug fix: Fixed typo in archive deletion confirmation dialogue. \n
- Update: Set version constant from plugin file. \n
- Misc: Updated readme.txt for Tested up to 4.6.1. \n
1.2.2
\nRelease Date: September 7th, 2016
\n- \n
- New feature: Added the ability to upload a backup archive. \n
- Bug fix: Fixed errors during deactivation. \n
- Bug fix: Update class was not getting current plugin version. \n
1.2.1
\nRelease Date: August 23rd, 2016
\n- \n
- Bug fix: Updates via adminajax now updates the rollback timer. \n
- Misc: Updated readme.txt for Tested up to 4.6. \n
1.2
\nRelease Date: August 9th, 2016
\n- \n
- New feature: Added XHProf for optional PHP profiling. Can be enabled in “config.local.php” by setting “xhprof” to true. \n
- Bug fix: Fixed auto-update action hook. \n
- Bug fix: Changed restore and delete buttons to POST forms, to resolve an issue with people reloading the restoration URL. \n
- Bug fix: Reworked error notices for restoration. Emptying archive list before updating after performing a backup. \n
- Bug fix: Disabled backup and restore buttons after starting a restoration. \n
- Bug fix: Removed homedir not writable notice; moved info to the functionality test page. \n
- Bug fix: Removed add cron action on activation. \n
- Redesign: Changed backup duration display seconds to 2 decimal places. \n
- Rework: Settings page will now load if functionality test fails. \n
- Rework: Cleanup for the rollback admin notice. \n
- Rework: Added a warning in the notice for restorations (may get logged-out). \n
- Rework: Moved cron methods to a new class. \n
- Rework: Reworked for translations. \n
1.0.2
\nRelease Date: July 22nd, 2016
\n- \n
- Rework: Removed notice for staged pending rollback. \n
1.0.1
\nRelease Date: July 6th, 2016
\n- \n
- New feature: Added setting for a notification email address. \n
- New feature: Added setting for backup directory. \n
- New feature: Cancel auto-rollback if restoration is performed. \n
- New feature: Added Rollback Site Now button in the rollback notice. \n
- New feature: Made it possible to change siteurl and retain matched archives (backups made as of this update). \n
- New feature: Added capability for auto-updates by BoldGrid API response. \n
- Redesign: Formatted the Functionality Test page. \n
- Bug fix: Removed PHP SAPI check in the cron script. \n
- Bug fix: Restoration cron did not always complete. \n
- Bug fix: Better aligned rollback countdown timer with the cron job. \n
- Bug fix: Provided message for empty archive list. \n
- Bug fix: Rollback information is now removed after the timer reaches 0:00. \n
- Bug fix: Test for crontab now works when crontab is empty. \n
- Bug fix: Now closing PHP session on backup, download, and restore, so that other PHP requests from the client may load. \n
- Testing: Tested on WordPress 4.5.3. \n
1.0
\nRelease Date: June 21st, 2016
\n- \n
- Initial public release. \n
![\"Easily](\"https://ps.w.org/boldgrid-backup/assets/screenshot-1.png?rev=2199062\")
Easily schedule backups using Cron or WP Cron. Set a time of day, select the days of the week, and Total Upkeep will automate backups for you. You will receive an email after each backup has been completed.
![\"Automatically](\"https://ps.w.org/boldgrid-backup/assets/screenshot-2.png?rev=2009431\")
Automatically perform a backup before WordPress auto updates itself. This feature hooks into the pre_auto_update action.
![\"After](\"https://ps.w.org/boldgrid-backup/assets/screenshot-3.png?rev=2009431\")
After a scheduled backup completes, you can have it uploaded automatically to an FTP / SFTP server. Users who upgrade to premium can also store backups on Amazon S3.
![\"You](\"https://ps.w.org/boldgrid-backup/assets/screenshot-4.png?rev=2009431\")
You can configure which files and folders and include in your backups. \"Include\" and \"Exclude\" filters are easy to set up, and you can click the \"Preview\" button to get a listing of which files and folders will actually be included in your backup.
![\"Have](\"https://ps.w.org/boldgrid-backup/assets/screenshot-5.png?rev=2009431\")
Have tables you don\'t want to back up? Within the list of database tables, uncheck the tables you want to be excluded from backups, and they won\'t be included.
![\"Take](\"https://ps.w.org/boldgrid-backup/assets/screenshot-6.png?rev=2009431\")
Take control of how WordPress automatically updates itself. Select whether to auto update for major updates, minor updates, development updates, and/or translation updates.
![\"Select](\"https://ps.w.org/boldgrid-backup/assets/screenshot-7.png?rev=2009431\")
Select which of your plugins to have automatically updated when updates are available.
![\"Select](\"https://ps.w.org/boldgrid-backup/assets/screenshot-8.png?rev=2009431\")
Select which of your themes to have automatically updated when updates are available.
![\"Before](\"https://ps.w.org/boldgrid-backup/assets/screenshot-9.png?rev=2199062\")
Before upgrading WordPress, or any plugins or themes, backup your site. After the upgrade, test your site for any issues. If any issues are found, you can one-click restore your website or wait for the countdown to end and your site will automatically restore itself.
![\"For](\"https://ps.w.org/boldgrid-backup/assets/screenshot-10.png?rev=2199062\")
For large sites, backups can sometimes take a bit of time to complete. During backups, a progress bar is shown to keep you updated on the backup\'s status.
![\"When](\"https://ps.w.org/boldgrid-backup/assets/screenshot-11.png?rev=2009431\")
When backups are completed, or when a backup is restored, Total Upkeep will send you an email.
![\"The](\"https://ps.w.org/boldgrid-backup/assets/screenshot-12.png?rev=2009431\")
The Backup Archives page will list all of your backups, and show you where each backup is stored (Web Server, FTP/SFTP, etc).
![\"When](\"https://ps.w.org/boldgrid-backup/assets/screenshot-13.png?rev=2199062\")
When viewing the details of a backup, click the \"Upload\" button to easily upload the backup archive to one of your remote storage providers, such as an FTP server.
![\"To](\"https://ps.w.org/boldgrid-backup/assets/screenshot-14.png?rev=2199062\")
To help keep your backups organized, you can add titles and descriptions to each backup.
![\"Use](\"https://ps.w.org/boldgrid-backup/assets/screenshot-15.png?rev=2009431\")
Use the Backup Browser to view what files are contained in each of your backups.
![\"You](\"https://ps.w.org/boldgrid-backup/assets/screenshot-16.png?rev=2009431\")
You can also use the Backup Browser to see which database tables are included in the backup and compare the # records to your current database.
![\"The](\"https://ps.w.org/boldgrid-backup/assets/screenshot-17.png?rev=2199062\")
The right sidebar of the Backup Archive Details page shows information about a backup, including who made the backup, what was backed up, how long the backup took, and more.
![\"You](\"https://ps.w.org/boldgrid-backup/assets/screenshot-18.png?rev=2199062\")
You can configure retention settings (only keep X number of backups) so that disk space used by your Web Server and/or your FTP/SFTP to store backups does not grow out of control.
![\"For](\"https://ps.w.org/boldgrid-backup/assets/screenshot-19.png?rev=2199062\")
For backups you don\'t want to be deleted by your retention settings, you can configure them to be saved and not deleted when the retention process deletes the backup.
![\"Migrating](\"https://ps.w.org/boldgrid-backup/assets/screenshot-20.png?rev=2199062\")
Migrating websites from one host to another only takes a few steps. On the source server, generate a protected link for which a backup can be downloaded. Then, on the destination server, upload a backup using that protected link. All that\'s left is clicking restore!
Couldn't Be Better
\n \n\n By 
Otimo.
\n \n\n By 
Great plugin
\n \n\n By 
A great plug in
\n \n\n By 
Works very well
\n \n\n By 
The only backup and migration tool you need.
\n \n\n By
backups
\n \n\n By 
Excellent WP tool!
\n \n\n By 
It works
\n \n\n By 
Marvelous
\n \n\n By 
weForms- The Best Contact Form Builder plugin for WordPress
\nOne of the most important features of a WordPress form plugin is the ability to quickly and easily create a form. That’s why we built our product to be the easiest form builder available.
\nweForms enables you to create WordPress forms in a matter of minutes. With numerous templates and an easy to use drag and drop interface, your form can go from concept to reality instantly. Live preview functions allow you to see what your users will see with a click of a button.
\nBeyond the functionality of building the form itself, weForms boasts more than 20 custom fields. These range from address fields to multi-select boxes. All of the fields can help you build forms to collect various types of user information for things such as a support ticket, event registration, or job application. You can also see all of your users’ submissions right inside your WordPress dashboard for added convenience.
\nweForms is an all-in-one form builder created for every skill level of user. Its minimalistic design is not only modern but also super fast and user-friendly. Everything works on a single page. Stop wasting time trying to find a developer to build a form, knock it out yourself in a matter of minutes!
\nQuick Overview of weForms
\n\nKey Features
\n- \n
- Unlimited Forms: Create as many forms as you want and collect all the data you need \n
- Predefined and Customizable Templates: Save time using our unique & customizable form templates \n
- Drag & Drop Builder: Build the form of your dream with its fully featured drag & drop form editing option \n
- Real-time Live Preview: Instantly preview your work in real-time \n
- Expiry Time: Set a form expiration date to automate your forms showing on a schedule \n
- Entry Restrictions: Limit the number of entries for each individual form by setting the maximum form submission limit. Perfect for event registration! \n
- One Page Submission: Form submission occurs without a page refresh using AJAX, making submissions instant \n
- Field Customization Options: Customize the form fields available with tons of options to best fit your needs. \n
- Form Redirection: Upon form submission easily redirect your users to any page of your choice \n
- Form Submission Notification: Use our built-in email notifications to never miss a beat when your users submit a form on your website \n
- Manage Form Submissions: Manage the submission of forms to collect data without the hassle of backend coding \n
- Import or Export Forms: Use the quick form exporting and importing option that lets you start from where you left off or save your data offline \n
- Mobile-friendly forms: weForms is mobile-friendly and responsive, making it easy for your users to submit forms via computer, mobile phone, or tablet \n
- Mail support: Get complete mail support feature in the form of customize mails and HTML email template \n
- Email submission data: Connect your forms to several of our integrated email services to get form submission data in emails \n
- Anti-spam & reCaptcha: Get rid of spam entries with reCaptcha or through our other integrated partners, like Human Presence to eliminate spam messages and registrations with WordPress forms \n
- Slack Integrations: Get notified through your Slack account whenever any user submits a form using weForms \n
- Column Field: Build your form the way you want by adding any field into our column field. Resize them the way you need them to create a dynamic form for your website \n
KEY ATTRIBUTES – WEFORMS STANDS OUT FROM THE CROWD!
\nDRAG & DROP FORM BUILDER WITH LIVE FORM PREVIEW
\nWith weForms smooth drag and drop form builder, create any type of form you need within minutes. You aren’t required to know a single line of code to create a powerful form with the help of our intuitive drag & drop form building feature. Simply drag & drop the fields you want to add from the panel of the available form fields. Instantly live preview the form that you have created in the frontend.
\nMOBILE RESPONSIVE FORMS FOR ALL OF YOUR DEVICES
\nHaving a responsive contact form on your WordPress is a must for a user-friendly experience. weForms ensures that your created forms are all well-responsive even on all mobile devices. This will help you increase form conversion rates and customer satisfaction.
\nPRE-DEFINED FORM TEMPLATES FOR QUICK ACCESS
\nIn a lot of cases, you might not need to build a form from scratch. A simple form with some predefined fields would fit all of your needs. With weForms, you get a variety of pre-built form templates that fit a multitude of use cases, helping you to capture leads easier and faster.
\nweForms predefined form templates include: Registration forms, Application forms, Payment forms, Reservations forms, Poll and Feedback forms, Request forms, and Event Registration forms.
\nADD WEFORMS WORDPRESS CONTACT FORMS USING GUTENBERG
\nEasily add your forms in the WordPress editor with the weForms block. When users want to publish forms on a page, they can simply select it from the drop-down present in the dedicated weForms block for Gutenberg. The entire form automatically renders within the editor as well as on page. It’s much easier than manually copying and pasting shortcodes! This saves you a ton of time and clicks, but for those who prefer shortcodes, you can still add forms to your pages with other page builders too.
\nSUPER FAST, SUPERCHARGED WEBSITE FORMS
\nWhen it comes to the speed of submitting a form from the frontend or in the backend, weForms does the job faster than any other form builder. Regardless if it is sent via computer, phone, or tablet, you can rest assured it will be quick!
\nTHE ONLY LIMITATION IS YOUR IMAGINATION
\nTaking a form from concept to reality is a walk in the park with weForms. Quickly design any type of form you can think of using our easy to use builder with plenty of field options & a beautiful drag and drop user interface.
\nInstantly preview the form you built and make changes right away. Improve the quality and standard of your form-building process with weForms.
\nCUSTOM FIELDS TO MAKE THE MOST OF YOUR CONTACT FORMS
\nWhile building a form with weForms custom field, anyone, even those without any prior coding knowledge are able to create great forms. From check-box to image upload fields, or radio button to the signature field, weForms provides you with every great form field. This also includes the column field option to make your forms look great and flow beautifully.
\nEXTEND & CUSTOMIZE YOUR CONTACT FORMS WITHOUT A HITCH
\nAs an advanced user, you might want your form to look or perform in a certain way. This is where the customization capabilities of weForms will come in handy. With its custom CSS, HTML blocks, and section dividers, users are able to customize their forms exactly the way they like. weForms also has heaps of filters and hooks that help developers easily extend a contact forms functionality.
\nEASY FORM IMPORT & EXPORT FACILITY
\nMoving from a different form provider? Easily import your forms in a JSON format or from built-in form import tools. Looking to export out your form or the submissions? We have you covered with both form submissions exports as well as a JSON export of the form itself.
\nFORM ENTRY RESTRICTIONS, SCHEDULING, AND EXPIRATION TIMES
\nHave full control over your forms and when they can be used! Create exclusive campaigns by allowing only a limited number of entries, controlling user access, and adding a start and expiration date. Form with an expiration date will automatically disappear after the time you want.
\nCUSTOMIZABLE EMAIL NOTIFICATIONS FOR ADMINS
\nStay alert with every submission. Create multiple custom notifications on each form with advanced mail forwarding and quickly create templates with hooks.
\nFORM REDIRECTION PAGE OR CUSTOM URL
\nWhen a user completes a form, you can redirect them with a custom link or to a page to guide the user through your desired workflow. It’s very useful when you want to direct the visitor’s attention to additional pages, or just creatively customize your submission received messaging.
\nOTHER NOTABLE WEFORMS ATTRIBUTES INCLUDE
\n- \n
- ReCaptcha and Human Presence Anti-Spam integrations to ensure an extra layer of security for forms.
\n*The ability to sync email form data with numerous email integrations \n - Multi-step and Multi-part Forms to break up the submission process for your users. \n
- Geolocation & SMS notifications to help improve your response times and data. \n
- Much, much more. \n
DON’T JUST TAKE OUR WORD FOR IT, HERE IS WHAT SOME OF THE BIGGEST NAMES IN THE COMMUNITY HAVE TO SAY
\n\n\nweForms is both easy and super fast, even the completely new users can build beautiful WordPress forms without any hassle. – WP Arena
\nThe free version offers a host of useful and advanced features that are not available in many existing alternatives. – Cloudways
\nWe tried to do some experimentation with weForms and to our utter delight, it looks like we can build all types of contact forms using it! – WPBlog
\n
MODULES & INTEGRATIONS FOR WEFORMS
\nEmail Marketing Integrations
\n* MailChimp: This integration makes the already powerful form builder your ultimate lead generation source for one of the best email marketing tools available.
\n* AWeber: Connect weForms with AWeber mail lists to reach submitters via email campaigns. Easily grow your contact base and do more with emails.
\n* Constant Contact: Make your email marketing powerful and simple using Constant Contact integration for weForms.
\n* Campaign Monitor: Boost your email marketing by integrating weForms with Campaign Monitor. Quickly generate more leads by syncing your mail lists with those who post form submissions.
\n* GetResponse:Supercharge your email marketing to boost your business by integrating it with weForms.
\n* MailPoet: It provides you the experience of using the best WordPress Newsletter plugin with the best Form Builder weForms.
\n* ConvertKit: Quickly boost your business by generating more leads, syncing the mail lists with submissions by integrating them with weForms.
Payment Integrations
\n* Paypal: Collect PayPal payments with your forms easily by integrating it with weForms.
\n* Stripe: Collect credit card payments safely and quickly by integrating Stripe with your forms
Productivity Tool Integrations and Modules
\n* Google Analytics: Provides a powerful & complete marketing analytics solution for businesses of all sizes using forms.
\n* Zapier: The easiest and most popular automated workflow management system on the internet integrates with the fastest form builder.
\n* Google Sheets: This integration for weForms will give you the ease of managing submitted information in the familiar Google Sheets environment.
\n* Trello: Instantly create task cards from your form submissions by enabling this module.
\n* Calculation: Enable your form to have calculation capabilities with your numeric fields
\n* PDF Form Submission: Enable this module to get a better printable PDF version of all your collected submission forms.
\n* Quiz: Create simple yet engaging quiz forms and keep your audiences hooked getting a lot of shares by enabling this module.
\n* Slack: Notify your team instantly in Slack when someone submits an entry to your forms created with weForms enabling this free integration.
\n* SMS Notification: Enable the module to get a notification through SMS every time a form submission occurs.
\n* File Upload: Allow users to attach files of whatever type you specify to streamline application processes, add images and more.
CRM Integrations
\n* Salesforce: Integrate with weForms to instantly enhance your user list building more customers and more interactions.
\n* WP ERP: Integrate your forms with WordPress CRM contact lists & instantly get tons of new leads who you can convert as subscribers or customers.
\n* HubSpot: Get more opportunities to make deals at your fingertips by integrating HubSpot with weForms and instantly enhance your contact list.
\n* Zoho: Enabling it gets you better sales-qualified lead generation. Simply connect it once, pass data instantly & start tracing form subscribers from your CRM as they move through the sales funnel.
WEFORMS PRO FEATURES ARE AWESOME!
\nNeed more features? Then you might want to upgrade to one of our weForms Pro versions. This amazing contact form builder for WordPress has 4 convenient and affordable plans to strengthen your form building and lead capture functionalities.
\nTHE FOUR PRO PLANS:
\n- \n
- Personal \n
- Business \n
- Professional \n
- Developer \n
These tailored plans consists of some highly essential & cutting-edge PRO features and integrations that include:
\n- \n
- Advanced fields \n
- Conditional logic \n
- Multistep form \n
- Webhooks \n
- Country List Field \n
- File uploader \n
- PDF form submissions \n
- Geolocation tracking \n
- SMS notification \n
- Email Marketing Integrations\n
- \n
- MailChimp \n
- MailPoet \n
- AWeber \n
- Constant Contact \n
- Campaign Monitor \n
- Get Response \n
- Convert Kit \n
\n - Productivity Tool Integration\n
- \n
- Google Analytics \n
- Zapier \n
- Trello \n
\n - Payment Integration\n
- \n
- Paypal \n
- Stripe \n
\n - CRM Integration\n
- \n
- Salesforce \n
- Zoho \n
- Hubspot \n
\n
Learn more about our weForms Pro Features now!
\n\";s:12:\"installation\";s:609:\"This section describes how to install the plugin and get it working.
\ne.g.
\n- \n
- Upload the plugin files to the
/wp-content/plugins/weformsdirectory, or install the plugin through the WordPress plugins screen directly. \n - Activate the plugin through the ‘Plugins’ screen in WordPress \n
- Use the
weForms->Settingsscreen to configure the plugin \n - (Make your instructions match the desired user flow for activating and installing your plugin. Include any steps that might be needed for explanatory purposes) \n
\n
Yes, you can customize the plugins language using poedit with the provided pot file.
\n\n\n
Contact form created by weForms is mobile responsive and looks beautiful in any device.
\n\n\n
We have built-in integration with reCaptcha. So your forms are protected from the evil bots.
\n\n\n
You can set as many email notifications as possible with weForms.
\n\n\n
weForms is the most beginner friendly and fastest WordPress contact form plugin available and getting started is so easy!
\n\n\n\";s:9:\"changelog\";s:20886:\"Version 1.6.13 (02 March, 2022)
\n- \n
- Fix: Fixes placeholders being blank on the frontend. \n
- Fix: Fixes issue setting multiple field tag in notification body. \n
- Fix: Fixes and adds logic for support url in help section. \n
Version 1.6.12 (26 January, 2022)
\n- \n
- Fix: Fixes form previews when using block based themes. \n
Version 1.6.11 (05 January, 2022)
\n- \n
- Fix: Fixes fatal error in translator. \n
Version 1.6.10 (05 January, 2022)
\n- \n
- Update: Axios from 0.21.1 to 0.21.2. \n
- Update: Set-value from 3.0.2 to 4.0.1. \n
- Update: Added data-sytle to all fields. \n
- Fix: Enforce date format from datepicker. \n
- Fix: Changed entry after submission to form setting from global setting. \n
- Fix: Removed id from entry table view. \n
- Fix: Entry details show option and value selected. \n
- Improvement: Address fields in notifications now accepts value: tags for selection fields \n
Version 1.6.9 (15 September, 2021)
\n- \n
- Fix: PHP 8.0 Emogrifier updates \n
- Fix: Transaction page link updated to weforms site \n
- Fix: Entry Field Names update on form save when changed \n
- Fix: Using Vue.js minified file for production \n
- Fix: Google Maps integration provides address in notification \n
- Update: Field Authentication updates \n
- Update: Dependancy updates \n
- Impovement: Sprout Invoices integration multiple line items and payment options \n
Version 1.6.8 (10 June, 2021)
\n- \n
- Fix: weSerialize not extended \n
Version 1.6.7 (26 April, 2021)
\n- \n
- Fix: PHP 8.0 form submission issues fixes and removal of admin notice callback \n
- Fix: Transaction table id matching entry id and addition of entry after submission fixes \n
- Fix: Added weSerialize wapper for backward compatbility with weSerialize \n
- Fix: Admin notice form import fixes \n
Version 1.6.6 (13 April, 2021)
\n- \n
- Fix: Front End report link fixes \n
- Fix: Signature Displays in Entries \n
- Update: jQuery updates for Columns \n
Version 1.6.5 (18 February, 2021)
\n- \n
- Fix: Updated admin notices to better conform to WordPress design standards, and configured them to only show on WeForms pages. \n
- Update: Removed FortressDB admin notice. \n
- Update: Updated axios dependancy \n
Version 1.6.4 (23 December, 2020)
\n- \n
- Fix: Added spreadsheet functione escaping to prevent CSV exploits. [#50] (https://github.com/BoldGrid/weforms/pull/50) \n
- Update: Update Node Packages \n
Version 1.6.3 (11 November, 2020)
\n- \n
- Update: Sprout Invoices Integration \n
Version 1.6.2 (11 November, 2020)
\n- \n
- Update: Sprout Invoices Integration \n
Version 1.6.1 (11 November, 2020)
\n- \n
- Update: Sprout Invoices Integration \n
Version 1.6.0 (11 November, 2020)
\n- \n
- Update: Sprout Invoices Integration \n
Version 1.5.5 (29 October, 2020)
\n- \n
- Fix: Quick Vulnerability Fix \n
Version 1.5.4 (29 October, 2020)
\n- \n
- Fix: Quick Vulnerability Fix \n
Version 1.5.3 (20 October, 2020)
\n- \n
- Fix: Fixed bug causing a blank screen to appear for some users \n
Version 1.5.2 (13 October, 2020)
\n- \n
- Fix: Fixed JS Issues. \n
- Fix: Email Header Formatting. \n
- Update: Added Fortress DB Integration. \n
Version 1.5.1 (1 September, 2020)
\n- \n
- Fix: Fixed Fortress DB tab. \n
Version 1.5.0 (1 September, 2020)
\n- \n
- Update: Added Fortress DB and Conditional Banner. \n
- Update: Removed Diagnostic Pop Up. \n
- Fix: JSON import issue fixed. \n
- Fix: Double Column not working, issue fixed. \n
- Fix: File Upload issue fixed. \n
- Fix: Signature field issue fixed. \n
Version 1.4.9 (30 June, 2020)
\n- \n
- Update: Added a privacy page. \n
Version 1.4.8 (30 March, 2020)
\n- \n
- Fix: Fixed escaping of select options when adding a form to a page. \n
- Fix: Fixed Email notification formatting issue. \n
- Fix: Fixed column field resize issue. \n
- Fix: Fixes Array to string conversion warning with address field. \n
- Fix: Replace an instance of non-existant. \n
- Fix: Conflict with kingcomposer. \n
- Fix: Recaptcha token expire. \n
Version 1.4.7 (10 March, 2020)
\nUpdate: Links now point to new https://weformspro.com/
\nVersion 1.4.6 (20 February, 2020)
\n- \n
- Fix: image upload field issue \n
- Fix: widget not rendering properyly \n
- Fix: HTML Tags are not rendering the HTML format for the Radio or Checkbox Field \n
- Fix: submit issue with image and recaptcha. \n
Version 1.4.5 (31 January, 2020)
\n- \n
- Feature: Added Recaptcha v3 support \n
- Fix: Fixed Some regressions after phpcs fixes \n
Version 1.4.4 (14 January, 2020)
\n- \n
- Improvement: Imporve Code Quality \n
Version 1.4.3 (10 January, 2020)
\n- \n
- Fix: Field display issue in form entries page \n
- Fix: Hidden Field not working properly in builder \n
- Fix: Some Column field issue \n
- Fix: Sanitize and Escape data before saving and rendering \n
- Improvement: Add privacy policy in readme \n
Version 1.4.2 (18 November, 2019)
\n- \n
- Fix: Fixed Form was not showing immediately after duplicating. \n
- Fix: Fixed some column field issues. Closes #172 \n
- Fix: Fixed a csv export issue. closes #175 \n
Version 1.4.1 (24 September, 2019)
\n- \n
- New: Added Rest api \n
- Fix: Full name shows instead of first name in the email notification \n
- Fix: Dynamic value population – not saving value \n
Version 1.4.0 (17 June, 2019)
\n- \n
- Feature: Added GDPR Export and Delete Requests Forms. \n
- Fix: Multistep form: scroll to the top of the form when click on Next & Previous buttons. \n
Version 1.3.9 (10 May, 2019)
\n- \n
- Fix: Updated plugin description for WordPress.org \n
Version 1.3.8 (11 April, 2019)
\n- \n
- Feature: Added column field: Now, creating multi-column in a single row is super easy with weForms Column field. Just drag the column field in the builder area, configure columns number, column space and add any fields you want inside that Column field. \n
- Enhancement: Allow dynamic value population for hidden field. \n
- Fix: Address field country full name not showing in the entries & PDF. \n
Version 1.3.7 (14 February, 2019)
\n- \n
- Improvement: New design for form integrations tab. \n
- Improvement: Replace single checkbox with switch button. \n
- Fix: When duplicating a contact form, showing error
schedule_form of undefined. \n
Version 1.3.6 (17 January, 2019)
\n- \n
- Fix: Changed get countries function name as the same function exists in the professional version and there was a possibility to get an error. \n
Version 1.3.5 (16 January, 2019)
\n- \n
- Feature: As per user suggestion, we have added a status column for the form listing table. By this, the admin will be able to see whether the form is ‘Open’ or ‘Close’. In addition to that, the admin will also be able to view or show the reasons behind keeping a form open or close according to the 3 form submission restrictions (scheduling form, requiring login and limiting submission entries) from the form settings. \n
- Feature: As per client suggestion, we have added a “Created by” column on form listing table. This will allow the admin to know the creator of a form, their gravatar image and the date on which the form was created. \n
- Fix: Import description and settings from WP Forms. \n
- Fix: When viewing the entries, country short-name was displayed. With this release, we have changed the short-name to the full name. For example, Now it shows Canada instead of just showing CA. \n
- Fix: Improved submit button design for the form builder. \n
- Fix: Deleting form entries didn’t remove the media/file from the media library permanently. But now it does. \n
- Fix: Gutenberg block was not loading on edit post/page which has been fixed. \n
- Fix: On activating the WP User Frontend, the reCaptcha field of weForms did not work which has been fixed. \n
Version 1.3.4 (22 November, 2018)
\n- \n
- Fix: Undefined name field \n
- Fix: Shortcode popup form width fix \n
Version 1.3.3 (12 November, 2018)
\n- \n
- New: Design phone field \n
- Fix: Default input style issue of form builder \n
Version 1.3.2 (23 October, 2018)
\n- \n
- Fix: Calendar not showing on date field \n
- New: Use theme CSS option in form display settings \n
Version 1.3.1 (18 August, 2018)
\n- \n
- New: Added custom classes to make two or three columns form \n
- Fix: Sanitized name field \n
Version 1.3.0 (09 August, 2018)
\n- \n
- Fix: Form preview link fixed where site_url and home_url is different \n
- Fix: WPUF builder not loading properly is resolved \n
Version 1.2.9 (11 July, 2018)
\n- \n
- New: Integrate Dokan vendor contact form \n
- New: Added Form select media button weforms \n
- New: Added no-conflict mode to resolve Backend JS conflicts with other plugins \n
- New: Added Privacy Suggestion for GDPR \n
- Fix: Resolved conditional logic not working for custom_html and section_break \n
- Fix: Load weForms specific frontend css \n
- Fix: php 5.4 compatbility for bulk delete entry \n
- Fix: Fixed no buffer to delete warning \n
Version 1.2.8 (09 May, 2018)
\n- \n
- New: Show submitted form data in message after form submission \n
- New: Added device option in form entry data \n
- Improved: Nocaptcha recaptcha wasn’t working if allow_url_fopen was disabled, now it will. \n
Version 1.2.7 (22 April, 2018)
\n- \n
- New: Added weForms Guten block for Gutenberg \n
- Fix: Fixed Pagination issue in form entries \n
- Improved: Fixed entry data meta remains in database after deleting an entry \n
Version 1.2.6 (22 March, 2018)
\n- \n
- Improved: Added Missing text-domains \n
- Fix: Admin Notices from Form Builder Pages are removed. \n
- Fix: JavaScript conflicts with WP User Frontend are fixed. \n
- Fix: Form entries with UTF-8 charset were not exporting properly. \n
Version 1.2.5 (19 February, 2018)
\n- \n
- New: Added more starter form templates for use like Donation Form, Online Booking Form, Conference Proposal etc. \n
- Improved: Added dark theme support for recaptcha. \n
- Fix: Google map entry display template fixed. \n
Version 1.2.4 (28 December, 2017)
\n- \n
- Improved: External libraries extracted to a separate JavaScript file. This is going to reduce the requests count and improve loading time. Also now we are loading the minified version of all JavaScript file for production sites. \n
- Fix: ReCaptcha validation was giving a 400 error. Fixed that bug. \n
- Fix: Fixed undefined index error on field duplicate checking. \n
- Improved: Now we are loading upgrades on admin side only. \n
Version 1.2.3 (16 December, 2017)
\n- \n
- Improved: Now we are loading the shortcode for ajax requests as well, required for the integration of page builders. \n
Version 1.2.2 (19 November, 2017)
\n- \n
- New: Now you can set up the form in a way, so Email and Name fields value can be auto-populated from user’s WordPress profile when the user is logged. And those fields will get hidden on front-end. \n
- New: We’ve added trash functionality for entries. When you delete an entry, that will move to trash. And later you can delete those permanently or restore if you need. \n
- New: To help debug the integrations API error messages, we’ve added a custom error logging function and a log viewer. Can be found on
WP-Admin > weFroms > Tools > Logs\n - Improved: Sometimes, we need to show dynamic default or placeholder text on fields. Merge tag support for default and placeholder attribute added. \n
- Improved: When you edited a form and leaving the builder without saving, we’ve added a little warning to let you know, if you leave your changes are going to be discarded. \n
- Improved: To help you find the right form template easily, We’ve re-categorized the form templates. \n
Version 1.2.1 (8 November, 2017)
\n- \n
- New: We’ve added a rich text editor for notification email template editing area. It’s going to help you write better HTML email with less effort. \n
- Improved: Now you can decide if you would like to hide or show the empty fields on Entry Page. We’ve added a checkbox to toggle that. \n
- Improved: We’ve added a little filter on {all_fields} shortcode. When sending email notification it’s going to exclude all the empty fields. So it becomes more readable. \n
- Fix: There was some issue with CSV exporting. We fixed that. \n
Version 1.2.0 (30 October, 2017)
\n- \n
- New: We added a lot’s of ready to use form templates. So you can just select the form template you need and your form will be ready. \n
- New: Added an Entries page in admin menu. Now you can access the form entries directly without going through few clicks. \n
- New: MailPoet Integration added from premium version. We thought to give it away for free. \n
- New: Date / Time field added from premium version. As it’s a very commonly used field, it provides a lot more value in the free version. \n
- New: Pop-up/Modal form option added. Can be used through shortcode like
[weforms id=\"ID\" modal=\'true\' button=\'Open Form\']. \n - New: Dynamic field population added. Field options or default values can be pre-populated by hooks or query string. \n
- New: Unique entry checking for fields like email, phone, text, number, URL added. Now, you can prevent duplicate submissions if you want. \n
- Improved: Settings page re-designed. New settings page is more user friendly and easy to use. \n
- Fix: Previously created forms sometimes failed work with new features. We added a new filter, now all new features are going to work smoothly even with old forms. \n
- Fix: There was a small issue on showing validation error message on front-end. We’ve Fixed that. \n
Version 1.1.1 (3 October, 2017)
\n- \n
- Fix: Fatal error on completely new installation. As default form creation format has been changed, it was giving a fatal error. \n
Version 1.1.0 (2 October, 2017)
\n- \n
- New: Added WP ERP integration. You can subscribe a user to a contact group in ERP when submitting a form. \n
- New: Form sharing. You can share a form without inserting the shortcode to a page. A hashed URL will be provided for privacy. \n
- Improved: Removed WP User Frontend dependency. Now you can use weForms without requiring WPUF. \n
- Improved: Core API rewrites. Now it’s easier to manage the internals with more OOP code improvements. \n
- Improved: Every fields are now a separate class, and managed via a field manager class. Creating a new form field is way more easier than previous. \n
- Improved: Importer’s are managed by a separate importer manager class. \n
- Improved: The form templates are now more simpler to create. The modal template popup has been redesigned by grouping the templates and now shows a form preview image. \n
- Improved: Added autocomplete attributes to field attributes so form fills can detect the fields and auto-populate with related content. \n
- Fix: reCaptcha validtion wasn’t working. \n
v1.0.4 (5 September, 2017)
\n- \n
- [fix] Wrong reference of static $separator used. \n
v1.0.3 (30 August, 2017)
\n- \n
- [new] Gravity Forms Importer \n
- [new] Caldera Forms Importer \n
- [new] Ninja Forms Importer \n
- [new] WP Forms Forms Importer \n
- [new] Frontend Form Preview \n
- [new] Add form credit settings \n
- [fix] Notification mail shows level with Underscore between all words \n
- [fix] New columns added on entries listing page \n
v1.0.2 (24 August, 2017)
\n- \n
- [improved] Affiliate link tracking for plugin install \n
v1.0.1 (23 August, 2017)
\n- \n
- [improved] Added missing integration icons \n
- [fix] Email content type fixed \n
v1.0.0 (19 August, 2017)
\n- \n
- [new] Added reCaptcha support \n
- [new] Emailer class added for hookable email gateway support \n
- [new] Added support for google map in rendering entries \n
- [new] Added help page and premium contents \n
- [improved] Sync settings between weforms and wpuf map and recaptcha \n
- [improved] Routes moved to localize script, better hookability \n
- [fix] Form status checking in rendering \n
- [fix] Image and file upload and rendering issue fixed \n
v1.0.0-beta.3 (6 August, 2017)
\n- \n
- [fix] Fatal error on creating a new form \n
- [inhancement] Hide WPUF page installation and tracking prompt \n
v1.0.0-beta.2 (5 August, 2017)
\n- \n
- [fix] Padding in email template. Looks better now. \n
- [fix] Support name in “From Name” email notification. Fixes #16 \n
- [fix] Remove recaptcha “type” from settings page \n
- [fix] Other fields were not coming in export entries csv file \n
- [new] Import Contact form 7 forms into weForms ? \n
- [new] Create a default form upon installation \n
v1.0.0-beta.1 (1 August, 2017)
\n- \n
- First beta version \n
![\"How](\"https://ps.w.org/weforms/assets/screenshot-1.gif?rev=1721119\")
How it works
![\"The](\"https://ps.w.org/weforms/assets/screenshot-2.png?rev=1721119\")
The form listings
![\"Create](\"https://ps.w.org/weforms/assets/screenshot-3.png?rev=1721119\")
Create form from a range of pre-defined templates
![\"A](\"https://ps.w.org/weforms/assets/screenshot-4.png?rev=1721119\")
A single contact form with it\'s builder view
![\"Edit](\"https://ps.w.org/weforms/assets/screenshot-5.png?rev=1721119\")
Edit the field properties on the right side and see the changes instantly
![\"Form](\"https://ps.w.org/weforms/assets/screenshot-6.png?rev=1721119\")
Form settings
![\"Submission](\"https://ps.w.org/weforms/assets/screenshot-7.png?rev=1721119\")
Submission restriction settings of a form
![\"Form](\"https://ps.w.org/weforms/assets/screenshot-8.png?rev=1721119\")
Form display settings
![\"Create](\"https://ps.w.org/weforms/assets/screenshot-9.png?rev=1721119\")
Create and send unlimited email notifications to various destinations
![\"Email](\"https://ps.w.org/weforms/assets/screenshot-10.png?rev=1721119\")
Email notification settings
![\"Free](\"https://ps.w.org/weforms/assets/screenshot-11.png?rev=1721119\")
Free slack integration and various premium integrations
![\"Export](\"https://ps.w.org/weforms/assets/screenshot-12.png?rev=1721119\")
Export the forms, as well as the form entries (CSV).
![\"Import](\"https://ps.w.org/weforms/assets/screenshot-13.png?rev=1721119\")
Import forms, also import forms from various other plugins
![\"The](\"https://ps.w.org/weforms/assets/screenshot-14.png?rev=1721119\")
The help page
![\"Plugin](\"https://ps.w.org/weforms/assets/screenshot-15.png?rev=1721119\")
Plugin settings
![\"A](\"https://ps.w.org/weforms/assets/screenshot-16.png?rev=1721119\")
A simple contact form displayed on the site
![\"Event](\"https://ps.w.org/weforms/assets/screenshot-17.png?rev=1721119\")
Event registration form displayed on the site
Formulaire reçu imcomplet
\n \n\n By 
plugin is good but it can't save after update plugin
\n \n\n By 
Great Forms maker
\n \n\n By 
Does his function
\n \n\n By 
Razorpay payment Gateway Not include
\n \n\n By 
Easy to Install
\n \n\n By 
Good but missing one vital feature
\n \n\n By 
useless
\n \n\n By 
Great Plugin
\n \n\n By 
Nag, nag, nag
\n \n\n By 
W3 Total Cache (W3TC) improves the SEO, Core Web Vitals and overall user experience of your site by increasing website performance and reducing load times by leveraging features like content delivery network (CDN) integration and the latest best practices.
\nW3TC is the only web host agnostic Web Performance Optimization (WPO) framework for WordPress trusted by millions of publishers, web developers, and web hosts worldwide for more than a decade. It is the total performance solution for optimizing WordPress Websites.
\nAn inside look:
\n\n
BENEFITS
\n- \n
- Improvements in search engine result page rankings, especially for mobile-friendly websites and sites that use SSL \n
- At least 10x improvement in overall site performance (Grade A in WebPagetest or significant Google Page Speed improvements) when fully configured \n
- Improved conversion rates and “site performance” which affect your site’s rank on Google.com \n
- “Instant” repeat page views: browser caching \n
- Optimized progressive render: pages start rendering quickly and can be interacted with more quickly \n
- Reduced page load time: increased visitor time on site; visitors view more pages \n
- Improved web server performance; sustain high traffic periods \n
- Up to 80% bandwidth savings when you minify HTML, minify CSS and minify JS files. \n
KEY FEATURES
\n- \n
- Compatible with shared hosting, virtual private / dedicated servers and dedicated servers / clusters \n
- Transparent content delivery network (CDN) management with Media Library, theme files and WordPress itself \n
- Mobile support: respective caching of pages by referrer or groups of user agents including theme switching for groups of referrers or user agents \n
- Accelerated Mobile Pages (AMP) support \n
- Secure Socket Layer (SSL/TLS) support \n
- Caching of (minified and compressed) pages and posts in memory or on disk or on (FSD) CDN (by user agent group) \n
- Caching of (minified and compressed) CSS and JavaScript in memory, on disk or on CDN \n
- Caching of feeds (site, categories, tags, comments, search results) in memory or on disk or on CDN \n
- Caching of search results pages (i.e. URIs with query string variables) in memory or on disk \n
- Caching of database objects in memory or on disk \n
- Caching of objects in memory or on disk \n
- Caching of fragments in memory or on disk \n
- Caching methods include local Disk, Redis, Memcached, APC, APCu, eAccelerator, XCache, and WinCache \n
- Minify CSS, Minify JavaScript and Minify HTML with granular control \n
- Minification of posts and pages and RSS feeds \n
- Minification of inline, embedded or 3rd party JavaScript with automated updates to assets \n
- Minification of inline, embedded or 3rd party CSS with automated updates to assets \n
- Defer non critical CSS and Javascript for rendering pages faster than ever before \n
- Defer offscreen images using Lazy Load to improve the user experience \n
- Browser caching using cache-control, future expire headers and entity tags (ETag) with “cache-busting” \n
- JavaScript grouping by template (home page, post page etc) with embed location control \n
- Non-blocking JavaScript embedding \n
- Import post attachments directly into the Media Library (and CDN) \n
- Leverage our multiple CDN integrations to optimize images \n
- WP-CLI support for cache purging, query string updating and more \n
- Various security features to help ensure website safety \n
- Caching statistics for performance insights of any enabled feature \n
- Extension framework for customization or extensibility for Cloudflare, WPML and much more \n
- Reverse proxy integration via Nginx or Varnish \n
- Image Service API extension provides WebP image format conversion from common image formats (on upload and on demand) \n
Speed up your site tremendously, improve core web vitals and the overall user experience for your visitors without having to change your WordPress host, theme, plugins or your content production workflow.
\nWhat users have to say:
\n- \n
- Read testimonials from W3TC users. \n
Who do I thank for all of this?
\nIt’s quite difficult to recall all of the innovators that have shared their thoughts, code and experiences in the blogosphere over the years, but here are some names to get you started:
\n- \n
- Steve Souders \n
- Steve Clay \n
- Ryan Grove \n
- Nicholas Zakas \n
- Ryan Dean \n
- Andrei Zmievski \n
- George Schlossnagle \n
- Daniel Cowgill \n
- Rasmus Lerdorf \n
- Gopal Vijayaraghavan \n
- Bart Vanbraban \n
- mOo \n
Please reach out to all of these people and support their projects if you’re so inclined.
\n\";s:12:\"installation\";s:4384:\"- \n
- Deactivate and uninstall any other caching plugin you may be using. Pay special attention if you have customized the rewrite rules for fancy permalinks, have previously installed a caching plugin or have any browser caching rules as W3TC will automate management of all best practices. Also make sure wp-content/ and wp-content/uploads/ (temporarily) have 777 permissions before proceeding, e.g. in the terminal:
# chmod 777 /var/www/vhosts/domain.com/httpdocs/wp-content/using your web hosting control panel or your FTP / SSH account. \n - Login as an administrator to your WordPress Admin account. Using the “Add New” menu option under the “Plugins” section of the navigation, you can either search for: w3 total cache or if you’ve downloaded the plugin already, click the “Upload” link, find the .zip file you download and then click “Install Now”. Or you can unzip and FTP upload the plugin to your plugins directory (wp-content/plugins/). In either case, when done wp-content/plugins/w3-total-cache/ should exist. \n
- Locate and activate the plugin on the “Plugins” page. Page caching will automatically be running in basic mode. Set the permissions of wp-content and wp-content/uploads back to 755, e.g. in the terminal:
# chmod 755 /var/www/vhosts/domain.com/httpdocs/wp-content/. \n - Now click the “Settings” link to proceed to the “General Settings” tab; in most cases, “disk enhanced” mode for page cache is a “good” starting point. \n
- The “Compatibility mode” option found in the advanced section of the “Page Cache Settings” tab will enable functionality that optimizes the interoperablity of caching with WordPress, is disabled by default, but highly recommended. Years of testing in hundreds of thousands of installations have helped us learn how to make caching behave well with WordPress. The tradeoff is that disk enhanced page cache performance under load tests will be decreased by ~20% at scale. \n
- Recommended: On the “Minify Settings” tab, all of the recommended settings are preset. If auto mode causes issues with your web site’s layout, switch to manual mode and use the help button to simplify discovery of your CSS and JS files and groups. Pay close attention to the method and location of your JS group embeddings. See the plugin’s FAQ for more information on usage. \n
- Recommended: On the “Browser Cache” tab, HTTP compression is enabled by default. Make sure to enable other options to suit your goals. \n
- Recommended: If you already have a content delivery network (CDN) provider, proceed to the “Content Delivery Network” tab and populate the fields and set your preferences. If you do not use the Media Library, you will need to import your images etc into the default locations. Use the Media Library Import Tool on the “Content Delivery Network” tab to perform this task. If you do not have a CDN provider, you can still improve your site’s performance using the “Self-hosted” method. On your own server, create a subdomain and matching DNS Zone record; e.g. static.domain.com and configure FTP options on the “Content Delivery Network” tab accordingly. Be sure to FTP upload the appropriate files, using the available upload buttons. \n
- Optional: On the “Database Cache” tab, the recommended settings are preset. If using a shared hosting account use the “disk” method with caution, the response time of the disk may not be fast enough, so this option is disabled by default. Try object caching instead for shared hosting. \n
- Optional: On the “Object Cache” tab, all of the recommended settings are preset. If using a shared hosting account use the “disk” method with caution, the response time of the disk may not be fast enough, so this option is disabled by default. Test this option with and without database cache to ensure that it provides a performance increase. \n
- Optional: On the “User Agent Groups” tab, specify any user agents, like mobile phones if a mobile theme is used. \n
\n
Search engines like Google, measure and factor in the speed of web sites in their ranking algorithm. When they recommend a site they want to make sure users find what they’re looking for quickly. So in effect you and Google should have the same objective.
\nSpeed is among the most significant success factors web sites face. In fact, your site’s speed directly affects your income (revenue) — it’s a fact. Some high traffic sites conducted research and uncovered the following:
\n- \n
- Google.com: +500 ms (speed decrease) -> -20% traffic loss [1] \n
- Yahoo.com: +400 ms (speed decrease) -> -5-9% full-page traffic loss (visitor left before the page finished loading) [2] \n
- Amazon.com: +100 ms (speed decrease) -> -1% sales loss [1] \n
A thousandth of a second is not a long time, yet the impact is quite significant. Even if you’re not a large company (or just hope to become one), a loss is still a loss. W3 Total Cache is your solution for faster websites, happier visitors and better results.
\nMany of the other consequences of poor performance were discovered more than a decade ago:
\n- \n
- Lower perceived credibility (Fogg et al. 2001) \n
- Lower perceived quality (Bouch, Kuchinsky, and Bhatti 2000) \n
- Increased user frustration (Ceaparu et al. 2004) \n
- Increased blood pressure (Scheirer et al. 2002) \n
- Reduced flow rates (Novak, Hoffman, and Yung 200) \n
- Reduced conversion rates (Akamai 2007) \n
- Increased exit rates (Nielsen 2000) \n
- Are perceived as less interesting (Ramsay, Barbesi, and Preece 1998) \n
- Are perceived as less attractive (Skadberg and Kimmel 2004) \n
There are a number of resources that have been documenting the role of performance in success on the web, W3 Total Cache exists to give you a framework to tune your application or site without having to do years of research.
\n\n\n
It’s a complete framework. Most cache plugins available do a great job at achieving a couple of performance gains. Total Cache is different because it remedies numerous performance reducing aspects of any web site. It goes farther than the basics, beyond merely reducing CPU usage (load) or bandwidth consumption for HTML pages. Equally important, the plugin requires no theme modifications, modifications to your .htaccess (mod_rewrite rules) or programming compromises to get started. Most importantly, it’s the only plugin designed to optimize all practical hosting environments small or large. The options are many and setup is easy.
\n\n\n
Rarely do readers take the time to complain. They typically just stop browsing earlier than you’d prefer and may not return altogether. This is the only plugin specifically designed to make sure that all aspects of your site are as fast as possible. Google is placing more emphasis on the speed of a site as a factor in rankings; this plugin helps with that too.
\nIt’s in every web site owner’s best interest is to make sure that the performance of your site is not hindering its success.
\n\n\n
To use all features in the suite, a minimum of version WordPress 3.8 with PHP 5.6 is required. Earlier versions will benefit from our Media Library Importer to get them back on the upgrade path and into a CDN of their choosing.
\n\n\n
Great question. W3 Total Cache uses several open source tools to attempt to combine and optimize CSS, JavaScript and HTML etc. Unfortunately some trial and error is required on the part of developers is required to make sure that their code can be successfully minified with the various libraries W3 Total Cache supports. Even still, if developers do test their code thoroughly, they cannot be sure that interoperability with other code your site may have. This fault does not lie with any single party here, because there are thousands of plugins and theme combinations that a given site can have, there are millions of possible combinations of CSS, JavaScript etc.
\nA good rule of thumb is to try auto mode, work with a developer to identify the code that is not compatible and start with combine only mode (the safest optimization) and increase the optimization to the point just before functionality (JavaScript) or user interface / layout (CSS) breaks in your site.
\nWe’re always working to make this more simple and straight forward in future releases, but this is not an undertaking we can realize on our own. When you find a plugin, theme or file that is not compatible with minification reach out to the developer and ask them either to provide a minified version with their distribution or otherwise make sure their code is minification-friendly.
\n\n\n
On the contrary, as with any other action a user can perform on a site, faster performance will encourage more of it. The cache is so quickly rebuilt in memory that it’s no trouble to show visitors the most current version of a post that’s experiencing Digg, Slashdot, Drudge Report, Yahoo Buzz or Twitter effect.
\n\n\n
No, on the contrary if you use the minify settings you will improve their performance by several times.
\n\n\n
Indeed it does.
\n\n\n
Yes.
\n\n\n
Yes, indirectly – if you have a lot of bloggers working with you, you will find that it feels like you have a server dedicated only to WP Admin once this plugin is enabled; the result, increased productivity.
\n\n\n
We are aware of no incompatibilities with apache 1.3+, nginx 0.7+, IIS 5+ or litespeed 4.0.2+. If there’s a web server you feel we should be actively testing (e.g. lighttpd), we’re interested in hearing.
\n\n\n
Yes, built from the ground up with scale and current hosting paradigms in mind.
\n\n\n
The media library import tool is for old or “messy” WordPress installations that have attachments (images etc in posts or pages) scattered about the web server or “hot linked” to 3rd party sites instead of properly using the media library.
\nThe tool will scan your posts and pages for the cases above and copy them to your media library, update your posts to use the link addresses and produce a .htaccess file containing the list of of permanent redirects, so search engines can find the files in their new location.
\nYou should backup your database before performing this operation.
\n\n\n
Use the “Help” button available on the Minify settings tab. Once open, the tool will look for and populate the CSS and JS files used in each template of the site for the active theme. To then add a file to the minify settings, click the checkbox next to that file. The embed location of JS files can also be specified to improve page render performance. Minify settings for all installed themes can be managed from the tool as well by selecting the theme from the drop down menu. Once done configuring minify settings, click the apply and close button, then save settings in the Minify settings tab.
\n\n\n
Technically no, a CDN is a high performance cache that stores static assets (your theme files, media library etc) in various locations throughout the world in order to provide low latency access to them by readers in those regions. Use Total Cache to accelerate your site by putting your content closer to your users with our many CDN integrations including Cloudflare, StackPath, AWS and more.
\n\n\n
Login to your CDN providers control panel or account management area. Following any set up steps they provide, create a new “pull zone” or “bucket” for your site’s domain name. If there’s a set up wizard or any troubleshooting tips your provider offers, be sure to review them. In the CDN tab of the plugin, enter the hostname your CDN provider provided in the “replace site’s hostname with” field. You should always do a quick check by opening a test file from the CDN hostname, e.g. http://cdn.domain.com/favicon.ico. Troubleshoot with your CDN provider until this test is successful.
\nNow go to the General tab and click the checkbox and save the settings to enable CDN functionality and empty the cache for the changes to take effect.
\n\n\n
First create an S3 account (unless using origin pull); it may take several hours for your account credentials to be functional. Next, you need to obtain your “Access key ID” and “Secret key” from the “Access Credentials” section of the “Security Credentials” page of “My Account.” Make sure the status is “active.” Next, make sure that “Amazon Simple Storage Service (Amazon S3)” is the selected “CDN type” on the “General Settings” tab, then save the changes. Now on the “Content Delivery Network Settings” tab enter your “Access key,” “Secret key” and enter a name (avoid special characters and spaces) for your bucket in the “Create a bucket” field by clicking the button of the same name. If using an existing bucket simply specify the bucket name in the “Bucket” field. Click the “Test S3 Upload” button and make sure that the test is successful, if not check your settings and try again. Save your settings.
\nUnless you wish to use CloudFront, you’re almost done, skip to the next paragraph if you’re using CloudFront. Go to the “General Settings” tab and click the “Enable” checkbox and save the settings to enable CDN functionality. Empty the cache for the changes to take effect. If preview mode is active you will need to “deploy” your changes for them to take effect.
\nTo use CloudFront, perform all of the steps above, except select the “Amazon CloudFront” “CDN type” in the “Content Delivery Network” section of the “General Settings” tab. When creating a new bucket, the distribution ID will automatically be populated. Otherwise, proceed to the AWS Management Console and create a new distribution: select the S3 Bucket you created earlier as the “Origin,” enter a CNAME if you wish to add one or more to your DNS Zone. Make sure that “Distribution Status” is enabled and “State” is deployed. Now on “Content Delivery Network” tab of the plugin, copy the subdomain found in the AWS Management Console and enter the CNAME used for the distribution in the “CNAME” field.
\nYou may optionally, specify up to 10 hostnames to use rather than the default hostname, doing so will improve the render performance of your site’s pages. Additional hostnames should also be specified in the settings for the distribution you’re using in the AWS Management Console.
\nNow go to the General tab and click the “Enable” checkbox and save the settings to enable CDN functionality and empty the cache for the changes to take effect. If preview mode is active you will need to “deploy” your changes for them to take effect.
\n\n\n
First create an account. Next, in the “Content Delivery Network” section of the “General Settings” tab, select Rackspace Cloud Files as the “CDN Type.” Now, in the “Configuration” section of the “Content Delivery Network” tab, enter the “Username” and “API key” associated with your account (found in the API Access section of the rackspace cloud control panel) in the respective fields. Next enter a name for the container to use (avoid special characters and spaces). If the operation is successful, the container’s ID will automatically appear in the “Replace site’s hostname with” field. You may optionally, specify the container name and container ID of an existing container if you wish. Click the “Test Cloud Files Upload” button and make sure that the test is successful, if not check your settings and try again. Save your settings. You’re now ready to export your media library, theme and any other files to the CDN.
\nYou may optionally, specify up to 10 hostnames to use rather than the default hostname, doing so will improve the render performance of your site’s pages.
\nNow go to the General tab and click the “Enable” checkbox and save the settings to enable CDN functionality and empty the cache for the changes to take effect. If preview mode is active you will need to “deploy” your changes for them to take effect.
\n\n\n
If the domain name of your site has changed, this tool is useful in updating your posts and pages to use the current addresses. For example, if your site used to be www.domain.com, and you decided to change it to domain.com, the result would either be many “broken” images or many unnecessary redirects (which slow down the visitor’s browsing experience). You can use this tool to correct this and similar cases. Correcting the URLs of your images also allows the plugin to do a better job of determining which images are actually hosted with the CDN.
\nAs always, it never hurts to back up your database first.
\n\n\n
Captcha and recaptcha will work fine, however you will need to prevent any pages with forms from being cached. Add the page’s URI to the “Never cache the following pages” box on the Page Cache Settings tab.
\n\n\n
Yes. Follow these steps:
\n- \n
- Enable dynamic loading of ratings by checking GD Star Rating -> Settings -> Features “Cache support option” \n
- If Database cache enabled in W3 Total Cache add
wp_gdsrto “Ignored query stems” field in the Database Cache settings tab, otherwise ratings will not updated after voting \n - Empty all caches \n
\n
If a theme or it’s files use the call php_flush() or function flush() that will interfere with the plugins normal operation; making the plugin send cached files before essential operations have finished. The flush() call is no longer necessary and should be removed.
\n
Add /.+ to page cache “Never cache the following pages” option on the page cache settings tab.
\n
First, make sure the plugin is not active (disabled) network-wide. Then make sure it’s deactivated network-wide. Now you should be able to successful upgrade without breaking your site.
\n\n\n
The plugin uses WordPress FileSystem functionality to write to files. It checks if the file owner, file owner group of created files match process owner. If this is not the case it cannot write or modify files.
\nTypically, you should tell your web host about the permission issue and they should be able to resolve it.
\nYou can however try adding define(‘FS_METHOD’, ‘direct’); to wp-config.php to circumvent the file and folder checks.
\n\n\n
No. The Image Service extension converts common image file formats to the modern WebP format using our API services. The conversions occur on our API service, so that resource usage does not impact your website server.
\n\n\n
Image data received by our API is destroyed after a converted image is generated. The converted iamges are destroyed once picked-up/downloaded to your website by the Total Cache plugin.
\n\n\n
You will be able to see the results instantly on each page load, but for tangible metrics, you should consider using the following tools:
\n\n\n\n
Yes! Please reach out to us and we’ll get you acclimated so you can “set it and forget it.”
\nInstall the plugin to read the full FAQ on the plugins FAQ tab.
\n\n\n\";s:9:\"changelog\";s:30352:\"= 2.2.1=
\n* Fix: Cloudflare: Removed use of the retired ip_lkup V1 endpoint
\n* Fix: Prevent error in some environments using non-direct filesystems
\n* Fix: Added better checking for some filesystem actions
\n* Fix: AWS CloudFront: Reverted async change for cache invalidation to honor promises
\n* Enhancement: Added option to exclude minified JS files from being processed by Rocket Loader
\n* Enhancement: Improved handling of Image Service rate-limiting and error messages
2.2.0
\n- \n
- Feature: Image Service API extension: WebP conversion options \n
2.1.9
\n- \n
- Fix: Cloudflare Dashboard Widget: Updated to use GraphQL \n
- Fix: Cloudflare Dashboard Widget: Use WordPress timezone \n
- Fix: CDN: Execute purge only if hosting is enabled, to prevent unneeded delays \n
- Fix: Published/modified custom posts not clearing the archive cache(s) \n
- Fix: Native WordPress sitemap caching \n
- Fix: Extra MIME groups other than controlled by settings were added to rules \n
- Fix: Usage Statistics: Not functioning when object cache is set to Redis \n
- Fix: AMP Extension: Prevent popup admin bar for endpoints \n
- Fix: Setup Guide Wizard: CSS for long translations \n
- Fix: Opcache Settings: Validate timestamp indicator checkbox \n
- Update: Remove robots.txt cache toggle setting \n
- Enhancement: Impove 404 detection \n
- Enhancement: Improved compatibility check indicators \n
- Enhancement: AWS CloudFront: Faster cache invalidation using async \n
2.1.8
\n- \n
- Fix: Corrected handling of robots.txt (file and filter) \n
2.1.7
\n- \n
- Fix: Corrected relative paths used in the JS minify YUI Compressor \n
- Fix: Disallow crawling of cache directory \n
- Fix: Responsive display for the dashboard \n
- Enhancement: Added lazy load threshold setting \n
- Enhancement: Added feature policy security headers to settings \n
2.1.6
\n- \n
- Fix: JS minify issue with template literal backticks \n
- Fix: Do not redirect when using WP-CLI \n
- Fix: Missing whitespace in Memcached Nginx configuration \n
- Fix: Setting for CDN over passive FTP \n
- Fix: Updated CDN Minify regex \n
- Fix: Added missing text domains and fixed translations \n
- Enhancement: Allow default AWS credentials provider \n
- Enhancement: Added error logging when minification base URL is not found \n
2.1.5
\n- \n
- Fix: Sanitize extension argument \n
2.1.4
\n- \n
- Fix: Use Memcached server from config for Nginx rules instead of localhost \n
- Fix: Allow more characters in CDN hostname sanitization \n
- Fix: Added missing textdomains for Browser Cache settings \n
- Fix: Avoid a possible PHP warning in LazyLoad mutator \n
- Enhancement: Added a filter w3tc_cdn_cf_flush_all_uris for CloudFront purging \n
2.1.3
\n- \n
- Fix: Authenticated Persistent XSS & XFS in CDN admin page \n
- Update: AWS library version 3.183.0 \n
- Update: Minify: Include theme template files using page_* filenames \n
2.1.2
\n- \n
- Fix: Skip removing spaces around “ \n
- ” tags in HTML Minify \n
- Fix: Updated admin URL logic for multisite installations \n
- Fix: TransparentCDN purge URL validation \n
- Fix: Added an option to use ABSPATH as the document root for Minify \n
- Fix: Database cache debug message \n
- Update: Added regions for AWS S3 (af-south-1, cn-north-1, cn-northwest-1, eu-south-1) \n
- Update: Added MIME types AVIF and AVIFS for Browser Cache rules \n
- Update: Enhanced “get_pagenum_link” filter \n
- Update: Removed “comment” from the non-persistent object cache group \n
2.1.1
\n- \n
- Fix: Move Minify library to a namespace to avoid conflicts with other plugins \n
- Fix: Check for AWS before loading functions \n
- Fix: Update Minify ClosureCompiler base URL; use HTTPS \n
- Fix: Corrected getting the network siteurl \n
- Fix: Prevent PHP warning in CurlFactory \n
- Update: Added information links to general minify options \n
- Update: Added video/ogg support for browser caching \n
2.1.0
\n- \n
- Feature: Added a Feature Showcase to highlight new and existing features \n
- Update: Consolidated cache groups settings pages \n
- Update: Replaced deprecated jQuery method for WordPress 5.6 \n
- Fix: PHP warnings for sprintf placeholders in PHP 8 \n
- Fix: PHP deprecated warnings in PHP 8 \n
- Fix: Browser Cache Quick Reference Chart link \n
- Fix: Bad nonce in help \n
- Fix: Google Drive CDN JavaScript \n
2.0.1
\n- \n
- Fix: Corrected redirection logic for the new Setup Guide \n
- Fix: Fixed JavaScript w3tc_ga error \n
2.0.0
\n- \n
- Feature: Added the Setup Guide wizard for onboarding \n
- Update: Updated jQuery compatibility and methods deprecated in WordPress 5.6 \n
- Fix: Browser Cache: Fixed ExpiresByType code; changed from modified time to client access time \n
0.15.2
\n- \n
- Fix: Minify: Do not remove quotes around meta tags \n
- Fix: Minify: Removal of spaces in calc function was breaking CSS \n
- Fix: Browser Cache: Query string was not added to prevent caching after setting changes \n
- Fix: Avoid warning when sending an empty URL for purging \n
- Update: Added a filter for minified JavaScript content \n
- Update: Minify: Added options for minify only got both JS and CSS in auto mode \n
0.15.1
\n- \n
- Fix: Fixed Memcached flush logic \n
- Fix: Remove disk enhanced rewrites when disabling page cache \n
- Fix: Better handle conflicts on activation \n
0.15.0
\n- \n
- Feature: Added TransparentCDN full-site delivery option \n
- Fix: Update settings on activation in a changed environment \n
- Fix: Fixed a compatibility check for Apache when PHP is running as CGI \n
- Fix: Always set HSTS headers in Apache; not only for 2xx HTTP codes \n
- Fix: Implemented anatomic incrementing of key version in Memcache(d) \n
- Update: Allow filtering of w3tc_minify_url_for_files Minify URL for files \n
0.14.4
\n- \n
- Fix: Cleanup widget and postbox display for WordPress 5.5 \n
- Fix: Update to PageSpeed API v5, show webvitals metrics \n
- Fix: Console error when adminbar is hidden and PageSpeed module is active \n
- Fix: Stats view JS issue \n
- Fix: Deprecated jQuery warnings \n
- Fix: Require files for request_filesystem_credentials() call \n
- Added option to disable jquery-migrate on the front-end. Fixed #172 master (#240) \n
0.14.3
\n- \n
- Fix: Take “Accepted Query Strings” into account when “Cache query strings” enabled \n
- Fixed typo in variable for lazy loading \n
- Update: Add lazy load Google Maps reference to the general settings page \n
- Update: Support background-image: together with background: for lazy loading \n
0.14.2
\n- \n
- Fixed WP-CLI redirect issue in multisite \n
- Fix: Avoid PREG_JIT_STACKLIMIT_ERROR in minify \n
- Fix: Prevent empty needle PHP warning \n
- Update: Allow to specify URIs with a query string in Additional Pages \n
0.14.1
\n- \n
- Fixed CSS minify URL rewrite logic that affected some lazy loading and CSS URL addresses using protocols \n
0.14.0
\n- \n
- Added lazy loading for Google Maps \n
- Added a filter w3tc_minify_css_content for minified contents \n
- Fixed a minify regex issue in non-Unicode websites \n
- Fixed a PHP notice in WPMU: accessing array offset on null \n
- Fixed a minify issue where embedded CSS URL fragments were converted incorrectly \n
- i18n improvement \n
- Changed default to disabled for wp-admin requests in the object cache \n
0.13.3
\n- \n
- Fixed HTML minification of img elements containing embedded SVG strings \n
- Removed an identifying value for GDPR \n
0.13.2
\n- \n
- Fix: Dont store content of HEAD requests \n
- Updated informational URL on page cache static page comments \n
0.13.1
\n- \n
- Fixed php warnings in PgCache_ContentGrabber.php \n
0.13.0
\n- \n
- Added new Pro feature, Debug – Purge Stack Trace \n
- Added “Feature Policy” security header \n
- Removed deprecated get_magic_quotes_gpc() \n
- Improved AMP Extension by ignoring value of amp querystring marker in request if passed without value in config \n
- Improved lazyload by not processing elements with skip-lazy class or data-skip-lazy attribute \n
- Fixed caching of query-string normalization redirects, no longer cached when cache key is normalized by accept querystring arguments, caused redirect loop \n
0.12.0
\n- \n
- Added querystring based URL structures for AMP pages \n
- Added filter of minify options \n
- Added lazyload picture tag support \n
- Removed footer link “Support Us” option \n
- Improved wp_die handling \n
- Improved lazyload handling of content in script tags \n
- Improved lazyload handling of feeds \n
- Improved printing tags coming from feeds \n
- Improved handling of modified posts before wp_rewrite initialized \n
- Nginx rules changed a lot to avoid “location” block conflicts. That change may cause problems on some systems using non-default WordPress rules – keep a backup of your original rules \n
- Improved handling of .htaccess files in regard to EOF \n
- Fixed Varnish purging \n
- Fixed html minification of data tags equaling 0 \n
0.11.0
\n- \n
- Added recommendation for BoldGrid’s Total Upkeep plugin \n
- Added new lazy loading feature \n
- Removed New Relic extension by default for new installations \n
- Updated usage of html minification and quote removal \n
- Improved memcached config and added optional binary protocol setting \n
- Improved process of renewing expired licenses \n
- Improved page cache purging \n
- Improved FAQ link by opening in new window \n
- Improved detection of detect_post_id \n
- Improved REST caching in relation to cache headers like X-WP-* \n
- Improved Vary User-Agent header usage \n
- Improved various features with AMP pages and HTTP2 \n
- Improved redis connection string to allow for tls://host:port format \n
- Fixed file headers for Cloudfront S3 CDN \n
- Fixed fatal error on with flush / SNS \n
- Fixed comments with URLs within minify debug mode \n
- Fixed ObjectCache statistics within footer \n
- Fixed temporary hotfix with wp_die and regular output \n
- Fixed fragment cache header link \n
- Fixed flushing of /feed and /feed/ cache \n
- Fixed js error in widget \n
- Fixed fatal cache flush error caused by empty $wp_rewrite \n
- Fixed path for file_generic REST caching on non-default port \n
- Fixed test minify button with Closure Compiler engine \n
0.10.2
\n- \n
- Fixed compatibility with wpdb::prepare in WordPress 5.3 \n
0.10.1
\n- \n
- Fixed slowdown in memcached engine \n
- Fixed Purge Cache menu links so they flush current blog in WPMU \n
- Fixed error during upgrade, “Call to undefined method W3TC\\Util_Content::is_database_error” \n
- Updated Redis cache engine to avoid “Function Redis::delete() is deprecated” warning \n
0.10.0
\n- \n
- Improved Statistics component for pro users \n
- Improved support for CloudFront distributions with multiple origins \n
- Improved redirects by using safter wp_safe redirect \n
- Improved .htaccess usage when pagecache does not require it \n
- Improved protection of unexpected values in global variables \n
- Added more Amazon S3 regions \n
- Added support for memcached binary protocol when available \n
- Added caching for webp MIME type \n
- Updated S3 bucket creation by settings CORS policy \n
- Updated blogmap to allow urls with custom ports \n
- Fixed usage of base url with minify \n
- \n
Fixed mixing content of sync & async scripts with minify
\n \n - \n
Fixed S3 + CloudFront urls when CNAMEs not used
\n \n
0.9.7.5
\n- \n
- Updated AWS library \n
- Added support of set_sql_mode by dbcluster \n
- Improved support for webserver running on non-default port with disk-enhanced \n
- Improved menu icons \n
- Fixed php warning when remote service cannot be loaded \n
- Fixed php warnings on support page \n
0.9.7.4
\n- \n
- Fixed PHP warning when Redis integration not configured correctly \n
- Fixed 404 in multisite caused by subdirectory issue \n
- Fixed object cache issue in multisite where object cache was cleared at wrong time \n
- Fixed database cluster in WordPress 5.1 \n
- Fixed warning caused by user agent theme change used \n
- Fixed minification in multisite when URLs were set to root-blog based url \n
- Fixed undefined w3tc_ga issue \n
- Improved purging of current page by using post_id instead of URL \n
- Improved cache delivery of /feed URLs \n
- Improved security on calls to opcache flush \n
- Improved minification of files in environments running on non-default ports \n
0.9.7.3
\n- \n
- Fixed caching of redirect responses based on empty response body \n
- Improved compatibility with WordPress 5.1 \n
- Improved transports, unix: prefix not required \n
- Improved minify html \n
0.9.7.2
\n- \n
- Fixed fatal error during media file upload with CDN module active \n
- Fixed removal of empty values, JSON encoded string in attribute, trailing quote at end of tag, and the handling of anchors in HTML minify \n
- Fixed undefined index warning \n
- Fixed fatal error when purging CDN using full site delivery \n
0.9.7.1
\n- \n
- Fixed undefined variable notice \n
- Fixed “No such file or directory” warning \n
- Fixed writing to PHP error log rather than WordPress debug log \n
- Fixed default referrer policy should be “no-referrer-when-downgrade” \n
- Fixed php_flag error related to browser cache, using ini_set instead \n
- Fixed CloudFlare IPv6 check undefined offset \n
- Fixed Undefined constant WP_ROOT \n
- Fixed frame-ancestors being overwritten by frame-src \n
- Fixed missing semicolon in nginx configuration \n
- Fixed HTTP/2 URLs handling for browser cache and CDN modules \n
- Fixed display of CDN debug information \n
- Fixed CSS Minification with Google Fonts when included via “Include external files/libraries” and non-latin character-sets are loaded \n
- Fixed media query string not updating when all caches were purged \n
- Fixed double slash with ABSPATH if file exists \n
- Fixed setting max-age and expires header simultaneously \n
- Fixed SASL detection for PECL Memcached \n
- Fixed handling of manually entered objects to be purged on CDN \n
- Fixed query string handling in Nginx \n
- Improved error handling with Cloudfront \n
- Improved page cache logging \n
- Improved multi-tenant support for memory-based caching engines \n
- Improved CSS minification \n
- Improved purge behavior for changed media objects when using CDN \n
- Improved compatibility with sitemap plugins \n
- Added support for Memcached for Nginx \n
- Added support for caching webm files \n
- Added Brotli HTTP compression support \n
- Added StackPath full site delivery support \n
- Added wc_session to the list of ignored query stems for improved WooCommerce compatibility \n
0.9.7
\n- \n
- Fixed minified files not being hosted by CDN when enabled if “host minified files” is disabled \n
- Fixed warning thrown when purge all was selected (via nigrosimone) \n
- Fixed undefined offset error in fragment cache \n
- Fixed MaxCDN test button failure when debug mode is enabled \n
- Fixed purging of feeds when cache feeds option is enabeld \n
- Improved handling of errors when full site delivery isn’t set \n
- Improved nginx.conf to support xml caching \n
- Improved nginx.conf to support HSTS for static files \n
- Improved minify’s handling of query strings \n
- Improved database caching, frequent wp_options no longer flush posts or comments data \n
- Improved Limelight Networks CDN integration \n
- Improved FAQ, they’re now hosted in the GitHub public repository \n
- Improved handling for /<![CDATA[/ in HTML minify engine \n
- Imporved garbage collection for basic disk caching \n
- Improved HSTS support (via Dave Welsh) \n
- Improved reliabilty of CSS embed options \n
- Improved New Relic requirements in compatibility test \n
- Added StackPath CDN integration (including full site delivery) \n
- Added support for page cache priming via WP-CLI via prime function \n
- Added filter support for managing cache groups \n
- Added API for flushing individual cache groups via flush_group function \n
- Added purge support for JSON cache e.g. cached REST API requests \n
- Added filter support for managing database cache settings \n
- Added filter support before (w3tc_process_content) and after (w3tc_processed_content) a cache object is created \n
- Added compatibility for AMPforWP plugin \n
- Added JSON caching support for Pro subscribers \n
- Added additional security headers (via amiga-500) \n
0.9.6
\n- \n
- Fixed anonymous usage tracking, default to disabled \n
- Fixed incorrect minify cache data written if target directory missing \n
- Fixed empty minify cache file written when file locking enabled \n
- Fixed missing commas in CSS (via nigrosimone) \n
- Fixed typo in object cache engine (via Furniel) \n
- Fixed incorrect reuse of redis connections when persistent connections option enabled \n
- Fixed reliability of Google Drive (via jikamens) \n
- Fixed handling of UTF-8 encoded files by writing them in binary (via jikamens) \n
- Improved Full Site Delivery configuration user flow on the General and CDN settings screens \n
- Improved content type matching and cache hits as a result \n
- Improved minify file locking logic \n
- Improved visual langage of the compatibility test (via Furniel) \n
- Improved configuration file management \n
- Improved MaxCDN set up wizard \n
- Improved page cache’s accepted query string handling to handle optional values and add support for disk enhanced mode (via amiga-500, nigrosimone) \n
- Improved handling of timeouts to origin push CDN proviers \n
- Added HTTP/2 push headers for disk enhanced page caching (via nigrosimone) \n
- Added X-Forwarded-Proto header for use cases like HTTPS recognition behind proxies or load balancers \n
- Added multiple CDN support i.e. static file objects and pages, posts, feeds, API responses etc to use different respective CDN providers \n
- Added page caching by cookie name or value (sponsored by SQweb) \n
- Added toggle for CORS header to improve inter-operatbility with various CDN providers \n
- Added support for CDN hosted media to media library (inspired by amiga-500) \n
- Added object caching of AJAX calls (via andyexeter) \n
- Enterprise features are now available to Pro subscribers! Including reading from multiple databases concurrently and purging caches across multiple hosts via a Message Bus \n
0.9.5.4
\n- \n
- Fixed regression with browser caching and query strings \n
0.9.5.3
\n- \n
- Fixed handling of HTTP compressed documents in PHP v5.3 (via amiga-500) \n
- Fixed a bug with accelerated mobile pages (via nigrosimone) \n
- Improved reliability of minify in manual mode \n
- Improved JavaScript interoperability with CDATA use cases \n
- Improved file name generation on Windows for IIS servers \n
- Improved handling of # in URLs \n
- Improved handling of exclusions for e-commerce in Genesis Framework \n
- Improved handling of headers for Microsoft Azure \n
- Improved functionality with existing Cloudfront Distributions when configuring Full Site Delivery \n
- Improved minify debug logging \n
- Improved handling of URLs that omit the protocol \n
- Improved handling of custom files with CDN (via amiga-500) \n
- Updated CSSTidy library (via nigrosimone and amiga-500) \n
- Added Swarmify Video Optimization Extension [Hat tip the Swarmify Team] \n
- Added flushing of AMP pages \n
0.9.5.2
\n- \n
- Fixed security issue by protecting configuration data by adding .php to relevant files \n
- Fixed security issue with the creation of dot folders that could be abused \n
- Fixed handling HTTP compression for uncached pages \n
- Fixed handling of .svgz files \n
- Added expiration headers to webP images \n
- Added support for Microsoft Azure’s latest API \n
- Added ability to cache WP Admin. Recommended setting, is off. (Improved WP Admin performance with object caching enabled) \n
- Added HTTP/2 Push support for minified files \n
- Added option management support for wp-cli \n
- Improved handling of uncompressed minified files \n
- Improved handling of purging of modified pages / posts \n
- Improved compatibility with Rackspace Cloud Files \n
- Improved initial CDN configuration reliability \n
- Improved reliability of object caching \n
- Improved PHP 7.0 compatibility \n
- Improved PHP 4.3 compatibility \n
- Improved HTTP/2 support \n
- Improved CSS embed handling \n
- Improved reliability of object cache, transients now fallback to database \n
- Improved handling of cached http compressed objects \n
0.9.5.1
\n- \n
- Fixed missing namespace, which caused issues with other implementations of Google APIs \n
- Fixed handling Cloudflare zone list being incomplete for users with many zones \n
- Added extension to support Accelerated Mobile Pages (AMP) \n
- Added notification for users that are still using PHP 5.2 (end of life in 2011) \n
- Improved default settings \n
- Improved compatibility with Yoast SEO sitemap caching \n
- Improved compatability with Jetpack \n
- Improved directory handling on IIS \n
- Improved backwards compatibility for 3rd party implementations against legacy W3TC functions \n
0.9.5
\n- \n
- Fixed XSS vulnerability \n
- Fixed issues with dismissing overlays \n
- Fixed handling of tilde in URLs \n
- Fixed issue with HTTP compression header when using mfunc calls \n
- Fixed cache ID issue with minify in network mode \n
- Fixed rare issue of caching empty document when some PHP errors occur in themes or plugins \n
- Fixed caching of query strings \n
- Added support for APCu Opcode Cache \n
- Added support for Redis \n
- Added support for Google Drive \n
- Added support for Amazon S3-compatible stroage services \n
- Added support for PECL memcached \n
- Added support for srcset elements \n
- Added support for Rackspace CDN Origin Pull \n
- Added support for minification of external fonts \n
- Added support for WOFF2 font format \n
- Added support for FTPS (FTP-SSL, S-FTP) \n
- Added YUI Compressor’s PHP Port of the CSS minifier \n
- Added Narcissus’ JS minifier \n
- Added purge of parent page when attachments are added or updated \n
- Added Highwinds CDN provider \n
- Added “Validate Timestamps” option for compatible opcode caches functions like apc.stat are enabled \n
- Added Full Site Delivery for Pro subscribers \n
- Added HTTP Strict Transport Security (HSTS) support \n
- Added a sample extension for developers to reference \n
- Added Rackspace Cloud Files Multi-Region Support \n
- Added more support for exclusions to database cache \n
- Added more optionality to minifiers \n
- Added WPML Performance Extension \n
- Added use of namespace which creates mininum dependency on version PHP 5.3 \n
- Improved PHP 5.6 compatibility \n
- Improved PHP 7 compatibility \n
- Improved performance menu in admin bar, including purging of specific cache engines and more \n
- Improved SSL interoperability \n
- Improved reliablity of test buttons \n
- Improved nomenclature of caching files for higher cache hit rates \n
- Improved nginx compatibility \n
- Improved WP CLI support \n
- Improved Cloudflare compatibility (now using latest APIs), Cloudflare must be re-authorized \n
- Improved AWS API compatibility (now using latest APIs) \n
- Improved Rackspace Cloud Files compatibility (now using latest APIs) \n
- Improved page cache purge for extensions like cloudflare and other reverse proxy use cases \n
- Improved extension framework functionality \n
- Improved compatibility of headers like ETag and content encoding \n
- Improved template fragment caching \n
- Improved notifications, warnings and errors \n
- Improved moble user agents detection \n
- Improved security with nonces and form elements \n
- Improved security throughout the codebase \n
- Improved detail of debug messages \n
- Improved Amazon SNS security (validation) \n
- Improved minify’s ability to match script tags without type attribute \n
0.9.4
\n- \n
- Fixed undefined w3tc_button_link \n
- Fixed support and other form submissions \n
- Fixed extension enabled key error \n
- Fixed Test CDN errors \n
- Fixed trailing slashes in custom wp content path and Minify \n
- Fixed WP_PLUGIN_DIR not being available when object-cache.php is loaded and W3TC constant not set \n
- Fixed Minify Auto and restructuring of JS code placement on page \n
- Fixed remove / replace drop in file on plugins page \n
- Fixed false positive check for legacy code \n
- Fixed deprecated wpdb escape \n
- Fixed Fragment Caching and APC anomalies \n
- Fixed cached configs causing 500 error on interrupted file writes \n
- Fixed readfile errors on servers with the functionality disabled \n
- Fixed false positives for license key verification \n
- Fixed debug information not printed on cached pages \n
- Fixed backwards compatibility and flushing and added doing it wrong notification \n
- Fixed “Prevent caching of objects after settings change” \n
- Fixed “Use late init” being shown as enabled with Disc:Enhanced \n
- Fixed missing param in APC cache method declaration \n
- Fixed user roles property not begin an array \n
- Fixed adding empty Vary header \n
- Fixed notice on failed upgrade licencing check \n
- Fixed Database Cache description text \n
- Fixed duplicate bb10 agents \n
- Fixed settings link in Minify Auto notification \n
- Fixed notice with undefined constant \n
- Fixed nginx configuration and Referrer, User Groups setting \n
- Fixed Genesis settings and Suhosin field name limit error \n
- Fixed Genesis and Fragment Caching (caching categories etc) \n
- Fixed CDN being enabled when creating NetDNA / MaxCDN pull zone \n
- Fixed NewRelic related notice in compatibility popup \n
- Fixed trailing slash issue in filename to url conversion \n
- Fixed issue with wp in subdirectory and relative minimal manual urls \n
- Fixed issue with widget styling \n
- Fixed issue with Purge All button action \n
- Fixed issue with exporting of settings \n
- Fixed issue with plugin interferring with preview theme \n
- Fixed issue with malformed config files \n
- Added caching of list of posts pages (tags, categories etc) to Genesis extension a long with flush it checkbox \n
- Added typecasting on expiration time in object cache drop-in \n
- Added capability check for save options \n
- Added FeedBurner extension \n
- Added woff support to Browser Cache \n
- Added new CloudFlare IPs \n
- Added support for WordPress defined charset and collate in CDN queue table creation \n
- Added WordPress SEO by Yoast extension \n
- Added *.less to CDN theme uploads and MIME \n
- Added default settings for MaxCDN Pull Zone creation \n
- Added call to change MaxCDN canonical header setting to match plugin setting \n
- Added one button default pull zone creation to MaxCDN without refresh \n
- Added MaxCDN authorization validation \n
- Added whitelist IPs notification for MaxCDN \n
- Added support for use of existing zones without refresh \n
- Added new mime types \n
- Added support for separate domains for frontend and admin backend \n
- Added CloudFlare as an extension \n
- Added nofollow to blogroll links \n
- Added DEV mode support to PRO version \n
- Added EDGE MODE functionality \n
- Improved wrapper functions in plugins.php for plugin / theme authors \n
- Improved reliability of NetDNA / MaxCDN API calls by using WP HTTP and not cURL \n
- Improved Fragment Caching debug information \n
- Improved preview mode, removed query string requirement \n
- Improved FAQ structure \n
- Improved empty minify/pgcache cache notification when using CDN \n
- Improved default settings for MaxCDN zone creation \n
- Improved CDN queue performance \n
- Improved blogmap url sanitation \n
- Improved MaxCDN automatic zone creation process \n
- Improved license key saving and Pro mode activation on Pro license purchases \n
- Updated EDGE MODE: Full site mirroring support for MaxCDN \n
- Updated translations \n
A must have plugin.
\n \n\n By 
Love The Plugin
\n \n\n By 
Excellent service
\n \n\n By 
Excellent plugin and support
\n \n\n By 
Great Plugin
\n \n\n By 
Great cache plugin
\n \n\n By 
Great cache!
\n \n\n By 
Great plugin!
\n \n\n By 
Awesome plugin and support
\n \n\n By 
Otimização
\n \n\n By 
In the thirty-second episode of the WordPress Briefing, WordPress Executive Director Josepha Haden Chomphosy shares her open source reading list for that post-WordCamp Europe downtime.
Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Santana Inniss and Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- Producing Open Source Software, Karl Fogel
- Working in Public: The Making and Maintenance of Open Source Software, Nadia Eghbal
- Collaborative Ownership and the Digital Economy, ed Rishab Aiyer Ghosh, Roger F. Malina PhD, Sean Cubitt
- Humble Inquiry, Edgar H. Schein (Author), Peter A. Schein
- WordPress Milestones
- WordCamp Europe 2022
- 2022 Annual Meetup Survey
Transcript
\n\n\n\n\n\n\n\n[Josepha Haden Chomphosy 00:00:00]
\n\n\n\nHello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it. As well as get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nWith the approach of various mid-year breaks and the prospect of wandering off for some safe, restorative travel, I’ve been updating my to-read and re-read list. As I was looking at the queued books for my Northern hemisphere summer, there were some common threads, mostly around leadership, but there’s also like a chunk that’s about cross-cultural group theory and economics, and then like some beach reads, but there’s one group in particular that you all might find interesting.
\n\n\n\nAnd that’s a group that’s sort of like a back-to-FOSS basics list. So I’ll share my top few with you in case you want to pack a copy for your next getaway.
\n\n\n\nThe first one on our list is called Producing Open Source Software by Karl Fogel. I think everyone who contributes to FOSS projects has received this as one of their first recommendations. Like, y’all are building open software? Excellent, you need to read Producing Open Source Software. Like, that is just a sentence that comes out of everyone’s mouths. So this was one of the first open source books that was recommended to me when I joined the WordPress community. It was freshly revised in 2020, and I haven’t given it a read since then, which is why it is on my reread list this year.
\n\n\n\n[Josepha Haden Chomphosy 00:01:54]
\n\n\n\nHowever, it shaped the early days of the WordPress project’s leadership, and their lead developers, and some of WordPress’s basic philosophies. It’s all available online, under a creative commons, ShareAlike license. And so it’s worth the read. I’ll put a link to it in the show notes so it’s easy for everyone to find in the event that is your preferred beach read.
\n\n\n\nThe second one on this list is a book from Nadia Eghbal. She wrote the excellent Roads and Bridges report that also is probably not light beach reading, but you know, this one is on my list to read this summer because Eghbal always delivers truths about the reality of maintaining popular software, popular, open source software, in a way that’s easy for me to access and process rather than getting paralyzed by the enormity of it all.
\n\n\n\nFor what it’s worth your mileage may vary on that. I realized that, like, I live and breathe open source stuff. And so just because I am not paralyzed by the enormity of her explanations of things doesn’t necessarily mean that you will have a similar experience. And so I’m just going to claim that elephant in the room for all of us.
\n\n\n\nHowever, if you only read one book on this list this year, I think that this should be the one that you read.
\n\n\n\n[Josepha Haden Chomphosy 00:03:14]
\n\n\n\nThe third one is called Code: Collaborative Ownership and the Digital Economy. It was edited by Rishab Aiyer Ghosh. I am certain that I butchered that name. And so I apologize on my own behalf to everyone that knows whether or not I said it correctly.
\n\n\n\nThis book focuses on intellectual property rights and the original purpose of having anything like copyright in the world. So, right up my alley! The writers who contributed to this work promise exploration of the plight of creativity in the commons, the role of sharing in creative advancement, and a concept of what it would look like if intellectual property were to mean the second closing of an ecosystem versus a triumph of the commons.
\n\n\n\nI mean, obviously, this one is very light reading. You can take this topic to high tea and everyone will not know what you’re talking about. However, this one looks like a really interesting book to me and I am just super ready to read it.
\n\n\n\n[Josepha Haden Chomphosy 00:04:19]
\n\n\n\nThe second to last one on the list is a book called Humble Inquiry.
\n\n\n\nThis is a new-to-me book that seems right in line with one of my favorite books to recommend to leaders in the open source space. From reviews of it, I have gathered that it takes a hard look at the value of listening and asking for clarification in a world that puts a high value on an unsolicited hot take.
\n\n\n\nIt puts the importance of high trust relationship building, which is at the heart of any cross-culturally aware organization. And for folks who’ve been working with me for a while, you know, that relationship building is an important part of my leadership expectations for myself. So it puts relationship building at the front and center with a promise of practical applications for everyday life.
\n\n\n\nAnd if you ever have tried to tackle a complicated topic like this, you know that practical applications are really hard to come by and it’s often hard to understand it if you don’t have those practical applications. And so that is why this one is on my read and reread list this year.
\n\n\n\n[Josepha Haden Chomphosy 00:05:24]
\n\n\n\nAnd then finally the WordPress Milestones book.
\n\n\n\nSo this sounds like a shameless plug for WordPress. And on the one hand, this whole podcast is about WordPress. And so, yes! But on the other hand, I actually am reading this for two specific reasons. I’m rereading this actually. I read it when I first joined Automattic. And so the first of the two reasons that I’m rereading it this year is that volume two of this is, like the second decade of WordPress currently, being researched and written in preparation for WordPress’s 20th birthday next year.
\n\n\n\nSo I am rereading this to kind of get that all back in my mind as that work is getting done. And the second reason is that I honestly like to remind myself of how far we’ve come sometimes. I talk about our work frequently. And I talk about what we’re working on right now, all the time.
\n\n\n\nI talk about what we’re looking at three years from now, five years from now. The biggest concerns of today, tomorrow, and the future-future. And it’s very easy to forget how much success WordPress has had and how much growth the contributors that support us have had over the course of our long and storied history.
\n\n\n\n[Josepha Haden Chomphosy 00:06:40]
\n\n\n\nAnd so I like to go back to that just to kind of give myself some grounding in our progress, as well as get some concept for how we can move forward together. So that one is also available online. Also under a creative commons ShareAlike license and it is also worth the read. I will share a link to that with the other one in the show notes as well.
\n\n\n\nThat brings us now to our small list of big things. Let’s see what we got in the old lineup today.
\n\n\n\nSo, firstly WordCamp Europe is happening this week and it’s possible to watch the live stream from the comfort of your own home. There are some smart and talented speakers at the event. So I encourage you to catch a few if you have the time. I’ll include a link to the live stream information in the show notes below, and then also you can always keep an eye out on Twitter.
\n\n\n\nThere will be a lot of discussions, a lot of conversation there. And so you can engage with folks that are there at the time and catch up on those conversations, catch up on those presentations in your own time, as it fits into your day.
\n\n\n\n[Josepha Haden Chomphosy 00:07:50]
\n\n\n\nThe second thing is that WordPress’s community team is preparing the annual meetup survey right now. So if you participate in meetup events, keep an eye out for that because your feedback helps us to make plans to improve that program so that it works better for you. And it helps you to learn WordPress better and feel more confident with what you are taking out into the world that way.
\n\n\n\nBut, if you are wanting to use this as a chance to contribute, we actually will need folks who are able to translate the surveys as well. So I’ll leave a link to some information about that in the show notes. If all of that stuff about contribution didn’t make any sense, then just like keep an eye out from your meetup organizer and they will make sure that you have that survey so that you can have your voice heard.
\n\n\n\n[Josepha Haden Chomphosy 00:08:33]
\n\n\n\nAnd then item three is less of an item. I mean, it’s an item cause it’s in this list, but it’s less of, like, a thing to know and more of a general thing to be aware of. It’s a general awareness item. There’s a lot going on in WordPress right now. I can see how hard it is to keep track of some of these things these days.
\n\n\n\nAnd I know as someone who’s looking at this all day every day that, yeah, it’s a lot. And it’s hard to get your bearings. So if you have a team that you contribute to already, don’t forget to reach out to each other, just to check-in. Sometimes we don’t think to ask for help. Sometimes we don’t think to offer help and you know, if no one needs any help from you at that moment, a little hello also can brighten someone’s day.
\n\n\n\nAnd that, my friends, is your smallest of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy. And I’ll see you again in a couple of weeks.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 May 2022 17:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Santana Inniss\";s: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:88:\"Gutenberg Times: Gutenberg Changelog #67 Gutenberg 13.2 and 13.3, WordPress 6.0 and 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://gutenbergtimes.com/?post_type=podcast&p=21224\";s:7:\"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://gutenbergtimes.com/podcast/gutenberg-changelog-67-wordpress-6-0/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:58930:\"Birgit Pauli-Haack and special guest, Grzegorz Ziolkowski talk about WordPress 6.0 release, Gutenberg 13.2 and 13.3 and interesting discussions happening on the Gutenberg Repo
\n\n\n\n- Music: Homer Gaines
- Editor: Sandy Reed
- Logo: Mark Uraine
- Production: Birgit Pauli-Haack
Show Notes
\n\n\n\nWordPress 6.0
\n\n\n\n- WordPress 6.0 “Arturo” Release post
- WordPress 6.0 Field Guilde with all DevNotes and changes
- Video: Release announcement
- Building a site with WordPress 5.0 vs WordPress 6.0 w/ Anne McCarthy
- New Video Explores Site Building Progress From WordPress 5.0 to 6.0
- What to expect from WordPress 6.0 by Birgit Pauli-Haack via Pantheon
Community Contributions
\n\n\n\n- Plugin: Core Roll back by Andy Fragen
- Plugin: PWA (Progressive Web App)
What’s Released
\n\n\n\nGutenberg 13.2
\n\n\n\n- What’s new in Gutenberg 13.2? (May 11)
- Gutenberg 13.2 Adds Persistent User Preferences and a Visualizer for Margin and Padding Controls (WPTavern)
Gutenberg 13.3
\n\n\n\n- What’s New in Gutenberg 13.3.0 ( May 25 )
- Gutenberg 13.3 Introduces Experimental Table of Contents Block (WPTavern)
What’s being worked on or discussed
\n\n\n\n- Focus: Blocks Adoption (Label on GitHub)
- Allow usage of block based “template parts” without using block based “templates” (#37943)
- Site Editor & Templates Roadmap
- Global Styles Ongoing Roadmap
- Tracking: Add a Style Engine to manage rendering block styles (Updated May 20th, 2022)
- Pattern as Sectioning Elements
- Add a zoomed out view to the site editor (#41156)
- Improving FSE for the Agency Use Case #41349
Stay in Touch
\n\n\n\n- Did you like this episode? Please write us a review
- Ping us on Twitter or send DMs with questions. @maryojob and @bph.
- If you have questions or suggestions, or news you want us to include, send them to changelog@gutenbergtimes.com.
- Please write us a review on iTunes! (Click here to learn how)
Transcript
\n\n\n\nBirgit Pauli-Haack: Hello, and welcome to our 67th episode of the Gutenberg Fran Podcast. In today’s episode, we will talk about Gutenberg 13.2 and free WordPress 6.0 and discussions that are taking place and would need your opinion. I’m Birgit Pauli-Haack, curator at the Gutenberg Times and WordPress developer advocate.
\n\n\n\nAnd I’m here today with my special guest and former co-host Grzegorz Ziolkowski, JavaScript developer at Automattic and virtual school contributor. For WordPress 6.0 release co-lead for editor responsible for the merge of the Gutenberg bits and bites into core. Mary Job sends her regards and is taking a break this week. Good evening, Greg. Thank you so much for joining me again tonight. How are you?
\n\n\n\nGrzegorz Ziolkowski: I’m great. I’m so happy that the release went out. Everything works, the work didn’t collapse, so that’s great. Also, want to thank you also for being part of the release team and also, I need to mention that I was also a co-lead for the editor with Adam Hevinski, his help was so important to making that happen, because that was a lot of work to bring all the changes from the editor to WordPress core and making sure that everything works.
\n\n\n\nThe group that helped was so huge. There was, I don’t know, 20 people, at least helping all the time with different type of tasks, which was an amazing experience to see how everyone cooperates.
\n\n\n\nBirgit Pauli-Haack: Yeah.
\n\n\n\nGrzegorz Ziolkowski: And also the release team was much bigger. You and the documentation team also having a core lead like Milana, right?
\n\n\n\nBirgit Pauli-Haack: Yeah, yeah.
\n\n\n\nGrzegorz Ziolkowski: Oh yeah. So it’s really interesting to be part of the team and see how it works. Also, the team was bigger than ever, as far as I know, and I think that it still could be bigger. In my opinion. We have so many tasks that are necessary to make all that happen.
\n\n\n\nBirgit Pauli-Haack: I was on the release course now as a rookie and of course I needed co-leads because as a rookie, you don’t know what to get yourself into. But there are so many pieces that go into this release and it all has been a mystery and most still are mystery to me. Yeah. But I learned a lot. I learned a lot from all of the people on the release squad. But it’s also the more I know, the more I know what I don’t know.
\n\n\n\nAnd so it’s kind of that really overwhelming feeling that, okay, I have watched so many times, but I still had no idea what is really behind it in all the different pieces that are there. So, and as you said, I’m in awe of all the brilliant people that make these run smoothly and are always there to help each other out. It’s an amazing experience.
\n\n\n\nYeah, absolutely. I’m glad I did it. It was a lot of work and, but wrangling dev notes, it’s a unique experience anyway. But yeah, congratulations that you helped bring it over the finish line.
\n\n\n\nAnnouncements
\n\n\n\nSo yes, WordPress 6.0, Arturo was released this week named after the contemporary Latino jazz musician, Arturo O’Farrill with a good Irish name. And there are many features and enhancements that are rolled out with a new version. We talk probably about all of them during the months, leading up to the release on this podcast, we will share again, of course, the release post, and then the field guide with the dev notes. And we will also share two videos with you. One is the release video by the design team. If you haven’t seen it yet on the about page or in the release post, watch it.
\n\n\n\nIt’s a great design and cutting from screen to screen, to highlight all the features that are in there. It’s a great piece of art, so definitely watch it. And then the second video is by Anne McCarthy and she covered the site building process between WordPress 5.0 and WordPress 6.0. 5.0 was released just to repeat that December 6th, 2018. So it’s three and a half years ago. And in that video, you’ll see how it changed from the early versions to how you build sites now. It’s a great, interesting video to watch. If you haven’t tried out the block editor yet, if you’re one who hasn’t started using it yet, I think you will be surprised, or it’s eye opening to see how it really changed and maybe it intrigues you to start using it again.
\n\n\n\nGrzegorz Ziolkowski: Yeah. It’s a huge change. How it all has evolved from starting small to edit only the content that’s post and pages. And throughout all that time, how data change itself, by bringing more tools that are supported and allow you to do more and more things with the content to add some styling and create beautiful designs without using a single line of code. And now even you can create the whole experience. And there’s many block themes that empower users to edit everything without ever opening and edit or code the detail where you need to deal with PHP files, CSS, and all that big stuff that are becoming more and more complex every year.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I think the biggest piece that helps a user to one part be in control, but on the other hand, not have to think about too much about design or the block patterns. And I think they have come really a long way from the first idea of a reusable block that people used this kind of templates or block patterns, but then they were changing it and then they changed it over the whole page site. But now combining just core blocks into this amazing designs and design system, it’s really remarkable. Yeah.
\n\n\n\nSo that’s definitely part of that show notes today is that video. And we also shared the article that the WP Tavern posted about that. And then just today I found that Pantheon published an article by yours truly like what to expect from WordPress 6.0. And it goes a little bit more on the developer side. And apart from the enhancements, talk about the enhancements for the writing experience. It’s more about develop oriented, how to code, with code examples for the new pattern features on pulling in patterns from the directory wire theme, JSON Slug, or also create page layouts on the create page action, and then some block locking examples, and also how to establish those style variations in the theme, JSON. So it’s a little bit different than the release post on WordPress.org. So, Greg, what are the most intriguing features that you found for WordPress 6.0?
\n\n\n\nGrzegorz Ziolkowski: So you already mentioned them, from the coding perspective, you covered how to integrate them on, on the owners of the site. And I think for the user, very exciting possibility is to use style variation when they are provided with theme because everyone have different taste and style variation allow you to quickly change colors, fonts have presets that you can quickly pick one and another, and another until it’s something that clicks with you and you don’t have to go and change every setting on the website yourself is just, you have bigger chance to… The other thing block locking. I think it’s great and it has a lot of value, but it’s still missing much more detailed control because everyone can lock and unlock now, which is nice, but you can change that.
\n\n\n\nYeah. But the idea is that in the future, you could have permission-based rules. So, as a site admin, you could just block everything you want for everyone else or whatever else you would like. So this still needs some development, but it’s the step in the right direction. And also all the work on patterns that how it evolves. You mentioned that how it was limiting and the beginning, and it was introducing with classic themes in WordPress 5.5. And it didn’t have so much power because for the content of the post, you don’t use design so often, but with templates, it’s just so powerful having a way to insert a footer, a header. And now this is even integrated more contextual. If you use this in line inserter and you are on the bottom of the page, it’ll propose you some footer patterns in other places, it will propose other patterns.
\n\n\n\nSo it tries to be smart and help you to do the right choice. So it’s no longer, only core blocks in those inline researcher, but also patterns. And yeah, in general, I really like how all the concepts that we already know, they build on top of each other that you mentioned reusable block. So you can now do sort of magic things. You find the block pattern you like, you convert that to reusable block and suddenly you have something you like, and it syncs with all other places the same applies with template parts.
\n\n\n\nYou can pick from the block directory pattern of footer and just magically it’s there and synced suddenly with all other places. So I’m looking forward to seeing more and more things like that, so people no longer have to worry that they open a new template or new post and they see blank canvas and they don’t know what to do. Now they open an inserter. There is so much inspiration in there and that you… it’s just a different experience. It’s so much easier to create the same website that you see on the themes demo side than it was before.
\n\n\n\nBirgit Pauli-Haack: Yeah, well said, Greg. That said, I also like the writing experience. So the favorite feature that I have, it’s not a big deal, but it’s actually helping, when you are doing a lot of in-line linking you have the two square brackets, and then you get a list of all the latest posts or pages that you’ve had. And then you can do in in-line linking for your site. And before you had to kind of look for that and search for it, and what’s the name of it? And you had to go out and then you had this. Yeah, so this is really nice. And I liked all those keyboard shortcuts that make it, I don’t have to change from keyboard to mouse and have a very smooth experience yeah. So 6.0 is out.
\n\n\n\nGrzegorz Ziolkowski: It’s definitely for experienced users because there are lot more gems like that. Once you discover you never want to go back and you use all the methods. But it takes time, but…
\n\n\n\nBirgit Pauli-Haack: Yeah. And then the same, what trips me up. So the WordPress had this for a long time that when you have a highlighted text, and if you have a see a link on the browser and you copy the link and you highlight text, and then you can just Ctrl V you can actually, it uses the URL as a link on that highlighted text. That trips me up everywhere else.
\n\n\n\nGrzegorz Ziolkowski: Yeah.
\n\n\n\nBirgit Pauli-Haack: Especially, so I know that GitHub took it over. Yeah, now when you want to highlight, or have a link there, you highlight the text on that. You have to URL Ctrl V works. Yeah. That’s really cool. And I use a user note taking app called LogSync. They have taken that on too, but the Google docs, every link I put in Google logs, I have to do twice because it just over click. I can’t do it anymore. It’s just so interesting. Yeah.
\n\n\n\nGrzegorz Ziolkowski: Another experience.
\n\n\n\nCommunity Contributions
\n\n\n\nBirgit Pauli-Haack: Google docs get on it. We need that there too. Yeah. So another experience that I had during the WordPress 6.0 release cycle, during the beta and release candidates, I used a great plugin that I want to do a shout out for. And it’s called the Core Rollback Plugin. And it was created by Andy Fragen, who is a long time contributor to WordPress and also part of the beta tester plugin crew. And it allows me to select all the WordPress versions back to 4.0 and install it on a test site. So I was able to test the upgrade from 4.0.23, to 6.0, and does it work or does it bomb?
\n\n\n\nAnd then at first I was a bit disappointed because when I started it, I had a block theme enabled. And of course, then I can only have a WordPress version that actually can handle block theme. So I was only rolling back to 5.9, which didn’t help me much, but then I realized that, okay, I needed to change the theme. So I changed it to Twenty Ten theme. And then the other part was, how do I get to 4.0? I also needed to change the PHP version to 5.6 and I lose local WP. So that was really interesting. And then it took me maybe a minute or two to install the old version and then upgrade was WCLI to the next version. And that was so fast to test. And then I just went into the site again and did a comment or something like that, just to make sure it works. But that is really, it was very helpful.
\n\n\n\nSo I’m sad that I didn’t know about it before, because sometimes when you had a WordPress install and the new version came out and you were way on the cutting edge, you had a plugin conflict or something like that. And then how do you roll it back to the previous version? And this plugin will save you so much time and headaches. So just make it sure that’s in your toolbox when you manage other people’s websites, because it can really help you with that, go back to the safe version within five minutes or so. And wait, the next two weeks till the next version comes out from workers. Yeah.
\n\n\n\nGrzegorz Ziolkowski: Yeah. It’s also fascinating that warper still supports some old version that to get it working, you need to use PHP version that is no longer even developed like 5.6. But still, if people have that, they can use WordPress, which is mind blowing.
\n\n\n\nBirgit Pauli-Haack: Yeah. It totally is. And I think Serge is watching that percentage of users that still use PHP 5.0 very closely, because I think it’s going to be real soon that WordPress is going to skip it and say, “okay, yeah, from now on, we are not supporting 5.6 anymore. You got to have to be on 7.4” or something like that, but it’s that promise of backwards compatibility and not kicking users out just because they don’t know they are hosting environment that still uses these old PHP variations.
\n\n\n\nWhat’s Released
\n\n\n\nAll right, but this were two interesting weeks. So we had not only WordPress 6.0 come out, but in the last two weeks, we also had two plugin releases. One was 3.2 and the other one was 3.3 and we will cover them both today. So let’s get started. So Gutenberg 3.2 was released on May 11th and it had a few new features in there.
\n\n\n\nOne was the new preference, persistence API, and we are also happy that it’s there. Now. It saves now the editor preference in user meta, not in local storage anymore for that the preference handling needed to be revamped before. So we talked about it a little bit in the last episode, but now it’s here in Gutenberg 13.2. So you won’t see the welcome guide. You dismiss the welcome guide and it will remember on the site. If you prefer the top toolbar, it will remember. And if you don’t like the full screen anymore, it will remember, but only on a site basis. So you can access the same site over and over again. And the user settings will be there for you.
\n\n\n\nGrzegorz Ziolkowski: Yeah. It might be also per editor screen. I mean, if you are on the edit site page might be different and on edit post page or widget page could be different. I don’t know, because I didn’t play with that, but I would expect that to happen this way, because in the past, those changes were independent, but it’s a huge change. We waited for so long to make it happen. It wasn’t a trivial task, but we finally have that. And it’s a huge improvement for all users.
\n\n\n\nBirgit Pauli-Haack: Yeah, definitely for new users and long time users. Yes. I probably will miss the welcome guide popping up once in a while…
\n\n\n\nGrzegorz Ziolkowski: And you can always enable it. There is a setting.
\n\n\n\nEnhancements
\n\n\n\nBirgit Pauli-Haack: Yeah. So in that version also received a visualizer for the panning and margin of all blocks. So when you use the dimension settings of your block, blue outline appears on the screen around the block and expands and contracts, depending on the width of your padding and your margins. And that is really helpful for people that don’t know what padding and margins are, but they know they want the distance and they want the distance inside or outside. Yes.
\n\n\n\nGrzegorz Ziolkowski: The other change was for the comment query loop. So there is a new block, which is post comments form. And the idea was to reach the alt experience. When on the post page you would have comments section, which usually is a list of comments and there is also the form. So the form was missing. And now inside the editor, you have something that isn’t interactive, but just presents a preview of what you will see on the front end. So it’s on the front end, of course, there will be interactive form that you can use to comment on the website, which is a great change. And that brings the feature priority with the old approach that we had in WordPress 5.9 with the post comments block that is now hidden from the insert it’s still there.
\n\n\n\nBut the idea is just to combine those blocks together in the future. So depending on what you use, what the team prefers, whether the new version of the comments log which allows you to move all the pieces around the rapid with group blocks, with all the blocks you can imagine within its template. And the old one is still based on PHP functions that all team authors know from the past, you can provide your own template with template PHP file. There is a lot of hooks, all the things. So I’m looking forward to see that combined to have a full experience for all the use cases we have for the classic blocks and for the new blocks.
\n\n\n\nBirgit Pauli-Haack: No, it’s wonderful. And I, there were about 10 new blocks coming to 6.0, with a common section. And this one, unfortunately it didn’t make it, but it’s coming then in 6.1.
\n\n\n\nGrzegorz Ziolkowski: No we made it, it was so important to bring the same experience that we added that, that was still during beta phase because, the release happens, but that change was already one or two weeks ago so that there was still time to include that.
\n\n\n\nBirgit Pauli-Haack: Oh, okay. Excellent. So there’s a full common suite. Suite of blocks for, for the common settings for themes and templates.
\n\n\n\nGrzegorz Ziolkowski: Yeah. It also came from user testing during beta phase that people were complaining that they cannot replicate, their old designs without this block.
\n\n\n\nBirgit Pauli-Haack: Yeah. So makes sense to backboard it to 6.0 yes. So we talked about the next version of the quote block and the next version of the list blocks are in experimental stage and you have to switch them on through the experience menu item on the Gutenberg plugin. And now with this release, the quote block version one now has the feature that you can exit the block just by hitting enter we know this from other blocks that works here with the list you have to hit enter twice, out of the block and then a paragraph block and the code block has now too, before you actually had to physically get out of the block by using the mouse or hitting tab or something like that. Yeah. So that’s really good. So explain to me, Greg, I’m glad you’re here. Explain to me, so I’m at the block API section where now it’s allowing the custom domain path for the view scripts, assuming that’s through register that’s for blocks and that you can have a different path than before.
\n\n\n\nGrzegorz Ziolkowski: Yeah. So that’s coming, if you ever build the theme or plugin, there is this domain pet metadata field that you can provide. It’s just when you are using translations, there is a default folder for that inside every WordPress, but as an author of the theme, you can generate all the translations yourself and put it in every folder you want. So because plugin, authors and team authors use that, we added a change that allows to provide the same type of functionality when you are registering view script, it’s mostly for plugin and team authors. And when they, if they want to have some special JavaScript code that is for many blocks, they add additional functionality, then it’s going to be useful.
\n\n\n\nBirgit Pauli-Haack: Excellent. So I know there was something important, but I couldn’t explain it. Thank you. What’s also in 13.2, is that the style engine now added typography and color to the back end for the editor so you can, can add it to the block styles and is it for the blocks, Jason, right?
\n\n\n\nGrzegorz Ziolkowski: Yeah. As far as I know the study in gen, at least at this stage of development, it’s mostly about extracting existing code to something that in the future could evolve into something more sophisticated. So it’s more on the refactor side for now, but it’s a preparation for bigger things that we have planned for the future with having unified of way of the handing styles for blocks on the PHP and JavaScript side to ensure that it’s the same on both sides and in the future, we can do interesting things, we will cover that probably with the next release, it might be going in the next release. So one of the changes that recently landed in the Gutenburg is that because of the style in gen, you can only serve CSS styles for blocks that are actually displayed on the page, which is mind blowing that you can can think about all the savings you have because of that, because you exactly know, not only the blocks you used, but also what type of styles were enabled for those blocks.
\n\n\n\nAnd I think that’s the biggest win for this whole refactoring.
\n\n\n\nBirgit Pauli-Haack: Yeah. There’s a whole discussion about, is of one of the implementation about standardizing, how themes interact with the styling of the blocks and as well as plugins. And I think that’s also necessary to standardize that in terms of when, when plugins want to introduce new blocks, they need to be able to use the variables that are introduced with the theme JSON file to just seamlessly integrate with, with an existing theme. Yeah. So what’s, I’m really sad to see that go. But what was removed was the experimental PWA support for the WP admin, which pretty much was playing around with the idea that you might get an offline and still would be able to write your post and manage your site. There was an experiment by Ella Van Durpe I think. And I think it was a good experiment, but it wasn’t pursued any further because of course, had other priorities.
\n\n\n\nGrzegorz Ziolkowski: But there is PWA plugin from Google and you can also check it out and it has a lot of similar functionality but for the front end, which is also a nice thing.
\n\n\n\nBirgit Pauli-Haack: Excellent. Yeah. And I will dig that up and show it in the show notes link in the show notes, the Google PWA plugin.
\n\n\n\nGrzegorz Ziolkowski: Yes. And one interesting, I think from the release and being on the team, so together with Adam Janinski, we work on several improvements to the workflow of bringing code from the Google plugin to WordPress core. And we are using NPM packages as a way to share code from Gutenberg and use that directing core. And we introduce a change in workflow that is automated with GitHub actions. So if someone is using GitHub and actions that they know how powerful those tools are. And now we are tagging for the WordPress major release those packages and we can easily update all of them, by using only the distribution tax, little change in the code, but it simplifies so much things inside WordPress core and how the code is shared between those two code bases, which is quite interesting. Someone wants digging into strategies for managing deep projects. I recommend that reference.
\n\n\n\nBirgit Pauli-Haack: Yeah. you should write about those little tools or little ideas that make such a difference on the release of WordPress, because I can see.
\n\n\n\nGrzegorz Ziolkowski: Oh yes.
\n\n\n\nBirgit Pauli-Haack: That other people can really benefit from that. But I think it takes a little bit more strategic approach than just a PR that it has been in the release. Yeah. And the Gutenberg release. So that would be really great.
\n\n\n\nGrzegorz Ziolkowski: Yeah, it’s interesting because usually the code you need to write is the easiest part because all the tools are so advanced these days, Github has APIs tools for that. And so it’s not an issue to code something. The issue is to come up with all the steps, what needs to happen after what, so it works together. So we definitely will be updating documentation for the release team for future releases, how we use the tools we improved and yeah, also for NPM packages, that’s also something I plan to write to describe how the process has changed with this release and to benefit everyone.
\n\n\n\nBirgit Pauli-Haack: Yeah, definitely. So I found with the release that quite a few things have been done by the same people over and over again. Yeah. So the documentation is kind of the shortcuts for them, but if a new person would step in, then it kind of needs a little bit more flesh and strategy kind of yeah. High level information in there. Yeah. So what’s again, is there anything else in Gutenberg 13.2, we wanted to talk about? I guess that’s it for 13.2 and we are going right into Gutenberg release 13.3, that was released yesterday. Ryan Welcher wrangled the release over the finish line and posted the release notes. There are comments from 55 contributors among them with their first time contribution. Yay.
\n\n\n\nThat’s really good. I was really amazed at the 6.0, sorry. Just digress again. Those WordPress 6.0 release was interesting that there were also 25% of the 500 plus contributors when new contributors, they had never done this before. So it was very interesting. It wasn’t, as I think previous releases 5.8 and nine were a little bit higher, but still, that’s a very high number of new contributors and…
\n\n\n\nGrzegorz Ziolkowski: Yeah, the number of contributors is really interesting thing we know for Gutenberg about people who contributed with scope. It’s now over 900 people and, it’s only code and there’s so many more people that help with testing with finding issues, trying to, provide designs, documentation. That’s a lot. And for core, we don’t know the exact number for all releases because we have core commuters. So which is a smaller group, like 60 or 70 people only. But I would love to do to get the exact number of people who ever got props for WordPress core, that would be a huge number.
\n\n\n\nBirgit Pauli-Haack: Yeah, must have been in the tens of thousands of people there.
\n\n\n\nGrzegorz Ziolkowski: Yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah, and you said it right. It’s not only those people that commit code, but it’s also those who, who argue about the best features, how to approach it. Yeah. and comment on things or review PRs or patches. So yeah. It must be a huge number and it’s still a huge number if you also consider the people that write documentation, the people that organized meetups, the people, they alone, 780 meetups in the world. Of course, the last two years, they were a little bit crippled because of the pandemic situation, but they will come up again and organizing months over months of meet up Wordcamp meet up, Wordcamp organizers that it’s just really amazing, people that test things. There are 20 different themes on make.wordpress.org that people could join and see what they can do.
\n\n\n\nSo if you want to do something, just a little pitch here, it’s the end user documentation team still needs writers. They triage a lot of things and all in GitHub now where you can look for the first night issues, good first issues that you could start writing and help beef up the documentation. And if you are interested in doing just that, feel free to write to me or ping me on slack or on Twitter. And I’ll have you get onboarded on that.
\n\n\n\nGutenberg 13.3
\n\n\n\nWell, let’s dive into 13.3 release. So the first thing is you can now transform a cover block into a media text block and keep most of the design too. And that’s fantastic. Because sometimes you want to do that and you couldn’t. So you had to delete the cover block and start all over again.
\n\n\n\nGrzegorz Ziolkowski: Yeah. It’s really intriguing how far you can go with transform these days and also how block adjust, because now it’s not only content, but also a lot of styles and those styles are also, taken from one place from version to another, which is quite a complex thing to do.
\n\n\n\nBirgit Pauli-Haack: Yeah. I tested it in WordPress 6.0 there is this feature where you can transform from a paragraph into a quote block or a list block. And it also keeps background color and text color. And it is really amazing. Yeah. And this transformation from cover to media text did not make it, but it’s now in the Gutenberg plugin,
\n\n\n\nGrzegorz Ziolkowski: I’m a little bit surprised to see that, but also it’s a great news that table of contents block is back in the Gutenberg plugin. I mean, it was disabled at some point because it’s hard to sell. I mean, it wasn’t ready for pride time for some reasons, but now it’s back and it’s still experimental. So that means it still needs some testing, but it’s really nice, especially for posts where you have a lot of headings because it automatically generates tables of contents, how the name says. And because of that, you will have a nice overview of what’s inside the post. And it’s also super handy to be able to go to the section when the post is very long. So that should have a lot of usage on some websites.
\n\n\n\nBirgit Pauli-Haack: Yeah. And it automatically detects your headings and creates if they’re not already in there anchor links for them. That’s how it works. So you could also use the same anchor links if you want to link from outside of the post, into the post to a certain section. So that’s definitely a nice side effect for that. And it also does it, if you have on page breaks, it detects the heading over all the pages. And it also can jump from two headings that are on subsequent pages for that post. So it’s quite sophisticated in the feature set. One feature set that I’m actually missing is that it automatically creates the table of content as a numbered list. And I have never used a number table of content on a website. So it was always in a bullet list, but I cannot change it back into a bullet list.
\n\n\n\nWhat you have to do is to kind of create a static block out of that. And then it does a bullet list. But it does not update anymore when you add a heading. So then you have to delete it and start all over again. So that’s a little bit cumbersome, but I think I will file a feature request for that to have it as a real feature I advocated for it, but it didn’t make it in the first version. So what’s also interesting actually in this release is that the post terms, you can now add dynamic variations for custom taxonomies. So when you have the post term block, it kind of also lists every taxonomies that are registered with your site. And then the other part, what I really like is that query loop block now has a parents filter.
\n\n\n\nSo when you’re working with, with a page, you can now use the parent filter to display content from the children of a particular parent page, which eliminates the need for a plugin again. Yeah. I think I need to count all the plugins that I have that I won’t use anymore because work has it built in, and the place on a list of the sub pages, or you can, even if you have featured images with it, you can even make some nice cards with that on the parent page and show up the next subsequent pages. At the agency. We had quite a few requests for that because some people couldn’t rock the post kind of post page thing and they always want the pages that’s so static. They never change, but you want them a different path of discovery and not just through the navigation menu, but also through imagery on the page where it can say, “okay, now you go here, then here and here and here,” it’s really interesting.
\n\n\n\nGrzegorz Ziolkowski: Yeah. It’s also, the way query loop evolves and how many new features gets with every plugin. It’s really interesting to follow.
\n\n\n\nBirgit Pauli-Haack: So let me ask you this, are teams working, or is a team working on the idea that you have a developer ahead who wants to kind of modify the query a little bit more granular than just what you offer through the interface, kind of handled SQL statements or something like that.
\n\n\n\nGrzegorz Ziolkowski: So to also support SQL, I don’t think that it’s on the roadmap mostly because it’s way too complex and you still can go and code yourself something very custom if you want to right? So it wouldn’t be that hard to replicate, maybe let me put it this way, replace the server implementation of the query loop, the wrapping block and provide your custom query from that. That’ll be much easier in my opinion than allowing users to start filling with as well and all the square injection, vulnerabilities and stuff like that.
\n\n\n\nBirgit Pauli-Haack: Yeah. I hear you. It’s a small thing, but in the new version, you now have tool tips on the split border radios control. So when you’re in the sidebar work on the border radios, you actually get tool tips where you are actually working on it. Is it the top part of the border or is it the left or the right part or the bottom part? And that’s really some quality interface and you can actually have a radio separate. And I didn’t know that, it’s kind of here now. You can have a radius control just for the left border. Yeah. It’s a little round, but the other three, they don’t have a radius at all. And it makes for nice, interesting forms. Now you can do this with Gutenberg in there.
\n\n\n\nAnd I also like the color controls are now merged with a dropdown component that is a little bit more helpful. It shows when you change the background color to a gradient, it now also shows you in the sidebar when you just open it, what is the current color? And it also shows the gradient instead of just the breakdown color. And you surprised that’s not the background color that I had. It’s a gradient. And now you see it all. But the color panel has gotten quite complicated as well. With the same with you click on it and then it comes out and then you have two tabs on there, one the solid color, then the gradient color. And then in the gradient, you can then change the radius and it’s gotten quite complicated. And I can see that certain things take a little longer or need to be tested first with one block before it’s rolled out to the other blocks yeah. But that makes also for sometimes it’s not consistent over all the blocks.
\n\n\n\nGrzegorz Ziolkowski: Yeah. But it also makes a lot of sense to combine all those related tools into one. So the sidebar is not so overwhelming for users. So before we had many colors, if you would open that, a year ago, that would be all those things that you see now in this tool table dropdown, they were inside the sidebar, it’s just the necessary step to organize all that better.
\n\n\n\nBirgit Pauli-Haack: Yeah. I like that curation of settings, then there is for each section heading for the color there’s on the right end side, sometimes a little too subtle, the three dot menu where you can also switch on and off some features. Yeah. By default, you only see the color for the text for the background, but when you click on the three dot menu, you also see that you could actually manage the link color, but it’s not offered for every block, but you can switch it on if you need it, for instance, for a quote block or for a list block. But sometimes you need to kind of really go beyond the obvious and click on that three dot menu to find additional features that you knew were there before, but now are a little bit hidden. Yeah, that is…
\n\n\n\nGrzegorz Ziolkowski: Yes, but if you are a new WordPress user, I’m curious how it works, because it might take some time for people to discover that the three dots actually allows you to enable more controls or remove the controls that are there, but they don’t like.
\n\n\n\nBirgit Pauli-Haack: Yeah. So the same…
\n\n\n\nGrzegorz Ziolkowski: Feeling of similar changes, there is one, I would say big change because the block list, the thing you see on the sidebar, but the other side, the one we were talking was on the right side. But on the left side, you can see all the list of all the blocks that are on a given page or template. And that’s very important for the editing experience, especially for templates where there’s a lot of nesting involved. And now there is an option in your settings to show openly view as default. So before you have to click a button to open that list, but you can just dock it and it’ll be there all the time.
\n\n\n\nBirgit Pauli-Haack: Yeah. I really like that, especially. Yeah, you’re right. The list view is such an integral part working with templates with all the nested blocks. Yeah. So having that open all the time really cuts down on the load time of the editor and your work workflow when you work quite a few templates or even in, on a normal post. Yeah. But I don’t think that setting is available for the post editor. I think it’s only for the site editor.
\n\n\n\nGrzegorz Ziolkowski: Yeah. I don’t know about that.
\n\n\n\nBirgit Pauli-Haack: Yeah. It’s only for the site editor it’s post editor. Well, has that too always open list view. Yeah. So I looked at the preference tables that were in the screenshots. It’s for both the post editor and for the site editor. Yeah. A lot of people ask me about that when I demoed some of the new features. So what else do we have?
\n\n\n\nGrzegorz Ziolkowski: There’s there is still no official post with all the change lock files. So we are using something that was prepared earlier. And so we might need to jump a little bit.
\n\n\n\nBirgit Pauli-Haack: Yeah.
\n\n\n\nGrzegorz Ziolkowski: To find other items that we have highlighted today. And one of the change is for the heading block. And now we have font family support there. So it was available in other places now it’s been enabled there for future party.
\n\n\n\nBirgit Pauli-Haack: Yeah. And a lot of people have been waiting for that our user can now change the font family for the heading block and not just the theme developer. And there’s also a enhancement for the gallery block, but especially for converting a classic block gallery into a gallery block to also include the image caption up until now it didn’t come over with it. So that’s definitely a plus for those who converting galleries to gallery blocks. Yeah. And the other two things that are highlighted here are actually part of the table of contents block. And we already talked about that. So I think we are through with that. Was there anything in the three 13.3 that you wanted to point out
\n\n\n\nGrzegorz Ziolkowski: There is a lot of items as you rule in the change logs from two releases. And also we discussed work 6.0. So I think we covered a lot today.
\n\n\n\nBirgit Pauli-Haack: Yeah. But we didn’t cover all and we never cover all. So dear listeners, definitely check out the change log that will be on the make.Wordpress.org blog when it comes out as a what’s new in Gutenberg 13.3. Yeah.
\n\n\n\nWhat’s Discussed and in the Works
\n\n\n\nAnd we are at the section, what’s discussed and what’s in the works that hasn’t been released yet? But it’s definitely top of mind and or discussed quite a bit. So there were some discussions on what keeps theme developers or agency developers who build themes for on taking, for instance, block themes or other features of the site editor.
\n\n\n\nSo those issues come up quite a bit, not quite a bit, but once in a while, and to have some ideas on what would be good for an agency. So one of them was that made it into WordPress 6.0 was for instance, that themes could register blocks. And I think Grzegorz, you were quite instrumental in that to get it fixed or get it implemented that although the recommendation says that blocks are the territory of plugins. But we heard from agencies that we are building custom themes just for that one site implementation that had additional cost also to deploy a theme as well as blocks in plugins to make it available for them. So that was one of the discussions that came out of…
\n\n\n\nGrzegorz Ziolkowski: Yeah, also the use case was that sometimes themes require some very custom design and this is a way for them to bundle a block that just is targeting that specific theme. And it wouldn’t make sense in all, all other places. And, but yeah, it’s not the recommendation blocks belong to plugins.
\n\n\n\nBirgit Pauli-Haack: Yeah, but just because it’s technically possible, doesn’t have to be, you have to use it, but it’s available for those who really, really need it. Now, before they had each agency or each freelancer who needed it, came up with their own hacks to make that. And now it’s just the standard way of using register block type on the theme PHP theme.
\n\n\n\nSo to alleviate some of the adoption hurdles or blockers for adoption there’s now a new label on the Gutenberg rebuild called focus blocks adoption. And it’s used on the Gutenberg repo to identify those specific issues that if they would be solved, they could remove the blockers from adopting blocks or block themes. And I think it’s an interesting concept now to highlight those one of them is one issue. He got that label is by Fabien who has issues C7943 titled allow the usage of block based template parts without using block based templates. And that’s an interesting idea for classic themes that want to gradually adopt what’s possible now with the site editor also for their themes and how to implement that.
\n\n\n\nAnd part of it is already Grzegorz told me, and Ari has it in the issue is already available since 5.9. But what this particular issue is talking about that it also activate the site editor to edit those template parts without editing any other templates or sections.
\n\n\n\nGrzegorz Ziolkowski: Yeah. So idea was that if you have a classic theme, you can also provide a template part HTML file that will contain this template particular template part, and that worked, but you wouldn’t be able to edit that. But the proposal is to open the UI for the same, that is inside in block themes for classic themes, which is an interesting way might be a challenge. But the more we open those solutions for classic themes, the better everything becomes.
\n\n\n\nBirgit Pauli-Haack: Yeah. And it follows the narrative that Matias actually had when he joined us here at the show, after he published the preliminary roadmap of 6.0, when he said that all the things that come with the block theme are not there necessarily to replace how themes work. It’s more to expand the reach that classic themes can offer to their users or the site owners. And I really like that narrative because it kind of, has that new can come in, but in piece and bits and you don’t have to adopt it completely, it’s a gradual adoption. And even in two or three years, you still have a need for classic themes, but there might be a need to open that up for some of the user controls or for the site owners controls. So yeah. Block themes are not replacing or making themes totally redundant. It’s actually opening up the whole place for new things.
\n\n\n\nGrzegorz Ziolkowski: It also opens an interesting world where you have a block theme, but you’ll like it, you could switch to the classic block and still retain template parts that you build in your previous theme, it’s WordPress, everyone can do whatever they like.
\n\n\n\nBirgit Pauli-Haack: Yeah. And now you can do even more and you didn’t know that you liked it. Yeah. Like gradients.
\n\n\n\nSo then another discussion that came up now that 6.0 is out Matias Ventura, the lead architect also updated already some of the tracking issues. And I’m sure there is a new blog post in the making in outlining the roadmap for 6.1. But he already has a site editor and template roadmap tracking issue about 19 tasks. And that’s about the site editor and how to create template and template parts changes to the interface or updates to the interface to make it for impossible, to edit a template part properties and focus mode. What is a focus mode? It’s another way of seeing the editor. There’s also a browse mode coming to the site editor that you look at it from, you just browse the designs, but you’re not editing.
\n\n\n\nSo yeah. And other things like restricting block editing capabilities, we talked about the block locking at the beginning of the show that comes in 6.0, and that is now that needs to be expanded on. You mentioned that it needs to be role based of course, but also you probably want to lock down the editing part of a footer or header that people can edit it. Not just remove it or move it, but also not edited that is still missing.
\n\n\n\nSo there are quite a few in this tracking issue, hints of what’s to come. And if you’re curious, we of course share the link in the show notes and what he did for template for the site, edit 10 templates, roadmaps Matias Ventura also published a global style, ongoing roadmap that he updated. And that covers some of the style engine that we talked about. If you want to learn more about it, also the main interface for making changes to the global styles, browsing styles, without having to edit things, web fonts that would just have the web fonts for the style variations right now. But the big part of the web funds API didn’t make it into 6.0, but it will hopefully make it into 6.1.
\n\n\n\nGrzegorz Ziolkowski: Yeah. Also interesting discussion on Twitter where Matias were involved about the future of web phones that maybe openverse could host some web phones and having those open source version of phones, integrated with the WordPress for everyone. That’s also interesting perspective and general openverse opens so many new ways of reusing content created by other people, which is images, videos, music, and whatever… Phones. That would be another way.
\n\n\n\nBirgit Pauli-Haack: Yeah, and color palettes would actually be also quite interesting. Yeah. So you can swap out the color palette of your theme and just by bringing it in from the openverse. Yeah. Oh, did you see that there’s a new contributor batch if you added photos to the openverse, to the WordPress photo directory, you can now see that on your profile. Open verse open so many different things for WordPress. It’s amazing, yeah.
\n\n\n\nGrzegorz Ziolkowski: I already have this batch. I just checked.
\n\n\n\nBirgit Pauli-Haack: Yeah me, too
\n\n\n\nGrzegorz Ziolkowski: I Uploaded two photos.
\n\n\n\nBirgit Pauli-Haack: Yeah. I think I uploaded four or so but yeah, it doesn’t matter. It’s a contribution and it will be honored. Yeah. So you have the site editor, the template, the global styles tracking issue. And then the last one is pattern as the section elements. That’s kind of the next phase for patterns and interesting proof of concept there’s first a tracking issue. And then James Costa has quite a few little videos and what he kind of considers as a browse mechanism for where you can browse through certain block patterns for the header, for instance, but you see the full page and that will make working on their site so much easier when you’re actually not only just looking at that section, that’s visible in your screen, but you can see the full page. And that’s also available for posts, for instance, or for pages that you create. So there are quite a few things in the works that hopefully make it.
\n\n\n\nGrzegorz Ziolkowski: It, the idea for those sectioning element is really interesting. You mentioned that you can just have the recent exploration is to have zoom out mode. So, you focus on the header and then you get ways to quickly switch the versions of this header by using block patterns or maybe pre-existing template parts, and you just use arrows or something else depending, or how you use that. And how’s going to maybe implement, and it just quickly switch to another version. Another, until you find something that clicks for you, but it’s inside the page. It’s not that you open a model, then you see only just some preview of these things, but you exactly see how it fits to your website.
\n\n\n\nBirgit Pauli-Haack: Yeah, and so we will share the links to those comments and PRs in the show notes. And if you’re interested in where things are going, definitely look at those and see what it does for you. And if you have ideas, how it’s made better or what does not look right or how it can be augmented. Yeah. Chime in now is the time because now people are working on it. And the last discussion that I wanted to point out is that during the FSE program Anne McCarthy did a hallway hangout to talk about the FSE programs and how it works and all that. And then there’s an issue created or it’s not an issue, it’s a discussion post on the developer experience category on the GitHub discussions. And what the full site editing for agency use case is what are the existing features that work that are available and then what are missing features.
\n\n\n\nAnd then as well as the features that can be improved, for instance, as a missing features, it identifies the robust permission system for the template editing, as Grzegorz mentioned earlier, or another one is allow editing for only template parts or only specific template parts, but not other parts or other templates that is much more granular. Another interesting thought was that WordPress inland CSS does not always respect the editor font sizes. That might be a bug, but it could also be that some of the mechanics don’t work as well.
\n\n\n\nBut that comes all out of a hangout meeting, which is a hallway hangout meeting is kind of an informal meeting of brains, people that discuss certain things. And this came out of it. I shared the hangout notes, hangout recap, post by Anne McCarthy, as well as this discussion at the GitHub repo. So for all you interested people. All right. So Gregorz, we are at the end of our show. I’m so glad that you were able to jump in for Mary Job this week and walk us through some of the things. Thank you so much.
\n\n\n\nGrzegorz Ziolkowski: That was a pleasure to meet with you again and talk about Gutenberg.
\n\n\n\nBirgit Pauli-Haack: Yeah. And as always the listeners, the show notes will be published on Gutenbergtimes.com/podcast. And if you have questions and suggestions or news, you want us to include sent them to changelog@gutenbergtimes.com that’s changelog@gutenbergtimes.com. So this was it from me. Thank you for listening. Thank you for stopping by. I’m glad you were here and I will talk to you in two weeks. I say goodbye and goodbye, Greg, to you until I see you again.
\n\n\n\nGrzegorz Ziolkowski: You for having me, Birgit. It’s always a pleasure. See you goodbye.
\n\n\n\nBirgit Pauli-Haack: Yes. And come see us all at Wordcamp Europe. Bye bye.
\";s: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, 28 May 2022 20:45: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:19:\"Gutenberg Changelog\";s: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:49:\"BuddyPress: BP Rewrites 1.2.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=324836\";s:7:\"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://buddypress.org/2022/05/bp-rewrites-1-2-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:849:\"Immediately available is BP Rewrites 1.2.0. This maintenance release fixes two bugs. For details on the changes, please read the 1.2.0 release notes.
\n\n\n\nUpdate to BP Rewrites 1.2.0 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.
\n\n\n\n\n\n\n\nMany thanks to 1.2.0 contributors
\n\n\n\nshawfactor & imath.
\";s: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, 28 May 2022 05:33: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: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: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:50:\"Post Status: What’s a WordPress “Developer?”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=98436\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"https://poststatus.com/whats-a-wordpress-developer/\";s: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:383:\"It’s a good time to celebrate growth, maturity — and longevity. This is our 500th issue. WordPress is 19! And the 6.0 release is just a few days old, with new and old hands contributing from all over the world. Many are \"developers\" of some kind. Those who are showing up every day to make the project work and to make a living in WordPress are the professionals. Here\'s to them!\";s: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, 28 May 2022 00:35:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Dan Knauss\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:28:\"WPTavern: WordPress Turns 19\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=134868\";s:7:\"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:39:\"https://wptavern.com/wordpress-turns-19\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3626:\"Today marks 19 years since 19-year old Matt Mullenweg partnered with Mike Little to release the first version of WordPress based on the b2/cafelog software. The blog where he shared his thoughts on life and tech was starting to get more traffic and he wanted to ensure its future after the b2/cafelog’s main developer disappeared.
\n\n\n\nMullenweg had the vision for what WordPress should be, even before it had a name. It centered on extensibility, a hallmark feature that has made the platform as popular as it is today:
\n\n\n\n\n\n\n\nWhat should it do? Well, it would be nice to have the flexibility of MovableType, the parsing of TextPattern, the hackability of b2, and the ease of setup of Blogger.
Matt Mullenweg – The Blogging Software Dilemma, January 24, 2003
Although Textpattern, the interesting new publishing tool at the time, had everything Mullenweg might want in a blogging tool, he wasn’t sure about its licensing at the time. He decided to fork b2/cafelog, which lives on today in a different form as WordPress, thanks to its GPL licensing. Mike Little joined the effort and the rest is history.
\n\n\n\nThe highlight of this year’s anniversary celebrations is the wp19.day website created by David Bisset and his daughter Olivia Bisset, who also managed the project. WordPress users and contributors from all over the world left their heartfelt greetings to celebrate the occasion. Reading through, it’s easy to get a sense of the tremendous good WordPress has done for the world, giving so many a voice, a livelihood, and a chance to live their dreams.
\n\n\n\nThe wp19.day website also featured video submissions from WordPress enthusiasts. Although many first came for the software, the common thread among those who have stayed is the value of the community that has grown up around the project and the leadership it has cultivated. WordCamp and meetup organizer Joe Simpson said WordPress empowered him to take a leadership role in his local community.
\n\n\n\n“Our community here is nurturing – it’s a family,” Simpson said. “I’m excited to see where we go from here. Happy birthday, WordPress.”
\n\n\n\n\n\n\n\nMatt Mullenweg also joined in the fun of celebrating the milestone by contributing his own greeting to the wp19.day project. In his video submission, he said it’s very rare for a 19-year-old software project and its community to not just still be surviving but actually thriving and “doing better than ever.” He thanked contributors of all kinds who have helped people find their way with WordPress.
\n\n\n\nMatt Mullenweg on WordPress’ 19th Birthday – video source: wp19.day\n\n\n\n“That is a testament to every single person who has ever told a friend about WordPress, participated on the forums, had a translation, contributed code,” Mullenweg said. “Anything that’s been part of the WordPress ecosystem is part of why WordPress is transforming the web and making it into a place that is more open, more inclusive, more democratic, and a place that we want our future generations to grow up in.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 May 2022 22:12:13 +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:54:\"Post Status: WooCommerce Function of the Week: add_fee\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=98289\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://poststatus.com/woocommerce-function-of-the-week-add_fee/\";s: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:321:\"Before we dive in this week\'s function, please note that it\'s usually against any payment provider\'s Terms of Service (like PayPal\'s) to add fees to a transaction based on the customer\'s chosen payment gateway, so please make sure to use “cart fees” in a legal way. You got it — in this issue we\'ll study...\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 May 2022 21:29: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:15:\"Rodolfo Melogli\";s: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:72:\"WPTavern: Gutenberg 13.3 Introduces Experimental Table of Contents 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=134845\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://wptavern.com/gutenberg-13-3-introduces-experimental-table-of-contents-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:1960:\"Gutenberg 13.3 was released this week with support for an experimental new Table of Contents block. It is perfect for longform content that is organized by multiple headings within the document. The block automatically detects Heading blocks within the content and will display them with anchor links that jump to each section.
\n\n\n\nTable of Contents block – video credit: Gutenberg 13.3 release post\n\n\n\nUsers may select the block without knowing how it works with headings. If the post or page doesn’t contain any headings, the block inserts a message prompting users to start adding Heading blocks in order to display a Table of Contents.
\n\n\n\nFor sites that have registered custom taxonomies, Gutenberg’s Post Terms Block now automatically generates a block variation for each term. That means users can select a block to display all the terms associated with that custom taxonomy.
\n\n\n\nOther notable additions in 13.3 include the following:
\n\n\n\n- Query block now supports a “parent” filter that will display content of children from the defined parent
- Heading block now supports Font Family controls
- Save Block List default view preference – allowes users to set a preference for having the Blost Lick view open or closed by default
- New transforms between the Cover and Media & Text blocks
The latest release also brings dozens of enhancements and bug fixes to preferences, border controls, error messages, tooling, accessiblity, and performance. Check out the release post for the full list of changes.
\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 May 2022 18:21:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Matt: WordPress 19\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=56325\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://ma.tt/2022/05/wordpress-19/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1096:\"Today is the 19th anniversary since WordPress’ first release, which is especially exciting for a number of reasons:
\n\n\n\n- The community put together an awesome site celebrating the occasion at wp19.day.
- We just had an awesome 6.0 “Arturo” release.
- Next week June 2-4 WordCamp Europe returns in-person in Porto, Portugal, and I’ll be there and so excited to connect with the community! Tickets are still available.
- Nineteen seems like an in-between number, but actually it’s very salient for me because now WordPress is the same age I was when the first release came out.
- Which means I’ve now been working on WordPress half my life!
Cheers and here’s to many more years together. ![\"?\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f942.png\")
By Dan Knauss and David Bisset ![\"?\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f5d3.png\")
May 27, 2022
It\'s the 500th issue of Post Status Notes and the Post Status newsletter coinciding with WordPress\'s 6.0 release and its 19th anniversary! ![\"?\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f382.png\")
WordPress 6.0 Released
\n\n\n\nWordPress 6.0 “Arturo” was released on schedule (May 24th) with many new features and enhancements related to full site editing.
\n\n\n\n- Gutenberg 13.3 was released yesterday.
- Check out Anne McCarthy‘s post on the latest core editor improvements to container blocks and block locking. Anne shows off some new features to explore with rows, stacks, and groups.
- Anne also has a recap (video and written highlights) of yesterday\'s hallway hangout on Full Site Editing topics.
The Global Community of Contributors
\n\n\n\nJean-Baptiste Audras offers some interesting stats for the 6.0 release as he\'s done with six previous releases — 5.3, 5.4, 5.5, 5.6, 5.7, not 5.8, and 5.9) so we can see compare them. Some highlights:
\n\n\n\n- 519 people (~25% were first-time contributors) from at least 53 countries and 134 identified companies contributed.
- The United States leads in contributions followed by Russia, thanks to Sergey, who had the highest number of individual contributions to 6.0. Then comes Jean-Baptiste himself in France and George Mamadashvili in Georgia.
- Automattic (with its 70 contributors) had the most contributions, followed by Yoast, Whodunit (France), and GoDaddy.
It\'s interesting to see how national populations, the number of their contributors, and their total contributions are independent variables that can vary widely. Automattic‘s Jorge Filipe Costa from Portugal is in the top 20 by contributions, and Portugal ranks high despite having only three contributors in all.
\n\n\n\nSome standout individuals, like Sergey, George, Jean-Baptiste, and Jorge do an enormous amount for the project, and there are quite a few of them! It is ultimately a community effort.
\n\n\n\nWordPress\'s Last Year as a Teenager
\n\n\n\nNyasha Green interviewed Olivia Bisset about her work on wp19.day. Olivia is also an intern here at Post Status. (An enthusiastic WordPresser, coder, WordCamp speaker and volunteer, Olivia is slightly younger than WordPress itself.)
\n\n\n\nNewly posted to WP19.day: brief video greetings from Matt Mullenweg, Lindsey and Cory Miller, Syed Balkhi, Vito Peleg, much of the team at Yoast, and many others.
\n\n\n\nWordCamp Updates
\n\n\n\nHari Shanker R passed along the news that regional WordCamps will not need to go through a proposal process anymore — they can directly apply to organize a camp for their region using the WordCamp application form. From now on, “WordCamp Central will evaluate the health of local communities when assessing a regional WordCamp application.”
\n\n\n\nBob Dunn has some nice, bite-sized tips on building WordPress sites from some of the speakers at the upcoming WordCamp Europe 2022.
\n\n\n\nGiving Back and Looking Forward
\n\n\n\nThomas Fanchin at Weglot has a great post about his company enthusiastically embracing Five for the Future and becoming a WordPress Global Sponsor. He notes how much there is to look forward to in events, worldwide, in 2022.
\n\n\n\nWeglot has been sponsoring Juan Hernando, a WCEU organizer (among other things) and now Pedro Mendonça on the core Polyglot team.
\n\n\n\nWhat Contributions Count for Five for the Future?
\n\n\n\nJosepha Haden Chomphosy has taken a stab at defining activities that can be considered contributions to Five For the Future, and she is looking for feedback.
\n\n\n\nJosepha says valid 5ftF contributions should clearly benefit the WordPress project and not an individual person or company. Contributions related to creating or supporting (third-party) WordPress themes, plugins, or blocks “are critical to extending the reach and utility of the WordPress project,” but they are also in a “grey area.” Generally they shouldn\'t be associated with the Five For the Future mission or count toward corporate commitments to the program.
\n\n\n\nIn the comments, Adam Warner asked if completely free code like Contact Form 7 might be worth counting, and Brian Gardner asked about contributions to the Pattern Directory with Courtney Robertson chiming in about CC0 images contributed to Openverse.
\n\n\n\nManaged WordPress(.com) Hosting Starter Plan
\n\n\n\nWordPress.com has launched a new plan called “WordPress Starter“ for $5/month. It seems to be a the “in-between” option some were looking for earlier when the “Pro” level was first announced. The “Starter” level includes custom domains, additional storage, simple payment processing, and Google Analytics to the free option.
\n\n\n\nNotably, WordPress.com is increasingly being marketed as a web host for “managed WordPress hosting,” and it can claim to be the fastest on the planet.
\n\n\n\nWordPress and Sustainability
\n\n\n\nJoost De Valk explains how optimizing search engine crawling can help save energy — and therefore the environment. Remember that search engines will crawl almost any URL they can find in your page source.
\n\n\n\nTom Greenwood shares some tips on reducing waste in web design. Even if you just stop autoplaying videos, that\'s a start.
Over at the Matt Report, Hanna Smith asks, “Can WordPress save the planet?”
It\'s good to see these economic and ecological concerns emerging more in the WordPress space. If you\'d like to take a hard look at the situation, try starting with the Stockholm Resilience Centre‘s Planetary Boundaries Framework (CC BY 4.0).
\n\n\n\nOne of Bill Gates‘ favorite authors, Vaclav Smil, is also worth a weekend deep dive. Smil is a Czech-Canadian scientist and policy analyst on the Faculty of Environment at the University of Manitoba. His new book, How The World Really Works, was summarized nicely in the latest issue of Sentiers by Patrick Tanguay.
\n\n\n\nOpportunities for Lean WordPress and WooCommerce Solutions?
\n\n\n\nRob Howard asks what growth opportunities WooCommerce might see ahead as Shopify suffers a post-pandemic decline in its stock price and market share. Shopify will likely stabilize as pressure from Wix, Squarespace, and WooCommerce increases. Some would say — unfavorably — this is an “Apple-like” tactic. But Rob\'s right — there\'s an opportunity here for WordPress and Woo:
\n\n\n\n\n\n\n\n“Let Shopify, Squarespace and Wix duke it out for the low-end market, and do everything you can to help WooCommerce corner the market for higher-end, highly custom e-commerce solutions.”
There\'s also a good opportunity for a “build a store on a mobile device quickly” experience now.
\n\n\n\nCheck out the new Fruits platform — it seems to do just that.
\n\n\n\nWhat if something similar existed based on a trimmed-down WordPress install? Want a full store with custom features? Click a button, and it becomes the full WordPress + Woo experience ready for customization.
\n\n\n\nChristina Warren and Dan Knauss have similar thoughts about a Substack or Ghost-like distribution of WordPress.
\n\n\n\nWordPress Job Titles and Skills – Where Do We Stand? (2015-22)
\n\n\n\nThis recent Woo DevChat, with Zach Stepek, Till Krüss, and Carl Alexander is a deep, funny, and much more thoughtful (and generously, even inclusive) take on the age-old question “What is a WordPress Developer?”
\n\n\n\nTen years ago this topic was reliable clickbait for much wp-drama because it was often expressed as “who counts” or “who deserves to be called a Developer?” Will the real developers please stand up? Perspectives have changed and matured a lot.
\n\n\n\nMaybe today there is such a thing as a “No-Code Developer…”
\n\n\n\nZach, Till, and Carl\'s conversation is reminiscent of this 2015 post by Mario Peshev and the comment discussion it provoked. It\'s worth a read still, and so are the comments.
\n\n\n\nMaybe that\'s where Bob locked onto Site/WordPress/Woo “Builder.” I knew “Integrator” and “Customizer” would never be widely used.
\n\n\n\n2015 is probably about when (if not exactly where) a lot of us locked onto the inclusive but specific term, “WordPress Professional” that Jenny Beaumont introduced in the discussion over Mario\'s post.
\n\n\n\n“WordPress Professional” slid into Post Status\'s self-understanding too and grew to become quite central to our idea of membership.
\n\n\n\nDo you enjoy our weekly notes?
\n\n\n\nGet them and more in Post Status\' Week in Review. We gather WordPress and WooCommerce news along with significant writing, videos, and podcast episodes from the WordPress community and beyond. Don\'t miss the latest updates from the people making WordPress in our This Week at WordPress.org summaries. It\'s all in our newsletter! ![\"?\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f48c.png\")
WordPress turns 19 today. And as I did my first draft of this podcast, I found myself redoing it. I have it all wrong.
\n>> The post WooBits: Happy Birthday WordPress_Community appeared first on Do the Woo - a WooCommerce Builder Community .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 May 2022 09:09:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"Post Status: WordPress Podcast and Video Picks for the Week of May 22\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=98170\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://poststatus.com/wordpress-podcast-and-video-picks-for-the-week-of-may-22/\";s: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:3836:\"Catch up on the gold at Wordsesh! Mark Ashton on the success of UiPress. Hanna Smith on web sustainability. Michelle and Allie on sponsored events. Mark Root-Wiley on CSS Standards for WordPress. Takis and Taeke on organizing WCEU.
My Podcast Picks ![\"?\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f399.png\")
\n\n\n\n- Make Lemonade: Mark Ashton shares his story of success with his product UiPress, a plugin that provides a white label WordPress admin experience.
- Matt Report: Hanna Smith talks about web sustainability.
- Underrepresented in Tech: This episode contains a discussion about the challenges of sponsored events in WordPress.
- WP Tavern Jukebox: Mark Root-Wiley talks about creating standards for CSS in WordPress.
- Do the Woo: Two of the WCEU organizing team members, Takis Bouryouris and Taeke Reijenga, talk about that upcoming conference.
- Woo DevChat: What is a WordPress Developer? with Zach Stepek, Till Krüss, and Carl Alexander.
My Video Picks ![\"?\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f4fa.png\")
\n\n\n\n- WordSesh: Learn the path From Agency Owner to Plugin Shop from Lesley Sim, Aurooba Ahmed describes how to Hack the Block Editor for Faster Content Creation, Vikas Singhal has 5 Easy Ways to Fix your WordPress Workflow, and Leonardo Losoviz asks, Will WordPress be Better with the Block Protocol? Keynotes include Anil Gupta explaining How Big Enterprises Use WordPress for Publishing, the 10up team on Rebuilding WhiteHouse.gov in Six Weeks, and Susan Enners, Matthew Haines-Young, and Wisdom HamboluI on Building and Defending a Free Press. It\'s all there — and more!
Get our weekly WordPress community news digest — Post Status\' Week in Review — also available in our newsletter.
And don\'t miss the latest updates from the people making WordPress. We\'ve got you covered with This Week at WordPress.org. ![\"⚙\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/2699.png\")
After a lengthy discussion, the Community Team has decided to make it easier for organizers to apply for regional in-person WordCamps. These are events that pull in a community from a geographical area larger than one city or metro area.
\n\n\n\nIn past years, WordPress Community Support (WCS) saddled regional events with numerous additional requirements beyond regular WordCamps, such as preparing a proposal and a minimum of three cities in the region hosting local events, with at least one having hosted a WordCamp.
\n\n\n\n“The Community Team has decided to simplify the guidelines for regional in-person WordCamps,” Automattic-sponsored WordPress.org community manager Hari Shanker said.
\n\n\n\n“Moving forward, regional WordCamps will not need to go through additional steps (such as writing a proposal), and can directly apply to organize a camp for their region using the regular WordCamp application form.”
\n\n\n\nShanker asummarized community feedback that influenced the decision to ease up on the requirements and move towards using common sense as guide for hosting regional WordCamps:
\n\n\n\n- Regional WordCamps could be beneficial in restarting events in a region in a post-pandemic situation. It would be a great way to revive the community.
- WordCamps should be evaluated on a case-by-case basis, with conditions such as the region, geographic size, country, etc.
- Successful Country-based WordCamps were held in the past, and the community team should not police event organizers based on the region. The event organizing process could be simplified.
- City-based events could be difficult to organize because it’s difficult for a small group to organize a big event. It also causes repetition and a lack of repeat value for sponsors. Regional WordCamps might be a great way to solve this problem.
Shanker emphasized that while guidelines are being simplified, it’s imperative that local meetups are presesrved when regional WordCamps are organized.
\n\n\n\n“Local communities offer more accessible ways to connect over WordPress, and more supportive pathways to participation in larger, more complex events,” he said.
\n\n\n\nOrganizers who are interested in starting up regional WordCamps are encouraged to continue developing local leadership and will be required to impose a strict, two-year term limit on lead organizers.
\n\n\n\nMore simplified guidelines for these events is particularly beneficial in Europe where many smaller countries find that regional WordCamps have a strong unifying effect for their WordPress communities.
\n\n\n\n“There is a reason that a ‘small country’ like The Netherlands is now in the top of WordPress contributors and companies,” WordCamp organizer Dave Loodts commented on the previous discussion. “It all started in the lap of all the previous WordCamp The Netherlands. Never underestimate the power of these kinds of events.”
\n\n\n\nShanker is requesting feedback on the proposal, particularly on what metrics should be in place to determine the health of regional communities. The proposed change has already started receciving positive feedback.
\n\n\n\n“Switzerland is like the Atlanta metropolitan area in term of population (8 millions vs 6 millions = ‘similar’) and about 10 meetup groups,” Geneva meetup organizer and WordCamp Switzerland co-organizer Patricia BT commented.
\n\n\n\n“Since we had to rename Switzerland to city name after 2015, we knew it was unrealistic to have more than one per year in the country (like if you asked people of Atlanta to have one WordCamp per meetup group) so we moved it from city to city year after year, which was awesome to onboard new organisers, but still missing a ‘united’ event.
\n\n\n\n“It’s really cool that we can now go forward with WC Switzerland next year, as I feel we had lost a bit of the ‘Swiss community momentum.’ We will recreate that feeling again next year.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 26 May 2022 18:55:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"Post Status: Post Status Upgrade: Group Facilitation Skills\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=98118\";s:7:\"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://poststatus.com/post-status-upgrade-group-facilitation-skills/\";s: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:2893:\"Learn new skills and build your knowledge to enhance your career in WordPress! Post Status Upgrade is an ongoing series of live workshops centered around a particular skill or learning activity.
\n\n\n\nPost Status\' motto — Give, Grow, Together — is more than just a phrase we repeat a lot. We live our motto. This training will give you key insights into how to facilitate group conversations with an eye to giving and growing together.
\n\n\n\nThis is a training workshop for anyone who wants to be a facilitator or a participant in the small groups that Post Status will be rolling out soon for its members.
\n\n\n\nGroup Facilitation Skills with Corey Wilks. \n\n\n\n![\"Corey](\"https://cdn.poststatus.com/wp-content/uploads/2022/05/corey-wilks-150x150.png\")
Corey Wilks is a Licensed Clinical Psychologist and Executive Coach. His mission is to help founders, creators, and entrepreneurs build an Intentional Life using evidence-based psychology.
\n\n\n\n“How do I define an Intentional Life? Spending your most precious resource—time—doing meaningful, purpose-driven work that fulfills you. It’s about clarifying your Core Value, embracing your authenticity, and reaching your potential by building your life, and your business, around what resonates with you on a fundamental level.”
Dr. Corey Wilks
![\"StellarWP\"](\"https://cdn.poststatus.com/wp-content/uploads/2022/02/stellarwp-black-1-300x300.png\" "\\"StellarWP\\"")
StellarWP is a collective of WordPress innovators empowering business owners and creators with plugins and tools to help them thrive. We build great plugins, but we don’t stop there; we continually challenge ourselves to keep innovating and improving. Our solutions include the most trusted names in WordPress, with more than 2.5 million installs. Since 2021, we’ve grown to encompass seven brands and dozens of plugins. StellarWP is part of the Liquid Web family of brands.
Zach Stepek, Till Kruss and Carl Alexander have a conversation on how and if you can define a WordPress developer.
\n>> The post Woo DevChat, What is a WordPress Developer with Zach, Till and Carl appeared first on Do the Woo - a WooCommerce Builder Community .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 26 May 2022 09:33:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:54:\"Post Status: This Week at WordPress.org (May 23, 2022)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=98186\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://poststatus.com/this-week-at-wordpress-org-may-23-2022/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14991:\"Each week we are highlighting the news from WordPress.org that you don\'t want to miss. If you or your company create products or services that use WordPress, we\'ve got the news you need to know. Be sure to share this resource with your product and project managers.
Are you interested in giving back and contributing your time and skills to WordPress.org? ![\"?\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f64f.png\")
Start Here ›
Get our weekly WordPress community news digest — Post Status\' Week in Review — covering the WP/Woo news plus significant writing and podcasts. It\'s also available in our newsletter.
News
\n\n\n\n- WordPress 6.0 “Arturo”
- The Kim Parsell Memorial Scholarship Returns for WordCamp US 2022
- Defining Five for the Future Pledges & Contributions
- Request for feedback: Recording Five for the Future contributions
Accessibility
\n\n\n\n- Request for feedback on the WordPress Accessibility Statement.
Central
\n\n\n\n- WordCamp Europe 2022 is just around the corner
- Join the European WordPress Community in Porto, Portugal!
Core
\n\n\n\n\n\n\n\n- Core Editor Improvement: Creating & containing containers
- Survey to hosting providers from Performance team
- Performance team is seeking points of contact to contribute to Site Health iniatives
- Measurement overview doc
- Capturing front-end performance metrics in WordPress doc from Performance team
Community
\n\n\n\n- Regional In-person WordCamps Going Forward
- Seeking Feedback on Annual Meetup Survey for 2021-2022
- Meetup Organizer Newsletter: May 2022
- WordCamp Europe 2022 Contributor Day: Plans for the Community Team Table
Docs
\n\n\n\n\n\n\n\nSupport Docs:
\n\n\n\n\n\n\n\nDeveloper Docs:
\n\n\n\n- WP_Widget_Media::reset_default_labels()
- WP_Widget_Media::get_l10n_defaults()
- WP_Widget_Media::get_default_description()
- term_exists_default_query_args
- registered_taxonomy_{$taxonomy}
- the_author_link
- WP_Taxonomy::get_default_labels()
- WP_Taxonomy::reset_default_labels()
- WP_Post_Type::get_default_labels()
- register_{$taxonomy}_taxonomy_args
Design
\n\n\n\n\n\n\n\nMeta
\n\n\n\n\nMobile
\n\n\n\n- Mobile Team Update – May 18th
- Call for Testing: WordPress for Android 19.9
- Call for Testing: WordPress for iOS 19.9
Plugins
\n\n\n\n\n\n\n\nPolyglots
\n\n\n\n\n\n\n\nProject
\n\n\n\n- Request for feedback: Recording Five for the Future contributions
- Discussion: Contrib Handbook, Part 3
- Defining Five for the Future Pledges & Contributions
- Discussion: Contrib Handbook, Part 2
- Discussion: Contrib Handbook, Part 1
Test
\n\n\n\n- Hallway Hangout: Discussion on Full Site Editing Issues/PRs/Designs (25 May)
- Test Team Rep: Call for Nominations for Remaining Current Term
Themes
\n\n\n\n\n\n\n\nSupport
\n\n\n\n\n\n\n\nTraining
\n\n\n\n\n\n\n\nLesson Plan
\n\n\n\n\n\n\n\nWorkshop
\n\n\n\n\n\n\n\nSocial Learning Spaces:
\n\n\n\n\nFive for the Future
\n\n\n\nWhat\'s happening specific to Five for the Future? Provide your feedback on these posts:
\n\n\n\n- Default workflow for team membership lifecycle?
- Add activity when Meetup organizers host events
- Update Usermeta with latest 5ftf contribution.
![\"Post](\"https://cdn.poststatus.com/wp-content/uploads/2021/09/vertical-post-status-logo-250.png\"){kind=logo}
You — and your whole team can Join Post Status too!
\n\n\n\nBuild your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. ![\"✉\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/2709.png\")
Listen to podcasts. Follow @Post_Status. ![\"?\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f426.png\")
WordPress.com announced a new “Starter” plan today for customers that bridges the pricing gap between the free plan and its $15/month Pro plan. The Starter plan is $5/month and includes a custom domain name, along with 6GB storage, and the ability to use payment collection blocks (Donations Form, Premium Content, and Payment Button).
\n\n\n\nWhen WordPress.com rolled out major, unannounced pricing changes on April 1, slashing free storage limits, users took to the forums to express their profound disappointment in the controversial update and the company’s lack of communication around it. After receving overwhelmingly negative feedback, WordPress.com increased traffic and storage limits on the free plan before officially announcing it.
\n\n\n\nSeven weeks after WordPress.com began testing the waters with pricing changes, the company has responded to feedback about the wide gap between the free and Pro plans. Many customers were diappointed to learn that they would have to pay $15/month to have access to custom domain names, even though they do not need the commercial themes and plugins included in the Pro plan. Some users expressed that they felt “trapped in the net” with the pricing updates and planned to shift their sites to new platforms.
\n\n\n\nThe new Starter plan solves some of these customer issues but it is still partially subsidized by advertising. Customers on this plan and the free plan will have ads displayed on their sites. This is different than the legacy Personal plan, which was $4/month for no ads, a custom domain, and the ability to collect payments. The fact that the new Starter plan costs more but doesn’t remove ads is a point of contention customers mentioned in the comments on the announcement. It does, however, include Google Analytics integration, which was previously limited to customers on the legacy Premium plan and higher.
\n\n\n\n“The Starter plan is not meant to be a replacement for the old legacy Personal plan,” WordPress.com CEO Dave Martin told the Tavern. “Our goal with every additional pricing iteration that we launch will be to learn something new. The Pro plan and the Starter plan are two of many future iterations that we plan to experiment with.”
\n\n\n\nMartin also reiterated that customers on the legacy Free, Personal, Premium, Business, or eCommerce plans are able to continue on them.
\n\n\n\n“[If] you are happy with your current plan, we have no plans to force you to change,” Martin said. “You can stay on your current plan.
\n\n\n\n“Finding the right balance between the value that we deliver to our customers and the price that we charge in exchange for that value is something that generally has to be iterated towards. We plan to do just that.”
\n\n\n\nMoving forward, Martin said WordPress.com is aiming to do a better job at communicating important updates to customers.
\n\n\n\n“I made a mistake with how we communicated the pricing changes with WordPress Pro,” Martin said. “We listened to feedback from our customers, I took responsibility for it, and then we worked to correct that with this next phase of our pricing change. We’re constantly working to be better at communicating updates.”
\n\n\n\nIt’s interesting to see how WordPress.com is evolving its pricing in response the market and WordPress’ changing capabilities. Whereas the legacy plans leaned heavily on selling access to commercial themes, full-site editing has changed the game, giving users more customization power than before.
\n\n\n\nThe company is still planning to introduce a range of add-ons for the Starter plan to give customers more flexibility. It’s possible there will be add-ons for removing ads and adding more storage, but the company still hasn’t announced what they will offer.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 25 May 2022 21: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:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: #28 – Mark Root-Wiley on Creating Standards for CSS 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:48:\"https://wptavern.com/?post_type=podcast&p=134775\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://wptavern.com/podcast/28-mark-root-wiley-on-creating-standards-for-css-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:61298:\"On the podcast today we have Mark Root-Wiley.
\n\n\n\nMark builds WordPress websites for nonprofits in Seattle, Washington, USA with a focus on accessibility and usability. He’s a long-time WordPress community member in Seattle and has previously helped organise WordPress Seattle meetups and WordCamp Seattle speakers.
\n\n\n\nHe maintains Nonprofit WP, a free guide for people building WordPress websites for their nonprofits, and has a few free plugins available on WordPress.org.
\n\n\n\nHe’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards.
\n\n\n\nOver the years, as WordPress has evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You could do what you like, and that worked very well, after all, we all have preferred ways of doing things.
\n\n\n\nNow however, the reach of WordPress has outgrown those early roots and some 40+ percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites as they try to unpick the way that the CSS is built and implemented.
\n\n\n\nMark thinks that it’s time for WordPress to lay out some simple standards which are easy to understand, and if they became universal, would save us a lot of time and head scratching.
\n\n\n\nHe’s not proposing anything radical, just some basic advice for the most commonly used CSS, and it’s quite a compelling idea which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards.
\n\n\n\nIt’s very much the kernel of an idea at present, but thought provoking nonetheless.
\n\n\n\nUseful links.
\n\n\n\n\n\n\n\nStandardized block markup, theme.json design tokens, and CSS classes to improve interoperability
\n\n\n\nVariable Design Token Scales with Static CSS Classes (Proof of Concept)
\n\n\n\nCore Styles and Theme Customization: the next steps
\n\n\n\nExplore options to add back semantic classnames to block wrappers
\n\n\n\nAdd a Style Engine to manage rendering block styles
\n\n\n\nTranscript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox has a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, creating standards for WordPress’s CSS.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy and paste that URL into most podcast players.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast well, I’m very keen to hear from you, and hopefully get you all your idea featured on the show. Head over to WPTavern.com forward slash contact forward slash jukebox, and use the contact form there.
\n\n\n\nBefore we start, I thought that I’d let you know that there won’t be an episode of the podcast next week. This is because I’m hoping to be going to WordCamp Europe. I’ll be there with my microphone, recording episodes for the coming weeks. If you’re going to be there too, it would be lovely to meet up.
\n\n\n\nSo on the podcast today we have Mark Root-Wiley. Mark builds WordPress websites for nonprofits in Seattle, Washington with a focus on accessibility and usability. He’s a long time WordPress community member in Seattle and has previously helped organize WordPress Seattle meetups and WordCamp Seattle speakers.
\n\n\n\nHe maintains NonprofitWP. A free guide for people building WordPress websites for their nonprofits. And has a few free plugins available on wordpress.org.
\n\n\n\nHe’s on the podcast today to talk about why he thinks that it would be useful for WordPress to adopt some CSS standards. Over the years as WordPress’s evolved, the way that you implemented CSS was very much left to the individual user, themer or developer. You can do what you like, and that worked very well. After all, we all have preferred ways of doing things.
\n\n\n\nNow, however, the reach of WordPress has outgrown those early roots and some 40 plus percent of websites are using it. Projects that were built by one agency are often taken over by another. Users are often swapping themes to reflect their brand. Extra work is created for those inheriting sites. As they try to unpick the way that the CSS is built and implemented.
\n\n\n\nMark thinks that it’s time for WordPress to lay out some simple standards, which are easy to understand, and if they became universal would save us a lot of time and head scratching.
\n\n\n\nHe’s not proposing anything radical. Just some basic advice for the most commonly used CSS. And it’s quite a compelling idea, which would need a lot of community buy-in, and possibly some top-down approval if it were to move forwards. It’s very much the kernel of an idea at present, but thought provoking, nonetheless.
\n\n\n\nIf you’re interested in finding out more, you can find all the links in the show notes by heading over to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Mark Root-Wiley.
\n\n\n\nI am joined on the podcast today by Mark Root-Wiley. Hello Mark.
\n\n\n\n[00:04:02] Mark Root-Wiley: Hello. Thanks for having me.
\n\n\n\n[00:04:04] Nathan Wrigley: You are really, really welcome. I always like to begin the podcast with a bit of orientation. I think it’s very important that the audience gets to know a little bit about our guests. Who they are, what their journey with WordPress is and so on.
\n\n\n\nSo although the question is a little bit generic, I’m going to ask it anyway. Please, just give us a little bit of a history about yourself specifically in relation to your WordPress journey.
\n\n\n\n[00:04:28] Mark Root-Wiley: Awesome. Yes, let’s see. It’s been a pretty long one at this point. I am a child of the web almost. So, even back in the middle grades, I was learning to make websites. And so, it’s always been my hobby and my passion. And so when I, when I went off to college and got a degree in sociology, of course, that was much less employable than web work.
\n\n\n\nSo, I looked around at all the systems and I had some jobs and internships where I was working with Joomla and Drupal. And so of course I ended up landing on WordPress. So since 2010, I’ve been here in Seattle, Washington where I build WordPress websites specifically for nonprofits most of the time, and so, my journey has really been that about serving clients, building custom themes doing some custom plugin work, but really like, deep in the world of WordPress for well over a decade now. And, I got to say, I love it and I’m not considering going anywhere anytime soon.
\n\n\n\n[00:05:19] Nathan Wrigley: Oh, that’s excellent news. Now the topic under discussion today is going to be CSS and in particular, we’re going to reference right at the beginning, an article, which was published by Justin Tadlock on February 22nd on the WP Tavern website. And it was called the case for a shared CSS toolkit in WordPress.
\n\n\n\nAnd we’re going to get into the nuts and the bolts of that in a moment because Mark, I think it’s fair to say, would like to see some kind of overhaul in the way that WordPress handles CSS. And as I say, we’ll get into what that means in a moment. But Mark, I know that you may not be able to lay out the history of CSS in WordPress perfectly for us, but clearly you believe there’s a problem.
\n\n\n\nI’m just wondering if you could give us any insight that you’ve got into the way that the legacy of CSS in WordPress has meant that we’ve got a problem where we are right now. What has been going on and where are we at now?
\n\n\n\n[00:06:15] Mark Root-Wiley: It’s such an interesting question, and I think if I had to boil it down to just one sentence answer, you know, it’d probably be there used to not be very much CSS in WordPress and now there’s a whole lot more. To really expand upon that, I think what has happened is, you know, it used to be that WordPress really only had a little bit of front-end markup that it would put out. There were things, HTML for menus, HTML for the search form, HTML for widgets and themers just sort of applied their own CSS to that.
\n\n\n\nMaybe in some limited cases, WordPress had a little bit of CSS that they were adding to the front, but really very little. And with the block editor, we saw the project looking to really empower users to be able to control much more design of the sites they build, through the WordPress editor interface.
\n\n\n\nAnd if you want to give people more control over the design, you’re going to be, at the end of the day, you have to do that with CSS. CSS is the language we use to make design on the web. And so it has just become much, much more complicated. And I think all software, you know, to some extent, right, it’s always evolving, but I think in our world of open source, that development process can be much messier and much more organic. And I think that that can be a benefit sometimes. But I think that maybe this is one of those instances where, right now there’s a lot of different ways for accomplishing, you know, similar types of CSS on the front end. Certain blocks handle their CSS in different ways.
\n\n\n\nAnd I think we’re just seeing that, you know, it’s been what, three or four years now of the block editor and there still isn’t really a strong opinion of sort of, this is the way that the block editor handles CSS and that has made it really hard for, people in my chair. I’m trying to make themes that are going to work every time I hit the update button on WordPress.
\n\n\n\nThere’s just more complex CSS. There’s more of it. It’s done in varied ways. With more code comes more complexity and, it’s time to try to bring some order to that complexity.
\n\n\n\n[00:08:20] Nathan Wrigley: So it’s a case of the project being older than it was 15 years ago. There’s more that’s been added on top. It’s like a layer cake. We’ve had update after update, after update and things have been added in and fiddled with. We’ve had complete turnarounds in the way the interface has been put together and so on Gutenberg and all of those kinds of things.
\n\n\n\nAnd, essentially we’ve now got something which you, I think it’s fair to say, you would like to have a bit of a reset. You’d like us to rethink the way that the CSS is handled. And you’ve got some ideas around that.
\n\n\n\nCould you give me, before we get into the weeds of it, could you give me examples of pain points that you believe need solving? And you can be as specific as you like, you could describe a particular website that you built and a particular moment where you realized, ah, there’s things that I wish were different. So pain points that illustrate well what the problem is.
\n\n\n\n[00:09:12] Mark Root-Wiley: Yeah, that is such a, such a good question. I think that in some ways, the WordPress 5.9 release gave us a brief set of examples that I think made things hard for a lot of us themers. What probably looked like fairly small changes to for instance, the HTML and CSS of the cover block.
\n\n\n\nThere was I think one class that was removed from buttons that told you about the orientation of the buttons, how they were vertically aligned. But when that was removed, suddenly all these themes that had written CSS styles where they needed to know the alignment of buttons on their site, they just stopped working because that class had been removed.
\n\n\n\nSo rather than even really an overhaul, I think it’s a lot more about refining the practices and making a public commitment to, in the future, we are going to include classes in all of these circumstances, so that you can rely on them.
\n\n\n\nWe are going to output all of our CSS rules with a certain specificity. It’s time for the CSS to sort of be better, organized, more consistent, and just communicated better. Which is not really an issue of code, it’s more matter of having standards for the project. If anything that’s really what I am hoping to see.
\n\n\n\n[00:10:24] Nathan Wrigley: You’re not the first person to suggest that this would be a good idea. It feels in the article, at least anyway, you, you make the point that you are standing on the shoulders of giants, really. And do you just want to give a shout out to some of the people who in the past have elucidated what it is that you’re trying to do? There’s several of them, but I think it might be nice to give them some credit along the way.
\n\n\n\n[00:10:46] Mark Root-Wiley: Absolutely. Yes. I completely agree. I hoped that when I wrote my big blog post, this proposal that I know we’re going to talk about. What I see as one of the strengths is that there’s very little original thought in it. It’s really trying to bring together all these other great ideas from other people.
\n\n\n\nI think it goes back to, and I think you can still find it, the theme user experience standards, or TUX that came from Automattic’s theme team. And I think they have an example we should talk about in a little while. So, I owe a lot to them. Rich Tabor, I think about two years ago had some really awesome posts about what it would mean if we could standardize how we named font sizes, how we named colors and how we handle spacing and WordPress.
\n\n\n\nI think that’s a critical thing that we really do want to make happen. That’s something that I would love to see. And then, I think if you’re just tooling around on GitHub and following, you know, people who are filing issues and the Gutenberg repository, or writing about it. I certainly think Matias, one of the lead developers of the Gutenberg project has written really, really smart stuff about CSS.
\n\n\n\nAnd there were also I think, a couple of like small folks I want to give shout outs to. Louis herons on Github, talked about having a theme block contract. Things that themers can count on for blocks, making that contract. I love that phrase. I think that is super important. And I think also, uh, Andrew on ocean has written about needing different layers of CSS. And I really liked that idea too.
\n\n\n\n[00:12:11] Nathan Wrigley: Well, thank you. Hopefully, they’ll be listening in and they’ll acknowledge your acknowledgement, which is nice. So the idea really is you want there to be some sort of overarching structure. You want there to be some sort of consistency in the way that things are handled, and that WordPress Core would make moves towards that.
\n\n\n\nNow this is probably something that you’re going to have an opinion on, but there are out there already, all sorts of different ways of handling CSS. Frameworks, and what have you, you know. Just off the top of my head written a couple of down here, you know, you’ve got CSS Grid and Bootstrap and so on, but I’m pretty sure that that’s possibly not the approach you want us to go down. You don’t want to bolt those into WordPress Core?
\n\n\n\n[00:12:52] Mark Root-Wiley: Definitely not. Yeah. I think that WordPress has never taken a really strong position on like, this is how your theme code has to be written, and if you’re going to pull in an entire CSS framework like Bootstrap or Tailwind, that’s way more opinionated. That would be very limiting to anyone who didn’t want to do things that way.
\n\n\n\nSo, I think, when I sat down and really thought about like, what is it that I as a themer want. What it was is really baseline standardization more about just making sure that all block HTML and block CSS are done in a similar way. So that they’re, they’re sharing styles, they’re sharing CSS classes.
\n\n\n\nI think that there is also a ton of power if we can just standardize key styles that every site is going to need. So colors and font sizes. The amount of space between elements, things like that. But certainly not going as far as something like Bootstrap where there’s, gosh, sliders and drop down menus and modal dialogues and all those things.
\n\n\n\nIt’s not at all about that. It’s really, I think the word I really settled on is it’s, it’s a toolkit. It’s providing more tools that all theme developers, all plug in developers, we can all use and share, but we still get to choose how we use them and how much we use them. So that, if we want to play nicely together, you know, those tools are available, but we can still choose to do things in our own way where it makes sense.
\n\n\n\n[00:14:18] Nathan Wrigley: We mentioned at the start that there was a WP Tavern article, which in turn was written because of something that you wrote and I’m going to include everything that we talk about today as far as possible in the show notes. But if you wish to pause this podcast and go and read Mark’s piece, it’s called standardized design tokens and CSS for a consistent, customizable and interoperable WordPress future.
\n\n\n\nYou’re going to find that over at There’s no, no hyphens or anything like that. It’s just M R W web.com. That outlines everything that Mark is talking about. And so that really frames the conversation that we’re going to have from this moment on.
\n\n\n\nNow you mentioned that you wanted some sort of standardization. Presumably if that’s the case, you believe that the standardization at the moment is lacking. It’s messed up. It’s a muddle for people to create things. Everybody’s using their own different ways of doing things. Just kind of outline the specific problems about fragmentation versus standardization. What is it that you’re trying to overcome? What are the problems in Core that we’ve got at the moment? Things that need amending. Things that possibly need creating or uncreating?
\n\n\n\n[00:15:35] Mark Root-Wiley: Yeah. I’m going to answer your question and I think I want to like start us maybe five years in the future and then walk backwards to get there. in five years, I think we’re going to see a lot of sites that were built with the early years of the block editor.
\n\n\n\nLike now suddenly they’re needing to move to new themes. And so what does that look like? And, right now what we have are a lot of what I think of as kind of in the moment decisions that have been made. Both by the themer and the editor. Let’s take the theme or example first.
\n\n\n\nSo, the block editor from day one has always allowed themers to define named font sizes, right? So, they can call them whatever they want. A lot of themers have something like small, medium, large, extra large, I know. Justin Tadlock on the Tavern posted his extensively researched list of font size names that he likes. Definitely worth a read for anyone who hasn’t seen that.
\n\n\n\nBut I think the critical thing is that you can call them whatever you want. You can call them broccoli, apple, bicycle. You can call them seven forty, two ninety six, even if that has nothing to do with their sizes. And so what this means is that if we’re going to switch to a new theme in the future, if we switched to a theme that uses different names, all those font size settings that were set on the last version of the site are just gone. There is no bridge.
\n\n\n\nAnd so if we could agree to some like naming schemes, whether it is small through large, or even just 0 1, 2, 3, 4, 5, 6, 7. Now, when you move from one theme to another, you’re going to inherit, the choices that were made by the editors of the site, and be able to keep content as intact as possible. And right now I think the systems that the block editor is giving us are not really encouraging that consistency.
\n\n\n\nAnd it hasn’t really bitten us yet. The problems I think are coming. And so when I talk about portability of content. That’s what I’m talking about is how, what happens when we move from one theme to another. And I think that when you make that process smoother, it’s because you have good standards and that’s going to benefit everybody, working all the time.
\n\n\n\n[00:17:41] Nathan Wrigley: So the idea then is that things would become more standard and hopefully the community as a whole would adopt some standards.
\n\n\n\nNow, although we haven’t discussed this in our conversation prior to clicking record, I’m curious about your thoughts about this. Do you have any expectation that this would be something that would be, if you like, top down, in other words, would this be something which you would like to just be reflected in documentation?
\n\n\n\nAnd it’s a thing that you could use, or are you looking for a framework for CSS where really there are standards, which must be adhered to. In other words, you don’t really get to choose. If you want to be a WordPress theme in the repository, then you must do it in such and such a way. And over time, you mentioned five years in the future, we slowly encourage people to become the writers of CSS in that way.
\n\n\n\n[00:18:38] Mark Root-Wiley: That is such a tough question. I think that I guess I’ll say a few different things. I mean, I think that whenever possible, it’s better to use carrots than sticks. And I think that, right now in fact, I think the theme dot json standard is a great one where, if you’re building, what we’re now starting to think of is like classic themes.
\n\n\n\nLike you can use the theme dot json it’s on, it’s up to you and you also get like a ton of benefits by doing it. So I think that if we had standards like this, there would just be tremendous benefits to anyone who uses them, because themes would sort of work more similarly and even, there would be ways where plugins could suddenly sort of start referencing theme styles.
\n\n\n\nI would like to think that maybe this could bubble up, and be, you know, a community standard that people want to buy in, but aren’t forced to buy into. At the same time, I don’t know what it’s going to take to get this moving. Standardizing semantic names is something, we could talk about it forever.
\n\n\n\nAnd so I know that I personally, like I put out, in my blog post, a bunch of suggestions for the names. I thought really long and hard about them. I have my reasons. And honestly, like if someone said, nope, we’re going to use this really weird naming scheme that I don’t really care for anyway, I would use it in a heartbeat. I think having standards is more important than the specific names of them are. And so I do think that, there could be some room for some top-down decision-making here. As long as it’s a fairly simple thing, and we’re not going to punish people for not using it.
\n\n\n\nIn WordPress land, you know, maybe that means we’re going to maybe throw some errors on occasion if you’re not using, some warnings, excuse me, not errors warnings. But no errors, nothing’s going to actually quit working.
\n\n\n\n[00:20:21] Nathan Wrigley: You mentioned in the piece that there are some recent issues They were obviously some kind of catalysts for you, where you thought, okay, these kinds of things are happening and it makes it pretty obvious that we need to rethink this. I’m just going to read them out, and maybe this will give some context to somebody listening to this.
\n\n\n\nYou say to quote, recent issues make the need for a consistent, transparent approach, clear. Classes that were previously present and used by theme authors have been removed in favor of inline styles. Okay, we’ll get onto why that’s bad. Inline styles are redundant, hard to override and remove valuable selectors for theme authors. New instances of important, let’s just say that, CSS rules catch theme authors by surprise. Markup changes to Core blocks were only announced after the fact.
\n\n\n\nNow, I don’t know if you want to take all four of those or just riff on generally why you think these are the core things which need to be addressed, but yeah, there’s obviously something in there that sparked your interest and made you want to create this framework, if you like. Let’s just talk about that for a minute. Have you got something to say around that? What is it that you’ve found problematic?
\n\n\n\n[00:21:27] Mark Root-Wiley: I certainly have things to say. I suspect that honestly, maybe it was just random, how many, how many issues in 5.9 there were that sort of just got my goat as it were. I think that this is maybe one of the areas where there has already been a little bit of movement actually, which is wonderful. So yesterday, was this day when sort of all the dev notes for WordPress 6.0 showed up on the make.wordpress.org/core blog, and it included a lot of announcements about some changes to things, that are coming in WordPress 6.0. And I think that that advanced notice, already feels like, maybe some of what I’ve been saying has been heard and, and that, that is really great to see.
\n\n\n\nSo, you know, there’s going to be some changes to like how images get aligned, the quote blocks CSS, some changes around the group block in the block editor. And, I’m really happy to see that communication. So I do think that some of these smaller things were addressed, but I also think that the fact that some classes disappeared and some markup changed and nobody knew about it, and like important CSS got added. If you ever want to like really get a bunch of people worked up about CSS, just start talking about important.
\n\n\n\nI think the fact that those all happened at once, I think more than any one specific issue, it just felt like, okay, there’s a lot of people changing a lot of things all at the same time and there’s no cohesive vision for we’re trying to take CSS in WordPress.
\n\n\n\n[00:22:47] Nathan Wrigley: Yeah. So essentially you want there to be far less surprises in the way that things are released and also to have some cohesive framework that everybody can dip into and everybody understands because it’s been well-documented and everybody can buy into it. As you said, carrot, not stick, because it just makes sense.
\n\n\n\nThe article on the WP Tavern website had a very large amount of commentary on it. More so than anything I’ve seen in quite a while, to be honest, a lot of praise for the idea of what you’re doing. A lot of people saying, yes, we need this, we need this right now. And to develop it a little bit further, you are, you’re keen to get involved in a semantic approach.
\n\n\n\nNow that might not be obvious to everybody. So what does that mean? What is it you hope would come out of this? We may have a different vocabulary, in use in the end, but the idea is that we’re going to be substituting words or not as the case may be. So talk to us a little bit about that.
\n\n\n\n[00:23:43] Mark Root-Wiley: Yeah. I when I’m talking about semantics here, it’s really about can we establish shared meanings for some naming conventions within our CSS? So, back to the font size example earlier, if we can all agree that every time we name our font sizes, we’re going to call them small, medium, and large.
\n\n\n\nAnd every time we create our color palettes, we’re going to start with a primary color and a secondary color and maybe an accent color. Having that shared meaning, that’s what semantics are, is going to just provide so many benefits, and it’s also going to speed things up.
\n\n\n\nThere’s going to be less mental overhead, fewer decisions that themers have to make. There’s just tons of value there. Thinking back I had mentioned that the theme user experience standards were maybe the best spiritual forbearer to this kind of point of the proposal. One of the things they recommended is when you’re naming your menu positions to call them menu one, menu two, menu three, menu four. Maybe that’s not what I would have chosen, but I started doing it and I’ve done it ever since.
\n\n\n\nAnd what it means is that any time I switched one of my themes to another themes that uses that same menu naming convention, like, the same main menu just popped up in the header, right where I would want it to be without me having to update any settings at all, just because, our themes knew how to talk to each other.
\n\n\n\nSo it’s really about, can we make our themes and plugins talk to each other better and, ironically or, or appropriately, I think that just means we all need to do a bit more communication together in the project.
\n\n\n\n[00:25:10] Nathan Wrigley: Let’s get into weeds of the areas you think ought to be covered off, with some kind of framework. I keep using the word framework. I hope that’s okay. So for example, you mentioned fonts and you mentioned that the fonts might have things like small, medium, large, and that could probably extend up and down.
\n\n\n\nBut also there’s obviously other things in CSS that we would like to cover. So before we get into nomenclature of what those things might be, let’s just talk about the things that you want to cover aside from fonts. What other things do you think are so essential that we need to have a standard that everybody just understands?
\n\n\n\n[00:25:47] Mark Root-Wiley: Great question. So in terms of those kinds of like standard things that we should name, I think beyond font sizes, including font weights, because if you’ve ever used a font, you know, that some have nine or now in infinite number of weights. So we need a way to sort of have a standardized font scale. Colors and gradients I had mentioned.
\n\n\n\nAnd again, that’s something where WordPress already lets us name our colors and gradients. So let’s just agree to always call them the same things. I think font families. So what are you using for your copy versus what you’re using for your heading? And then I would love to also see maybe some border widths, and probably the biggest one that I am most excited about is let’s agree on one or a few named scales for spacing.
\n\n\n\nSo the space between blocks in a post, also the space between columns. The space between a gallery. If we can all agree on those names, then we can have a gallery with small space, a gallery with large space. And that’s just always going to look good from theme to theme, even though those values are going to be different and up to the themer.
\n\n\n\n[00:26:53] Nathan Wrigley: So aside from the fact that you would like to take into account things like font sizes and weights, colors, gradients, font, families, borders, spacing gaps, and so on columns and what have you. There would obviously need to be things that are associated with those, and you, you mentioned font sizes, small, medium, and large. Do you have some sort of insight into how far each of these go? Let’s for example take font sizes or weights? Well, let’s go for font sizes just for illustrative purposes.
\n\n\n\nHow far would you like to take that, and do you have a system for making it so that it can be extendable indefinitely? So an example might be, one dash large or something like that, or XL large or something like that. Just give us a flavor of how far that scale would go down as well as up.
\n\n\n\n[00:27:39] Mark Root-Wiley: Yeah, that’s a good question. So I think, if it were up to me, if I were making a top-down decision, I think I would just pick a scale of numbers. Either, you know, starting at zero or going up, or maybe even centered around zero with positive and negative numbers. I like the fact that you don’t need to know English to use a scale like that, and it is infinitely scalable.
\n\n\n\nI think the other scaling systems that a lot of people really like is what’s often called a t-shirt sizing. So instead of small, medium and large, we would just have S M and L. And the nice thing about that one is you can infinitely go in either direction.
\n\n\n\nSo XL, XXL, XXXL. It gets a little silly after a while, but you can do it. Some people like to say like three XL instead of XXXL. And you can do the same with XS, extra small. I will say that I think that when it comes to what WordPress should be standardizing, I don’t think it makes sense for us to say that every theme needs to have a 15 point scale for font sizes.
\n\n\n\nSome themes are gonna want three or five and that will be fine. I like to think of, of the 80 20 rule. 80% of needs out in the world can be satisfied by only 20% of the possible names in this case, that we could come up with.
\n\n\n\nSo I think that for something like font sizes, a seven point scale, maybe would probably meet everybody’s needs in terms of switching from site to site, and keeping things looking pretty good. Again, to go back to sort of like why I like to think of this as a tool kit. I wouldn’t want to ever say that themes can only have seven font sizes. Right. It would just be that if they want more than that, they’re on their own to go figure that out.
\n\n\n\nI will say that I did, I did a lot of thinking about this even after my blog post. And there’s, there’s a demo I put together that was showing how maybe we could even have a way of having really big scales that could kind of shift down to only a three point scale, or maybe you want to have a five point scale, but it skipped 0.4. I think there’s some clever things you can do with CSS custom properties that could allow that to happen. So you can find that demo in the blog blog post.
\n\n\n\n[00:29:38] Nathan Wrigley: Yeah. I ran that demo. That was really useful to look at that. But let’s move on to colors and much, much more constrained there. You just want a handful really unlike font sizes, which there’s definitely more scope with colors. You just want a few basic standards that will satisfy most websites I guess?
\n\n\n\n[00:29:56] Mark Root-Wiley: I think that’s right. And I think that the more colors that we defined, probably the more disagreement there would be. What purpose does the fifth most important color in your palette have versus what purpose does the primary or secondary colors have in your palette?
\n\n\n\nAnd so I think that, especially for colors, I think it’s the best example where if you had a bunch of standards, they probably wouldn’t actually be that useful. So let’s just, let’s keep it simple, right? Let’s not, over-complicate this. Let’s make as few things we all need to agree on as possible. So hopefully we can actually agree on them and move forward.
\n\n\n\n[00:30:28] Nathan Wrigley: The font weights and the font size is obviously really dramatically changed the way a website looks. And if you switch from theme to theme and those get messed up, it really can look remarkably different. And you mentioned spacing, so gaps and columns and padding and margin and all that.
\n\n\n\nAgain, it can really catastrophic effect things. What was a very small space can become a gigantic gulf, given a change in theme and so on, and so I was just wondered let’s ask the basic question again. What kind of constraints are you placing on that? How many different things do you think you need regarding spacing and gaps and all of that? Are we looking at dozens of different options or just three or four?
\n\n\n\n[00:31:06] Mark Root-Wiley: My first thought was, we probably only need maybe five, and I think that that probably would be about enough. If someone wants to do a few more than that, that would be fine. I think that spacing is maybe a really good example of the other key reason why I would love to see themes like shifting to these scales, because right now, for the most part, when an editor wants to change the spacing, of something in their posts, they can, you know, set a specific margin value or a specific padding value.
\n\n\n\nThey can say, I want the top margin of this image to be 24 pixels. And they’re making that decision based on how their content looks in that moment, on their screen with that specific theme. Let’s say design trends again in five years are like really into white space. Maybe that 24 pixels is going to look super tiny all of a sudden. So if we can allow editors instead of having to pick a number and on the next page, they forget that they entered 24. And so they entered 20. And like now there’s just chaotic numbers all over the place. If we just say like, well, at the top of this image, I want to have a large margin.
\n\n\n\nNow, when they move to their next theme, it’s going to be not 24 pixels, it’s going to be whatever that is in the next theme. It’s always going to look cohesive. And so I think it’s really important to point out that it’s not just about standardizing the scales for theme developers, but I think if we provide these scales as options for customizing post content, we’re going to see editors just having to like not think so specifically, and that’s actually going to enable them to be more consistent, both in the moment and in the future, when they need to sort of switch their design.
\n\n\n\n[00:32:43] Nathan Wrigley: In a sense, you’ve read my mind because my next question was really about that because obviously your doing this for a living, you can probably come up with some naming system, some framework that works for you, and just keep executing that over and over again. But, that’s not the world. We live in the world where you’ll probably take over a website in a few years’ time that somebody else built, and it will be littered with CSS classes and CSS styling, specific to that exact one little thing on that one page and how on earth did that happen?
\n\n\n\nBut it did. And so you need to go back and unpick all of the problems. So there’s that. The developers amongst us have probably figured out a system for themselves over the years, and they’ve got something which works. But when you swap a website, when you go and take on somebody else’s work, the fact that there’s consistency and stability in the naming of things would really help.
\n\n\n\nBut then you mentioned the bit, which I thought was really interesting, about the non-technical users and having things in easy to understand, non-technical language that somebody can just get a hold on and okay. All right. It would appear that that thing, okay, might not be the most obvious name in the world, but right, it does that. And it seems to do that consistently over the site. That just makes sense for end users.
\n\n\n\nYou described them as editors, but it could be anybody touching the website who has the capability to edit things. They, they really don’t want to get involved with CSS. In fact, that’s probably their worst nightmare that they need to think about CSS. They just want a handful of things, easy to understand. A minimal array of choices. The styling decisions were made months ago, and I’m just happy to stick with them.
\n\n\n\n[00:34:17] Mark Root-Wiley: You probably described that bit better I ever could. And, I think it really gets to this, there are lots of strong feelings about, is WordPress maybe becoming more like a site builder? Is it forgetting about being a content management system?
\n\n\n\nI truly believe that I think it can be both. And I also think that a lot of the work, especially around full site editing right now, like it has that more site builder mindset. And so I do think it’s important to remember that not every person with a WordPress site wants that super, super, super fine-grained control.
\n\n\n\nYou’re right. I work with folks that just, they are busy professionals in nonprofits in particular. A lot of the organizations I have, you know, whoever is updating the website that is a teeny tiny part of their job. It’s probably not even in their job description at all sometimes.
\n\n\n\nThey don’t want to be thinking about pixels or ems or if they don’t even know what MSR right. Can’t I just have some large space. That’s all I want, right. And so I think that not only are there these like huge technical advantages behind the scenes, but I really do want to just call out that I think this could actually like, just bring some simplicity to the editor and like help people make good decisions without constraining them.
\n\n\n\n[00:35:25] Nathan Wrigley: It also provides some kind of muscle memory options as well, in that if you have been working with a WordPress website, let’s say you’re working for company A over here, and you’ve been working with a WordPress website, and you go to interview for another job and they say, have you any experience with WordPress website?
\n\n\n\nYeah, that’s fine. I can do that. Then you don’t need to relearn it over on this site though. That thing does. Okay, that wasn’t quite expecting that. That’s a lot bigger than I thought. It makes the whole process of editors moving from one website to another easier as well. So it just seems like a bit of a win-win.
\n\n\n\nNow having said all of that, we’re 15 years plus into the project. Everybody in the comments on the Tavern article seemed to think this was a cracking idea. You seem to think it’s a cracking idea, the likes of Rich Tabor, they think it’s a cracking idea. And yet here we are talking about it as an idea.
\n\n\n\nWhat’s holding us back? What is stopping this gaining momentum if it’s such a sensible idea? Are we, is the project too limited in time? Are we concentrating on other things? You may not have the answers, but you may have some intuitions.
\n\n\n\n[00:36:33] Mark Root-Wiley: I guess I would start with, this is, you know, a little off the cuff, just a theory, but I do think that the block editor is written in JavaScript. And so the amount of JavaScript in the WordPress project in the last few years has just exploded.
\n\n\n\nTo be really clear, that’s fine. You couldn’t build the block editor without that level of JavaScript. But I do think it means that a ton of the development is done. When people are thinking in terms of JavaScript, and I will say that, one thing that I’ve looked for and I don’t really feel like I’ve seen a lot of, is people sort of starting with, like, what do we want the output to look like? What is the ideal HTML and CSS to allow a user to select the margins of their images, you know, how do we want to handle that? And then build the interface that’s going to enable that.
\n\n\n\nIt feels like it’s sort of working the opposite way. If we’re worried about what is the settings interface going to look like? And then like, we’ll figure out what the code, to make it actually work on the front end is going to be last. I do think that maybe working backwards a little bit more frequent. What CSS do we want, and now how are we going to make sure that it can be created in a sensible way? I wonder if that would help, because at least to me looking, somewhat from the outside, it doesn’t seem like folks are working that way.
\n\n\n\nAnd now having said all of that, I think it’s mostly a people and a communication problem. And I think that’s just harder than tech problems, right? Give someone an infinite amount of time and by themselves they could build the block editor on their own, but they certainly could not organize an entire community to agree on what to call font sizes.
\n\n\n\nThat just requires folks coming together. And honestly like making compromises and, and trying to think about what’s best for the community and not just best for themselves. I think that’s really hard. I think we can do it. I think things like that have happened in the past. I do think that’s the fundamental issue and so I don’t, I don’t know exactly what’s needed though.
\n\n\n\nAgain, that’s why I do wonder, could someone maybe make a, a bit of an executive decision on this one and, and just try to say this is happening and we’re going to be taking comments for this long, and then we’re going to make a decision and roll with it because we think the advantages to having a system are bigger than the disadvantages to any sort of, in the weeds decision that might make it through.
\n\n\n\n[00:38:47] Nathan Wrigley: I wonder if it’s because CSS, of all of the different parts of WordPress. The HTML and the CSS bits, they’re the easy building blocks, aren’t they? They’re the bits that a lot of people can get hold of really quickly. And with a quick flick through some kind of 1 0 1 tutorial, you can get yourself up and running with the basics of font sizing and padding and margins and, and quickly gain an understanding of it.
\n\n\n\nAnd so everybody’s been left to their own devices on that. The theme may very well take care of all of that, of all of that for you. And you may need to adjust absolutely nothing. You’re entirely happy with the theme and you don’t dabble. But if on that one particular occasion, you just wished to change that one particular thing you want the, I, don’t know, the, the heading to be slightly bigger, you just fiddle about and locate the CSS for that and modify it, add something to a style sheet, so on. And it’s fairly straightforward and it can be done by more or less anybody on their own, but it doesn’t require any consistency. Naming what you like so long as it works.
\n\n\n\nBut your approach is, is slightly different. And yeah, it feels as if maybe it’s not got the momentum at the moment, but it feels like, you know, maybe with things like this happening, your initiative happening, people talking about it more, maybe somebody could take this on. And as you say, maybe at some point it does need somebody on high to make a decision executively and say, okay, we’re going to concentrate on this and it’s going to become important. But I don’t know that any of that is in the roadmap right now. So you may need to keep banging the gong for a little bit longer I think.
\n\n\n\n[00:40:23] Mark Root-Wiley: I actually, you know, I, I played a lot of percussion growing up, so I love banging a good gong. One thing I noticed is, you mentioned the number of comments on the Tavern post, I certainly got a few comments on my blog post and I published a, sort of a Github issue that the sister of the blog post and it got a lot of comments and, and I do think people are listening.
\n\n\n\nI’m not sure what’s required to sort of get some action steps. But, I will say that, what really made me think that, yes, I, I do think people are listening at this moment is there was a blog post, at this point, I think about a month ago, on the make wordpress.org/core blog called core styles and theme customization, the next steps.
\n\n\n\nThe gist of that post is basically like here’s a bunch of links to get hub issues, please go read them and leave your feedback. The speed of change in an open source project is never going to be what we want it to be. And I really do try to always remember that when I’m feeling impatient, which is certainly why I wrote this whole thing.
\n\n\n\nBut I do think that, it is important for folks to always be paying attention, always be sharing their mind, because I do think, at some point, especially if a lot of us keep talking about this, like some decisions will get made. And so, you know, make sure if you’re interested in this, make sure to go leave some comments on, on these issues and keep bumping them up so people can see that they are high priority for a lot of us in the community. I know it’s not just me.
\n\n\n\n[00:41:42] Nathan Wrigley: Yeah, it was quite interesting. The article that you mentioned, the core styles and theme customization, the next steps I was highlighting the bits that were basic replications of everything that you were saying. And quite a lot of the article got highlighted. Let’s put it that way. So it would seem that, on some level, there is movement here and people are definitely in agreement with you.
\n\n\n\nDo you have any insight into how this might get revved up and get more interest attached to it? In other words, are you willing to put your best foot forward and become somebody in the vanguard? Like I said, banging the gong. Or do you find that there’s probably a better way of, have you got any insights into where people could go if they agree with you and want to get involved to make this happen?
\n\n\n\n[00:42:25] Mark Root-Wiley: Gosh, it takes everyone in the community weighing in, I think that. One thing I’ll say is that, you know, I tried to get a lot of people to review my blog post and, even gives me advice on like, how should I publish it and who should I let know about this?
\n\n\n\nCause I think that if it’s just me it’s ineffective. It does need to be a community. And so, you know, I would say I would love to see other people sharing their own proposals even. I don’t know. I don’t even know if you want to include this part, I don’t think it can just be me.
\n\n\n\nI it’s pretty silly actually. I published this blog post and then 24 hours later, we had a new baby. I definitely had to fall off the face of the earth and disappear for a while, but I was so thrilled to see other people, saying like, yeah, this is awesome. And here’s the couple of things I have to add.
\n\n\n\n[00:43:08] Nathan Wrigley: There’s a whole lot towards the end of the article where you outline the different problems that your solution may solve. I won’t list them all now, but all of it kind of makes common sense to me. One can only hope that the ideas that you’ve suggested go forwards and that people, as a community, can coalesce and come up with an idea.
\n\n\n\nAnd as you said, you’re not bound to any one particular way of doing it. It’s just the mere idea of standardizing things, whether it be named this or that is not important, it would just be nice to have some standard documented that everybody can adhere to and therefore make it a lot easier for all of us to make websites, whether we’re building them for clients or we’re just editing and tweaking them ourselves.
\n\n\n\nOne of the concerns that we may have is the stability of WordPress CSS in the future. And I know that you have possible concerns that in the future, for example, Gutenberg blocks, there’s no requirement for the CSS, the classes, and so on to be the same today as it will be tomorrow or indeed yesterday.
\n\n\n\nSo in other words, is that a problem, do you think? Is there any problem of consistency where let’s say that you build something and you ship It, and it goes out to your client. It’s using blocks, but suddenly unbeknownst to you, the blocks CSS classes all get modified, perhaps ever so slightly, but enough to break things. Is that a concern that you have?
\n\n\n\n[00:44:36] Mark Root-Wiley: It really is. And I think that this is one of the biggest things I sort of learned from this intense period of engagement I’ve been having with the project is that, in discussing this with other people and really closely going through, uh, lots and lots of issues and the Gutenberg Github repository. I found some core development team members really saying that they viewed the HTML markup and the classes and how the CSS has written as essentially like non-public, which is to say you can’t count on this stuff not changing in the future.
\n\n\n\nThat was really shocking to me. And I think for a couple of reasons, I mean, th the first is that, you know, that’s never how it’s been in WordPress in the past. The HTML for the comment forum, the HTML for the search forum, like those weren’t always seen as, you can count on this, there are ways to change it if you need to, but if we’re going to change this stuff, it’s going to be a huge deal and you’ll hear about it in advance, and we’re really gonna try to avoid that.
\n\n\n\nAnd so it felt like, uh, that was a departure from how things had previously been. And also as I’m someone who I think follows the project, like more closely than average, even though I, you know, I’m certainly not like a day-to-day contributor, or anything, but this was huge news to me as someone who’s been working with the block editor for years now.
\n\n\n\nAt least to me, I don’t even really know that it’s reasonable to just say that like, well, here’s a bunch of HTML and CSS. Themers I know you have like your job to do and you need to make changes to this, but like, you can’t count on it. That doesn’t really seem fair.
\n\n\n\nAnd I certainly don’t think people are really aware of that. They’re not going to go in and one day, you know, completely change the image block or the block quote block drastically. I don’t really think they mean we’re going to just completely change everything. But I do think it just highlights the need again, to really spend some time focusing on what is the HTML that can serve as best going forward. So we don’t need to change it.
\n\n\n\nWhat are the CSS classes and the ways of handling CSS styles that we want to commit to now so that we can all just know what’s coming in the future. And so that when there are changes made, they are a big deal, and people are given lots of advance warning and they can, they can react.
\n\n\n\nAnd so I think I’m seeing more advanced warning in WordPress 6.0, which is awesome. It’s time to have that conversation about how can we just reduce the number of times we need to make big changes like that. Cause people are going to style HTML, no matter what.
\n\n\n\n[00:46:58] Nathan Wrigley: Yeah. I wonder if it’s a product of the fact that the block editor is now basically a conduit to put in lots and lots of little components. So you might have a paragraph block and you might have a, an image block or a cover block or whatever it might be. You’ve got all of these different blocks and the functionality of that is not yet a hundred percent certain. In other words, aspects of it could change. And so I wonder if them communicating CSS will change is a product of that. They’re just not sure exactly what those blocks will look like in a few years time. And if they become radically different, maybe the functionality changes. Let’s hope it doesn’t. I’m sure it won’t, but if it did, some of the CSS may need to change. I don’t know.
\n\n\n\n[00:47:42] Mark Root-Wiley: I think you’re right on the money there. I mean, the block editor is so much more powerful and I want to be really clear that like, that’s awesome. Like the folks I work with generally, like love that they can do more complex things like columns, or like finally putting text on top of an image for the cover block.
\n\n\n\nThose are good things. And we had to have a more complex system to make that possible. So I’m not against the complexity, but I just think it’s really important that the folks who are building the product, don’t forget about those of us in the real world who, you know, have to make things work every day. And we have, we have new sites we’re constantly working on, the impact of even what can seem like a really tiny change can be really big.
\n\n\n\nTo bring it all back around, I really do think that if we can have just a few more standards and right, if we can have that kind of contract between themes and blocks, I think we can reduce the amount of times that those kinds of changes happen.
\n\n\n\nI totally acknowledge that they’re going to have to happen every once in a while. If we want to have this like big, nice thing, we’re going to have to put up with probably more changes. Cause there’s more things that can change, but, let’s really, let’s take a minute and figure out how we can make that as infrequent unpainful as possible.
\n\n\n\n[00:48:51] Nathan Wrigley: Yeah. It’s interesting your language there. You described it as a big, nice thing. And in a sense it’s a big, nice thing made up of lots of smaller little nice things. Each of those little nice things is completely independent. And you may not use those on your website, but you may.
\n\n\n\nAnd if there’s modifications made to the CSS classes and what have you, the downstream effect could be pretty catastrophic. You know, if you’ve just built 50 websites and they’re all using the exact same block and some tiny little change affects you 50 times, that’s suddenly created a lot of work for you that potentially was not even thought about elsewhere.
\n\n\n\n[00:49:27] Mark Root-Wiley: It has. In some extreme cases, this is maybe the reason why some people are often building custom blocks that really they could just be using the core block, but I’ve, I’ve at least anecdotally heard that folks do that sometimes because they know that their block isn’t going to change, even if they don’t want to have to take the time to build it.
\n\n\n\n[00:49:44] Nathan Wrigley: If people Mark wants to find you. They want to actually reach out to you. You may wish to share a Twitter handle or a website or an email address. Totally up to you. Yeah, any place that you could be found if people are inspired to join you?
\n\n\n\n[00:49:58] Mark Root-Wiley: Yes. I am M R W web pretty much everywhere. So that’s, uh, MRW web with two W’s, uh, I’m MRW web.com. I’m M R W web on GitHub and Twitter and in the WordPress Slack and Post Status Slack. All these other places. I have a highly Googleable namee. If you want to come find me, I would love to hear from you I’m. I am not that hard to find.
\n\n\n\n[00:50:23] Nathan Wrigley: Well, Mark, thank you very much for being on the podcast today. I really appreciate.
\n\n\n\n[00:50:28] Mark Root-Wiley: Thanks so much for having me. This was a blast Nathan. Great, great questions. I got to say.
\nAlthough as a WooCommerce builder, you likely don’t sell fish, but here is a story to get you thinking creatively about follow-up emails.
\n>> The post dev_life snippet: Timing the Perfect Follow-up Customer Email appeared first on Do the Woo - a WooCommerce Builder Community .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 25 May 2022 02:00:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"WPTavern: WordPress 6.0 “Arturo” Adds More Templates and Patterns, Style Switching, and Block Locking UI\";s:7:\"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=134698\";s:7:\"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:111:\"https://wptavern.com/wordpress-6-0-arturo-adds-more-templates-and-patterns-style-switching-and-block-locking-ui\";s: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:6321:\"WordPress 6.0 “Arturo” was released today, named for Latin jazz musician and director Arturo O’Farrill, who has 15 albums to his credit.
\n\n\n\nCheck out the official release video for a quick overview of some of the most important changes.
\n\n\n\n\n\n\n\nThis release introduces sweeping improvements to the block editor and its utilities and design tools. Most notably, users can now select text across multiple blocks, manipulating the highlighted portion as a group while keeping the rest of the content blocks in tact.
\n\n\n\nThe List View has been updated to offer a more intuitive display that helps with navigating blocks on a page. Select multiple blocks using keyboard shortcuts, make changes, and drag-and-drop inside the list. List View is closed by default but will expand to the current selection when a block is selected.
\n\n\n\nWordPress 6.0 also introduces a new interface for locking blocks, which allows useres to prevent blocks from being moved or removed. It is useful for preventing accidental edits but also for theme developers who want to prevent users from removing blocks inside templates, preserving more complex layouts.
\n\n\n\nOther block editor improvements include the following:
\n\n\n\n- New Blocks: Avatar, Post Author Biography, Read More, Comments Query Loop, and Stack block
- Type two open brackets
[[to quickly access the link menu - Improved support for preserving unrecognized content in the editor
- Preserve existing styles transforming blocks from one kind to another—from a Paragraph block to a Code block, for instance
- New block style transformation options: Tag Cloud > Categories, Calendar > Archives, Paragraph > Code, and Group > Row
- Create customized buttons and any new buttons will retain the style customizations automatically
- New drop-down based color picker UI
- Make tag clouds and social icons more appealing with updated settings and controls, and a new outline style for the tag cloud
- Instant block style previews
- Featured images now available in Cover block
- New border controls for more precise control when setting borders
- Transparency levels for colors offers more creative control
WordPress 6.0 also introduces a gaggle of new layout controls for page building. Users can now control gaps, margins, typography, and more on multiple blocks inside a Group block. Creating layouts is easier with the ability to position groups of blocks by quickly switching between stack, row, and group variations. The Gallery block is now more flexible with gap support for custom spacing.
\n\n\n\n\n\n\n\nFull-Site Editing Updates: More Templates, More Patterns, and Style Switching
\n\n\n\nPatterns are now available in more places and better integrated with the Site Editor. Gutenberg 12.7 brought major improvements to the patterns experience by making them easier to discover. The block inserter has been updated to display patterns, as opposed to blocks, when users are editing a template in the post or site editor. It also favors showing patterns when the inserter is at the root level or the content being inserted is between other blocks. WordPress will now show existing template parts, as well as block patterns in the template creation process.
\n\n\n\nTheme authors can now register patterns from the official Pattern Directory using theme.json, so that users have quick access to patterns the author has highlighted.
\n\n\n\nWordPress 6.0 introduces five new template options for full-site editing: author, date, categories, tag, and taxonomy.
\n\n\n\nOne of the most anticipated features of this release is the Style Switcher. It allows userse to apply quick style changes within the same theme, and includes the ability to further edit the font weight, style options, and color palette.
\n\n\n\nTheme authors can create multiple different theme.json style variations and place them into their themes’ /styles folder. Users will then see the styles under the Styles menu in the top toolbar of the site editor.
WordPress 6.0 is the product of collaboration from more than 500 contributors in 58+ countries. It introduces more than 1,000 updates and bug fixes, including many that make the platform more performant and accessible.
\n\n\n\nCheck out the 6.0 Field Guide and the release notes for a more detailed look at all the changes in the 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 24 May 2022 20:29:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:46:\"WordPress.org blog: WordPress 6.0 “Arturo”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12879\";s:7:\"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/2022/05/arturo/\";s: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:52729:\"\n\n\n\nWelcome to “Arturo”
\n\n\n\nSay hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, Arturo O’Farrill. Known for his influence on contemporary Latin jazz, Arturo has pressed more than 15 albums spanning a body of work across five decades.
\n\n\n\nTake some time to explore WordPress 6.0, built to help you unlock your creative aspirations and make your site-building experience more intuitive. And check out some of Arturo’s inspirational sounds that span Afro Cuban jazz, contemporary Latin jazz, and so much more.
\n\n\n\nWith nearly 1,000 enhancements and bug fixes, the second major release of 2022 is here. Download it now! As of today, WordPress powers more than 42% of websites worldwide.1
\n\n\n\nSite owners and administrators should upgrade to take full advantage of the many stability, performance, and usability enhancements today. WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.
\n\n\n\n\n\n\n\nExpanding Gutenberg into a full site editing experience in WordPress means that all of the problems the community had to address were complex and far-reaching. WordPress 6.0 is an example of the community’s commitment to tackling these tough challenges together. With thoughtful updates to the writing experience, building better block functionality, and adding a new intuitive style switcher, I’m really proud of the work that’s been done in this release to make a great site editing experience.
Josepha Haden Chomphosy, Executive Director
What’s Inside
\n\n\n\n\n\n\n\nEnhanced Writing Experience
\n\n\n\nWriting improvements abound, whether you’re writing a brand new post or adding elements to an existing page. Explore more ways to streamline your content creation process, including:
\n\n\n\n- Select text across multiple blocks for easier copying and pasting.
- Type two open brackets `
[[` to quickly access a list of recent posts and pages. - Keep existing styles when you transform some blocks from one kind to another—from a Paragraph block to a Code block, for instance.
- Create customized buttons and any new buttons you make will retain the style customizations automatically.
- Make tag clouds and social icons even more appealing with updated settings and controls, and a new outline style for the tag cloud.
\n\n\n\nStyle Switching
\n\n\n\nBlock themes now include the option to contain multiple style variations. This expands the new Style system even further and enables shortcuts to switch the look and feel of your site all within a single theme. In block themes that support this feature, you can change both the available settings, like the font-weight, and the style options, like the default color palette. Change the look and feel of your site with just a few clicks.
\n\n\n\n\n\n\n\nMore Template Choices
\n\n\n\nWordPress 6.0 includes five new template options for block themes: author, date, categories, tag, and taxonomy. These additional templates provide greater flexibility for content creators. Tailor each with the tools you already know or with the following new options in this release:
\n\n\n\n- Featured images can be used in the cover block.
- New featured image sizing controls make it easier to get the results you want.
- While editing a template, at the root, or between blocks, the quick inserter shows you patterns and template parts to help you work faster and discover new layout options.
- The query block supports filtering on multiple authors, support for custom taxonomies, and support for customizing what is shown when there are no results.
\n\n\n\nIntegrated Patterns
\n\n\n\nPatterns will now appear when you need them in even more places, like in the quick inserter or when creating a new header or footer. If you’re a block theme author, you can even register patterns from the Pattern Directory using `theme.json`, enabling you to prioritize specific patterns that are most helpful to your theme’s users.
Additional Design Tools
\n\n\n\nDesign tools grow more powerful and intuitive with each release. Some highlights for 6.0 include:
\n\n\n\n- A new color panel design saves space, but still shows your options at a glance.
- New border controls offer a simpler way to set your border exactly as you like it.
- Transparency levels for your colors allow for even more creative color options.
- Control gaps, margins, typography, and more on a collection of blocks, all at once, in the Group block.
- Switch between stack, row, and group variations to position groups of blocks with more layout flexibility.
- Use the gap support functionality in the Gallery block to create different looks – from adding spacing between all images, to removing spacing altogether.
\n\n\n\nBetter List View
\n\n\n\nNew keyboard shortcuts enable you to select multiple blocks from the list view, modify them in bulk, and drag and drop them within the list. List View can be opened and closed easily; it comes collapsed by default and it automatically expands to the current selection whenever you select a block.
\n\n\n\n\n\n\n\nBlock Locking Controls
\n\n\n\nNow you can lock your blocks. Choose to disable the option to move a block, remove a block, or both. This simplifies project handover, allowing your clients to unleash their creativity without worrying about accidentally breaking their site in the process.
\n\n\n\nImproved Performance in WordPress 6.0
\n\n\n\nThis release includes several updates focused on improving the performance of WordPress. These enhancements cover a range of performance areas including improving the page and post-load speed, reducing the execution time of various query types, caching, navigation menus, and much more. The performance team working group is an important focus area of the core development team. For more information on this group’s work, please follow their work on Making WordPress with the #performance hashtag.
\n\n\n\nEnhancing WordPress 6.0 Accessibility
\n\n\n\nAccessibility is an integral part of the WordPress mission of fostering an inclusive community and supporting users of all types around the world. With this in mind, WordPress 6.0 includes more than 50 updates specifically focused on enhancing the accessibility of the platform. You can read about these updates and learn more about the accessibility initiatives that are ongoing.
\n\n\n\nLearn More About WordPress 6.0
\n\n\n\nSee WordPress 6.0 in action! Watch a brief overview video highlighting some of the major features debuting in WordPress 6.0.
\n\n\n\n\n\n\n\nExplore learn.wordpress.org for quick how-to videos and lots more on new features in WordPress. Or join a live interactive online learning session on a specific WordPress topic.
\n\n\n\nDevelopers can explore the WordPress 6.0 Field Guide. It is overflowing with detailed developer notes to help you build with and extend WordPress.
\n\n\n\nRead the WordPress 6.0 Release Notes for more information on the included enhancements and issues fixed, installation information, developer notes and resources, release contributors, and the list of file changes in this release.
\n\n\n\nThe WordPress 6.0 Release Squad
\n\n\n\nThe group listed below tirelessly supported the release, from conception to ship date, and beyond:
\n\n\n\n- Release Lead: Matt Mullenweg
- Release Coordinators: Héctor Prieto and Anne McCarthy
- Core Tech Lead: Peter Wilson
- Editor Tech Leads: Adam Zieliński and Greg Ziółkowski
- Core Triage Leads: Ahmed Chaion and Colin Stewart
- Editor Triage Lead: Nick Diego
- Documentation Leads: Birgit Pauli-Haack, Milana Cap, and Abha Thakor
- Marketing & Communications Lead: Dan Soschin
- Test Leads: Piotrek Boniu and Brian Alexander
- Design Lead: Channing Ritter
Thank you to 500+ Contributors
\n\n\n\nWordPress 6.0 would not have been possible without the contributions of more than 500 people in at least 58 countries. Their asynchronous coordination to deliver hundreds of enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\nAaron Jorbin · Aaron Robertshaw · Abdullah Ramzan · Abha Thakor · Adam Silverstein · Adam Zielinski · adi64bit · Adil Ali · agepcom · Ahmed Chaion · Aki Hamano · Akira Tachibana · Alain Schlesser · Alan Jacob Mathew · alansyue · Albert Juhé Lluveras · albertomake · Alefe Souza · Aleksandar Kostov · Alex Concha · Alex Lende · Alex Mills · Alex Stine · aliakseyenkaihar · Alkesh Miyani · Alok Shrestha · Amanda Giles · Andrea Fercia · Andrei Draganescu · Andrei Surdu · Andrew Dixon · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrey \"Rarst\" Savchenko · André · Andy Fragen · Angelika Reisiger · Anh Tran · Ankit K Gupta · Anne McCarthy · Anoop Ranawat · Anthony Burchell · Anthony Ledesma · Anton Vlasenko · antonrinas · Antony Booker · arcangelini · Ari Stathopoulos · Arne · Arpit G Shah · artdecotech · ArteMa · Arthur Chu · Asaquzzaman mishu · atomicjack · Aurélien Joahny · Aurooba Ahmed · Barry · Barry Ceelen · Bartosz Gadomski · Beda · Ben Dwyer · Benachi · Bernhard Reiter · BettyJJ · Bhrugesh Bavishi · binarymoon · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Blair Williams · BlogAid · Boone Gorges · Brandon DuRette · Brandon Kraft · Brian Alexander · bronsonquick · Brooke Kaminski · Brooke. · Bruno Ribaric · caraya · Carlos Bravo · Carlos Garcia · Carolina Nymark · cbigler · Chad Chadbourne · Channing Ritter · charleyparkerdesign · charlyox · Chintan hingrajiya · Chloe Bringmann · Chouby · Chris Lubkert · Chris Van Patten · chriscct7 · clonemykey · Colin Stewart · conner_bw · Cory Hughart · Courtney Robertson · Crisoforo Gaspar · Dan Soschin · Daniel Bachhuber · Daniel Richards · danieldudzic · darerodz · Dat Hoang · Dave Smith · David Baumwald · David Biňovec · David Calhoun · David Gwyer · David Herrera · David Shanske · Deb Nath Utpol · Delowar Hossain · denishua · Dennis Claassen · Dennis Snell · Dhanendran · Dharmesh Patel · dhusakovic · Dilip Bheda · Dion Hulse · Dominik Schilling · donmhico · drago239 · Drew Jaynes · dromero20 · Eddy · ehtis · Eliezer Peña · Ella van Durpe · Emmanuel Hesry · Enrico Battocchi · eric3d · Erik Betshammar · espiat · Estela Rueda · etaproducto · EverPress · Fabian Kägy · Fabio Blanco · Faison · Felipe Elia · Felix Arntz · Femy Praseeth · Florian Brinkmann · Florian TIAR · FolioVision · Francesca Marano · Francisco Vera · frankei · furi3r · gadhiyaravi · Garrett Hyder · Garth Mortensen · Gary Jones · Gary Pendergast · genosseeinhorn · George Hotelling · George Mamadashvili · George Stephanis · Gerardo Pacheco · Glen Davies · Grégory Viguier · Grant M. Kinney · Greg Ziółkowski · gregoiresailland · Guido Scialfa · gumacahin · gvgvgvijayan · Hareesh · Hasanuzzaman · Hasnain Ashfaq · Hauwa Abashiya · Haz · Helen Hou-Sandi · HelgaTheViking · Henry Wright · Hilay Trivedi · Hitendra Chopda · HristoK · Hugh Lashbrooke · Héctor Prieto · Ian Belanger · Ian Dunn · ianatkins · ianmjones · ImanGM · imokol · Isabel Brison · ishitaka · itsamoreh · Iulia Cazan · Ivan Lutrov · jadpm · Jake Spurlock · jakeparis · James Koster · Jamie VanRaalte · Jan Weiss · janh2 · Jarret · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Arce · Javier Prieto · Jay Trees · jazbek · Jean-Baptiste Audras · Jeff Bowen · Jeff Matson · Jeff Ong · Jeff Paul · Jenny Dupuy · Jenny Wong · Jeremy Felt · Jeremy Herve · Jeremy Yip · Jez Emery · jhned · jhnstn · jigar bhanushali · jiteshdhamaniya · Joe Dolson · Joe McGill · Joen Asmussen · Johannes Kinast · John Blackbourn · John James Jacoby · John Regan · John Watkins · Jon Brown · Jonathan Champ · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Jorge · Jorge Costa · José Arcos · Josepha · Josepha Dambul · Joshua Fredrickson · Joy · jrivett · jsnajdr · juanlopez4691 · JuanMa Garrido · Juliette Reinders Folmer · Junaid Ahmed · Justin Ahinon · Justin Busa · Justin Tucker · KafleG · Kai Hao · Kajal Gohel · kapacity · Kapil Paul · karolinakulinska · Kaspars · kbatdorf · Kelly Choyce-Dwan · Kemory Grubb · Kerry Liu · Kev Provance · Kharis Sulistiyono · Kirtan Gajjar · Kjell Reigstad · KMix · Knut Sparhell · Konrad.K · Konstantin Obenland · kpegoraro · kubiq · Kukhyeon Heo · Lauren · Lena Morita · lenasterg · leskam · Lew Ayotte · linux4me2 · Lisa Schuyler · lkraav · Louis · Lovekesh Kumar · Lucas Karpiuk · Luis Felipe Zaguini · luisherranz · Luke Cavanagh · Lukman Nakib · M. van Dam · macbookandrew · Maciej · Maggie Cabrera · maguijo · Mahbub Hasan Imon · malthert · manfcarlo · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marin Atanasov · Marius L. J. · Mark Jaquith · Markus Kosmal · marv2 · Mary Baum · Mat Lipe · Mathieu · Matias Ventura · matiasbenedetto · Matt Chowning · Matt Martz · Matt Mullenweg · Matt Royal · Matt Stoney · Matt Wiebe · maur · Mauriac AZOUA · Max Kellermann · Mehedi Foysal · Meher Bala · mgol · Michael Burridge · Michal Czaplinski · Miguel Fonseca · Mike Auteri · Mike Schroder · miken32 · Milan Dinić · Milana Cap · Minal Diwan · Mirco Babini · MMDeveloper · Mohadese Ghasemi · Mohammad Ahsan Habib · Mohammad Rockeybul Alam · MohammadJafar Khajeh · Morten Rand-Hendriksen · moushik · mqudsi · Muhammad Faizan Haidar · Mukesh Panchal · Mustaque Ahmed · Nabil · Nagesh Pai - a11n · Nalini Thakor · Nathan · Nayana Maradia · Nicholas Garofalo · Nick Ciske · Nick Diego · Nicolas Juen · nidhidhandhukiya · Nik Tsekouras · Nil · nmschaller · Noah Allen · oakesjosh · oguzkocer · Oliver Campion · Omar Alshaker · opr18 · Otshelnik-Fm · overclokk · ovidiul · Paal Joachim Romdahl · Pablo Honey · Paolo L. Scala · Paragon Initiative Enterprises · Pascal Birchler · Paul Bearne · Paul Biron · Paul Ryan · Paul Von Schrottky · paulkevan · Pavan Patil · Pavlo · pbking · Pedro Mendonça · Petar Ratković · Peter Smits · Peter Westwood · Peter Wilson · petrosparaskevopoulos · Petter Walbø Johnsgård · pgpagely · Phil Johnston · Pieterjan Deneys · pikamander2 · Piotrek Boniu · Pooja Derashri · Pooja N Muchandikar · Pravin Parmar · Presskopp · presstoke · Priyank · pypwalters · r-a-y · Rachel Baker · Rafi Ahmed · Ramanan · Ramon Ahnert · Ramon James · Ramona · Ravi Vaghela · ravipatel · Razvan Onofrei · Rehan Ali · Remy Perona · Riad Benguella · Rian Rietveld · Rich Tabor · Richard B. Kreckel · ricomoorman · Rob Scott · Robert Anderson · Rolf Allard van Hagen · Rolf Siebers · Rostislav Wolný · Rufus87 · Ryan Boren · Ryan Fredlund · Ryan McCue · Ryan Welcher · Sébastien SERRE · Sören Wrede · Sabbir Ahmed · Sabbir Hasan · Sami Falah · Sanjeev Aryal · santosguillamot · Sarah Norris · Sarah Snow · sarayourfriend · Sathiyamoorthy V · Sayedul Sayem · sbossarte · sclayf1 · Scott Buscemi · Scott Reilly · Scott Taylor · Segayuu · Sergey Biryukov · sheepysheep60 · Shital Marakana · Shreyas Ikhar · siddharth · Siddharth Thevaril · silb3r · Simon Blackbourn · Simon Prosser · simonhammes · Siobhan · Smit Rathod · snapfractalpop · socalchristina · Spencer Cameron-Morin · stacimc · stefanfisk · Stefano Lissa · Stefano Minoia · Stefanos Togoulidis · Stephen Bernhardt · Stephen Edgar · Stephen Harris · Steve Grunwell · Subrata Sarkar · Sumit Singh · Sumit Singh · Sumon Sarker · SunilPrajapati · sunyatasattva · Sven Wagener · Sybre Waaijer · Synchro · Takashi Kitajima · Tammie Lister · tharsheblows · Theo H · Thimal Wickremage · Thomas McMahon · Thomas Patrick Levy · Thomas Pike · Till Krüss · Tim Blankenship · Tim Nolte · Timothy Jacobs · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tomasz Tunik · Tomek · Tomoki Shimomura · Tony Tahmouch · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Tracy · trex005 · tszming · tumas2 · twstokes · Tynan Beatty · tzipporahwitty · Uday Kokitkar · ugljanin · Ugyen Dorji · Ulrich · Utkarsh · valer1e · versusbassz · Vicente Canales · Vishal Kumar · vlad.olaru · Volodymyr Kolesnykov · vortfu · WebMan Design | Oliver Juhas · Wendy Chen · Wes Theron · Weston Ruter · whoisnegrello · Will Skora · wpmakenorg · wpsoul · WraithKenny · wslyhbb · Xidorn Quan · Yui · Yunus Ertuğrul · Zebulan Stanphill · znuff · Česlav Przywara
\n\n\n\nBy release day, 76 locales had translated 90-percent or more of WordPress 6.0 into their language. Community translators continue after a release ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in 205 languages.
\n\n\n\nMany thanks to all of the community volunteers who contribute to the support forums by answering questions from WordPress users around the world.
\n\n\n\nIf contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to Make WordPress and explore the product roadmap on the core development blog.
\n\n\n\nThe WordPress Mission & You
\n\n\n\nWordPress is software designed for everyone, emphasizing accessibility, performance, security, and ease of use. The project believes great software should work with minimum setup, so you can focus on sharing your story, product, or services freely. The basic WordPress software is simple and predictable so you can easily get started. It also offers powerful features for growth and success.
\n\n\n\nWordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a large community of people collaborating on and contributing to this project. The WordPress community is welcoming and inclusive. Our contributors’ passion drives the success of WordPress which, in turn, helps you reach your goals.
\n\n\n\nLearn more about WordPress and how you can join our community to help shape the future of the world’s most popular website platform.
\n\n\n\n\n\n\n\n
A Release Haiku
\n\n\n\nSix-point-oh is here
Time to download and upgrade
Let’s pause, celebrate
\n\n\n\n
1 According to W3Techs as of May 5, 2022.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 24 May 2022 20:01:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:69:\"Do The Woo Community: Builder Tips from WordCamp Europe 2022 Speakers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=71730\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://dothewoo.io/woocommerce-tips-speakers-wordcamp-europe/\";s: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:454:\"Tips from Daisy Olsen, Dave Lockie, Devin Walker, Greg Ziolkowski, Jonathan Wold, Milana Cap, Nev Harris, Paul Bearne, Ryan Welcher, Vassilena Valchanova and Vito Peleg
\n>> The post Builder Tips from WordCamp Europe 2022 Speakers appeared first on Do the Woo - a WooCommerce Builder Community .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 24 May 2022 09:01:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: Open Source Initiative Launches News Blog on WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=133438\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wptavern.com/open-source-initiative-launches-news-blog-on-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7242:\"The Open Source Initiative (OSI), a public benefit corporation and steward of the Open Source Definition, has launched a news blog on WordPress. In 2021, OSI’s board appointed Stefano Maffulli as its first Executive Director, and he is leading the organization in overhauling its web presence.
\n\n\n\n“One of the main objectives for OSI in 2022 is to reinforce our communication channels,” Maffulli said. “We’re improving the perception of OSI as a reliable, trustworthy organization. The OSI didn’t have a regular publishing schedule before, nor a content plan. Now we have established a regular cadence, publishing at least once a week (often more), commenting on recent news like a winning against a patent troll or court decisions about open source licenses, featuring our sponsors, and offering opinions on topics of interest for the wider community. It’s a starting point to affirm OSI as a convener of conversations among various souls of the open source communities.”
\n\n\n\nThe blog was launched on a subdomain of the opensource.org website, which uses Drupal 7, self-hosted on a droplet from Digital Ocean. It’s also tightly integrated with CiviCRM to manage members’ subscriptions, donations from individuals, tracking sponsorships, and sending the newsletter.
\n\n\n\nAs Drupal 7 is approaching EOL in November 2022, the team is planning to move everything to WordPress. They explored managed hosting with Drupal but found it was more expensive and also required them to migrate to a more recent version of Drupal. Themes and plugins made for D7 are not compatible with D9+, so they didn’t see an advantage in terms of time or simplicity.
\n\n\n\n“Unfortunately we don’t have staff to manage a self-hosted Drupal installation and nobody on staff really knows how to use it,” Maffulli said. “Tasks like creating landing pages proved to be quite time consuming for us.
\n\n\n\n“With money, knowledge and time constraints and an urgent need to increase our publishing rate, ramping up the organization’s visibility online we decided to migrate the website in two phases: First, we migrate the blog so we have a fresh look together with the improved publishing schedule. This phase is complete – the blog is on a managed hosting offered by DreamHost. The second phase is the migration of the rest of the site: this is ongoing with the help of Automattic and will take a few months to complete.”
\n\n\n\nAlthough Maffulli wanted to avoid creating a blog under a subdomain, and preferred using the old URL (opensource.org/blog...), mixing Drupal self-hosted with a managed WordPress site was not a common use case with straightforward solutions. If the new blog design looks familiar, that’s because it was inspired by WP Tavern’s new design.
\n\n\n\n“Once we decided to go with a subdomain, the new site took really only a few days to launch: I knew I wanted to have a simple site, minimal amount of plugins, no page builders and a very clean design based on WP Tavern, of which I’m a fan,” he said.
\n\n\n\nSince the Tavern’s theme wasn’t yet on GitHub, Maffulli contracted a developer who used WordPress’ new full-site editing features to create a simple child theme based on the Twenty Twenty-Two default theme. He said he is glad overseeing the project gave him a chance to learn the basics of FSE.
\n\n\n\nSome members of the OSI staff were already familiar with WordPress, which contributed to the decision to use the software. The wide range of functionality and third-party integrations were also a factor.
\n\n\n\n“We rely a lot on content calendar solutions that allow to manage schedule posts and social media promotions from one tool,” Maffulli said.
\n\n\n\n“We’re addicted to CoSchedule. That tool is far from perfect, primarily because it’s not Open Source. But it’s so incredibly powerful and convenient for a small team like us. We track our publishing calendar and tasks with CoSchedule, making it so easy not to miss a beat: every blog post has it’s social media attachment, same with the newsletter, that becomes a blog post for archive. Soon, we’ll add podcasts.”
\n\n\n\nMaffulli said he wishes the WordPress media library offered a more standardized way of storing and tracking copyright information, like the author, source, and license.
\n\n\n\n“I think this unnecessarily exposes WP users to copyright infringement claims where trolls could threaten successfully people who may have not kept their records clean,” he said. “It’s something to think about for future releases of Instant Images and similar plugins.”
\n\n\n\nThe OSI team has opted to keep comments closed on posts at this time, since they do not have the capicity to properly moderate comments.
\n\n\n\n“I have a lot of experience managing online communities and I know it can become very time consuming,” Maffulli said. “We just don’t have staff but we’re raising funds to solve that.”
\n\n\n\nOSI is also looking into creating a way to give its members the privilege of commenting. This would require a way to integrate authentication with CiviCRM to access members’ records.
\n\n\n\n“While we build staff and upgrade opensource.org, I hope to setup services from the IndieWeb community into Voices of Open Source,” Maffulli said. “This will allow for comments made on various social networks to be aggregated back into blog.opensource.org.”
\n\n\n\nThe new Voices of Open Source blog has started by featuring the network of OSI affiliates, which boasts 80 organizations, including Mozilla, Wikimedia, Linux Foundation, OpenUK, and more.
\n\n\n\n“We’d like to share OSI’s unique position to highlight open source stories, challenges, and successes of companies and people around the world,” Maffulli said. OSI is in communication with its affiliates to make them aware of this opportunity and is aiming to open guest posting on the blog to indvidual members in the wider community sometime 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:\"Mon, 23 May 2022 21:31:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:75:\"Post Status: WooCommerce Function of the Week: wc_get_product_category_list\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=97560\";s:7:\"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:85:\"https://poststatus.com/woocommerce-function-of-the-week-wc_get_product_category_list/\";s: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:8904:\"Here\'s yet another time-saving WooCommerce function. No need to reinvent the wheel — with a single line of code and no custom queries, you can get all the categories a product belongs to.
\n\n\n\nThis week\'s function is wc_get_product_category_list, and there\'s no need to explain what it does as its name is self-explanatory.
As usual, we\'ll study the WooCommerce core function code, see where and why it\'s used, and finally we\'ll cover a quick case study. Enjoy!
\n\n\n\n\n\n\n\nFunction code
\n\n\n\nThe function wc_get_product_category_list can be found under \\woocommerce\\includes\\wc-product-functions.php:
/**\n * Returns the product categories in a list.\n *\n * @param int $product_id Product ID.\n * @param string $sep (default: \', \').\n * @param string $before (default: \'\').\n * @param string $after (default: \'\').\n * @return string\n */\nfunction wc_get_product_category_list( $product_id, $sep = \', \', $before = \'\', $after = \'\' ) {\n return get_the_term_list( $product_id, \'product_cat\', $before, $sep, $after );\n}First of all, let\'s look at the function parameters:
\n\n\n\n$product_id, which is of course the product we want to get the categories for.$sep, by default a comma, which defines the list separator.$beforeand$after, by default empty strings, which define what shows before and after the list of categories. (prefix / suffix)
Now to the function statements — actually, statement, as there is only one:
\n\n\n\nreturn get_the_term_list( $product_id, \'product_cat\', $before, $sep, $after );That really sounds like a WordPress function as there is no mention of “woo,” “wc,” or any other WooCommerce prefixes. Let\'s look it up in the WordPress developer code reference documentation. (https://developer.wordpress.org/reference/functions/get_the_term_list/)
\n\n\n\nHere we go:
\n\n\n\nfunction get_the_term_list( $post_id, $taxonomy, $before = \'\', $sep = \'\', $after = \'\' ) {\n $terms = get_the_terms( $post_id, $taxonomy );\n \n if ( is_wp_error( $terms ) ) {\n return $terms;\n }\n \n if ( empty( $terms ) ) {\n return false;\n }\n \n $links = array();\n \n foreach ( $terms as $term ) {\n $link = get_term_link( $term, $taxonomy );\n if ( is_wp_error( $link ) ) {\n return $link;\n }\n $links[] = \'<a href=\"\' . esc_url( $link ) . \'\" rel=\"tag\">\' . $term->name . \'</a>\';\n }\n \n /**\n * Filters the term links for a given taxonomy.\n *\n * The dynamic portion of the hook name, `$taxonomy`, refers\n * to the taxonomy slug.\n *\n * Possible hook names include:\n *\n * - `term_links-category`\n * - `term_links-post_tag`\n * - `term_links-post_format`\n *\n * @since 2.5.0\n *\n * @param string[] $links An array of term links.\n */\n $term_links = apply_filters( \"term_links-{$taxonomy}\", $links ); // phpcs:ignore WordPress.NamingConventions.ValidHookName.UseUnderscores\n \n return $before . implode( $sep, $term_links ) . $after;\n}Simple enough — get_the_term_list accepts basically the same parameters we covered above, plus the $taxonomy parameter, which in our case is passed as product_cat to tell WordPress we\'re retrieving WooCommerce product categories.
Here\'s how it works:
\n\n\n\nget_the_terms( $post_id, $taxonomy )gets the product ID category objects.$linksarray gets filled with the list of categories, each with its own link.return $before . implode( $sep, $term_links ) . $aftergives us the content we need: “prefix + $links separated with $sep + suffix”
Function usage
\n\n\n\nDefine a product ID (e.g., 57) — and that\'s all you need to do!
\n\n\n\nCall the function:
\n\n\n\necho wc_get_product_category_list( 57 );And see the magic happen:
\n\n\n\ncat1 link, cat2 link, cat3 link, ...Of course, if you have access to the $product global, you can call the function dynamically. For example, if you want to call the function on every single product pages, you could do this:
echo wc_get_product_category_list( $product->get_id() );Now I want to see where and when the function is called, so we give it a bit of context. With a quick search through the WooCommerce plugin, I find a single result in \\woocommerce\\templates\\single-product\\meta.php, line 34:
<?php echo wc_get_product_category_list( $product->get_id(), \', \', \'<span class=\"posted_in\">\' . _n( \'Category:\', \'Categories:\', count( $product->get_category_ids() ), \'woocommerce\' ) . \' \', \'</span>\' ); ?>Which generates this output on my single product page:
\n\n\n\n![\"\"](\"https://cdn.poststatus.com/wp-content/uploads/2022/05/image-752x357.png\")
Now we know wc_get_product_category_list is responsible for showing the list of categories in the single product page where it comes with a prefix (‘Category:\' or ‘Categories:\' based on category count) plus the default comma separator and no suffix.
Let\'s use wc_get_product_category_list for our custom development example now and consider a quick case study.
Case study
\n\n\n\nWhere could wc_get_product_category_list come in handy? Surely, in the shop page.
By default, WooCommerce shows the list of products with image, title, price and button. There is no mention of product categories there, so let\'s add them ourselves.
\n\n\n\nBefore:
\n\n\n\n![\"\"](\"https://cdn.poststatus.com/wp-content/uploads/2022/05/image-1-752x398.png\")
The custom snippet:
\n\n\n\n/**\n * @snippet Show Categories | WooCommerce Shop\n * @how-to Get CustomizeWoo.com FREE\n * @author Rodolfo Melogli\n * @testedwith WooCommerce 6\n * @donate $9 https://businessbloomer.com/bloomer-armada/\n */\n\nadd_action( \'woocommerce_after_shop_loop_item\', \'bbloomer_show_product_categories\', 9 );\n\nfunction bbloomer_show_product_categories() {\n global $product; \n echo wc_get_product_category_list( $product->get_id(), \' - \', \'<p>In: \', \' \' . _n( \'category\', \'categories\', count( $product->get_category_ids() ), \'woocommerce\' ) . \'</p>\' );\n}After:
\n\n\n\n![\"\"](\"https://cdn.poststatus.com/wp-content/uploads/2022/05/image-2-752x383.png\")
A few notes:
\n\n\n\n- I used the
woocommerce_after_shop_loop_itemhook with priority 9, which is just before priority 10 (the add-to-cart button). TLDR: I\'m outputting the category list above the add to cart button. - I declare the global
$productso that I can access the product ID. - I then call the
wc_get_product_category_list function, with the following parameters:$product->get_id() -> the product ID\' - \' -> the separator\'<p>In: \' -> the prefix\' \' . _n( \'category\', \'categories\', count( $product->get_category_ids() ), \'woocommerce\' ) . \'</p> \' -> the suffix
It\'s interesting how I reused this line from the single product page, as I mentioned above:
\n\n\n\n_n( \'category\', \'categories\', count( $product->get_category_ids() ), \'woocommerce\' )Basically, if count = 1 the first string is returned (singular “category”), while if count > 1 you get the plural “categories.” You can see the difference in the last screenshot above.
Any other use cases you have in mind? 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, 22 May 2022 21:00:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Rodolfo Melogli\";s: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:88:\"Gutenberg Times: WordCamp Europe, 75 Themes, Thunks and Filters – Weekend Edition 216\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=21184\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"https://gutenbergtimes.com/wordcamp-europe-75-themes-thunks-and-filters-weekend-edition-216/\";s: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:11675:\"Howdy,
\n\n\n\nGreetings from Porto, Portugal. It’s a wonderful city. You cn walk and walk and walk, up the hill, down the hill, with ever changing view. The ratio of restaurants and bar per block is on average three. In certain areas, every single doorwar offers you a different place to eat or drink.
\n\n\n\n\n\nLast week, WordCamp Europe organizers announced that there will be a livestream of the sessions’ in track one and two. That’s good news, as there are amazing talks and speakers on the schedule. If you want to casually run into me, I will be at the Community Booth Friday and Saturday around 10 am ?
\n\n\n\nBefore people from the WordPress Community descend to Porto, core contributors will release WordPress 6.0 on May 24, 2022. The signs seem in their favor, and RC candidate four is now available. Hector Prieto, release co-coordinator, outline the WordPress 6.0 Release Day Process, just in case you are interested in how the sausage is made, so to speak.
\n\n\n\nStay well, and safe!
\n\n\n\nYours, ?
Birgit
Theme Building and Full-Site Editing
\n\n\n\nNick Diego, developer advocate at WPEngine, has been teaching the Working with Template in Full Site Editing series on the Meetup Social Learning space. Part 1 and Part 2 are now available on WordPress.tv
\n\n\n\n- Working with Templates in Full Site Editing (Part 1)
- Working with Templates in Full Site Editing (Part 2)
\n\n\n\n
If you want to know how far the Gutenberg project and the block editor in WordPress has come, watch this video by Anne McCarthy: Building a site with WordPress 5.0 vs WordPress 6.0
\n\n\n\n\n\n\n\n
The Pattern Creator is a online tool which allows you to create block patterns for inclusion into the WordPress Patterns Directory, a place where you can access freely available patterns for your websites. On this podcast episode of the WPTavern’s Jukebox, Ana Segota and Kelly Choyce-Dwan on How To Use the New Pattern Creator, Nathan Wrigley talked to Ana Segota and Kelly Choyce-Dwan, who share two different perspectives. Segota is a themer and Choyce-Dwan is on the team, that built the Pattern Creator.
\n\n\n\n\n\n\n\n
Now that the Style Switcher is coming to WordPress 6.0, it might be time to learn how to create Style variations for your theme. A style variations is a user-selectable skin of the same theme. Everything stays that same except the color palette or the available fonts. Caroline Nymark published a lesson for you on her site.
\n\n\n\nJustin Tadlock also wrote about Global Style Variations, “Skins” for Themes, Have Landed in Gutenberg earlier this year.
\n\n\n\n\n\n\n\n
Carolina Nymark aslo pursued the question: Can a full site editing theme be accessibility-ready? and shares her throughts and knowledge
\n\n\n\nUpdate for site owners and site builders.
\n\n\n\n75 Block Themes in the WordPress Theme Directory, Catch FSE is one of them. Justin Tadlock took it for a spin and published his review. Catch FSE Is a Bold, Business-Friendly WordPress Block Theme.
\n\n\n\nTake a look at the others: WordPress Theme Directory, Full-Site Editing
\n\n\n\n\n\n\n\n
Kevin Batdorf, developer at Extendify, published a plugin called Image Filters that adds 22 more filters to your choices, even better than Instagram and you can do it all on your website!
\n\n\n\nRead more about it on the WPTavern: The Image Filters Plugin Adds Over 20 Filters, Including Vintage, Pastel Pink, and More
\n\n\n\nNow available on WordPress TV
\n\n\n\nUsing the Navigation Block with Wes Theron, a 45 minute walk through the ins and outs of the new Navigation block.
\n\n\n\nAnd when you are done with that, or if you already know it you might want to Take Advantage of Query Loops also with Wed
\n\n\n\nBlock Buidling and Tools for Developers
\n\n\n\nIn his live stream, reviewing the changes to the @wordpress/scripts package and trying out Thunks for the first time, Ryan Welcher looked at the new changes to the @wordpress/scripts package that make using it much easier for developers. He then get into using Thunks in the datastore created for the pre-publish checklist.
\n\n\n\nWhat are Thunks you might ask? Here is a post by Adam Zielinsky: Thunks in Gutenberg
\n\n\n\nUpcoming WordPress Events
\n\n\n\nSocial Learning Events
\n\n\n\nMay 23, 2022 1pm EDT / 17:00 UTC
Hello Blocks! Coding a custom block w/ Ryan Welcher
May 25, 2022 – 7pm EDT / 23:00 UTC
Design With Me: Create a Simple Website for your Small Business w/ Sarah Snow
May 26, 2022 – 5 pm EDT / 19:00 UTC
I want a Website, not a Blog! w/ Destiny Kano
June 16, 2022 – 5pm EDT / 19:00 UTC
Let’s build a homepage together w/ Wes Theron.
WordCamp and other Events
\n\n\n\nJune 2 – 4th, 2022
WordCamp Europe
June 11 + 12, 2022
WordCamp Warsaw
June 20 – 24, 2022
Page Builder Summit
June 25, 2022
WordCamp Montclair, NJ
September 9 – 11, 2022
WordCamp US, San Diego, California
September 15 + 16, 2022
WordCamp Netherlands
February 17-19 2023 (tent)
WordCamp Asia, Bangkok, Thailand
\n\n\n\n
Don’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 21 May 2022 05:43:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"WPTavern: New Video Explores Site Building Progress From WordPress 5.0 to 6.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=134617\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:88:\"https://wptavern.com/new-video-explores-site-building-progress-from-wordpress-5-0-to-6-0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4086:\"
Do you remember what it was like to use WordPress 5.0? Three years and ten major releases have radically changed the site building experience, but it’s not always easy to see recognize when focused on some of the smaller, iterative changes that slowly add up. Anne McCarthy, WordPress product liaison at Automattic and co-release coordinator for 6.0, has created a short 13-minute video that shows the immense amount of progress contributors have made on site building features.
\n\n\n\n\n\n\n\nMcCarthy takes viewers back in time to WordPress 5.0, released in December 2018, which introduced the block editor and the Twenty Nineteen default theme through the work of 400+ contributors. She demonstrates using the Customizer with the default theme. These were simpler days and it’s clear now how limited the Customizer was for implementing the most basic changes.
\n\n\n\nThe video contrasts that experience with the upcoming 6.0 release, which features the work of 500+ contributors on features that didn’t exist three years ago.
\n\n\n\nMcCarthy quickly demonstrates the 6.0 site editing experience, swapping out template parts, and showcasing the breadth of the customization available for images, colors, typography, controlling the posts that are displayed, style variations, and the impressive array of design tools available.
\n\n\n\nTen major versions later, nearly every aspect of a WordPress site is customizable through the site editor. For those who have not yet made the leap into full-site editing – it’s essentially like the old Customizer but with super powers, better instant previews, and the interface is a panel on the right. At this point, I don’t think the usability is at a level where someone can just get in there and immediately know what they are doing. It takes a little bit of exploring, but it’s moving in the right direction.
\n\n\n\nVideos like this one show what is possible and just how far WordPress has come since it first introduced the block editor. It also indirectly answers Joost de Valk’s recent claims that the full-site editing project not being done yet is partially to blame for WordPress’ recent decline in market share.
\n\n\n\nWhile WordPress remains the uncontested market leader among CMS’s, some say this small percentage of a decline is inconsequential. Matt Mullenweg has stated in previous interviews that he views market share stats as a “trailing indicator” in the quest to create the best possible experience for users and developers. A growing market share, in that sense, is a signal of user satisfaction.
\n\n\n\nWordPress jumped into the block paradigm at the right time, just as many other apps began adopting the concept of composable blocks for creating content and designs. Full-site editing is the extension of that vision but it takes time to make it something polished and delightful to use. McCarthy’s video is a good reminder of the limitations that users previously labored under while trying to edit their sites, and the “why” behind all the effort going into FSE.
\n\n\n\n“As someone who’s currently on the WordPress 6.0 Release Team, I can attest that the project needs more contributors,” WordPress contributor Nick Diego said in response to the recent market share discussion. “The fact that FSE has taken so long is not a lack of effort. There are many contributors pouring their hearts and souls into the project. We just need more help.”
\";s: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, 21 May 2022 01:14:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:67:\"Post Status: Post Status Upgrade — Zen and the Art of Lockpicking\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=97950\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://poststatus.com/zen-and-the-art-of-lockpicking/\";s: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:2550:\"Learn new skills and build your knowledge to enhance your career in WordPress! Post Status Upgrade is an ongoing series of live workshops centered around a particular skill or learning activity.
\n\n\n\nWatch Robert Rowley explain the basics of lock picking in this live, hands-on workshop for Post Status members that took place on May 5th, 2022. Watch as Robert teaches participants how to open locks, as well as their minds. He shares stories about emotional intelligence and the life cycle of skill practice from the beginner\'s mind to the expert\'s. You\'ll laugh at some entertaining mishaps Robert has had with lock picks!
\n\n\n\n![\"Robert](\"https://cdn.poststatus.com/wp-content/uploads/2022/03/robert-snow-1-132x150.png\")
Robert RowleyRobert Rowley is Patchstack‘s Security Advocate and has been picking locks since 2004. Between 2016 and 2019 Robert ran a retreat for his information security friends and colleagues called Disconnect Camp. This is where he first combined skills like lock picking with reflection on mental health, wellness, skill development and more.
\nStellarWP is a collective of WordPress innovators empowering business owners and creators with plugins and tools to help them thrive. We build great plugins, but we don’t stop there; we continually challenge ourselves to keep innovating and improving. Our solutions include the most trusted names in WordPress, with more than 2.5 million installs. Since 2021, we’ve grown to encompass seven brands and dozens of plugins. StellarWP is part of the Liquid Web family of brands.
Kim Parsell Memorial Scholarship returns to WCUS › Think like a platform again! › Leo Gopal on support for mental health in the community › WP Accessibility Day › Performance Lab 1.1.0 › The WordPress Way › Dropping jQuery for speed › More to WP than Headless and FSE for devs › and more…
With WordCamp US being held in-person (September 9-11), that also means the WordPress Foundation’s Kim Parsell Memorial Scholarship has returned! This scholarship provides financial assistance — including travel costs — so the recipient can attend the conference. It\'s good to see three scholarships will be awarded this time, thanks to COVID-19 taking out in-person events for us in 2020 and 2021.
\n\n\n\nBrian Coords says WordPress “needs to start thinking like a platform again.” While I don\'t agree that Full Site Editing feels like or is the next “Google Plus or Apple’s Ping,” I do believe it could distract from user experience elsewhere and other things that need attention. (My take: Google abandoned Plus without putting much effort into it, and Apple is just bad at social full stop.) [DB]
\n\n\n\nI talked about what WordPress needs in a recent Post Status Comments episode on the prospects of declining market share with Joost de Valk, Alex Denning, and Jessica Frick. [DB]
\n\n\n\nLeo Gopal from Cape Town, South Africa writes about depression and mental illness, and how the WordPress community has rallied around him.
\n\n\n\nHere\'s a new plugin from Xaver Birsak that hosts the Google Fonts you use on your own server.
\n\n\n\nIf you\'re a Gravity Forms user and have ever needed charts and graphs, then GravityView‘s new plugin might be of interest.
\n\n\n\nThe WP Accessibility Day website is live! The date for this event is November 2-3, 2022.
\n\n\n\nCarolina Nymark took to Twitter for an insightful investigation and survey about the Full Site Editing themes already in the .org theme directory. She shares stats like the number of core blocks styled in theme.json and common color slugs.
Here\'s a good two part series (part one and part two) from Hidde de Vries on common accessibility issues that you can address and fix on your site today.
\n\n\n\nRoss Wintle has combined a searchable command palette with “fancy browser APIs” to enable voice-controlled WordPress. Fun experiment!
\n\n\n\nIf you are new to WooCommerce and looking into performance enhancements, this post from Ibad Rehman might be a good place to start.
\n\n\n\nBernhard Kau has released a WordPress plugin for MailChimp users. “If you are using MailChimp and want to show a nice archive on your page, you can now add it with a block.”
\n\n\n\nThe WordPress Performance Team has published the 1.1.0 release of the Performance Lab plugin. It includes an enhancement that “replaces the featured image with a WebP version when available.”
\n\n\n\nA nice take here from Ollie Williams on color fonts. Modern web typography, fonts, and CSS have come very far in a relatively short period of time.
\n\n\n\nWhile Jason Coleman‘s “The WordPress Way” post is a few weeks old, if you haven\'t read it, you should. Jason explains the core values of his team at Paid Memberships Pro, which includes the idea that the GPL license will result in “the best code.”
\n\n\n\nJason explains what this means in specific terms in a time of debate and discussion about what should happen to WordPress software when a paid support license expires. For Jason, the WordPress way “means our code will continue to work as expected if your paid license expires.”
\n\n\n\nWhile I think there are slightly different takes on what is best for customers and that experiments in the WordPress ecosystem should be encouraged, I also would like to see more people follow in Jason\'s footsteps and publish their core values.
\n\n\n\nWooCommerce has opened up a call for testing regarding the move to custom tables. It\'s the first milestone for a large effort but the goal of the call “is to test the migration process across various hosts and server combinations.”
\n\n\n\nCourtney Robertson shows you how to lock blocks in WordPress, a new feature coming in 6.0. Good for when a client takes over writing and revising content and hits a button accidentally.
\n\n\n\nHere\'s a free and open source tool that converts tweets into static HTML — perfect for testimonials.
\n\n\n\nGOV.UK dropped their jQuery dependency from their front end, with some impressive numbers in the performance results. Great takeaway: “Don\'t shortchange your users if the web platform can easily do the job a framework can.”
\n\n\n\nHéctor Prieto shares the WordPress 6.0 release process (starting next week), including the timeline and how you can help.
\n\n\n\nTom McFarlin thinks there is more to WordPress than FSE and Headless. He feels “we’re spending a lot of time talking about the same things in WordPress as of late.”
\n\n\n\nI can understand where Tom is coming from — there are lots of technologies beyond React we can use. Getting off the beaten path is a good way for developers to get new ideas, have fun, and prevent nimble competitors from dominating certain niches.
\n\n\n\nJonathan Bossenger explains why it\'s important to think about indexes for custom database tables — and when not to use them. He shows how you can diagnose and add indexes, offering valuable tips. One example: “When you are filtering or joining data based on specific fields, adding indexes to those fields is a crucial step in ensuring your queries are optimized.”
\n\n\n\nSari Azout says it’s no longer enough to organize the world’s information — it\'s more important to organize the world’s trustworthy information with “boutique search engines that index, curate, and organize things in new ways.” This article rings true to me, as I find some Google searches less effective than they have been in the past.
\n\n\n\nDo you enjoy our weekly notes?
\n\n\n\nGet them and more in Post Status\' Week in Review. We gather WordPress and WooCommerce news along with significant writing, videos, and podcast episodes from the WordPress community and beyond. Don\'t miss the latest updates from the people making WordPress in our This Week at WordPress.org summaries. It\'s all in our newsletter!
\n\n\n\nGrowth is uncomfortable; you have to embrace the discomfort if you want to expand.
Jonathan Majors
Have you ever had to work outside of your comfort zone? It’s something I’m trying to get used to. But it sure isn’t easy.
\n\n\n\nThis week and next I’m working from my dad’s home office in Tennessee while we prepare to sell his house.
\n\n\n\nThis place is beautiful, and the view from the office is breathtaking. It’s easy to see why my dad loved it here.
\n\n\n\nBut beautiful things can still be uncomfortable.
\n\n\n\nTraveling to WCEU has many people anxious about traveling after so long, and attending a WordCamp after a number of years.
\n\n\n\nBut discomfort can help us grow, connect, and be more than we were before.
\n\n\n\nWhatever you’re doing, I hope you’ve built in a little discomfort to help you evaluate where you are, plan a course for the future, and thrive wherever you end up.
\n\n\n\nIf you\'re going to WCEU, here are some tips on getting the most out of it!
\n\n\n\nHave a great weekend,
\n\n\n\n— Michelle
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 20 May 2022 19:22:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Michelle Frechette\";s: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:69:\"Post Status: WordPress Podcast and Video Picks for the Week of May 15\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=97722\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://poststatus.com/wordpress-podcast-and-video-picks-for-the-week-of-may-15/\";s: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:3617:\"Good viewing and listening for you this weekend! Krogsgard on memberships and churn. Web 2.0 tech leaders reflect. Mike McAlister on the journey from Atomic Blocks and Array Themes to the Liftoff Creator Course. Paid services at Underrepresented in Tech. The Pattern Creator and Directory. WCEU. Inclusive Open Source Processes and Governance.
My Podcast Picks
\n\n\n\n- How I Built It: Post Status founder Brian Krogsgard on determining membership benefits and preventing churn.
- Techmeme Ride Home: Not WordPress-related, but this reunion of some key web 2.0 tech leaders is a fascinating retrospective.
- Make Lemonade: Mike McAlister on how he went from selling his WordPress business to WP Engine to launching the Liftoff Creator Course.
- Underrepresented in Tech: It\'s Allie Nimmons and Michelle Frechette on the paid services they provide and why these are important additions to the UiT database.
- WP Tavern Jukebox: Ana Segota and Kelly Choyce-Dwan on the new Pattern Creator and the WordPress Patterns Directory.
- Do The Woo: Two of the WCEU organizing team members, Takis Bouryouris and Taeke Reijenga, talk about the upcoming conference.
My Video Pick
\n\n\n\n- Inclusive Open Source Processes and Governance is a great presentation by Silona Bonewald via Open Source 101 in early April 2022.
Get our weekly WordPress community news digest — Post Status\' Week in Review — also available in our newsletter.
And don\'t miss the latest updates from the people making WordPress. We\'ve got you covered with This Week at WordPress.org.
Version 4.2.4 of the Akismet plugin for WordPress is now available. This update contains the following improvements:
\n\n\n\n- Improved translator instructions for comment history.
- Bumped the “Tested up to” tag to WP 6.0.
To 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:\"Fri, 20 May 2022 10:01:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Stephane Daury\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"Do The Woo Community: Do the Woo is Heading to WordCamp Europe 2022 as a Media Partner\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=71779\";s:7:\"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:24:\"https://dothewoo.io/235/\";s: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:385:\"WCEU is happening in Porto, Portugal. Find Do the Woo there and join us in a podcast or let\'s just have a conversation.
\n>> The post Do the Woo is Heading to WordCamp Europe 2022 as a Media Partner appeared first on Do the Woo - a WooCommerce Builder Community .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 20 May 2022 09:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:49:\"BuddyPress: BuddyPress 10.3.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=324694\";s:7:\"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://buddypress.org/2022/05/buddypress-10-3-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:1192:\"Immediately available is BuddyPress 10.3.0. This maintenance release fixes seven bugs, mainly BP Nouveau improvements. It also makes sure BuddyPress is ready for the upcoming WordPress 6.0 release. For details on the changes, please read the 10.3.0 release notes.
\n\n\n\nUpdate to BuddyPress 10.3.0 today in your WordPress Dashboard, or by downloading it from the WordPress.org plugin repository.
\n\n\n\nMany thanks to 10.3.0 contributors
\n\n\n\nmike80222, oztaser, mackey1, shanebp, comminski, dd32 & imath.
\";s: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, 19 May 2022 21:45:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:29:\"WPTavern: WP Tavern Is Hiring\";s:7:\"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=134578\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wptavern.com/wp-tavern-is-hiring\";s: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:1256:\"WP Tavern is looking for talented writers who are eager to report on WordPress news every day. We cover a wide range of topics, including (but not limited to) the Gutenberg project, core development, e-commerce, community, plugin and theme ecosystems, events, and the wider world of open source software. We are looking for writers who can inform, engage, and inspire readers with their work.
\n\n\n\nThe position requires the ability to discern the immediacy of news stories that need to be told, attention to accuracy, and the ability to cultivate sources. Applicants must be willing to engage positively with the WordPress community and maintain an unwavering commitment to serve the public interest, without corporate influence. A deep knowledge of the WordPress ecosystem and the Gutenberg project is helpful for this position.
\n\n\n\nWP Tavern is WordPress’ newspaper of record. We are looking for writers who can approach this community with a critical and unbiased point of view, preserving the independent and provocative spirit of the Tavern. Applicants should use the contact form to get in touch, and be prepared to submit at least three writing samples for consideration.
\";s: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, 19 May 2022 18:25:55 +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:76:\"Do The Woo Community: WooCommerce Checkout and Cart Blocks with Nadir Seghir\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=71766\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://dothewoo.io/woocommerce-checkout-and-cart-blocks-with-nadir-seghir/\";s: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:436:\"Automattic engineer Nadir Seghir chats about where we are at with the WooCommerce cart and checkout blocks and where we are going.
\n>> The post WooCommerce Checkout and Cart Blocks with Nadir Seghir appeared first on Do the Woo - a WooCommerce Builder Community .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 19 May 2022 09:28:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:78:\"WPTavern: WooCommerce Calls for Early Testing on Custom Order Table Migrations\";s:7:\"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=134456\";s:7:\"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:89:\"https://wptavern.com/woocommerce-calls-for-early-testing-on-custom-order-table-migrations\";s: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:2217:\"At the beginning of this year, WooCommerce announced its plan to produce an MVP of custom order tables by Q3, 2022, a long-awaited improvement that promises significant performance gains for stores. The plugin’s development team is now calling for developers, agencies, and hosting companies to test migration to its first implementation of customer order tables.
\n\n\n\nThe process involves migrating orders from wp_posts and wp_postmeta to four new custom orders tables:
- wp_wc_orders
- wp_wc_order_addresses
- wp_wc_order_operational_data
- wp_wc_orders_meta
It requires a staging environment configured with WP-CLI and a staging database pre-loaded with order data.
\n\n\n\nWooCommerce developer Vedanshu Jain has created a migration testing guide, which details the custom code developers will need to add in order to enable the custom order tables. Once enabled, developers will have the option to migrate tables using WP-CLI or via Action Scheduler.
\n\n\n\nJain is requesting feedback from anyone who runs the migration process with details about how many orders, server memory size, DB version, and whether or not it timed out or responded better to a different batch size.
\n\n\n\nWooCommerce updating to use custom order tables will be a major change that will impact extension developers in different ways. The development team intends to publish an upgrade guide to support adoption of custom order tables after migrations have been ironed out. Later this year, when the update is anticipated to be rolled out to the core plugin, WooCommerce is aiming to make it strictly opt-in at first to allow shop owners time to make their sites compatible.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 18 May 2022 21:05: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: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:87:\"WordPress Foundation: The Kim Parsell Memorial Scholarship Returns for WordCamp US 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://wordpressfoundation.org/?p=262042\";s:7:\"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:108:\"https://wordpressfoundation.org/news/2022/the-kim-parsell-memorial-scholarship-returns-for-wordcamp-us-2022/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1709:\"The wait is over! WordCamp US is once again being held as an in-person, and with that the WordPress Foundation’s Kim Parsell Memorial Scholarship returns.
\n\n\n\nKim’s commitment and valuable contributions to the WordPress open source project are honored at each in-person WordCamp US by the WordPress Foundation. The Foundation’s goal is to further the efforts of other contributors demonstrating Kim’s spirit by helping to ease the burden that travel can bring.
\n\n\n\nThis scholarship is awarded to someone who:
\n\n\n\n- Identifies as a woman.
- Is a WordPress contributor.
- Has never attended WordCamp US before.
- Requires financial assistance to attend.
This scholarship provides financial assistance so that the recipient can attend WordCamp US, including travel from the recipient’s home city, hotel stay for the duration of the event, and a ticket to WordCamp US.
\n\n\n\nFinally, since the WordPress Foundation was unable to offer the scholarship in 2020 and 2021 due to the COVID-19 pandemic, this year only there will be three (3) scholarships awarded for 2022, 2021, and 2020.
\n\n\n\nIf you meet these requirements and would like to be considered, please apply no later than Sunday, June 26, 2022 at 12 am Pacific. All applicants will be notified by July 5, 2022.
\n\n\n\nFor more details, please visit the WordPress Foundation’s About the Kim Parsell Memorial Scholarship page.
\n\n\n\nApply for the scholarship today.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 18 May 2022 20:42:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Cate DeRosia\";s: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:54:\"Post Status: This Week at WordPress.org (May 16, 2022)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=97849\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://poststatus.com/this-week-at-wordpress-org-may-16-2022/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:15949:\"Each week we are highlighting the news from WordPress.org that you don\'t want to miss. If you or your company create products or services that use WordPress, we\'ve got the news you need to know. Be sure to share this resource with your product and project managers.
Are you interested in giving back and contributing your time and skills to WordPress.org? Start Here ›
Get our weekly WordPress community news digest — Post Status\' Week in Review — covering the WP/Woo news plus significant writing and podcasts. It\'s also available in our newsletter.
News
\n\n\n\n- WordPress 6.0 Release Candidate 3 (RC3) Now Available for Testing
- WordPress 6.0 Field Guide
- WP Briefing: Episode 31: Open Source & Accessibility– Celebrating Global Accessibility Awareness Day With Guest Joe Devon
Accessibility
\n\n\n\n- Request for feedback on the WordPress Accessibility Statement.
Central
\n\n\n\n- WordCamp Europe 2022 is just around the corner
- Join the European WordPress Community in Porto, Portugal!
Core
\n\n\n\nReminder: Gutenberg 13.0 ships with WordPress 6.0.
\n\n\n\n- WordPress Hosting Image/Storage questions
- Ensure WebP/Image/Optimization plugins can integrate & use existing WebP images
- Research: Impact of additional WebP images on upload
- Research: WebP compatibility
- Prime users in cache in WP_Query
- Measurement overview doc
- Capturing front-end performance metrics in WordPress doc
- Module proposal workflow
- Large-site inefficiency in REST users endpoint used by Gutenberg editor
- A Week in Core – May 16, 2022
- What’s new in Gutenberg 13.2? (May 11)
DevNotes
\n\n\n\nLeading up to releasing WordPress 6.0, DevNotes and release-related information will remain.
\n\n\n\n- WordPress 6.0 Field Guide
- Block Locking Settings in WordPress 6.0
- WordPress 6.0 Release Candidate Phase
- Miscellaneous Dev Notes for WordPress 6.0
- Block Editor miscellaneous Dev Notes for WordPress 6.0
- Page creation patterns in WordPress 6.0
- Global Styles variations in WordPress 6.0
- Separator block: Updated to use block supports color settings
- Block markup updates for image, quote, list, and group blocks
- Support for handling resolution errors for Editor data module
- Taxonomy performance improvements in WordPress 6.0
- Changes to the do_parse_request filter in WordPress 6.0
- Caching improvements in WordPress 6.0
- New filter to modify content images in WordPress 6.0
- Media: storing file size as part of the metadata
- Updates to the @wordpress/create-block templating system
- Object type-specific registration hooks in 6.0
- Taxonomy performance improvements in WordPress 6.0
- New features for working with patterns and themes in WordPress 6.0
- Theme export in WordPress 6.0
- WP_User_Query now accepts fields options in WordPress 6.0
- Performance increase for sites with large user counts (now also available on a single site)
Docs
\n\n\n\n\n\n\n\nSupport Docs:
\n\n\n\n\n\n\n\nDeveloper Docs:
\n\n\n\n\nCommunity
\n\n\n\n\n\n\n\nDesign
\n\n\n\n\n\n\n\nHosting
\n\n\n\n\n\n\n\nMeta
\n\n\n\n\n\n\n\nMobile
\n\n\n\n- Mobile Team Update – May 18th
- Call for Testing: WordPress for Android 19.9
- Call for Testing: WordPress for iOS 19.9
Plugins
\n\n\n\n\n\n\n\nPolyglots
\n\n\n\n\n\n\n\nProject
\n\n\n\n\n\n\n\nTest
\n\n\n\n\n\n\n\nThemes
\n\n\n\n\n\n\n\nSupport
\n\n\n\n\n\n\n\nTraining
\n\n\n\n\n\n\n\nSocial Learning Spaces:
\n\n\n\n\nFive for the Future
\n\n\n\nWhat\'s happening specific to Five for the Future? Provide your feedback on these posts:
\n\n\n\n- Default workflow for team membership lifecycle?
- Add activity when Meetup organizers host events
- Update Usermeta with latest 5ftf contribution.
You — and your whole team can Join Post Status too!
\n\n\n\nBuild your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. Listen to podcasts. Follow @Post_Status.
The Software Freedom Conservancy (SFC), a non-profit that provides infrastructure support for free and open source software projects, has received a favorable ruling in its right-to-repair lawsuit against Vizio, an American TV manufacturer. The SFC alleges that Vizio has demonstrated “repeated failures to fulfill even the basic requirements of the General Public License (GPL),” after the company refused to provide the source code for software with copyleft licenses that it bundles with its products.
\n\n\n\nVizio had filed a request to “remove” the case from California State Court into U.S. Federal Court. After hearing oral arguments from both sides, the court has granted SFC’s motion to remand the case back to California State Court.
\n\n\n\nIn the ruling, US District Court judge Josephine L. Staton stated that the GPL introduces “an additional contractual promise separate and distinct from any rights provided by the copyright laws:”
\n\n\n\n\n\n\n\nThe Court finds Versata’s reasoning persuasive, and it finds here, as the court
found there, that the enforcement of “an additional contractual promise separate and distinct from any rights provided by the copyright laws” amounts to an “extra element,” and therefore, SFC’s claims are not preempted. Id. at *5. There is an extra element to SFC’s claims because SFC is asserting, as a third-party beneficiary of the GPL Agreements, that it is entitled to receive source code under the terms of those agreements. There is no right to receive certain works—or source code in particular—under the Copyright Act; indeed, the Act’s primary purpose is to limit who may reproduce, prepare derivative works, distribute, and display protected works. As SFC points out in its briefing, the right to receive the source code would appear to be “the very opposite” of those exclusive rights. (Reply, Doc. 26, at 17.) The fact that SFC claims status as a third-party beneficiary to the GPL Agreements and not the actual copyright holder—and therefore, has no authority to impose limitations on the reproduction and distribution of the software—only underscores that the contractual right at issue is qualitatively different from the rights under the Copyright Act. Thus, there can be no question that the extra element—that SFC is third-party enforcing its right to receive source code under the terms of a contract—transforms the nature of the action.
One of the functions of the SFC is to assist member projects in enforcing the terms of FLOSS licenses, including through litigation. This particular case is unique because the organization is presenting this lawsuit on behalf of individual consumers, as opposed to the traditional path of defending copyright holders of the GPL code in question.
\n\n\n\n“The ruling is a watershed moment in the history of copyleft licensing,” SFC executive director Karen Sandler said. “This ruling shows that the GPL agreements function both as copyright licenses and as contractual agreements.”
\n\n\n\nSFC contends that many electronics products are built for planned premature obsolescence and that companies often do this by violating the GPL. If the product is bundled with copyleft software, a consumer has the right to modify, improve, and repair the software. For this the be possible, the companies producing the products must make the source code available. This also enables consumers to find skilled people to repair their products when a device fails after updates have been disabled so that products do not become nonfunctional. This ruling is not just a major win for the GPL but also for consumers who may not know that companies violating the GPL significantly impact their ability to find repairs for electronic products.
\n\n\n\n“Software Freedom Conservancy looks forward to our opportunity to prove, in state court, our third-party beneficiary right to the complete, corresponding source code as defined by the GPL and related agreements,” Sandler said. “This claim is central to the right to software repair, as it allows users to exercise the right to copy, share, modify, and reinstall the software on the devices that they receive.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 18 May 2022 18:03:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:88:\"WPTavern: #27 – Ana Segota and Kelly Choyce-Dwan on How To Use the New Pattern Creator\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=134337\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:102:\"https://wptavern.com/podcast/27-ana-segota-and-kelly-choyce-dwan-on-how-to-use-the-new-pattern-creator\";s: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:48510:\"On the podcast today we have Ana Segota and Kelly Choyce-Dwan.
\n\n\n\nI suspect that you might have heard about block patterns, but if you haven’t, you’re in for a treat. Patterns are collections of blocks which anyone can assemble for easy reuse at a later date. You can make them as simple or as complex as you, style them and save them away. When you’re ready to reuse them, they’re just one click away. It’s a great time saver.
\n\n\n\nHaving said that, not all of us are great at design, or perhaps we’ve just not had the time to explore how block patterns are created. Wouldn’t it be great if there was a source of patterns which we could use in our WordPress websites, safe in the knowledge that they were completely free to use? There is, and it’s called the Pattern Directory. You simply find a pattern you like and copy / paste it into your site.
\n\n\n\nYou could stop there, but you could also use this as a way of learning how blocks are constructed. Open up the pattern to see how it’s laid out. What settings were used to create the styling?
\n\n\n\nRight now, the Pattern Directory is quite small. There’s a few hundred patterns to explore, but it could certainly do with some more contributions, and that is what this podcast is all about.
\n\n\n\nThe Pattern Creator is the way to create patterns so that they can be submitted, reviewed, and hopefully accepted into the Pattern Directory.
\n\n\n\nWe’ve got two perspectives on the podcast today from people who come at it from different angles.
\n\n\n\nAna is a self taught WordPress themer and designer who is making use of patterns at Anariel Design, her website building business, and Kelly is an Automattician who has been working with the team building the Pattern Directory and Creator.
\n\n\n\nWe talk about how the Creator works, how you can submit your patterns and what constraints are there for having your submissions accepted.
\n\n\n\nSo, if you’re curious about how patterns can speed up your website building workflow, this episode is for you.
\n\n\n\nUseful links.
\n\n\n\nhttps://wordpress.org/news/2022/03/get-creative-with-the-all-new-pattern-creator/
\n\n\n\nhttps://wordpress.org/patterns/
\n\n\n\nhttps://wordpress.org/patterns/about/
\n\n\n\nhttps://wordpress.org/patterns/new-pattern/
\n\n\n\nAna is @ana_segota on Twitter, and @anasegota on the Make Slack Channel.
\n\n\n\nKelly is @ryelle on both Twitter and the Make Slack Channel.
\n\n\n\nTranscript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast, which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, learning about the new pattern creator.
\n\n\n\nIf you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WP Tavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.
\n\n\n\nIf you’ve got a topic that you’d like us to feature on the podcast, well, I’m very keen to hear from you, and hopefully get you, or your idea featured on the show. Head over to WP Tavern.com forward slash contact forward slash jukebox, and use the contact form there.
\n\n\n\nSo on the podcast today, we have Ana Segota and Kelly Choyce-Dwan. I suspect that you’ve heard about block patterns, but if you haven’t, you’re in for a treat.
\n\n\n\nPatterns are collections of blocks which anyone can assemble for easy reuse at a later date. You can make them as simple or as complex as you like. Style them and save them away. When you’re ready to reuse them, they’re just one click away. It’s a great time-saver .
\n\n\n\nHaving said that, not all of us are great at design, or perhaps we’ve just not had the time to explore how block patterns are created. Wouldn’t it be great if there was a source of patterns which we could use in our WordPress websites, safe in the knowledge that they were completely free to use? There is, and it’s called the pattern directory. You simply find a pattern that you like and copy paste it into your site.
\n\n\n\nYou could stop there, but you could also use this as a way of learning how blocks are constructed. Open up the pattern and see how it’s laid out. What settings we’ll use to create the styling?
\n\n\n\nRight now, the pattern directory is quite small. There’s a few hundred pounds to explore, but it could certainly do with some more contributions. And that is what this podcast is about. The pattern creator is the way to create patterns so that they can be submitted, reviewed, and hopefully accepted into the Pattern Directory. We’ve got two perspectives on the podcast today from people who come at it from different angles.
\n\n\n\nAna is a self-taught WordPress themer, and a designer who is making use of patterns in her website builds. And Kelly is an Automattician who has been working with the team building the Pattern Directory and Creator. We talk about how the creator works, how you can submit your patterns and what constraints are there for having your submissions accepted.
\n\n\n\nSo, if you’re curious about how patterns can speed up your website building workflow, this episode is for you.
\n\n\n\nIf you’re interested in finding out more, you can find all the links in the show notes by heading over to WP tavern.com forward slash podcast, where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Ana Segota and Kelly Choyce-Dwan.
\n\n\n\nI am joined on the podcast today by Ana Segota and Kelly Choyce-Dwan. Hello.
\n\n\n\n[00:04:01] Ana Segota: Hi.
\n\n\n\n[00:04:01] Kelly Choyce-Dwan: Hello.
\n\n\n\n[00:04:02] Nathan Wrigley: Very nice to have you both here. As we always do at the beginning of the podcast, I’m going to give both of you an opportunity to introduce yourselves, to give us a bit of an orientation.
\n\n\n\nIf you’ve listened to the introduction to this podcast, you probably know that we’re going to be talking about the pattern creator. And so it would be important to know why the two guests today are coming on talking about that. So, we’ll take it one at a time. We’ll begin with Ana. Ana, just tell us a little bit about your journey with WordPress and how come it is that you became involved with the pattern creator.
\n\n\n\n[00:04:33] Ana Segota: So, hi Nathan, nice to meet you and thank you for inviting me. So I’m Ana Segota, and I am a themer, and I love creating WordPress themes using block patterns. I always was more as a designer, but I learned to code to be able to create WordPress themes myself, but now having a block patterns is such a relief for me because I can concentrate on design more.
\n\n\n\n[00:05:04] Nathan Wrigley: That’s really nice. Thank you. Yeah. The intention of the tool is to make all of those decisions a little bit easier. So it’s nice, nice to know that in your case, it’s working. So, okay that’s going to be one perspective that we’ve got in the show today. And another perspective comes from Kelly. So Kelly, just spend a moment, tell us who you are please.
\n\n\n\n[00:05:21] Kelly Choyce-Dwan: Sure. So my name is Kelly Choyce-Dwan, also ryelle online. I work at Automattic and I have for over seven years. I started with WordPress in 2009, and I’m now working on the Meta team where my focus recently has been on the pattern directory and pattern creator.
\n\n\n\n[00:05:41] Nathan Wrigley: Now many people listening to this podcast will be very up-to-date users of WordPress. There’ll be using the tools that are shipping all of the time, and they may well have discovered patterns and be using them to great effect.
\n\n\n\nOn the other hand, I suspect that there’ll be a fair amount of people who as yet have not delved into patterns. They may know what they are. They may not. So I’m wondering if we could really just rewind a little bit, make no assumptions about anybody’s knowledge about patterns and just lay out what they are. So it’s a very general question. Either of you feel free to answer it. What are patterns in WordPress and why might you wish to use them?
\n\n\n\n[00:06:24] Ana Segota: So for me block patterns, I like predefined and ready to use layout that you can click or drug and create pages. It’s like a collection of blocks arranged together to help you create different layouts. If you’ve used sometimes page builders, or Elementor templates, for example, it’s the same thing. You can use them on your website. You can adjust them, change the layout, change the colors. And I think they’re very useful.
\n\n\n\n[00:06:59] Nathan Wrigley: Thank you. So they are basically quick ways to build websites. You’re using other people’s predefined layouts. The work, in great measure, has been done for you. You can discover collections of blocks, which are generically called patterns, and you can click on those and import them into your post or page or whatever it might be.
\n\n\n\nSo it speeds things up. I’m curious, for those of you, who’ve never used this before again, how do you actually build them? What’s the process that one might find themselves in, and bear in mind, we might be speaking to users of WordPress who are familiar with page builders, and don’t really find themselves interacting with the WordPress block editor.
\n\n\n\nSo we may need to have a little bit of a description around there. What are we actually doing? How do we create and build patterns?
\n\n\n\n[00:07:51] Ana Segota: Okay. so mostly, I’m building block patterns for the themes. As a background, I first start, with niche, different niche, and what can be useful for that niche. And then I start creating block patterns directly in the editor, where you have all the options of block that you can combine in one block pattern.
\n\n\n\nSo mostly I started with a group block, where I put then columns or cover or images, and start creating different ideas and different layout.
\n\n\n\n[00:08:34] Nathan Wrigley: Are you able to save those, as WordPress currently stands? Are you able to save those and I’ll stay with Ana. Are you able to save those Ana so that they can be reused on other websites. In other words, can you save more time by having your own little collection of blocks, which you then can use on this website over here and this other completely different website?
\n\n\n\n[00:08:58] Ana Segota: Maybe Kelly knows better, the other way, but what I know you can always copy the block you have and paste it on other website. Or you can export it. But not sure if you can save it inside the editor for like a gallery or something. I’m not sure that you can, or if you can do this, maybe Kelly knows that.
\n\n\n\n[00:09:22] Kelly Choyce-Dwan: Well, I know that you can, if you copy the block code into like a code file, the you can register it that way, but it requires code.
\n\n\n\n[00:09:33] Ana Segota: I think, there is no easy way to save it in a gallery for the beginner user, for example.
\n\n\n\n[00:09:41] Nathan Wrigley: At the moment, it feels as though it is the domain of people who are fairly experienced with WordPress. All of the tooling, with things like Elementor that you described, where you, you might have a private cloud of things that you’ve created in the past, and you can log in, and there’s a cloud service attached and you can download those to all of the other websites. We’re not quite at that point yet, although maybe some of the discussion that we’ll have today will revolve around that.
\n\n\n\n[00:10:10] Ana Segota: Yeah, I would love that.
\n\n\n\n[00:10:12] Nathan Wrigley: Yeah, that would be a really nice addition.
\n\n\n\n[00:10:14] Ana Segota: But I think the, pattern creator is doing some kind of saving those block patterns and one place where you can reuse it. But we will come to it.
\n\n\n\n[00:10:24] Nathan Wrigley: That’s okay. We’ll come to that in a moment. Just to say, patterns are collections of blocks and you piece them together, akin to a jigsaw and you build up designs, and style those designs, add images, add forms, add whatever it might be, background, color, padding, and so on, until you’ve got something that you’d like to look off. And at the moment, it probably lives within one WordPress website. But you can copy and paste that over somewhere else, but there’s no sort of cloud functionality.
\n\n\n\nAnd so, to the main conversation today, which is the pattern creator. Just so that you know, the links will be in the show notes to everything that we talk about today. And the pattern creator may well be something that you want to go and play with because it enables you to do a very large amount more than potentially you can do in your normal WordPress website. So, whoever wishes to take this. What is the pattern creator? Hopefully we’ll be providing people with the link so they can find that. That’s all good. But what’s the purpose of it? Why was it built? Why did the WordPress team decide that a tool like this needed to exist?
\n\n\n\n[00:11:33] Kelly Choyce-Dwan: So the pattern creator is a place to go and create patterns to share with anyone who uses WordPress, and it was created to make the process of making a sharing patterns easier. It’s a place that you can go and make a pattern and you know that it can be reused without having to write that code.
\n\n\n\n[00:11:54] Nathan Wrigley: So, at the moment it’s not only is it a place where you can go and create patterns. It’s a place where you can go and discover other people’s already created patterns. And if you’re, if you’re coming to this podcast from another page builder, think about it as rows. You’re essentially grabbing rows from websites or component parts of websites. And so it serves that double purpose. Not only can you create your own, but you can also go and freely download other people’s work. Have I got that right? Have I misstated that?
\n\n\n\n[00:12:25] Kelly Choyce-Dwan: That’s correct?
\n\n\n\n[00:12:26] Nathan Wrigley: So in terms of how the editor works, we need to go to the website, the pattern creator website. And once we’re there, my understanding is that you need a, a wordpress.org account.
\n\n\n\nOnce you’ve got yourself, a wordpress.org account, you can log in and you are presented with something which looks very, very similar to the usual WordPress block editor interface. It’s a little bit more spartan because the menu on the left kind of basically doesn’t exist. So all of those options for posts and pages and what have you are gone. Let’s talk about the design decisions.
\n\n\n\nSo the menu on the left is gone. We’ve got the option to add blocks. Are we just dealing with a subset of the core blocks or can we add any of the core blocks?
\n\n\n\n[00:13:15] Kelly Choyce-Dwan: It is a subset currently, because we don’t have the dynamic content that might be on your website. So we can’t replicate the full experience of using that block. But almost all of the core blocks are available.
\n\n\n\n[00:13:30] Nathan Wrigley: Okay, so you can log in and you can start building out your blocks, or rather, I should say you can start building out your patterns. Then presumably there’s some kind of save process. And if you’re happy with things, can you use this if you chose to do it this way, can you use this as a private repository of your own blocks, that you’re maybe not ready to share with the world? Maybe they have to be kept in a draft state or something like that. Could it be used in that way? I know that’s not the intention. The intention is to have them shareable, but you were to design something and be not entirely satisfied with it, could you keep it there and come back to it at a later date and tweak it?
\n\n\n\n[00:14:13] Kelly Choyce-Dwan: Yeah, totally. You can save things as drafts. Actually, when we were first building it out, one of the ideas was that it could be a private repo for you to put your own patterns in. That isn’t built yet, but it could be in the future.
\n\n\n\n[00:14:26] Nathan Wrigley: So there is a kind of workaround to make it a directory of your own, if you simply save things as draft. But that isn’t the point. The intention is to make it universally available to everybody. And so on.
\n\n\n\nDoes this require an up to date version of Gutenberg on the backend? So just to be clear, it’s like a SaaS product. You’re not installing WordPress anywhere. You are just going to a website and interacting with it. But I’m just curious to know, as Gutenberg is updated and modified and the blocks change, we’re several years in, and there’s been a great deal of change in the way that certain things work.
\n\n\n\nDo you have confidence that everything that you build today will look the same in, let’s say a couple of years time. In other words, do you anticipate that some things may break in the future or are you trying as hard as possible to mitigate against that?
\n\n\n\n[00:15:18] Kelly Choyce-Dwan: Well, I hope it won’t, but the pattern creator is using always the stable version of Gutenberg. So it will always be up-to-date when you’re creating patterns. Patterns created a few months ago, we’re created with an older version of Gutenberg, but between backwards compatibility block transformation, Gutenberg is trying not to break your content too. So I’m fairly confident that things will continue to work. If there are patterns that do brake, we have a reporting mechanism for reporting that.
\n\n\n\n[00:15:51] Nathan Wrigley: So it’s just Core blocks that we need to worry about. And it’s a subset of the Core blocks. Now, I’m looking on the interface at the moment. There’s the option for me to add a title? Obviously that’s just for the purposes of knowing what the pattern is that I’m saving somewhere. And then I can, in the normal way, click the little plus icon and I can add blocks as I choose. Put a group in, put some columns in and so on, and fiddle with those blocks just as I would do on my regular WordPress website.
\n\n\n\nAnd I’ve got the list view where I can see the stack of all of the different things that. I’ve created. And then on the right-hand side, you’ve got a title and a description. Do both of those serve the purpose of showing to somebody, once it’s been submitted to the pattern directory, which we’ll get onto in just a moment. Those titles and descriptions would give the people, browsing the pattern directory, some orientation as to what it was about and what it was designed to achieve.
\n\n\n\n[00:16:46] Kelly Choyce-Dwan: Yeah, that’s right. The title is the pattern title, and it’s the same when you’re in that little sidebar and the top title, they’re just two inputs for the same thing. Good title would describe what the pattern is, like one of the pattern contains, what it should be used for.
\n\n\n\n[00:17:01] Nathan Wrigley: Then in order to presumably aid search on the other end in the pattern directory. Currently we have six categories. There’s no option to create categories of your own. At the minute we look like we’ve got buttons, columns, gallery, header, images, text, and then there’s the option to add in keywords, maximum of 10.
\n\n\n\nAgain, is this all just to help the taxonomy of it, to help assist people on the other side to locate things which you’ve got buttons in and specifically columns and galleries and so on? Is that the That’s the sole purpose of that.
\n\n\n\n[00:17:34] Kelly Choyce-Dwan: That’s right. And, they’re also used, those are the same properties that are used in WordPress Core when you’re registering patterns.
\n\n\n\n[00:17:41] Nathan Wrigley: So I could spend hours happily building out my new blocks and constructing them up into patterns and saving them away. And once I’ve got something that I’m happy with, there’s a blue submit button at the top right hand corner in the same way that you would have publish in WordPress typically, but this is submit.
\n\n\n\nWhat is the process, what’s going on there? What is the list of things which happen after that? So I’m thinking in terms of, I just clicked submit, but presumably at that point, all sorts of other things are set in motion. Maybe it’s sent to a particular team and people have to authorize things and check that it doesn’t break any guidelines. And that might be a long list of things that go on in the background there.
\n\n\n\n[00:18:24] Kelly Choyce-Dwan: Yeah. So when you submit a pattern, it asks you a few things more just to make sure you filled out all of your details. there are a few things that we’ll check for automatically, making sure you’re using a decent title. We’ve had a few patterns that are just called my pattern, which isn’t helpful for other people. So we detect things like that.
\n\n\n\nSo after the automated checks, it does get submitted as pending. So it does not automatically approved yet. And there is a pattern review team that will look through the pending patterns and publish things that are valid. Most things do get published. So you probably would get published within a day or two.
\n\n\n\n[00:19:02] Ana Segota: It’s mostly hours or a day. I submitted here, so top, one day
\n\n\n\n[00:19:08] Nathan Wrigley: Yeah, it’s really quick. A big gripe about the, let’s say the theme review team or the plugin review team was that there was quite a long wait, sometimes very long. There’s a lot more complexity, I guess, within a theme, a lot more code floating about. So at the moment. if you submit something, as of, let’s say May 2022, you’re very likely to have a decision fairly quickly.
\n\n\n\nIn terms of that being authorized, what are the guidelines? What are the kinds of things that are allowed and disallowed? In other words, so you mentioned that a good title, a good descriptive title is going to set you on the road to having its, authorized and put on the pattern directory.
\n\n\n\nAre there any other guidelines that need to be, you need to be mindful of? Not only in terms of getting it submitted, but things that you don’t want people to submit because it contravenes certain rules or regulations.
\n\n\n\n[00:20:03] Ana Segota: I think the most important part is to combine multiple blocks together, so not just to use one block and post it. So multiply blocks together and create some interesting and useful layouts. So maybe front design part and also something that can be creative and useful to the users. Also to highlight the capabilities of the blocks they contain and provide a starting point to customize the content.
\n\n\n\nGood pattern book needs to be, has a well-defined purpose too. And for don’ts, maybe to avoid to design patterns for a single theme. So to think about it to be used in different websites. Not to create a pattern that is like a full page. Or just a simple pattern that is using a paragraph. And I think you need to use photos from the gallery there. You can’t import your photos or from some other website, and that’s probably it.
\n\n\n\n[00:21:11] Nathan Wrigley: So the photos are coming in from, Kelly, maybe you can help us out here. Are they coming in from Openverse?
\n\n\n\n[00:21:18] Kelly Choyce-Dwan: They are yeah. It’s all CC0 photos from Openverse. So they’re able to be used by anyone without any, without worry about crediting people.
\n\n\n\n[00:21:27] Ana Segota: Yeah, that’s very helpful.
\n\n\n\n[00:21:30] Nathan Wrigley: Another podcast episode altogether isn’t it? The whole Openverse project’s fabulous. Yeah. so obviously there’s constraints in terms of the do’s, you know, it needs to be usable on multiple websites, and so on, just as Ana said, but there’s some certain don’ts as well. We’ve prevented the ability to upload images by just using Openverse images, which is great.
\n\n\n\nBut also, I guess that would be in terms of the text that you write into paragraph or heading fields, there would be a requirement for it to be, let’s call it family friendly. You know, we don’t want anything which might cause anybody any hassle and presumably that’s a trip wire which the team would immediately reject it on.
\n\n\n\nSo, okay. Let’s let’s imagine that we’ve built this fabulous pattern. It’s absolutely hit the guidance on the head and it’s been approved. What then? Where does it go? Where does it live? How can other people find it?
\n\n\n\n[00:22:24] Kelly Choyce-Dwan: So it’s in the pattern directory, which is just wordpress.org/patterns. You can use that website to search through patterns. Once you found a pattern that you like, you’re able to use it in your own website, just by simply copying it. And there is a copy button on each pattern that you can use to copy the code for it.
\n\n\n\nAnd if you just paste that straight into your editor, you have that pattern.
\n\n\n\n[00:22:48] Nathan Wrigley: So, you go to the pattern directory, presumably you would then search and filter against the things which you created when you were submitting your pattern. And then there’s a simple copy and paste button. You copy it. It’s in the clipboard of your computer and you just go over to your website and in an empty block, there’s no sort of container or wrapper that you need to stick it in. You literally just paste it into a brand new empty text block and all will work?
\n\n\n\n[00:23:18] Kelly Choyce-Dwan: Yep.
\n\n\n\n[00:23:19] Ana Segota: Yeah.
\n\n\n\n[00:23:19] Nathan Wrigley: Are there any gotchas there? Because that process, whilst it’s not necessarily quite as optimal as the cloud that we were talking about earlier, where you could actually see it within your WordPress website, which I guess ultimately would be an easier experience?
\n\n\n\nDoes it always work? Are there any situations where copying and pasting that code has unexpected consequences. I don’t mean things breaking. I just mean that the styling, for example, something that the theme brings to bear might make things look peculiar and not quite how you intended.
\n\n\n\n[00:23:51] Kelly Choyce-Dwan: Yeah, I think that’s possible because it is, I mean it uses the Core blocks. So if your theme styles the core blocks minimally, maybe, you’ll probably be fine, but if your theme is doing anything really creative with some of the blocks, I suppose you could have some trouble where a quote that you copied from the pattern directory looks totally different on your site.
\n\n\n\n[00:24:12] Ana Segota: But if you are using a full site editing theme, I think you are good with.
\n\n\n\n[00:24:17] Nathan Wrigley: It should just work. Yeah. Do you know if there’s any intention to bring any of this kind of functionality into WordPress Core. And what I’m meaning by that is that I could hook up my let’s say wordpress.org account to my website. And then I could create patterns inside my website and then authorize them to be submitted to the pattern directory.
\n\n\n\nI feel like that might be quite a useful workflow at some point in the future, because then you’re not necessarily having to go out and go to a different website in order to create the patterns and publish them and so on. And equally, I wonder if in the future there are any plans to make it so that I can pull these patterns in, in the same way that we described that page builders like Elementor and so on, have their cloud templates and so on, and so forth.
\n\n\n\n[00:25:11] Kelly Choyce-Dwan: Yeah, I think the second is much more likely than the first. So if you were to create a pattern on your own website. Uh, you might be using any number of blocks that are not Core blocks. So I don’t know that creating a pattern on your website and pushing it up is on the roadmap at least, because there’s a lot more gotchas. We can’t control the media that you’re using. Like we’re able to use Open verse images on the pattern creator.
\n\n\n\nSo there’s a lot more, a lot more like gotchas that way. But, having an ability to pull patterns from the pattern directory on wordpress.org into your own site. I do think that that is probably going to happen soon.
\n\n\n\nAlready, you can call out, well already in WordPress 6.0, you’ll be able to register pattern slugs when you’re building a theme, and then it will pull down those patterns from the pattern directory. So you can pull patterns like that.
\n\n\n\n[00:26:06] Nathan Wrigley: Yeah. That’s, that’s interesting. So imagine that I’ve submitted one of my patterns. I’m very happy with it, but a year or two passes and I now for goodness knows what reason, I now don’t wish that pattern to be part of the directory. I’m wondering if either of you have any knowledge about whether things can be removed or once I’ve submitted it, is it up there for life? And I have essentially given it over to the community in perpetuity.
\n\n\n\n[00:26:36] Kelly Choyce-Dwan: You can revert your pattern to draft, if you want to take it down. You can also trash it. We’re not tied to always supporting things the way that the theme and plugin directories are because there isn’t really as much of a tie to your content and this thing on wordpress.org, because once you copy a pattern down, you have it, you don’t need to sync back up with the parent. So we don’t need to, we don’t have the same issues of keeping something around.
\n\n\n\n[00:27:00] Nathan Wrigley: Yeah, so you can curate that yourself. You can just, if you like return it to a draft status. So there’s a permanent connection between the wordpress.org repository that I can access with my user login and password, and the pattern being published. In other words, when I clicked submit, it’s not just taken from my submission and put into some other SaaS, if you like.
\n\n\n\nSo my expectation was that when I submitted it, much in the same way that I was submitting a form on a website, that form can then live somewhere else. You know, the form submission can come to me via email. I can’t rescind that form being sent. But in the directory the submit button and the draft status button is directly connected to whether it’s on the pattern directory.
\n\n\n\nSo if I click draft again, it will immediately, without any human supervision, it will suck it out of the directory and mean that it’s no longer there.
\n\n\n\n[00:28:03] Kelly Choyce-Dwan: Yeah, that that’s correct.
\n\n\n\n[00:28:05] Nathan Wrigley: Yeah, I really didn’t understand that. I just assumed that I was submitting it rather like a form. Somebody would inspect it, check it into another platform. So that’s kind of good to know.
\n\n\n\n[00:28:15] Kelly Choyce-Dwan: Yeah. It also means that you can edit. So if you make your pattern and then you decide that you actually, you’ve submitted it, it’s been a week though. And you don’t like the color of the button. You can make that change. It’ll submit it back to pending, and it has to go through that review again. But, once it’s published, your pattern will have the new change now.
\n\n\n\n[00:28:34] Nathan Wrigley: Okay. So we have to go through the process. Do you have any insight into how popular patterns have become over time? I mean, I still feel that the editing experience for proprietary page builders is something that people are keen for Gutenberg to have. You know, in other words, what you see is literally what you get.
\n\n\n\nThere’s no ifs or buts, it’s just exactly the same on the backend as it is on the front end. And I feel that a lot of people are not moving over to Gutenberg because that experience is not there yet. So, this one may be for Kelly, it may be for Ana. Ana, you might like to draw on, you know, your experience or maybe your friends and colleagues. Is it as usable yet? Are patterns as useful to you as your page builder that you may have used in the past yet? Or if we still got a way to go, what are your, what are your instincts on that?
\n\n\n\n[00:29:25] Ana Segota: From my point of view, I think the block patterns are now really well made and they can be really useful. And I think they are mostly easier to use them. So for the user’s point of view, but they come more to the problem where we are starting to use templates, for example. Full site editing and templates. Block patterns are I think easiest part from the whole full site editing,.
\n\n\n\nFrom my experience, mostly they like block patterns but, I think we are still in early stage because there is not a lot of themes that are full site editing themes. And sometimes we also have older themes that we are updating with block patterns, but it’s like a mix of old way and new way. So I think when we start doing more full site editing themes, it will get easier and user will get to know znd to accept it more.
\n\n\n\nBut I think block patterns are really useful from the user side, but templates are a bit tricky now, I must say, a bit confusing because we have a two editors now, like site editor and normal editor that they know from past. And they’re asking why I see now here block pattern, but in the old editor I need to click on the edit template to edit the template. It’s a bit tricky and confusing at the moment I must confess.
\n\n\n\n[00:31:00] Nathan Wrigley: We’re on the cusp of WordPress 6.0 being released, and as each different, a new release comes around, there is more being added and the complexity sometimes goes up and hopefully at some point the complexity will go down again and be more straightforward to use.
\n\n\n\nI guess that one of the biggest wins of using patterns and the pattern directory, which you would submit things to with the creator, is that all of this is just free. It’s completely freely available. You can use it in any which way you’d like, there’s no constraints over how you might use it. And if we rewind the clock about, oh, I don’t know, let’s go for about 12 or 13 years.
\n\n\n\nI imagine that the plug-in directory felt like a similar thing, you know, you would submit your plugin and within a few hours, somebody would say yes. That’s great, thank you very much. We now know that WordPress has 50,000 plus plugins. The directory whilst being very useful is quite hard, it’s very difficult to track things down. We’ve got certain things being recommended because they’re popular and it may be hard for people to have their bits and pieces discovered.
\n\n\n\nI’m just wondering, Kelly I’ll fire this one at you. I’m just wondering if in the future there are plans to make it so that as you submit patterns, there’s maybe more options around curating it, more taxonomy, terms, greater ways of being able to search and discover things. Because at the moment, it’s easy.
\n\n\n\nThere’s a handful of patterns, well, that’s not quite true, but you get point. There aren’t 50,000 of them. But in the future, when this takes off, I could see there being literally hundreds of thousands of patterns. And at that point it’s going to be extremely difficult to separate the ones that you would like from the ones which are just there in front of you, but you don’t necessarily feel able to use. So really I’m just wondering how that may be curated in the future. Any roadmap plans for that?
\n\n\n\n[00:33:00] Kelly Choyce-Dwan: Yeah. you’re right there are, what did you say, 50,000 plugins?
\n\n\n\n[00:33:03] Nathan Wrigley: Yeah,
\n\n\n\n[00:33:04] Kelly Choyce-Dwan: Yeah, there’s 400 patterns.
\n\n\n\n[00:33:06] Nathan Wrigley: Yeah, yeah.
\n\n\n\n[00:33:07] Kelly Choyce-Dwan: So a little different. I don’t know that there’s any concrete roadmap for what the future of this directory might look like. There are some discussions about whether there should be different categories, like buttons, columns, taxonomy. There’s questions about how we should handle patterns that are more for site building versus just content patterns. So I do think that this is all very much still like to be decided, and really if anyone has opinions, I’m sure we’d love to hear them.
\n\n\n\n[00:33:39] Nathan Wrigley: Yeah, we’ll get onto that actually now because that feels like a good point. So obviously this is being built out in the open. The pair of you have obviously taken a great interest in it, but it may be that people listening to this, this is new to them. And they think that they would like to play with this a little bit, become involved with the team.
\n\n\n\nSo maybe again, I’ll direct this one at Kelly first off. Are there any ways, better ways where people can get involved in the project of the directory or the creator? Where are the best places to go and hang out?
\n\n\n\n[00:34:12] Kelly Choyce-Dwan: If you want to have feedback about the future of the pattern directory or if you just want to report that something’s not working. The project is on GitHub. It’s at github.com/wordpress/patterndirectory.
\n\n\n\n[00:34:27] Nathan Wrigley: So that’s the best place to go if you wish to find out about becoming involved. Ana, just wondering about your experiences of being involved with this. Have you got any, any insights? Is there a thing that you found the most useful? A, I don’t know, a Slack channel or a website where people are helping each other out. A group of some kind, maybe a community online somewhere where this is all happening?
\n\n\n\n[00:34:50] Ana Segota: I was in contact per Slack, with Anne McCartney also and, mostly Slack and Twitter, but yeah, mostly Slack or Github, yeah.
\n\n\n\n[00:35:01] Nathan Wrigley: Now, I know that neither of you will be able to answer this question directly, but the theme repository and the plugin repository, they feel like there’s no way that they are going away. They’re going to be here for the long-term. You know, I can imagine decades from now, they’ll still be in existence. Do you both have confidence that this journey that we’ve taken on where blocks and patterns are becoming the new, the new way of creating quick and easy websites. Do you feel confident that this is the way it’s going to be done? You know, that we ought to sail our ship in this direction?
\n\n\n\nYour long-term thoughts really on whether or not this is the way it’s going to be done in the future.
\n\n\n\n[00:35:40] Ana Segota: I hope so. I really hope so. I think this way is, better way of making, for example, I am in theme business, so, it’s easier to create themes. Especially to offer easier way of using themes to users. So finally theme can be a design for me, and that’s a really big step in the right direction. So I really hope it will stay. And also be better with the time and more easier to use.
\n\n\n\n[00:36:12] Nathan Wrigley: Thank you. And Kelly.
\n\n\n\n[00:36:14] Kelly Choyce-Dwan: Yeah, I do think that this is the way forward. I think that using blocks and making patterns is really only going to become more, more standard. Easier to use. And so I think that this is going to be the way to make websites
\n\n\n\n[00:36:28] Nathan Wrigley: Yeah. Just one last quick thought. I mentioned something similar earlier and Ana talked about it, I’m going to direct this one at you, Kelly, if that’s all right. I don’t know what your experience is with other website building tools. And we mentioned page builders, such as Elementor and, I just wondered what your thoughts are on where the user interface is and the user experience is at the moment.
\n\n\n\nMaybe you’ve got some insight into that. Maybe you don’t, but I just wondered whether you thought that it was yet at a point of maturity. And that kind of ties into the question I’ve just asked about whether it would be widely adopted, because it feels like there’s a big holdout of people the moment who simply cannot make the move because the experience as yet doesn’t have that, it’s exactly the same on the front end, as it is on the backend. And Ana, I think you just said, Yeah in the background. You can identify. You’ve committed, you’ve jumped over and you’ve made that journey and put the investment of time into…
\n\n\n\n[00:37:24] Ana Segota: Yeah, but it takes a lot of challenges, yeah. Because I get the input from the user side and I also used Elementor before to see how it works. And I must say it’s still a long way. But, what is most confusing now to the users, what I said before, also, those two editors and two different phase. We now have again templates that you can edit.
\n\n\n\nAnd they’re a bit confused. Like, okay, I go on out to edit the template and I saved it and now it’s applied to all my pages and now you need to explain it that they need to refresh it and pull it back. And it’s a bit confusing. So we don’t have one editor where you can do all the things. For example, you come to one editor and click, for example, to choose a layout and this layout is there and you can edit it and that’s it. Yeah, it’s a bit struggle for now.
\n\n\n\n[00:38:25] Nathan Wrigley: I do wonder if that struggle, and I’m going to see what Kelly makes on this, I do wonder if that’s going to be for a little while into the future, if that’s going to be a limitation in terms of adoption, is the fact that there are difficulties. There’s a lot of learning which needs to take place to wean you off those tools and, whilst the WordPress Core way of doing blocks and patterns and so on is free, widely available, done in the open, open source and all of that kind of stuff. I wonder if the adoption is going to be stifled because of the constraints that Ana just mentioned. What do you think about that?
\n\n\n\n[00:39:04] Ana Segota: I think it depends also on us, on themers a lot. How we will implement this and make it easier for the users. And we also need to educate now the users, how they can use it and make it as easier as possible. And sometimes there’s not that easy because you need to follow updates and to do the updates all the time and to educate people about it.
\n\n\n\nBut I think it’s a good step in the right direction. And I think with the time and with the education people will adopted it yeah. Just by creating a pages using just block pattern it’s a really a big step. And it’s a great thing. You can really create most everything with block patterns without using templates for example.
\n\n\n\n[00:39:54] Nathan Wrigley: Yeah, I think people just need time, the inspiration to get into it…
\n\n\n\n[00:39:59] Ana Segota: It’s a new, it’s a new thing and you always need time to learn something new.
\n\n\n\n[00:40:03] Nathan Wrigley: That’s right. We actually interviewed Courtney Robertson from the Learn initiative last week. And there’s an awful lot of content. And I think that’s maybe a piece that was missing in the past, the ability to go and find video tutorials, which answer the exact question that you’re looking for.
\n\n\n\nKelly, can I put that one to you? Is it basically the same question? You said that you hadn’t got a great deal of experience with page builders and so on, but I’m just wondering if you had any intuitions around there, whether or not the UI and the UX is, is everything that you guys had hoped it would be, or do you feel that there’s still quite a lot of work going through WordPress six and seven and maybe even, eight.
\n\n\n\n[00:40:39] Kelly Choyce-Dwan: Yeah, I haven’t used page filters. I am definitely a pretty vanilla WordPress user. But I have been, you know, working with the site editor and I can see that it is a little confusing still. I do think that it needs to be iterated on, but I think that the future is going to be good.
\n\n\n\nI think the plans are there and it’s constantly getting better. So I’m very positive about it. Yeah.
\n\n\n\n[00:41:02] Nathan Wrigley: Thank you. Okay, just to wrap up, if people have listened to this podcast today and they would like to get in touch with you and make contact and use your expertise. What’s the best way of getting in touch with you? It could be a Twitter handle could be an email address, or it could be nothing. You might wish to share nothing at all, but I’ll start with Ana. What’s the best way to get in touch with you, Ana?
\n\n\n\n[00:41:24] Ana Segota: Twitter, or Slack or email. It’s all good. Maybe you can add a later?
\n\n\n\n[00:41:31] Nathan Wrigley: Yeah, I will definitely add your Twitter and Slack into the show notes. And same question to you, Kelly. What’s the best way to get in touch with you?
\n\n\n\n[00:41:40] Kelly Choyce-Dwan: You can find me on Twitter, Ryelle, R Y E L L E or on wordpress.org Slack. I can also chat there.
\n\n\n\n[00:41:49] Nathan Wrigley: Okay, Ana and Kelly, thank you so much for talking to me on the podcast today, and I appreciate you giving me an hour of your time. Thank you very much, indeed.
\nWell, the week started the release of WooCommerce 6.5 and ended with a 6.5.1 bug fix release. Between all of that, WooCommerce Blocks 7.6 was also released.
\n\n\n\nOver on Do the Woo, we had a conversation about the upcoming release of WordPress 6.0. The Woo Roundtable, consisting of Ronald Gijsel, Robbie Adair, Robert Jacobi, and Tammie Lister dove in to offer some insights about 6.0 and how WooCommerce plays into it.
\n\n\n\nThen Ronnie Burt from Sensei LMS and Automattic shared his extensive experience in the wider education space and his journey to move into the WordPress ecosystem, and LMS space:
\n\n\n\n\n\n\n\n“And so when I think about democratizing education, I think about how do we help [provide] the best content [so the] best learning experiences bubble to the top and be found.”
A little bird told me about a drop in the WordPress market share. Or actually, a Tweet from Joost de Valk. As a result I had to add my small take to the influx of reaction we have seen. It\'s short!
\n\n\n\nI think we just need to wait and see what shakes out. It\'s too early to say if this is a new trend.
\n\n\n\n\n\n\n\n“…I am not losing any sleep over that number right now. To be fair, depending on your own stakes, you may feel differently. And trust me, there are some interesting insights that Joost shared in the post, as well as others that are either agreeing with or serving a rebuttal. And if you dare go down that rabbit hole, well, good luck.”
Trust me, I didn’t spend much time on my response for several reasons:
\n\n\n\n\n\n\n\n\n\n\n\n“I have had touchpoints in the technical space for over 3 decades. If I was someone that could predict what came next for any specific technology, or 100% understood a lot of the ups and downs, well, maybe I wouldn\'t be rich but I would sure have a lot to talk about.”
\";s: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 May 2022 21: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:8:\"Bob Dunn\";s: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:87:\"WPTavern: How To Start Testing Your WordPress Code With the Pest PHP Testing Framework\";s:7:\"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=134402\";s:7:\"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:97:\"https://wptavern.com/how-to-start-testing-your-wordpress-code-with-the-pest-php-testing-framework\";s: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:9024:\"
We can all agree that WordPress has come a long way since its beginning and that it grew into something a lot more than blogging software.
\n\n\n\nAt its core, it’s still a content management system (CMS), but with over 59,000 plugins in the wordpress.org directory, you can customize it to be much more.
\n\n\n\nThe reason for its popularity is its low entry barrier for both content creators and developers. Sometimes this comes with a cost. It’s no secret that WordPress has a bad reputation when it comes to development. It has a lot of legacy baggage and die-hard rules that prevent any backward compatibility breaking change when it comes to PHP code (Gutenberg is another story I won’t get into).
\n\n\n\nThat legacy PHP code is often used by the developers that are starting to enter the world of programming, and the issue with that is they can learn some bad programming patterns. That in turn means they will reuse the poorly written code, increasing the amount of bad code in the world.
\n\n\n\nThis is where WordPress gets its bad reputation in the developer community.
\n\n\n\nBreaking the cycle
\n\n\n\nSo how can we break this cycle of bad code? By teaching new developers how they should write good code. One example of teaching new developers (but also old ones that are still clinging to the ‘WordPress’ way of doing things) is by writing tutorials.
\n\n\n\nAnother way is to encourage them to use tools that can help them write better code.
\n\n\n\nI’m currently involved in the work which aims to release the new version of the WordPress Coding Standards, a set of rules used for the PHP_CodeSniffer tool that will let you know if your code has some potential issues (security, best practices, code style).
\n\n\n\nAnother tool that I’ve recently developed is a package that will help developers set up WordPress integration tests that use the Pest testing framework.
\n\n\n\nOk, so why do we need this new tool?
\n\n\n\nThe main motivation behind creating this package is to encourage more people to write tests for their code, especially plugin developers.
\n\n\n\nA lot of developers in the WordPress community go with the mantra: I can see that it works because I’ve tried it out in my browser. That’s OK, but there are issues with that.
\n\n\n\nFirst, it’s time-consuming. Every time you make some change, you need to make sure it works, but also that you didn’t break anything.
\n\n\n\nSecond, people make mistakes. We are not foolproof, and code may be misused in ways you never thought possible. You would be amazed at how creative people can be when writing code.
\n\n\n\nAutomated tests are quick and can help you in testing various cases that will happen when you execute your code.
\n\n\n\nYou test for the intended behavior (happy path), and in a quick way, you can add examples of how your code can be used in a way you didn’t intend it to be used (unhappy path).
\n\n\n\nIt also safeguards your code from regressions. A code regression is when you unintentionally break one part of your code by adding new code.
\n\n\n\nThe problem with tests set up so far
\n\n\n\nTesting in WordPress is not a new thing. And it’s not like you couldn’t set up tests for your code before. There are amazing libraries out there that will help you set everything up like wp-browser.
\n\n\n\nBut the problem is that the setup procedure is often clunky.
\n\n\n\nYou need to set up a separate database for tests, and you need to run certain scripts, then change files to make it all work.
\n\n\n\nLet’s face it, it’s not a straightforward thing to do, and developers are by nature lazy creatures (that’s why we write code to do things for us ![\"?\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f604.png\")
).
The aim of the wp-pest integration test setup is to eliminate all that extra work.
\n\n\n\nHow to set it up
\n\n\n\nIn order to set it up, your project must use Composer. It’s a de-facto standard way of adding packages to your code.
\n\n\n\nIn your terminal type
\n\n\n\ncomposer require dingo-d/wp-pest-integration-test-setup --devAfter you’ve downloaded the package and its dependencies you can set up the theme tests by typing
\n\n\n\nvendor/bin/wp-pest setup themeOr, in the case you want to set up tests for your plugin, you can write
\n\n\n\nvendor/bin/wp-pest setup plugin --plugin-slug=your-plugin-slugOptionally, you can provide a --wp-version parameter, to specify which WordPress version you’d like to test your code on.
In the background, a WordPress instance will be downloaded, and an in-memory database will be set up, along with two examples of tests that you can run.
\n\n\n\nThen, running either
\n\n\n\nvendor/bin/pest --group=unitor
\n\n\n\nvendor/bin/pest --group=integrationwill run the tests.
\n\n\n\nThe beauty of Pest is that its syntax is developer-friendly. It has amazing documentation and great syntax. Let’s look at a simple example. Say you are registering a custom post type called ‘Books’:
\n\n\n\n<?php\n\n/**\n * Plugin Name: Test plugin\n * Desctiption: Test plugin\n * Version: 1.0.0\n * License: MIT\n */\n\nfunction test_plugin_register_books_cpt() {\n $args = array(\n \'label\' => esc_html__( \'Books\', \'test-plugin\' ),\n \'public\' => true,\n \'publicly_queryable\' => true,\n \'show_ui\' => true,\n \'show_in_menu\' => true,\n \'query_var\' => true,\n \'rewrite\' => array( \'slug\' => \'book\' ),\n \'capability_type\' => \'post\',\n \'has_archive\' => true,\n \'hierarchical\' => false,\n \'menu_position\' => null,\n \'supports\' => array( \'title\', \'editor\', \'author\', \'thumbnail\', \'excerpt\', \'comments\' ),\n );\n \n register_post_type( \'book\', $args );\n}\n \nadd_action( \'init\', \'test_plugin_register_books_cpt\' );\nAfter running the setup command that adds an example, a test called BooksCptTest.php would look like this:
<?php\n\nnamespace Tests\\Integration;\n\nbeforeEach(function () {\n parent::setUp();\n});\n\nafterEach(function () {\n parent::tearDown();\n});\n\ntest(\'Books custom post type is registered\', function () {\n // We can use assertions from PHP_Unit.\n $this->assertNotFalse(has_action(\'init\', \'test_plugin_register_books_cpt\'));\n\n $registeredPostTypes = \\get_post_types();\n\n // Or we can use expectations API from Pest.\n expect($registeredPostTypes)\n ->toBeArray()\n ->toHaveKey(\'book\');\n});\nRunning vendor/bin/pest --group=integration gives us the following output:
Installing...\nRunning as single site... To run multisite, use -c tests/phpunit/multisite.xml\nNot running ajax tests. To execute these, use --group ajax.\nNot running ms-files tests. To execute these, use --group ms-files.\nNot running external-http tests. To execute these, use --group external-http.\n\n PASS Tests\\\\Integration\\\\BooksCptTest\n ✓ Books custom post type is registered\n\n Tests: 1 passed\n Time: 0.14sConclusion
\n\n\n\nAnd just like that, you have the ability to run WordPress integration tests in your theme or plugin. Tests are amazing because not only are they safeguarding us from mistakes, but they also force us to write clean and testable code. This is especially true for plugins that have complicated logic or are communicating with third-party APIs.
\n\n\n\nWriting tests for such a codebase will force you to think about what your code architecture looks like so you can easily write automated tests – not to mention the time and money you’ll save from not having to manually test everything.
\n\n\n\nIf you think this is something you might benefit from, feel free to use it, and star the repository on GitHub.
\n\n\n\nHopefully, this will encourage more WordPress developers to use tools that will enhance their coding skills.
\";s: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 May 2022 18:25: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:13:\"Denis Žoljom\";s: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:125:\"WPTavern: Online Meetup: WordPress NYC to Host Series on Modern, Privacy-Respecting Analytics and Leveraging First-Party Data\";s:7:\"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=134464\";s:7:\"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:134:\"https://wptavern.com/online-meetup-wordpress-nyc-to-host-series-on-modern-privacy-respecting-analytics-and-leveraging-first-party-data\";s: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:3125:\"One of the positive effects of the COVID-19 pandemic is local meetups are more frequently broadcasting their events online, giving people outside the immediate area the opportunity to attend and learn new skills. Searching meetup.com for WordPress, filtered to show Online Events, will show upcoming events that anyone can attend.
\n\n\n\nWordPress NYC is hosting an interesting new six-part series on analytics beginning this week on Thursday, May 19, at 7PM EDT. Co-organizer Victor Ramirez will kick it off with a workshop titled “The Product & Marketing Data Landscape.” Attendees will get an overview of the current WordPress analytics landscape. Subsequent events will cover how to make a tracking plan, how to migrate to open source tracking options (while respecting privacy), and how to leverage WordPress data to improve user experiences.
\n\n\n\nRamirez is the lead product analytics engineer at The Knot Worldwide and also runs a WordPress agency on the side.
\n\n\n\n“I was inspired because product analytics has been my job for two years,” Ramirez said. “It’s one of the hottest roles in technology everywhere except WordPress.”
\n\n\n\nDuring the workshop he plans to demonstrate the benefits of using Rudderstack, an open source customer data pipeline tool, and Avo workbench, a data governance platform, comparing those to private enterprise options. The schedule for the series includes weekly presentations through June 23:
\n\n\n\n- May 19: The Product & Marketing Data Landscape
- May 26: Tracking Plans as the Lynchpin for Success
- June 2: Goodbye Google, Hello 1st Party Data
- June 9: Privacy, Performance, 3rd Party Integrations
- June 16: Build Dashboards & Reporting in Minutes not Weeks
- June 23: Leveraging Data for Enhanced User Experiences
The series will introduce attendees to the concept of collecting first-party data (as opposed to third-party data) and learn how to create better, privacy-respecting experiences for consumers, instead of “targeting” them with unwanted messages.
\n\n\n\nIf you’re using WordPress for a product or service, this workshop may give you a new way to think about consumer data collection for your business. The event is free and the link to attend online will be visible for those who sign up to attend.
\";s: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 May 2022 17:34: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: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:85:\"WordPress.org blog: WordPress 6.0 Release Candidate 3 (RC3) Now Available for Testing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12866\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-3-rc3-now-available-for-testing/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4194:\"WordPress 6.0 is scheduled for release next week on May 24, 2022! This RC3 release is the final opportunity for you to test and help contribute to making the 6.0 release great.
\n\n\n\nYou can view changes since the RC2 release via Gutenberg and Trac.
\n\n\n\nInstalling RC3
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you install RC3 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 RC3 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the release candidate (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, RC1, or RC2 on a case-insensitive filesystem, please use the following command:
\n\n\n\nwp core update --version=6.0-RC3
Plugin and Theme Developers
\n\n\n\nAll plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.0 RC3 and update the “Tested up to” version in their readme file to 6.0 this week. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24.
\n\n\n\nReview the WordPress 6.0 Field Guide, for more details on this release.
\n\n\n\nReview additional information on the full 6.0 release cycle.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail upcoming changes.
\n\n\n\nTranslate WordPress
\n\n\n\nDo you speak a language other than English? Help translate WordPress into more than 100 languages.
\n\n\n\nHow to Help Test WordPress
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\n\n\n\n\n
RC3, An (Almost) Final Haiku
\n\n\n\nIt’s near time for six
The reward is the journey
Just one week to go
\n\n\n\n
Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat.
\";s: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 May 2022 16:39: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:11:\"Dan Soschin\";s: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:82:\"Do The Woo Community: WordCamp Europe 2022 with Takis Bouyouris and Taeke Reijenga\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=71671\";s:7:\"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:32:\"https://dothewoo.io/episode-223/\";s: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:396:\"Takis Bouyouris and Taeke Reijenga, part of the organizing team for WordCamp Europe, joins us in a conversation all about WCEU.
\n>> The post WordCamp Europe 2022 with Takis Bouyouris and Taeke Reijenga appeared first on Do the Woo - a WooCommerce Builder Community .
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 17 May 2022 09:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:85:\"WPTavern: How The Welch News Uses WordPress To Keep Local News Alive in West Virginia\";s:7:\"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=134197\";s:7:\"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:96:\"https://wptavern.com/how-the-welch-news-uses-wordpress-to-keep-local-news-alive-in-west-virginia\";s: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:13172:\"For 95 years, the people living in the McDowell County coalfields have depended on The Welch News for local coverage of important events. The county sits at the southernmost point of state, with a declining population of 18,363 and a median household income of $27,682.
\n\n\n\nIn the 1950’s, at the apex of the mining industry’s economic influence, McDowell County had close to 100,000 people living there. They mined the coal that built much of the infrastructure for American cities. After the industry became more mechanized and many left to find work elsewhere, the community began to deteriorate, drugs got a foothold, and many local kids are now raised by their grandparents. Property taxes evaporated, as a large number of homes are on homestead exemption, which further lowers property taxes for those who are 65+ or considered disabled.
\n\n\n\nThe Welch News remains in the county as a unifying force that the dwindling populace relies on to stay connected and informed. Publisher Melissa Nester often says she learned how to read by reading the Welch News. Three years ago, she purchased her local newspaper to keep it from shuttering.
\n\n\n\n“Our previous owner made the decision to close the newspaper at a point we felt we were going strong,” Nester said. “Revenue had declined along with the business population we used to support our operation over the years, however we felt it was an asset to community building and wanted to use it as such.”
\n\n\n\nNester purchased the paper, with the promised support of her core team members at the time. Most of them are still working with her today.
\n\n\n\n“The Welch News had been a staple in all our lives,” Nester said. “When we announced that we would cease to print, the community was outraged. We cried with customers stopping in to see us one last time, most of them sharing stories of their first job being a paper carrier at the newspaper. One of our carriers at the time told us the story of an elderly woman who said all she had at home was a landline phone and The Welch News. It’s all she had. We were absolutely floored as we heard how much our community wanted us to remain.”
\n\n\n\nThe Welch News Launches a Digital Publication on WordPress with the Help of the PaywallProject
\n\n\n\nAfter purchasing the paper, Nester held a meeting on May 8, 2018, where she invited everyone she could think of to help her plan a path to move forward. Tyler Channell, creator of the PaywallProject, attended this meeting and listened to the team’s goals and concerns.
\n\n\n\n“Building simple WordPress-based sites for various businesses is something I’ve done dating back to 2008,” Channell said. “I really started focusing on local newspaper web development in late 2017 after graduate school (journalism) at West Virginia University.”
\n\n\n\nChannell began helping local West Virginian newspapers, after they reached out with specific questions about generating revenue from their publications.
\n\n\n\n“Digital ads weren’t cutting it for them (a similar story I hear from publishers across the country),” Channell said. “With Facebook and Google owning virtually the entire digital ad market, newspapers must focus their efforts on generating paid digital subscriptions to remain sustainable. People are willing to pay for local content that they can’t get anywhere else.”
\n\n\n\nAfter helping his first local newspaper find success with a paywall he implemented, he decided to put together a simple ready-to-go website solution focused on growing paid digital subscribers for local newspapers across West Virginia and beyond. He now has approximately 20 local newspapers signed on to the PaywallProject’s services. The all-in-one subscription platform for local news costs $199/month and includes website development, a flexible paywall subscription platform with no transaction fees, migration, and built-in ad management.
\n\n\n\n“I use a number of different themes/plugin-based solutions combined with custom code, payments via Stripe, and hosting through DigitalOcean to bring it all together,” Channell said. “The goal for me is to provide all technical aspects so that local news publishers can focus on publishing content.”
\n\n\n\nFor many small publishers, this is their very first website. Channell said his clients are quick to acclimate to WordPress.
\n\n\n\n“I think when you remove the technical aspects of digital subscriptions, it reduces the learning curve dramatically,” he said.
\n\n\n\n“Growing digital subscriptions takes a lot of time and effort. But with each new paid subscriber a newspaper brings on board, local journalism becomes that much more sustainable.”
\n\n\n\nThe Welch News’ WordPress site helped put the publication on a path to sustainability. Within the first ten days of launching their digital edition, they gained 100 new subscribers, and subscriptions keep rolling in from local residents and people all over the country.
\n\n\n\n“I believe [Channell] was particularly interested when he learned our newsroom was staffed by millennials who cared deeply about the community they live in and hoped to make a positive change,” Nester said. “He realized our staff could easily transition.
\n\n\n\n“As publisher/owner, at 56 years old, I have probably been the person hardest to train on using the site, but even I am very comfortable posting articles without help.”
\n\n\n\nWelch News Editor Derek Tyson is the primary person writing and editing articles, approving submissions, and managing ad design and layout for the front page.
\n\n\n\n“We really enjoy the ease of access WordPress offers,” Tyson said. “I think we all were quite surprised how easy it was to put our articles into the digital format to share with the world at large. The transition wasn’t hard. Changing our office routine after over 90 years of only print publishing was by far the hardest part. PaywallProject made this transition easy for us. Trainings happened in our own newsroom, and PaywallProject has always available to help with any issues.”
\n\n\n\nThe entire publication process is still very much a labor of love, as is evident in this video the PaywallProject created featuring The Welch News. The team managing it is far younger than most of the town but fiercely dedicated to keeping this vital community resource going.
\n\n\n\n\nGrowing paid digital subscriptions in rural Appalachia is possible! @nestergirl2 @thatdamntyson pic.twitter.com/rpOE8fUEqM
— PaywallProject (@paywallproject) May 9, 2022
“Putting ourselves out into the digital world was both exciting and terrifying,” Nester said. “We were skeptical about our content being capable of generating online subscriptions. But it was the best case of being proven wrong in our lives.
\n\n\n\n“It does sometimes feel unnerving to move from a local publication that is only read via print media in your community, to a publication with a far greater reach. Sometimes that brings forth ‘internet warriors’ to criticize, as well as ‘internet warriors’ to support. PaywallProject is knowledgeable in the field of journalism, and that makes a great difference.”
\n\n\n\nThe Welch News Still Prints and Delivers the Paper Three Days Per Week
\n\n\n\nThe Welch News is just one of hundreds of publications that have found WordPress in the post-print news era, but unlike many others who transitioned to purely digital publishing, they are committed to keeping their print version going on their 1966 model printing press. They print three days a week and offer home delivery within McDowell County, as well as mail delivery across the nation.
\n\n\n\n\n“We have a high population of elderly residents, and strongly feel that they need the connection with the home delivery drivers three times each week,” Nester said. “We understand this isn’t the greatest business model, and often hear the advice to move to a weekly publication. Our desire to serve our residents in the best way possible keeps us headstrong about a three-day print publication.”
\n\n\n\nThough nearly everyone from his generation has moved away from the area, Tyson’s commitment to serve The Welch News’ elderly subscribers burns strong.
\n\n\n\n“We’re here to serve a very vulnerable population that I feel like the modern world is pretty quick to sweep under the rug,” Tyson said in a recent documentary about the county. “I see elderly people suffer, feeling like they’re not important and nobody needs them anymore. That’s just awful. They’re not as strong, they move a little slow, they’ll talk your head off but they’re living human beings that matter, and I’m going to fight for them.”
\n\n\n\nLocal news stands as a guardian for small, economically vulnerable counties like McDowell. In an area that is frequently cited among the five poorest counties in the US, the people still have their own voice through The Welch News. This publication finding sustainability is like a flower growing up through the concrete.
\n\n\n\nAs we witness the slow death of the American newspaper, these little newspapers staying alive to keep the public informed offer a ray of hope. Small publications continue to contend with the greed and corruption of the advertising industry, tech giants that have willfully eroded publishers’ trust through collusion and manipulation of the digital ad market. With affordable publishing tools like WordPress, The Welch News and its contemporaries can have a fighting chance.
\n\n\n\n“This is very much a heart project to serve and better our community, and we aren’t sure how long we can sustain it,” Nester said. “I’m certain we wouldn’t have survived the income loss from COVID without our website.
\n\n\n\n“I often say I quit my job every morning, but go anyway. I quit again by nightfall, and the email comes showing the income from online subscriptions and I decide to try again.”
\n\n\n\nTyson and his small team of journalists believe the best hope for keeping local news alive, when many small outlets have shuttered or consolidated, is maintaing a hyperlocal focus.
\n\n\n\n“Our strategy has been to shift our content priorities from broad coverage to a hyperlocal focus on issues within McDowell County’s borders,” he said. “With so many forms of media coverage available today, we decided to focus on what you couldn’t find anywhere else and in turn, showing that important things happen in small towns that deserve media attention.”
\n\n\n\nWordPress and the PaywallProject helped introduce a new stream of revenue for their century-old business. As the subscriptions continued to flow in, Nester said they realized “hyperlocal content did indeed have true value and would not be found anywhere else.” It’s one of the reasons many of the 2022 Pulizter prize winners have won for local stories that would never be covered in the larger news market.
\n\n\n\n“Citizens near and far should understand the need to fund local newsrooms, and the important work they do,” Nester said. “Understanding that without supporting local journalists, a large sense of community will be lost with each news desert that comes. If newsrooms are funded through community support, it is a better representation of that community and a means to bring forward local issues for resolution.”
\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:\"Mon, 16 May 2022 15:16: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: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:147:\"WordPress.org blog: WP Briefing: Episode 31: Open Source & Accessibility– Celebrating Global Accessibility Awareness Day With Guest Joe Devon\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=12855\";s:7:\"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:140:\"https://wordpress.org/news/2022/05/episode-31-open-source-accessibility-celebrating-global-accessibility-awareness-day-with-guest-joe-devon/\";s: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:33186:\"In the thirty-first episode of the WordPress Briefing, GAAD Co-Founder Joe Devon joins WordPress Executive Director Josepha Haden Chomphosy to discuss Global Accessibility Awareness Day and the role of open source in accessibility.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
Credits
\n\n\n\n- Guest: Joe Devon
- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Santana Inniss and Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- About GAAD
- GAAD Foundation Pledge
- World Health Organization on Disability
- The Dress Phenomenon
- The Guardian on Yanny or Laurel
- Empathy vs. Altruism in Modern Leadership, Josepha Haden Chomphosy
- The WebAim Million 2022 Report
- WordPress 6.0 Development Cycle
- WordCamp Europe 2022
Transcript
\n\n\n\n\n\n\n\n[Josepha Haden Chomphosy 00:00:00]
\n\n\n\nHello everyone. And welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nY’all, we’ve got an absolutely jam-packed couple of weeks in WordPress. We’ve got events happening and releases shipping and contributor days being coordinated (I almost said contributor days being contributed). That’s also what they’re doing. I’ll share some of those highlights in today’s small list of big things, but I did want to specifically call out something that’s coming up this week on Thursday (May 19, 2022), and that something is Global Accessibility Awareness Day.
\n\n\n\nThe team of contributors over on the Accessibility team has participated in the Global Accessibility Awareness Day in the past. So I thought it would be interesting to hear from one of the co-founders of this particular day of awareness.
\n\n\n\n[Josepha Haden Chomphosy 00:01:27]
\n\n\n\nAll right. And with that, Joe Devin, would you like to tell us a little bit more about yourself?
\n\n\n\n[Joe Devon 00:01:34]
\n\n\n\nSure. So I am the co-founder of Global Accessibility Awareness Day, which is a day that goes viral every year on the third Thursday of May. We typically have the Twitter reach on the GAAD hashtag on Twitter of 200 million users, which is, I think, pretty much their active user count. We stopped counting once we hit their daily active user count.
\n\n\n\nAnd then, I am Chair of the GAAD Foundation, which we launched last year. And then I have a day job too, where I’m CEO and co-founder of Diamond, which is an inclusive digital agency that builds software accessibly by default.
\n\n\n\n[Josepha Haden Chomphosy 00:02:15]
\n\n\n\nWonderful. Well, we are so excited to have you today. I said we like it’s me and the mouse in my pocket—we in the WordPress community that’s going to listen to this. Super excited to have you today. So you mentioned GAAD, Global Accessibility Awareness Day. Last year was your 10th anniversary, which is very exciting, but like with so many good things, I hear it all started with a blog post and a blog post on WordPress, no less.
\n\n\n\nSo I’d love to hear about how GAAD evolved from that, with, as I understand it, your co-founder of Jennison (Asuncion). That must be where you met him, I assume.
\n\n\n\n[Joe Devon 00:02:51]
\n\n\n\nYes. Yes. So what happened was I started a WordPress blog called My SQL Talk. So it’s a database blog, and I just thought it was a brilliant name. I mean, My SQL Talk, like that, should be super popular.
\n\n\n\nAnd it probably had maybe ten people who ever looked. Um, and then my dad was getting older, and my dad was a survivor of the concentration camps, and he was a genius. He spoke ten languages. It, he was one of those people. That, when he walked into a room, he just commanded respect. You knew that there was history. I don’t know how to explain it really, but it was special when my dad walked into the room. And considering all of this that he suffered in his life, watching him get older and struggle, particularly with his banking, was very painful to see. And the bank wasn’t accessible, so I wrote this blog post proposing that we create a Global Accessibility Awareness Day.
\n\n\n\nSometimes I get these visions, and they never turn into anything. But while I think about it, I’m like, “all right, let’s write this blog post and this can definitely work. Right?” And then you finish the blog post to hit send, and you’re like, “this is not going to work.”
\n\n\n\nBut I wasn’t even smart enough to do social media on it. But fortunately, WordPress had an auto-tweet feature, and it tweeted it out, and Jennison Asuncion, my co-founder, happened to be around and not out that Saturday night. And he read the blog post, and he said, “this is a great idea. Let’s make it happen.”
\n\n\n\nAnd we had two busy people, but we both had a community. He had the accessibility community, and I was building a tech scene in Los Angeles. And what I discovered is if you combine a great idea with the community, great things can happen.
\n\n\n\n[Josepha Haden Chomphosy 00:04:49]
\n\n\n\nOh man, you’re speaking my language over here, helping people find their communities, knowing that community is the thing that is the lifeblood of society.
\n\n\n\nThat sounded like a tautology. It is not a tautology. You can have a society with an attempt to not have any sort of community around it, but I bet it doesn’t work very well. Well, that’s, that’s very interesting. And so you all just kind of talked through what that would look like, I assume in confidence, or that would have to take place, right? Or was it on Twitter in those days?
\n\n\n\n[Joe Devon 00:05:24]
\n\n\n\nOh, you could still look in the comments and see the back and forth of Jennison and a bunch of other people that got pretty involved with GAAD that are some legendary folks in there. It’s kind of mind-blowing because I dunno how, how you feel, but for me, when I used to code, uh, three months later, I’d look back at old code and be like, “oh, I suck,” you know, or write an email even and you look back on it a day later and are like “what a stupid email, how stupid am I?” You know? But I look back on that one after ten years; I was scared to look at it because I’m like, it must’ve been really bad. But you know, it kind of held up, and exactly what I wrote in there happened – to my utter shock.
\n\n\n\n[Josepha Haden Chomphosy 00:06:06]
\n\n\n\nBut also, it’s kinda nice, though, to look back and be like, “oh, I used to be much dumber.”
\n\n\n\nCause then you’re like, look how far I’ve come. I’m no longer that dumb. I’m a different kind of dumb now; good for me. I always hope to be a different kind of dumb as I go forward.
\n\n\n\nSo then, okay, so that was your ten-year anniversary last year. GAAD, in general, now has been going on for 11 years, and at the time of this recording, in a couple of weeks, but then probably a week when it finally publishes, you have your next, your next round of that going.
\n\n\n\nI think it seems safe to assume that awareness of the need for accessibility has increased during that time, but we all know that the work of accessibility is ongoing. And so, I’m just curious to hear from your perspective if the awareness of the need for accessibility has generally started to permeate developer communities.
\n\n\n\nAnd are you seeing more developer awareness around the need for accessibility in tech in general?
\n\n\n\n[Joe Devon 00:07:12]
\n\n\n\nYeah. You know, it’s not enough. It’s certainly improved a lot. I keynoted a conference probably four years after GAAD started, maybe five, and I kind of assumed nobody would have heard of accessibility, and I was taken aback when I asked who had heard of it, and a good chunk of the room had. So even then, there had been a difference, and I’d say now I see accessibility mentioned a lot more in conferences and stuff. But when it comes to actually building it, there’s a tremendous amount of ignorance. There, there still needs to be a lot more awareness.
\n\n\n\nAnd I think partially people are a little bit scared to dip their toe because they’re scared that they’re going to be told that “no, it’s not accessible,” or that they’re going to say the wrong word or offend somebody. So I’d say that there’s some degree of trepidation, but also developers, and it’s not just developers, designers, and product people. There’s so much to learn, and it’s like, “oh God, there’s another piece that I have to learn.”
\n\n\n\nAnd I’m so glad that you invited me on this podcast because it’s the developers that, you know, I am a developer, not anymore, I haven’t touched code in years, but that’s where I came from. Right? This is my peach, right? Particularly WordPress folks, because I had done a fair bit of WordPress before I moved on to some other things. And, I think we have to talk about usability and understand that accessibility is so much more than how we look at disability.
\n\n\n\nAnd if you don’t mind, I’m going to ask you a question. How do you think the typical WordPress developer or designer would define disability?
\n\n\n\n[Josepha Haden Chomphosy 00:09:05]
\n\n\n\nin the kinds of conversations that I’ve had over the years, it frequently has to do with visual things. Because it’s just screens all day, right? And that’s a primary area where our designers and developers really have made some effort.
\n\n\n\nBut my personal favorite sort of, of example, for like, when you’re looking at how to make sure that your products are accessible is, what, if you have to use your website, or you have to build your website using only one arm. Because that gives you an opportunity to kind of look at disability from a permanent standpoint.
\n\n\n\nLike if you have lost permanent use of one arm, but also gives you an opportunity to look at the temporary options for that sort of lack of mobility. Like you’re a mother with an infant, and so you have to be able to, you know, get your stuff done with one arm. And so I know that we paid a bunch of attention to screen readers and what works in not way back in 2018 and 2019 did a lot of work with. Literally zero screen. And can you still do the thing that you need to do, which was incredibly difficult. And I was really excited to see what our developers came up with around that. But I think that that is quite a bit of that discussion as we’re going through it from the beginning to the end.
\n\n\n\n[Joe Devon 00:10:27]
\n\n\n\nYeah. I mean, that’s a great answer, and you definitely understand some of the nuances way better than I think that the average creator, digital product creator, I’m including the, you know, the product people, the designers, and the developers.
\n\n\n\n[Josepha Haden Chomphosy 00:10:42]
\n\n\n\nWe’re very fortunate to have more than just developers in WordPress.
\n\n\n\n[Joe Devon 00:10:50]
\n\n\n\nThe reason I bring this up is that the WHO (World Health Organization) had to; they’re the ones that did massive research across the globe. And they had to, they had to come up with a definition, and in their definition, they needed to draw a line. Typically, I don’t remember the exact thing cause it’s a 350-page report, and I kept looking for where they defined it again.
\n\n\n\nIt was a little hard to find, but essentially it’s if there’s a major disability or a disability that impacts some significant portion of your day-to-day activities. And that’s really great when you’re trying to do a report on how many disabilities there are out there; what percentage of the population has a disability?
\n\n\n\nAnd their figures are something like 15% of the population has a disability, which is a huge number. But at the same time, they also mentioned that 2.2 billion people have a visual impairment. And we also know that over 33% of the population is over 50, and I’m included in that population. And I can say that when you’re over 50, you know, I’ve got clouds in my eyes.
\n\n\n\nI don’t know where they came from, but they definitely make it harder to see. When I’m in a restaurant, I can’t focus on the person across from me the same way. My hearing is not the same, and anybody over 50 is going to have certain impairments and won’t see as well; color contrast issues are a big deal.
\n\n\n\nBeing able to raise the font is a big deal. And I think that accessibility is connected in most people’s minds with disability. And they’ll attach that to something like being blind or being deaf or hard of hearing or having a missing limb or having some other kind of disability.
\n\n\n\nAnd, as a result, they’re like, “well, I don’t even know any people in that category possibly,” and as a result, they’re like, “well, how important is this?” Yes. They might feel guilty. I should do the right thing. This is the right thing to do. But honestly, like how much money should I spend on it? How much, what percentage of my time should I spend on it?
\n\n\n\nAnd it’s because they don’t realize that everybody has different abilities. And so, I’m starting to go away from even talking about disabilities and asking people to remember that all of us perceive things differently.
\n\n\n\nDo you remember the gold dress where they were trying to say, what color is this dress? Is it gold and white or blue and black? And it is blue and black, but to me, all I see is gold and white. And then there was Laurel or Yanny. Do you remember that?. And some people heard it, and typically older people heard it as Laurel, and I’ve, and I do this in some of my presentations. I play that, that sound. And usually, it’s Laurel for me, but sometimes it’s Yanny. Even personally, it changes.
\n\n\n\nAnd so, we have a totally different perception. Now think about memory. There’s a different kind of blindness. If you try and remember, let’s say a relative or a friend that is no longer. How well do you see that picture?
\n\n\n\nBecause for me, it is very, very vague, but for some people, they say, and I’ve been asking people, and I’d love your answer as well. How vivid is it? And some people say, I can read the, I can see the pattern on the shirt. It’s as vivid as if I see with opening my eyes, seeing, you know, the regular in front of me, and I can even read a name tag in the memory.
\n\n\n\nAnd I’m like, Woah, so maybe I’m blind in a way. Right? So how do you see it? How do you remember things?
\n\n\n\n[Josepha Haden Chomphosy 00:14:42]
\n\n\n\nOh, I’m a, I’m a real visual person and a tactile person. And so, like if I interacted with someone, I’m very likely to be able to picture, like, recreate that mental picture pretty well in my mind. I recently, very recently, met some of my first people in that executive leadership space who were like, yeah, I don’t, I don’t visualize things.
\n\n\n\nAnd I was like, what are you, how do you do this work? Because like, you have to be able to do that. And they were like, no, I don’t have mental pictures.
\n\n\n\n[Joe Devon 00:15:13]
\n\n\n\nSome people don’t have an inner dialogue.
\n\n\n\n[Josepha Haden Chomphosy 00:15:17]
\n\n\n\nI don’t understand that either,
\n\n\n\n[Joe Devon 00:15:19]
\n\n\n\nMe either. So accessibility studies all of these differences with respect to how you’re presenting all of this information.
\n\n\n\nAnd if you don’t pay attention to accessibility, you’re really just missing out. And then there’s colorblindness. If you’re creating something like slack that has an online/offline indicator, and you only use red and green for people who are colorblind, they see gray and gray. And so what I’m trying to teach the community with digital product creators is that no, you cannot ignore it.
\n\n\n\nYou can ignore accessibility, but then you’re not good at your job. I mean, I don’t mean to say it in an offensive way, but you’re not good at your job if you’re unaware. If you break a rule on purpose, great. But if you don’t know the rule, it’s just a lack of craft, and you absolutely should make it a priority.
\n\n\n\nAnd you’re not doing it as a charity. You’re doing it because you care about your users, and you care about your craft, and you want to build things well, and it’s a necessity. And I think that this is the kind of message that our community needs to hear.
\n\n\n\n[Josepha Haden Chomphosy 00:16:31]
\n\n\n\nI want to touch on something that you sort of brought up a bit, um, at the start of the answer there.
\n\n\n\nSo you brought up the concept of usability. And in the last time that I did a podcast about accessibility, I defined accessibility as a subset of usability. Do you think that if we were to consistently draw that line for people so that it’s not just like accessibility is this thing that you should do outside of usability?
\n\n\n\nIf we were to more consistently draw that line, do you think that that would help people to see and understand better that its shades of existence, usability, and accessibility?
\n\n\n\n[Joe Devon 00:17:10]
\n\n\n\nOh, 100%, a hundred percent. And in my company, we kind of realized that that’s exactly what we have to do. We have to see this as usability.
\n\n\n\nAnd I don’t, we talk about accessibility a lot, but I don’t want to. It’s part of the plumbing for us. We’ve made it part of the plumbing, and I can tell you it’s a struggle to take accessibility and make it part of an organization, even when you’re bringing it top-down, believe it or not. For our teams, particularly the designers, they are blown away by what they’re learning because they’re improving their craft.
\n\n\n\nAnd design is typically where there’s a struggle to get accessibility accepted because there seems to be a very strong idea of what a design should look like. And I think it’s really about the approach because UX and design it’s all about empathy for people. And when you approach it, not as, even though empathy should mean that, that, you know, do the right thing at the same time, it’s more about empathy for your user, and your user includes so much more than just people with disabilities that you haven’t run into somebody that has that disability and therefore you build it better, and it’s, it’s completely blown their mind. They love it. They love doing it. And I’m not hiring people with accessibility coming in. We’re training them to work accessibly.
\n\n\n\n[Josepha Haden Chomphosy 00:18:34]
\n\n\n\nSo I think it’s interesting that you talk about empathy as part of being able to make sure that you’re creating something that’s accessible because I actually feel like empathy is. Like it’s being considered this gold standard for many, many things right now. And I think it actually is more harmful in the long run than instead making altruistic choices.
\n\n\n\nAnd so, I have a blog post that I will link in our show notes that will kind of help everybody see more fully my concept there. But when you rely on empathy, you do kind of have to rely on one, being able to run into all of the issues you were mentioning. You have to know people who have problems in order to know that the problems exist.
\n\n\n\nAnd then you also kind of have to assume that once you have willingly put yourself into the discomfort of that kind of disability, whatever, wherever it exists on that spectrum, your experience of that discomfort is the same as someone who lives with it. And I just don’t think that we can necessarily do that.
\n\n\n\nI always think that trying to do the altruistic thing, like doing your research and figuring out what it is and trying to make decisions on behalf of other people as best you can, which is a terrible thing. Still, like decisions that take into account the experiences that people are sharing with you and then going to them and saying, “does this make that experience better or worse?” is the more sustainable option from my perspective, this is specifically leadership. Still, I think it’s true for accessibility as well, and probably product design as a whole, but it’s very difficult. Like people really feel like they understand the concept of empathy right now. And I do think that sometimes that leads us down the wrong path for things.
\n\n\n\nWhat’s your thought on that? I think you kind of agree based on what your answer was
\n\n\n\n[Joe Devon 00:20:33]
\n\n\n\nOh, no, absolutely. And you know, we, you, can’t never about us without us, as the common saying, and we’ve gathered a group of a hundred people with a wide variety of disabilities for research. Whenever we do any UX and research, and sometimes we’re asked to just do research projects, we go out and ask the users.
\n\n\n\nWe had some really interesting companies approach us to do innovation and accessibility, and they had strong assumptions. We looked at the assumptions and agreed with it, but we’re like, all right, they were smart. They said, “vet this with users for us, please,” because they didn’t want to gather their own group.
\n\n\n\nWe vetted with users, and we’re blown away, always blown away because there are so many things you just don’t know unless you’ve lived with a particular disability. You can’t guess, and you’ve got to speak to your users and a wide variety of them.
\n\n\n\n[Josepha Haden Chomphosy 00:21:30]
\n\n\n\nYes, absolutely. Absolutely. What role does open source play in expanding accessibility, either in specifically the digital space or just accessibility in general?
\n\n\n\n[Joe Devon 00:21:42]
\n\n\n\nI guess if the question is, what role does it play? I would say the role it plays is it is, unfortunately, it makes accessibility worse because, for the most part open source is not very accessible. And it’s a personal passion of mine, so I’m really glad that you brought that up.
\n\n\n\nYou know, it is so bizarre. You write a blog post and then it goes viral, and it goes viral every year to a degree that you can’t even believe it, that all these companies that you know are running events. Privately, publicly talking about it. And then you get all these people thanking you for what you’ve done year after year.
\n\n\n\nAnd then one year, you read on Twitter, The Blind Onion; I’m sure you’re familiar with The Onion, the satirical clip, there’s the Blind Onion. And they tweet out, “Now that Global Accessibility Awareness Day is over, we look forward to 364 days of global accessibility oblivion.” And that really hurt at the time, but at the same time, and I was told to ignore it, don’t worry about it, but I’m like, no, this is coming from a place of pain.
\n\n\n\nAnd the point of GAAD was to make a difference. It wasn’t too to just give everybody an opportunity to say, “Hey, look at what we’re doing,” and then not make a difference. So, as a result of that, I started to think about, well, where are we with this? And, and so I’ve created a state of accessibility report that through my company, we’re able to run for a few years, and it’s not, you know, the state is not great.
\n\n\n\nAnd I’m like, well, what can we do to change things? So, as a result of all of this, I really wanted to figure out, well, what can we do to make sure that GAAD does make a difference? And so, I came up with the idea of the GAAD pledge, which is specifically meant for open source frameworks.
\n\n\n\nAnd the idea of the GAAD pledge is that an open source framework, when they are ready, takes the pledge to make accessibility a core value of the framework. Now, terms of what that actually entails are different for every single project because every project is unique. We did create a bit of a framework, which had the idea of saying, okay, you’re going to, first of all, create an accessibility statement that says that this framework is going to conform to whatever, WCAG, which is Web Content Accessibility Guidelines, to whatever WCAG level is decided and is appropriate for the framework. That there’s going to be documentation for anybody that is downloading this piece of open source project and trying to implement it, that there should be guidelines for them, that all of the examples should be accessible.
\n\n\n\nIt’s really important because even the frameworks that try to pay attention to accessibility. You’ll often see that people from the community will provide examples, and they’re inaccessible. And it’s really sad when you see that because so many people are just copy-pasting. That’s typically how it works, and they’re going to copy-paste something bad. So putting a statement around it, I think, would be really great.
\n\n\n\nAnd what we’re hoping to see is that lots and lots of big open source communities decide to take the pledge. And then it’ll sort of be table stakes that any new open source projects as well look, all of these frameworks that made it, they took the pledge and therefore we should take the pledge as well.
\n\n\n\nAnd so the very first year, we had React Native take the pledge, and they put a lot of effort into their accessibility. The second group to take it was Ember.js, and they always put a lot of effort into their accessibility, and they continued that effort. We’re about to announce the next one, but we’re still two weeks away.
\n\n\n\nSo I can’t say anything yet, but yeah, we’re, uh, we’re hoping for a lot more uptake on, on the gap pledge because it, it affects so many people downstream. WordPress’s what percent of the web right now? 43%? So there you go. That’s so many people.
\n\n\n\n[Josepha Haden Chomphosy 00:25:57]
\n\n\n\nSo many people. Yeah, fun fact Gutenberg, our current rewriting of the editing experience in WordPress, primarily uses React. And so, I’m glad to hear that they have taken that pledge as well.
\n\n\n\nAs with any good cooking, it starts with good ingredients.
\n\n\n\n[Joe Devon 00:26:12]
\n\n\n\nYou said it. That was great. I wish I was a cook, though.
\n\n\n\n[Josepha Haden Chomphosy 00:26:23]
\n\n\n\nI love it. All right. Let’s what keeps you up at night when it comes to the state of accessibility?
\n\n\n\n[Joe Devon 00:26:29]
\n\n\n\nWhat keeps me up at night is how to move the needle. It is such a big thing to change. And there are so many angles that you can approach this with, but at the end of the day, it’s, it’s a monster.
\n\n\n\nIt’s a monster. There are so many legacy sites out there. If you look at WebAIM, they do a yearly report on the state of accessibility as well. They call it the WebAIM Million, and they’re typically seeing 97% inaccessible, 98%. It goes up and down a little bit every year. And that’s, that’s just a huge boat to move.
\n\n\n\nI think we need to at least get the newer, uh, newer websites and mobile apps to move. And what we’ve seen in our state of accessibility report is that only the very top companies seem to put in the effort to make their products accessible. There is a big push with the enterprise companies to do it.
\n\n\n\nThe CEOs are starting to talk about it, but what we need is the entire culture of software development to change. Or I should even say digital product development change and to move that boat is massive. And that’s I put it in my tagline in my email like that’s my mission in life, and I hope to achieve it before I die.
\n\n\n\nSo that keeps me up at night.
\n\n\n\n[Josepha Haden Chomphosy 00:27:52]
\n\n\n\nI think that would keep me up at night as well. I mean, it seems like you are really just personally mission-driven and impact-driven. Do you feel like, in the event that the work that you’ve accomplished so far is what you accomplish, you feel still like you’ve had an impact?
\n\n\n\nI feel like you have had an impact.
\n\n\n\n[Joe Devon 00:28:13]
\n\n\n\nI’m not one of those people that tries to have a legacy or like tries to focus on what my impact is and all of that. I just try and do good work. And hopefully, it just shows at the end of the day. I’m just trying to have the impact without the accolades.
\n\n\n\n[Josepha Haden Chomphosy 00:28:34]
\n\n\n\nI get it. Well, Joe, thank you so much for joining us here on this episode of WP Briefing. You have been a delight to chat with.
\n\n\n\n[Joe Devon 00:28:42]
\n\n\n\nLikewise, it’s really been a pleasure to meet you, and uh, and I appreciate the opportunity.
\n\n\n\n[Josepha Haden Chomphosy 00:28:54]
\n\n\n\nAnd now it’s time for our smallest of big things. As I mentioned at the start, it is packed. Number one tomorrow, May 17th, RC3. So one of the final RCs that we’re going to have for the WordPress 6.0 release, unless something goes horribly, horribly wrong, which I don’t think it will.
\n\n\n\nAnd then, two days after that, Global Accessibility Awareness Day, as I mentioned, will be on May 19th. So, this coming Thursday.
\n\n\n\nAnd then next week, we have the 6.0 release. We have the WordPress 6.0 release on May 24th.
\n\n\n\nThree days after that, WordPress turns 19 on May 27th, starting its final teenage year before we turn twenty in 2023. So that was the rapid-fire dance card for the next two weeks.
\n\n\n\nThe stuff that is happening with and around WordPress for everyone to know. As a heads up, also, many people are headed to WordCamp Europe in Porto(, Portugal). The first week of June, I am going to do a live from WordCamp Europe episode. It will not be live. I’ll just record it live. And so. You know you’ll get to hear me with my hoarsest voice and maybe singing to my computer. Cause that almost always happens at these things.
\n\n\n\nAnd that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy. And I’ll see you again in a couple of weeks.
\";s: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, 16 May 2022 12:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:117:\"Gutenberg Times: Three Block Theme Generators, Gutenberg 13.2, Coupons with Blocks and more – Weekend Edition 215\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=21139\";s:7:\"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:120:\"https://gutenbergtimes.com/three-block-theme-generators-gutenberg-13-2-coupons-with-blocks-and-more-weekend-edition-215/\";s: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:16135:\"Howdy,
\n\n\n\nI can hardly wait to be in the same room with fellow contributors across many teams during Contributor Day at WordCamp Europe, collaborate on the open-source project tasks, and meet new contributors in person!
\n\n\n\nNext week, my husband and I will fly to Porto for a two-week work-cation prior to WordCamp Europe. We will explore Portugal’s second largest city and its wider area during lunch breaks, evening strolls and weekend excursions. It’s a new way of traveling for us and we are grateful for our remote work so we can stay for a longer period of time in a city.
\n\n\n\n\n\nAnd now back to the topic at hand: News and community resources around the block editor, block themes, full-site editing and more.
\n\n\n\nEnjoy the mixture of articles and post. Have a great weekend!
\n\n\n\nYours, ?
Birgit
This week’s releases
\n\n\n\nWordPress 6.0 RC2
\n\n\n\nWordPress 6.0 Release Candidate 2 (RC2) Now Available for Testing. It seems everything is on track for the final release scheduled for May 24, 2022.
\n\n\n\nCurious what WordPress 6.0 looks like? Watch this great video by Jamie Marsland with short succinct demos of the most important features for site builders and he asks WordPress 6: The Most Exciting Update Ever?
\n\n\n\nCan you believe, Core Contributors already started Bug Scrubs for 6.1? I guess you can never start too soon.
\n\n\n\nGutenberg 13.2
\n\n\n\nFor the first time, George Hotelling led the release for the Gutenberg plugin and posted the release notes: What’s new in Gutenberg 13.2? (May 11). Many PRs were Bug fixes, and not so many new features. Hotelling highlights the new save method for user’s editor preferences. Now that the preferences (Welcome buide, Full Screen, Top Toolbar etc) are stored in the user meta table of the site, you can now access the site from any computer and it will remember the choices you made. We waited quite a while for this feature to land.
\n\n\n\nJustin Tadlock took the plugin for spin and he has more details in his article: Gutenberg 13.2 Adds Persistent User Preferences and a Visualizer for Margin and Padding Controls
\n\n\n\n\n\n\n\n
Earlier this week, I was part of the This Week in WordPress #208 live show and podcast. with Daniel Schutzsmith, Nathan Wrigley, and Michelle Frechette.
\n\n\n\nWe talked about FSE Testing Call 14 using the refactored List and Quote Blocks, the new feature to assign patterns to the page creation process, the Artist in Residence program by DigitalCube, introduced by Rachel Winchester and so much more. It was lovely to connect with my friends again. We had great fun. Listen in!
\n\n\n\n\n\n\n\n
Three Block Theme Generators
\n\n\n\nEver we started seeing Full-site editing evolving, community members pushed the envelop and created tools for creating themes. Today, I put three of them in one space.
\n\n\n\nThemeGen.App by David Gwyer was very early and the site provides you an easy way to make all the color and settings choices via a nice web interface and then create a theme.json file.
\n\n\n\nCarolina Nymark‘s Block Theme Generator makes a few decisions for you. She offers visitors to download a basic block theme, and empty theme and an advanced block theme. The latter is the best teaching tool, as it includes not only a bare bones theme, but also example templates, block patterns and block styles. With help of a bare bones form, you also can select your color palette and some default settings.
\n\n\n\nWhile both mentioned Block Theme Generators are aimed at the Theme developers working with code, Jamie Marsland of PootlePress just built a Block Theme Generator that’s aimed at the #nocode site builder. It’s fairly new and used out of the box tools and the WordPress site editor to design every aspect of a theme that you then can export. Marsland explains in this video on YouTube, how he built it, why Theme Export is such a big deal, and how you can also build a theme generator for you team.
\n\n\n\nFull Site Editing & Plugins for site builders
\n\n\n\nWordPress 6.0 To Ship New Block Locking Feature – Justin Tadlock gives you a sneak preview on the new feature.
\n\n\n\n\n\n\n\n
Full-site editing experience is not for everyone yet. Ruth Raventós, CEO of Nelio, after explaining what FSE entails, walk you through the decision-making process on if your site, your online business, is suited to adopt aspects of FSE. It’s not a technical evaluation, rather than a strategic approach. “The first task you should do is to understand all the functionalities you want your “new” website to have and see which of them can be provided by FSE. Then, for those that are provided by plugins, evaluate if they are compatible with FSE or what alternatives you have.” Ruth Raventós wrote.
\n\n\n\n\n\n\n\n
4 (four) more days, until May 18th, 2022, to heed the FSE Program Testing Call #14: Rallying Recipe Reviewers. It’s also available in Italian. (Raduniamo i recensori di ricette), thanks to Piermario Orecchioni
\n\n\n\nAnne McCarthy, Courtney Robertson and Sarah Snow tested all the features mentioned in the call for testing together in a zoom video meeting. If you don’t have time to do the testing yourself, but want to know what’s in the pipeline you can watch this on WordPress.TV: Testing WordPress Together: New Interactivity Features for Recipe Websites
\n\n\n\n\n\n\n\n
Vikas Singhal announced that their block theme Gutena already supports Webfonts API that allows you to host fonts locally, with a single line in theme.json.
\n\n\n\n\n\n\n\n
In his latest Building with Blocks post, Justin Tadlock walks you through the process of How To Build Coupon Cards With WordPress Blocks. Get ready for the 2022 eCommerce season for Black Friday and Cyber Monday in the fall. Or for any other eCommerce sale you might have in mind.
\n\n\n\n\n\n\n\n
Bernhard Kau, who is not only co-organizer of this year’s WordCamp Europe but also a plugin developer, just released a new plugin: Campaign Archive Block for Mailchimp
\n\n\n\nAfter adding an API key in the settings, the block displays the latest newsletters from your Mailchimp account. Kau has added some display settings and a control for the numbers of campaigns to be listed. This way, you keep your visitors for one more page on your site before they head off to read you latest campaigns. A plugin that does one thing and only one thing. The best kind of block.
\n\n\n\nIt’s a solid first version and if you are interesting in a short twitter exchange between Kau and myself, on possible improvements, you can follow along here.
\n\n\n\n\n\n\n\n
Munir Kamal, developer of the EditorPlus plugin, demonstrates in this video How to Create Animated Search Box in Gutenberg. All through the plugin and a short CSS snippet added to the backend for rendering the animation. Pretty nifty!
\n\n\n\n\n\n\n\n
Justin Tadlock reviewed one of the newest block themes: Catch FSE Is a Bold, Business-Friendly WordPress Block Theme
\n\n\n\nDeveloping Custom Blocks and Tools
\n\n\n\nCore contributor and Gutenberg developer Dave Smith, gave a presentation recently on Gutenberg Now, Next and How to Use it Better Today.
\n\n\n\nHe spoke to developers at the WordPress agency CornerShop Creative who are building sites for nonprofits, small and large. The video description has time stamps so you can jump to the relevant topics. Smith also points out that the second half of the presentation was Live Q & A and he provided answers to questions, you might have too. The slidedeck is available online.
\n\n\n\n\n\n\n\n
Liam Giddy ventured into building a business listing using ACF Blocks and the Query Loop Block with a block theme and created this tutorial. It’s great step on the journey to switch to block theme development.
\n\n\n\nUpcoming WordPress Social Learning Meetups
\n\n\n\nMay 18, 2022 – 6 pm EDT / 22:00 UTC
Sticky Styling: Getting Colors, Fonts, and Sizes to Stick w/ Sarah Snow
May 19, 2022 5pm EDT / 21:00 UTC
Using the Navigation Block w/ Wes Theron
May 19, 2022 – 2pm EDT / 18:00 UTC
Builder Basics: Working with Templates in Full Site Editing (Part 3) w/ Nick Diego
May 23, 2022 1pm EDT / 17:00 UTC
Hello Blocks! Coding a custom block w/ Ryan Welcher
May 25, 2022 – 7pm EDT / 23:00 UTC
Design With Me: Create a Simple Website for your Small Business w/ Sarah Snow
Featured Image: Skyline of Chicago by Birgit Pauli-Haack (Nov 2021)
\n\n\n\n\n\n\n\n\n\n
Don’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 14 May 2022 19:47:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:111:\"WPTavern: WordSesh 2022 Kicks Off Monday, May 16, Featuring a World-Class Speaker Lineup and Hands-On Workshops\";s:7:\"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=134352\";s:7:\"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:120:\"https://wptavern.com/wordsesh-2022-kicks-off-monday-may-16-featuring-a-world-class-speaker-lineup-and-hands-on-workshops\";s: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:4797:\"
WordSesh 2022, the live, virtual conference for WordPress professionals, is right around the corner. The event runs from May 16–20, 2022. While previous WordSesh events have always been high quality, this particular edition is jam-packed with a diverse selection of industry experts – many who have been building high impact projects with WordPress for years.
\n\n\n\nThis year’s WordSesh will feature 20 sessions, 3 keynotes, and two in-depth workshops. On May 19, at 8PM EDT, frontend developer Ellen Bauer from Elma Studio will guide users in a workshop on how to “Convert a Classic Theme to a Block Theme.” If you are a theme developer who hasn’t taken the leap into block themes, this workshop will get you started:
\n\n\n\n\n\n\n\nTogether, we will set up the header and footer in a block theme, learn to work with Templates and Template Parts, set up page contents, and dive into how Styles work.
Throughout the workshop we’ll discuss which website projects can benefit from the new FSE features the most, what limitations we are still facing, and how the future of WordPress themes will most likely look.
The second workshop will be given by Tiffany Bridge, Product Manager at Nexcess, on May 20. She will give attendees an overview of how to prepare their web properties for a high traffic event.
\n\n\n\nOne of the most exciting sessions on the schedule is the keynote on May 19. The team that rebuilt WhiteHouse.gov on WordPress in just six months will join the event to talk about the project. Other topics on the schedule include custom block development, headless WordPress, hacking, client services, performance, accessibility, and user experience.
\n\n\n\nIn 2021, Brian Richards, founder of WPSessions.com and organizer of WordSesh, has transitioned the event to be more inclusive of timezones around the world. This year’s event will happen over the course of four days, with time offsets that accommodate a global audience. The first block of sessions is optimally timed for attendees across Asia and the Pacific. Day 2 is designed for attendees across Europe, Middle East, and Africa, and day 3 will cater to attendees in the Americas, Iceland, and Greenland.
\n\n\n\n“In 2019 and 2020 I ran entirely separate events for each region, but in 2021 I brought them back together as a single event,” Richards said. “I found it was a lot easier to get people excited about and paying attention to one big WordSesh event.
\n\n\n\n“It feels more inclusive this way, even though the separate events were also open to attendees from around the world. I think that’s primarily because there is something that is conveniently scheduled for someone no matter where they live. And with a single event, watching the recordings feels more akin to catching up on the pieces you missed rather than trying to watch talks for an event that was designed for somebody else.”
\n\n\n\nThe scheduling modifications seem to be working, as the last event in 2021 hosted 3,600 attendees, making WordSesh the second largest WordPress community event behind WCEU 2020.
\n\n\n\nRichards continues to curate a high-quality speaker lineup year after year, through the help of attendee surveys, which reveal where people are spending their time, attention, and money. WordSesh pays its speakers and Richards also invests time for personal outreach. Through this combination, he said the schedule fills up fast.
\n\n\n\n“I think paying the speakers certainly helps with recruiting such incredible presenters, but I imagine that’s more icing on the cake for most speakers,” Richards said. “Probably the biggest draw is the history WordSesh now has (this is the 9th year and 12th event, officially), helped by the ever-increasing reach of my own personal network.”
\n\n\n\nUntil 2021, Richards had been running the events entirely by himself. Last year he hired a part-time assistant and also started contracting out the video editing, which has helped him keep the event running more efficiently. It is quite a feat to have hosted WordSesh so many years running when many comparable virtual WordCamps of this caliber often rely on a large team of volunteers and organizers.
\n\n\n\nRegistration for WordSesh is still open and it’s free for anyone to attend. The event will be live captioned by real people and all sessions will be recorded for purchase later on WPSessions.
\";s: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, 13 May 2022 19:35:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:68:\"Post Status: WordPress Podcast and Video Picks for the Week of May 8\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=97445\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://poststatus.com/wordpress-podcast-and-video-picks-for-the-week-of-may-8/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2661:\"Jane Genova on overcoming ageism. Courtney Robertson on Learn #WordPress. 10 lesser-known browser APIs. PHP encryption. Free FSE theme.
My Podcast Picks
\n\n\n\n- Freelancing After 50: Jane Genova on dealing with marketplace age bias and her “reset” — shifting her services and mindset to fit prevailing marketing forces.
- WP Tavern Jukebox: Courtney Robertson discusses how the Learn Project educates people about WordPress.
- Syntax.fm: 10 browser APIs you might not be familiar with.
My Video Picks
\n\n\n\n- Best Ways To Encrypt Passwords, Keys, and More With PHP: Thomas McGee from Delicious Brains covers hashing, secret key encryption, and envelope encryption.
- Bricksy: A video tour of a recently released (and free) full site editor theme.
Get our weekly WordPress community news digest — Post Status\' Week in Review — also available in our newsletter.
And don\'t miss the latest updates from the people making WordPress. We\'ve got you covered with This Week at WordPress.org.
We’re a studio in Berlin with an international practice in architecture, urban planning and interior design. We believe in sharing knowledge and promoting dialogue to increase the creative potential of collaboration.
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":6:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:17:\"large text, title\";s:16:\"wpop_description\";s:12:\"Heading text\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:1:{i:0;s:12:\"core/heading\";}s:11:\"wpop_locale\";s:5:\"en_US\";}s:14:\"category_slugs\";a:2:{i:0;s:8:\"featured\";i:1;s:4:\"text\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:621:\"\nWe\'re a studio in Berlin with an international practice in architecture, urban planning and interior design. We believe in sharing knowledge and promoting dialogue to increase the creative potential of collaboration.
\n\";}i:1;O:8:\"stdClass\":7:{s:2:\"id\";i:185;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:35:\"Large header with left-aligned text\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:2153:\"\n![\"\"](\"https://s.w.org/images/core/5.8/forest.jpg\")
Forest.
\n\n\n\nEven a child knows how valuable the forest is. The fresh, breathtaking smell of trees. Echoing birds flying above that dense magnitude. A stable climate, a sustainable diverse life and a source of culture. Yet, forests and other ecosystems hang in the balance, threatened to become croplands, pasture, and plantations.
\nForest.
\n\n\n\nEven a child knows how valuable the forest is. The fresh, breathtaking smell of trees. Echoing birds flying above that dense magnitude. A stable climate, a sustainable diverse life and a source of culture. Yet, forests and other ecosystems hang in the balance, threatened to become croplands, pasture, and plantations.
\nOverseas:
1500 — 1960
\n\n\n\nAn exhibition about the different representations of the ocean throughout time, between the sixteenth and the twentieth century. Taking place in our Open Room in Floor 2.
\n\n\n\nOverseas:
1500 — 1960
\n\n\n\nAn exhibition about the different representations of the ocean throughout time, between the sixteenth and the twentieth century. Taking place in our Open Room in Floor 2.
\n\n\n\n\n![\"Close-up](\"https://s.w.org/images/core/5.8/soil.jpg\")
What’s the problem?
\n\n\n\nTrees are more important today than ever before. More than 10,000 products are reportedly made from trees. Through chemistry, the humble woodpile is yielding chemicals, plastics and fabrics that were beyond comprehension when an axe first felled a Texas tree.
\n\n\n\nWhat\'s the problem?
\n\n\n\nTrees are more important today than ever before. More than 10,000 products are reportedly made from trees. Through chemistry, the humble woodpile is yielding chemicals, plastics and fabrics that were beyond comprehension when an axe first felled a Texas tree.
\n\n\n\n\n![\"Close-up,](\"https://s.w.org/images/core/5.8/architecture-04.jpg\")
Open Spaces
\n\n\n\n\nOpen Spaces
\n\n\n\n\n![\"A](\"https://s.w.org/images/core/5.8/art-02.jpg\")
Shore with Blue Sea
\n\n\n\nEleanor Harris (American, 1901-1942)
\nShore with Blue Sea
\n\n\n\nEleanor Harris (American, 1901-1942)
\n\n\n\n\n
![\"A](\"https://s.w.org/images/core/5.8/portrait.jpg\")
\n\n\n\n“Contributing makes me feel like I’m being useful to the planet.”
— Anna Wong, Volunteer
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":6:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:0:\"\";s:16:\"wpop_description\";s:0:\"\";s:19:\"wpop_viewport_width\";i:800;s:16:\"wpop_block_types\";a:1:{i:0;s:10:\"core/quote\";}s:11:\"wpop_locale\";s:5:\"en_US\";}s:14:\"category_slugs\";a:1:{i:0;s:4:\"text\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:1012:\"\n
\n\n\n\n
\n\n\n\n\"Contributing makes me feel like I\'m being useful to the planet.\"
— Anna Wong, Volunteer
\n\";}i:7;O:8:\"stdClass\":7:{s:2:\"id\";i:200;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:21:\"Three columns of text\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:2429:\"\n
Virtual Tour ↗
\n\n\n\nGet a virtual tour of the museum. Ideal for schools and events.
\nCurrent Shows ↗
\n\n\n\nStay updated and see our current exhibitions here.
\nUseful Info ↗
\n\n\n\nGet to know our opening times, ticket prices and discounts.
\nVirtual Tour ↗
\n\n\n\nGet a virtual tour of the museum. Ideal for schools and events.
\nCurrent Shows ↗
\n\n\n\nStay updated and see our current exhibitions here.
\nUseful Info ↗
\n\n\n\nGet to know our opening times, ticket prices and discounts.
\nECOSYSTEM
\n\n\n\nPositive growth.
\n\n\n\n\nNature, in the common sense, refers to essences unchanged by man; space, the air, the river, the leaf. Art is applied to the mixture of his will with the same things, as in a house, a canal, a statue, a picture. But his operations taken together are so insignificant, a little chipping, baking, patching, and washing, that in an impression so grand as that of the world on the human mind, they do not vary the result.
\n![\"The](\"https://s.w.org/images/core/5.8/outside-01.jpg\")
![\"Wind](\"https://s.w.org/images/core/5.8/outside-02.jpg\")
![\"The](\"https://s.w.org/images/core/5.8/outside-03.jpg\")
Undoubtedly we have no questions to ask which are unanswerable. We must trust the perfection of the creation so far, as to believe that whatever curiosity the order of things has awakened in our minds, the order of things can satisfy. Every man’s condition is a solution in hieroglyphic to those inquiries he would put.
\nECOSYSTEM
\n\n\n\nPositive growth.
\n\n\n\n\nNature, in the common sense, refers to essences unchanged by man; space, the air, the river, the leaf. Art is applied to the mixture of his will with the same things, as in a house, a canal, a statue, a picture. But his operations taken together are so insignificant, a little chipping, baking, patching, and washing, that in an impression so grand as that of the world on the human mind, they do not vary the result.
\nUndoubtedly we have no questions to ask which are unanswerable. We must trust the perfection of the creation so far, as to believe that whatever curiosity the order of things has awakened in our minds, the order of things can satisfy. Every man\'s condition is a solution in hieroglyphic to those inquiries he would put.
\n![\"Close-up,](\"https://s.w.org/images/core/5.8/architecture-01.jpg\")
![\"Close-up,](\"https://s.w.org/images/core/5.8/architecture-02.jpg\")
![\"Close-up](\"https://s.w.org/images/core/5.8/architecture-03.jpg\")
The voyage had begun, and had begun happily with a soft blue sky, and a calm sea.
\n\n\n\nThey followed her on to the deck. All the smoke and the houses had disappeared, and the ship was out in a wide space of sea very fresh and clear though pale in the early light. They had left London sitting on its mud. A very thin line of shadow tapered on the horizon, scarcely thick enough to stand the burden of Paris, which nevertheless rested upon it. They were free of roads, free of mankind, and the same exhilaration at their freedom ran through them all.
\nThe ship was making her way steadily through small waves which slapped her and then fizzled like effervescing water, leaving a little border of bubbles and foam on either side. The colourless October sky above was thinly clouded as if by the trail of wood-fire smoke, and the air was wonderfully salt and brisk. Indeed it was too cold to stand still. Mrs. Ambrose drew her arm within her husband’s, and as they moved off it could be seen from the way in which her sloping cheek turned up to his that she had something private to communicate.
\nThe voyage had begun, and had begun happily with a soft blue sky, and a calm sea.
\n\n\n\nThey followed her on to the deck. All the smoke and the houses had disappeared, and the ship was out in a wide space of sea very fresh and clear though pale in the early light. They had left London sitting on its mud. A very thin line of shadow tapered on the horizon, scarcely thick enough to stand the burden of Paris, which nevertheless rested upon it. They were free of roads, free of mankind, and the same exhilaration at their freedom ran through them all.
\nThe ship was making her way steadily through small waves which slapped her and then fizzled like effervescing water, leaving a little border of bubbles and foam on either side. The colourless October sky above was thinly clouded as if by the trail of wood-fire smoke, and the air was wonderfully salt and brisk. Indeed it was too cold to stand still. Mrs. Ambrose drew her arm within her husband\'s, and as they moved off it could be seen from the way in which her sloping cheek turned up to his that she had something private to communicate.
\nOceanic Inspiration
\n\n
Winding veils round their heads, the women walked on deck. They were now moving steadily down the river, passing the dark shapes of ships at anchor, and London was a swarm of lights with a pale yellow canopy drooping above it. There were the lights of the great theatres, the lights of the long streets, lights that indicated huge squares of domestic comfort, lights that hung high in air.
\nNo darkness would ever settle upon those lamps, as no darkness had settled upon them for hundreds of years. It seemed dreadful that the town should blaze for ever in the same spot; dreadful at least to people going away to adventure upon the sea, and beholding it as a circumscribed mound, eternally burnt, eternally scarred. From the deck of the ship the great city appeared a crouched and cowardly figure, a sedentary miser.
\nOceanic Inspiration
\n\n
Winding veils round their heads, the women walked on deck. They were now moving steadily down the river, passing the dark shapes of ships at anchor, and London was a swarm of lights with a pale yellow canopy drooping above it. There were the lights of the great theatres, the lights of the long streets, lights that indicated huge squares of domestic comfort, lights that hung high in air.
\nNo darkness would ever settle upon those lamps, as no darkness had settled upon them for hundreds of years. It seemed dreadful that the town should blaze for ever in the same spot; dreadful at least to people going away to adventure upon the sea, and beholding it as a circumscribed mound, eternally burnt, eternally scarred. From the deck of the ship the great city appeared a crouched and cowardly figure, a sedentary miser.
\n![\"An](\"https://s.w.org/images/core/5.8/nature-above-01.jpg\")
![\"An](\"https://s.w.org/images/core/5.8/nature-above-02.jpg\")
![\"\"](\"https://s.w.org/patterns/files/2021/06/image-from-rawpixel-id-430289-jpeg-1-1024x1024.jpg\"){kind=tracking}
Opening
Party
\n\n\n\n\nOpening
Party
\n\n\n\n\nHÉLÈNE DUMAS
FRAGMENTS
\n\n\n\n20/4 — 9/9/2021
SOUTH LONDON ART GALLERY
\n\n\n\n\n\n\n\n![\"\"](\"https://mywptesting.site/wp-content/uploads/2021/06/Histoire_naturelle_..._-fragments-_-_Upper_cover_C108eee15-1.jpg\")
MORE INFO AT: WP.ORG · +44 21 1234 5678
\nINSTAGRAM · TICKETS
\nHÉLÈNE DUMAS
FRAGMENTS
\n\n\n\n20/4 — 9/9/2021
SOUTH LONDON ART GALLERY
\n\n\n\n\n\n\n\nMORE INFO AT: WP.ORG · +44 21 1234 5678
\nINSTAGRAM · TICKETS
\n![\"Image](\"https://s.w.org/patterns/files/2021/06/Group-17-scaled.jpg\")
Location:
82 Main St. Brooklyn, NY
Date:
October 24, 2021
Location:
82 Main St. Brooklyn, NY
Date:
October 24, 2021
We’re a studio in Berlin with an international practice in architecture, urban planning and interior design. We believe in sharing knowledge and promoting dialogue to increase the creative potential of collaboration.
\n\";s:9:\"protected\";b:0;}s:4:\"meta\";O:8:\"stdClass\":6:{s:10:\"spay_email\";s:0:\"\";s:13:\"wpop_keywords\";s:17:\"large text, title\";s:16:\"wpop_description\";s:12:\"Heading text\";s:19:\"wpop_viewport_width\";i:1200;s:16:\"wpop_block_types\";a:1:{i:0;s:12:\"core/heading\";}s:11:\"wpop_locale\";s:5:\"en_US\";}s:14:\"category_slugs\";a:2:{i:0;s:8:\"featured\";i:1;s:4:\"text\";}s:13:\"keyword_slugs\";a:1:{i:0;s:4:\"core\";}s:15:\"pattern_content\";s:621:\"\nWe\'re a studio in Berlin with an international practice in architecture, urban planning and interior design. We believe in sharing knowledge and promoting dialogue to increase the creative potential of collaboration.
\n\";}i:4;O:8:\"stdClass\":7:{s:2:\"id\";i:669;s:5:\"title\";O:8:\"stdClass\":1:{s:8:\"rendered\";s:31:\"Image and quote on a background\";}s:7:\"content\";O:8:\"stdClass\":2:{s:8:\"rendered\";s:3127:\"\n![\"\"](\"https://s.w.org/patterns/files/2021/06/pear-1-1024x1024.png\")
Even the bitterest fruit has sugar in it.
\n\n\n\n– Terry a O’Neal
\n![\"\"](\"https://s.w.org/patterns/files/2021/06/pear-half-1024x1024.png\")
The trees that are slow to grow bear the best fruit.
\n\n\n\n– Molière
\nEven the bitterest fruit has sugar in it.
\n\n\n\n– Terry a O\'Neal
\nThe trees that are slow to grow bear the best fruit.
\n\n\n\n– Molière
\n![\"\"](\"https://s.w.org/patterns/files/2021/06/wire-sculpture-263x300.jpg\")
Airplane
\n\n\n\nCopper wire, wood base. I created this piece in late 2008. For this work, I aimed to convey both the industrial heaviness of an airplane, but also the cloudlike floating quality you feel when you’re in one.
\nAirplane
\n\n\n\nCopper wire, wood base. I created this piece in late 2008. For this work, I aimed to convey both the industrial heaviness of an airplane, but also the cloudlike floating quality you feel when you’re in one.
\n![\"Vintage](\"https://s.w.org/patterns/files/2021/06/image-from-rawpixel-id-539759-jpeg-1-1024x1024.jpg\"){kind=tracking}
Cupid in Flight
48” x 48” Giclee print on archival paper.
Cupid in Flight
48” x 48” Giclee print on archival paper.
Forest.
\n\n\n\nEven a child knows how valuable the forest is. The fresh, breathtaking smell of trees. Echoing birds flying above that dense magnitude. A stable climate, a sustainable diverse life and a source of culture. Yet, forests and other ecosystems hang in the balance, threatened to become croplands, pasture, and plantations.
\nForest.
\n\n\n\nEven a child knows how valuable the forest is. The fresh, breathtaking smell of trees. Echoing birds flying above that dense magnitude. A stable climate, a sustainable diverse life and a source of culture. Yet, forests and other ecosystems hang in the balance, threatened to become croplands, pasture, and plantations.
\nOpen Spaces
\n\n\n\n\nOpen Spaces
\n\n\n\n\n![\"\"](\"https://s.w.org/patterns/files/2021/06/Iris-793x1024.jpg\")
White Irises
Ogawa Kazumasa
Cherry Blossom
Ogawa Kazumasa
![\"\"](\"https://s.w.org/patterns/files/2021/06/Cherry-Blossom-707x1024.jpg\")
White Irises
Ogawa Kazumasa
Cherry Blossom
Ogawa Kazumasa
Single
\n\n\n\nEnrich our growing community.
\n\n\n\n\n\n\n\n
- General admission and member discounts for one adult
- One free ticket per special exhibition
- Two single-use guest passes per year
Family
\n\n\n\nSupport special exhibitions.
\n\n\n\n\n\n\n\n
- General admission and member discounts for two adults
- Four free tickets per special exhibition
- Four single-use guest passes per year
Patron
\n\n\n\nTake support to the next level.
\n\n\n\n\n\n\n\n
- General admission and member discounts for two adults
- Five free tickets per special exhibition
- Six single-use guest passes per year
Single
\n\n\n\nEnrich our growing community.
\n\n\n\n\n\n\n\n
- General admission and member discounts for one adult
- One free ticket per special exhibition
- Two single-use guest passes per year
Family
\n\n\n\nSupport special exhibitions.
\n\n\n\n\n\n\n\n
- General admission and member discounts for two adults
- Four free tickets per special exhibition
- Four single-use guest passes per year
Patron
\n\n\n\nTake support to the next level.
\n\n\n\n\n\n\n\n
- General admission and member discounts for two adults
- Five free tickets per special exhibition
- Six single-use guest passes per year
GET IN TOUCH
\n\n\n\nSchedule a Visit
\n\n\n\nGET IN TOUCH
\n\n\n\nSchedule a Visit
\n\n\n\n\n\n\n\n\nVirtual Tour ↗
\n\n\n\nGet a virtual tour of the museum. Ideal for schools and events.
\nCurrent Shows ↗
\n\n\n\nStay updated and see our current exhibitions here.
\nUseful Info ↗
\n\n\n\nGet to know our opening times, ticket prices and discounts.
\nVirtual Tour ↗
\n\n\n\nGet a virtual tour of the museum. Ideal for schools and events.
\nCurrent Shows ↗
\n\n\n\nStay updated and see our current exhibitions here.
\nUseful Info ↗
\n\n\n\nGet to know our opening times, ticket prices and discounts.
\nECOSYSTEM
\n\n\n\nPositive growth.
\n\n\n\n\nNature, in the common sense, refers to essences unchanged by man; space, the air, the river, the leaf. Art is applied to the mixture of his will with the same things, as in a house, a canal, a statue, a picture. But his operations taken together are so insignificant, a little chipping, baking, patching, and washing, that in an impression so grand as that of the world on the human mind, they do not vary the result.
\nUndoubtedly we have no questions to ask which are unanswerable. We must trust the perfection of the creation so far, as to believe that whatever curiosity the order of things has awakened in our minds, the order of things can satisfy. Every man’s condition is a solution in hieroglyphic to those inquiries he would put.
\nECOSYSTEM
\n\n\n\nPositive growth.
\n\n\n\n\nNature, in the common sense, refers to essences unchanged by man; space, the air, the river, the leaf. Art is applied to the mixture of his will with the same things, as in a house, a canal, a statue, a picture. But his operations taken together are so insignificant, a little chipping, baking, patching, and washing, that in an impression so grand as that of the world on the human mind, they do not vary the result.
\nUndoubtedly we have no questions to ask which are unanswerable. We must trust the perfection of the creation so far, as to believe that whatever curiosity the order of things has awakened in our minds, the order of things can satisfy. Every man\'s condition is a solution in hieroglyphic to those inquiries he would put.
\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','','','2020-07-18 17:51:40','2020-07-18 17:51:40','',0,'https://legacy.chrismansfield.com/?page_id=2',0,'page','',0),(3,1,'2020-07-18 17:51:40','2020-07-18 17:51:40','Who we are
Our website address is: https://legacy.chrismansfield.com.
What personal data we collect and why we collect it
Comments
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
Media
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Contact forms
Cookies
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Analytics
Who we share your data with
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Your contact information
Additional information
How we protect your data
What data breach procedures we have in place
What third parties we receive data from
What automated decision making and/or profiling we do with user data
Industry regulatory disclosure requirements
','Privacy Policy','','draft','closed','open','','privacy-policy','','','2020-07-18 17:51:40','2020-07-18 17:51:40','',0,'https://legacy.chrismansfield.com/?page_id=3',0,'page','',0),(4,0,'2020-07-18 17:51:42','2020-07-18 17:51:42','\nComing soon.
\n','Attribution','','publish','closed','closed','','attribution','','','2020-07-18 17:51:42','2020-07-18 17:51:42','',0,'https://legacy.chrismansfield.com/attribution/',0,'bg_attribution','',0),(6,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','The New UMoMA Opens its Doors','','inherit','open','closed','','the-new-umoma-opens-its-doors','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/2020-landscape-1.png',0,'attachment','image/png',0),(7,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','The premier destination for modern art in Northern Sweden. Open from 10 AM to 6 PM every day during the summer months.
![\"\"](\"https://legacy.chrismansfield.com/wp-content/themes/twentytwenty/assets/images/2020-three-quarters-1.png\")
Works and Days
August 1 -- December 1
![\"\"](\"https://legacy.chrismansfield.com/wp-content/themes/twentytwenty/assets/images/2020-three-quarters-3.png\")
Theatre of Operations
October 1 -- December 1
![\"\"](\"https://legacy.chrismansfield.com/wp-content/themes/twentytwenty/assets/images/2020-three-quarters-2.png\")
The Life I Deserve
August 1 -- December 1
![\"\"](\"https://legacy.chrismansfield.com/wp-content/themes/twentytwenty/assets/images/2020-three-quarters-4.png\")
From Signac to Matisse
October 1 -- December 1
![\"\"](\"https://legacy.chrismansfield.com/wp-content/themes/twentytwenty/assets/images/2020-landscape-2.png\")
“Cyborgs, as the philosopher Donna Haraway established, are not reverent. They do not remember the cosmos.”
With seven floors of striking architecture, UMoMA shows exhibitions of international contemporary art, sometimes along with art historical retrospectives. Existential, political and philosophical issues are intrinsic to our programme. As visitor you are invited to guided tours artist talks, lectures, film screenings and other events with free admission
The exhibitions are produced by UMoMA in collaboration with artists and museums around the world and they often attract international attention. UMoMA has received a Special Commendation from the European Museum of the Year, and was among the top candidates for the Swedish Museum of the Year Award as well as for the Council of Europe Museum Prize.
Become a Member and Get Exclusive Offers!
Members get access to exclusive exhibits and sales. Our memberships cost $99.99 and are billed annually.
![\"\"](\"https://legacy.chrismansfield.com/wp-content/themes/twentytwenty/assets/images/2020-square-2.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/themes/twentytwenty/assets/images/2020-square-1.png\")
This is our geeky little gaming site for updates, campaign info and creative outbursts!.
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/logo.jpg\"){kind=logo}
The Current Player Characters
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/00000000000-605x1024.jpg\")
Cadeus (Vermin) Solaris ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0000000000.jpg\")
Dragon Fyre ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Kenny.jpg\")
Gwynn Brightfoot ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/temp_lord_telior-1.jpg\")
Ebron ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/po.jpg\")
Possessio ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/image1.jpeg\")
Gardel Servant of House Breckon ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/eliza.jpg\")
Eliza Pryce ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/02/guigu-z--724x1024.jpg\")
Craelor
Telempe (Givian the Good)
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/telempedragonform2.jpg\")
Silver Dragon ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/telempefinal.jpg\")
Human Form ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/telempe-attack.jpg\")
Harbor Attack
Lord Teo Easterly
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Lord-Teo-Easterly2-1.jpg\")
Lord Teo Easterly ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/teointerior-1.jpg\")
Interior of Lord Teo\'s Manor ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/teohouse-1.jpg\")
Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Roc.jpg\")
Roc ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Channel-theater-1024x585.jpg\")
The Channel Theater ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Veyhanna.jpg\")
Vey\'Hanna
The Pryces
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0justinia.jpg\")
Justinia Pryce ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/cliffshadow.jpg\")
Cliffshadow Keep ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Countessa-Pyrce.jpg\")
Countessa Pryce
The Breckons
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0b3.png\")
Duke Breckon ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0b2.png\")
Gareth Breckon ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Lady-Elsbeth-545x1024.jpg\")
Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/First-mate-weatherby-1.jpg\")
First Mate Weatherby ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/stefano-borella-sailor-big-765x1024.jpg\")
Stephano ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/524dd854938e4e6747c56b8c38630f44.jpg\")
Minn
Tree Elves of Ajagara
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-2.png\")
Earth Walker Druid ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-1.png\")
Earth Walker Scouts ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-4.png\")
Earth Walker Ranger ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed.jpg\")
The City in the Canopy ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-1.jpg\")
Jandar
Ajagara’s Yuan-ti
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0y.jpg\")
Tazeesh -A Pureblood ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0yuanti.jpg\")
A Malison ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Abomination2.jpg\")
An Abomination ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/e74121997ef8720cd8f85f6934d40cdf.jpg\")
A Pureblood ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/edf0bbf59678b2e4a43c205cb9f2a9f8.jpg\")
A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-3-1.png\")
Orn ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/bronze.jpg\")
Auraj ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/14460762_f1024.jpg\")
Qu\'mado ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/green-dragon.jpg\")
Achuak ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/blue.jpg\")
Ulhar ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/red.jpg\")
Char-Ir
Sevna
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/08/asev-847x1024.jpg\")
The Revenant waits ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/08/SEVNA-RESTORED.bmp\")
Sevna restored
The Current Player Characters
\n\n\n\nCadeus (Vermin) Solaris Dragon Fyre Gwynn Brightfoot Ebron Possessio Gardel Servant of House Breckon Eliza Pryce ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/02/sorin-markov-art.jpg\")
Craelor
In the Realms, Aeo and his Children are the primary gods of the humans of the Realms
\n\n\n\nThe Lore of Aeo and his Children
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/pasted-image-0.png\")
Aeo ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/pasted-image-0-1.png\")
Asdin ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed.png\")
D\'wyden ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/pasted-image-0-2.png\")
Daos-Das ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/angel-2-768x428-1.jpg\")
Azrael
The Dark Weaver and the Sisters of the Loom
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/08/Dark-Weaver.bmp\")
The Lore of Ajagara\'s Animists
\n\n\n\nAjagara’s Primordial Elementals: Arrianod, LLyr, Ceridwen, and Belanus
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/7c23c101e6c5a756991aa385584fdb70-elemental-magic-wind-elemental.jpg\")
Arrianod ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/7f55ee900d68e7e5768558249ba032d2.jpg\")
Llyr ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/d5ms9ei-848e3188-f1f2-41c0-b0d4-fb88e560383a-605x1024.jpg\")
Ceridwen ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/eb3c22962c04c92b75fd55b6377f92d5.jpg\")
Belanus
The Realms
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0amap-e1516227035901-768x563-1.jpg\")
Keepers Port (Garramond)
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/unnamed.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/fav2.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/fav.jpg\")
The Docks of Keepers Port
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/The-docks-of-Keepers-Port-scaled.jpg\")
The Underdark
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/tg.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/grak.png\")
Ajagara
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Ajagara.bmp\")
The City of Black Stone (formerly Breith)
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/the-city-of-black-stone1.jpg\")
The Current Player Characters
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/6b8af80112a9561fc305d0ba28dc1713.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/lp8jdvw6l9d71.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Chivalry_2_beginners_guide_17-1-1.jpeg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/5abe6ff5aadb6bfd1cd2eefd367405b0-edited.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/tumblr_6923a8cf3304e6fdf197397a30283d8c_d7b8d068_1280-edited.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/corelle.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/din.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/nil.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Pic_140.webp\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/giacomo.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/the-oracle.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Talya.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/numi.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/D7mMpxwWwAErXqj-742x1024.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/zarill.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/amalia.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/magra.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Ellis-and-Keen.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/2a6f4e51e65621f6001e63500d885cd9.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/elsbeth.webp\")
Telempe (Givian the Good)
\n\n\n\nLord Teo Easterly
\n\n\n\n\n\n\n\n
Roc a’ Danesh
\n\n\n\nThe Pryces
\n\n\n\nThe Breckons
\n\n\n\nThe Crew of Hayden\'s Serpant
\n\n\n\nTree Elves of Ajagara
\n\n\n\nAjagara’s Yuan-ti
\n\n\n\nThe Dragons of the Weyr: Metallics & Chromatics
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/0000-1.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/000-1.jpg\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/00-1.jpg\")
The Grey Cloaks of the Weyr
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/unnamed.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/unnamed-1.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/unnamed-2.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/unnamed-3.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/unnamed-4.png\")
Sevna
\n\n\n\nThe Construct
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/04/Construct-1024x791.jpg\")
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nTazeesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Qu\'mand Auraj Achuak Ulhar Char-Ir
Sevna
\n\n\n\nThe Revenant waits Sevna restored
The premier destination for modern art in Northern Sweden. Open from 10 AM to 6 PM every day during the summer months.
Works and Days
August 1 -- December 1
Theatre of Operations
October 1 -- December 1
The Life I Deserve
August 1 -- December 1
From Signac to Matisse
October 1 -- December 1
“Cyborgs, as the philosopher Donna Haraway established, are not reverent. They do not remember the cosmos.”
With seven floors of striking architecture, UMoMA shows exhibitions of international contemporary art, sometimes along with art historical retrospectives. Existential, political and philosophical issues are intrinsic to our programme. As visitor you are invited to guided tours artist talks, lectures, film screenings and other events with free admission
The exhibitions are produced by UMoMA in collaboration with artists and museums around the world and they often attract international attention. UMoMA has received a Special Commendation from the European Museum of the Year, and was among the top candidates for the Swedish Museum of the Year Award as well as for the Council of Europe Museum Prize.
Become a Member and Get Exclusive Offers!
Members get access to exclusive exhibits and sales. Our memberships cost $99.99 and are billed annually.
Welcome to your site! This is your homepage, which is what most visitors will see when they come to your site for the first time.
\n','Home','','inherit','closed','closed','','15-revision-v1','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',15,'https://legacy.chrismansfield.com/2020/07/18/15-revision-v1/',0,'revision','',0),(30,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','The Pantheon','','inherit','closed','closed','','19-revision-v1','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',19,'https://legacy.chrismansfield.com/2020/07/18/19-revision-v1/',0,'revision','',0),(31,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','World','','inherit','closed','closed','','20-revision-v1','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',20,'https://legacy.chrismansfield.com/2020/07/18/20-revision-v1/',0,'revision','',0),(32,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','The PCs','','inherit','closed','closed','','21-revision-v1','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',21,'https://legacy.chrismansfield.com/2020/07/18/21-revision-v1/',0,'revision','',0),(33,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','The NPCs','','inherit','closed','closed','','22-revision-v1','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',22,'https://legacy.chrismansfield.com/2020/07/18/22-revision-v1/',0,'revision','',0),(34,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','Factions and Organizations','','inherit','closed','closed','','23-revision-v1','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',23,'https://legacy.chrismansfield.com/2020/07/18/23-revision-v1/',0,'revision','',0),(35,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','Home','','publish','closed','closed','','home','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/home/',1,'nav_menu_item','',0),(36,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','DMs Discussion','','publish','closed','closed','','dms-blog','','','2020-08-16 19:57:54','2020-08-16 19:57:54','',0,'https://legacy.chrismansfield.com/2020/07/18/dms-blog/',2,'nav_menu_item','',0),(37,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','Yelp','','publish','closed','closed','','yelp','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/yelp/',0,'nav_menu_item','',0),(38,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','Facebook','','publish','closed','closed','','facebook','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/facebook/',1,'nav_menu_item','',0),(39,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','Twitter','','publish','closed','closed','','twitter','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/twitter/',2,'nav_menu_item','',0),(40,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','Instagram','','publish','closed','closed','','instagram','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/instagram/',3,'nav_menu_item','',0),(41,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','Email','','publish','closed','closed','','email','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/email/',4,'nav_menu_item','',0),(45,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','Email','','publish','closed','closed','','email-2','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/email-2/',4,'nav_menu_item','',0),(46,1,'2020-07-18 18:10:37','2020-07-18 18:10:37',' ','','','publish','closed','closed','','46','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/46/',4,'nav_menu_item','',0),(47,1,'2020-07-18 18:10:37','2020-07-18 18:10:37',' ','','','publish','closed','closed','','47','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/47/',5,'nav_menu_item','',0),(48,1,'2020-07-18 18:10:37','2020-07-18 18:10:37',' ','','','publish','closed','closed','','48','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/48/',6,'nav_menu_item','',0),(49,1,'2020-07-18 18:10:37','2020-07-18 18:10:37','','The World','','publish','closed','closed','','the-world','','','2020-07-18 18:10:37','2020-07-18 18:10:37','',0,'https://legacy.chrismansfield.com/2020/07/18/the-world/',3,'nav_menu_item','',0),(50,1,'2020-07-18 18:11:51','2020-07-18 18:11:51','','0amap-e1516227035901-768x563-1','','inherit','open','closed','','0amap-e1516227035901-768x563-1','','','2020-07-18 18:11:51','2020-07-18 18:11:51','',20,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0amap-e1516227035901-768x563-1.jpg',0,'attachment','image/jpeg',0),(138,1,'2020-07-18 21:35:19','2020-07-18 21:35:19','\n\n\n\n\n
This is our geeky little gaming site for updates, campaign info and creative outbursts!.
\n\n\n\nThe Realms
\n\n\n\nKeepers Port (Garramond)
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Legacy-Map-Keepers-Port-1-819x1024.jpg\")
The Docks of Keepers Port
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/The-docks-of-Keepers-Port-1024x791.jpg\")
Ajagara
\n\n\n\nThe City of Black Stone (formerly Breith)
\n\n\n\nThe Realms
\n\n\n\nKeepers Port (Garramond)
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Legacy-Map-Keepers-Port-1-scaled.jpg\")
The Docks of Keepers Port
\n\n\n\nAjagara
\n\n\n\nThe City of Black Stone (formerly Breith)
\n\n\n\nThe Realms
\n\n\n\nKeepers Port (Garramond)
\n\n\n\nThe Docks of Keepers Port
\n\n\n\nAjagara
\n\n\n\nThe City of Black Stone (formerly Breith)
\n\n\n\nIn the Realms, Aeo and his Children are the primary gods of the humans of the Realms
\n\n\n\nThe Lore of Aeo and his Children
\n\n\n\nAeo Asdin D\'wyden Daos-Das Azrael
Ajagara’s Primordial Elementals: Arrianod, LLyr, Ceridwen, and Belanus
\n\n\n\nThe Lore of Ajagara\'s Animists
\n\n\n\nArrianod Llyr Ceridwen Belanus
In the Realms, Aeo and his Children are the primary gods of the humans of the Realms
\n\n\n\nThe Lore of Aeo and his Children
\n\n\n\nAeo Asdin D\'Wyden Daos-Das Azrael
Ajagara’s Primordial Elementals: Arrianod, LLyr, Ceridwen, and Belanus
\n\n\n\nThe Lore of Ajagara\'s Animists
\n\n\n\nArrianod Llyr Ceridwen Belanus
The Current Player Characters
\n\n\n\nCadeus (Vermin) Solaris Dragon Fyre Gwynn Brightfoot Possessio Gardel Servant of House Breckon Eliza Pryce Craelor ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/02/Ebron2.jpg\")
Ebron
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n','Original Art','','inherit','closed','closed','','138-revision-v1','','','2020-08-16 20:36:18','2020-08-16 20:36:18','',138,'https://legacy.chrismansfield.com/2020/08/16/138-revision-v1/',0,'revision','',0),(246,1,'2020-08-16 20:41:40','2020-08-16 20:41:40','\n
\n\n\n\nRevenge is poorly spent passion. Vengeance is justice.
She had been too long in the City. The cold, dark, and emptiness closed off her heart, her humanity, her pain.
\n\n\n\nNow she stood on a hillside overlooking the City of Black Stone. A warm breeze fluttered her tattered robes as she surveyed her fallen kingdom once more.
\n\n\n\nHer withered heart ached for the beauty and light that had been lost, no, taken. The ache sparked, but she snuffed the growing rage. She had come here to learn.
\n\n\n\nThe strangers were easy to track but hard to see. Some type of arcane camouflage hid their movements in their camp. She could sense that the nature witch was already recovered and that another of their party was very stealthily stalking her, but she could glean little else.
\n\n\n\nShe had learned much from their conversation. They knew him, but they didn\'t know who he was, not really. The irony forced a broken smile across her face. In another life, she hadn\'t known him at all. She had learned much from their conversation.
\n\n\n\nShe felt the sun rising behind her. Moving all day and all night, she could watch the next sunrise from the shore. While she looked for their boat.
\n\n\n\nThe Current Player Characters
\n\n\n\nCadeus (Vermin) Solaris Dragon Fyre ![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0000000.jpg\")
Craelor Gwynn Brightfoot Ebron Possessio Gardel Servant of House Breckon Eliza Pryce
The Current Player Characters
\n\n\n\nCadeus (Vermin) Solaris Dragon Fyre Craelor Gwynn Brightfoot Ebron Possessio Gardel Servant of House Breckon Eliza Pryce
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/asev-847x1024.jpg\")
\n\n\n\n\n\n\n\nRevenge is poorly spent passion. Vengeance is justice.
Sevna
\n\n\n\nShe had been too long in the City. The cold, dark, and emptiness closed off her heart, her humanity, her pain.
\n\n\n\nNow she stood on a hillside overlooking the City of Black Stone. A warm breeze fluttered her tattered robes as she surveyed her fallen kingdom once more.
\n\n\n\nHer withered heart ached for the beauty and light that had been lost, no, taken. The ache sparked, but she snuffed the growing rage. She had come here to learn.
\n\n\n\nThe strangers were easy to track but hard to see. Some type of arcane camouflage hid their movements in their camp. She could sense that the nature witch was already recovered and that another of their party was very stealthily stalking her, but she could glean little else.
\n\n\n\nShe had learned much from their conversation. They knew him, but they didn\'t know who he was, not really. The irony forced a broken smile across her face. In another life, she hadn\'t known him at all. She had learned much from their conversation.
\n\n\n\nShe felt the sun rising behind her. Moving all day and all night, she could watch the next sunrise from the shore. While she looked for their boat.
\n','NPC\'s POVs','','inherit','closed','closed','','138-revision-v1','','','2020-07-19 00:12:00','2020-07-19 00:12:00','',138,'https://legacy.chrismansfield.com/2020/07/19/138-revision-v1/',0,'revision','',0),(184,1,'2020-07-19 00:11:42','2020-07-19 00:11:42','','7925cfec587be50ede609307c94b317f','','inherit','open','closed','','7925cfec587be50ede609307c94b317f','','','2020-07-19 00:11:42','2020-07-19 00:11:42','',138,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/7925cfec587be50ede609307c94b317f.jpg',0,'attachment','image/jpeg',0),(176,1,'2020-07-18 23:25:57','2020-07-18 23:25:57','','asev','','inherit','open','closed','','asev','','','2020-07-18 23:25:57','2020-07-18 23:25:57','',138,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/asev.jpg',0,'attachment','image/jpeg',0),(177,1,'2020-07-18 23:32:17','2020-07-18 23:32:17','\n\n\n\n\n\n\n\n\nRevenge is poorly spent passion. Vengeance is justice.
Sevna
\n\n\n\nShe had been too long in the City. The cold, dark, and emptiness closed off her heart, her humanity, her pain.
\n\n\n\nNow she stood on a hillside overlooking the City of Black Stone. A warm breeze fluttered her tattered robes as she surveyed her fallen kingdom once more.
\n\n\n\nHer withered heart ached for the beauty and light that had been lost, no, taken. The ache sparked, but she snuffed the growing rage. She had come here to learn.
\n\n\n\nThe strangers were easy to track but hard to see. Some type of arcane camouflage hid their movements in their camp. She could sense that the nature witch was already recovered and that another of their party was very stealthily stalking her, but she could glean little else.
\n\n\n\nShe had learned much from their conversation. They knew him, but they didn\'t know who he was, not really. The irony forced a broken smile across her face. In another life, she hadn\'t known him at all. She had learned much from their conversation.
\n\n\n\nShe felt the sun rising behind her. Moving all day and all night, she could watch the next sunrise from the shore. While she looked for their boat.
\n','NPC\'s POVs','','inherit','closed','closed','','138-revision-v1','','','2020-07-18 23:32:17','2020-07-18 23:32:17','',138,'https://legacy.chrismansfield.com/2020/07/18/138-revision-v1/',0,'revision','',0),(106,1,'2020-07-18 21:03:20','2020-07-18 21:03:20','','Countessa-Pyrce','','inherit','open','closed','','countessa-pyrce','','','2020-07-18 21:03:20','2020-07-18 21:03:20','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Countessa-Pyrce.jpg',0,'attachment','image/jpeg',0),(107,1,'2020-07-18 21:03:30','2020-07-18 21:03:30','','cliffshadow','','inherit','open','closed','','cliffshadow','','','2020-07-18 21:03:30','2020-07-18 21:03:30','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/cliffshadow.jpg',0,'attachment','image/jpeg',0),(108,1,'2020-07-18 21:06:41','2020-07-18 21:06:41','','Lady-Elsbeth','','inherit','open','closed','','lady-elsbeth','','','2020-07-18 21:06:41','2020-07-18 21:06:41','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Lady-Elsbeth.jpg',0,'attachment','image/jpeg',0),(181,1,'2020-07-19 00:02:18','2020-07-19 00:02:18','','StoneDiceBanner_V1_1600x','','inherit','open','closed','','stonedicebanner_v1_1600x','','','2020-07-19 00:02:18','2020-07-19 00:02:18','',15,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/StoneDiceBanner_V1_1600x.png',0,'attachment','image/png',0),(109,1,'2020-07-18 21:08:07','2020-07-18 21:08:07','','First-mate-weatherby','','inherit','open','closed','','first-mate-weatherby','','','2020-07-18 21:08:07','2020-07-18 21:08:07','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/First-mate-weatherby.jpg',0,'attachment','image/jpeg',0),(110,1,'2020-07-18 21:10:13','2020-07-18 21:10:13','','0b2','','inherit','open','closed','','0b2','','','2020-07-18 21:10:13','2020-07-18 21:10:13','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0b2.png',0,'attachment','image/png',0),(111,1,'2020-07-18 21:10:33','2020-07-18 21:10:33','','0b3','','inherit','open','closed','','0b3','','','2020-07-18 21:10:33','2020-07-18 21:10:33','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/0b3.png',0,'attachment','image/png',0),(112,1,'2020-07-18 21:12:13','2020-07-18 21:12:13','','First-mate-weatherby-1','','inherit','open','closed','','first-mate-weatherby-1','','','2020-07-18 21:12:13','2020-07-18 21:12:13','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/First-mate-weatherby-1.jpg',0,'attachment','image/jpeg',0),(113,1,'2020-07-18 21:12:25','2020-07-18 21:12:25','','stefano-borella-sailor-big','','inherit','open','closed','','stefano-borella-sailor-big','','','2020-07-18 21:12:25','2020-07-18 21:12:25','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/stefano-borella-sailor-big.jpg',0,'attachment','image/jpeg',0),(114,1,'2020-07-18 21:12:32','2020-07-18 21:12:32','','524dd854938e4e6747c56b8c38630f44','','inherit','open','closed','','524dd854938e4e6747c56b8c38630f44','','','2020-07-18 21:12:32','2020-07-18 21:12:32','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/524dd854938e4e6747c56b8c38630f44.jpg',0,'attachment','image/jpeg',0),(115,1,'2020-07-18 21:14:27','2020-07-18 21:14:27','','unnamed-1','','inherit','open','closed','','unnamed-1','','','2020-07-18 21:14:27','2020-07-18 21:14:27','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-1.jpg',0,'attachment','image/jpeg',0),(116,1,'2020-07-18 21:14:28','2020-07-18 21:14:28','','unnamed-1','','inherit','open','closed','','unnamed-1-2','','','2020-07-18 21:14:28','2020-07-18 21:14:28','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-1.png',0,'attachment','image/png',0),(117,1,'2020-07-18 21:14:29','2020-07-18 21:14:29','','unnamed-2','','inherit','open','closed','','unnamed-2','','','2020-07-18 21:14:29','2020-07-18 21:14:29','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-2.jpg',0,'attachment','image/jpeg',0),(118,1,'2020-07-18 21:14:30','2020-07-18 21:14:30','','unnamed-2','','inherit','open','closed','','unnamed-2-2','','','2020-07-18 21:14:30','2020-07-18 21:14:30','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-2.png',0,'attachment','image/png',0),(119,1,'2020-07-18 21:14:31','2020-07-18 21:14:31','','unnamed-3','','inherit','open','closed','','unnamed-3','','','2020-07-18 21:14:31','2020-07-18 21:14:31','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-3.jpg',0,'attachment','image/jpeg',0),(120,1,'2020-07-18 21:14:32','2020-07-18 21:14:32','','unnamed-3','','inherit','open','closed','','unnamed-3-2','','','2020-07-18 21:14:32','2020-07-18 21:14:32','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-3.png',0,'attachment','image/png',0),(121,1,'2020-07-18 21:14:33','2020-07-18 21:14:33','','unnamed','','inherit','open','closed','','unnamed-4','','','2020-07-18 21:14:33','2020-07-18 21:14:33','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed.jpg',0,'attachment','image/jpeg',0),(122,1,'2020-07-18 21:14:34','2020-07-18 21:14:34','','unnamed-4','','inherit','open','closed','','unnamed-4-2','','','2020-07-18 21:14:34','2020-07-18 21:14:34','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/unnamed-4.png',0,'attachment','image/png',0),(151,1,'2020-07-18 22:23:03','2020-07-18 22:23:03','','astral-plane-traveller','','inherit','open','closed','','astral-plane-traveller','','','2020-07-18 22:23:03','2020-07-18 22:23:03','',19,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/astral-plane-traveller.jpg',0,'attachment','image/jpeg',0),(152,1,'2020-07-18 22:23:12','2020-07-18 22:23:12','\nIn the Realms, Aeo and his Children are the primary gods of the humans of the Realms
\n\n\n\nThe Lore of Aeo and his Children
\n\n\n\nAeo Asdin D\'wyden Daos-Das Azrael
Ajagara’s Primordial Elementals: Arrianod, LLyr, Ceridwen, and Belanus
\n\n\n\nThe Lore of Ajagara\'s Animists
\n\n\n\nArrianod Llyr Ceridwen Belanus
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/teo-2.jpg\")
Lord Teo Renovations Interior of Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nZaneesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Qumado Auraj Achuak Ulhar Char-Ir
The Realms
\n\n\n\nKeepers Port (Garramond)
\n\n\n\nThe Docks of Keepers Port
\n\n\n\nThe Underdark
\n\n\n\nAjagara
\n\n\n\nThe City of Black Stone (formerly Breith)
\n\n\n\nThe party had left the humidity and heat of Yuan-Ti Basin to explore the City of Black Stone. Here , they hoped to find the Vessel that bound the Marid who held their boat. As they scouted the uncanny remains of a once thriving culture, they discovered many oddities. It seemed the heart of the city radiated an impenetrable darkness. A darkness that was slowing and steadily sucking the energy out of its surroundings, leaving even the high outer walls of the city cold to the touch.
\n\n\n\nAs they navigated the quadrants of the city, they came upon several clues of its origins and demise. This lead them the grand home of an Animist named Teoatlay. The lord of the house was not at home, but a revenant lay in wait. After a frustrating discussion with the single-minded Sevna, the party had new leads to follow.
\n\n\n\nEventually, they found the Temple of the Air. Using their combined abilities they were able to penetrate its passages and puzzles to find the object they sought-the Shell of Compulsion. Taking it, however, triggered the appearance of its guardians. We pick up our tale, as the party makes a mad dash to escape the ziggurat and its elemental forces...
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/61314.hq_-1.jpg\")
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Lord-Teo-Easterly2.jpg\")
Lord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nZaneesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Qumado Auraj Achuak Ulhar Char-Ir
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Lord-Teo-Easterly.gif\")
Lord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nZaneesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Qumado Auraj Achuak Ulhar Char-Ir
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n','Original Art','','inherit','closed','closed','','138-revision-v1','','','2020-07-30 14:35:03','2020-07-30 14:35:03','',138,'https://legacy.chrismansfield.com/2020/07/30/138-revision-v1/',0,'revision','',0),(200,1,'2020-07-20 23:19:01','2020-07-20 23:19:01','\n
\n\n\n\n\n\n\n\nRevenge is poorly spent passion. Vengeance is justice.
Sevna
\n\n\n\nShe had been too long in the City. The cold, dark, and emptiness closed off her heart, her humanity, her pain.
\n\n\n\nNow she stood on a hillside overlooking the City of Black Stone. A warm breeze fluttered her tattered robes as she surveyed her fallen kingdom once more.
\n\n\n\nHer withered heart ached for the beauty and light that had been lost, no, taken. The ache sparked, but she snuffed the growing rage. She had come here to learn.
\n\n\n\nThe strangers were easy to track but hard to see. Some type of arcane camouflage hid their movements in their camp. She could sense that the nature witch was already recovered and that another of their party was very stealthily stalking her, but she could glean little else.
\n\n\n\nShe had learned much from their conversation. They knew him, but they didn\'t know who he was, not really. The irony forced a broken smile across her face. In another life, she hadn\'t known him at all. She had learned much from their conversation.
\n\n\n\nShe felt the sun rising behind her. Moving all day and all night, she could watch the next sunrise from the shore. While she looked for their boat.
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/the-city-of-black-stone.jpg\")
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n','POVS','','inherit','closed','closed','','138-revision-v1','','','2020-08-16 20:33:40','2020-08-16 20:33:40','',138,'https://legacy.chrismansfield.com/2020/08/16/138-revision-v1/',0,'revision','',0),(201,1,'2020-07-20 23:23:15','2020-07-20 23:23:15','','po2-1','','inherit','open','closed','','po2-1','','','2020-07-20 23:23:15','2020-07-20 23:23:15','',21,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/po2-1.jpg',0,'attachment','image/jpeg',0),(202,1,'2020-07-20 23:23:45','2020-07-20 23:23:45','','po3-1','','inherit','open','closed','','po3-1','','','2020-07-20 23:23:45','2020-07-20 23:23:45','',21,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/po3-1.jpg',0,'attachment','image/jpeg',0),(258,1,'2021-02-18 20:53:28','2021-02-18 20:53:28','','shadar-kai','','inherit','open','closed','','shadar-kai','','','2021-02-18 20:53:28','2021-02-18 20:53:28','',21,'https://legacy.chrismansfield.com/wp-content/uploads/2021/02/shadar-kai.jpg',0,'attachment','image/jpeg',0),(205,1,'2020-07-21 01:16:36','2020-07-21 01:16:36','','Lord-Teo-Easterly2-1','','inherit','open','closed','','lord-teo-easterly2-1','','','2020-07-21 01:16:36','2020-07-21 01:16:36','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2020/07/Lord-Teo-Easterly2-1.jpg',0,'attachment','image/jpeg',0),(206,1,'2020-07-21 01:17:10','2020-07-21 01:17:10','\n
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nZaneesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Qumado Auraj Achuak Ulhar Char-Ir
The party had left the humidity and heat of Yuan-Ti Basin to explore the City of Black Stone. Here , they hoped to find the Vessel that bound the Marid who held their boat. As they scouted the uncanny remains of a once thriving culture, they discovered many oddities. It seemed the heart of the city radiated an impenetrable darkness. A darkness that was slowing and steadily sucking the energy out of its surroundings, leaving even the high outer walls of the city cold to the touch.
\n\n\n\nAs they navigated the quadrants of the city, they came upon several clues of its origins and demise. This lead them the grand home of an Animist named Teoatlay. The lord of the house was not at home, but a revenant lay in wait. After a frustrating discussion with the single-minded Sevna, the party had new leads to follow.
\n\n\n\nEventually, they found the Temple of the Air. Using their combined abilities they were able to penetrate its passages and puzzles to find the object they sought-the Shell of Compulsion. Taking it, however, triggered the appearance of its guardians. We pick up our tale, as the party makes a mad dash to escape the ziggurat and its elemental forces...
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/07/61314.hq_.jpg\")
The party had left the humidity and heat of Yuan-Ti Basin to explore the City of Black Stone. Here , they hoped to find the Vessel that bound the Marid who held their boat. As they scouted the uncanny remains of a once thriving culture, they discovered many oddities. It seemed the heart of the city radiated an impenetrable darkness. A darkness that was slowing and steadily sucking the energy out of its surroundings, leaving even the high outer walls of the city cold to the touch.
\n\n\n\nAs they navigated the quadrants of the city, they came upon several clues of its origins and demise. This lead them the grand home of an Animist named Teoatlay. The lord of the house was not at home, but a revenant lay in wait. After a frustrating discussion with the single-minded Sevna, the party had new leads to follow.
\n\n\n\nEventually, they found the Temple of the Air. Using their combined abilities they were able to penetrate its passages and puzzles to find the object they sought-the Shell of Compulsion. Taking it, however, triggered the appearance of its guardians. We pick up our tale, as the party makes a mad dash to escape the ziggurat and its elemental forces...
\n\n\n\nThe party had left the humidity and heat of Yuan-Ti Basin to explore the City of Black Stone. Here , they hoped to find the Vessel that bound the Marid who held their boat. As they scouted the uncanny remains of a once thriving culture, they discovered many oddities. It seemed the heart of the city radiated an impenetrable darkness. A darkness that was slowing and steadily sucking the energy out of its surroundings, leaving even the high outer walls of the city cold to the touch.
\n\n\n\nAs they navigated the quadrants of the city, they came upon several clues of its origins and demise. This lead them the grand home of an Animist named Teoatlay. The lord of the house was not at home, but a revenant lay in wait. After a frustrating discussion with the single-minded Sevna, the party had new leads to follow.
\n\n\n\nEventually, they found the Temple of the Air. Using their combined abilities they were able to penetrate its passages and puzzles to find the object they sought-the Shell of Compulsion. Taking it, however, triggered the appearance of its guardians. We pick up our tale, as the party makes a mad dash to escape the ziggurat and its elemental forces...
\n\n\n\nThe party had left the humidity and heat of Yuan-Ti Basin to explore the City of Black Stone. Here , they hoped to find the Vessel that bound the Marid who held their boat. As they scouted the uncanny remains of a once thriving culture, they discovered many oddities. It seemed the heart of the city radiated an impenetrable darkness. A darkness that was slowing and steadily sucking the energy out of its surroundings, leaving even the high outer walls of the city cold to the touch.
\n\n\n\nAs they navigated the quadrants of the city, they came upon several clues of its origins and demise. This lead them the grand home of an Animist named Teoatlay. The lord of the house was not at home, but a revenant lay in wait. After a frustrating discussion with the single-minded Sevna, the party had new leads to follow.
\n\n\n\nEventually, they found the Temple of the Air. Using their combined abilities they were able to penetrate its passages and puzzles to find the object they sought-the Shell of Compulsion. Taking it, however, triggered the appearance of its guardians. We pick up our tale, as the party makes a mad dash to escape the ziggurat and its elemental forces...
\n\n\n\nTelempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nZaneesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Qumado Auraj Achuak Ulhar Char-Ir
Sevna
\n\n\n\nThe Revenant waits Sevan restored
In the Realms, Aeo and his Children are the primary gods of the humans of the Realms
\n\n\n\nThe Lore of Aeo and his Children
\n\n\n\nAeo Asdin D\'wyden Daos-Das Azrael
Ajagara’s Primordial Elementals: Arrianod, LLyr, Ceridwen, and Belanus
\n\n\n\nThe Dark Weaver and the Sisters of the Loom
\n\n\n\nThe Lore of Ajagara\'s Animists
\n\n\n\nArrianod Llyr Ceridwen Belanus
In the Realms, Aeo and his Children are the primary gods of the humans of the Realms
\n\n\n\nThe Lore of Aeo and his Children
\n\n\n\nAeo Asdin D\'wyden Daos-Das Azrael
Ajagara’s Primordial Elementals: Arrianod, LLyr, Ceridwen, and Belanus
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2020/08/The-Dark-Weaver-and-her-Sisters.bmp\")
The Sisters of the Loom
\nThe Lore of Ajagara\'s Animists
\n\n\n\nArrianod Llyr Ceridwen Belanus
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nZaneesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Qumado Auraj Achuak Ulhar Char-Ir
Sevna
\n\n\n\nThe Revenant waits Sevna restored
In the Realms, Aeo and his Children are the primary gods of the humans of the Realms
\n\n\n\nThe Lore of Aeo and his Children
\n\n\n\nAeo Asdin D\'wyden Daos-Das Azrael
The Dark Weaver and the Sisters of the Loom
\n\n\n\nThe Lore of Ajagara\'s Animists
\n\n\n\nAjagara’s Primordial Elementals: Arrianod, LLyr, Ceridwen, and Belanus
\n\n\n\nArrianod Llyr Ceridwen Belanus
In the Realms, Aeo and his Children are the primary gods of the humans of the Realms
\n\n\n\nThe Lore of Aeo and his Children
\n\n\n\nAeo Asdin D\'wyden Daos-Das Azrael
Ajagara’s Primordial Elementals: Arrianod, LLyr, Ceridwen, and Belanus
\n\n\n\nThe Dark Weaver and the Sisters of the Loom
\n\n\n\nThe Lore of Ajagara\'s Animists
\n\n\n\nArrianod Llyr Ceridwen Belanus
Our party defeated the guardians of the Temple of the Winds and secured the arcane object which they sought, the Conch of Binding. By removing the object from the power of the summoning chamber and blowing into it, Craelor was able to call forth and free the Marid they had encountered upon their arrival to Ajagara.
\n\n\n\nThe grateful Marid granted the party one wish. An intense discussion ensued. Eventually, our heroes decided that they would restore the Revenant of Sevna to the world of the living. As we return to our tale, our adventurers find themselves bathed in a pool of light and witnesses to the resurrection of the god-queen of Breith.
\n\n\n\nThe Revenant waits... Sevna Reborn
Our party defeated the guardians of the Temple of the Winds and secured the arcane object which they sought, the Conch of Binding. By removing the object from the power of the summoning chamber and blowing into it, Craelor was able to call forth and free the Marid they had encountered upon their arrival to Ajagara.
\n\n\n\nThe grateful Marid granted the party one wish. An intense discussion ensued. Eventually, our heroes decided that they would restore the Revenant of Sevna to the world of the living. As we return to our tale, our adventurers find themselves bathed in a pool of light and witnesses to the resurrection of the god-queen of Breith.
\n\n\n\nThe Revenant waits... Sevna Reborn
\n\n\n\nRevenge is poorly spent passion. Vengeance is justice.
She had been too long in the City. The cold, dark, and emptiness closed off her heart, her humanity, her pain.
\n\n\n\nNow she stood on a hillside overlooking the City of Black Stone. A warm breeze fluttered her tattered robes as she surveyed her fallen kingdom once more.
\n\n\n\nHer withered heart ached for the beauty and light that had been lost, no, taken. The ache sparked, but she snuffed the growing rage. She had come here to learn.
\n\n\n\nThe strangers were easy to track but hard to see. Some type of arcane camouflage hid their movements in their camp. She could sense that the nature witch was already recovered and that another of their party was very stealthily stalking her, but she could glean little else.
\n\n\n\nShe had learned much from their conversation. They knew him, but they didn\'t know who he was, not really. The irony forced a broken smile across her face. In another life, she hadn\'t known him at all. She had learned much from their conversation.
\n\n\n\nShe felt the sun rising behind her. Moving all day and all night, she could watch the next sunrise from the shore. While she looked for their boat.
\n\n\n\nTelempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nTazeesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Qumado Auraj Achuak Ulhar Char-Ir
Sevna
\n\n\n\nThe Revenant waits Sevna restored
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nTazeesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Auraj Qu\'Mand Achuak Ulhar Char-Ir
Sevna
\n\n\n\nThe Revenant waits Sevna restored
The Current Player Characters
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2021/03/0-1.jpg\")
Gwenn Briarfoot
The Current Player Characters
\n\n\n\nCadeus Dragon Fyre Possessio Gardel Eliza Pryce Craelor Ebron Gwenn Briarfoot
The Current Player Characters
\n\n\n\nGwenn Briarfoot
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nTazeesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Weyr: Metallics & Chromatics
\n\n\n\nOrn Auraj Qu\'Mando Achuak Ulhar Char-Ir
Sevna
\n\n\n\nThe Revenant waits Sevna restored
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nTazeesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Dragons of the Weyr: Metallics & Chromatics
\n\n\n\nOrn Auraj Auraj-Human Form Qu\'Mando Qu\'mando-female Qu\'Mando-male Ulhar Char-Ir Achuak
The Grey Cloaks of the Weyr
\n\n\n\nVena- Hall Master Nala -Arms Master Kali-Hunt Master Billings-Lore Master Dox-Keeper of the Caves
Sevna
\n\n\n\nThe Revenant waits Sevna restored
The Current Player Characters
\n\n\n\nThe Current Player Characters
\n\n\n\nCadeus Dragon Fyre Possessio Gardel Eliza Pryce Craelor Ebron Gwenn Briarfoot
Telempe (Givian the Good)
\n\n\n\nSilver Dragon Human Form Harbor Attack
Lord Teo Easterly
\n\n\n\nLord Teo Easterly Interior of Lord Teo\'s Manor Lord Teo\'s Manor
\n\n\n\n
Roc a’ Danesh
\n\n\n\nRoc The Channel Theater Vey\'Hanna
The Pryces
\n\n\n\nJustinia Pryce Cliffshadow Keep Countessa Pryce
The Breckons
\n\n\n\nDuke Breckon Gareth Breckon Elsbeth Breckon
The Crew of Hayden\'s Serpant
\n\n\n\nFirst Mate Weatherby Stephano Minn
Tree Elves of Ajagara
\n\n\n\nEarth Walker Druid Earth Walker Scouts Earth Walker Ranger The City in the Canopy Jandar
Ajagara’s Yuan-ti
\n\n\n\nTazeesh -A Pureblood A Malison An Abomination A Pureblood A Mage Hunter
The Dragons of the Weyr: Metallics & Chromatics
\n\n\n\nOrn Auraj Auraj-Human Form Qu\'Mando Qu\'mando-female Qu\'Mando-male Ulhar Char-Ir Achuak
The Grey Cloaks of the Weyr
\n\n\n\nVena- Hall Master Nala -Arms Master Kali-Hunt Master Billings-Lore Master Dox-Keeper of the Caves
Sevna
\n\n\n\nThe Revenant waits Sevna restored
The Construct
\n\n\n\n\n\n\n\n
The Current Player Characters
\n\n\n\nThe Current Player Characters
\n\n\n\nThe Current Player Characters
\n\n\n\nThe wise ones say it is easier to tell our darkest troubles to a perfect stranger than to our closest ally. Perhaps that stranger is the key to solving those troubles for you. Perhaps that stranger needs something you have as well. Perhaps, this is what Zarill thought when he unloaded his sordid tale of sexual escapades, angry exes, and bastard children to our adventurers.
\n\n\n\nSitting in the Shattered Spire, a tavern built on a broken stalagmite on the outskirts of the Dark Lake district of Gracklstugh, our heroes considered Zarill’s story, his motivations, and his proposal. They had come to the cavern city through its subterranean port. The journey had been dangerous, and the docks were a welcome sight, despite the constant clanging and acrid smoke produced by its numerous and nonstop Dwarven forges. They had barely taken two steps off the docks when Zarill found them. A few hours later, they had a mission, a treasure, travel passes, and most importantly, the promise of Krenka’s location when they solved Zarill’s little problem.
![](\"https://lh5.googleusercontent.com/BAGBwUgeIP-wnscoJ-D2QX_CABm2PdO7HzDp1GwPszcc9y-1uoVBFEZCTnKsxUD4DmI6MQD-XRM6PBoiwZ5UJOjH6ss8xI8FJs4yBUwQ3DXFM_hoBubeV_yH3YIlEDhGans9uwis7z6mVOsyTg\")
Despite Ebron’s assurance that Zarill’s words were truthful, the party set out with a sense of unease. The mission itself was fraught with unknowns. They were to rescue a ten-year-old teifling child from a human mother who didn’t want it. They were to exchange the child for an item Zarill assured them she would desire. They were to bring the child back to Zarill to become a wanted and loved member of Zarill’s impressive brood. But “what ifs” abound. As they entered the impressive granite gates of Gracklstugh our party discussed various hypotheticals. What if the mother doesn’t want to trade the child? What if the child doesn’t want to go? What if the child is not actually ill-used? What if the child is, but still doesn’t want to go? Gwen suggested heavy reconnaissance was needed and the party agreed. It was time to return to Trader’s Gate, Mei\'q Videnn in the local tongue.
![](\"https://lh6.googleusercontent.com/Z-JBTNi7neo1obK1mPrB-gANtDQoB3Q9U7twO9BR5Y-HcWYPWG4w6-om-JylzzNQIP063T2ZE3m16Cb0TJOdggGR9yp9GhKcOaJMnvHM99jGf-N2ozIb-mNn4sDSZ3CyjRYBQmhwsBk6B9a3wA\")
The return trip turned out to be a bit of a contest. First Po, Eliza, and Ebron had to prove their strength against the Duergar’s test before they were allowed to pilot the cars. Vermin and Craelor used their dark vision to assist, and the journey turned into a race. Ebron’s cart was victorious, but the celebration was short-lived as the parties disembarked and faced the task at hand.
\n\n\n\nUnable to contain their curiosity, Gwen and Ebron peered into the treasure bag that Zarill had entrusted to them. What they found turned out to be no mere treasure. Gwen passed the object around for inspection. Yulanue knew this to be a powerful artifact called a Cubic Gate. Po identified some of the runes as being elemental in nature and began testing it. They opened a hole to what appeared to be The plane of Fire, Water, and the Asterion’s dining hall, where Ebron’s father and mother sat having their soup.
![](\"https://lh5.googleusercontent.com/x_i4iouGbVfPk9_lGURIepD99iCEUJ6N0Uphw1kPCJwuk3bfbGIds55ASk062wuC3QO_k6UBRJOIk10WygsVhd6Zvgt3rXDbbM2L9iYNrCmNtNTMHZGaS2J9DNRm1kN-YMJwu5O6B1gVjNGdew\")
Now, the party has even more questions. Should this merchant, Amalia Durnholde, have this artifact? Should Zerill? Should anyone?
\n\n\n\nThe Party must now decide how best to navigate the investigation ahead, the choices that await, and the dangerous byways of Trader’s Gate.
\n','When last we left out intrepid adventurers...','','publish','open','open','','when-last-we-left-out-intrepid-adventurers','','','2022-05-22 17:20:48','2022-05-22 17:20:48','',0,'https://legacy.chrismansfield.com/?p=318',0,'post','',0),(319,1,'2022-05-22 13:17:42','2022-05-22 13:17:42','','tiefling_bard_custom_dnd_char_comission_by_caioesantos_dayxmvm-fullview','','inherit','open','closed','','tiefling_bard_custom_dnd_char_comission_by_caioesantos_dayxmvm-fullview','','','2022-05-22 13:17:42','2022-05-22 13:17:42','',318,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/tiefling_bard_custom_dnd_char_comission_by_caioesantos_dayxmvm-fullview.jpg',0,'attachment','image/jpeg',0),(320,1,'2022-05-22 13:19:16','2022-05-22 13:19:16','','tiefling_bard_custom_dnd_char_comission_by_caioesantos_dayxmvm-fullview-1','','inherit','open','closed','','tiefling_bard_custom_dnd_char_comission_by_caioesantos_dayxmvm-fullview-1','','','2022-05-22 13:19:16','2022-05-22 13:19:16','',318,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/tiefling_bard_custom_dnd_char_comission_by_caioesantos_dayxmvm-fullview-1.jpg',0,'attachment','image/jpeg',0),(322,1,'2022-05-22 15:53:14','2022-05-22 15:53:14','\nThe wise ones say it is easier to tell our darkest troubles to a perfect stranger than to our closest ally. Perhaps that stranger is the key to solving those troubles for you. Perhaps that stranger needs something you have as well. Perhaps, this is what Zarill thought when he unloaded his sordid tale of sexual escapades, angry exes, and bastard children to our adventurers.
\n\n\n\nSitting in the Shattered Spire, a tavern that sat on a broken stalagmite on the outskirts of the Dark Lake district of Gracklstugh, our heroes considered Zarill’s story, his motivations, and his proposal. They had come to the cavern city through its subterranean port. The journey had been dangerous, and the docks were a welcome sight, despite the constant clanging and acrid smoke produced by its numerous and nonstop Dwarven forges. They had barely taken two steps off the docks when Zarill found them. A few hours later, they had a mission, a treasure, travel passes, and most importantly, the promise of Krenka’s location when they solved Zarill’s little problem.
Despite Ebron’s assurance that Zarill’s words were truthful, the party set out with a sense of unease. The mission itself was fraught with unknowns. They were to rescue a ten-year-old teifling child from a human mother who didn’t want it. They were to exchange the child for an item Zarill assured them she would desire. They were to bring the child back to Zarill to become a wanted and loved member of Zarill’s impressive brood. But “what ifs” abound. As they entered the impressive granite gates of Gracklstugh our party discussed various hypotheticals. What if the mother doesn’t want to trade the child? What if the child doesn’t want to go? What if the child is no actually ill-used? What if the child is, but still doesn’t want to go? Gwen suggested heavy reconnaissance was needed and the party agreed. It was time to return to Trader’s Gate, Mei\'q Videnn in the local tongue.
The return trip turned out to be a bit of a contest. First Po, Eliza, Ebron had to prove their strength against the Duergar’s test, before they were allowed to pilot the cars. Vermin and Craelor used their dark vision to assist, and the journey turned into a race. Ebron’s cart was victorious, but the celebration was short lived as the parties disembarked and faced the task at hand.
\n\n\n\nUnable to contain their curiosity, Gwen and Ebron peered into the treasure bag that Zarill had entrusted to them. What they found turned out to be no mere treasure. Gwen passed the object around for inspection. Yulanue knew this to be a powerful artifact called a Cubic Gate. Po identified some of the runes as being elemental in nature and began testing it. They opened a hole to what appeared to be The plane of Fire, Water, and the Asterion’s dining hall, where Ebron’s father and mother sat having their soup.
Now, the party has even more questions. Should this merchant, Amalia Durnholde, have this artifact? Should Zerill? Should anyone?
\n\n\n\nThe Party must now decide how best to navigate the investigation ahead, the choices that await, and the dangerous byways of Trader’s Gate.
\n','When last we left out intrepid adventurers...','','inherit','closed','closed','','318-revision-v1','','','2022-05-22 15:53:14','2022-05-22 15:53:14','',318,'https://legacy.chrismansfield.com/?p=322',0,'revision','',0),(321,1,'2022-05-22 15:47:45','2022-05-22 15:47:45','','Gracklstugh','','inherit','open','closed','','gracklstugh','','','2022-05-22 15:47:45','2022-05-22 15:47:45','',318,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Gracklstugh.webp',0,'attachment','image/webp',0),(349,1,'2022-05-22 17:20:48','2022-05-22 17:20:48','\nThe wise ones say it is easier to tell our darkest troubles to a perfect stranger than to our closest ally. Perhaps that stranger is the key to solving those troubles for you. Perhaps that stranger needs something you have as well. Perhaps, this is what Zarill thought when he unloaded his sordid tale of sexual escapades, angry exes, and bastard children to our adventurers.
\n\n\n\nSitting in the Shattered Spire, a tavern built on a broken stalagmite on the outskirts of the Dark Lake district of Gracklstugh, our heroes considered Zarill’s story, his motivations, and his proposal. They had come to the cavern city through its subterranean port. The journey had been dangerous, and the docks were a welcome sight, despite the constant clanging and acrid smoke produced by its numerous and nonstop Dwarven forges. They had barely taken two steps off the docks when Zarill found them. A few hours later, they had a mission, a treasure, travel passes, and most importantly, the promise of Krenka’s location when they solved Zarill’s little problem.
Despite Ebron’s assurance that Zarill’s words were truthful, the party set out with a sense of unease. The mission itself was fraught with unknowns. They were to rescue a ten-year-old teifling child from a human mother who didn’t want it. They were to exchange the child for an item Zarill assured them she would desire. They were to bring the child back to Zarill to become a wanted and loved member of Zarill’s impressive brood. But “what ifs” abound. As they entered the impressive granite gates of Gracklstugh our party discussed various hypotheticals. What if the mother doesn’t want to trade the child? What if the child doesn’t want to go? What if the child is not actually ill-used? What if the child is, but still doesn’t want to go? Gwen suggested heavy reconnaissance was needed and the party agreed. It was time to return to Trader’s Gate, Mei\'q Videnn in the local tongue.
The return trip turned out to be a bit of a contest. First Po, Eliza, and Ebron had to prove their strength against the Duergar’s test before they were allowed to pilot the cars. Vermin and Craelor used their dark vision to assist, and the journey turned into a race. Ebron’s cart was victorious, but the celebration was short-lived as the parties disembarked and faced the task at hand.
\n\n\n\nUnable to contain their curiosity, Gwen and Ebron peered into the treasure bag that Zarill had entrusted to them. What they found turned out to be no mere treasure. Gwen passed the object around for inspection. Yulanue knew this to be a powerful artifact called a Cubic Gate. Po identified some of the runes as being elemental in nature and began testing it. They opened a hole to what appeared to be The plane of Fire, Water, and the Asterion’s dining hall, where Ebron’s father and mother sat having their soup.
Now, the party has even more questions. Should this merchant, Amalia Durnholde, have this artifact? Should Zerill? Should anyone?
\n\n\n\nThe Party must now decide how best to navigate the investigation ahead, the choices that await, and the dangerous byways of Trader’s Gate.
\n','When last we left out intrepid adventurers...','','inherit','closed','closed','','318-revision-v1','','','2022-05-22 17:20:48','2022-05-22 17:20:48','',318,'https://legacy.chrismansfield.com/?p=349',0,'revision','',0),(332,1,'2022-05-22 16:27:26','2022-05-22 16:27:26','','Talya','','inherit','open','closed','','talya','','','2022-05-22 16:27:26','2022-05-22 16:27:26','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Talya.png',0,'attachment','image/png',0),(333,1,'2022-05-22 16:27:26','2022-05-22 16:27:26','','giacomo','','inherit','open','closed','','giacomo','','','2022-05-22 16:27:26','2022-05-22 16:27:26','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/giacomo.png',0,'attachment','image/png',0),(335,1,'2022-05-22 16:41:27','2022-05-22 16:41:27','','D7mMpxwWwAErXqj','','inherit','open','closed','','d7mmpxwwwaerxqj','','','2022-05-22 16:41:27','2022-05-22 16:41:27','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/D7mMpxwWwAErXqj.jpg',0,'attachment','image/jpeg',0),(334,1,'2022-05-22 16:41:22','2022-05-22 16:41:22','','43721a532eca3d3fdf448621881a2417','','inherit','open','closed','','43721a532eca3d3fdf448621881a2417','','','2022-05-22 16:41:22','2022-05-22 16:41:22','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/43721a532eca3d3fdf448621881a2417.jpg',0,'attachment','image/jpeg',0),(336,1,'2022-05-22 16:41:27','2022-05-22 16:41:27','','Pic_140-1','','inherit','open','closed','','pic_140-1','','','2022-05-22 16:41:27','2022-05-22 16:41:27','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Pic_140-1.webp',0,'attachment','image/webp',0),(339,1,'2022-05-22 16:47:03','2022-05-22 16:47:03','','D7mMpxwWwAErXqj-2','','inherit','open','closed','','d7mmpxwwwaerxqj-2','','','2022-05-22 16:47:03','2022-05-22 16:47:03','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/D7mMpxwWwAErXqj-2.jpg',0,'attachment','image/jpeg',0),(337,1,'2022-05-22 16:41:47','2022-05-22 16:41:47','','D7mMpxwWwAErXqj-1','','inherit','open','closed','','d7mmpxwwwaerxqj-1','','','2022-05-22 16:41:47','2022-05-22 16:41:47','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/D7mMpxwWwAErXqj-1.jpg',0,'attachment','image/jpeg',0),(338,1,'2022-05-22 16:47:03','2022-05-22 16:47:03','','zarill','','inherit','open','closed','','zarill','','','2022-05-22 16:47:03','2022-05-22 16:47:03','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/zarill.jpg',0,'attachment','image/jpeg',0),(340,1,'2022-05-22 16:47:03','2022-05-22 16:47:03','','Amalia','','inherit','open','closed','','amalia','','','2022-05-22 16:47:03','2022-05-22 16:47:03','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Amalia.png',0,'attachment','image/png',0),(341,1,'2022-05-22 16:47:04','2022-05-22 16:47:04','','riki','','inherit','open','closed','','riki','','','2022-05-22 16:47:04','2022-05-22 16:47:04','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/riki.png',0,'attachment','image/png',0),(342,1,'2022-05-22 16:47:05','2022-05-22 16:47:05','','magra','','inherit','open','closed','','magra','','','2022-05-22 16:47:05','2022-05-22 16:47:05','',22,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/magra.png',0,'attachment','image/png',0),(358,1,'2022-05-30 23:49:38','2022-05-30 23:49:38','\nTelempe (Givian the Good)
\n\n\n\nLord Teo Easterly
\n\n\n\n\n\n\n\n
Roc a’ Danesh
\n\n\n\nThe Pryces
\n\n\n\nThe Breckons
\n\n\n\nThe Crew of Hayden\'s Serpant
\n\n\n\nTree Elves of Ajagara
\n\n\n\nAjagara’s Yuan-ti
\n\n\n\nThe Dragons of the Weyr: Metallics & Chromatics
\n\n\n\nThe Grey Cloaks of the Weyr
\n\n\n\nSevna
\n\n\n\nThe Construct
\n\n\n\n![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/Amalia.png\")
![\"\"](\"https://legacy.chrismansfield.com/wp-content/uploads/2022/05/4izav97tf6951.webp\")
Telempe (Givian the Good)
\n\n\n\nLord Teo Easterly
\n\n\n\n\n\n\n\n
Roc a’ Danesh
\n\n\n\nThe Pryces
\n\n\n\nThe Breckons
\n\n\n\nThe Crew of Hayden\'s Serpant
\n\n\n\nTree Elves of Ajagara
\n\n\n\nAjagara’s Yuan-ti
\n\n\n\nThe Dragons of the Weyr: Metallics & Chromatics
\n\n\n\nThe Grey Cloaks of the Weyr
\n\n\n\nSevna
\n\n\n\nThe Construct
\n\n\n\nTelempe (Givian the Good)
\n\n\n\nLord Teo Easterly
\n\n\n\n\n\n\n\n
Roc a’ Danesh
\n\n\n\nThe Pryces
\n\n\n\nThe Breckons
\n\n\n\nThe Crew of Hayden\'s Serpant
\n\n\n\nTree Elves of Ajagara
\n\n\n\nAjagara’s Yuan-ti
\n\n\n\nThe Dragons of the Weyr: Metallics & Chromatics
\n\n\n\nThe Grey Cloaks of the Weyr
\n\n\n\nSevna
\n\n\n\nThe Construct
\n\n\n\nTelempe (Givian the Good)
\n\n\n\nLord Teo Easterly
\n\n\n\n\n\n\n\n
Roc a’ Danesh
\n\n\n\nThe Pryces
\n\n\n\nThe Breckons
\n\n\n\nThe Crew of Hayden\'s Serpant
\n\n\n\nTree Elves of Ajagara
\n\n\n\nAjagara’s Yuan-ti
\n\n\n\nThe Dragons of the Weyr: Metallics & Chromatics
\n\n\n\nThe Grey Cloaks of the Weyr
\n\n\n\nSevna
\n\n\n\nThe Construct
\n\n\n\nThe wise ones say it is easier to tell our darkest troubles to a perfect stranger than to our closest ally. Perhaps that stranger is the key to solving those troubles for you. Perhaps that stranger needs something you have as well. Perhaps, this is what Zarill thought when he unloaded his sordid tale of sexual escapades, angry exes, and bastard children to our adventurers.
\n\n\n\nSitting in the Shattered Spire, a tavern built on a broken stalagmite on the outskirts of the Dark Lake district of Gracklstugh, our heroes considered Zarill’s story, his motivations, and his proposal. They had come to the cavern city through its subterranean port. The journey had been dangerous, and the docks were a welcome sight, despite the constant clanging and acrid smoke produced by its numerous and nonstop Dwarven forges. They had barely taken two steps off the docks when Zarill found them. A few hours later, they had a mission, a treasure, travel passes, and most importantly, the promise of Krenka’s location when they solved Zarill’s little problem.
Despite Ebron’s assurance that Zarill’s words were truthful, the party set out with a sense of unease. The mission itself was fraught with unknowns. They were to rescue a ten-year-old teifling child from a human mother who didn’t want it. They were to exchange the child for an item Zarill assured them she would desire. They were to bring the child back to Zarill to become a wanted and loved member of Zarill’s impressive brood. But “what ifs” abound. As they entered the impressive granite gates of Gracklstugh our party discussed various hypotheticals. What if the mother doesn’t want to trade the child? What if the child doesn’t want to go? What if the child is not actually ill-used? What if the child is, but still doesn’t want to go? Gwen suggested heavy reconnaissance was needed and the party agreed. It was time to return to Trader’s Gate, Mei\'q Videnn in the local tongue.
The return trip turned out to be a bit of a contest. First Po, Eliza, Ebron had to prove their strength against the Duergar’s test before they were allowed to pilot the cars. Vermin and Craelor used their dark vision to assist, and the journey turned into a race. Ebron’s cart was victorious, but the celebration was short-lived as the parties disembarked and faced the task at hand.
\n\n\n\nUnable to contain their curiosity, Gwen and Ebron peered into the treasure bag that Zarill had entrusted to them. What they found turned out to be no mere treasure. Gwen passed the object around for inspection. Yulanue knew this to be a powerful artifact called a Cubic Gate. Po identified some of the runes as being elemental in nature and began testing it. They opened a hole to what appeared to be The plane of Fire, Water, and the Asterion’s dining hall, where Ebron’s father and mother sat having their soup.
Now, the party has even more questions. Should this merchant, Amalia Durnholde, have this artifact? Should Zerill? Should anyone?
\n\n\n\nThe Party must now decide how best to navigate the investigation ahead, the choices that await, and the dangerous byways of Trader’s Gate.
\n','When last we left out intrepid adventurers...','','inherit','closed','closed','','318-autosave-v1','','','2022-05-22 17:20:37','2022-05-22 17:20:37','',318,'https://legacy.chrismansfield.com/?p=348',0,'revision','',0),(350,1,'2022-05-22 17:26:23','2022-05-22 17:26:23','','fav2','','inherit','open','closed','','fav2','','','2022-05-22 17:26:23','2022-05-22 17:26:23','',20,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/fav2.jpg',0,'attachment','image/jpeg',0),(351,1,'2022-05-22 17:26:23','2022-05-22 17:26:23','','unnamed','','inherit','open','closed','','unnamed-7','','','2022-05-22 17:26:23','2022-05-22 17:26:23','',20,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/unnamed.jpg',0,'attachment','image/jpeg',0),(352,1,'2022-05-22 17:26:23','2022-05-22 17:26:23','','fav','','inherit','open','closed','','fav','','','2022-05-22 17:26:23','2022-05-22 17:26:23','',20,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/fav.jpg',0,'attachment','image/jpeg',0),(353,1,'2022-05-22 17:28:48','2022-05-22 17:28:48','','tg','','inherit','open','closed','','tg','','','2022-05-22 17:28:48','2022-05-22 17:28:48','',20,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/tg.jpg',0,'attachment','image/jpeg',0),(354,1,'2022-05-22 17:28:53','2022-05-22 17:28:53','','grak','','inherit','open','closed','','grak','','','2022-05-22 17:28:53','2022-05-22 17:28:53','',20,'https://legacy.chrismansfield.com/wp-content/uploads/2022/05/grak.png',0,'attachment','image/png',0),(355,1,'2022-05-22 17:29:56','2022-05-22 17:29:56','\nThe Realms
\n\n\n\nKeepers Port (Garramond)
\n\n\n\nThe Docks of Keepers Port
\n\n\n\nThe Underdark
\n\n\n\nAjagara
\n\n\n\nThe City of Black Stone (formerly Breith)
\n\n\n\nTelempe (Givian the Good)
\n\n\n\nLord Teo Easterly
\n\n\n\n\n\n\n\n
Roc a’ Danesh
\n\n\n\nThe Pryces
\n\n\n\nThe Breckons
\n\n\n\nThe Crew of Hayden\'s Serpant
\n\n\n\nTree Elves of Ajagara
\n\n\n\nAjagara’s Yuan-ti
\n\n\n\nThe Dragons of the Weyr: Metallics & Chromatics
\n\n\n\nThe Grey Cloaks of the Weyr
\n\n\n\nSevna
\n\n\n\nThe Construct
\n\n\n\n