


<p>Due to the great many interconnected parts of full-site editing (FSE) that will make their debut in 5.9, contributors are organizing a more coordinated testing effort and have prepared <a href="https://make.wordpress.org/test/2021/11/30/help-test-wordpress-5-9-features/">a detailed guide</a>. It includes testing instructions for all the major features in the next release, including the template editor workflow, new theme blocks (focusing on the new Navigation Block), list view, expanded block design tools, the Gallery block refactor, Block Pattern explorer, and more general core updates.</p>



<p>If this is the first time you&#8217;re dipping your toes in the the new FSE features, you may be wondering what it&#8217;s supposed to look like. Anne McCarthy, who is co-leading testing for the release, has published several videos demonstrating the new features over the past few months. The video below is all about the new Navigation Block and another recent one <a href="https://www.youtube.com/watch?v=r59aR1tmY6k">explores block theme flows, styling, the patterns explorer</a>, and more. Sometimes it&#8217;s easier to get started testing if you see it working in a video first. </p>



<div class="wp-block-embed__wrapper">

</div>



<p>Version 5.9 will also introduce WordPress&#8217; first block-based default theme, Twenty Twenty-Two. Testing the theme is as easy as activating it from the Themes screen after installing 5.9 beta 1, as outlined in the testing guide:</p>



<blockquote class="wp-block-quote"><p>You can test the theme by installing the Beta and activating Twenty Twenty-Two from Appearance > Themes. To report issues with the theme, <a rel="noreferrer noopener" href="https://github.com/WordPress/twentytwentytwo/issues" target="_blank">you can do so here</a>.</p></blockquote>



<div class="wp-block-image"><img /></div>



<p>Just a handful of <a href="https://github.com/WordPress/gutenberg/issues/36556">pending issues and blockers</a> remain for 5.9, but the release already contains 580 enhancements and nearly 450 bug fixes. More beta releases are planned for December, followed by RC 1 on January 4, 2022. WordPress 5.9 is still on track to be released on January 25.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Dec 2021 04:00:11 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:31;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:65:"WPTavern: One Month Left To Take the 2021 WordPress Annual Survey";s:7:"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=126326";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:175:"https://wptavern.com/one-month-left-to-take-the-2021-wordpress-annual-survey?utm_source=rss&utm_medium=rss&utm_campaign=one-month-left-to-take-the-2021-wordpress-annual-survey";s: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:6317:"<p class="has-drop-cap">Last month, Josepha Haden Chomphosy <a href="https://wordpress.org/news/2021/11/take-the-2021-wordpress-annual-survey-and-view-the-2020-results/">announced the annual WordPress survey</a>. If you have not gotten around to participating, it is still open for the rest of 2021, leaving everyone another 30 days to answer.</p>



<p>The survey is relatively short. I finished it in 16 minutes, but I also took screenshots in case I needed to loop back to anything. There is also an optional WordPress contributors survey at the end, which took another 10 minutes to complete. However, it has more open-ended questions and could take much longer to complete for those with a lot of feedback.</p>



<p>The annual survey is available in the following six languages, but more may be considered for 2022:</p>



<ul><li><a href="https://wordpressdotorg.survey.fm/wordpress-2021-survey-english">English</a></li><li><a href="https://wordpressdotorg.survey.fm/wordpress-2021-survey-french">French</a></li><li><a href="https://wordpressdotorg.survey.fm/wordpress-2021-survey-german">German</a></li><li><a href="https://wordpressdotorg.survey.fm/wordpress-2021-survey-japanese">Japanese</a></li><li><a href="https://wordpressdotorg.survey.fm/wordpress-2021-survey-russian">Russian</a></li><li><a href="https://wordpressdotorg.survey.fm/wordpress-2021-survey-spanish">Spanish</a></li></ul>



<p>In the announcement, Haden Chomphosy stressed the importance of participating for WordPress users and professionals:</p>



<blockquote class="wp-block-quote"><p>Key takeaways and trends that emerge from this survey often find their way into the annual State of the Word address, are shared in the public project blogs, and can influence the direction and strategy for the WordPress Project.</p><p>Simply put: this survey helps those who build WordPress understand more about how the software is used, and by whom. The survey also helps leaders in the WordPress open source project learn more about our contributors&#8217; experiences.&#8221;</p></blockquote>



<p>Haden Chomphosy also announced that next year&#8217;s survey would take on a new format. She did not reveal any information outside of saying the included segments and questions would be included in that format change. That is still a year out, so we will have to wait and see what it looks like.</p>



<p>I would welcome some changes for what feels like the same-old-same-old survey that I have responded to in much the same way. My professional usage of WordPress has changed in the last two years, so I can now answer some questions from a different perspective. But, part of me feels like I am not adding as much value as newer voices.</p>



<p>One of the changes I would like to see is a separation of the annual and contributor surveys. By the time I finished the first, I had mostly lost interest in the second. It would be easier to come back to the contributor survey with a fresh mind at a different time.</p>



<p>Haden Chomphosy also linked to a <a href="https://wordpress.org/news/files/2021/11/WordPress.org-2020-Annual-Survey.pdf">164-page PDF of the 2020 survey results</a>. It includes breakdowns and insights into the data.</p>



<p>After a poor showing for the 2019 survey results, 2020 had nearly triple the respondents and was the highest since 2015. Here is a look at the last six years, excluding 2018, of completed surveys:</p>



<ul><li><strong>2015</strong> &#8211; 45,995</li><li><strong>2016</strong> &#8211; 15,585</li><li><strong>2017</strong> &#8211; 16,245</li><li><strong>2019</strong> &#8211; 6,203</li><li><strong>2020</strong> &#8211; 17,295</li></ul>



<h2 id="open-ended-questions">Open-Ended Questions</h2>



<p class="has-drop-cap">My favorite questions from the survey are those that are open-ended. These allow people to provide unique or more nuanced answers in comparison to checkboxes and radio inputs. Of course, it can be a mess to wade through the results when you have 1,000s of replies. I tried to keep these short in the survey. However, wanted to expand a bit on some of them below.</p>



<p><strong>What&#8217;s the best thing about WordPress?</strong></p>



<p>The community is always what is best about WordPress. You do not need to be a lead developer or a well-known business owner to make waves in the project. There are ways of contributing, making a living, or having an impact through dozens of avenues.</p>



<p>I started out blogging about things I learned in my development pursuits and building free plugins/themes. I never thought about whether I was making any sort of real change for the overall project. I just found a home with people who liked what I was doing. As I think back upon my early years, the WordPress community has always been welcoming.</p>



<p>Everyone has their own onramps into the WordPress ecosystem, and the more pathways we can carve out for other people, the better.</p>



<p><strong>Select three essential plugins from the 20 most popular.</strong></p>



<p>I almost feel like I am missing out. I have rarely used any plugin from the most popular list on sites I have worked on in the last few years.</p>



<p>Akismet is almost a given. WP Tavern uses Jetpack as an essential tool, and I have deployed it for various reasons with some builds. But, I am a bit of an outlier. I typically use stock WordPress with custom plugins. There are not many that I consider essential.</p>



<p>In the survey, the list was made up of September 2019&#8217;s top 20 most popular plugins. I reached out to Haden Chomphosy to verify if that was the correct date. She confirmed it was and said that the list has not changed substantially since then.</p>



<p><strong>For your next website project, which platform would you choose?</strong></p>



<p>The available answers to this question, such as Squarespace, Medium, and Wix, seemed geared more toward end-users than professionals or developers. While they represent popular alternatives, I would also like to see how the data might look if we overhaul this question in future surveys.</p>



<p>What happens if we split this question between users and developers? For example, are devs also building projects on top of Laravel, Symfony, and other frameworks or technologies outside of WordPress?</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Dec 2021 02:13:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:32;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:65:"HeroPress: How I Became a WordPress Evangelist in About Two 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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=4296";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:182:"https://heropress.com/essays/how-i-became-a-wordpress-evangelist-in-about-two-weeks/#utm_source=rss&utm_medium=rss&utm_campaign=how-i-became-a-wordpress-evangelist-in-about-two-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8916:"<img width="1024" height="512" src="https://heropress.com/wp-content/uploads/2021/12/113021-min.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: I imagine I'll always come back to WordPress." /><h2>How It Started</h2>
<p>When I first discovered WordPress, I wasn’t looking to start a web design business, or build websites for other people at all. That happened many years later. I came into the WordPress-i-verse simply because I needed to build a website for myself.</p>
<p>Back in 2009, I was a freelance illustrator and graphic designer. I was looking for a way to develop a website to showcase my work. In the past I had always created my sites from scratch, using basic HTML and CSS. This time I needed to get a site up and running in just a week or two. I also needed it to look professional and I didn’t want to learn an entirely new language. I wanted to stay as far away from back-end stuff as possible, so I could focus on the front-end design. I also wanted something low-cost and easy to maintain over time.</p>
<p>I know, right? Why didn’t I also ask for a flying car and a Star Trek food generator while I was at it? I knew it was a tall order, but I started hunting the internet anyway.</p>
<p>First, I tried out a couple of different CMS tools like Joomla and Drupal, but I found them too complex for what I needed at that moment. Then, going completely in the other direction, I messed around with uber easy builder platforms like Wix and Weebly. It was fun to design and build on those platforms, but I didn’t like the branded options. I couldn’t be sure that even if I did pay for the non-branded option, the platforms would still be around in the years to come (Spoiler alert: they are. Oh well).</p>
<p>Then, I stumbled upon WordPress.</p>
<p>At first, I thought WordPress would be similar to Drupal so I didn’t get my hopes up. I was completely prepared to keep looking under internet rocks to find a better solution. But like the intrepid little tech monster I am, I went ahead and installed it on my domain. The first thing I noticed was that the dashboard was well-organized and super intuitive. I could quickly get into settings and configure things as I needed. It was also easy to figure out what Themes and Plugins were without expending too much brainpower, which is always very precious in my head.</p>
<p>Because my site was brand new and unknown beyond my home office, I had the luxury of building things and tearing them down again without fear of visitors getting confused (what visitors?). I experimented with different plugins and explored several ways of setting up a gallery of my work. I felt a little like a mad scientist. Rather than wireframe a site and build with a solid plan, I allowed myself to create willy-nilly. I think that’s ultimately what got me hooked on WordPress. I didn’t sit down with a step-by-step manual, I sort of dove in and geeked out on messing things up and failing often.</p>
<blockquote><p>I had nothing to lose, which sometimes is the best way to explore a new system.</p></blockquote>
<p>Eventually, I did buckle down and create a more solid layout plan. I also did get into the back-end more than I intended, and it turns out I enjoyed that quite a bit. After a couple of weeks, my site was “ready for prime time” and I started sending out the link to art directors. Periodically – and somewhat randomly – I tweaked things according to what I thought wasn’t working for the visitors I wanted and what might work better.</p>
<p>After that first site, I slowly built more WordPress sites for myself, my family, and my friends. Every time I learned something new and every time I solidified my love for WordPress.</p>
<p>After 12 years using WordPress I’ve gone back to developing a solid plan before creating a new site. Even though I don’t use traditional wireframing for WordPress sites, I still draw up little layout sketches so at least I know where I’m headed. WordPress is so familiar to me now that I no longer spend time experimenting with basic stuff. However, I still enjoy breaking things now and then just to keep my skills sharp.</p>
<h2>What I Love About WordPress</h2>
<p>It’s hard to choose just one reason that I still love building sites in WordPress. From the intuitive dashboard menu to the thousands of plugins that help me (almost infinitely) expand what I can do with my site, there’s just so much to keep me in the ecosystem.</p>
<p>There’s the global WordPress community that has taught me – and saved me many times – throughout the years. I can’t count how many posts I’ve combed through in the wordpress.org support forums, looking for that one little nugget of information that would fix something I completely borked on the first try. Now that I know more about what I’m doing, I’ve been able to pay it forward by helping others to do the same. There’s also the vast community of WordPress users on Twitter, many with whom I’ve developed solid friendships over the years.</p>
<blockquote><p>However, if I were tied to a chair and threatened to be devoured by wolverines unless I gave just one answer, it would be that I own my content.</p></blockquote>
<p>Open-source is fascinating to me. Community-developed tech is always my first choice when it comes to software and hardware. It’s not always a practical choice, because I do have to work with other humans around the globe. So my primary working laptop is a Mac. But using and supporting platforms like WordPress is incredibly important to me because I believe the more we do that the more we retain the ability to own what we create.</p>
<p>There are always the people who will say, “WordPress is dead.” They were saying it in 2009, yet here we still are. I don’t believe WordPress is dying anytime soon, mostly because of the open-source, community-driven nature of the platform.</p>
<p>Is it for everyone? No. There are people I encounter today who I’ll steer towards SquareSpace or Wix. Usually, those are the ones who I get a sense just need things to work without trying very hard and need the kind of tech support you get from a mega-company like Apple or Microsoft. To them, WordPress was probably dead on arrival, but I don’t worry about that. The kind of people who get into using WordPress are the scrappier, “I’m-going-to-figure-this-out-if-it-kills-me” types.</p>
<p>Count me in that category.</p>
<h2>How I Use WordPress Now</h2>
<p>Over the last couple of years, I’ve expanded my knowledge of PHP, MySQL, and CSS to the point where I can make a WordPress site do pretty much anything I want. I’ve set up WooCommerce stores, photo galleries, membership sites, news feed sites, and business directories. I’ve learned to customize pages using CSS, bending layouts to my will and whimsy.</p>
<p>WordPress, like most software, is always evolving. Some people hate those evolutions, others merely tolerate it, but I love it. I admit that I’m not always thrilled with each change as they’re launched – in fact, sometimes I’m downright dumbfounded – but as a whole I feel that change is good.</p>
<p>For example, when Gutenberg blocks were introduced, I did everything I could, as long as I could, to keep designing and posting using the classic editor. After taking a break developing websites for a few years, I came back to Gutenberg. This time, I chained myself to my desk and forced myself to learn it completely, instead of skimming around the edges. Now I can’t imagine designing without Gutenberg.</p>
<p>I also very recently discovered WP CLI. I’m a bash geek from way back, so when I learned that I could use CLI commands to update my WordPress sites over ssh, I squealed like an 11-year old. I’m currently managing about 20 different sites on one of my host’s servers. I can easily log in remotely using my terminal and update plugins, themes and the core. I’ve found that it’s much faster than clicking around the dashboard and it satisfies some of my command line urges.</p>
<p>It’s only been in the last few years that I’ve started running a business centered around WordPress. I started taking on clients slowly, mostly managing the backend and host issues, as well as updating plugins and themes. I find that I do much less actual design and development than I do consulting and playing Tech Support. I’ve also found a niche in writing about WordPress for media outlets and other developers, which is very satisfying to both my brain and ego – as well as my bank balance.</p>
<p>I’ve spent a lot of time here gushing about WordPress. I do love it, but I also see the flaws and have an extensive list of I wish they would&#8230; in my mental notebook. I even – gasp – develop sites without WordPress, even blogs. And though I stray from time to time, I imagine I’ll always come back to WordPress.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 01 Dec 2021 16:00:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"DJ Billings";s: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:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:82:"WPTavern: Ask the Bartender: Should I Use a Page Builder or Wait for Block Themes?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=125794";s:7:"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:205:"https://wptavern.com/ask-the-bartender-should-i-use-a-page-builder-or-wait-for-block-themes?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-should-i-use-a-page-builder-or-wait-for-block-themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7171:"<blockquote class="wp-block-quote"><p>As a non-developer, I honestly don&#8217;t know what direction to take my WordPress site anymore.</p><p>I used to rely on themes and even bought some premium ones, but over time, I&#8217;d outgrow them. As an artist myself, I prefer having control over every aspect of my website, from its layout, colors, to its fonts. Thus, I turned to page builders.</p><p>I tried Elementor Pro, but it was frustrating how it was so difficult to create more advanced layouts without exponentially increasing the DOM size of the page. I had to install several Elementor plugins just to get the job done, but then it also made the site slower. Elementor would also often conflict with Gutenberg block styles since I used the block editor for writing posts.</p><p>There&#8217;s Oxygen, which I&#8217;ve heard great reviews of, but its learning curve is too much for me. I also couldn&#8217;t get used to themes being completely disabled, as I relied heavily on child themes, knowing a bit of CSS.</p><p>Now, there&#8217;s this whole Gutenberg uprising. FSE is the future, but I cannot adapt at all. Not to mention that there aren&#8217;t that many FSE themes out there yet.</p><p>I feel like I&#8217;m stuck between a rock and a hard place. I don&#8217;t know if I should take the theme route, the page builder route, or the Gutenberg route. If I take either of the first two, I fear they may become obsolete or incompatible in future versions of WordPress as Gutenberg is further developed. And if I take the Gutenberg route right now, I don&#8217;t really have much options yet. As it is, Gutenberg doesn&#8217;t seem to have any built-in ways of displaying custom meta fields like those from ACF. I don&#8217;t want to turn to another premium plugin for it, either.</p><p>How much longer is Gutenberg&#8217;s development going to take before ordinary but semi-advanced users like me can actually make use of it? What&#8217;s actually the best route to take in WordPress right now, a time when a lot of groundbreaking changes are constantly being rolled out?</p><cite>Isabel</cite></blockquote>



<p class="has-drop-cap">Before diving too deep into this, I want to clarify some terminology for readers. Some of the above uses of &#8220;Gutenberg&#8221; refer to site editing, a feature landing in the January release of WordPress 5.9. However, to use the site editor, users will need to activate a block theme. Currently, there are <a href="https://wordpress.org/themes/tags/full-site-editing/">not many to choose from</a> simply because this technology is under development.</p>



<p>You are not alone in wondering when we will move beyond what is a seemingly never-ending transitional phase. We are only now getting to some of the features touted three or four years ago when I was a full-time theme author. I am neck-deep in the development side of all this daily, so I can only imagine what it is like for non-developers.</p>



<p>The question is tough to answer without a hyper-specific use case. And, the right solution for one person will not always be ideal for another. There are questions of time, resources, budget, etc.</p>



<p>I only like the page-builder route if you are crunched for time and have a business riding on this. In the short term, Elementor and others make a lot of sense for getting something up and running fast while also giving you design freedom, assuming you have gotten past the learning curve. If this is the case, there is nothing wrong with going in this direction. I do not see builders disappearing anytime soon.</p>



<p>Finding an ideal theme can take a lot of searching. Typically, I recommend end-users look for a design that matches at least the overall layout that they want. Colors, fonts, and other stylistic pieces of it are generally easy to change. The average theme nowadays has options for essentially &#8220;skinning&#8221; the website.</p>



<p>The second part of this is whether you only want control over the global design or if you want to customize the layout for the inner pages of the site too. For the latter, you need something that supports the current WordPress features.</p>



<p>If you are looking for something sooner rather than later, I would go with a theme that supports <a href="https://wordpress.org/themes/tags/block-styles/">block editor styles</a>, bundles several <a href="https://wordpress.org/themes/tags/block-patterns/">custom patterns</a>, and includes a &#8220;blank canvas&#8221; template for building landing pages. This route gives you something that is forward-looking but does not rely on third-party builders. Many of these theme authors are already preparing for or building block themes for WordPress 5.9 and beyond.</p>



<p>I am partial to the <a href="https://wordpress.org/themes/eksell/">Eksell theme</a> by Anders Norén. He also has a block theme named <a href="https://wordpress.org/themes/tove/">Tove</a> that is more flexible.</p>



<img />Eksell theme homepage.



<p>Be skeptical of themes that only have block editor styles. I have seen enough that only add some custom CSS for a few blocks and call it a day. It is nothing more than another bullet point for their marketing material.</p>



<p>If you can afford to wait a couple of months, you should keep an eye on the upcoming <a href="https://wptavern.com/first-look-at-wordpress-upcoming-twenty-twenty-two-default-theme-the-most-flexible-default-theme-ever-created-for-wordpress">Twenty Twenty-Two theme</a>. It is one of the most beautifully-designed default themes I have seen, but it also has a ton of room for customization. Currently, it has over 60 custom patterns, so that gives you a lot of layout options. I expect this block theme to set the bar that all others must rise to.</p>



<img />Twenty Twenty-Two color and font variations.



<p>There is one area where page builders excel in comparison to WordPress at the moment. And that is with horizontal layouts. When creating flexible columns or grids for all screen sizes, the block editor falls short. While the block system&#8217;s tools have improved, this gap will not close for a while.</p>



<p>I mentioned patterns being one of the primary components more than once. If a theme offers a solid set of block patterns that focus on layout variations, piecing together a site can sometimes be as easy as pointing and clicking the mouse.</p>



<p>If you need to do some heavy work with layout, there are several block-based grid plugins. When I have needed such a tool, I have almost exclusively relied on the <a href="https://wordpress.org/plugins/layout-grid/">Layout Grid Block</a> by Automattic. It performs this one job and does it well. The plugin bridges the gap between page builders and the block editor when coupled with a well-designed theme.</p>



<p>Everything comes down to timing. You don&#8217;t want to build your site on top of one system only to recreate the entire thing from scratch six months from now. For that reason alone, I would forego page builders altogether, except where time is limited. Give block themes like the upcoming Twenty Twenty-Two some time to come into their own.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 01 Dec 2021 00:12:50 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:34;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:40:"WordPress.org blog: WordPress 5.9 Beta 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:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=11584";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2021/11/wordpress-5-9-beta-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10890:"<p>WordPress 5.9 Beta 1 is now available for testing!</p>



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



<p>You can test the WordPress 5.9 Beta 1 in three ways:</p>



<ul><li>Option 1: Install and activate the<a href="https://wordpress.org/plugins/wordpress-beta-tester/"> WordPress Beta Tester</a> plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).</li><li>Option 2: Direct download the <a href="https://wordpress.org/wordpress-5.9-beta1.zip">beta version here (zip)</a>.</li><li>Option 3: Use WP-CLI to test: <code>wp core update --version=5.9-beta1</code>. <strong><em>Do not use this option if your filesystem is case-insensitive.</em></strong></li></ul>



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



<p>Check the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/5-9+dev-notes/">5.9-related developer notes</a> in the coming weeks which will break down all upcoming changes in greater detail.</p>



<h2 id="how-you-can-help-testing"><strong>How You Can Help – Testing!</strong></h2>



<p>Testing for bugs is a critical part of polishing the release in the beta stage. It is also a great way to contribute. If you’ve never tested a beta release before, <a href="https://make.wordpress.org/test/2021/11/30/help-test-wordpress-5-9-features/">this detailed guide will help</a> walk you through what and how to test.</p>



<p>If you think you’ve found a bug, please report it to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta area</a> in the support forums. If you’re comfortable writing a reproducible bug report, <a href="https://core.trac.wordpress.org/newticket">file one on WordPress Trac</a>. That’s also where you can find a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>



<p>To see every feature in the Gutenberg releases since WordPress 5.8, check out the What’s New In Gutenberg posts for <a href="https://make.wordpress.org/core/2021/06/10/whats-new-in-gutenberg-10-8-9-june/">10.8</a>, <a href="https://make.wordpress.org/core/2021/06/24/whats-new-in-gutenberg-10-9-23-june/">10.9</a>, <a href="https://make.wordpress.org/core/2021/07/09/whats-new-in-gutenberg-11-0-0-9-july/">11.0</a>, <a href="https://make.wordpress.org/core/2021/07/21/whats-new-in-gutenberg-11-1-0-21-july/">11.1</a>, <a href="https://make.wordpress.org/core/2021/08/05/whats-new-in-gutenberg-11-2-0-4-august/">11.2</a>, <a href="https://make.wordpress.org/core/2021/08/18/whats-new-in-gutenberg-11-3-18-august/">11.3</a>, <a href="https://make.wordpress.org/core/2021/09/01/whats-new-in-gutenberg-11-4-1-september/">11.4</a>, <a href="https://make.wordpress.org/core/2021/09/17/whats-new-in-gutenberg-11-5-16-september/">11.5</a>, <a href="https://make.wordpress.org/core/2021/10/01/whats-new-in-gutenberg-11-6-29-september/">11.6</a>, <a href="https://make.wordpress.org/core/2021/10/14/whats-new-in-gutenberg-11-7-october-13th/">11.7</a>, <a href="https://make.wordpress.org/core/2021/10/28/whats-new-in-gutenberg-11-8-0-27-october/">11.8</a>, and <a href="https://make.wordpress.org/core/2021/11/12/whats-new-in-gutenberg-11-9-0-10-november/">11.9</a>.&nbsp;</p>



<p>Beyond the noted changes, which include 580 enhancements and nearly 450 bug fixes, contributors have fixed <a href="https://core.trac.wordpress.org/query?status=closed&milestone=5.9&group=component&max=500&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">297 tickets for WordPress 5.9</a>, including <a href="https://core.trac.wordpress.org/query?status=closed&status=reopened&type=enhancement&type=feature+request&milestone=5.9&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&col=changetime&col=keywords&order=changetime">110 new features and enhancements</a>. More fixes are on the way.</p>



<p>Happy testing!</p>



<p><em>Want to know what’s new in version 5.9? Read on for some highlights.</em></p>



<hr class="wp-block-separator" />



<h2 id="full-site-editing"><strong><strong>Full Site Editing</strong></strong></h2>



<h3 id="styles-interface">The <strong>Styles Interface</strong></h3>



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



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



<h3 id="theme-json"><strong>Theme.json</strong></h3>



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



<p>Other features supported by theme.json include: </p>



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



<h3 id="a-new-navigation-block"><strong>A New Navigation Block</strong></h3>



<p>Welcome to the most intuitive way to build navigation: the Navigation Block.&nbsp;</p>



<p>Here are the features that need testing the most:</p>



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



<h3 id="a-better-gallery-block"><strong>A Better Gallery Block</strong></h3>



<p>What if you could treat single images in your Gallery Block the same way you treat the Image Block? <strong>Now you can.</strong></p>



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



<p><strong>One thing to note: </strong>Have you built a plugin or theme on the Gallery Block functionality?<a href="https://make.wordpress.org/core/2021/08/20/gallery-block-refactor-dev-note/"> Be sure to review this Dev Note, which details what you need to do for compatibility</a>.</p>



<h3 id="focused-template-part-mode"><strong>Focused Template Part Mode</strong></h3>



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



<h3 id="block-pattern-directory"><strong>Block Pattern Directory</strong></h3>



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



<h2 id="twenty-twenty-two-default-theme"><strong>Twenty Twenty-Two Default Theme</strong></h2>



<p><strong>A whole new way of building WordPress themes.</strong></p>



<p>WordPress 5.9 introduces features that make Full Site Editing possible, including <strong>the first default block theme</strong>.</p>



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



<h2 id="more-improvements-and-updates"><strong>More Improvements and Updates</strong></h2>



<ul><li>Do you love to blog? New tweaks to the publishing flow let you add new posts just seconds after hitting Publish on your latest post.</li><li>List View lets you drag and drop content as easily as you could always cruise through it – and collapse entire sections – so you can concentrate on a task or get the bigger picture.</li><li><a href="https://github.com/WordPress/gutenberg/pull/33955">The Buttons and Social icons blocks now absorb</a> and display their parent block’s toolbar controls.&nbsp;&nbsp;</li><li><a href="https://core.trac.wordpress.org/ticket/43700">Choose your language</a> on the login screen.</li><li>More <a href="https://github.com/WordPress/gutenberg/pull/33868">performance improvements</a> (i.e., speed).</li></ul>



<p><em>Props to <a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a>, <a href="https://profiles.wordpress.org/priethor/" class="mention"><span class="mentions-prefix">@</span>priethor</a>, <a href="https://profiles.wordpress.org/psykro/" class="mention"><span class="mentions-prefix">@</span>psykro</a>, <a href="https://profiles.wordpress.org/annezazu/" class="mention"><span class="mentions-prefix">@</span>annezazu</a>, <a href="https://profiles.wordpress.org/webcommsat/" class="mention"><span class="mentions-prefix">@</span>webcommsat</a>, <a href="https://profiles.wordpress.org/marybaum/" class="mention"><span class="mentions-prefix">@</span>marybaum</a>, <a href="https://profiles.wordpress.org/hellofromtonya/" class="mention"><span class="mentions-prefix">@</span>hellofromtonya</a>, <a href="https://profiles.wordpress.org/davidbaumwald/" class="mention"><span class="mentions-prefix">@</span>davidbaumwald</a>, and <a href="https://profiles.wordpress.org/rmartinezduque/" class="mention"><span class="mentions-prefix">@</span>rmartinezduque</a> for their research and copy.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 30 Nov 2021 23:35:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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:35;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:"WordPress.org blog: People of WordPress: Devin Maeztri";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=11678";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wordpress.org/news/2021/11/people-of-wordpress-devin-maeztri/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:12456:"<p>In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people&#8217;s lives for the better. This month we feature a translator and campaigner who uses WordPress to highlight good causes and helps people in her area benefit from the open source platform.</p>



<div class="wp-block-image"><img width="632" height="843" src="https://i2.wp.com/wordpress.org/news/files/2021/11/devin-with-her-cat.jpg?resize=632%2C843&ssl=1" alt="Devin pictured with one of her cats" class="wp-image-11690" /></div>



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



<blockquote><p>“It is not that hard to fall for WordPress if you have a chance to experience WordPress. For me, it took a WordCamp.”</p><cite>Devin Maeztri</cite></blockquote>



<p>Devin&#8217;s first experience with camps came when she volunteered impromptu at an Indonesian event, WordCamp Denpasar, Bali in 2016.&nbsp;</p>



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



<p>With every WordCamp after that first experience, she became more interested in WordPress and the community.&nbsp;</p>



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



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



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



<div class="wp-block-image"><img width="632" height="632" src="https://i1.wp.com/wordpress.org/news/files/2021/11/wcasia_2020_organizers_in_wceu_2019.jpeg?resize=632%2C632&ssl=1" alt="Devin pictured with other WordCamp Asia organizers who attended WordCamp Europe in 2019" class="wp-image-11692" />WordCamp Asia 2020 Organizers at WordCamp Europe 2019. Devin is pictured in the front row, second from left. Photo Credit: Abha Thakor</div>



<h2 id="showing-how-wordpress-can-be-used-locally">Showing how WordPress can be used locally</h2>



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



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



<h3 id="encouraging-others-to-translate-wordpress">Encouraging others to translate WordPress</h3>



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



<img width="632" height="318" src="https://i1.wp.com/wordpress.org/news/files/2021/11/featured-img-used-for-devin-pow2.jpg?resize=632%2C318&ssl=1" alt="Polyglot nominatee - Devin Maeztri" class="wp-image-11706" />



<p>Through the efforts of Devin and the other translation editors, Indonesia took part in <a href="https://wptranslationday.org/">WordPress Translation Day</a> in 2020, and in 2021 held sprints and learning sessions spanning the whole 30 days of the event. </p>



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



<h2 id="helping-to-give-access-to-more-diverse-audiences">Helping to give access to more diverse audiences</h2>



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



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



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



<div class="wp-block-image"><img width="600" height="534" src="https://i1.wp.com/wordpress.org/news/files/2021/11/devin-at-wc-jakarta2019.png?resize=600%2C534&ssl=1" alt="" class="wp-image-11689" /><em>Organizing at WordCamp Jakarta 2019</em></div>



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



<h2 id="wordpress-can-support-your-skills-and-passions">WordPress can support your skills and passions</h2>



<p>With a background in environmental activism, Devin has worked for international development organizations on everything from policymaking to campaigning.&nbsp;</p>



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



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



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



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



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



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



<div class="wp-block-image"><img width="632" height="474" src="https://i2.wp.com/wordpress.org/news/files/2021/11/cat-watching-translation.jpg?resize=632%2C474&ssl=1" alt="One of Devin's cats watches the WPTranslationDay 2021 livestreamed events." class="wp-image-11688" />Devin&#8217;s cat became a regular on social media posts about #WPTranslationDay 2021</div>



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



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



<h2 id="wordpress-gives-everyone-a-chance-to-learn">WordPress gives everyone a chance to learn</h2>



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



<div class="wp-block-embed__wrapper">

</div>Devin talks about translating in this short <a rel="noreferrer noopener" href="https://www.youtube.com/watch?v=VsiQzdmAz8g" target="_blank">video</a> (opens in a new tab on YouTube)



<p>She is also active in other Contributor Teams and decided to become a Community Team Deputy to support meetups in new cities across Indonesia and perhaps future WordCamps.&nbsp;</p>



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



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



<h2 id="contributors">Contributors</h2>



<p>Thank you to Abha Thakor (<a href="https://profiles.wordpress.org/webcommsat/">@</a><a href="https://profiles.wordpress.org/webcommsat/">webcommsat</a>) and Mary Baum (<a href="https://profiles.wordpress.org/marybaum/" class="mention"><span class="mentions-prefix">@</span>marybaum</a>) for the interviews and writing this feature, and to Devin Maeztri (<a href="https://profiles.wordpress.org/devinmaeztri/">@devinmaeztri</a>) for sharing her story. Thanks to Meher Bala (<a href="https://profiles.wordpress.org/meher/">@meher</a>) for work on the images, and to Chloé Bringmann (<a href="https://profiles.wordpress.org/cbringmann/">@cbringmann</a>) and Collieth Clarke (<a href="https://profiles.wordpress.org/callye/" class="mention"><span class="mentions-prefix">@</span>callye</a>) for proofing.</p>



<p>Thanks to Josepha Haden Chomphosy&nbsp;(@<a href="https://profiles.wordpress.org/chanthaboune/">chanthaboune</a>) and Topher DeRosia (<a href="https://profiles.wordpress.org/topher1kenobe/">@topher1kenobe</a>) for their support for the series.</p>



<p><em>This People of WordPress feature is inspired by an essay originally published on </em><a href="https://heropress.com/"><em>HeroPress.com</em></a><em>, 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. </em>#HeroPress #ContributorStory</p>



<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 30 Nov 2021 22:21:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:28:"webcommsat AbhaNonStopNewsUK";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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: ACF Solicits Lifetime License Holders for Contributions, Urging Them to Purchase Annual Subscriptions";s:7:"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=126206";s:7:"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:265:"https://wptavern.com/acf-solicits-lifetime-license-holders-for-contributions-urging-them-to-purchase-annual-subscriptions?utm_source=rss&utm_medium=rss&utm_campaign=acf-solicits-lifetime-license-holders-for-contributions-urging-them-to-purchase-annual-subscriptions";s: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:8827:"<p>The Advanced Custom Fields (ACF) marketing team at Delicious Brains kicked up a sandstorm over the weekend after it emailed its lifetime license holders, asking them to consider signing up for a discounted subscription. Despite Delicious Brains&#8217; explicit promise that they would never be required to pay for ACF updates in the future, the sales email insinuates that the development team is in need of appreciation in the form of annual paid subscriptions:</p>



<blockquote class="wp-block-quote"><p>I know you already have a lifetime license for ACF Pro, but I&#8217;m hoping you&#8217;ll consider signing up for a discounted subscription to support our ongoing work in continuing to improve Advanced Custom Fields.</p><p>We&#8217;ve shipped two major releases (5.10 and 5.11) since we took over development of the plugin from Elliot in June, including a full-featured REST API! If you&#8217;re a fan of the work we&#8217;ve done so far, nothing will show our developers that you appreciate them more than signing up for an ACF Pro subscription, especially since you already have a lifetime license.</p></blockquote>



<p>This bewildering pitch to lifetime license holders landed in email boxes on the Friday after Thanksgiving in the US. It drew more attention after Paul Charlton, creator of WPTuts, <a href="https://twitter.com/WPTutz/status/1464324239243325442">tweeted</a> a screenshot of the email, saying it left &#8220;a really bad taste&#8221; in his mouth. Charlton also recorded <a href="https://youtu.be/3KL0UvcrV0M">a reaction video</a> that succinctly articulates why the email was so irksome to many lifetime license customers. He suggested Delicious Brains instead take the approach of offering a discount on their other subscription products.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Am I the only one who thinks this is bad form trying to guilt your existing Lifetime owners into paying for a subscription?<br /><br />This type of thing leaves a really bad taste in my mouth, especially after the issues surrounding honouring the LTD in the first place! <a href="https://twitter.com/wp_acf?ref_src=twsrc%5Etfw">@wp_acf</a> <a href="https://t.co/ZqNLcMjoAk">pic.twitter.com/ZqNLcMjoAk</a></p>&mdash; WPTuts (@WPTutz) <a href="https://twitter.com/WPTutz/status/1464324239243325442?ref_src=twsrc%5Etfw">November 26, 2021</a></blockquote>
</div>



<p>&#8220;If you&#8217;re going to broach the topic of asking lifetime subscribers to suddenly pay for $250/year for the same product, I would just think that something, anything, could be offered,&#8221; one lifetime license holder <a href="https://twitter.com/agoodsamaritan2/status/1464310822159663111">said</a>.</p>



<p>Some lifetime license holders found the email pitch was especially perplexing after the confusing messaging when <a href="https://wptavern.com/delicious-brains-acquires-advanced-custom-fields-plugin">Delicious Brains acquired ACF</a>. A hasty response to a customer inquiry caused lifetime license holders to question if the company would continue honoring the agreement after the acquisition. </p>



<p>&#8220;Lifetime license holders will get all ACF Pro software updates forever,&#8221; Delicious Brains founder and CEO Brad Touesnard said at the time. &#8220;They won’t be required to pay for version 6.0 or any other major or minor releases in the future. They signed up for updates for life, so we’ll continue to deliver on that promise forever.&#8221;</p>



<p>Some lifetime license holders tried to read between the lines of the recent sales emails and wondered if Delicious Brains was signaling an end to its commitment.</p>



<p>&#8220;What happened to our lifetime licenses being honored and we would get full and continued updates for life?&#8221; Brian J McCracken said in response to the email. &#8220;They haven’t said they aren’t doing that but talk about skirting the intention with this guilt trip.&#8221; Others are also skeptical, speculating that Delicious Brains may repurpose the code for a new product so they can &#8220;kill off the LTD&#8217;s once and for all.&#8221;</p>



<p>&#8220;I honestly believe they WANT the LTD owners to leave,&#8221; WordPress developer Wendell Harness said. &#8220;Think about it &#8212; they won&#8217;t have to support us anymore. An email like this may garner a few buy-ins while also wiping away a bunch of people they no longer want to support. It&#8217;s brilliant. Rude, but still brilliant.&#8221;</p>



<p>Those on the other side of the argument disagree with the notion that lifetime license holders should expect updates indefinitely. </p>



<p>&#8220;You paid a hundred bucks or so 5 years ago and you expect a company to keep adding value to your business that could have been generating hundred of thousands of dollars in revenue,&#8221; 10up WordPress engineer Clayton Collie said in response to critics of the email. &#8220;They could abandon the project. How would you feel about that?&#8221;</p>



<p>After the sales email created new confusion on the status of lifetime licenses, ACF tweeted to reaffirm their commitment to honor them, but many recipients had already formed their own conclusions about the intent of the email.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Not going to lie, the email was gross and unnecessary. If you don’t want to make your customers unhappy maybe doing a better job at hiding your disdain for lifetime license holders <a href="https://t.co/UilZa40pU2">https://t.co/UilZa40pU2</a></p>&mdash; Cameron Jones <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f468-200d-1f466.png" alt="👨‍👦" class="wp-smiley" /> (@cameronjonesweb) <a href="https://twitter.com/cameronjonesweb/status/1465451078653149185?ref_src=twsrc%5Etfw">November 29, 2021</a></blockquote>
</div>



<p>&#8220;We&#8217;ve heard from many lifetime customers who are happy with the work we&#8217;ve already been doing to improve ACF and glad to contribute by subscribing,&#8221; Touesnard said in response to customers who suggested the company offer something in return for signing up to a new annual subscription. &#8220;If you don&#8217;t feel the way they do, that&#8217;s fine, you aren&#8217;t required to subscribe.&#8221;</p>



<p>The heated conversations have renewed the controversial topic of selling lifetime licenses in the WordPress product space. Few have done this successfully long term, and it gets trickier when a company is acquired. </p>



<p>&#8220;I see both sides for this &#8211; as someone who bought a lifetime ACF license 7 years ago and also a plugin dev,&#8221; Amber Hinds said. &#8220;Really lifetime licenses should be offered with extreme caution.&#8221;</p>



<p>In many cases, when early adopters purchase a lifetime license, they are usually paying much more than the regular license, for an unproven product that isn&#8217;t guaranteed a future. This gives newer products the money they need to build momentum but also offers something in return. It&#8217;s a transaction where each participant extracts some value and assumes a share of the risk.</p>



<p>In this particular scenario, ACF appears to be mistaking its relationship with lifetime license holders as something more akin to investors or donors. Customers who purchase lifetime licenses rarely share those same motivations. </p>



<p>It&#8217;s quite unusual for a Black Friday sales email to ask for contributions for a product consumers have already paid for long ago. This unorthodox sales approach and timing was off-putting to many of the recipients. Was it worth upsetting a slew of customers who are not bringing ACF any money for the rest of its life as a product? Only the Delicious Brains team knows how successful the campaign has been so far. When asked if the email is generating new signups from lifetime license customers, Touesnard said the developer who pulls that report was not currently available. </p>



<p>&#8220;Does a company that spans across five very popular products require a donation approach, to keep a product like ACF, afloat?&#8221; WordPress business podcaster Matt Medeiros said in a post titled &#8220;<a href="https://thewpminute.com/wordpress-the-multi-billion-dollar-software-industry-that-has-us-begging-for-money/">WordPress, the multi-billion dollar software industry that has us begging for money</a>.&#8221; </p>



<p>&#8220;If so, we better start getting better at pricing and voting with our dollars,&#8221; he said.</p>



<p>&#8220;Either way, expecting lifetime updates for one price, coupled with a part-time donation strategy, is bad for both the consumer and the business. I don’t see any other major markets operating this way.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 30 Nov 2021 21:37:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:66:"WPTavern: Gutenberg 12.0 Focuses on Cleanup and Minor Enhancements";s:7:"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=126191";s:7:"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:177:"https://wptavern.com/gutenberg-12-0-focuses-on-cleanup-and-minor-enhancements?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-12-0-focuses-on-cleanup-and-minor-enhancements";s: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:5639:"<p class="has-drop-cap">Last week, contributors to the Gutenberg plugin wrapped up the <a href="https://make.wordpress.org/core/2021/11/29/whats-new-in-gutenberg-12-0-0-24-november/">version 12.0 release</a> just ahead of the U.S. Thanksgiving holiday. Most work is being pushed toward the upcoming WordPress 5.9 release, which has been <a href="https://wptavern.com/wordpress-5-9-revised-release-date-confirmed-for-january-25-2022">postponed to January 25</a>. As a result, Gutenberg 12.0 has fewer bells and whistles and more bug fixes and maintenance. However, the latest update has a handful of enhancements.</p>



<p>The most notable features are an overhaul of block styles previews, grouped paragraph typography options, and block icons in the global styles sidebar. The site editor also has a new <a href="https://github.com/WordPress/gutenberg/pull/36172">welcome guide</a>, which should ship with WordPress 5.9 and introduce users to the new tool.</p>



<p>Theme authors can now opt-out of the <a href="https://github.com/WordPress/gutenberg/pull/36492">core color palette and gradients</a>. There is <a href="https://github.com/WordPress/gutenberg/issues/36852">still a bug</a> where this does not currently work for the site editor.</p>



<h2 id="block-styles-previews">Block Styles Previews</h2>



<img />Hovering a block style to see its preview.



<p class="has-drop-cap">For once in the last few years, the editor sidebar feels kind of clean and organized. When using a theme with multiple block styles, the style previews have been nothing short of an annoyance. The tab that held them took up a lot of space by presenting an entire demo of every option.</p>



<p>In the latest Gutenberg plugin release, the previews have been replaced with text-based buttons, emphasizing the style names. Users can still <a href="https://github.com/WordPress/gutenberg/pull/34522">see what individual block styles look like</a> by hovering over each one or focusing on it with a keyboard.</p>



<p>The downside to this new experience is that longer block-style names can sometimes get cut off. For example, the &#8220;Portfolio: Tilt Left&#8221; and &#8220;Polaroid: Tilt Right&#8221; options in my custom theme both read &#8220;Portfolio: Ti…&#8221; I will have to rethink their names, but that is a small price to pay for the cleaner interface.</p>



<h2 id="paragraph-drop-cap-control-moved">Paragraph Drop Cap Control Moved</h2>



<img />Drop cap control now under Typography tab.



<p class="has-drop-cap">It seems this release has been one for fixing those irritating issues with the user experience. The option for adding a drop cap to the Paragraph block now <a href="https://github.com/WordPress/gutenberg/pull/36334">rests alongside similar controls</a> under the Typography block options tab.</p>



<p>Formerly, users had to find it under a separate Text Settings tab, which only held the drop cap option. I am sure I have mentioned this being a poor user experience on a few occasions as someone who often reaches for the control. I, for one, am a happy camper with this change.</p>



<h2 id="icons-shown-in-the-blocks-list">Icons Shown in the Blocks List</h2>



<img />Blocks now show their icons.



<p class="has-drop-cap">After the <a href="https://wptavern.com/gutenberg-11-7-iterates-on-global-styles-improves-adding-navigation-links-and-adds-column-spacing">Gutenberg 11.7 release</a>, one of my suggestions was to add icons to the global styles blocks list. Previously, it was a vertical scrollable area with dozens of block names, making it hard to find something specific to customize.</p>



<p>Whether Nik Tsekouras, who wrote the patch for this change, happened to read that Tavern post or saw the same issue with his own experience, I am grateful that he <a href="https://github.com/WordPress/gutenberg/pull/36520">coded a solution</a>. Finding a block is now much faster because I can just scan the list for a recognizable icon.</p>



<h2 id="themes-can-opt-into-all-appearance-settings">Themes Can Opt Into All Appearance Settings</h2>



<p><em><strong>Note:</strong> This was incorrectly <a href="https://github.com/WordPress/gutenberg/releases/tag/v12.0.0">tagged as part of 12.0</a> but did not make it into the release. However, the code should be merged in the trunk branch of the Gutenberg repository.</em></p>



<p class="has-drop-cap">For any theme author who has been working with <code>theme.json</code>, you know how unruly the file can get when enabling or disabling specific settings. A new flag allows themes to opt into <a href="https://github.com/WordPress/gutenberg/pull/36646">support of all appearance-related options</a> at once.</p>



<p>An example <code>theme.json</code> file would look like the following:</p>



<pre class="wp-block-code"><code>{
        "version": 2,
        "settings": {
                "appearanceTools": true
        }
}</code></pre>



<p>Setting the <code>appearanceTools</code> flag to <code>true</code> enables support for all border, color, spacing, and typography options. This should cut back on unnecessary JSON code, especially for themers who are opting into almost everything. Theme authors can still disable specific features individually.</p>



<p>Depending on the theme author&#8217;s point of view, the potential up or downside to this new flag is that it will also enable support for other appearance-related features in the future. It would allow users to access new features before their themes officially support them. On the flip-side, theme authors may want more control or to run tests before enabling something new.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 29 Nov 2021 23:15: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:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:"WordPress.org blog: WP Briefing: Episode 21: All Things Block Themes!";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/news/?post_type=podcast&p=11636";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://wordpress.org/news/2021/11/episode-21-all-things-block-themes/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:26885:"<p>In episode 21 of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy, talks all things block themes with developers and theme specialists Maggie Cabrera and Jeff Ong.</p>



<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href="mailto:wpbriefing@wordpress.org">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>



<h2 id="credits">Credits</h2>



<ul><li>Editor:&nbsp;<a href="https://profiles.wordpress.org/dustinhartzler/">Dustin Hartzler</a></li><li>Logo:&nbsp;<a href="https://profiles.wordpress.org/beafialho/">Beatriz Fialho</a></li><li>Production:&nbsp;<a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a></li><li>Song: Fearless First by Kevin MacLeod</li></ul>



<h2 id="references">References </h2>



<ul><li><a href="https://make.wordpress.org/core/2021/11/17/wordpress-5-9-beta-1-delayed/">5.9 Beta 1 Delay Announcement </a></li><li><a href="https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/">5.9 Revised Release Schedule</a></li><li><a href="https://sevilla.wordcamp.org/2021/">WordCamp Sevilla 2021</a></li><li>Charitable Giving: <ul><li><a href="https://wordpressfoundation.org/donate/">WordPress Foundation</a></li><li><a href="https://donate.bigorangeheart.org/">Big Orange Heart</a></li><li><a href="https://heropressnetwork.com/support/">HeroPress</a> <em>(Update: This organization is not a non-profit.)</em></li></ul></li></ul>



<h2 id="transcript">Transcript</h2>



<span id="more-11636"></span>



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:11</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:40</p>



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



<p><strong>Jeff Ong&nbsp; </strong>01:39</p>



<p>Thank you for having us. Excited to be here.&nbsp;</p>



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:45</p>



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



<p><strong>Jeff Ong&nbsp; </strong>02:34</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>03:04</p>



<p>I think you can dare to say it.&nbsp;</p>



<p><strong>Jeff Ong&nbsp; </strong>03:03</p>



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



<p><strong>Jeff Ong&nbsp; </strong>04:04</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:03</p>



<p>I also think it&#8217;s a good example. Maggie, did you have anything that you wanted to add to that?</p>



<p><strong>Maggie Cabrera&nbsp; </strong>05:08</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:07</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:57</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>08:20</p>



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



<p><strong>Jeff Ong&nbsp; </strong>09:11</p>



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



<p><strong>Jeff Ong&nbsp; </strong>09:33</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>10:57</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>12:08</p>



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



<p>12:29</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>14:00</p>



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



<p><strong>Maggie Cabrera&nbsp; </strong>14:31</p>



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



<p><strong>Jeff Ong&nbsp; </strong>14:54</p>



<p>They still need to support the old way of doing things.</p>



<p><strong>Maggie Cabrera&nbsp; </strong>14:58</p>



<p>Like being backward compatible and being ready for any kind of user.</p>



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>15:05</p>



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



<p><strong>Maggie Cabrera&nbsp; </strong>15:12</p>



<p>It&#8217;s also good for users; If they feel secure in using the customizer.</p>



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>15:20</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>17:40</p>



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



<p><strong>Jeff Ong&nbsp; </strong>19:23</p>



<p>So you&#8217;re asking like, what in the last 12 months has maybe like really surprised me or like sticks out to me as something that like, Wow, look how far we&#8217;ve come?</p>



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>19:36</p>



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



<p><strong>Maggie Cabrera&nbsp; </strong>20:05</p>



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



<p><strong>Jeff Ong&nbsp; </strong>21:23</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>22:10</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>22:41</p>



<p>So, Maggie, Jeff, thank you both for joining me. And I&#8217;m sure that we&#8217;ll talk to you all again soon.&nbsp;</p>



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>22:56</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>23:19</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>24:33</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>24:55</p>



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



<p><strong>Josepha Haden Chomphosy&nbsp; </strong>25:42</p>



<p>And that is your small list of big things. Thank you so much for tuning in today for the WordPress Briefing. Thank you again to our special guests, Maggie and Jeff. I&#8217;m your host Josepha Haden Chomphosy, and I&#8217;ll see you again in a couple of weeks.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 29 Nov 2021 12:07:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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:39;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:"Gutenberg Times: Gutenberg Changelog #56 – Gutenberg 12.0, WordPress 5.9 Release Schedule, Navigation Block and Site Editor";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://gutenbergtimes.com/?post_type=podcast&p=19715";s:7:"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:98:"https://gutenbergtimes.com/podcast/gutenberg-changelog-56-gutenberg-12-wordpress-5-9-ryan-welcher/";s: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:75294:"<p>Co-hosts, Birgit Pauli-Haack and Grzegorz Ziolkowski discuss with Ryan Welcher the Gutenberg 12.0 release, the updated WordPress 5.9 Release Schedule and a lot more.</p>



<ul><li>Music:&nbsp;<a href="https://soundcloud.com/xirclebox">Homer Gaines</a></li><li>Editor:&nbsp;<a href="https://www.linkedin.com/in/sandy-reed/">Sandy Reed</a></li><li>Logo:&nbsp;<a href="https://markuraine.com/">Mark Uraine</a></li><li>Production:&nbsp;<a href="https://paulisystems.net/wordpress-consulting">Pauli Systems</a></li></ul>



<p><a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-56-Gutenberg-12-wordpress-5.9-Ryan-Welcher#shownotes">Show Notes </a>/ <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-56-Gutenberg-12-wordpress-5.9-Ryan-Welcher#transcript">Transcript</a></p>



<span id="more-19715"></span>



<p><strong>Subscribe to the&nbsp;<a href="https://gutenbergtimes.com/podcast/">Gutenberg Changelog</a>&nbsp;podcast via your favorite podcast apps!</strong><br />🎙️&nbsp;<a href="https://open.spotify.com/show/620NwVKQJGdTupy36zYxvg?mc_cid=4b6c9f88fe">Spotify</a>&nbsp;|&nbsp;<a href="https://podcasts.google.com/feed/aHR0cHM6Ly9ndXRlbmJlcmd0aW1lcy5jb20vZmVlZC9wb2RjYXN0">Google</a>&nbsp;|&nbsp;<a href="https://podcasts.apple.com/us/podcast/gutenberg-changelog/id1469294475">iTunes</a>&nbsp;|&nbsp;<a href="https://pca.st/podcast/f8445ec0-7508-0137-f267-1d245fc5f9cf">PocketCasts</a>&nbsp;|&nbsp;<a href="https://www.stitcher.com/show/gutenberg-changelog">Stitcher</a>&nbsp;|<br />🎙️&nbsp;<a href="https://www.podbean.com/podcast-detail/chi7j-9904a/Gutenberg-Changelog-Podcast">Pod Bean</a>&nbsp;|&nbsp;<a href="https://castbox.fm/channel/Gutenberg-Changelog-id2173375">CastBox</a>&nbsp;|&nbsp;<a href="https://www.podchaser.com/podcasts/gutenberg-changelog-878239/">Podchaser</a>&nbsp;|&nbsp;<a href="https://gutenbergtimes.com/feed/podcast">RSS Feed</a>&nbsp;</p>



<p class="has-large-font-size" id="shownotes"><strong>Show Notes </strong></p>



<h2 id="ryan-welcher-developer-advocate-sponsored-by-automattic"><a href="https://twitter.com/ryanwelcher"><strong>Ryan Welcher</strong></a>, Developer advocate, sponsored by Automattic. </h2>



<ul><li><a href="https://www.twitch.tv/ryanwelchercodes">Twitch Live Streams @ ryanwelchercodes</a></li><li><a href="https://github.com/WordPress/gutenberg-examples">Gutenberg Examples Repository at GitHub</a></li><li><a href="https://ryanwelcher.com/">Website &amp; Blog </a></li></ul>



<h2 id="community-contributions">Community Contributions</h2>



<p><a href="https://make.wordpress.org/core/2021/11/24/wordpress-development-environment/">WordPress development environment</a> by Marcus Kasmierczak</p>



<h2 id="wordpress-5-9-updated-schedule"><strong>WordPress 5.9 updated Schedule</strong></h2>



<ul><li><a href="https://make.wordpress.org/core/5-9/">Updated Release Schedule for 5.9 </a></li><li><a href="https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/"><strong>WordPress 5.9 Revised Release Schedule</strong></a> by Core release lead <strong>Tonya Mork</strong></li><li><a href="https://nomad.blog/2021/11/23/why-i-voted-to-delay-wordpress-5-9/"><strong>Why I voted to delay WordPress 5.9</strong></a> by <strong>Anne McCarthy</strong>, release co-lead for testing</li><li><a href="https://wptavern.com/wordpress-5-9-revised-release-date-confirmed-for-january-25-2022"><strong>WordPress 5.9 Revised Release Date Confirmed for January 25, 2022</strong></a>, <strong>Sarah Gooding</strong>, WPTavern</li><li><a href="https://wordpress.org/news/2021/11/a-look-at-wordpress-5-9/"><strong>A Look at WordPress 5.9</strong></a> with the newly published video via WordPress News. </li><li>Video: <a href="https://www.youtube.com/watch?v=r59aR1tmY6k&t=75s"><strong>Exploring WordPress 5.9: Block theme flows, Styling, Patterns Explorer, &amp; more</strong></a></li></ul>



<h2 id="gutenberg-12-0">Gutenberg 12.0</h2>



<p><strong><a href="https://github.com/WordPress/gutenberg/releases/tag/v12.0.0">Find the full changelog on GitHub</a></strong>  </p>



<ul><li>Block Styles Previews (<a href="https://github.com/WordPress/gutenberg/pull/34522">34522</a>),</li><li>Featured Image block Visual Enhancement in the Site Editor (<a href="https://github.com/WordPress/gutenberg/pull/36517">36517</a>), </li><li>the Site Editor Welcome Guide (<a href="https://github.com/WordPress/gutenberg/pull/36172">36172</a>) and </li><li>the updates to the JSON schemas for <a href="https://schemas.wp.org/trunk/block.json"><strong>block.json</strong></a> and <strong><a href="https://schemas.wp.org/trunk/theme.json">theme.json</a></strong>. </li><li><a href="https://github.com/WordPress/gutenberg/discussions/categories/developer-experience">GitHub discussions on Developer Experience</a>.</li></ul>



<p><a href="https://www.twitch.tv/videos/1214655583">Gutenberg plugin v12.0.0 Release Party with Ryan Welcher</a></p>



<h2 id="what-s-discussed-and-in-active-development">What&#8217;s discussed and in active development</h2>



<ul><li>Pull Request by Ryan Welcher related to ordering slotfill/panel: <a href="https://github.com/WordPress/gutenberg/pull/16384">Plugin sorting via priority property in registerPlugin</a></li><li><a href="https://github.com/WordPress/gutenberg/pull/28273">Enable React Fast Refresh for block development</a> coming to @wordpress/scripts by Grzegorz Ziolkowski</li><li><a href="https://www.godaddy.com/garage/gutenberg-how-to-test-the-latest-updates/">Gutenberg: How to test the latest updates</a> w/ Birgit Pauli-Haack, Andy Fragen and George Mamadashvili via GoDaddy Pro</li></ul>



<p class="has-large-font-size">Stay in Touch</p>



<div class="wp-container-61b8b14738969 wp-block-group"><div class="wp-block-group__inner-container">
<ul><li>Did you like this episode? <a href="https://lovethepodcast.com/gutenbergchangelog"><strong>Please write us a review </strong></a></li><li>Ping us on Twitter or send DMs with questions. <a href="https://twitter.com/gziolo">@gziolo </a>and <a href="https://twitter.com/bph">@bph</a>.</li><li><em>If you have questions or suggestions, or news you want us to include, send them to <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>. </em></li><li><em>Please write us a review on iTunes! <a href="https://gutenbergtimes.com/itunes/">(Click here to learn how)</a></em></li></ul>
</div></div>



<p class="has-large-font-size" id="transcript"><strong>Transcript</strong></p>



<p class="has-large-font-size" id="transcript"><strong>Transcript</strong></p>



<p><em>Birgit Pauli-Haack</em>: Hello, and welcome to our 56th episode of the Gutenberg Changelog Podcast. In today&#8217;s episode, we will talk about Gutenberg 12.0, the updated WordPress 5.9 release schedule, navigation block site editor, and so much more. I&#8217;m Birgit Pauli-Haack, curator at the Gutenberg Times. And I&#8217;m here with my co-host, Grzegorz Ziolkowski, JavaScript developer at Automattic and WordPress call contributor. Our guest today is Ryan Welcher. Developer advocate at the Open Source Project and sponsored by Automattic. Hi, Ryan. Thank you for joining us today. How are you?</p>



<p><em>Ryan Welcher</em>: I&#8217;m good. Hi, thank you for having me. I&#8217;m excited to be here.</p>



<p><em>Birgit Pauli-Haack</em>: Well, howdy-howdy and Grzegorz, how are you doing?</p>



<p><em>Grzegorz Ziolkowski:</em> Hello, Ryan, and hello Birgit. I&#8217;m fine. It&#8217;s a little bit dark outside because the winter is coming to Poland, which means that about 4:00 PM, you don&#8217;t see anything outside. So it&#8217;s just a little bit depressing, but I&#8217;m happy that we have a lot of exciting things to discuss today.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. So we all have to have our sun in the hearts. Right?</p>



<p><em>Grzegorz Ziolkowski</em>: And all the warmth from the Florida, you send us.</p>



<p><em>Birgit Pauli-Haack</em>: Yes. I&#8217;m pushing it all towards Canada and Poland.</p>



<p><em>Ryan Welcher</em>: Yes. You can&#8217;t see it, but I&#8217;m wearing a toque right now during the recording of this.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. I have one of those and I need to take them to Canada when leaving.</p>



<p><em>Ryan Welcher</em>: You&#8217;ll definitely need them. Yes, you will.</p>



<p><em>Birgit Pauli-Haack</em>: So Ryan, you just completed your first Gutenberg release from the release candidate last week to this week&#8217;s final version. What did you learn?</p>



<p><em>Ryan Welcher</em>: It was a fun experience. I&#8217;d never done it before. I went into it with my imposter syndrome kind of pinging in the red, I have to say. I learned that it&#8217;s pretty foolproof. You click a button and wait for the actual process of creating the release and the zip file and all that. Really, it&#8217;s all done in GitHub actions, which is really. It was really, really simple. I did a live stream of both, and it was a lot of fun, but it was like a lot of action, and then nothing while we waited.</p>



<p>And so, it was a lot of me like trying to fill in the awkward silences, and then things would go, and then, we&#8217;d be done. Probably the biggest, the most amount of work on my end was definitely the changelog, was sort of organizing the release notes and moving some things around and making sure that the various pull requests were in the appropriate locations and all that sort of stuff. But I had a lot of help from a couple of folks at Automattic that had done releases before to give me a hand, sort of know what to look for.</p>



<p>I also learned that I don&#8217;t need to know, as the release lead, you don&#8217;t need to know what every commit did and how, like it&#8217;s not your job so much to make sure that the code works, because at this point, the code should be working and as automated process is in place that will flag things if stuff&#8217;s not working. So that was probably the biggest sort of learning for me was that like, I don&#8217;t… I wasn&#8217;t going to break 42-1/2% or 43% of the internet by pressing this button, it was by this point things are usually good. So yeah. It was a fun experience though. I&#8217;m looking forward to doing it again.</p>



<p><em>Birgit Pauli-Haack</em>: All right. Good. Good. I know that there are always a few more contributors wanted to do releases to walk us through. And so, I&#8217;m glad that you are here and tell us that it might not be, and we should all put us on imposter syndromes and just get started because there are some security nets there not only for security technology, but also for, it&#8217;s a safe place to get started contributing.</p>



<p><em>Ryan Welcher</em>: Yeah. Absolutely. Absolutely. One thing I did want to mention is that not anybody can just go and click the buttons. You have to be part of the contributor team, the Gutenberg contributor team, which you do by just getting involved, doing a couple pull requests, getting some eyes on your code. And then, it&#8217;s pretty straightforward to get added. You just have to put in a bit of work to get some sort of clout, I guess, behind you to get that that ….</p>



<p><em>Birgit Pauli-Haack</em>: Right. But it&#8217;s not the first good issue kind of contributing is definitely a progression. Yeah.</p>



<p><em>Ryan Welcher</em>: For sure. For sure.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. So we will also talk about a new section, the change up a little beta, a little bit later. A little beta. It&#8217;s a nice kind of-</p>



<p><em>Ryan Welcher</em>: It sounds like a beta version, right?</p>



<p><em>Birgit Pauli-Haack</em>: A little bit later. It&#8217;s called the developer experience and we&#8217;ll talk about it as I said. So before we head into the changelog and the announcements and everything, I want to take the opportunity to introduce you to our listeners and also discuss briefly some of your great work of the last couple of months. So how long have you been working as developer advocate and what did you on before you came to Automattic?</p>



<p><em>Ryan Welcher</em>: Well, my road to developer advocacy was a long one. I haven&#8217;t been a developer advocate professionally for, well, since I started at Automattic. This is my first official role as a developer advocate. I&#8217;ve always wanted to try it out. I remember, I tell this story to anybody that will listen. But way back in the day when I was doing flash work back in 2005, something like that. I saw this guy at a conference, and he was doing all this really cool stuff. I&#8217;m like, &#8220;That&#8217;s the coolest job in the world. You just go around doing cool things and showing people.&#8221; And that&#8217;s what I thought developer advocacy was.</p>



<p>So, yeah. So I joined Automattic, I guess, it was in, I think it was August of this year. So that&#8217;s how long I&#8217;ve been a developer advocate. I&#8217;ve been a developer for about 17 years. Prior to joining Automattic, I was at 10up. I was there for about six years. And then, before that I worked at various places where I&#8217;ve done a lot of… I had my own agency. &#8220;Agency,&#8221; if you want to call it that. And yeah. Done all kinds of developing stuff.</p>



<p><em>Birgit Pauli-Haack</em>: What did you do at 10up?</p>



<p><em>Ryan Welcher</em>: 10up, I left as a lead web engineer. So my job was to be the technical lead for many… Well, all the projects that I was on, I was usually the technical lead. So doing a lot of estimating and kind of like driving, sort of like guiding the ship as far as from a technical standpoint. Got to do some really cool things with Gutenberg. Really, really, really cool things with Gutenberg. I did a standalone Gutenberg implementation that was tied in the Larabel that was it was so much fun to put together.</p>



<p>I can&#8217;t say the client or anything like that, but it&#8217;s lots of, they do really cool stuff there. So yeah. That&#8217;s what I did there. Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: So I know that you, because you are on the same team as I am and you started the same time as I did, and we had our Chicago meeting and we were talking a little bit more and you were doing some great work on the Gutenberg examples repo. What was that about?</p>



<p><em>Ryan Welcher</em>: The examples repo is an awesome resource for learning how to do blocks, how to build blocks basically. It was very out-of-date. So what we did was we just, we updated it. And I live streamed it all. We updated all the blocks so they use the most recent versions of the block API. So now they all support block JSON, and they&#8217;re using the most recent version of WP-scripts and take advantage of all the sort of built in CSS stuff and all the goodness that really comes with the tools that we have available to us as WordPress developers, right?</p>



<p>We have some really cool ones like scripts package, the EMV package for just quickly spinning up a development environment, which is like such a pain point for so many people. Like, &#8220;What do I use?&#8221; And I don&#8217;t want to install VVV or docker or whatever, right? Well, I guess you need docker for EMV, but some of these more complicated things, right? And so, that was the effort.</p>



<p>The effort was to get the examples repo up-to-date and get some more examples in there. We added one for a slot fill, which we didn&#8217;t have before, which is great. Yeah. And I&#8217;m super excited about it. Super proud of all that work and it&#8217;s been a really good, a lot of people in the community have really kind of like jumped on the bandwagon with that and been really supportive of keeping it up-to-date.</p>



<p>I know that there was talk of maybe retiring the repo, but I think it&#8217;s been referenced in so many places across the internet that I think we just need to keep it up-to-date and keep it moving forward.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And I think that&#8217;s a great tool to really get into the examples and see how it&#8217;s actually done. And then, transfer that to your own Gutenberg block building experience. Yeah. So you mentioned your Twitch streams. I think people kind of watch that. How often do it? Do you have any additional plans?</p>



<p><em>Ryan Welcher:</em> Well, it started out as an experiment. I always wanted to… I&#8217;ve always thought I&#8217;ve never really seen a Twitch stream for WordPress specific stuff. I know there are a couple of streamers out there that do like one that they might do something with WordPress once or twice in a month or something, or maybe less. But I stream every Thursday, 10:30 Eastern, usually. Try to do it for about two hours.</p>



<p>Still, I&#8217;ll do some ad hoc ones now and again. You can find me at Ryan Welcher codes on Twitch, and also on YouTube. So I stream to both Twitch and YouTube at the same time. And, yeah. I mostly just fight, struggle through writing code live. And people get to watch me type horribly and do write really bad CSS, because I am not a front end developer. So hopefully, it&#8217;s… I&#8217;m sure it&#8217;s tarnishing my reputation as a developer, which is great. But also, I hope that it&#8217;s showing people that like, people, even folks like me who&#8217;ve been doing it for a long time still have to look up how to do like a ray filter, right? Or how to float something left, which you don&#8217;t even do in CSS anymore. That&#8217;s how long it&#8217;s been since I&#8217;ve written CSS.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. It&#8217;s a real pleasure for me when I get the time to watch your stream because you have a similar correction on typing that I do. I kind of have two or three times. So it kind of takes care of my imposter syndrome as well.</p>



<p><em>Ryan Welcher</em>: Yeah. Totally. I hit the daily key more than I hit any other key on my keyboard like without a doubt.</p>



<p><em>Birgit Pauli-Haack</em>: The backspace key.</p>



<p><em>Ryan Welcher</em>: Yeah. Exactly.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah.</p>



<p><em>Ryan Welcher</em>: Yeah. It&#8217;s worn out.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Yeah. So did you stream… So we are recording this on Friday, November 26th. And did you do a stream yesterday?</p>



<p><em>Ryan Welcher</em>: I did. I did a stream yesterday. It&#8217;s a part two, actually, Birgit, you gave me the topic of creating a pole block in Gutenberg. And so, we did. This is the part two, and there&#8217;s going to be a part three, because it&#8217;s actually a pretty complicated block. More complicated than I was expecting, but this series is going to be fun because I think I approached it one way in the first stream that we did last week. And it was bad.</p>



<p>It kind of worked, but it really demonstrated the power of inner blocks. And because I didn&#8217;t use inner blocks, basically what I wanted was a block that allowed you to put in options and you create as many or as little options as you wanted. So I was kind of rolling my own solution. And that&#8217;s never a good idea, not when you&#8217;ve got really powerful tools already available to you.</p>



<p>So in last week or sorry, yesterday&#8217;s. I refactored the block to use inner blocks and it went so much smoother. And now, I&#8217;m just trying to get the front end working, and so that&#8217;ll be next week most likely so.</p>



<p><em>Birgit Pauli-Haack</em>: Awesome.</p>



<p><em>Grzegorz Ziolkowski</em>: Front end is the most difficult because that&#8217;s something that it&#8217;s a new territory. That&#8217;s not so much exercised, especially by the core team. And we are looking at that, like started looking into that for the comments form block, which is also a quite complex thing to move to front, and then to the block concept. And yeah, so like I&#8217;m looking forward what you come up with just to like see and what the ideas you have and how people have to struggle with that today.</p>



<p>So, yeah. So I just want to also thank you for updating the Gutenberg examples repository, because we just didn&#8217;t have contributors that would actively work on that one. And the way you did it with live streams was just amazing so people can see everything how it works. And also, a good way for people to, and bring up-to-date their own configuration and use the latest and the most great approaches for the goal.</p>



<p><em>Ryan Welcher</em>: Awesome. Thank you. Yeah. I really enjoyed doing it and I think… I don&#8217;t have a huge following on Twitch. I think I have something like 60 subscribers or whatever, but I really feel like it&#8217;s helped a little bit to get a bit more exposure to some of the great tools. Like I said before, some of the fantastic tools that Gutenberg and WordPress have available. So build processes are pain. Well, we have scripts package. It just handles it for you. You don&#8217;t need to worry about it, right?</p>



<p>And so, I think as part of updating that, I think I hopefully got a bit of sort of exposure for those tools and just how powerful they are.</p>



<p><em>Birgit Pauli-Haack</em>: Awesome. Yeah. So I&#8217;m so glad that you&#8217;re here and let&#8217;s get a little bit further into the show.&nbsp;</p>



<h3 id="announcements"><strong>Announcements</strong></h3>



<p>So dear listeners, if you haven&#8217;t heard it yet, WordPress 5.9 release has been postponed to January 25th, 2022. A few modules needed two more weeks to get it into the release before the feature freeze. So instead of the first beta to come out on November 16th, it&#8217;s now scheduled for November 30th, 2021, because of the holidays in America and Europe, the release schedule now spans a bit longer. And instead of December 14th, the WordPress version is not to be released until end of January.</p>



<p>In the show notes, I have two, three links for you. One is from Tonya Mork. She&#8217;s the core release lead for this release and she published on the make blog, the decision making process about the postponement. She shared links of the issues list, and also the reasoning, the why the postponement was favored over removing the features was that weren&#8217;t ready yet.</p>



<p>And then, Anne McCarthy. She&#8217;s the FSE program manager, but also core release lead on this release for testing, posted a personal blog post with her thought process on why she voted for the delay. And in her post she also walks us through the issues and why it made sense to give them a few more days to land in the core release rather to rip out the whole FSE from the release, and then release it in 6.0. Turned out that the release lead from editor, Robert Anderson&#8217;s also was, of course, he found that it would be almost more work to rip out the features from the core than just wait two weeks and finish the little things that needed to be added to that.</p>



<p><em>Grzegorz Ziolkowski</em>: Yes. And in fact, all the blockers are already resolved so there is no more risk that the release would be further postponed. So you don&#8217;t have to worry about that at all. And one more note about that, if there wouldn&#8217;t be a holiday season, New Year and such, then we just have a two-week delay. And because of that making sure that everyone can get back to work after New Year&#8217;s, like then don&#8217;t have to rush and update their website and prepare for all the things that are usually connected with that so people will have much more time.</p>



<p>And I guess I also saw some opinions from people that they are happy that it&#8217;s happening in January, because it&#8217;s not so tight schedule before the New Year and Christmas and holidays. And so, depending on the parts of the world what people celebrate.</p>



<p><em>Ryan Welcher</em>: Yeah. I&#8217;m in a few different sort of communities that are not in WordPress Slack, but across the place or the internet. It&#8217;s either been like everyone&#8217;s sort of like, &#8220;Yeah. That&#8217;s the right decision,&#8221; or in some of the more… Hostile is not the right word. In some of the more lively places, it&#8217;s silence. Which usually means that it&#8217;s good. So if no one&#8217;s complaining, then that&#8217;s probably a good thing.&nbsp;</p>



<p>So I think it was the right move. Obviously, everyone seems used to be on board with it. And it&#8217;s just going to move us to a much more stable release. It&#8217;s very cool.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And I really heard a collective big sigh of relief from the WordPress e-commerce community to spread, to be spared yet another major WordPress release during the biggest e-commerce time of the year of the holidays. Yeah.&nbsp;</p>



<p><em>Grzegorz Ziolkowski</em>: Oh that&#8217;s a good note, because in the past when I was in the e-commerce business, like there was a feature freeze of on everything in December and sometimes even in November. So I now can relate to that. So I see where it comes from.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Although I think John Baptiste Audras who has been a core team rep, he had a comment on one of the comments on the release, first release blog post, who said, &#8220;Well, in the life of WordPress, we had 46 releases in December before, and there will always holidays and there will always, and yeah. It&#8217;s a global community.&#8221; And yeah. So there is a sense of, &#8220;Okay, it&#8217;s not only the American holiday or the European holiday season there are other holidays that are not, they are not so much in that are considered to blocking a WordPress release, so why should this one?&#8221; But I get it.</p>



<p>So if you need a fast overview of what will come for WordPress 5.9, the WordPress team published a fabulous video on the news section to show that you can or watch yourself, but also then show your clients, meet up members and others. So it&#8217;s really fabulously made. I also will have a link for you to a little longer video by Anne McCarthy about some of the full site editing features a little bit more in detail, also in the show notes. So the show notes will be quite big now.</p>



<h3 id="community-contributions-1"><strong>Community Contributions</strong></h3>



<p>So for the community contribution, I wanted to point out Marcus Kazmierczak kicked off an interesting discussion and you mentioned it as well, Ryan. Discussion about what would be a, should be a WordPress recommended development environment in view of the Dockers change of license for the desktop app. This developer discussion certainly can use your voice, you listeners as well.</p>



<p><em>Grzegorz Ziolkowski</em>: I think it&#8217;s-</p>



<p><em>Ryan Welcher</em>: Really interesting. Sorry. And unfortunate that Docker&#8217;s going to a paid model for their Docker for desktop app. I thought we had a good thing going with the E&amp;V in environment like the WordPress/E&amp;V package. I hope there&#8217;s something similar. I have a feeling we&#8217;re going to end up, we, being the community, will end up kind of rolling another solution, which is unfortunate because the more solutions you have, the sort of more diluted the waters get, and that it&#8217;s hard to kind of support all sorts of things.</p>



<p>I know VVV was used a lot. Having used it, I wouldn&#8217;t, I don&#8217;t really want to go back to that personally. Not that there&#8217;s anything wrong with it. It was just, if you&#8217;re doing a lot of sites, just the way that the… And this may have changed in the time it&#8217;s been since I&#8217;ve used it, but it took up a lot of space on your computer. And there&#8217;s a running joke about hit up, and then run them. And then, go have a coffee and watch a movie and come back and it&#8217;ll be done. But yeah. No. I hope that we can… I hope something changes there, but maybe not. I don&#8217;t know. What do you think, Grzegorz?</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. I think that&#8217;s very interesting what&#8217;s happening here because my initial thought would be that the post is about unifying everything and like picking one of the solutions. The benefit of WP/E&amp;V and using Dockers is that it works out of the box on Linux. So all the continuous integration that we use with Gutenberg, and now also with WordPress core, it just doesn&#8217;t need any special handing. It just works.</p>



<p>And by installing this single command, WP/E&amp;V install, you recreate the same setup on your local machine, which is like just amazing, because you can easily go back when something wrong happens and that was the whole idea. And it&#8217;s like Marcus mentioned that in call, we use a bit different setup, however, it&#8217;s also based on Docker. And there is something else used in one of the different products that is also used to by the WordPress project.</p>



<p>And yeah. So basically, it&#8217;s also a bit strange because the license for Docker allows open source usage, but with a special remark that if you work for a company and you are a paid contributor, if the company has over 250 people, or it turns like over $10 million revenue, then you need to pay for the license, which means like, for the most of the contributors from the committee, it&#8217;s not a blocker, however, there is no paid contributors like us, which we can afford the license, but for some people from different companies, the policy might be different so that creates friction.</p>



<p>So that&#8217;s really unfortunate that it happened, because instead of picking a right solution, now we need to decide what to do about Docker like for the whole community.</p>



<p><em>Ryan Welcher</em>: Well, do you think that this reminds me a bit of when React&#8217;s license conflicted with WordPress? I wonder if there might be some conversations that could happen down the road? I&#8217;m not sure. I mean I think this is a fairly recent licensing change. Is that accurate?</p>



<p><em>Grzegorz Ziolkowski</em>: Yes.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah.</p>



<p><em>Ryan Welcher</em>: I mean WordPress can&#8217;t be the only community that has paid contributors that this is going to affect. So maybe there&#8217;ll be some changing of the wording in the license. I don&#8217;t know. I mean I&#8217;m being cautiously optimistic that there&#8217;ll be some adjustments that will allow the usage to continue. Because I mean from a project point of view, it&#8217;s very hard to have that argument of we&#8217;re going to keep using this tool, but some of the people in our community have to pay for it and others don&#8217;t. And that&#8217;s kind of goes against the whole free, and what am I trying to say here? The open source.</p>



<p><em>Birgit Pauli-Haack</em>: Easy access. Yeah.</p>



<p><em>Ryan Welcher</em>: … mentality. Yeah. Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. So to be continued and to see what&#8217;s happening, but chime in on the discussion on the make blog post. So your opinion will be heard as well.&nbsp;</p>



<h3 id="what-s-released-gutenberg-12-0"><strong>What’s Released &#8211; Gutenberg 12.0</strong></h3>



<p>So now we are coming to our what&#8217;s release section and Gutenberg 12.0 was released. Do you want to do the honors, Ryan, and start us off going through the changelog?</p>



<p><em>Ryan Welcher</em>: Sure. I can do that. Yeah. So 12.0 was released on, I guess it would&#8217;ve been the 24th of this week. And then, there were 86 pull request it looks like. So we can start with the enhancements. So there&#8217;s 28 enhancements. We can go for the start with the block library. There&#8217;s a move WP Rest block navigation areas controller from Gutenberg to core. I should actually backtrack and mention that this release has a lot of sort of maintenance style releases.</p>



<p>So there&#8217;s a lot of like little bug fixes and little things. And so, some of these features might not be, or some of these enhancements and things might not be super newsworthy, but they&#8217;re all needed.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And we won&#8217;t go… Yeah. For our listeners, we won&#8217;t go through all 86. We highlighted a few, each one of us to kind of see what we want to talk about. And so, just kind of make sure you&#8217;re not preparing for a two-hour listen.</p>



<h3 id="enhancements"><strong>Enhancements</strong></h3>



<p><em>Ryan Welcher</em>: I&#8217;m not going to read through every single one. Okay. Great. So for the block library, there was some changes of some verbiage from website to site. One of the ones that we probably should talk about are the featured image. The featured image now looks like a placeholder, which is a really nice addition. So if you remember the featured image block prior to this release would have sort of a placeholder where you could click a button and upload something, but it didn&#8217;t really give you a sense of what it would look like in the post.</p>



<p>And so, they&#8217;ve changed that now. So now there&#8217;s a nice sort of like mountain scape dotted line graphic and it actually does respect the height attribute as well. So it&#8217;s a lot more representative of what it&#8217;s going to actually look like in your site layout, which is really nice.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. The featured image block is actually one of the theme blocks for the post template in the query loop. So if you&#8217;re not using any block themes, you won&#8217;t see that yet, but I really like how it kind of adapts to the dimensions the width and the height. So cool. Yeah.</p>



<p><em>Ryan Welcher</em>: Yeah.</p>



<p><em>Grzegorz Ziolkowski</em>: It also has a border that is always visible. So even if you unselect the block, you will still see the shadows of the feature image. And also, I want to mention that is the similar approach was taken previously for the site logo block. So if you are familiar with that, it&#8217;s just the same concept.</p>



<p><em>Birgit Pauli-Haack</em>: So the next item on our list is the navigation block now has enabled previews for the link blocks. We saw this on other editors, but now it&#8217;s also in the site editor for the navigation block. So when you hover over a link, it shows you a preview of the text, the image and the excerpt, if it&#8217;s available in a little popup window there. So you know exactly, okay. Oh yeah. That post is, or that page that I link to is the right one without having go to it and looking it up kind of thing. So this really enables a few more faster user interface for checking up on the links.</p>



<p><em>Ryan Welcher</em>: Yeah. And I think changes like that, which this release has a sort of a lot of sort of visual changes for the user. I think they&#8217;re great. I mean it makes, like WordPress historically has been a lot of like save it and hope for the best. Right? And these things kind of get us further away from that close. Much more to like a true what you see is what you get editing experience, right?</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. I like how Helen calls it, &#8220;The save and surprise.&#8221;</p>



<p><em>Ryan Welcher</em>: That&#8217;s it. Save and surprise. Yes. Helen. That&#8217;s great.</p>



<p>Yeah. Helen&#8217;s great. I guess there&#8217;s a few more in there. The next one that we wanted to sort of talk about was the paragraph block. We&#8217;ve merged the typography settings all in the same one. Specifically the drop cap setting had its own kind of section in the block inspector sidebar. Now that&#8217;s been moved into the typography panel, which I think is a nice, again, it makes sense.</p>



<p>It&#8217;s a typography change. It should go with the rest of the typography control. So that&#8217;s a nice little feature in there.</p>



<p><em>Birgit Pauli-Haack</em>: That we also pointed out for the people who are looking for it now, and don&#8217;t find it. You find it in the typography panel, which might not be expanded when you open up your sidebar.&nbsp;</p>



<p><em>Ryan Welcher</em>: Right.</p>



<p><em>Grzegorz Ziolkowski:</em> Unless the team author decided that you shouldn&#8217;t do that and they disabled that, because now we have this possibility and that&#8217;s a really great feature of block teams that basically any control can be disabled, like removed from the view in the sidebar.&nbsp;</p>



<p><em>Ryan Welcher</em>: Yeah. If you want to test this, I was testing this this morning actually with the TT1 theme blocks and that the drop cap is enabled. It&#8217;s in there and it&#8217;s good to go. And I believe drop cap is really the only block that really supports… Well, I shouldn&#8217;t say supports it. The block that you&#8217;d find it in the most is paragraph. I don&#8217;t know of any other blocks that have drop cap off the top of my head.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. It&#8217;s only the paragraph. You&#8217;re right. Yeah.</p>



<p><em>Ryan Welcher</em>: And just a side here. The way that they&#8217;re handling the typography and the borders, and there&#8217;s a new component. Well, it&#8217;s new to me. I think it&#8217;s tool… No. What&#8217;s it called? It&#8217;s the component that you click the three dots and you get the… It&#8217;s the tools, the tool panel? I think it&#8217;s… Yeah.</p>



<p><em>Grzegorz Ziolkowski</em>: Yes.</p>



<p><em>Ryan Welcher</em>: It&#8217;s very, very slick. I think that&#8217;s such a really nice way of combining lots of controls that I&#8217;m going to… You know what? I&#8217;m going to do a live stream where I use that in a block, because I think that would be super, super handy. Because historically, you would have the sort of the inspector controls and every little thing would, every panel would line up and you have a really long, like really tall, tall experience with a very complicated block. And I think this is going to be a really nice sort of tool for the block developers&#8217; toolkit to be able to put lots of complicated related things together and not take up the entire screen.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. The idea we discussed this on the show previously that the idea is to have more control over that. So block authors could also register their own controls that would be displaying one of those groups. So to have even better organization there.</p>



<p><em>Ryan Welcher</em>: Yeah. I think that&#8217;s a great addition.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. I got a question from some of the, from someone in the community, if there is an idea to actually, or is that in the future that you, as a user can change the order of those panels that maybe the featured image can go a little higher in the priority rather than being on the bottom of things, because it&#8217;s some, like in a post editor controls?</p>



<p><em>Ryan Welcher</em>: I can kind of speak to that a little bit. I&#8217;ve done a fair amount of work with SlotFill. And one of the things that I was in a lot of conversations with was this concept of, because… So in the post editor, there&#8217;s a SlotFill that allows you to insert a custom panel just below the publish panel. And we had this idea of priority, because what if there was five panels, how do you set the order?</p>



<p>And so, that devolved into a different conversation, but the idea… I think it&#8217;s a fantastic idea that those panels be sortable by the user. I mean I don&#8217;t know if anyone&#8217;s actually tried to do that, but that&#8217;s where that conversation of SlotFill priority ended up was first, we should allow the user to pick the order. And then, we can have… Then, we don&#8217;t need to worry about it. Then, they can order anything including panels that have been added by slots. So that doesn&#8217;t answer that question, but I think it&#8217;s on people&#8217;s radar. It&#8217;s definitely a fantastic user experience that we should probably be moving towards.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. So I&#8217;m going to scout out that issue and assuming it was in an issue discussed, kind of see if we can surface it again and another-</p>



<p><em>Ryan Welcher</em>: Yeah. I&#8217;ll find it for you. For sure.</p>



<p><em>Birgit Pauli-Haack</em>: Okay.&nbsp;</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. I remember that discussion. And the blocker that we had was that if that said developers&#8217; tool that not necessarily would be in favor of user when those priorities would be set. So we were in favor of having more organized way, like the groups we have now and giving the power to users to move those panels however they want. So that&#8217;s like something definitely some rather, and always being discussed this way.</p>



<p><em>Birgit Pauli-Haack</em>: All right. Let&#8217;s continue. And the site editor, it comes now with a welcome guide that gives you four panels, I think, and explains a little bit where you find things on the new site editor for the full site editing experience.</p>



<p><em>Ryan Welcher</em>: Yeah. You get a pop up when you first load the site editor. And then, when you first click on the little icon for the global styles editor, you&#8217;ll get a secondary sort of walkthrough there.</p>



<p><em>Birgit Pauli-Haack</em>: Right. Yeah. For those styles specifically. Yes. Awesome. Yeah.&nbsp;</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. I think it has four steps the last time I saw it, like it walks you through the different concepts of the site, which is pretty handy for new users.</p>



<p><em>Birgit Pauli-Haack</em>: Absolutely.</p>



<p><em>Ryan Welcher</em>: Yeah. I think it&#8217;s a great introduction to it.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Sooner or later we will find a place where, or find a way to actually put this on the user data instead of in the local storage, because those are going away. And then, you see all the welcome guides, again, when you come in with a new one, but that has been an ongoing issue or maybe now that most editors like the widget editors done, the site editors done, the post editors done, there&#8217;s one more coming that&#8217;s the navigation editor. And maybe after that, there might be a unifying idea on how to store that on a user basis.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. The next thing I would like to highlight in there is the styles. And there we have now in the section with blocks, we have now icons. So it just like a nice visual change that helps you to much easier to find the block you are looking for if you are familiar with the icons.</p>



<p>One thing that I miss there is like the section to get to there is like blocks. It doesn&#8217;t have an icon. So I had trouble in trying the place in the sidebar. So that&#8217;s could be next enhancement on the-</p>



<p><em>Ryan Welcher</em>: Yeah. When I was looking at that issue before this, I was also like, I don&#8217;t know how to get there. I&#8217;m just going to ….</p>



<p><em>Birgit Pauli-Haack</em>: Sometimes things are right in your face like a welcome guide and sometimes things are very subtle and I think it&#8217;s more like the… It&#8217;s still in the process of getting better. Yeah. So you don&#8217;t want to… Yeah. It&#8217;s not that you want to point people to it when it&#8217;s going to change a lot, but what it does, it&#8217;s in the style section of the style editor and you could with that do a side wide configuration or settings for any of your blocks. But right now it&#8217;s the core blocks, so you can say, &#8220;Okay, which is the default style for my heading? And which is my default topography for the paragraph?&#8221;</p>



<p>If your theme doesn&#8217;t do that, you can change that or you can override your theme, because you don&#8217;t like how the theme does your quotes, for instance, or something like that. So there is a place to make those changes for the full site, but on a block, individual block basis. So that&#8217;s for those who have done adventure into the full set editing experience with 5.9.</p>



<p><em>Grzegorz Ziolkowski</em>: The next feature that we want to cover is for the block stars. In the past, we would have in the cyber of the block, for instance, the quad block is a good example. It has several styles to pick from, and you would see the currently selected, like the preview for the currently selected block version.</p>



<p>And the change now is that instead of showing that, you are presented with buttons, and once you hover or you go with the, when you are using keyboard and you move focus to the button. Then, the preview is shown, which is pretty nice, because it was a bit too much, because it was too prominent and that&#8217;s not definitely something that&#8217;s the most important for the block. So that&#8217;s a nice change.</p>



<p>It also like the PR was quite big. So the changes were also included in the transform, like drop down menu. So when you go to the block tool bar, if you click on the icon of the block, you are presented with the ways how you can transform, for instance, the paragraph block, you can transform to the least, to the quote, and so on and so on.</p>



<p>And for some blocks, if they have block stars, there is also a list of possible options to pick from. I believe that before when you would hover over the option there, you would see preview. At the moment there is no preview. I don&#8217;t know why it happens. So I couldn&#8217;t identify that information. And yeah, but definitely something that would be just unified and the people will look the same at some point, at least this is what I hope for.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. I read through this and I think the biggest hurdle was that, so what I like is that it&#8217;s in both places, it&#8217;s in the sidebar and the styles are also in the transform on the block toolbar. So if the sidebar is not open, you still have the choices to go to the styles. And that there has no preview. It seems that there is a little bit of a placement issue there that all of a sudden, this gets really disjointed when you have the toolbar, and then you transform and have another preview kind of on that block tool.</p>



<p>So that is a little harder to solve them, but this PR had a lot of comments and different explorations on how to solve that. And it really made me realize that there is, even for the smallest things, there are a lot of things that need to be considered and there are quite a few people who have a lot of experience with that still trying to figure that out. So even if it&#8217;s a small, yeah, if it&#8217;s a small line item kind of show style preview over hover and focus, but there&#8217;s a lot of thought that goes into it, and even if you….</p>



<p>Yeah. So I really marveled on that that how people or designers and developers can articulate all the different things that they need to think about when you do that for. As Ryan mentioned, 42 million, 42% of the internet, these are heavy decisions to make. All right, Ryan, do you want to take the next one?</p>



<p><em>Ryan Welcher</em>: So the next one we have highlighted is the allow additional props on tools panel. I think this is just a nice little developer addition, be able to add whatever you need in there. I&#8217;m not that familiar. It&#8217;s a pretty small PR, looks like just basically spreading some props in there. So that one, again, I love it that this is sort of like thinking about the developer experience as well. Like one more tool for the toolkit so to speak, right?</p>



<p><em>Birgit Pauli-Haack</em>: Right. Yeah. If the developer has a custom block or something like that, and I need an additional top for the tool [crosstalk 00:39:34]-</p>



<p><em>Ryan Welcher</em>: Yeah. And which is….</p>



<p><em>Birgit Pauli-Haack</em>: … Yeah. Then, now there&#8217;s a relatively easy way to accommodate that through that component. Yes.</p>



<h3 id="bug-fixes"><strong>Bug Fixes</strong></h3>



<p><em>Grzegorz Ziolkowski</em>: Oh I think that takes us into the bug fixes.</p>



<p><em>Birgit Pauli-Haack</em>: Bug fixes.</p>



<p><em>Ryan Welcher</em>: Bug fixes, fiction? Bug fixes?</p>



<p><em>Birgit Pauli-Haack</em>: That&#8217;s a good band name, right?</p>



<p><em>Ryan Welcher</em>: Yeah. Bug fixes. There we go. First of all, it&#8217;s fixed background colors nested sub menus. I&#8217;m not that familiar with that particular PR. I&#8217;m just going to take a quick look at it. I don&#8217;t know. It just looks very, very, very small. So one liner, my favorite type of PR.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Right. But it solves a big problem, because the background [crosstalk 00:40:11]-</p>



<p><em>Ryan Welcher</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: … from your sub menus should be propagate over all those sub menus. Yeah.</p>



<p><em>Ryan Welcher</em>: For sure.</p>



<p><em>Birgit Pauli-Haack</em>: And quite a few have noticed that that&#8217;s not handled, even if it&#8217;s handled by the theme. Yeah. You still need to have it actually work on the core rather than every theme handling that problem. Yeah.</p>



<p><em>Ryan Welcher</em>: Next one here is the page list using entities instead of direct API Fetch, which I think is really nice, because we have it available to us to use the entities and why kind of not use what&#8217;s already there. So that&#8217;s a nice little change too.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And that if you go and as you listen, if you go and look at the PR that&#8217;s three, six, five, three, one, and you see the difference of what the effect of it is, and that is on the second load, there is no going back to the server and get it again. So there is no delay on the editor side, so which are… That&#8217;s pretty much the promise that the block editor has for, even for dynamic content that comes in that it&#8217;s immediate and it&#8217;s, doesn&#8217;t have another one at the server grabbing the information.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. It&#8217;s also start locally so whenever some other part of the code base wants to access the same data, it&#8217;s already there, unless there is some update that&#8217;s going from the server, there will be still the same data source used. So which is always a great improvement in terms of performance.</p>



<p><em>Ryan Welcher</em>: It also allows you to tie into some of the other, like some of the other tools like invalidate resolver, if you wanted to update this query, you can just pull, because we know how this query is built inside of get entity records. It&#8217;s sort of there&#8217;s a standardized approach. You could invalidate that and have it reload.&nbsp;</p>



<p>And also, the pull request has more removals than additions and that&#8217;s always a nice little pull request when you have less code. When you&#8217;re taking code out, but making it better. That&#8217;s always a good way of approaching things.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: That&#8217;s the best way.&nbsp;</p>



<p><em>Ryan Welcher</em>: Yeah. Exactly.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. There&#8217;s one which I don&#8217;t think that should be counted as back fix, because it&#8217;s a feature for the full site editing, and in part for the theme JSON, you now are able to opt out of color palette. So in your theme JSON, in the setting sections, if you go and you use update the color subsection, there is no color palette and color gradients, two fields that you can set default, which basically will disable the default color, probably have some gradients.</p>



<p>And you can go the other way around and use the same concept to enable that for a given block. So you it&#8217;s up to you. You can disable that for the block, enable for everything. It&#8217;s like you just can decide whatever is good for your team.</p>



<p><em>Ryan Welcher</em>: Yeah. That&#8217;s really interesting. I wasn&#8217;t aware, like I know that… I just did this whole deep dive into theme.json to kind of get an idea of what block support and what don&#8217;t, what they do and don&#8217;t support and all that stuff. And I didn&#8217;t realize that, I knew that you could turn it off currently, like before this release on a per block basis, but I didn&#8217;t realize that you couldn&#8217;t do it at the sort of the settings level.</p>



<p>So that&#8217;s nice. That&#8217;s a really nice enhancement, because there&#8217;s definitely going to be times where you don&#8217;t want to use that or maybe you only want to opt-in in certain places. So that&#8217;s really nice. That&#8217;s definitely an enhancement, I think. I don&#8217;t think it&#8217;s a bug.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. I feel the same way that that is really a good new feature kind of thing for the theme developer. But if I understood that correctly though is that the core color palette is still available on the back end of it. Because thinking about a theme switch, if the color palette of the thing goes away there&#8217;s still a color palette from core that will pick up some of the colors when the theme is a different theme and your content wouldn&#8217;t go just all white or all black or depending on the background.</p>



<p>Yeah. So what it switches off is the use of panel on the sidebar for the blocks as well as for the site editor.</p>



<p><em>Ryan Welcher</em>: Yeah. So if I understand it correctly, if you have a theme and it defines a palette, you could also say, &#8220;Here&#8217;s my palette, but also let&#8217;s use the core ones.&#8221; And then, yeah. And then, like you said, &#8220;You can opt out on a per block, but a basis.&#8221; But you&#8217;re right. You won&#8217;t lose anything to just get the core palette by default, I guess.</p>



<p><em>Birgit Pauli-Haack</em>: All right, so next. One of you, all the WebP extension.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Hang on. I had one that we skipped over it and there&#8217;s use… So the block API now also has use first child and last child when parsing lists from MS Word. That&#8217;s not so much a bug fix. It&#8217;s more like an enhancement of the parsing when you write something in MS Word, in Microsoft Word, and then copy-past it into the block editor. You now have a better list experience, because it uses these new, what is it, functions? So you can have a better parsing experience. That&#8217;s just for the content creators and those who are not writing in the block editor. So now it&#8217;s up to you. Back to you, Grzegorz.</p>



<p><em>Grzegorz Ziolkowski:</em> Yes. So in the block editor there was a block fix solution, which has change that add WebP extension in file past handler and get by even data, which for like visibility, for the same experience you mentioned with Microsoft Word, like when you copy and paste if you want, remove, you may just start use those extensions. Before, it was just removed or just like sanitized by the parser.</p>



<p><em>Birgit Pauli-Haack</em>: So now it can handle images at all of the WebP format, before it wouldn&#8217;t be a good image file.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. It was added to WordPress core so it just a sequence of that, that it has to be rolled out to all other places and it was easy to miss.</p>



<p><em>Birgit Pauli-Haack</em>: Okay. And there was some CSS and styling done now also for the code block, which didn&#8217;t get a lot of love before. So now you can do a few more things with the code block then. And your theme JSON, I would think or maybe it&#8217;s mostly to take the code out. Oh it&#8217;s still… Yeah.</p>



<p><em>Grzegorz Ziolkowski:</em> Yeah. The code lock needs much more love from the core contributors. It&#8217;s a very complex topic because all the codes like the JavaScript or CSS style that you need to load is gigantic so that&#8217;s why we didn&#8217;t come up with a good solution so far.</p>



<h3 id="documentation"><strong>Documentation</strong></h3>



<p><em>Birgit Pauli-Haack</em>: Which brings us to the documentation section and there were quite a few updates in the handbook concerning the theme JSON file. Do you want to talk about it, Ryan? I think you quite a few….</p>



<p><em>Ryan Welcher</em>: Well, yeah. The theme in block.json has been sort of my… I&#8217;ve been kind of focused on it myself and Marcus and Greg as well. Well, many people, not just us. But we probably talked about this a bit more in the developer experience as well. But some of these documentation things just sort of indicate things like there&#8217;s a schema entry that you can put into the theme in block.json. That is only for… Like it&#8217;s VS Code specific. You don&#8217;t need it if you&#8217;re not using VS Code, but VS Code is used by, I don&#8217;t know. I don&#8217;t even know what the percentage of people using VS Code would be.</p>



<p>Yeah. A lot of people. And we&#8217;re just sort of referring to this, they have to do the gif, the schema. We actually have it posted on like there&#8217;s a WordPress URL for it, which I can&#8217;t remember what it is wp.org. So it&#8217;s just updating that. It&#8217;s also hosted on schema store, but they&#8217;re all connected. So, yeah. So if you refer to it from the host and there&#8217;s more in the developer experience. I&#8217;ll talk about that but later.</p>



<p><em>Birgit Pauli-Haack</em>: And also updated that, and I just want to point it out for our listeners. There is a contributor handbook page that has a list of which version of the Gutenberg plugin landed actually, in which WordPress version, because there&#8217;s always a little bit of a disconnect like we have now Gutenberg 12, and only some pieces of that make it into the 5.9. But when 5.9 comes out in January, there might be about four more Gutenberg plugin versions and the people need to look up, especially a plugin developer is it kind of, what can I expect with sites that have 5.9 versus the plugin?</p>



<p>So that page has been updated and it&#8217;s in the developer.wordpress.org block editor contributors section. And so, you can make that a bookmark or something like that.</p>



<p><em>Grzegorz Ziolkowski:</em> Yeah. It&#8217;s very handy because I already forgot which one goes, the last version of Gutenberg blog that fully goes to the WordPress 5.9 release.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah.</p>



<p><em>Ryan Welcher</em>: It&#8217;s 11/9.</p>



<p><em>Birgit Pauli-Haack</em>: It&#8217;s 11/9.</p>



<p><em>Ryan Welcher</em>: And 12 didn&#8217;t make the cut, but who knows? Maybe there&#8217;ll be some features.</p>



<p><em>Birgit Pauli-Haack</em>: Well, I saw a few of the PRs on 12 that had the labeled backboard to 5.9, and that made it, I think this morning or Eastern time or no, Australia time. I think they were already rolled into core now. They are the backboard ones. So if you want to look at that, look at the release handbook, the release project to kind of see which made it in, which of the PRs from here made it into 5.9.</p>



<p>So now we come to Ryan&#8217;s favorite section of this release.</p>



<h3 id="developer-experience"><strong>Developer Experience</strong></h3>



<p><em>Ryan Welcher</em>: Yeah. So this is a new section that&#8217;s been added to the changelog. Recently, a lot of contributors have been spending time trying to improve the developer experience. That&#8217;s something that, as a developer advocate, we hear a lot that the documentation could be better. We need more examples. We, being like the royal we of developers who work with WordPress are like struggling a bit to get the information.</p>



<p>And so, yeah. So that&#8217;s what we&#8217;re doing here so like probably the biggest thing that we&#8217;ve done is the schema for block.json and theme.json. And that might not seem like a big deal, but when you are dealing with something like a theme.json file that has so many entries and so many possible combination of entries, having sort of a common source of truth, where in your editor, you start typing and it prompts you and shows you what can go in there.</p>



<p>That&#8217;s such a big win, both for ease of use and also for learning. And I think that&#8217;s really going to help a lot of people really get their head around… Like I&#8217;ve been spending a lot of time in theme.json lately, and I still don&#8217;t really get what goes where. And it just can be a lot. Right?</p>



<p>And so, some of the things that have been added is there&#8217;s a schema definition for block.json that was added. Block.json also supports custom blocks. So we&#8217;ve added sort of like a RegX to have a name in there. We&#8217;ve updated the schema URL to wp.org domain, which is really cool. Just a couple of fixed things like the attribute type can be an array, as well as some other things. Fixed schema tool allow for custom blocks and theme.json.</p>



<p>So there&#8217;s a lot of really nice enhancements, and we&#8217;re still working through some more enhancements. It&#8217;s kind of become a bit of a pet project of mine. There&#8217;s an open issue right now where we&#8217;re talking about valid versus supported when it comes to blocks. So for example, the button block. If you were to go into the button block, and then in its settings, go to border and turn off all four items. There&#8217;s only one of those items that actually affects anything in that block.</p>



<p>And so, the question becomes, technically that&#8217;s valid, because that setting, that border object supports four entries. But for this block, three of them don&#8217;t do anything. So that&#8217;s kind of a confusing developer experience. So how do we handle that?</p>



<p>So we have sort of have a conversation around making the schema a bit more granular. It&#8217;s more work, but it&#8217;s going to mean that when I, as a developer, sit down to start, trying to customize some of my blocks in theme.json, and I put an entry in, and I get that little squiggly green line that says, &#8220;This is wrong.&#8221; It&#8217;s because that block doesn&#8217;t actually do anything with that thing. Right? So anyways, lots more on the horizon there. That&#8217;s not part of this release, but I just wanted to go on a bit of a tangent there. So thank you for indulging me.</p>



<p><em>Birgit Pauli-Haack</em>: And we welcome that. Yeah. So I also want to add that there&#8217;s now… So GitHub discussions have been open for maybe three months now to get a little bit closer to the developers and get questions answered, but there&#8217;s now a separate sections that&#8217;s called Developer Experience. And I really appreciate that, because I think the problem that a lot of extenders have, so extenders or developers for plugins and themes and agency developers is that so many new things come with each plugin release that it&#8217;s really hard to keep up.</p>



<p>And the developer, none of our tools really accept a changelog, and you have to study them really carefully and to find those things that are actually relevant to your own work. There is no way to bubble that up into the… This is new section and this replaces that. So if you use the old one, yeah, like what you said, updating the Gutenberg examples, when you have the older method on how I&#8217;m doing things, which is still valid and it still works, but it&#8217;s so much easier to use some of the new tools that can be surfaced here in the developer experience section as well, much easier.</p>



<p>And so, I&#8217;m really happy that we have that. I still need to curate the things for people that come in three months later and don&#8217;t, can&#8217;t go through all the discussions there. But that&#8217;s a different problem solve. Yeah.</p>



<p><em>Ryan Welcher</em>: I&#8217;m also excited because it does, it gives us a place where people, like a sort of a central repository for people to drop stuff. And be like, &#8220;I don&#8217;t want to do that.&#8221; It&#8217;s not support. It&#8217;s not like, I don&#8217;t know how to do this. It&#8217;s more like, I don&#8217;t know how to find this or I don&#8217;t know where… The documentation is confusing. And that&#8217;s the kind of stuff that me, as a developer advocate, if I hear that. I&#8217;m like, &#8220;Well, show me where and let&#8217;s make it work.&#8221; Right? Because if it&#8217;s a small fix that brings so much joy to developers then we can make it happen. Right?</p>



<p><em>Birgit Pauli-Haack</em>: Right. Yeah.</p>



<p><em>Grzegorz Ziolkowski</em>: So the GitHub discussions, the motivation for that was also to give a space for people to propose some ideas? And because creating an issue is not something that is actionable if you don&#8217;t have the solution. So you need to first do some sort of research, discuss with other people, exchange opinions, and then that could be solidified and you can come up with a final solution and file an actual issue that people can work on.</p>



<p>So I really like this whole concept of discussions that GitHub introduced some time ago. And I&#8217;m glad that we finally have that on the Gutenberg repository. And one more note, there is also for the issues, there is also the same label developer experience, which is used to generate in the changelog those items that I uncover.</p>



<p><em>Birgit Pauli-Haack</em>: So what else is in the… Did you see anything in the code quality section or in the tool section that you want to talk about today?&nbsp;</p>



<p><em>Ryan Welcher</em>: The only thing that I noticed was TypeScript.&nbsp;</p>



<p><em>Grzegorz Ziolkowski</em>: That one.</p>



<p><em>Ryan Welcher</em>: Yeah. That one.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Opening a can of worms, right?</p>



<p><em>Ryan Welcher</em>: Yeah. I think TypeScript… I mean people come into WordPress from the JavaScript community are probably very familiar with TypeScript. I mean I&#8217;m not that familiar with TypeScript. It&#8217;s sort of, I mean I want to learn it, and like I know what it is. I just haven&#8217;t played with it that much, but I think it&#8217;s… If that&#8217;s what the JavaScript community is doing, then, I think it&#8217;s really cool that we are trying to get that into Gutenberg.</p>



<p>I do know that many of the packages do support TypeScript now. They do to some TypeScript definitions. There&#8217;s one package that I can&#8217;t remember which one it was that was written entirely in TypeScript. But getting that, trickling that into like block development or theme development and using TypeScript inside of that, I think will be really interesting.</p>



<p>I&#8217;ve even gotten on my Twitch, I have a repository for my Twitch streams, and someone is like… Like literally yesterday, someone opened up an issue saying, &#8220;Hey, it&#8217;d be really cool if you could show us how to do TypeScript with block development.&#8221; So I immediately closed it and ran away screaming, but no, I&#8217;m kidding. But I think that that is something that is probably, will that drive adoption? Will that drive… So people coming here with really strong JavaScript backgrounds, will that make it easier for them to get into block development, theme development, and things like that? I think it&#8217;s an interesting, it&#8217;s definitely an interesting tool. And I think there&#8217;s a learning curve, of course, but yeah. What do you think on that?</p>



<p><em>Grzegorz Ziolkowski</em>: So we already have TypeScript support in Gutenberg. So that the idea if someone is using WordPress scripts, they might want to use the same setup. I mean we do not entirely rely on TypeScript in the Gutenberg. So it&#8217;s like it&#8217;s mixed. Anyways, it&#8217;s possible so why not to open the same door for everyone else and they can benefit from TypeScripts? And if they are familiar, they will definitely be happy to start using that.</p>



<p>And this one is in WordPress script. So it&#8217;s not yet published to NPM. So you need to wait probably a few bit, more weeks because of the delay of WordPress 5.9, and the way how we do NPM publishing that is tied to the major WordPress releases, but once it&#8217;s out and something that people can explore. And the idea came from Marcus Kazmierczak, who opened a repository with an example of the block written in TypeScripts. So I just like look at the code and it didn&#8217;t seem to be very complex to replicate.</p>



<p><em>Ryan Welcher</em>: Yeah. Well, maybe I&#8217;ll just steal Marcus&#8217; repo for my live stream. Or get him to come on maybe. Maybe we can do it that way, give him some credit. Yeah. I think that could probably have gone in developer experience as well, to be honest. I mean I think that&#8217;s a, even just to… This is what&#8217;s coming. It&#8217;s not published, it&#8217;s not ready in scripts yet, but it&#8217;s there. Yeah.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: All right. So I&#8217;m taking it that this is kind of the end of our changelog discussion. I don&#8217;t have anything else and I&#8217;m looking at our time, we are quite into it already. And it&#8217;s so good to have you on this show, Ryan. So before we end the show, have any of you a final announcement or reminder that you want our listeners to know about?</p>



<p><em>Ryan Welcher</em>: For me, just if you&#8217;re interested in watching me code or type badly while I write code, check me out at Twitch. I&#8217;m Ryan Welcher codes on Twitch. I&#8217;m also Ryan Welcher codes on YouTube. Yeah. And there&#8217;s a repository associated with all my streams where if you want to see a specific topic, you can add an issue, mark it as a topic idea. And I love getting topics from the community. I&#8217;d rather do it that way than kind of come up with my own, because that&#8217;s speaking to what people need rather than what I think they need. But yeah. So yeah. I&#8217;d love to have you all drop by.</p>



<p><em>Birgit Pauli-Haack</em>: Awesome. And I&#8217;m looking forward to the part three of your full block.</p>



<p><em>Ryan Welcher</em>: Part three of 38.</p>



<h3 id="what-in-active-development-or-discussed"><strong>What in Active Development or Discussed</strong></h3>



<p><em>Grzegorz Ziolkowski</em>: Me as well. So I have one small thing also to mention. So we spoke a lot about developer experience. So this year, because I started that in January, I was exploring. I think react fast refresh to the WordPress script. So that&#8217;s basically allows you to write something in the code editor. And once you save that, it&#8217;s automatically gets updated or React code, and then also CSS, which is pretty nice when you are developing with WordPress scripts.</p>



<p>So yeah. I had breakthrough this week, actually, today in the morning and it&#8217;s all working and we are preparing this and together with the TypeScript changes, we mentioned in a few weeks that will be a part of WordPress scripts. And I hope that will improve the experience for all the people that develop blocks.</p>



<p><em>Birgit Pauli-Haack</em>: All right.&nbsp;</p>



<p><em>Ryan Welcher</em>: That sounds amazing.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah.</p>



<p><em>Grzegorz Ziolkowski</em>: Yeah. And I will leave the link to the pull request so people can check and see what&#8217;s that about.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. That&#8217;s great. I saw it kind of flowing by this morning, so I definitely want to dive into that. So last week I participated in a webinar with wonder for contributors, George Mamadashvili and Andy Fragen. And we talked through the various ways you as listeners, you can test Gutenberg and the workers releases and help us get, help the contributors to find all the little bugs and big bugs and how to test PRs.</p>



<p>George demonstrated that. You can use the Gutenberg nightly from the Gutenberg times to test what&#8217;s already emerged into Gutenberg, but not yet in a plugin. And then, you can test upcoming WordPress releases like the beta release and the release candidates by using the WordPress beta tester plugin that Andy Fragen and other contributors update all the time.</p>



<p>And if you&#8217;re new to testing, this webinar will hopefully get you started. And if you have questions, all three of us, George, Andy, and I are reachable via the WordPress Slack? And I&#8217;ll keep those links also on the show notes. So speaking about reachable, Grzegorz and Ryan, how can people get in touch with you?</p>



<p><em>Grzegorz Ziolkowski</em>: Ryan, maybe you go first?</p>



<p><em>Ryan Welcher</em>: Okay. Sure. Yes. I&#8217;ll go first. You can find me basically everywhere. I am @RyanWelcher. I&#8217;m @RyanWelcher on Twitter. I&#8217;m on make WordPress Slack. You can find me in there. I&#8217;m on post status, basically my full name, Ryan Welcher. My website&#8217;s ryanwelcher.com. And like I said, I am Ryan Welcher Codes on Twitch and on YouTube. So feel free to reach out. My DMs are open on Twitter and I&#8217;m always up for a conversation.</p>



<p><em>Birgit Pauli-Haack</em>: All right. Excellent.</p>



<p><em>Grzegorz Ziolkowski</em>: The same for me, like most of the places where I&#8217;m @GZIOLO. So that would be Twitter, GitHub, WordPress.org, WordPress Slack. So you can DM me or just shout at me publicly and ask of everything related to WordPress Core.</p>



<p><em>Birgit Pauli-Haack</em>: Excellent. And yes, I&#8217;m reachable on Twitter @BPH as well as the WP Slack @BPH. And as always, the show notes will be published on gutenbergtimes.com/podcast. This is episode 56 and if you have questions, suggestions or news, you can also then via email. That&#8217;s a blast from the past, but email at <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>. That&#8217;s <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>.</p>



<p>Well, thank you, Grzegorz. Thank you, Ryan. It was a great fun to have you again and talk to you about this nerd and gig out over all the good things Gutenberg. Thank you all for listening. This is goodbye for me.</p>



<p><em>Grzegorz Ziolkowski</em>: And thank you, everyone, for spending with us another hour. And hopefully, see you in two weeks.</p>



<p><em>Ryan Welcher</em>: Thanks for having me. I really appreciated it. And thank you for indulging all of my tangents on today&#8217;s podcast.</p>



<p><em>Birgit Pauli-Haack</em>: Oh, you know what? We might invite you again.</p>



<p><em>Ryan Welcher</em>: Oh, I&#8217;d love to come back.</p>



<p><em>Birgit Pauli-Haack</em>: Good. Yeah. Awesome. All right. Let&#8217;s get out of here. You take care. Bye.</p>



<p><em>Ryan Welcher</em>: Bye.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 27 Nov 2021 23:33:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Birgit Pauli-Haack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:40;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:"Gutenberg Times: Rendering WooCommerce Blocks, Hold the Phone, WTF is FSE? and more — Weekend Edition #194";s:7:"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=19686";s:7:"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://gutenbergtimes.com/rendering-woocommerce-blocks-hold-the-phone-wtf-is-fse-and-more-weekend-edition-194/";s: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:16505:"<p>Howdy, </p>



<p>For my US American friends, I am sending Happy Thanksgiving greetings! I hope y&#8217;all had a Happy Turkey Day! 🦃 🍗 You probably won&#8217;t get to read this until Monday or even later next week. Hopefully, the Black-Friday-Cyber-Monday offerings turn out well for you. </p>



<p>I am so grateful that you let me drop a weekend edition into your inbox every week. And thank you for the thoughtful notes, questions, ideas, and product updates.  Keep &#8217;em coming. It is you for whom I build the Gutenberg Times, and it has been an ongoing joy and wonderful adventure! </p>



<p>I am also grateful for everyone working on Gutenberg and on WordPress. The contributors and the Community at large has been a home to me in a world more and more divided.  I have been hurting through these two years of no in-person meetings, longing to see my friends again,  so I hope to meet you&#8217;all soon at a future WordCamp! </p>



<p>That&#8217;s it for now. Y&#8217;all have a great weekend! </p>



<p>Yours,💕<br />Birgit </p>




<p><strong>Table of Contents</strong></p>



<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#updates-on-wordpress-5-9">Updates on WordPress 5.9 </a><ul><li><a href="https://gutenbergtimes.com/feed/#new-schedule-for-january-25-2022-release">New schedule for January 25, 2022 release</a></li></ul></li><li><a href="https://gutenbergtimes.com/feed/#gutenberg-12-0-x-released">Gutenberg 12.0.x released</a></li><li><a href="https://gutenbergtimes.com/feed/#developing-custom-blocks">Developing Custom Blocks</a></li><li><a href="https://gutenbergtimes.com/feed/#full-site-editing-and-themes">Full-Site Editing and Themes</a><ul><li><a href="https://gutenbergtimes.com/feed/#fse-program-testing-call-11">FSE Program Testing Call #11</a></li></ul></li><li><a href="https://gutenbergtimes.com/feed/#wordpress-events">WordPress Events</a></li></ul></div>




<hr class="wp-block-separator is-style-wide" />



<h2 id="updates-on-wordpress-5-9">Updates on WordPress 5.9 </h2>



<p><a href="https://wordpress.org/news/2021/11/a-look-at-wordpress-5-9/"><strong>A Look at WordPress 5.9</strong></a> with the newly published video via WordPress News. </p>



<p>You can also take a longer discovery journey with <strong>Anne McCarthy</strong> on video <a href="https://www.youtube.com/watch?v=r59aR1tmY6k&t=75s"><strong>Exploring WordPress 5.9: Block theme flows, Styling, Patterns Explorer, &amp; more</strong></a></p>



<h3 id="new-schedule-for-january-25-2022-release">New schedule for January 25, 2022 release</h3>



<p class="has-drop-cap">After a few features were deemed not-quite ready, the WordPress release team held intense discussions about the feature freeze and the release schedule of WordPress 5.9.  Beta 1 was supposed to be released on November 16th. </p>



<p>After careful weighing a few aspects of contributor sanity, user expectations, and technical details, the release team decided to punt Beta 1 for two weeks and release it on November 30th, 2021. Because of the Holidays mostly in America and Europe, these two weeks delay resulted into a six-weeks postponement of the final release, now scheduled for January 25th, 2021. </p>



<p>Core release lead <strong>Tonya Mork</strong> has the details about the  <a href="https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/"><strong>WordPress 5.9 Revised Release Schedule</strong></a></p>



<p><strong>Anne McCarthy</strong>, release co-lead for testing, wrote in <a href="https://nomad.blog/2021/11/23/why-i-voted-to-delay-wordpress-5-9/"><strong>Why I voted to delay WordPress 5.9</strong></a>, her hope &#8220;is to bring you all along for the decision-making process and to demystify how this decision came to be.&nbsp;&#8220;</p>



<p><strong>Sarah Gooding </strong>over the WPTavern posted: <a href="https://wptavern.com/wordpress-5-9-revised-release-date-confirmed-for-january-25-2022"><strong>WordPress 5.9 Revised Release Date Confirmed for January 25, 2022</strong></a>.</p>




<p><strong>&nbsp;<a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/" target="_blank" rel="noreferrer noopener">&#8220;Keeping up with Gutenberg &#8211; Index 2021&#8221;</a>&nbsp;</strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly.  </p>




<hr class="wp-block-separator is-style-wide" />



<h2 id="gutenberg-12-0-x-released">Gutenberg 12.0.x released</h2>



<p class="has-drop-cap">Grzegorz Ziolkowski and I asked Ryan Welcher to be our guest for the Gutenberg Changelog episode 56. As he also worked on the release of this version, we heard first hand what the experience is like. </p>



<p>Most contributors worked on the final touches for the WordPress 5.9 Beta 1 Feature Freeze, there are no big new features expected in this version. This version is more about the small details that end up making a big difference in the overall user experience. </p>



<p>The most exciting updates: </p>



<ul><li>Block Styles Previews (<a href="https://github.com/WordPress/gutenberg/pull/34522">34522</a>),</li><li>Featured Image block Visual Enhancement in the Site Editor (<a href="https://github.com/WordPress/gutenberg/pull/36517">36517</a>), </li><li>the Site Editor Welcome Guide (<a href="https://github.com/WordPress/gutenberg/pull/36172">36172</a>) and </li><li>the updates to the JSON schemas for <a href="https://schemas.wp.org/trunk/block.json"><strong>block.json</strong></a> and <strong><a href="https://schemas.wp.org/trunk/theme.json">theme.json</a></strong>. </li></ul>



<p>The changelog  has a new section called <strong>Developer Experience.</strong> It lists the PRs that are relevant to WordPress extenders (plugin &amp; theme developers and developers working in agencies) as well as core contributors. It goes along with the <a href="https://github.com/WordPress/gutenberg/discussions/categories/developer-experience">GitHub Discussion</a> Category with the same name.</p>



<p><strong><a href="https://github.com/WordPress/gutenberg/releases/tag/v12.0.0">Find the full changelog on GitHub</a></strong>  </p>




<p><em>A huge thank You to Álvaro Gómez Velasco who mentioned the Gutenberg Changelog as one of his <a href="https://mrfoxtalbot.wordpress.com/2021/11/25/my-favorite-podcasts-2021-edition/"><strong>Favorite podcasts in 2021</strong></a>.</em></p>



<blockquote class="wp-block-quote"><p><a href="https://twitter.com/bph">&#8220;</a><a href="https://gutenbergtimes.com/feed/podcast">Gutenberg Changelog</a>&nbsp;podcast is the best way to keep up with changes in Gutenberg, the WordPress Block Editor. The show is very on point, full of useful content and they have some great guests too.&#8221;</p><cite>Álvaro Gómez Velasco</cite></blockquote>



<p><strong>Subscribe to the&nbsp;<a href="https://gutenbergtimes.com/podcast/">Gutenberg Changelog</a>&nbsp;podcast </strong><br />🎙️&nbsp;<a href="https://open.spotify.com/show/620NwVKQJGdTupy36zYxvg?mc_cid=4b6c9f88fe">Spotify</a>&nbsp;|&nbsp;<a href="https://podcasts.google.com/feed/aHR0cHM6Ly9ndXRlbmJlcmd0aW1lcy5jb20vZmVlZC9wb2RjYXN0">Google</a>&nbsp;|&nbsp;<a href="https://podcasts.apple.com/us/podcast/gutenberg-changelog/id1469294475">iTunes</a>&nbsp;|&nbsp;<a href="https://pca.st/podcast/f8445ec0-7508-0137-f267-1d245fc5f9cf">PocketCasts</a>&nbsp;|&nbsp;<a href="https://www.stitcher.com/show/gutenberg-changelog">Stitcher</a>&nbsp;|<br />🎙️&nbsp;<a href="https://www.podbean.com/podcast-detail/chi7j-9904a/Gutenberg-Changelog-Podcast">Pod Bean</a>&nbsp;|&nbsp;<a href="https://castbox.fm/channel/Gutenberg-Changelog-id2173375">CastBox</a>&nbsp;|&nbsp;<a href="https://www.podchaser.com/podcasts/gutenberg-changelog-878239/">Podchaser</a>&nbsp;|&nbsp;<a href="https://gutenbergtimes.com/feed/podcast">RSS Feed</a>&nbsp;</p>




<h2 id="developing-custom-blocks">Developing Custom Blocks</h2>



<p id="developing-custom-blocks"><strong><a href="https://twitter.com/AlexStandiford">Alex Standiford</a></strong> published a 2-hours course to teach developer how to <a href="https://www.wpdev.academy/course/build-a-block-from-other-blocks/"><strong>build a Block from other Blocks</strong></a>. He wrote: &#8220;You’ll learn how to build a WordPress block using existing WordPress blocks. This allows you to pre-build commonly used block patterns and drastically simplify the block editing experience, even with the most advanced page layouts.&#8221; </p>



<hr class="wp-block-separator is-style-wide" />



<p><a href="https://twitter.com/laras126"><strong>Lara Sc henck</strong></a> shared on her blog how to <a href="https://notlaura.com/gutenberg-snippet-retrieve-taxonomy-terms-with-compose-withselect-and-getentityrecords/"><strong>Retrieve taxonomy terms with compose, withSelect, and getEntityRecords</strong></a>, using the built-in @wordpress/data packages. </p>



<hr class="wp-block-separator is-style-wide" />



<p><strong><a href="https://twitter.com/ryanwelcher">Ryan Welcher</a> </strong>continues building a <a href="https://www.twitch.tv/videos/1215549420"><strong>Poll Block on his Twitch Live Stream</strong></a>. Last week, he started on the block. This week, he decided to abandons the original approach and rebuild it with the &lt;InnerBlocks/&gt; that is part of the WordPress scripts and takes care of the &#8220;CRUD stuff&#8221;. Check it out!  </p>



<hr class="wp-block-separator is-style-wide" />



<p>In his article, <strong>Nadir Seghir</strong>, code wrangler at Automattic, explains <a href="https://developer.woocommerce.com/2021/11/15/how-does-woocommerce-blocks-render-interactive-blocks-in-the-frontend/"><strong>how  WooCommerce Blocks plugin renders interactive blocks in the&nbsp;frontend</strong></a>. The gist of it? Both, PHP and React component read the HTML data attributes. It&#8217;s of course more complicated than this. Follow along! </p>



<h2 id="full-site-editing-and-themes">Full-Site Editing and Themes</h2>



<p><strong><a href="https://twitter.com/JS_Zao">Justin Sainton</a> </strong>takes his readers along on his journey to <a href="https://zao.is/blog/2021/11/22/building-the-new-pagely-com/"><strong>Building the New website of the hosting company Pagely</strong></a>, recently sold to GoDaddy. He writes about what excites him about the new way of building themes. He explains what FSE is and how to get started with great list of resources. In his Bad &amp; Ugly section, Sainton  &#8220;found things to be painful or otherwise confusing.&#8221; He puts a lot of work in getting to the actionable details. Readers beware the post is over 4,500 words.  </p>



<hr class="wp-block-separator is-style-wide" />



<p>If you want to contribute and stay on the bleeding edge of the development of Full-site Editing, Design Tool, Global Styles and block Themes, <a href="https://twitter.com/jeffikus"><strong>Jeffrey Pearce</strong></a> posted the<a href="https://make.wordpress.org/themes/2021/11/26/gutenberg-themes-week-of-november-22nd-2021/"><strong> Gutenberg + Themes 74th weekly round-up</strong></a> of approximately 40 theme related open issues and PRs. He also shares released merged features and updates as well as overview issues that are a great resource to keep up with the development. </p>




<p><strong><a href="https://gutenbergtimes.com/need-a-zip-from-master/">Need a plugin .zip from Gutenberg&#8217;s main (trunk) branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. <br />Have you been using it? Hit reply and let me know.</p>



<p><img alt="GitHub all releases" src="https://img.shields.io/github/downloads/bph/gutenberg/total" /></p>




<h3 id="fse-program-testing-call-11">FSE Program Testing Call #11</h3>



<p>The deadline for Call for Testing #11 Comments has been extended to December 7th, 2021. <a href="https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/"><strong>FSE Program Testing Call #11: Site Editing Safari</strong></a> There won&#8217;t be any zebras, rhinos and giraffes, though. </p>



<p>If you prefer an Italian version of the call for testing, <a href="https://twitter.com/succoallapera"><strong>Piermario Orecchioni</strong></a> published the translation: <a href="https://it.wordpress.org/team/2021/11/25/chiamata-per-il-test-del-programma-fse-11-un-safari-nella-modifica-di-un-sito/"><strong>ESF Program Test Call # 11: A Site Editing Safari</strong></a>. </p>



<p><a href="https://twitter.com/atachibana"><strong>Akira Tashibana</strong> </a>posted the Japanese version of the FSE Call for testing #11 <a href="https://ja.wordpress.org/team/2021/11/12/2381/"><strong>FSE プログラムのテスト募集 #11: サイト編集の探索</strong></a></p>



<p><strong><a href="https://twitter.com/cdils">Carrie Dils</a> </strong>prepared a <a href="https://carriedils.com/local-import-for-wordpress-5-8-x-beta-testing/">one file import for LocalWP</a> to have an easy way to set up a test environment for the FSE Call for Testing. </p>



<h2 id="wordpress-events">WordPress Events</h2>



<p><strong>December 11 + 12, 2021</strong> <br /><a href="https://taiwan.wordcamp.org/2021/"><strong>WordCamp Taiwan</strong></a></p>



<hr class="wp-block-separator is-style-wide" />



<p><strong>December 14th, 2021 &#8211; 5:00 pm ET / 22:00 UTC</strong> <br /><strong><a href="https://wordpress.org/news/2021/11/state-of-the-word-2021/">WordPress News</a></strong> <br /><strong>State of The Word w/ Matt Mullenweg</strong> + Q &amp; A</p>



<hr class="wp-block-separator is-style-wide" />



<p><strong>February 4+5, 2022 <br /><a href="https://birmingham.wordcamp.org/2022/">WordCamp Birmingham, AL</a></strong> <br />Call for Sponsors and Speakers are open now. </p>



<hr class="wp-block-separator is-style-wide" />



<p><strong>March 4th, 2022 all day <br /><a href="https://www.wordfest.live/2022/march/">WordFest 2022</a></strong> <br />a 24-hour festival of WordPress. <a href="https://www.wordfest.live/2022/march/call-for-speakers/">Call for Speakers is open</a>. Deadline Dec 6th, 2021. </p>



<hr class="wp-block-separator is-style-wide" />



<p class="has-drop-cap">On the<a href="https://wpcalendar.io/online/">&nbsp;<strong>Calendar for WordPress Online Events</strong>&nbsp;</a>site, you can browse a list of the upcoming WordPress Events, around the world, including WordCamps,  WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.</p>




<hr class="wp-block-separator is-style-wide" />



<p class="has-text-align-center"><strong>Don&#8217;t want to miss the next Weekend Edition? </strong></p>



<form class="wp-block-newsletterglue-form ngl-form ngl-portrait" action="https://gutenbergtimes.com/feed/" method="post"><div class="ngl-form-container"><div class="ngl-form-field"><label class="ngl-form-label" for="ngl_email">Type in your Email address to subscribe.</label><div class="ngl-form-input"><input type="email" class="ngl-form-input-text" name="ngl_email" id="ngl_email" /></div></div><button class="ngl-form-button">Subscribe</button><p class="ngl-form-text">We hate spam, too and won&#8217;t give your email address to anyone except Mailchimp to send out our Weekend Edition</p></div><div class="ngl-message-overlay"><div class="ngl-message-svg-wrap"></div><div class="ngl-message-overlay-text">Thanks for subscribing.</div></div><input type="hidden" name="ngl_list_id" id="ngl_list_id" value="26f81bd8ae" /><input type="hidden" name="ngl_double_optin" id="ngl_double_optin" value="yes" /></form>



<hr class="wp-block-separator is-style-wide" />





<p><a href="https://www.flickr.com/photos/13998657@N02/18526571462" target="_blank" rel="noreferrer noopener"></a><a href="https://www.flickr.com/photos/51035555243@N01/38744499" target="_blank" rel="noreferrer noopener"></a>Featured image: <a href="https://www.flickr.com/photos/21524575@N05/2301648783" target="_blank" rel="noreferrer noopener">&#8220;office block in sutton&#8221;</a>&nbsp;by&nbsp;<a href="https://www.flickr.com/photos/21524575@N05" target="_blank" rel="noreferrer noopener">Mr Tigggs</a>&nbsp;is licensed under&nbsp;<a href="https://creativecommons.org/licenses/by/2.0/?ref=openverse&atype=rich" target="_blank" rel="noreferrer noopener">CC BY 2.0</a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 Nov 2021 22:09:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:41;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:92:"Post Status: Post Status Excerpt (No. 34) — Developer Overload: Physical and Mental Health";s:7:"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=89989";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:34:"https://poststatus.com/excerpt/34/";s: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:3530:"<h2>&#8220;I prioritized my mental health over my physical health until I realized it was all the same thing.&#8221;</h2>



<p class="has-drop-cap">In this episode of Post Status Excerpt, David chats with Cory about taking care of your physical and mental health and how these factor into &#8220;Developer Overload.&#8221; Far too often (especially younger) professionals do not prioritize their health so they can work or do more in a day — until it comes back to bite them.</p>



<p><strong>Also: </strong>David shares that getting up early in the morning works for him and encourages people who have a hard time managing things in the morning to give it a shot — early mornings are usually quiet for many people, both in the place they live and the clients and employees they communicate with during the day.</p>







<p class="has-background">Every week <strong><a href="https://poststatus.com/podcast/the-excerpt/">Post Status Excerpt</a></strong> will brief you on important WordPress news — in about 15 minutes or less! Learn what's new in WordPress in a flash. <img src="https://s.w.org/images/core/emoji/13.0.1/72x72/26a1.png" alt="⚡" class="wp-smiley" /><br /><br />You can listen to <a href="https://poststatus.com/podcast/the-excerpt/">past episodes</a> of <strong>The Excerpt</strong>, <a href="https://poststatus.com/category/post-status-podcasts/">browse all our podcasts</a>, and don’t forget to subscribe on <a href="https://open.spotify.com/show/1m3xwXbe0MG5BzFVPtB0A7">Spotify</a>, Amazon Music, <a href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zaW1wbGVjYXN0LmNvbS8ySkU5c2M4UA">Google Podcasts</a>, <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">iTunes</a>, <a href="https://castro.fm/podcast/c53552c6-1ee0-4fc4-9de4-08ed6bf1ee4d">Castro</a>, <a href="https://www.youtube.com/c/PostStatus">YouTube</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, <a href="https://player.fm/series/wordpress-post-status-podcasts">Player.fm</a>, <a href="https://pca.st/05rR">Pocket Casts</a>, <a href="https://wordpress-post-status-draft-podcast.simplecast.com/">Simplecast</a>, or by <a href="https://feeds.simplecast.com/2JE9sc8P">RSS</a>. <img src="https://s.w.org/images/core/emoji/13.0.1/72x72/1f3a7.png" alt="🎧" class="wp-smiley" /></p>



<h3 id="h-mentioned-in-the-show"><img src="https://s.w.org/images/core/emoji/13.0.1/72x72/1f517.png" alt="🔗" class="wp-smiley" /> Mentioned in the show:</h3>



<ul><li><a href="https://twitter.com/dimensionmedia" target="_blank" rel="noreferrer noopener">David Bisset (Twitter)</a></li><li><a href="http://twitter.com/nathaningram">Cory Miller</a><a href="http://twitter.com/corymiller303"> (Twitter)</a></li><li><a href="https://twitter.com/post_status" target="_blank" rel="noreferrer noopener">Post Status (Twitter)</a></li></ul>



<h3><img src="https://s.w.org/images/core/emoji/13.0.1/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> Sponsor: <a href="https://poststat.us/sandhills" target="_blank" rel="noreferrer noopener sponsored nofollow">Bluehost</a></h3>



<p>Everything your website needs — from start-up to success story — is at Bluehost. Whether you're looking to create a website, blog, or online store, Bluehost will get you started with an all-in-one website platform tailored to your specific needs. Get a free domain name in your first year, free 24/7 lifetime support, and total design freedom with WordPress at Bluehost.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 25 Nov 2021 04: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:12:"David Bisset";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:42;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:"WordPress.org blog: Watch State of the Word at a Watch Party with your WordPress Friends";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=11641";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:104:"https://wordpress.org/news/2021/11/watch-state-of-the-word-at-a-watch-party-with-your-wordpress-friends/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:18279:"<p><a href="https://wordpress.org/news/2021/11/state-of-the-word-2021/">State of the Word 2021</a> is just around the corner!&nbsp;</p>



<p>Although attending State of the Word in person would be ideal, not all WordPress community members get to enjoy the experience of attending the speech live with friends.&nbsp;</p>



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



<blockquote class="wp-block-quote"><p><strong>We encourage WordPress meetup organizers and community members worldwide to (safely) host State of the Word 2021 watch parties —</strong><a href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/2021-state-of-the-word-watch-parties/"><strong>read this handbook to learn more</strong></a><strong>.</strong></p></blockquote>



<h2 id="why-organize-a-watch-party">Why organize a watch party?&nbsp;</h2>



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



<h2 id="how-do-i-organize-a-state-of-the-word-watch-party">How do I organize a State of the Word watch party?</h2>



<p>You can choose to host a watch party online or in person. Check out <a href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/2021-state-of-the-word-watch-parties/#schedule-a-state-of-the-word-watch-party-for-your-meetup">our handbook</a> for detailed instructions on how to schedule an event (including event templates).</p>



<div class="wp-block-columns">
<div class="wp-block-column">
<h3 id="online">Online</h3>



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



<div class="wp-container-61b8b3f35f590 wp-block-buttons">
<div class="wp-block-button"><a class="wp-block-button__link" href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/2021-state-of-the-word-watch-parties/#organizing-an-online-watch-party" target="_blank" rel="noreferrer noopener">Organize an Online Watch Party</a></div>
</div>
</div>



<div class="wp-block-column">
<h3 id="in-person">In Person</h3>



<p>If your region meets <a href="https://make.wordpress.org/community/handbook/meetup-organizer/2021-returning-to-in-person-meetups/">the guidelines for in person events</a> (if vaccines and testing are freely available), you can organize an in person watch party event (for fully vaccinated OR recently tested OR recently recovered folks) for your WordPress Meetup! Group members can hang out together (following local safety guidelines of course) and watch State of the Word live.</p>



<div class="wp-container-61b8b3f35fb87 wp-block-buttons">
<div class="wp-block-button"><a class="wp-block-button__link" href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/2021-state-of-the-word-watch-parties/#organizing-an-in-person-watch-party" target="_blank" rel="noreferrer noopener">Plan an In person Watch Party</a></div>
</div>
</div>
</div>



<div class="wp-block-spacer"></div>



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



<blockquote class="wp-block-quote"><p>If your Local WordPress Meetup is organizing an in person watch party, <a href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/2021-state-of-the-word-watch-parties/request-swag-for-in-person-watch-parties/"><strong>fill out this form</strong></a><strong> so that we can ship some swag for your group to celebrate!</strong><br />Deadline: November 30, 2021</p></blockquote>



<h2 id="what-else-do-i-need-to-know-about-organizing-a-state-of-the-word-watch-party">What else do I need to know about organizing a State of the Word watch party?</h2>



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



<ul><li><strong>Check out this </strong><a href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/2021-state-of-the-word-watch-parties/"><strong>handbook</strong></a><strong> for detailed instructions on how to organize a watch party, </strong>be it online or in person.</li><li>Looking for a Zoom Pro account to host your online watch party?&nbsp;<a href="https://make.wordpress.org/community/handbook/meetup-organizer/getting-started/special-virtual-events-zoom-request/">Request a community zoom pro account</a>&nbsp;for your event right away!</li><li>We have prepared some <a href="https://make.wordpress.org/community/handbook/meetup-organizer/event-formats/2021-state-of-the-word-watch-parties/email-templates-for-state-of-the-word/">email templates</a> that Meetup Organizers can use to spread the word in their Meetup groups.</li><li>Don’t forget to share on social media about your watch party events using the hashtag <strong>#StateOfTheWord</strong> so we can join in on the fun!</li></ul>



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



<h2 id="join-a-state-of-the-word-watch-party-near-you">Join a State of the Word Watch Party near you!</h2>



<p>We have compiled a list of State of the Word Watch Parties around the world. If you don&#8217;t see a watch party in your region listed here, <a href="https://meetup.com/pro/wordpress" target="_blank" rel="noreferrer noopener">check this page on Meetup.com</a>  to see if your local WordPress group is organizing one. If not, why don&#8217;t you consider organizing a watch party on your own? <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f642.png" alt="🙂" class="wp-smiley" /> </p>



<ul><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a href="https://www.meetup.com/WordPressNYC">WordPress NYC Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/WordPressNYC/events/282276960/" target="_blank">An In Person MeetUp: The State of the Word 2021 is in Manhattan.</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a href="https://www.meetup.com/South-Jersey-WordPress-Meetup">South Jersey WordPress Meetup</a>]  <a rel="noreferrer noopener" href="https://www.meetup.com/South-Jersey-WordPress-Meetup/events/282402090/" target="_blank">JerseyPress: State of the Word 2021 Watch Party</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Morris-County-NJ-WordPress-Group" target="_blank">Morris County NJ WordPress Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Morris-County-NJ-WordPress-Group/events/282402069/" target="_blank">JerseyPress: State of the Word 2021 Watch Party</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/WordPress-Montclair-Meetup" target="_blank">WordPress Montclair Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/WordPress-Montclair-Meetup/events/282326195/" target="_blank">JerseyPress: State of the Word 2021 Watch Party</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a href="https://www.meetup.com/wordpressscv">WordPress Santa Clarita Valley</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/wordpressscv/events/282056842/" target="_blank">State of the Word 2021 Watch Party</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/houston-wordpress" target="_blank">The Houston WordPress Meetup Group</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/houston-wordpress/events/282402609/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a href="https://www.meetup.com/NEOWordPress/">North East Ohio WordPress Meetup</a>] <a href="https://www.meetup.com/NEOWordPress/events/282456476/">State of Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a href="https://www.meetup.com/Birmingham-WordPress-Meetup">Birmingham WordPress Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Birmingham-WordPress-Meetup/events/282313212/" target="_blank">State of the Word Watch Party</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Lehigh-Valley-WordPress-Meetup" target="_blank">Lehigh Valley WordPress Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Lehigh-Valley-WordPress-Meetup/events/282304472/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a href="https://www.meetup.com/metro-detroit-wordpress-meetup/">Metro Detroit WordPress Meetup</a>] <a href="https://www.meetup.com/metro-detroit-wordpress-meetup/events/282519538/">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Milwaukee-WordPress-MeetUp" target="_blank">Greater Milwaukee Area WordPress Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Milwaukee-WordPress-MeetUp/events/282598865/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Eastbay-WordPress-Meetup" target="_blank">The East Bay WordPress Meetup Group</a>] <a href="https://www.meetup.com/Eastbay-WordPress-Meetup/events/282539457/">State of the Word 2021 (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Sacramento-WordPress" target="_blank">Sacramento WordPress Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Sacramento-WordPress/events/282593192/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png" alt="🇺🇸" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/WordPress-Meetup-Louisville" target="_blank">WordPress Louisville</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/WordPress-Meetup-Louisville/events/281858101/" target="_blank">State of the Word Watch Party and Discussion (WP Louisville, KY)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1e8-1f1f4.png" alt="🇨🇴" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/WordPressMedellin" target="_blank">WordPress Medellín</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/WordPressMedellin/events/282306436/" target="_blank">State of the Word 2021: Discurso de Matt &amp; Fiesta de Comunidad (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ed-1f1f9.png" alt="🇭🇹" class="wp-smiley" /> [<a href="https://www.meetup.com/Port-au-Prince-WordPress-Meetup">Port-au-Prince WordPress Meetup Group</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Port-au-Prince-WordPress-Meetup" target="_blank"></a><a rel="noreferrer noopener" href="https://www.meetup.com/Port-au-Prince-WordPress-Meetup/events/282350488/" target="_blank">Rejoignez-nous le 14 décembre pour regarder State of the Word 2021 (online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ec-1f1e7.png" alt="🇬🇧" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/wpcoventry" target="_blank">WordPress Coventry Meetup</a>]  <a rel="noreferrer noopener" href="https://www.meetup.com/wpcoventry/events/282302051/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ec-1f1e7.png" alt="🇬🇧" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/wpexeter" target="_blank">WordPress Exeter</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/wpexeter/events/282293408/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ee-1f1f9.png" alt="🇮🇹" class="wp-smiley" /> [<a href="https://www.meetup.com/WordPress-Meetup-Torino/">WordPress Meetup Torino</a>] <a href="https://www.meetup.com/WordPress-Meetup-Torino/events/282467417/">State of the Word 2021 Video Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f7-1f1fc.png" alt="🇷🇼" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Kigali-WordPress-Meetup" target="_blank">Kigali WordPress Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Kigali-WordPress-Meetup/events/282321636/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f3-1f1ec.png" alt="🇳🇬" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Lagos-WordPress-Meetup-Group" target="_blank">Lagos WordPress Community</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Lagos-WordPress-Meetup-Group/events/282321642/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f3-1f1ec.png" alt="🇳🇬" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Ijebu-WordPress-Meetup" target="_blank">Ijebu WordPress Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Lagos-WordPress-Meetup-Group/events/282321642/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1ec.png" alt="🇺🇬" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/Jinja-WordPress-Meetup" target="_blank">Jinja WordPress Meetup</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/Jinja-WordPress-Meetup/events/282637298/" target="_blank">State of the Word 2021 Watch Party &#8211; WordPress Community Uganda (Online)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f5-1f1f0.png" alt="🇵🇰" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/WordPress-Lahore" target="_blank">WordPress Meetups Lahore</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/WordPress-Lahore/events/282311458/" target="_blank">State of the Word 2021 Watch Party (In-person)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ee-1f1f3.png" alt="🇮🇳" class="wp-smiley" /> [<a href="https://www.meetup.com/WordPress-Bhopal">WordPress Bhopal</a>] <a href="https://www.meetup.com/WordPress-Bhopal/events/282470541/">State of the Word 2021 Watch Party (In-person)</a></li><li><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f8-1f1ec.png" alt="🇸🇬" class="wp-smiley" /> [<a rel="noreferrer noopener" href="https://www.meetup.com/WordPress-Singapore" target="_blank">WordPress Singapore</a>] <a rel="noreferrer noopener" href="https://www.meetup.com/WordPress-Singapore/events/282296137/" target="_blank">State of the Word 2021 Watch Party (Online)</a></li></ul>



<hr class="wp-block-separator" />



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



<p><em>The following folks contributed to this post: <a href="https://profiles.wordpress.org/anjanavasan/" class="mention"><span class="mentions-prefix">@</span>anjanavasan</a> <a href="https://profiles.wordpress.org/eidolonnight/" class="mention"><span class="mentions-prefix">@</span>eidolonnight</a> <em><a href="https://profiles.wordpress.org/evarlese/" class="mention"><span class="mentions-prefix">@</span>evarlese</a></em></em> <em>and <a href="https://profiles.wordpress.org/rmartinezduque/" class="mention"><span class="mentions-prefix">@</span>rmartinezduque</a></em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 24 Nov 2021 18:30:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Hari Shanker R";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:43;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:66:"WordPress Foundation: Give Back to Open Source this Giving Tuesday";s:7:"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=202833";s:7:"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:87:"https://wordpressfoundation.org/news/2021/give-back-to-open-source-this-giving-tuesday/";s: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:3907:"<p>Giving Tuesday is a global, non-profit movement that encourages people, organizations, and companies around the world to give, collaborate and celebrate generosity.</p>



<p>Hosted on the first Tuesday following Thanksgiving in the United States, this year the charitable giving event will be taking place on <strong>November 30, 2021</strong>.</p>



<p>With Giving Tuesday around the corner, many in the world are thinking about giving back. If you’re one of them, consider this opportunity to give back to open source.</p>



<p>2021 and the pandemic brought a lot of changes to the world, including the open source community. And the year wasn’t without its challenges.</p>



<p>Open source developers worldwide <a href="https://www.statista.com/statistics/912378/worldwide-open-source-professional-challenges-in-work/" target="_blank" rel="noreferrer noopener">still face roadblocks</a>, from “lack of training opportunities” to “getting management buy-in for open source.”</p>



<p>This is why the WordPress Foundation exists.</p>



<h2 id="how-does-the-wordpress-foundation-support-open-source">How does the WordPress Foundation support open source?</h2>



<p>As a non-profit organization, our <a href="https://wordpressfoundation.org/">work</a> is to ensure that open source software gets the support it needs. The funds we raise go toward ensuring free access to the projects we promote, protecting the WordPress trademark, and funding multiple programs aligned with our mission.</p>



<p><strong>Some of the programs the WordPress Foundation supports include</strong>:</p>



<ul><li><a rel="noreferrer noopener" href="https://wordpress.tv/" target="_blank">Video documentation</a> of WordCamp and WordPress meetup events.</li><li>“<a href="https://wordpressfoundation.org/tag/intro-to-open-source/">Intro to Open Source</a>” workshops that increase awareness and understanding of the open web and open source in regions around the world that have relatively less participation.</li><li><a rel="noreferrer noopener" href="https://doaction.org/" target="_blank">Charity hackathons</a> where developers come together and volunteer to build websites for nonprofit organizations around the world.</li><li><a rel="noreferrer noopener" href="https://learn.wordpress.org/workshops/" target="_blank">Workshops</a>, both live and recorded, on how to use and develop for the WordPress platform.</li><li>School mentorship programs to encourage interest in WordPress and open source development from a young age.</li><li>Improving documentation about how to use and develop for, and contribute to the WordPress project.</li></ul>



<p>But this is just the beginning. With your help, we can strengthen our support for these programs and fund many more exciting open source projects.</p>



<a href="https://i0.wp.com/wordpressfoundation.org/content/uploads/2018/08/capetown.jpg?ssl=1"><img /></a>Volunteers from do_action Cape Town 2018 working on charity websites



<h2 id="how-can-you-help-this-giving-tuesday">How can you help this Giving Tuesday?</h2>



<p>The future is open source, and whether you’re a believer or part of the open source community, you can play a part in helping build this foundation for generations to come.</p>



<p><strong>This Giving Tuesday, consider donating to the WordPress Foundation so we can work together toward a future that’s built on open source.</strong></p>



<p>You can choose to donate annually or make a one-time donation. Every gift counts!</p>



<div class="wp-container-61b8bf8f9e6b0 wp-block-buttons">
<div class="wp-block-button is-style-fill"><a class="wp-block-button__link has-white-color has-text-color has-background" href="https://wordpressfoundation.org/donate/"><strong>Donate to the WordPress Foundation</strong></a></div>
</div>



<p></p>



<p class="has-text-align-left">Thank you for supporting our mission!</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 24 Nov 2021 16: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:12:"Anjana Vasan";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:44;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:83:"HeroPress: Tales Of A Serial Contributor – Histórias de um colaborador em série";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=4283";s:7:"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:132:"https://heropress.com/essays/tales-of-a-serial-contributor/#utm_source=rss&utm_medium=rss&utm_campaign=tales-of-a-serial-contributor";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:31833:"<img width="1024" height="512" src="https://heropress.com/wp-content/uploads/2021/11/112321-min.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: I believe that the great advantage and differential of WordPress ... is its community." /><p><a href="https://heropress.com/feed/#portuguese"><span class="css-901oao css-16my406 r-poiln3 r-bcqeeo r-qvutc0">O texto também está disponível em português do Brasil.</span></a></p>
<p>Hey! My name is Daniel Kossmann. I&#8217;ve been WordPress user since 2009, one of the organizers of the Curitiba community, creator of the weekly newsletter called PainelWP, and a regular writer about WP in my blog. This is my before and after story from joining the WordPress community in Brazil. Happy reading!</p>
<h2>First contacts with the internet</h2>
<p>Since I was a kid I was very fond of computers and video games, but the internet opened a whole new world for me. I was so fascinated that at eleven years, around 1998, reading tutorials and analyzing HTML codes I created my first website on James Bond, of whom I was a big fan. In those first years, even though my parents didn&#8217;t quite understand what I was doing and why I was spending so much time in front of the computer, they backed me up by purchasing books and computers.</p>
<p>Little by little I learned more about programming and developing my systems in ASP and only then PHP. Since there weren&#8217;t so many websites teaching programming, I created a series of websites that taught others how to create websites and add small functionalities for them, like counters, login area, blinking text, &#8230;. At that time, I even created a content management system, that could receive contributions through a form and automatically published them every day at a given time, with a countdown timer in the website telling visitors when the next update would occur. This may be seen as trivial today, but at that time it was very uncommon. Those were really fun days, where I spent several nights learning new things and talking to other people who had the same interest in IRC on the deceased Brasnet network. If you are curious to learn more, check out <a href="https://belohorizonte.wordcamp.org/2016/daniel-kossmann-ferraz-automacao/">my interview at WordCamp Belo Horizonte 2016</a> (content in Portuguese).</p>
<h2>First contact with WordPress</h2>
<p>When the time came to choose my undergraduate, there was no doubt that it would be something related to computers. So I chose a Computer Science degree from Federal University from Parana (UFPR). During college, I also wanted to dabble in other fields, so I decided to create a blog in which to write movie reviews. Looking for a platform in which to easily publish texts, so I wouldn&#8217;t have to worry about coding because I already was doing this every day at school, I discovered WordPress. It didn&#8217;t take long and, in 2009, I launched my first public blog about movies, which after one year became <a href="https://www.interrogacao.com.br/"><i>interrogAção</i></a> (content in portuguese), a cultural hub on cinema, literature, and comics, with collaborators from several cities in Brazil. As in the case with my first tutorial websites and IRC conversations, many of these people I only knew virtually, but we had an intense contact while exchanging know-how.</p>
<p>Even though my focus was more on content creation and editorializing, I began to learn more about how to create themes and features in WordPress to customize the website. In one of these researches, I found out that an event focused on WP was going to happen in my city. Even not knowing a lot about the platform, I decided to attend and learn more.</p>
<h2>First contact with the community</h2>
<p>The event was <a href="https://curitiba.wordcamp.org/2010/">WordCamp Curitiba 2010</a> (content in portuguese) and I still remember how amazed I was at it being so cheap, I think it was R$60 or less, offering so many souvenirs and snacks. Other tech events I had attended had always charged more than double and hadn&#8217;t offered half of these things.</p>
<p>The talks were amazing, and everyone was always very kind and available. I was so excited about everything that I promised myself that I would volunteer during the next edition and also try to be a speaker. As I didn&#8217;t know anyone at the event, I challenged myself to talk with at least three people — I was extremely shy back then. Since then two of them have become lifelong friends.</p>
<p>At the end of the event, I found out that there was an after-party called WordCana (a joke with the word &#8220;cana&#8221;, from sugarcane, that is used to make distilled spirit). Even though I didn&#8217;t drink alcohol, I decided to go and it was awesome! There, I got to know the event&#8217;s speakers, organizers and attendees. Everyone talking as equals. And the fact that I didn&#8217;t drink alcohol didn&#8217;t change at all my interaction with them.</p>
<h2>From attendee to WordCamp organizer</h2>
<p>The promise I had made during that event came true! Less than two years later, I was helping to organize the next edition, <a href="https://curitiba.wordcamp.org/2012/">WordCamp Curitiba 2012</a> (content in portuguese), which was where I also gave <a href="https://wordpress.tv/2012/10/11/daniel-kossmann-ferramentas-livres-para-desenvolvimento-wordpress/">my first public talk</a> (content in portuguese). I was still very shy and, during the talk, I was so nervous that I couldn&#8217;t hold the microphone near my mouth. Because of that, even though it was a small room, people were having a hard time listening to my voice. Nevertheless, it was an important overcoming experience that has kept me desiring to improve my public speaking skills for future talks to this day.</p>
<h2>From user to entrepreneur</h2>
<p>Since I was a kid I had dreamt about opening my own company. Therefore, when I graduated in 2011, as I have always liked creating websites, I had little doubts about my next step: creating a web development company. I named it Spirallab, because of my passion for spirals and imagining turning it into a creative project lab. In the beginning, I didn&#8217;t define a direction and I worked with various systems and programming languages. Soon I realized that giving maintenance to these different solutions was a lot of work. So I opted to use a single platform, WordPress, due to its ease of use for my clients and the possibility to create various types of websites.</p>
<p>This decision allowed me to dive even deeper into the system, making better and faster-to-deliver solutions for my clients. As time went by, I also increased my services within the platform, adding support, maintenance, courses, consulting and optimized hosting for WordPress, which at that time was extremely hard to find. This allowed for a broader client range. It also enabled us to specialize in the platform, getting to better know all of its facets.</p>
<p>Even being a small company, never going beyond four people, I made sure to find ways to contribute to the WordPress community. After all, I managed to support my business without paying a single cent to use the platform. That is why I sponsored several WordCamps and meetups. This created a curious situation: Spirallab&#8217;s name was side by side with other sponsors that had 10 to 50 times its size. I wondered why there weren&#8217;t more companies doing the same. The sponsorship quotas started with a very low price tag, sometimes R$250. Considering the annual revenue of a company that uses WP as its main solution, I believe that this cost or investment could be easily included in its annual budget. I wish more companies, regardless of their size, would do that.</p>
<p>Besides that, I&#8217;ve talked at several meetups and WordCamps, where I shared what I learned in my day-to-day life. It was always and still is a big pleasure to be able to make these contributions. During the events, I gave away some stickers from my company that had an illustration of a digital alchemist (a kind of modern wizard). Because of that, and my looks (long hair and beard), I ended up being nicknamed the WordPress Wizard.</p>
<p>Eight years after Spirallab&#8217;s foundation, I decided to close the company&#8217;s activities and start a new chapter at <a href="https://www.pipefy.com/">Pipefy</a> in 2019, where I currently work as a WordPress Development Coordinator.</p>
<h2>The return of Curitiba&#8217;s WordPress Community</h2>
<p>After WordCamp 2012, Curitiba&#8217;s community became inactive. But the urge to continue with the events stayed with me. It took me three years to take the first step. So I got in touch with other people from the Brazilian community that I had met at WordCamp, to find out what was needed to restart the meetings, which are called meetups, in Curitiba. Coincidentally, I found out three people who wanted to do the same and we started planning the event through Slack, a text chat software. In less than a month, we organized the <a href="https://www.meetup.com/pt-BR/wpcuritiba/events/224130389/">first event</a>, on August 5, 2015. The most curious thing was that we were able to do all of the planning virtually, and only met for the first time in person on the day of the event.</p>
<p>Due to the speed in which we were able to organize this event, it may seem that we already had experience with this type of organization, but in fact, we didn&#8217;t have much, if any. So the first thing we asked ourselves was, &#8220;What would be nice to have included in the event if we were attendees?&#8221;. And two things stood out: having food and fun. So we ordered food (pizza, for convenience) and we tried to make something funner and without many formalities. We didn&#8217;t want to have those events where hardly anyone talks to anyone and after the talk, everyone leaves like they&#8217;re running away from something.</p>
<p>Keeping anyone from feeling lost, we made a brief presentation with slides at the beginning of the meetup, explaining what the event was and how it was organized, asking everyone to introduce themselves. This structure was maintained during all future events. Little by little, we carried out several experiments, such as a section where everyone could share news, themes, or plugin tips, or a classified section, where people could say if they were looking for or offering a particular service. Among the organizers, we always pre-arranged tips to be shared, in order to encourage others to participate. At first, few people engaged, but over time, they ended up becoming an important part of the event.</p>
<p>As I was extremely shy, getting in front of people to introduce the meetup was not easy.</p>
<blockquote><p>I was very nervous and ended up speaking very low, even stuttering a little. I wanted to change that and knew that the only way was to practice. I believe the meetup is a great place for this, as it is a small group of people with a common interest: learning.</p></blockquote>
<p>This makes everyone more receptive, creating a safe environment to participate in a variety of ways.</p>
<p>By the way, this is something very important to me: making the events an environment where everyone feels welcome and safe to ask questions and share experiences. Therefore, I always welcome new participants and encourage them to participate and talk to other people. Sometimes I retell the story of my first WordCamp, where I challenged myself to talk to three strangers.</p>
<p>Nowadays, although I&#8217;m still a reserved person, I&#8217;m not so shy anymore and can speak in public without as much difficulty. Because of this personal achievement, whenever possible, I encourage others to give their first talk and also share all the tips I used, and still use, to make better presentations. I get very happy when I see people overcoming these challenges and growing personally and professionally. Despite having changed a lot, I still set a personal challenge to always do something to take me out of my comfort zone in each and every talk. Sometimes it doesn&#8217;t have the expected effect, but at least I have one more funny story to tell.</p>
<p>It&#8217;s been more than six years since the first meetup (there was even a <a href="https://www.youtube.com/watch?v=vhYqoPaRsPo">commemorative video</a>) and throughout this time the WordPress community in Curitiba has held monthly events. I confess that it is not easy to maintain this consistency, but it is very rewarding!</p>
<h2>From developer to WordPress content creator</h2>
<p>I&#8217;ve always enjoyed reading technology newsletters, but there weren&#8217;t any specific to WordPress in Brazil. After much contemplation (and procrastination) I decided to create a newsletter that prioritized the spreading of content in Portuguese. And, on June 22, 2019, I published the Zero edition of <a href="https://www.painelwp.com.br/">PainelWP</a> (content in portuguese). Since then, I&#8217;ve searched and published the main news, tutorials, tips, events, and WordPress jobs weekly. My main goal with the newsletter is to inspire more people to create content about WP in Portuguese.</p>
<p>As I learn a lot from reading tutorials and articles, this year (2021), I also started writing content regularly about WordPress on <a href="https://www.danielkossmann.com/category/wordpress/">my blog</a> (content in portuguese). One of the publications I&#8217;m doing on behalf of PainelWP is to write about <a href="https://developer.wordpress.org/reference/functions/">how to use WordPress&#8217;s native PHP functions</a> (content in portuguese), with code examples. Writing regularly is quite challenging, but it&#8217;s very rewarding and I learn a lot. I recommend creating a blog and posting on it regularly to all professionals who want to improve their knowledge. One idea is to keep a record of what you are learning on the blog.</p>
<p>In addition, all of this is published under the <a href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons BY-SA license</a>, almost an equivalent of free software license for content. I chose this license because it makes it easy for content to be shared and used, like the WordPress source code.</p>
<h2>The Importance of the WordPress Community</h2>
<p>I believe that the great advantage and differential of WordPress, in addition to the numerous plugins and themes available, is its community. Because it&#8217;s an open platform and makes it easy to create websites, it attracts people with very different technical levels and backgrounds. This diversity helps create an open space for exchange, where everyone has something different to teach.</p>
<p>This creates a connection both online and in person. It&#8217;s very satisfying to meet people in person at community events. From these encounters, I&#8217;ve made several lasting friendships. These contacts also have helped me a lot professionally. I&#8217;ve received several job referrals from them and I&#8217;ve also referred several people.</p>
<p>An important tip I&#8217;ve learned in the WordPress community is: every time you&#8217;re in a conversation circle during events, leave a free space for a new person to join the circle. This format is also called <a href="https://ericholscher.com/blog/2017/aug/2/pacman-rule-conferences/">the Pac-Man Rule</a>.</p>
<p>If you&#8217;re not yet part of the WordPress community, I recommend looking for a meetup in your city, or nearby, to join. There are also several community meetings online now, which is a great opportunity to exchange knowledge with people from other cities. Hope you&#8217;ve enjoyed my story and see you at the next meetup or WordCamp!</p>
<h1 id="portuguese">Histórias de um colaborador em série</h1>
<p>Oi! Meu nome é Daniel Kossmann. Utilizo WordPress desde 2009, sou um dos organizadores da Comunidade de WordPress de Curitiba, criador da newsletter semanal PainelWP e escrevo regularmente sobre WP em meu blog pessoal. Esta é a minha história antes e depois de começar a participar da comunidade do WordPress do Brasil. Boa leitura!</p>
<h2>Primeiros contatos com a internet</h2>
<p>Desde criança já gostava bastante de computadores e videogames, mas a internet abriu um mundo totalmente novo para mim. Fiquei tão fascinado que aos 11 anos, por volta de 1998, lendo tutoriais e analisando códigos HTML criei o meu primeiro site (sobre James Bond, eu era um grande fã). Nesses primeiros anos, apesar de meus pais não entenderem direito o que eu fazia e porque passava tantas horas em frente ao computador, eles me apoiaram comprando livros e computadores.</p>
<p>Aos poucos fui aprendendo mais sobre programação e criando meus próprios sistemas em ASP e depois em PHP. Como existiam poucos sites em português que ensinavam programação, criei vários sites que ensinavam outras pessoas a criarem sites e adicionar pequenas funcionalidades neles (como contadores, áreas de login, textos piscando, …). Nesta época, também cheguei a criar meu próprio gerenciador de conteúdo, que aceitava o envio de conteúdo por colaboradores através de um formulário e fazia a publicação automaticamente todos os dias em um determinado horário (com um contador no site avisando quando seria a próxima atualização). Isto pode parecer bem trivial hoje em dia, mas naquele tempo ainda não era nada comum. Esta foi uma época bem divertida, onde passei várias madrugadas aprendendo coisas novas e conversando com outras pessoas que tinham o mesmo interesse no IRC, na falecida rede Brasnet. Se você ficou curioso para saber sobre essa época, veja a <a href="https://belohorizonte.wordcamp.org/2016/daniel-kossmann-ferraz-automacao/">entrevista que o WordCamp Belo Horizonte 2016 fez comigo</a>.</p>
<h2>Primeiros contatos com o WordPress</h2>
<p>Quando chegou a hora de escolher um curso superior, não tinha dúvidas que seria algo relacionado à computação. Então entrei no curso de Ciência da Computação na Universidade Federal do Paraná (UFPR). Durante a faculdade, também queria experimentar outras áreas e decidi criar um blog para escrever críticas de filmes. Procurando por uma plataforma que fosse fácil de publicar textos para que eu não tivesse que me preocupar com códigos (já via isso todo dia no meu curso), descobri o WordPress. Não demorou muito e em 2009 criei meu primeiro blog público sobre cinema, que depois de um ano se transformou no <a href="https://www.interrogacao.com.br/">interrogAção</a>, um portal cultural sobre cinema, literatura e quadrinhos, com colaboradores de várias cidades do Brasil. Assim como nos meus primeiros sites de tutoriais, e conversas do IRC, muitas dessas pessoas eu só conhecia virtualmente, mas tínhamos um contato intenso de troca de conhecimento.</p>
<p>Apesar do meu foco estar mais voltado para criação e editoração de conteúdo, comecei a aprender mais sobre como funcionava a criação de temas e funcionalidades no WordPress para poder personalizar o site. Em uma dessas pesquisas, descobri que iria acontecer um evento só sobre o WP na minha cidade. Mesmo não sabendo ainda muito sobre o sistema, decidi me inscrever para poder aprender mais.</p>
<h2>Primeiro contato com a comunidade</h2>
<p>O evento era o <a href="https://curitiba.wordcamp.org/2010/">WordCamp Curitiba 2010</a> e ainda lembro do quanto fiquei impressionado por ele ser tão barato (acho que foi R$60 ou menos), oferecer tantos brindes e ter lanches. Os outros eventos de tecnologia que havia participado sempre custaram mais que o dobro e não ofereciam nem metade dessas coisas.</p>
<p>As palestras foram ótimas e todo mundo era sempre muito gentil e disponível. Fiquei tão empolgado com tudo, que prometi para mim mesmo que iria ajudar na próxima edição e também tentar palestrar nela. Como não conhecia ninguém no evento, defini como desafio pessoal falar com pelo menos três pessoas (eu era extremamente tímido). Duas delas acabaram se tornando amizades de longa data.</p>
<p>No final do evento, descobri que haveria uma continuação chamada WordCana. Mesmo não gostando de beber, decidi ir e foi sensacional! Lá, conheci mais de perto os palestrantes, organizadores e participantes do evento. Todos falando de igual para igual. E o fato de não beber, não influenciou em nada minha interação com as outras pessoas.</p>
<h2>De participante para organizador do WordCamp</h2>
<p>A promessa que fiz durante o evento deu certo! Menos de dois anos depois, estava ajudando a organizar a próxima edição, o <a href="https://curitiba.wordcamp.org/2012/">WordCamp Curitiba 2012</a>. Nele também fiz <a href="https://wordpress.tv/2012/10/11/daniel-kossmann-ferramentas-livres-para-desenvolvimento-wordpress/">minha primeira palestra pública</a>. Eu continuava sendo muito tímido e durante a palestra, fiquei tão nervoso que não conseguia deixar o microfone perto da boca. Por conta disso, mesmo em uma sala pequena, as pessoas tiveram dificuldades para me escutar. Mesmo assim, foi uma importante experiência de superação, que me ajudou a continuar querendo melhorar minhas habilidades de falar em público em futuras palestras.</p>
<h2>De usuário para empreendedor</h2>
<p>Desde criança sonhava em abrir minha própria empresa e como gostava de criar sites, quando me formei em 2011, não tive muitas dúvidas sobre qual seria meu próximo passo: abrir uma empresa que desenvolve soluções para a internet. Chamei ela de Spirallab, por conta da minha paixão por espirais e pensando em torná-la um laboratório para projetos criativos. No início não defini muito um foco e trabalhei com vários sistemas e linguagens de programação diferentes. Aos poucos percebi que a manutenção dessas diferentes soluções estava ficando muito trabalhosa. Decidi que deveria utilizar apenas uma única plataforma e escolhi o WordPress, porque era fácil de ser utilizado pelo cliente e permitia a criação de diversos tipos de sites.</p>
<p>Esta decisão me permitiu aprofundar muito mais no sistema, fazendo com que criasse soluções melhores e mais rápidas de entregar para meus clientes. Conforme o tempo foi passando, também aumentei as opções de serviços oferecidos em volta da plataforma: suporte, manutenção, hospedagem otimizada para WordPress (na época era extremamente difícil achar algo assim), cursos e consultorias. Isto permitiu uma diversificação maior de clientes. Também possibilitou uma especialização na plataforma, conhecendo todos os aspectos que a envolviam.</p>
<p>Mesmo sendo uma empresa pequena (nunca passou de 4 pessoas), fiz questão de encontrar maneiras de contribuir com a comunidade do WordPress. Afinal, eu estava conseguindo sustentar o negócio sem precisar pagar nenhum centavo para utilizar a plataforma. Por isso ajudei a patrocinar vários WordCamps e meetups. Isso criava uma situação curiosa: o nome da Spirallab ficava ao lado de outros patrocinadores que tinham 10 ou 50 vezes o tamanho dela. Ficava então me perguntando porque não haviam mais empresas fazendo o mesmo. As cotas desses patrocínios iniciavam com um valor bem baixo (muitas vezes em R$250). Se formos considerar o faturamento de uma empresa que utiliza o WP como solução principal, acredito que este custo (ou investimento) poderia ser facilmente adicionado ao planejamento anual. Gostaria muito que mais empresas, independente do tamanho, fizessem isso.</p>
<p>Além disso, palestrei em vários meetups e WordCamps, onde compartilhei o que havia aprendido no meu dia a dia. Sempre foi (e ainda é) uma satisfação muito grande poder fazer estas contribuições. Durante os eventos eu distribuía um adesivo da minha empresa que tinha a ilustração de um alquimista digital (uma espécie de mago moderno). Por conta disto, e do meu visual (cabelo comprido e barba), acabei ganhando o apelido de o Mago do WordPress.</p>
<p>Oito anos depois da fundação da Spirallab, decidi encerrar as atividades da empresa e iniciei um novo capítulo na <a href="https://www.pipefy.com/">Pipefy</a> em 2019, onde trabalho atualmente como coordenador de desenvolvimento WordPress.</p>
<h2>O retorno da Comunidade de WordPress de Curitiba</h2>
<p>Depois do WordCamp 2012, a Comunidade de Curitiba ficou inativa. Mas a vontade de continuar com os eventos continuou na minha cabeça. Demorei três anos para dar o primeiro passo. Então entrei em contato com outras pessoas da comunidade brasileira que tinha conhecido no WordCamp, para saber o que era necessário para voltar a fazer os encontros (também chamados de <i>meetups</i>) em Curitiba. Por coincidência, descobri que mais três pessoas estavam querendo fazer o mesmo e começamos a planejar o evento através do Slack (software de bate papo em texto). Em menos de um mês, organizamos o <a href="https://www.meetup.com/pt-BR/wpcuritiba/events/224130389/">primeiro evento, no dia 5 de agosto de 2015</a>. O mais interessante foi que conseguimos fazer tudo isso virtualmente. Só no dia do evento que nós nos encontramos pessoalmente pela primeira vez.</p>
<p>Pela velocidade que conseguimos organizar este evento, pode parecer que já tínhamos experiência neste tipo de organização, mas na verdade não tínhamos muita (ou nenhuma) experiência como organizadores. Por isso, a primeira coisa que nos perguntamos foi: o que seria legal ter, caso fossemos participantes? E duas coisas se destacaram: ter comida e ser divertido. Então pedimos comida (pizza, pela praticidade) e tentamos fazer algo mais divertido e sem formalidades. Não queríamos aqueles eventos onde quase ninguém fala com ninguém e depois da palestra todos vão embora como se estivessem fugindo de algo.</p>
<p>Para que ninguém se sentisse perdido, no início do meetup fizemos uma breve apresentação com slides, explicando o que é o evento e como ele é organizado, pedindo para cada um se apresentar. Essa estrutura se manteve durante todos os próximos eventos. Aos poucos fomos fazendo vários experimentos. Desde uma seção onde todos podiam compartilhar uma notícia, dica de tema ou plugin, até um espaço para classificados, onde as pessoas poderiam dizer se procuravam ou ofereciam determinado serviço. Entre os organizadores, sempre combinamos previamente dicas para serem compartilhadas, de forma a estimular outras pessoas a participarem. No começo poucas pessoas participavam, mas com o tempo, estes momentos acabaram se tornando uma parte importante do evento.</p>
<p>Como eu era extremamente tímido, ficar em frente a várias pessoas para apresentar o meetup não era nada fácil. Ficava muito nervoso e acabava falando bem baixo, até gaguejando um pouco. Queria mudar isso e sabia que o único jeito era praticar. Acredito que o meetup é uma ótima oportunidade para isto, por ser um grupo pequeno de pessoas com um interesse em comum: aprender. Isso faz com que todos sejam mais receptivos, criando um ambiente seguro para participar de várias formas.</p>
<p>Aliás, isto é algo muito importante para mim: tornar os eventos um ambiente onde todas as pessoas se sintam bem vindas e seguras para fazerem perguntas e compartilharem experiências. Por isso, sempre dou boas vindas para os novos participantes e os incentivo a participarem e conversarem com outras pessoas do evento. Às vezes, conto a história do meu primeiro WordCamp, onde me desafiei a conversar com três pessoas desconhecidas.</p>
<p>Hoje em dia, apesar de continuar sendo uma pessoa mais quieta, não sou mais tão tímido e consigo falar em público sem tanta dificuldade. Por conta desta superação pessoal, sempre que possível, incentivo outras pessoas a darem sua primeira palestra e também compartilho todas as dicas que utilizei (e ainda utilizo) para fazer melhores apresentações. Fico muito feliz quando vejo pessoas superando essas dificuldades e crescendo pessoalmente e profissionalmente. Apesar de ter mudado muita coisa, ainda utilizo como desafio pessoal fazer sempre algo para me tirar da zona de conforto em cada palestra (às vezes não tem o efeito esperado, mas pelo menos tenho mais uma história engraçada para contar).</p>
<p>Já se passaram mais de seis anos desde o primeiro meetup (teve até um <a href="https://www.youtube.com/watch?v=vhYqoPaRsPo">vídeo comemorativo</a>) e desde lá a comunidade de WordPress de Curitiba faz eventos mensalmente. Confesso que não é nada fácil manter essa consistência, mas é muito gratificante!</p>
<h2>De desenvolvedor para criador de conteúdo sobre WordPress</h2>
<p>Sempre gostei muito de ler newsletters sobre tecnologia, mas não havia nenhuma específica de WordPress no Brasil. Depois de muito contemplar (e procrastinar), decidi criar uma newsletter que priorizasse a divulgação de conteúdo em português. E, em 22 de junho de 2019, publiquei a edição zero do <a href="https://www.painelwp.com.br/">PainelWP</a>. Desde lá, semanalmente procuro e divulgo as principais notícias, tutoriais, dicas, eventos e vagas de WordPress. Meu principal objetivo com a newsletter é inspirar mais pessoas a criarem conteúdo sobre WP em português.</p>
<p>Como aprendo muito lendo tutoriais e artigos, também comecei a escrever regularmente este ano (2021) no <a href="https://www.danielkossmann.com/category/wordpress/">meu blog conteúdo sobre WordPress</a>. Uma das publicações que estou fazendo por conta do PainelWP é escrever semanalmente sobre como utilizar <a href="https://developer.wordpress.org/reference/functions/">funções nativas em PHP do WordPress</a>, com exemplos de códigos. Escrever regularmente é bem desafiador, mas é muito gratificante e aprendo bastante. Recomendo a todos os profissionais que querem aprimorar seus conhecimentos, criar um blog e postar regularmente. Uma ideia é manter um registro do que você está aprendendo no blog.</p>
<p>Além disso, tudo isso é publicado sob a <a href="https://creativecommons.org/licenses/by-sa/4.0/deed.pt_BR">licença Creative Commons BY-SA</a>, quase um equivalente do software livre para conteúdo. Escolhi esta licença pois facilita que o conteúdo seja compartilhado e utilizado, assim como o código fonte do WordPress.</p>
<h2>A importância da comunidade de WordPress</h2>
<p>Acredito que a grande vantagem e diferencial do WordPress, além dos inúmeros plugins e temas disponíveis, é a sua comunidade. Por ser uma plataforma aberta e facilitar a criação de sites, ele atrai pessoas com vários níveis técnicos e históricos muito diferentes. Esta diversificação ajuda a criar um espaço aberto para trocas, onde cada um tem algo diferente para ensinar.</p>
<p>Isto cria uma conexão que se dá tanto online quanto presencialmente. É muito gratificante encontrar pessoas pessoalmente em eventos da comunidade. A partir desses encontros, fiz várias amizades duradouras. Estes contatos também me ajudaram bastante profissionalmente. Já recebi várias indicações para serviços a partir deles e também já indiquei várias pessoas.</p>
<p>Uma dica importante que aprendi na comunidade de WordPress é: toda vez que estiver em uma roda de conversa durante os eventos, deixe um espaço livre para que uma nova pessoa possa se juntar à roda. Este formato também é chamado de <a href="https://ericholscher.com/blog/2017/aug/2/pacman-rule-conferences/">regra do Pac-Man</a>.</p>
<p>Se você ainda não faz parte da comunidade de WordPress, recomendo procurar um meetup na sua cidade (ou próximo dela) para participar. Também há várias comunidades fazendo encontros online agora, que são uma ótima oportunidade de trocar conhecimento com pessoas de outras cidades. Espero que você tenha gostado da minha história e nos vemos no próximo meetup ou WordCamp!</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 24 Nov 2021 11:00:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Daniel Kossmann";s: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:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:65:"WPTavern: WordPress, Blogging, and the Things We Are Thankful For";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=126085";s:7:"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:171:"https://wptavern.com/wordpress-blogging-and-the-things-we-are-thankful-for?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-blogging-and-the-things-we-are-thankful-for";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4238:"<p class="has-drop-cap">On Saturday, one side of my family held our pre-Thanksgiving reunion. It had been two years since we were able to do it. I offered to host this year when our previous venue&#8217;s loss threatened to sideline the event for yet another year. Needless to say, I was exhausted by the time my last cousin and his wife got in the car and drove off toward their home in south Alabama.</p>



<p>Sunday, the day after, was the first relaxing day I had taken in weeks. But, I am not one for spending the entire day dedicated to watching TV &#8212; except when <em>Squid Game</em> was released.</p>



<p>Dusting off my rarely-used personal blog, I began to pen an update post on my National Novel Writing Month progress. Instead of actually doing that, at least until later in the night, I looked over years of published blog posts.</p>



<p>There is a rich history there, at least to me. My blog is a journal of my personal memories going back to 2003. For 18 years, I have been writing something, spitting out words into what can sometimes feel like an endless void. That naïve 19-year-old kid who was just setting foot into the online world was not thinking he would still be doing the same thing all these years later. He was just blogging. It was one part an extension of the angst-ridden notebooks he had filled as a teen. It was another part of a new and exciting journey.</p>



<p>For around an hour or so, I simply clicked and read and clicked and read. It is an extraordinary time to be alive, to take part in this moment in history where anyone from all over the world could live those same memories with me. And I can read their blogs. I can read about their hopes and dreams, view galleries of their pets, or catch up on their goals for the new year.</p>



<p>This is one of the reasons I subscribe to people&#8217;s personal blog feeds more so than news or development sites. At the end of the day, everything we do here is about people.</p>



<p>I took a deep dive through my archives, caught up with some fun moments I had shared with the world, and read over some of my old WordPress development tutorials. I even scanned through my obsession with Marie Kondōs tidying rules.</p>



<p>I was only disappointed that there were many moments that I decided not to share. I perused some of the notes from unpublished drafts of various instances of #WPDrama, discussions where I decided to keep my thoughts to myself rather than rock the boat. I skipped over headlines for books I had read but never reviewed. I remembered some life-changing moments that I never bothered to even write a draft about.</p>



<p>Aside from reminiscing over the past half of my life, I realized that my blog is older than many people who are just starting their own blogging journeys. WordPress, which also <a href="https://wptavern.com/happy-18th-birthday-wordpress">turned 18 this year</a>, is older than its next generation of users.</p>



<p>I also realized that I simply enjoy blogging. I had never given it much thought before &#8212; the <em>why</em> behind my continued participation in this artform. Perhaps it is because I have something I want to say from time to time. Maybe it is simply therapeutic. In the end, it might not matter. However, I am grateful that we have platforms like WordPress that allow us all to do it, regardless of our reasons.</p>



<p>As we close shop for the week for some much-needed rest, I am making a note to read through the bookmarked blog posts I have not gotten around to (thank you to everyone who has shared). I want to dive into the backlog of personal blogs I have yet to catch up on. I always check out every Tavern commenter&#8217;s website when they leave a URL in the form. I do not always get around to them immediately, but I have found many blogs that I genuinely enjoy reading this way.</p>



<p>Heading into this year&#8217;s U.S. Thanksgiving holiday, I am reminded of how fortunate I am to be a part of the WordPress community. It is a living, breathing ecosystem that has always remained true to its blogging roots. The platform allows millions of people to share their voices while owning their content.  That alone is something worth being thankful for.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 24 Nov 2021 00:05:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:75:"WPTavern: WordPress 5.9 Revised Release Date Confirmed for January 25, 2022";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=126003";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:193:"https://wptavern.com/wordpress-5-9-revised-release-date-confirmed-for-january-25-2022?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-9-revised-release-date-confirmed-for-january-25-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:4198:"<p>Last week WordPress 5.9&#8217;s release leads found a consensus for <a href="https://wptavern.com/wordpress-5-9-delayed-until-january-2022">delaying the release</a> after missing the deadlines for Beta 1 due to significant blockers. At that time they proposed a schedule for moving forward, and that is now <a href="https://make.wordpress.org/core/5-9/">confirmed</a>. Beta 1 is planned for November 30, 2021, with subsequent betas in December. RC 1 is scheduled for January 4, 2022, and the official release is anticipated on January 25.</p>



<p>For the past decade, Matt Mullenweg&#8217;s <a href="https://make.wordpress.org/core/2010/04/20/deadlines-are-not-arbritrary-theyre-a/">deadlines are not arbitrary</a> philosophy has guided core development, preventing  releases from being delayed by the desire to squeeze in one more feature:</p>



<blockquote class="wp-block-quote"><p>Deadlines are not arbitrary, they’re a promise we make to ourselves and our users that helps us rein in the endless possibilities of things that could be a part of every release. </p></blockquote>



<p>Deadlines make it possible for agencies, product developers, and hosting companies with millions of WordPress customers, to prepare for upcoming releases in a predictable way that ultimately enables more sites to update regularly. The situation with WordPress 5.9 is unique, because the effort involves shipping a set of interdependent features that also provide the foundation for a new way of theming.</p>



<p>&#8220;As the FSE features are very closely intertwined, removing some of its pieces would risk making the release unstable,&#8221; 5.9 Core Tech Lead Tonya Mork said in a <a href="https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/">post</a> announcing the new schedule. &#8220;To avoid delivering a sub-optimal experience, moving fixes to a 5.9 minor or 6.0 was ruled out.&#8221;</p>



<p>Mork said the team considered punting full-site editing (FSE) and the Twenty Twenty-Two theme that depends on it to 6.0 but saw more benefit in shipping the collection of features sooner.</p>



<p>&#8220;The 6.0 release isn’t due until April 2022—too long for the community to wait for them,&#8221; Mork said. &#8220;After processing this<a href="http://github.com/WordPress/gutenberg/issues/36556">&nbsp;list of issues</a>,&nbsp;Core&nbsp;Editor team saw the features could ship in 5.9 with the revised schedule.&#8221;&nbsp;</p>



<p>Anne McCarthy, who is co-leading testing for the release, is in the trenches with FSE and wrote a <a href="https://nomad.blog/2021/11/23/why-i-voted-to-delay-wordpress-5-9/">summary</a> of why she was proponent of delaying in this instance. She cited improved sustainability for contributors, and the value of users getting access to the whole suite of FSE features rather than smaller pieces, as factors in the decision.</p>



<p>&#8220;More specifically, if we were to push everything to 6.0, this would delay the Twenty Twenty-Two theme, hold back the launch of block themes in general, and delay a ton of user value in exploring ways to edit all parts of a site,&#8221; McCarthy said.</p>



<p>The decision to delay 5.9 to January 2022 has been met with positive feedback from all sides, and many following the progress have expressed their appreciation of the team&#8217;s transparency throughout the decision-making process. It&#8217;s reassuring to see the release leads acting in the interest of users and contributors, instead of forcing something half-baked forward. </p>



<p>In the meantime, if you want a sneak peak of some newer features coming in 5.9, check out the video the release team <a href="https://wordpress.org/news/2021/11/a-look-at-wordpress-5-9/">published</a> today. It showcases the amazing flexibility of the upcoming Twenty Twenty-Two theme and how much more you can do with WordPress without having to change to a different theme. If you want to be part of the team making FSE better for everyone, jump in and <a href="https://make.wordpress.org/test/tag/fse-testing-call/">start testing</a> the new features ahead of the beta release.</p>



<div class="wp-block-embed__wrapper">

</div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 23 Nov 2021 23:20:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:47;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:43:"WordPress.org blog: A Look at WordPress 5.9";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=11625";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"https://wordpress.org/news/2021/11/a-look-at-wordpress-5-9/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2465:"<div class="wp-block-embed__wrapper">

</div>



<p>WordPress 5.9 is expected to be a ground-breaking release. It will introduce the next generation of themes with <a href="https://make.wordpress.org/core/2021/10/06/introducing-twenty-twenty-two/">Twenty Twenty-Two</a> joining the fun and over 30 theme blocks to build all parts of your site. <a href="https://make.wordpress.org/core/5-9/">In anticipation of the January 25th release</a>, we hope you enjoy this sneak peek of 5.9.</p>



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



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



<h2 id="stay-tuned">Stay Tuned</h2>



<p>Stay tuned for more updates as the date draws near. If you want to help, the best thing you can do is <a href="https://make.wordpress.org/core/handbook/testing/beta-testing/">test everything</a>! For all the details, <a href="https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/">check out this Make Core post</a>.</p>



<p><em>Video props: <a href="https://profiles.wordpress.org/annezazu/" class="mention"><span class="mentions-prefix">@</span>annezazu</a> (also co-wrote the post) <a href="https://profiles.wordpress.org/michaelpick/" class="mention"><span class="mentions-prefix">@</span>michaelpick</a> <a href="https://profiles.wordpress.org/matveb/" class="mention"><span class="mentions-prefix">@</span>matveb</a> <a href="https://profiles.wordpress.org/beafialho/" class="mention"><span class="mentions-prefix">@</span>beafialho</a> <a href="https://profiles.wordpress.org/javiarce/" class="mention"><span class="mentions-prefix">@</span>javiarce</a> <a href="https://profiles.wordpress.org/critterverse/" class="mention"><span class="mentions-prefix">@</span>critterverse</a> <a href="https://profiles.wordpress.org/joen/" class="mention"><span class="mentions-prefix">@</span>joen</a>.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 23 Nov 2021 21:02:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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:"";}}}}}i:48;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:104:"WPTavern: GoDaddy Data Breach Exposes 1.2 Million Active and Inactive Managed WordPress Hosting Accounts";s:7:"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=125998";s:7:"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:253:"https://wptavern.com/godaddy-data-breach-exposes-1-2-million-active-and-inactive-managed-wordpress-hosting-accounts?utm_source=rss&utm_medium=rss&utm_campaign=godaddy-data-breach-exposes-1-2-million-active-and-inactive-managed-wordpress-hosting-accounts";s: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:3380:"<p>In a disclosure to the U.S. Securities and Exchange Commission (SEC) that was <a href="https://www.sec.gov/Archives/edgar/data/1609711/000160971121000122/gddyblogpostnov222021.htm">published today</a>, GoDaddy announced a data security breach impacting its WordPress managed hosting customers. The company discovered unauthorized third-party access to its hosting environment on November 17, 2021, through an exploited vulnerability.</p>



<p>GoDaddy&#8217;s initial investigations show the attacker gained access using a compromised password beginning on September 6, 2021. Nearly every sensitive data point associated with hosting a WordPress website was compromised, including customer email addresses, admin passwords, sFTP and database credentials, and SSL private keys. GoDaddy published the following summary of data the attacker had access to for more than two months:</p>



<ul><li>Up to 1.2 million active and inactive Managed WordPress customers had their email address and customer number exposed. The exposure of email addresses presents risk of phishing attacks.</li><li>The original WordPress Admin password that was set at the time of provisioning was exposed. If those credentials were still in use, we reset those passwords.</li><li>For active customers, sFTP and database usernames and passwords were exposed. We reset both passwords.</li><li>For a subset of active customers, the SSL private key was exposed. We are in the process of issuing and installing new certificates for those customers.</li></ul>



<p>GoDaddy has more than 20 million customers but only the managed WordPress hosting accounts were affected by this breach. Looking further into the incident, <a href="https://www.wordfence.com/blog/2021/11/godaddy-breach-plaintext-passwords/">Wordfence claims that GoDaddy was storing sFTP credentials as plaintext</a>, although GoDaddy has not officially confirmed it:</p>



<blockquote class="wp-block-quote"><p>GoDaddy stored sFTP passwords in such a way that the plaintext versions of the passwords could be retrieved, rather than storing salted hashes of these passwords, or providing public key authentication, which are both industry best practices.</p><p>We confirmed this by accessing the user interface for GoDaddy Managed Hosting and were able to view our own password&#8230;When using public-key authentication or salted hashes, it is not possible to view your own password like this because the hosting provider simply does not have it.</p></blockquote>



<p>GoDaddy&#8217;s stock tumbled after the SEC disclosure got picked up by major news organizations, finishing down 5.25%. The company <a href="http://previous incidents: https://twitter.com/lenraleigh/status/1462974068588789769">emailed its customers</a> to notify them that their accounts may have been compromised during the two months when the attacker had unauthorized access.</p>



<img />



<p>The incident has damaged customers&#8217; trust and puts developers and agencies in an uncomfortable position if they are required to notify their customers about the breach. Impacted site owners will need to watch for malware, suspicious activity, and potential phishing attacks.</p>



<p>Godaddy says it has already taken steps to further secure its provisioning system and is continuing its investigation with the help of an IT forensics firm and law enforcement.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 23 Nov 2021 04:55:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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:"
	
	
	
	
	
	
";s: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:"WPTavern: How Do Post Formats Fit Into a Block Theme World?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=125982";s:7:"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:161:"https://wptavern.com/how-do-post-formats-fit-into-a-block-theme-world?utm_source=rss&utm_medium=rss&utm_campaign=how-do-post-formats-fit-into-a-block-theme-world";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5899:"<p class="has-drop-cap">Over the weekend, Nick Bohle asked Ellen Bauer of Elma Studio <a href="https://twitter.com/nickbohle/status/1462231308697018373">how post formats fit into the block-theming world</a>. The question was a proposal for her a WordPress theme and FSE <a href="https://twitter.com/i/spaces/1ZkJzbaDPVgJv/peek">chat she held yesterday</a> via Twitter Spaces. I could not attend and see if Bauer touched on the subject, but the question is something I have given a lot of thought to not that long ago.</p>



<p>Over the summer, I <a href="https://twitter.com/justintadlock/status/1407208677795373056">tweeted out a screenshot</a> of an experiment around post formats. A part of me was trying to figure out if we could revive a dying feature, one I continue to use today.</p>



<img />Aside post format archive.



<p>I have been using post formats since before they were a thing. &#8220;Asides&#8221; were one of the precursors to the feature landing in WordPress. I wrote my first on my personal blog back in 2006. I had borrowed some code that WordPress cofounder Matt Mullenweg had <a href="https://ma.tt/2004/05/asides/">posted two years earlier</a>. It was a concept he had borrowed from others.</p>



<p>For me, it was a way to give a unique layout to quick posts and links without all the beefiness of a long-form article.</p>



<p>In 2011, WordPress 3.1 launched with a new taxonomy. Users could choose between nine different formats for their posts, assuming their theme supported one or more of them. The goal was to allow theme authors to design custom layouts around each one.</p>



<p>For much of the community, it felt like WordPress was chasing Tumblr&#8217;s post content feature. The allure quickly wore off after it seemed to have hit a standstill beyond its initial release. Besides a few fixes and trivial enhancements under the hood, post formats never amounted to much.</p>



<p>They have remained a niche feature over the years. A few theme authors still add in support. Some of us old-school bloggers who have been using them in some form or fashion are still hanging on. But, post formats have been dead for a long time.</p>



<p>Therefore, I decided to try to make them work for block themes.</p>



<p>One of the most frustrating things I encountered with post formats in this block-based theme project was how powerless I felt over making them work &#8220;the old way.&#8221; The dynamic nature of classic theming meant that I could switch post content templates out on pages that listed multiple posts. Query Loop and its inner Post Template block do not allow me to show a different template for a quote or gallery-formatted post, for example.</p>



<p>This was frustrating because that part of the design process was out of my hands. If I wanted to do something as simple as show an entirely different design for an aside post within a mix of normal posts, I could not do so as the theme designer, at least not without doing some hacky workarounds.</p>



<p>My &#8220;light bulb&#8221; moment was when I realized that it was OK to not have that control. I needed to get outside of the mindset that the design was mine and mine alone. That is viewing creation through a classic theming lens. My approach was wrong. Instead, I had to start thinking about how to hand over these design tools to the user.</p>



<p>The question became: Can I create something that utilizes that original post format concept while giving users the freedom to do what they want?</p>



<p>Then, it dawned on me. The following is the response I tweeted to Jeff Chandler, who had <a href="https://twitter.com/jeffr0/status/1407211205685661700">asked if I thought post formats</a> would work as patterns:</p>



<blockquote class="wp-block-quote"><p>I think of blocks themselves as an evolution of post formats. Video, audio, embeds (basically cool links), quotes, etc. Most of the elements are already there. Patterns just give users an easy way to insert various designs, which could build off those blocks.</p></blockquote>



<p>Maybe post formats as they currently exist are dead. However, the idea of designing a layout around specific types of posts is very much alive.</p>



<p>If users want to embed a single video into a post, it is just a matter of copying and pasting a link. To share a quote they found from their favorite author, they merely need to drop it into a Quote block. Other than chat posts (let&#8217;s just gloss over those entirely), the concept of post formats has simply been replaced with blocks.</p>



<p>However, theme authors still have a role to play. If all the elements for post formats have been essentially replaced by blocks themselves, that means designers can have a field day building patterns around them.</p>



<img />Patterns built for post formats.



<p>That led me to build off my original idea for asides, my favorite post format. Instead of offering a single design, I built three different patterns for users to choose from. End-users could mix and match how they appeared on the front end.</p>



<p>I also built a custom <code>taxonomy-post_format-aside.html</code> template to showcase them on their archive page. It merely displayed the published date and the post content, which the user controls.</p>



<p>I went back to the drawing board and built a quote pattern that I liked. Again, it would be up to the user whether they wanted that particular design. They could always go in a different direction.</p>



<img />Quote block pattern and custom style.



<p>In some ways, post formats were always limiting. The feature was never fleshed out, and there were only nine allowed formats. At the end of the day, each was merely a term within a taxonomy. There were never any rules about how it all was supposed to work. Maybe that is not such a bad thing. Now, posts can be anything users want them to be.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 22 Nov 2021 23:57:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"*data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Tue, 14 Dec 2021 16:09:34 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Tue, 14 Dec 2021 16:00:16 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 1";s:16:"content-encoding";s:4:"gzip";}}s:5:"build";s:14:"20211023013714";}