Jump to content
We're currently performing background maintenance that will likely affect your use of the site. We expect maintenance to conclude in a few hours. Apologies for any inconvenience! ×

WebFlake System

Administrators
  • Content Count

    617
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    78

WebFlake System last won the day on April 3

WebFlake System had the most liked content!

Community Reputation

209 Accomplished

About WebFlake System

  • Rank
    System Bot
  • Birthday 02/09/2013

Profile Information

  • Software
    IPS4
  • Version
    4.4
  • Language
    English
  • Gender
    Not Telling

Contact Methods

Recent Profile Visitors

6,383 profile views
  1. In this episode, Josepha explores the five groups within the WordPress ecosystem and provides a high-level example of how they interact and support one another. As always, stay tuned for the small list of big things and a contributor highlight. Have a question you’d like answered? You can submit them to [email protected], either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho Production: Chloé Bringmann Song: Fearless First by Kevin MacLeod References Get to know WordPress TeamsFive Steps of Volunteer Engagement Community Highlight WordCamp Centroamérica 2021 Online (Schedule) So you want to make block patterns? Gutenberg Tutorial sign-up Transcript Hello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go! In the first episode of this podcast, I said that there’s a lot that goes into WordPress, that’s really hard to see. One of the hardest things to see about the WordPress project as you get started is the overall structure. There is quite a bit of documentation that can clarify the basics: the names of teams, what they work on, and where, and when they meet. The way that they influence and support each other can really feel like a bit of a mystery. So today, I’m going to break down the WordPress community into five big groups; I want you to keep a couple of things in mind. Firstly, these are high-level and based on my observations. Each of these groups can be further broken down into subgroups. So while you may not feel represented in this exact five, you are included if you were to dig a little bit deeper. The second thing to keep in mind is that the makeup of these groups is pretty fluid. Many community members find themselves in more than one group, but generally not far off. Some group two folks end up in group three, depending on the situation, people in group four can also end up in group five, and so on. As with so many things that I share, I’m not trying to insist that one size fits all. I’m not trying to put the WordPress community into a box. This is just a basic framework to understand how it all fits together. Alright, are you ready? I’m ready. Let’s do it! Okay, I have a broad definition of the community, which I have mentioned before. I believe that the community is anyone who has interacted with WordPress, whether they know it or not. So, I’ll start from way out there and work my way in that first group; we’re going to call our Visitors. Visitors are people who arrive at a WordPress site to gain information or engage in an activity. Sometimes they know it’s a WordPress site, but most of the time, they don’t. The second group are Users, people who use WordPress as their CMS. So, that’s website builders, website designers, small businesses, content creators, and the list goes on and on. The third group I like to refer to is the Extenders. Those are people who extend WordPress through the creation of blocks, themes, plugins, and more. There are also people who teach WordPress to others through WordPress podcasts, and newsletters and tutorials. The fourth group I refer to as our Contributors is the people who contribute to the open source software and the infrastructure supporting it, but not necessarily the same people who contribute directly to their own product. And then there’s group five, Leaders. Those are people who help drive the vision and strategy for WordPress; the most notable member of that group is of course, Matt Mullenweg. And I’m also in that group. Each of these groups directly influenced the groups on either side. For example, a WordPress user is affected by both visitors and extenders. Imagine a content creator who shares their passion for photography through a WordPress site; this photographer may have visitors that need to purchase photos. In response, the user now has a need to make it possible for visitors to purchase photos on a site. So they go to what we consider the extenders, people who have built a plugin that supports that need. And as a result, that user can install that on their site. And they have have satisfied the need of the visitors to their site, the people who now can purchase photos. There are a lot of examples like this in the WordPress project. Every small pattern that you see is mirrored in the larger patterns across our ecosystem. And every large pattern you see in the ecosystem can be seen among our teams. It’s pretty cool to look at really. So, why should this matter to you? From a very practical standpoint, this matters for anyone who’s trying to learn more about contributing to the WordPress project. These five groups mirror very closely the five steps of volunteer engagement that we see across the ecosystem and from a more philosophical standpoint, it’s just kind of nice to know who your neighbors are. Without the influence and support of the groups around us, it can be hard to know whether we’re on the right track or not. So take a look to your left and look to your right, and get to know your partners in this project. That brings us now to our community highlight, the segment where I share a note about contributors who have helped others along the way, or WordPress success story. This week’s highlight is from @CoachBirgit, Birgit Olzem, a longtime contributor and a friend of mine. Her success story goes like this. WordPress has allowed me as a mother of five to leave a toxic marriage for good. Later, the community picked me up when I became seriously ill. So I can say from the bottom of my heart, that working with WordPress has saved my life. And now our small list of big things. I’ve got three things for you this week. I think that they’re all very important. And I hope you check them all out. The first one is a reminder that word camp Central America is coming up on April 15 and 16th. If you have not registered for tickets, you still have time, I will share a link to the registration page and the schedule in the show notes below. The second thing on our small list of big things is that the Gutenberg 10.4 release is coming out later this week on April 14th. It’s an important release because it’s when we take a look at the current iteration of full site editing tools that we have, and decide if it’s ready to get into the WordPress 5.8 release. There’s a post that has a little more information about that which I will share in the show notes below as well. If you haven’t checked out the Gutenberg plugin lately, obviously I think it’s a good idea to do that in general, but definitely a good idea to check it out now. The third thing on our list today is a reminder to check out our most recent block pattern tutorial, I’ll share a link to that in the show notes. It’s this kind of tips and tricks, tutorial, the “show me how to do it,” kind of thing in the style of CSS-Tricks. If you or anyone that you know might be interested in sharing a similar style of tutorial, there’s a link to a form in that show notes as well so that you can share with us your name and the topic that you’re interested in. We’ll take a look and see if it’s something that we definitely need to make sure our users know how to do. So, that my friends is your small list of big things. Thank you for joining in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks! View the full article
  2. These words from Josepha Haden Chomphosy on the How WordPress Improves episode of the WP Briefing Podcast point to the factors that differentiate building software in an open-source environment. Our updates this month are closely tied to the philosophy behind those core principles of open source software. WordPress 5.7 released WordPress version 5.7 “Esperanza,” came out on March 9. The release offers fresher admin colors, several improvements to the block editor, single-click HTTP to HTTPS migration, and a new Robots API. Read more about it in the release post, the field guide, and the talking points post for meetup groups. The Core Team has also started work on WordPress 5.8 pre-planning. Want to contribute to WordPress 5.8? Join the WordPress #core channel in the Make WordPress Slack and follow the Core Team blog. The Core Team hosts weekly chats on Wednesdays at 5 AM and 8 PM UTC. Gutenberg Version 10.1 and 10.2 are out Contributor teams released Gutenberg Version 10.1 on March 3 and Version 10.2 on March 17. Version 10.1 showcases significant improvements to reusable blocks, a clearer image toolbar, and spatial options for the social media block. Version 10.2 offers block pattern options to display contents from the query block and removes writing prompts from empty paragraphs in the editor. It also adds width adjustment for spacer blocks in horizontal parent blocks and the ability to transform media and text blocks into columns. Want to get involved in building Gutenberg? Follow the Core Team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Make WordPress Slack. The “What’s next in Gutenberg” post offers more details on the latest updates. Don’t miss the monthly Gutenberg tutorial on How to make block patterns! Full Site Editing updates March saw a plethora of updates to the Full Site Editing project! @chanthaboune published a Full Site Editing pre-merge overview. She shares the project’s current status, go/no-go dates for core merge, communication plans, and challenges. March saw two calls for testing as part of the Full Site Editing outreach program. The first test of the month — creating a custom 404 page, wrapped up successfully. Participate in the latest testing initiative — build a restaurant-themed website header to help improve the future of WordPress! Deadline: April 8. You can also find high-level feedback on the FSE Program in this March 2021 post. Proposal launched for a WordPress contributor handbook A proposal has been kicked off on building a project-wide WordPress contributor handbook. The handbook will have content around the WordPress project’s underlying philosophies and commitments, along with shared expectations on working together and building products. It will also contain modern open source best practices for WordPress. Further Reading You can now schedule office hours with Matt Mullenweg and Josepha Haden as part of their Q2 Quarterly listening hours initiative. This quarter’s listening session is scheduled for April 7th, 2021, from 22:00–24:00 UTC. Slots are still available — sign up now! The Themes Team is working on automating the theme review process. The team has shared a detailed post on these changes and is requesting feedback. The Core Team has kicked-off plans on dual licensing Gutenberg under GPL and MPL. Version 7.2.1 of BuddyPress (security release) is out! Update all your BuddyPresses! The Docs Team shipped the WordPress documentation style guide as part of its Google Season of Docs 2020 effort. The team has also kicked off work on applying for Google Season of Docs 2021! The Polyglots Team is making significant progress on building their contributor training program. The team is also requesting feedback on building their dashboard. @chanthaboune shared an experiment to coordinate sponsored contributors by adding them to a private Slack channel to offer them better support. The Community Team announced its revamped 2021 Global Sponsorship Program. The team also published a financial update for WP Communities in 2021. The Core Team is moving ahead to drop support for Internet Explorer 11 for upcoming versions of WordPress. The Design Team shared initial designs for the Block pattern directory. The Make WordPress Slack workspace briefly went down on March 30 due to a Slack ToS issue, which was subsequently resolved. More details on this explainer post. Have a story that we should include in the next “Month in WordPress” post? Please submit it using this form. View the full article
  3. If you’ve ever built something for the WordPress block editor — a theme or a plugin — you may have also heard about block patterns. Looking at the patterns that come bundled with WordPress, I thought it would be nice to dedicate to them a short post. They’re pretty nice, useful shortcuts when you know them, but there’s a good chance you may not know what they are or why you might want to use them. What’s a block pattern? Patterns are collections of pre-arranged blocks that can be combined and arranged in many ways making it easier to create beautiful content. They act as a head-start, leaving you to plug and play with your content as you see fit and be as simple as single blocks or as complex as a full-page layout. They live in a tab in the block library. You can click or drag and you’re able to preview them with your site’s styles. Basically, a block pattern is just a bunch of blocks put together in advance: <!-- wp:group --> <div class="wp-block-group"><div class="wp-block-group__inner-container"><!-- wp:separator {"className":"is-style-default"} --> <hr class="wp-block-separator is-style-default"/> <!-- /wp:separator --> <!-- wp:image {"align":"center","id":553,"width":150,"height":150,"sizeSlug":"large","linkDestination":"none","className":"is-style-rounded"} --> <div class="wp-block-image is-style-rounded"><figure class="aligncenter size-large is-resized"><img src="https://blockpatterndesigns.mystagingwebsite.com/wp-content/uploads/2021/02/StockSnap_HQR8BJFZID-1.jpg" alt="" class="wp-image-553" width="150" height="150"/></figure></div> <!-- /wp:image --> <!-- wp:quote {"align":"center","className":"is-style-large"} --> <blockquote class="wp-block-quote has-text-align-center is-style-large"><p>"Contributing makes me feel like I'm being useful to the planet."</p><cite>— Anna Wong, <em>Volunteer</em></cite></blockquote> <!-- /wp:quote --> <!-- wp:separator {"className":"is-style-default"} --> <hr class="wp-block-separator is-style-default"/> <!-- /wp:separator --></div></div> <!-- /wp:group --> That’s also how you create them: just use the block editor to configure a smattering of blocks to your liking, and the hard part’s over. How do I get them in the block library? There’s more documentation in the handbook, but what it boils down to is this: <?php /* Plugin Name: Quote Pattern Example Plugin */ register_block_pattern( 'my-plugin/my-quote-pattern', array( 'title' => __( 'Quote with Avatar', 'my-plugin' ), 'categories' => array( 'text' ), 'description' => _x( 'A big quote with an avatar".', 'Block pattern description', 'my-plugin' ), 'content' => '<!-- wp:group --><div class="wp-block-group"><div class="wp-block-group__inner-container"><!-- wp:separator {"className":"is-style-default"} --><hr class="wp-block-separator is-style-default"/><!-- /wp:separator --><!-- wp:image {"align":"center","id":553,"width":150,"height":150,"sizeSlug":"large","linkDestination":"none","className":"is-style-rounded"} --><div class="wp-block-image is-style-rounded"><figure class="aligncenter size-large is-resized"><img src="https://blockpatterndesigns.mystagingwebsite.com/wp-content/uploads/2021/02/StockSnap_HQR8BJFZID-1.jpg" alt="" class="wp-image-553" width="150" height="150"/></figure></div><!-- /wp:image --><!-- wp:quote {"align":"center","className":"is-style-large"} --><blockquote class="wp-block-quote has-text-align-center is-style-large"><p>"Contributing makes me feel like I\'m being useful to the planet."</p><cite>— Anna Wong, <em>Volunteer</em></cite></blockquote><!-- /wp:quote --><!-- wp:separator {"className":"is-style-default"} --><hr class="wp-block-separator is-style-default"/><!-- /wp:separator --></div></div><!-- /wp:group -->', ) ); ?> That’s a snippet of PHP, which means you can drop it in a WordPress plugin, or perhaps more simply, paste it into the functions.php file from your theme. Done: For patterns that include images, it’s worth thinking about where those are stored. The TT1 Blocks theme (which is a fancy name for “TwentyTwentyOne Blocks”) stores images in the theme library. Now what? The thing about a block pattern is, as soon as you insert it from the block library, it stops being a cohesive unit — now it’s just a smattering of blocks, detached from the pattern you created and meant to be customized to your liking. It’s a shortcut, not a template. That also means you don’t have to worry about switching themes or deactivating pattern plugins: the blocks you already inserted won’t go anywhere. That being said, if you like this one pattern so much you want to use it again and again, with no customization at all, you can make it into a reusable block: Reusable blocks are created, as the name implies, to be reused. The feature is a great way to store small bits of commonly used snippets that you can edit in one place to update in all. “Follow me on Twitter,” “Article series,“ or “Subscribe to my podcast” are great examples of that. What makes a good block pattern? Patterns, as they ship today, are limited by the features available. If the block editor doesn’t allow you to customize letter-spacing, your block pattern can’t either. While the Global Styles project will expand what’s to blocks, in the meantime, we have to work with the available tools. Even then, with the most basic ingredients — color, photography, typography — it is possible to do a lot: Three columns with images and text Media and text with image on the right I designed these patterns to potentially land in WordPress core, which all have a few properties in common: They share a theme. You can think of a pattern as a section of a website: it is meant to be part of a whole, and so it works best when it can exist in the context of other patterns that share the same theme. There are a few sharing a Nature theme in the patterns above, a few sharing an Art theme, and others sharing an Architecture theme. When seen together, it becomes easier to see how you might be able to piece together multiple pages of your site, one page at a time. They share a minimalist color palette. By being parts of a whole, patterns will inevitably land in a context that uses different colors. With a reduced color palette, there’s both a better chance of fitting in and less to customize to make it just right. The best patterns do things you might have not done otherwise. Whether that’s images offset to create a unique silhouette, or just using less visible features (like fixed positioning in the Cover block), it’s a way to surface creativity. Here’s a plugin for you <?php /* Plugin Name: Quote Pattern Example Plugin */ register_block_pattern( 'my-plugin/my-quote-pattern', array( 'title' => __( 'Quote with Avatar', 'my-plugin' ), 'categories' => array( 'text' ), 'description' => _x( 'A big quote with an avatar".', 'Block pattern description', 'my-plugin' ), 'content' => '<!-- wp:group --><div class="wp-block-group"><div class="wp-block-group__inner-container"><!-- wp:separator {"className":"is-style-default"} --><hr class="wp-block-separator is-style-default"/><!-- /wp:separator --><!-- wp:image {"align":"center","id":553,"width":150,"height":150,"sizeSlug":"large","linkDestination":"none","className":"is-style-rounded"} --><div class="wp-block-image is-style-rounded"><figure class="aligncenter size-large is-resized"><img src="https://blockpatterndesigns.mystagingwebsite.com/wp-content/uploads/2021/02/StockSnap_HQR8BJFZID-1.jpg" alt="" class="wp-image-553" width="150" height="150"/></figure></div><!-- /wp:image --><!-- wp:quote {"align":"center","className":"is-style-large"} --><blockquote class="wp-block-quote has-text-align-center is-style-large"><p>"Contributing makes me feel like I\'m being useful to the planet."</p><cite>— Anna Wong, <em>Volunteer</em></cite></blockquote><!-- /wp:quote --><!-- wp:separator {"className":"is-style-default"} --><hr class="wp-block-separator is-style-default"/><!-- /wp:separator --></div></div><!-- /wp:group -->', ) ); ?> In case you want to make patterns, this example plugin features two of the patterns you saw above. Drop it in your plugins folder and they should show up in your block library. Installed pattern under “Text” Category Feel free to tweak it, customize it, and make it yours. It’s GPL, after all! Thank you @joen for the help writing this post. View the full article
  4. In this episode, Josepha is joined by Matías Ventura, also known as “the spark behind the vision of Gutenberg.” Josepha and Matías discuss full site editing and answer your questions, from “is full site editing a standalone plugin?” to “will full site editing break my current site?” Have a question you’d like answered? You can submit them to [email protected], either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho Production: Chloé Bringmann Song: Fearless First by Kevin MacLeod References Twenty Twenty One theme Word Camp Central America 2Q21 Listening Hours with Matt Mullenweg and Josepha Haden Chomphosy Transcript Hello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go! Josepha [0:41]: This month, we have a bonus briefing, so I’ve asked my dear friend and colleague Matías Ventura to join me. Matías was recently called “the spark behind the vision of Gutenberg.” With full site editing coming our way in 202, I asked if he would join me for a quick Q&A. Welcome, Matías. Matías [0:56]: Hello, hello! Thanks for inviting me. It’s a pleasure to be here. Josepha [1:00]: Well, I’m delighted to have you. And I think that we have a lot of excellent questions. All right, so Matías, we actually ended up with questions in about three different groupings. And so I’m going to start with the “what is it about full site editing,” sorts of questions that people had. We’re gonna work our way into “what are we doing with it?” and then “how are we planning on getting this out the door?” Then, a couple of big picture questions that people asked. We’re just gonna leap right in this full site editing part of the Gutenberg plugin, or is it a standalone plugin? Matías [1:39]: Okay, we’ll start with the basics. Full site editing is part of the Gutenberg plugin right now. I think it’s important to mention that full site editing is like an umbrella for several projects that we’re working on. They are all aiming to bring blocks into more parts of your site so that editing becomes easier and more expressive, and so on. So full site editing right now encompasses adding a ton of new blocks. I think we have around 20 new blocks coming in, including navigation query, site, title, logo, etc. There’s also the interface to interact with templates outside of the content; that’s another big part of the full site editing project. We also have a lot of new design tools included, many of these have been released in previous major releases, but they still comprise a strong part of what full site editing is. We also have something called Global Styles, which aims to allow people to configure the visual aspects of blogs across the entire site, not just on any individual blog. And of course, then there’s a whole layer of how we utilize these tools. It can get complex because there are many layers and projects that need to come together. So yeah, all of these are accessible through the Gutenberg plugin right now. Josepha [3:07]: Yeah. So it’s not a standalone plugin. If you wanted to check out full site editing the site editor experience as it is now, you would just have to make sure you had the Gutenberg plugin on your site. Right? Matías: Yes, correct. Josepha: So a couple of the questions related to this are how exactly do I enable it on my site? And what is the easiest and safest way to try this on my site? And I think the answer is, is right in there. It’s in the Gutenberg plugin. And so if you have that plugin, you don’t need the testing plugin or anything else to make that work, right? Matías [3:51]: No, you like, you might need to install a theme like Twenty Twenty One blocks that unlock some of these new interfaces that we just talked about. Like other of these pieces are available for anything. But some of these, like the interface to edit templates, right now only talk with things that know how to express their desire. Josepha [4:14]: And I think we have less than 10 themes right now that do that, but I’ll leave some links to at least 2021 blocks in the show notes. And then, if there are another one or two themes that I can find, I can add those in there as well. So you have to have the Gutenberg plugin; you have to have a theme that works with that site editor kind of experience. And then you’re safe to try everything out. It shows up in your left toolbar just like any other thing, like if you were working with plugins, or if you were adding a post or anything else, right? Matías [4:51]: Yes, correct. And so, some of these details are being worked on right now. Like how and where you access things, and so on. These things are subject to change, but right now, you have this site editor beta in the sidebar when both you have the plugin running and a theme that’s capable. Josepha [5:10]: Yeah. Excellent note. If you are running this on a production website, I would recommend you not do that unless you are very, very good with WordPress. It’s a really safe and easy thing to test and try out. But because it is still in beta, I recommend always putting it on a test site. I have a couple of different test sites that I run on myself. Another question that I had was, “will full site editing slow down my site?” And I think we have some refreshed performance tests coming out about that. And maybe they’ll be out by the time we publish this podcast. Matías [5:49]: Yeah, I mean, like the performance has been one of the major focuses for the whole project. In many cases, it should speed up things because we’re like, I think one of the big pieces that these projects bring into the picture, especially for themes, is that it allows only the necessary assets to be loaded on the front end. For example, if for a given page, there are, I don’t know, 10-15 blocks being used, you would only get the CSS and scrapes and so on related to those blocks. This can cut down on a lot a ton of CSS that themes used to end queue on a side, particularly if you were trying to customize many widgets and so on, like a lot of themes have the full styles or multiple widgets, even third party plugins, and so on. So one of the advantages of having this blog system is that we can know at the time of rendering what blogs are being used and only load those assets. Josepha [6:50]: Excellent. Another big question that we have is, “does full site editing work with the classic editor? And does it work with other builders?” I think that’s a really big answer if you’re going to get super deep into it. But I think that the short answer is yes, it does. Is that fair? Matías [7:08]: Yeah, I don’t think it touches a bit on that full site editing is not like a single thing. There are multiple projects around it. So again, like the template editor that only deals with blogs, it doesn’t have a lot to do with a classic editor. But the classic editor use for both doesn’t change anything at all; like the same way that when the block editor was introduced, it didn’t change how you could still write posts in the classic editor. You will still be able to do that. Josepha [7:41]: And if you are brand new to WordPress person, or, I mean, I guess at this point, you don’t have to be super brand new. If you’re fairly new to WordPress person and have no idea what we’re talking about when we say the classic editor, you don’t really have to worry about it either. You don’t have to go and find out what that is; the block editor that you have right now works perfectly for what you’re trying to do. So if you don’t know what I mean when I say classic editor, don’t worry about chasing it down either. I think that this last question we accidentally answered earlier, but I’m going to go ahead and ask it anyway since I received it. “I keep hearing that you can use the site editor with the 2021 theme. But I don’t seem to be able to. What am I missing?” I think the answer is that there’s the Twenty Twenty One theme shipped with the WordPress release 5.6. And then there is the Twenty Twenty One blocks theme; those are two different themes. The link to the Twenty Twenty One block theme is going to be in our show notes this time around. And so, if you have been trying to use the full site editor with Twenty Twenty One and not succeeding, try the link to the one below. And I bet that that will work for you. Matías [8:50]: Yes, that’s correct. Josepha [8:51]: All right, excellent. Well, that brings us kind of into our second set of questions, which is about how we are doing it. The first one that folks have is “will full site editing be on by default in the next release. In this context, the next release is WordPress 5.8. But I think it’s a safe question to ask if full site editing will be on by default in the release that it’s planned for. Matías [9:15]: Yeah, and for this, I need to go back to the same principle of many projects because there are many pieces of full site editing, and we have been merging them in major releases, particularly like the blocks and the design tools. There are more coming in that we want to make accessible as soon as possible. The full experience that requires a theme to opt-in to templates using blogs won’t be by default; it requires a specific theme running. A lot of these details we’re still like determining exactly what projects are ready to be merged and so on. But yeah, if you have a theme right now that works the way you want, it doesn’t change anything there. If anything, it adds some more capabilities and more customization tools, and so on. And the theme can also regulate how much they want to incorporate. Josepha [10:13]: Matías, you’ve mentioned a couple of times in this podcast so far like this is a really complex and really complicated part of this work. And just for anyone out there who’s either encountering Gutenberg or full site editing or this podcast for the first time, I think a tiny bit of context that’s worth having here is that Matías and I have been working on this together in various capacities for like, five years. And Matías has probably been working on this for practically a decade. So, when we say that this is a really complicated problem, and when we say that this is a complex set of issues that we’re working with like, it is all that we have been thinking about for I want to say at least the last three or four years, but certainly it’s all that we have been trying to untangle for quite a bit of time before that as well. So we don’t take it lightly when we’re like, “this is complicated;” we mean it. It’s really complicated. And we’re trying our hardest over here as WordPress. The next big question, since we’re all stuck in the “it’s very complicated,” part of things is the question, “will this update break my current site?” Like, if I have a site that is updated and ready, and it’s exactly as I wanted it to be, and it took me two years to get there will full site editing, whichever release it’s in. Currently, 5.8 is what we’re planning for. Will that break anything on my site as I know it right now? Matías [11:44]: No, not at all. One of the major things that the WordPress team, the WordPress community, always cares so much about, never to break things. Many of these things are stepping stones that you can adopt, as we’ve talked about full site editing. But for example, we also have a few concurrent projects around the widget screen and the navigation screen that are meant to bring blocks into existing interfaces. So again, the theme doesn’t need to change, and a lot of care is being put into making this more like you’re unlocking new features, and nothing really breaks or falls apart. Josepha [12:23]: This update, like all the other updates, should have minimal, minimal impact on what you have to actively fix on your site. Every once in a while, a bug is gonna get by. We can’t say that we’re 100% perfect with not breaking things. But also, we always and I and I know that we’re planning on this for our remaining releases for the rest of the year. At the very least, I can’t imagine we’d ever change it. But after every major release, we always make a plan to have a minor release within the next one or two weeks. Because we know that a broken thing on a site is really incredibly impactful, even if you’re only 1% of the sites that had that happen to it. And so I think that’s true in this case, too. And getting that feedback back from all of the people who are actually using WordPress is the thing that makes us be able to kind of move quickly when we do see those problems. One of the questions that we have been getting is, “can I see a live preview without saving the changes that I made?” When I got this question, I didn’t actually understand it. And so I went and looked at a site without the Gutenberg plugin on it, and then a site with the Gutenberg plugin on it. And of course, on sites without Gutenberg, without the block editor, without full site editing, when you are looking to preview, you have the option to open up your preview in a new window. And you don’t have that with Gutenberg because it’s supposed to be a true WYSIWYG editor. A true what you see is what you get, editor. I think that the answer to this is, yes, you can see a live preview without actually saving the changes on the front end of your site. But you don’t actually have to reload anything. You don’t have to open it up in a new window. You don’t have to, like, actively click “please show me a preview” because what you see in your editing screen should be what you see at the end of your app as an end-user. Matías [14:28]: Yeah, that’s the sort of the main gist to it. Yes, the site editor is built so that it always reflects the front end as truly as possible, so that’s one layer. Also, the preview tools should allow you to see in different devices like mobile breakpoints, and I don’t know if they will have breakpoints and stuff like that. There are a lot of things in the current interface that is just not enabled. There are some challenges in the sidebar. Because the site editor is not just focused on a single post, it’s focused on the entire site. So, there can be many, many changes that need to be shadowed for the site. If you’re changing the site title, some of the global styles, aspects, and so on need to be orchestrated. So, to see in the previewing new window, there are some challenges there to integrate. Again, the interface is not final yet; a lot of these things are still being tweaked and improved. There are many things from the regular post editor that are not enabled yet. But they will be enabled. So yeah, it’s a, I guess, it’s not a simple thing to answer. Because, again, the idea of previewing the site that’s core to the whole project is that you’re always interacting in the same way that when you’re in the customizer, you’re seeing the preview all the time. That’s the main scope of this project, Josepha [15:54]: Excellent. Changes like that changes to your workflow can be really hard to get your mind around, especially if part of that existing workflow was there to create some confidence in what you’re seeing with your users. And so I understand. Now that I’ve researched that question a bit, I see where that’s coming from. Based on existing workflows and existing patterns that we have for ourselves in WordPress, will we need to have a theme to use the full site editor? Matías [16:33]: I think we’ve already covered some of these. And again, they are tools that can work on any existing theme. There is other stuff that needs space-specific themes to opt-in into these tools, like blog templates and so on. Josepha [16:50]: Yes, I think the question that we have next, because I see that the literal next question I have is actually something we have covered; just because we’re being pretty conversational about it, not because anyone already asked the question. So I’m actually going to skip to the last question of this section that I received. I got this next one via Twitter. The question is, “how do you view the role of themes once full site editing is fully rolled out and all the page elements (content, headers, widgets, footers, etc.) and all the views are managed via blocks and block patterns? Will things become typographic and block styles?” Matías [17:28]: I think this is a great question because it goes to the heart of, why are we doing all this. One of the main reasons is to empower users more. WordPress has been democratizing publishing for a while; this is another step into allowing themes to get more customization tools and more control over their site if they want to. I think the recent call for testing has focused on the 404 page, for example. That’s something that forever has been locked away from users. And it’s also something that, as a theme developer, and I used to develop themes a long time ago, that was one of the things where you decide what sort of approach you take for the 404 page. Maybe sometimes you want to have something more whimsical. Sometimes you need something more serious. And committing to one when you can have such a diverse and broad user base can be challenging. With these, it becomes as easy as offering a few different patterns for that template. Then the user will always be able to change the copy and modify something. So again, it opens up a lot of these things that used to be locked down. However, from a theme perspective, I think this doesn’t reduce the theme at all. If anything, it allows the theme to focus less on coding and functions and more on design expression and aesthetics. I don’t think that would ever be exhausted. That will always remain as diverse as humans are interacting with WordPress. And so it’s not that I don’t see it’s just as like, typographic and block styles. How do you express a template, how do you express the structure, what choices you quote, what choices you make as a theme builder? And of course, there are many degrees of control there. Because a site maintainer may not want the 404 template to be editable, that sort of control will always be present. Josepha [19:38]: Yeah. And really fast. I have to add a caveat to a thing that you said in there. For anyone who’s listening keenly, you may have heard Matías say that the users can update any of the content there – any of the copy. In this context, we’re talking about users as in the people who are maintaining the site, not people who are visiting your site. Visitors to your site will not be able to change any copy on your page unless you’ve done something very interesting with your WordPress site, which is also fine if that’s what you prefer to do. By default, your visitors can’t change everything on your website, which is good news, frankly. So I’ve got one logistics question, which I’m happy to take. And then one is kind of a big picture question that I also got from Twitter. “What about the classic editor block; what is going to happen to that? And when will we know?” So ages and ages ago, before COVID? I think so. Probably maybe a couple of years ago, Matt said that the classic editor plugin would be supported through the end of 2021. And that is still the case; there will be active support on that through the end of 2021. After that, it will not be actively supported anymore. It won’t be removed from any place that you can get access to right now. In a “this is the end of its lifecycle” sort of way, we just won’t have anyone who is currently committed to maintaining that plugin anymore. So that’s what’s happening at the end of the year. And yeah, at the end of 2021. The big question that we have is, “why is full site editing being so rushed?” I think this is a bit of a loaded question. Matías [21:32]: Yeah, I think I think it’s still a fair question, though. I think we’re dealing with two things here. And one is ensuring that we release things in the best state possible. And also, some of the urgency is to offer tools that we know that people lack right now and that could really benefit from. Making that determination is very tricky. The full site editing project has been in the works for the last couple of years. If we count the initial phase of Gutenberg, that’s four to five years. We’ve been doing many calls for testing, which I think have been super useful to catch issues and reflect as a community on where things are going; how do we integrate with these? How do we use it? What are the shortcomings? What do we need to do? Based on all of these, we’ll continue to make decisions on when things become ready. We’re not committed to releasing something that’s not in a good state. And I think we will always be very careful about that. There are these two competing senses of the urgency – of getting some of these tools out, and because it also benefits from the feedback loops. I always say that, in many ways, the initial phase of Gutenberg, to me, is not finished. We took the initial two years to do the 5.0 release, the initial block editor, and so on. But, it’s still being improved at a very fast pace, among all the recent major releases improvements to the editor were included; that will continue to be the case. In many ways, phase one is not finished. And the moment we choose to release some of these tools or editing tools, it won’t be finished either. They will need to continue to grow, mature, and incorporate a lot of the feedback. Even the things that the ecosystem is building around. I’ve seen a few themes already that are incorporating a blank canvas template so that you can use them in some pages and take over and do everything with blocks. So even the community and ecosystem as a whole is also sort of paving the way for what needs to come. Josepha [24:06]: I think from my perspective, and of course, I’m on the people side of things, the communication side of things, the logistics side of things; I have a frequently a very different view from what a lot of other folks are seeing. And so from my side of things, I have to say, I’m communicating about this change in a really broad way, which has not been happening since 2019 when we started the work. We’ve been communicating broadly with the WordPress community, but not with everybody who uses WordPress. So, I think that for a lot of people, this looks like a project that we started really actively working on in the last six months or so. And now we’re just racing toward a finish line. I think that there’s, there’s not been a lot of awareness of everything that’s gone into it. And so, on the one hand, it feels a little less rushed to me knowing the full length of the history on this. But also, as you said, I really think that this gets a bunch of tools to people who otherwise have not been able to accomplish these things in WordPress or otherwise. I am so anxious to get something to people who really can benefit from this change the most. And it’s the nature of the open source, right that like, one, as long as you have users, you’re going to have stuff you have to fix in your software. So we’re never really, really going to be done with this; there’s not going to be like a done point of WordPress. And the second thing is, I think it’s generally true that you don’t really start getting full user feedback until after you have launched your major release. I think that we see that a lot in open source software; you can bring in as many people as you think you can in your user tests heading up to it. And in your accessibility tests. And, in general, quality assurance tests. You can bring in a lot of people and still not have gotten the full understanding of the various niche use cases that your users will bring to you. Because at this point, we’re like 40% of the web. And that means that we’re serving this majority collection of increasingly minority voices and niche voices in the space. And so, a little bit I feel a sense of urgency; I feel a bit of anxiousness about trying to get this out there for one, to get the tools in the hands of the people who can benefit the most from them, but also so that we can start really getting the full stress test of this software out and get that feedback in so that we can really build something responsive to what our users need our long tail, “anyone who ever uses WordPress ever,” definition of users. And so, that’s why I feel a sense of urgency around it. Even though you know, as I said, you and I have been working on this for like five years, and you’ve been working on it for a decade or something. I actually don’t know how long it’s been worked on. Matías [27:35]: Now that makes me feel a bit old. Josepha [27:40]: Nobody makes Matías feel old. He is a lovely, wonderful colleague. Sorry, Matías, If I made you feel old. Matías [27:46]: No, that’s totally fine. I also want to add that full site editing is not like a single toggle that’s going to drop into a major release. So I think that’s important to consider, I think this entire year is going to see a lot of these tools being, and sometimes the sort of the end-user is not the, again, the site maintainer. Still, you can also be the theme developer; I think there are many tools that would be empowering for theme developers to use. Again, we mentioned there are like five to ten themes, block themes right now. That needs to grow a lot, and that only grows through these sorts of feedback loops. And the theme community pushing things forward and seeing where things can lead to. I’m very excited about the pattern directory integration because I think that can also combine with blog themes in very powerful ways. Imagine if, I don’t know many of these patterns that are very common on the web and very needed, that if we can refine them together with a second community and make them available across themes, you can combine a header from one theme with a content of another; all these sorts of mixtures could happen. All of this needs exploration, the creativity of the entire community, and so on. In that sense, getting all these tools, even if it doesn’t immediately change anything for like the site itself, starts to unlock a lot of things. Josepha [29:27]: I’m going to take a bit of your answer from there and tie it all the way back to your first answer that we had when you joined me today. And say, I think you’re absolutely right. We have a set of users in our theme authors and our plugin developers as well that we desperately need to get looking at this set of tools. I hope that what we are shipping in the first iteration of this serves as an opportunity for all of those theme authors and agency owners, plugin authors, WordPress site configurers freelancers. Like, I really hope that this puts it into a really accessible, easy-to-access space for them so that they can do those experiments based on what they know their users need the most. They are the group that has the closest access to site maintainers. And what they need compared to, for instance, me or a potential you like we have a lot of information, you and I, we do a lot of tests, we have a strong sense of what is needed at the moment, but we don’t have as a close connection that our theme and agency and plugin folks all have. And so that’s another part of why I’m so excited to get this out in the current iteration of it. Josepha [31:04]: That was a lot of questions in a little bit of time. This is going to be officially my longest WordPress briefing. Matías, I am so glad that you were able to join me today. And I think that everyone’s going to be really, really excited to hear your answers to these questions. Matías [31:23]: Thank you for having me. Josepha [31:25]: All right, my friends. That brings us into our small list of big things. I’m going to skip our community highlight today just because we had a slightly longer word press briefing in our bonus iteration today. But the small list of big things. The first thing is WordCamp Central America is coming up on April 15; there is a registration link in the show notes that you can access your tickets with. I recommend that you go; we’ve got a lot of excellent speakers coming up there and a lot of good content and good training and learning for y’all. The second thing is that Matt Mullenweg and I have listening hours coming up with the community in the first week of April. I’ll add the link to register for those in the show notes as well; it’s just a few minutes for you all to stop by, check-in, see what’s going on, and share some celebrations or concerns with us. And I hope that I see you there. So that my friends is your small list of big things. Thank you for joining in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks! View the full article
  5. Community sharing is community caring. Take it from me: prominently curating your members’ content will profoundly accelerate growth. It’s also pretty darn fun. I’ve run my company, BreatheHeavy, since 2004. While many online businesses shuttered because of social media’s looming presence, mine thrived because of the community. Full disclosure? I had no idea creating a community back in 2004 would become the not-so-secret ingredient to staying alive. Ahh, if only I knew then what I know now. Hindsight is 2020 (that number gives me anxiety, am I right?), but I never fully understood or appreciated how immensely game-changing community building is. Related: The Importance of Moderation, err... Community Guidance (New Video!) In the past, I focused my efforts on writing news articles (in Wordpress) while my Invision Community community ran rampant. I felt my presence needed to take center stage. That cast a shadow on my community and thus my members. I unintentionally muted their voices by exclusively promoting mine. That was a colossal mistake, but the greatest learning lesson. One year ago, I decided to pivot and shift all my energy towards fostering my community; the results were astounding! I saw more than a 100% increase in unique visits compared to the previous year. The most powerful change I made was shining a light on the content my members created. My website went from being a news site to a community. I constructed a new homepage that featured topics created by myself AND my members. This not only manifested a dynamic, constantly varied homepage, but also incentivized members to post thought-provoking and engaging topics in the hopes their content gets featured. In my community, topics that are featured on the homepage are considerably more viewed and commented on than topics that aren’t. I suspect you’d find similar results. Here’s how I set up my new homepage: I utilized Invision Community’s custom blocks feature. It’s available with the Pages application. I created a new block plugin, selected “topic feed” from the list, then set the permissions in the Feed Configuration tab to only show “featured” topics from members. I also used @opentype's SuperTopics plugin to give a more-polished look. Might sound a bit complex, but it’s rather intuitive. Community leaders can “feature” members’ content by selecting their topic and in the moderation panel, tap “Feature.” Our Picks “Featuring” content isn’t the only powerful tool Invision Community has baked into its software to highlight your members’ content. We’ve also carefully crafted a promotion option to manually select content that’s included on the “Our Picks” page and corresponding block. This is another powerful method to curate community content. We created a guide on how to set up promotion/our picks. With great power comes great responsibility The ability to “feature” content is a privilege only moderators in your community should have access to – at least in the beginning. Avoid giving any member the ability to freely feature their own content onto the homepage - instead, focus on manually curating the content. Be selective and choose what topics you want to represent your community. By creating a standard, your homepage won’t feature any and all content. Instead, it’ll display items you believe will pack the greatest punch. Featuring your members' content visibly shows your desire to embrace your community. It’s one thing to comment on members’ topics, it’s another to feature and promote them for all to see. That’s the secret sauce of curation. Do you agree? Disagree? Have any suggestions? Curate content in your own community? How many questions can I ask in a row? Drop us a line in the comments below! View the full article
  6. Community sharing is community caring. Take it from me: prominently curating your members’ content will profoundly accelerate growth. It’s also pretty darn fun. I’ve run my company, BreatheHeavy, since 2004. While many online businesses shuttered because of social media’s looming presence, mine thrived because of the community. Full disclosure? I had no idea creating a community back in 2004 would become the not-so-secret ingredient to staying alive. Ahh, if only I knew then what I know now. Hindsight is 20/20 (that number gives me anxiety, am I right?), but I never fully understood or appreciated how immensely game-changing community building is. Related: The Importance of Moderation, err... Community Guidance (New Video!) In the past, I focused my efforts on writing news articles (in Wordpress) while my Invision Community community ran rampant. I felt my presence needed to take center stage. That cast a shadow on my community and thus my members. I unintentionally muted their voices by exclusively promoting mine. That was a colossal mistake, but the greatest learning lesson. One year ago, I decided to pivot and shift all my energy towards fostering my community; the results were astounding! I saw more than a 100% increase in unique visits compared to the previous year. The most powerful change I made was shining a light on the content my members created. My website went from being a news site to a community. I constructed a new homepage that featured topics created by myself AND my members. This not only manifested a dynamic, constantly varied homepage, but also incentivized members to post thought-provoking and engaging topics in the hopes their content gets featured. In my community, topics that are featured on the homepage are considerably more viewed and commented on than topics that aren’t. I suspect you’d find similar results. Here’s how I set up my new homepage: I utilized Invision Community’s custom blocks feature. It’s available with the Pages application. I created a new block plugin, selected “topic feed” from the list, then set the permissions in the Feed Configuration tab to only show “featured” topics from members. I also used @opentype's SuperTopics plugin to give a more-polished look. Might sound a bit complex, but it’s rather intuitive. Community leaders can “feature” members’ content by selecting their topic and in the moderation panel, tap “Feature.” Our Picks “Featuring” content isn’t the only powerful tool Invision Community has baked into its software to highlight your members’ content. We’ve also carefully crafted a promotion option to manually select content that’s included on the “Our Picks” page and corresponding block. This is another powerful method to curate community content. We created a guide on how to set up promotion/our picks. With great power comes great responsibility The ability to “feature” content is a privilege only moderators in your community should have access to – at least in the beginning. Avoid giving any member the ability to freely feature their own content onto the homepage - instead, focus on manually curating the content. Be selective and choose what topics you want to represent your community. By creating a standard, your homepage won’t feature any and all content. Instead, it’ll display items you believe will pack the greatest punch. Featuring your members' content visibly shows your desire to embrace your community. It’s one thing to comment on members’ topics, it’s another to feature and promote them for all to see. That’s the secret sauce of curation. Do you agree? Disagree? Have any suggestions? Curate content in your own community? How many questions can I ask in a row? Drop us a line in the comments below! View the full article
  7. The next XenForo Insights episode, continuing the topic of community management, will be at 9am Central / 3pm UK time on Friday, April 2nd 2021 via Zoom. Please do come and join us live on Friday 2nd if you... Read more View the full article
  8. The next XenForo Insights episode, continuing the topic of community management, will be at 9am CST / 3pm GMT on Friday, March 19th 2021 via Zoom. Please do come and join us live on Friday if you can, but if you can't... Read more View the full article
  9. In this episode, Josepha Haden Chomphosy explores the WordPress release process. Tune in and learn the phases of a release and catch this week’s small list of big things. Have a question you’d like answered? You can submit them to [email protected], either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho Production: Chloé Bringmann Song: Fearless First by Kevin MacLeod References WordPress 5.7 “Esperanza” Esperanza Spalding Gutenberg Tutorial: Reusable Blocks make.wordpres.org/test GitHub repository Transcript Hello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go! All right, so last week, we wrapped up and shipped the WordPress 5.7 release. The release team this time around was smaller than we’ve had in the last couple of years. By the numbers, it looks really good: 66 enhancements or feature requests went in, 127 bugs were fixed, and seven versions of a Gutenberg plugin were merged and backported. If you use WordPress, you are probably aware that we have new releases throughout the year, but you probably don’t know much about the release process. There’s not really a reason to know unless you’re actively contributing to a release. For those interested in knowing more about how we improve WordPress, this week’s exploration is for you. We’re gonna take a look at what goes into WordPress releases and just kind of zoom our way in from the highest level. At the highest level, there are three major WordPress releases a year, plus the minor releases, plus Gutenberg releases. So if you’re following current WordPress work and future WordPress work, that’s going to get you to probably around 30 releases a year. If we zoom in one level to the release itself, a single release of WordPress takes four to five months from start to the day that we ship, and an additional four to six weeks on support and translations, and minor releases after that. If you’re looking from my vantage point, you’ll see that WordPress releases have essentially five parts, some of which happen kind of simultaneously. The first part is planning and includes the project lead, lead developers, design; groups like that. The second phase is the creation phase when we’re actually building the things that have to go into the CMS that involves the design, core, editor, mobile, and other teams. Then there’s this phase that I like to refer to as the distribution phase. This is mostly done by the teams that make sure that WordPress is widely distributable; the polyglots team work on translations, accessibility does some work, docs make sure that everything is documented, and training, of course, gets things ready for when we have to be able to tell people how to use the release. Then there is the fourth phase; I really don’t think they go sequentially or in a waterfall format. The fourth-ish phase that I include, and that I tend to see, is this extending and iteration phase. It’s the phase where we see our theme authors and our plugin authors, folks who are doing support, show up and help us to make sure that WordPress is available not only widely but broadly to ensure that their audiences as theme authors and plugin authors are covered in the features that they need based on what they are using WordPress for. The fifth phase is the part of our communication that involves the community team, especially marketing, WordPressTV, and learn.wordpress.org. Basically, anyone who’s showing up to make sure that we all share what happened in the release, the features that are coming, and how that affects the users is involved in that particular phase. So five big phases of what happens over those four to five months, and then for the month or month and a half afterward. If we zoom in a bit more on the creation phase, each release has people who lead the work and coordinate contributor efforts during the course of the release. For any given release, hundreds of people contribute and receive credit for moving the WordPress project forward. Okay, hold on a second. Let’s pump the brakes and zoom in a bit on that. Hundreds of people work on every major release for a project that powers over 40% of the web that feels like a small number. But for the people who process the contributions in preparation for release, it’s actually pretty substantial. For every release, there is a small team of leaders who asked the hard questions. Is this a usable feature? Does this make WordPress better overall? And, of course, is this ready to ship? Some of those leaders, a smaller subset of even the leaders that we have already, are committers who actually prep and merge patches to the CMS; they don’t do all the work to create a design or write all the code. This tiny group of people processes hundreds and hundreds of bug fixes, improvements, and enhancements that have been submitted over the course of months and sometimes years. As a side note, that whole process is a little smaller, a little faster in the Gutenberg featured plugin, but the basic parts are still there. Alright, so we’ve zoomed from the big picture way into some of the finer details, and it really looks like any other project cycle. So now, I’m going to layer in the filter of open source to that process. There are a couple of things that make building software in an open source environment so different. The first is that the code is readily available. If you have a basic understanding of the languages, you can see the code, learn from it, and make suggestions about improving it. Second, you consider the user a co-developer in the process, which means that as long as people use your product, they will have opinions on what you shipped. This way of iterating improves WordPress and ties back to one of my favorite open source principles. The idea that with many eyes, all bugs are shallow. To me, that means that with enough people looking at a problem, someone is bound to be able to see the solution. This brings us to our community highlight, the segment where I share a note about contributors who have helped others along the way or a WordPress success story. This week’s highlight is from Nok in our Bangkok community. When asked to help her find her way into the WordPress community, she said, “@shinichiN who started the WordPress community in Bangkok and encouraged me to contribute, and also @mayukojpn has introduced me to the WP community team to join as a deputy. “ Thank you for sharing those two inspiring people with us. And if you, listener, have any stories that you would like to share of your own WordPress success or people that you have been so grateful to help you find your way in the project, you can feel free to email those to me at [email protected] That brings us to our final segment of the WP Briefing, the small list of big things. I only have three things to share with you this week. The first one is that about a week ago, we had our first release of 2021. It was the WordPress 5.7 release, titled Esperanza. If you have not yet seen it, go ahead and update your website or check with your host and make sure that they have updated you if you’re on a managed host. And then take a listen to the artists that it’s named after. The second thing that I want you to keep an eye out for is wordpress.org/news. We are starting a new series of content that gets at the heart of some of Gutenberg’s basic parts; there’s a lot of change coming up in the next few releases of WordPress. And the most important thing to me is that you understand what we’re trying to change and where those changes are primarily taking place. There will be a couple of tutorials that go up there over the course of the of the next few weeks. The third item on the small list of big things is to remind you of our call for testing. As I mentioned earlier in the podcast, the users of any open source software are the code developers; the software built is supposed to make your life and work easier. When you test things and find interactions that can use a little bit of refinement or features that are not working exactly as expected, it’s incredibly helpful for us to have that information to always make sure that we’re solving problems instead of accidentally creating them. If you want to participate in the Current call for testing, you can head over to make.wordpress.org/test. Or, if you’ve been doing your own testing, you can also submit any bugs you have found in the GitHub repo, which I will share in the show notes below. So that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks! View the full article
  10. WordPress 5.7 “Esperanza” Bringing you fresh colors in the admin, simpler interactions in the editor, and controls right where you need them, WordPress 5.7 lets you focus on the content you create. Meet “Esperanza”, the first WordPress release of 2021. “Esperanza” is named in honor of Esperanza Spalding, a modern musical prodigy. Her path as a musician is varied and inspiring—learn more about her and give her music a listen! With this new version, WordPress brings you fresh colors. The editor helps you work in a few places you couldn’t before without getting into code or hiring a pro. The controls you use most are right where you need them. Layout changes that should be simple, are even simpler to make. Now the new editor is easier to use Font-size adjustment in more places: now, font-size controls are right where you need them in the List and Code blocks. No more trekking to another screen to make that single change! Reusable blocks: several enhancements make reusable blocks more stable and easier to use. And now they save automatically with the post when you click the Update button. Inserter drag-and-drop: drag blocks and block patterns from the inserter right into your post. You can do more without writing custom code Full-height alignment: have you ever wanted to make a block, like the Cover block, fill the whole window? Now you can. Buttons block: now you can choose a vertical or a horizontal layout. And you can set the width of a button to a preset percentage. Social Icons block: now you can change the size of the icons. A simpler default color palette This new streamlined color palette collapses all the colors that used to be in the WordPress source code down to seven core colors and a range of 56 shades that meet the WCAG 2.0 AA recommended contrast ratio against white or black. Find the new palette in the default WordPress Dashboard color scheme, and use it when you’re building themes, plugins, or any other components. For all the details, check out the Color Palette dev note. From HTTP to HTTPS in a single click Starting now, switching a site from HTTP to HTTPS is a one-click move. WordPress will automatically update database URLs when you make the switch. No more hunting and guessing! New Robots API The new Robots API lets you include the filter directives in the robots meta tag, and the API includes the max-image-preview: large directive by default. That means search engines can show bigger image previews, which can boost your traffic (unless the site is marked not-public). Lazy-load your iFrames Now it’s simple to let iframes lazy-load. By default, WordPress will add a loading="lazy" attribute to iframe tags when both width and height are specified. Ongoing cleanup after update to jQuery 3.5.1 For years jQuery helped make things move on the screen in ways the basic tools couldn’t—but that keeps changing, and so does jQuery. In 5.7, jQuery gets more focused and less intrusive, with fewer messages in the console. Check the Field Guide for more! Check out the latest version of the WordPress Field Guide. It highlights developer notes for each change you may want to be aware of. WordPress 5.7 Field Guide. The Squad The WordPress 5.7 release comes to you from a small and experienced release squad: Release Lead: Matt Mullenweg (@matt) Triage Lead: Tonya Mork (@hellofromtonya) Release Coordinator: Ebonie Butler (@metalandcoffee) Core Tech Lead: Sergey Biryukov (@sergeybiryukov) Editor Tech Lead: Robert Anderson (@noisysocks) Design Lead: Tim Hengeveld (@hedgefield) Accessibility Lead: Sarah Ricker (@sarahricker) Documentation Lead: Jb Audras (@audrasjb) Test Lead: Monika Rao (@monikarao) This release is the reflection of the hard work of 481 generous volunteer contributors. Collaboration occurred on nearly 250 tickets on Trac and over 950 pull requests on GitHub. 7studio, aaribaud, Aaron Brazell, Aaron D. Campbell, Aaron Jorbin, aaronrobertshaw, abagtcs, acerempel, activecoder, ad7six, Adam Bosco, Adam Silverstein, adamboro, Addison Stavlo, Ahmad Awais, Ahmed Saeed, Albert Juhé Lluveras, albertomake, Alex Lende, Alex Woollam, alex27, Alexander Lueken, alexstine, allancole, Allen Snook, almendron, Amanda Riu, ambienthack, Amol Vhankalas, Andrea Fercia, Andrei Draganescu, Andrew Duthie, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrew Serong, André Maneiro, Andy Fragen, Andy Peatling, Ankit Panchal, Anne McCarthy, Anthony Burchell, Anton Lukin, Anton Timmermans, Anyssa Ferreira, archon810, Ari Stathopoulos, Arslan Ahmed, Artur Piszek, Aurélien Denis, Ayesh Karunaratne, bartosz777, basscan, bduclos, becdetat, Bego Mario Garde, Ben Dwyer, Bernhard Reiter, Bernhard Reiter, bhanusinghkre, Birgir Erlendsson (birgire), Birgit Pauli-Haack, bobbingwide, bonniebeeman, Boone Gorges, Boy Witthaya, Brandon Kraft, Brent Swisher, brijeshb42, burnuser, Caleb Burks, Cameron Voell, Carike, carloscastilloadhoc, carlosgprim, Carolina Nymark, celendesign, Cenay Nailor, ceyhun0, chexwarrior, Chip Snyder, Chloé Bringmann, Chouby, Chris Van Patten, Christian Sabo, Christina Workman, Christopher Finke, clayray, Clayton Collie, Code Amp, Collins Agbonghama, Copons, Corey, cristinasoponar, Damian Nowak, Dan Farrow, Daniel Richards, Daniele Scasciafratte, Danny van Kooten, Daria, Darren Ethier (nerrad), Dave Whitley, David Anderson, David Baumwald, David Calhoun, David Herrera, David Page, david.binda, dbtedg, dd32, Debabrata Karfa, dekervit, Denis Yanchevskiy, denishua, Diane Co, Dilip Bheda, Dominik Schilling, donmhico, dratwas, Drew Jaynes, Dávid Szabó, e_baker, Ebonie Butler, Edi Amin, Ella van Durpe, Ella van Durpe, Elliott Richmond, Enej Bajgorić, Enrico Carraro, epicfaace, epiqueras, Eric Andrew Lewis, Eric Binnion, Eric Mann, Erik Betshammar, Erin 'Folletto' Casali, Estela Rueda, etoledom, eventualo, Fabian Kägy, Felipe Elia, Felix Arntz, Florian TIAR, Florian Ziegler, floriswt, Francesca Marano, Frank Klein, fullofcaffeine, Gan Eng Chin, Garrett Hyder, Gary Pendergast, GeekPress, geekzebre, Geoff Guillain, George Stephanis, geriux, gKibria, glendaviesnz, gmariani405, Gord, greatsaltlake, Greg Ziółkowski, grzim, gumacahin, gunnard, Gustavo Bordoni, Hans-Christiaan Braun, Hardeep Asrani, Hareesh, hauvong, Haz, Helen Hou-Sandi, helmutwalker, Hemant Tejwani, Herre Groen, hirasso, hmabpera, Howdy_McGee, hsingyuc7, Ian Dunn, ianmjones, ibiza69, Igor Radovanov, ingereck, iprg, Ipstenu (Mika Epstein), Isabel Brison, Ismail El Korchi, iviweb, J.D. Grimes, jadeddragoon, Jake Spurlock, jakeparis, jakub.tyrcha, James Golovich, James Huff, James Koster, James Nylen, James Rosado, Jan Thiel, Jason Adams, Jason LeMahieu (MadtownLems), Jason Ryan, Jayman Pandya, Jean-Baptiste Audras, Jeff Chandler, Jeff Farthing, Jeff Paul, Jennifer M. Dodd, Jenny Dupuy, Jeremy Felt, Jeremy Yip, Jeroen Rotty, Jessica Duarte, Jessica Lyschik, joanrho, Joe Dolson, Joe McGill, joelclimbsthings, Joen Asmussen, Johannes Kinast, John Blackbourn, John James Jacoby, John Watkins, Jon Surrell, Jonathan Champ, Jonathan Desrosiers, Jonathan Stegall, Jonny Harris, Jono Alderson, Joost de Valk, jordesign, Jorge Costa, José Miguel, Jose Luis, Joseph Karr O'Connor, Josepha Haden, joshuatf, JoshuaWold, JOTAKI, Taisuke, Joy, JS Morisset, jsnajdr, Juliette Reinders Folmer, Julio Potier, Justin Ahinon, Justin Sainton, Justin Sternberg, kafleg, Kai Hao, Kailey (trepmal), Kalpesh Akabari, kara.mcnair, Karolina Vyskocilova, Kelly Choyce-Dwan, Kerry Liu, kimdcottrell, Kiril Zhelyazkov, Kirsty Burgoine, Kite, Kjell Reigstad, Knut Sparhell, Konrad Chmielewski, Konstantin Obenland, Konstantinos Xenos, Kurt Payne, Kyle B. Johnson, Lara Schenck, laurelfulford, Laxman Prajapati, leogermani, Levdbas, Lihä, litemotiv, lovor, lucasbustamante, Luigi Cavalieri, Lukas Pawlik, Luke Carbis, Luke Cavanagh, Luke Walczak, magnuswebdesign, Mahafuz, Mahdi Akrami, malinajirka, mallorydxw, mallorydxw-old, Manzoor Wani, Manzur Ahammed, marcelo2605, Marcio Zebedeu, Marcus, Marcus Kazmierczak, Marie Comet, Marijn Koopman, Marin Atanasov, Marius Jensen, Mark D Wolinski, Mark Howells-Mead, Mark Robson, Mark Uraine, Marko Andrijasevic, Markus, Mary Baum, Mathieu Berard Smartfire, Mathieu Viet, Matias Ventura, Matt Chowning, Matt Mullenweg, Matt Wiebe, Maxime Pertici, Mayank Majeji, mdrockwell, Meg Phillips, megabyterose, Meher Bala, Mehrshad Darzi, Mehul Kaklotar, Mel Choyce-Dwan, mendezcode, mgol, Michael Arestad, Michael Babker, Miguel Fonseca, Miina Sikk, Mike Schroder, Milan Dinić, Milana Cap, mirka, Mohamed El Amine DADDOU, Monika, Monika Rao, morenaf, mrjoeldean, Mukesh Panchal, munyagu, mzorz, Naveen, net, nicky, Nico, Nico Martin, Nicola Laserra, Nicolas Juen, NicolasKulka, Nik Tsekouras, Noah Allen, nwjames, oakesjosh, Olga Gleckler, ovidiul, oxyc, Paal Joachim Romdahl, Pascal Birchler, Paul Bearne, Paul Biron, Paul Bunkham, Paul Schreiber, Paul Von Schrottky, pawki07, pbking, Pedro Mendonça, Pete Nelson, Peter Smits, Peter Wilson, Pinkal Devani, Piotrek Boniu, Prem Tiwari, presstoke, prettyboymp, Prince, pypwalters, Q, r-a-y, Rafael Galani, rafhun, Rami Yushuvaev, Ramon Ahnert, ratneshk, Ravi Vaghela, ravipatel, retrofox, Reza Ardestani, Riad Benguella, Rian Rietveld, Richard Tape, Robert Anderson, Rodrigo Primo, roger995, Rolf Siebers, Romain, Ronnie Burt, Ross Wintle, Ryan Boren, Sébastien SERRE, Sören Wrede, Saša, Sanket Chodavadiya, Sarah Ricker, sarayourfriend, Scott Taylor, Sebastian Pisula, SeBsZ, Sergey Biryukov, Sergey Yakimov, sergiomdgomes, Shahin Sid, shaunandrews, Shital Marakana, Slava Abakumov, snapfractalpop, souri_wpaustria, Stefano Minoia, Stefanos Togoulidis, Stephen Bernhardt, Stephen Edgar, Steven Word, Subrata Sarkar, Sunny, t-p, Takashi Kitajima, Tami, Tammie Lister, Tanvirul Haque, Tapan, TeamDNK, TeBenachi, Thierry Muller, thorlentz, Tim Hengeveld, Tim Nolte, Timi Wahalahti, Timothy Jacobs, tinodidriksen, Tkama, tmatsuur, Tobias Zimpel, tobifjellner (Tor-Bjorn Fjellner), Toni Viemerö, Tony A, Tonya Mork, tonysandwich, Torsten Landsiedel, Toru Miki, transl8or, Tyler Tork, Ulrich, Umang Vaghela, vandestouwe, vcanales, Vipul Chandel, Vlad T., webcommsat AbhaNonStopNewsUK, WebMan Design | Oliver Juhas, Wendy Chen, wesselvandenberg, Weston Ruter, Willis Allstead, worldedu, WP OnlineSupport, Xristopher Anderton, Yann Kozon, Yoav Farhi, yscik, Yui, yuliyan, Zebulan Stanphill, and zieladam. Code is poetry. View the full article
  11. XenForo 2.2.4 Released​Exactly ten years and a day since the very first stable release of XenForo, we are happy to present a new release to increase the reliability and performance of XenForo. XenForo 2.2.4 is now available for all licensed customers to download. We strongly recommend that all customers running previous versions of XenForo 2.2 upgrade to this release to benefit from increased... Read more View the full article
  12. WordPress is open source software, maintained by a global network of contributors. There are many examples of how WordPress has changed people’s lives for the better. In this monthly series, we share some of the amazing stories that are lesser-known. From a natural interest in computers and fixing things as a young woman, Olga Gleckler from St Petersburg, Russia, found WordPress took her on a journey to becoming a successful female tech entrepreneur. On International Women’s Day, we share her story. Finding your path can take longer than you expect From the age of 15, Olga found herself under pressure to find a free place for her professional studies. She said: “I didn’t know how high or low my chances were even if I had very good marks. I could have been just the biggest fish in a small pond. But anyway, I made up my mind to go to technical school.” On leaving school in St Petersburg with her certificate, Olga felt her knowledge of opportunities was very narrow. She had pictured being an ecologist or guide translator based on the subjects she had been taught at school. There was also an advertising boom in Russia and she began to explore this as a career avenue. She had developed her computer skills and found opportunities to practise by helping her teachers with administrative work. Though she did not have access to any formal career advice, her journey led her into programming. She said: “The range of technical schools was not wide. I spent four years studying transistor markings, soldering and drawing PCB layouts. Programming courses using Pascal didn’t do anything useful with it.” A lack of suitable access to English-language courses made things harder for Olga. She was determined that she would master the language later in her life. In the meantime, she left technical school with an honors degree and improved typing skills. “I faced it was a wild, unfriendly market. I didn’t know how to recognize a genuine job offer or how to avoid the bad ones. It was difficult and I don’t know how long I would’ve looked for work without help.” Think differently to find where you belong Olga’s father worked in an IT company and was able to give her some advice and help with potential introductions. When she was still studying, he suggested her strong technical skills might be useful as a substitute typist. When she finished her studies, he helped her apply for a job updating a legal system on clients’ computers. Six months later, she got a full-time job in the same service department. She liked her position and her clients. However, she was given friendly advice that without a university degree she would not be able to have any further promotions. At this time, Olga was trying to study PHP from a book. She found it very exciting at first, but a lot of their functions did not give her explanations on how to build something useful. She found when she tried to build practical items from book reading, it did not always make sense and the solutions would often fail. She said: “It was hard to admit a failure even to myself and it was nagging me for a long time. I had to choose something I could handle, that I was interested in and could afford. It turned out to be advertising.” She spent most of the family’s holidays on learning sessions during the next six years. Olga recalled: “It was tricky for my husband to make me leave a computer, once I was glued to it, so he bought me my first laptop. English was still hard for me, I got high marks through just memorizing all the words in a textbook and how they should sound.” Olga’s life took a change after having a new baby and she spent three years doubting her professional skills and her chances of getting a good job. She tried to get back into other interests through studying, baking and drawing, but found ‘the pram was pulling me back’. She found she became very isolated and felt less able to contribute as the family was relying on her husband’s income as she tried to focus on looking forward. She said: “I was convinced (and saw) that not too many companies wanted a woman in the office, who with a small baby might need lots of leave.” She finished her education when she returned to work after three years caring for her son. She secured a promotion but with changes in the company’s staffing, things were tense. She found the difficulties there had become more heightened and felt that young female colleagues were treated as ‘pieces of furniture’ by one manager. She did not want to stay in this environment and in a few months time decided to leave. Your next chapter may be nearby Determined to not repeat this type of experience, Olga looked at the brighter side. She said: “I wanted to be a marketer. Knowing how tricky it is to sell intangibles, I wanted a solid product to work with.” It turned out to be more difficult to find a job outside traditional IT as a young mother. Some human resource officers advised her to remain within the technology arena. Olga remained hopeful and continued to study hard. She had many learning experiences along the way, which she hopes others can learn from too. One was setting a low bar to employers. She said: “Companies I worked in wanted to get all publicity and sales increases achieved through deductions from my salary.” This happened once and the next time she was in this situation she asked specifically about the budget before signing up. “I was assured this would not be the case, but again I found the budget for publicity came out of my wages. It was a tough period of disappointments. So when I was offered a part-time administrative job with basic sick leave, I took it gladly as a reprieve.” The job was far from home and involved a lot of travelling. Olga spent two to three hours a day on buses with Harry Potter audio books for company. “In these traffic jams, I started to feel English at last and loved it. It gave me a freedom no money can buy. Life was getting better.” Though the job did not pay highly, it gave her something valuable – a working website. After her boss and the developer parted company, she was asked to maintain the site. Through some studying and reverse engineering, she discovered how it worked and it gave her an insight into how to write simple websites from scratch. Olga’s first encounter with JavaScript wasn’t easy: “My first JavaScript calculator almost made me crazy, but I pursued it.” Quickly she started to get small tasks from friends and relatives, usually to solve some urgent problems and started to meet popular content management systems. One of the first she met with was WordPress. There was an issue in a website theme used by a website which had been changed and not maintained. It took a whole weekend to solve, but she was determined to work it out. Back then, WordPress was ‘just a system’. She didn’t know then how much it was to become part of her life. Olga spent the next two years in this role. As time went on, she started to feel worried and less satisfied with the work. The last straw for her was a negative statement from her boss, who was not a programmer and who hadn’t seen any of the work done on the website. She felt the approach was unfair as she had done extensive work on the site. She recalls: “I became angry, but it was exactly what I needed to move jobs.” When Olga was job hunting, she didn’t feel she had the courage to apply for a developer’s role, despite the learning and work she had already done. So instead she started working on projects where she felt she was more like a ‘seller of box-ready websites’. It was another tough half a year for her with a lot of work, low payment and plans not turning out as she had hoped. On top of long hours, she ended up with pneumonia. She said: “I see now that I was doing a disservice to customers, websites are not a microwave meal – quick, cheap and dummy. There was no life in the sites without a lot of work which no one was willing to buy. Most of the sites I sold back then died after the first year and they never were truly alive and useful.” You need to be brave and have courage Olga really wanted a developer job but seeking jobs of this type was very frustrating. From the job adverts she found, it felt like most IT companies were asking for geniuses who already knew a lot of technologies and frameworks. She found this very demotivating. She then found a job offer on a website outside the most popular job portals and it seemed like a perfect fit. They wanted someone with experience to write from scratch, understand someone else’s code and maintain it, with an ability to translate technical documentation and articles, and make simple designs for printing products. After completing a trial task, she was taken on, and enjoyed a better salary, in a calm environment with good colleagues and without the requirement for a lot of extra hours. The advert turned out to be a direct ad from one of the sales departments in a technology company. By succeeding in the task set, Olga had bypassed the Human Resources team which she felt would not normally have considered her. Her boss agreed to her working remotely most of the time. It solved any potential leave problems which Olga had thought may be an obstacle. For Olga it had been 14 years since the original decision to become a programmer and it was only the beginning. After a few years at what she describes as an ‘amazing experience’ in this workplace, Olga felt able to move on to her next challenge as a developer. Decision-making can benefit from wider knowledge After working with different systems Olga became sure that WordPress is the best CMS for developers and clients. But she was disappointed to find that the ease of use meant that good code was not always a priority for some of the sites she looked at. “The biggest flaw of WordPress – it’s so easy to make things work that some may feel they don’t need to bother to do things right, but this becomes a problem later.” In custom themes for a site, she also saw sites being made and clients left without any further support, or items hard coded when clients actually needed more control to change regularly. Olga used to rely on examples she could easily find, documentation and search engines to improve her understanding in using WordPress. She discovered that just by searching for a specific feature or a solution, you can miss the whole picture. She turned to online courses to get more comprehensive knowledge and then started to attend WordPress events, firstly online and then by foot, trains and planes! She discovered a worldwide community that was very much alive. She didn’t know when she started studying online materials and attending discussions that she would end up contributing herself to the Learn WordPress platform a few years later. WordCamps and contributor days became a big part of her life. From her early days attending events and starting out contributing to WordPress, she is an active member of the WordPress.org Global Marketing and Polyglots Teams, and supported the recent WordPress release. She is just beginning her first WordCamp organiser experience, joining WordCamp Europe 2021 on the Contribute Team. Olga said: “Through the wider WordPress community, I knew not only where to look but also whom to ask. Most importantly, I found allies who don’t think I’m going crazy by speaking with delight about work, and with whom I share a passion and fondness for WordPress. This is what matters. “Now, after more than seven years of full time development, I am still enjoying endless learning, frequent discoveries, mistakes and an impassioned wish to do better.” This and a desire to help others use WordPress.org is part of Olga’s continued contribution to its Support and Marketing Teams, and led her to be involved in the Release Marketing questions and answers in 2020. There is no chequered flag on the way The road to freedom and becoming her own boss has not been easy for Olga. It is the path that got her where she is today, and she continues to find joy in it. She retains the lessons she’s learned and is always hungry to learn more. “I travelled through a very uneven path, with a lot of obstacles and noise, but for me it’s like a kaleidoscope where a little turn presents a new picture, a new “ah-ha” moment, new excitement after seemingly pointless efforts.” She added: “When in doubt I remind myself about David Ogilvy (generally considered the Founding Father of the modern advertising industry) who tried a lot of things before he struck gold with advertising, and maybe that’s why he did.” Finally, she learned not only to keep a good spirit and try different things, but also to dare as you move forward. Contributors Thanks to Abha Thakor (@webcommsat), Nalini Thakor (@nalininonstopnewsuk), Larissa Murillo (@lmurillom), Meher Bala (@meher), Josepha Haden (@chanthaboune), Chloé Bringmann (@cbringmann) and Topher DeRosia (@topher1kenobe). Thank you to Olga Gleckler (@oglekler) for sharing her #ContributorStory. This post is based on an article originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard. Meet more WordPress community members in our People of WordPress series. #ContributorStory #HeroPress Photo credits: 2nd and 4th Pablo Gigena, Berlin, 2019 View the full article
  13. Moderation feels a bit like an outdated term created pre-social media, but it stuck. We’d like to re-frame your thinking in terms of guiding your community versus moderating it. Guidance is an essential component to any thriving community because it creates structure and boundaries for the community. Oftentimes, people think community guidance is about restriction, but in reality it allows your community to express itself in a healthy way. All communities run into issues unless there are clear guidelines laid out for all members. It only takes a couple of toxic trolls to bring down an entire community of thousands of members. As a community leader, it's important to find the balance between allowing freedom of speech and restricting what people can and can't say. An Internet troll tends to want to see what they can get away with and push the boundaries to the brink. They’ll claim that they are not allowed to speak their mind, but I want to stress the importance this: Freedom of speech has some limitations. For instance, you can't just shout ‘FIRE!’ in a crowded room because you believe you have the right to freedom of speech (though some would argue you can, which is why guidance is imperative). There are certain rules that everyone needs to follow in order for an online community to function. The first thing you'll want to do when guiding your community is... to create community guidelines. These guidelines must be visible and easy to access. There, you can lay out all the nitty-gritty rules you want, but essentially it should boil down to this: Be kind. Treat people with respect when posting and remember that there’s a person behind the user name. It's important not to hide behind anonymity just because you can. Being a part of the community means that all members must abide by these guidelines. Now what happens if someone "breaks the rules” or ignores these guidelines? As your community’s leader how do you proceed? You do so by creating actionable rules that can adversely affect a member’s standing in your community if they break them. I know that sounds kind of threatening, but it's important to establish to your community that you're there for them and that your priority is to hear them out, but at the same time you must take action to keep the peace. Invision Community has automatic moderation tools and a warning system section baked into the software. Below is a snapshot of Invision Community's administration panel where community leaders may set up custom automatic moderation rules: Tap here for more specific information on how to implement community guidance/moderation to your community. One important component to these rules is that you enforce them across-the-board to all members and do so consistently. If you leave the door open for one member and not another, it's going to create an unwanted hierarchy and instigate chaos. One of the best ways to be consistent is by walking the walk. Show your community how you want them to post by posting and contributing that way yourself. What that does is it sets a visible precedent. From there, you'll begin to notice other community members contributing in a way that is similar to you (lead by example). This is a great opportunity to consider them to join a new moderators team. Whether they are paid moderators or are volunteering their time, you still want them to be mini leaders inside your community. It's important that you are a positive role model for them. Watch the video up top, then drop us a line in the comments! And hey, while I've got you... check out what our own community has to say about moderation (aka community guidance ). Remember, guiding your community starts from the top (a.k.a. you!). Now get out there and moder-... guide! Stay tuned for more Invision Community video content coming soon! View the full article
  14. Moderation feels a bit like an outdated term created pre-social media, but it stuck. We’d like to re-frame your thinking in terms of guiding your community versus moderating it. Guidance is an essential component to any thriving community because it creates structure and boundaries for the community. Oftentimes, people think community guidance is about restriction, but in reality it allows your community to express itself in a healthy way. All communities run into issues unless there are clear guidelines laid out for all members. It only takes a couple of toxic trolls to bring down an entire community of thousands of members. As a community leader, it's important to find the balance between allowing freedom of speech and restricting what people can and can't say. An Internet troll tends to want to see what they can get away with and push the boundaries to the brink. They’ll claim that they are not allowed to speak their mind, but I want to stress the importance this: Freedom of speech has some limitations. For instance, you can't just shout ‘FIRE!’ in a crowded room because you believe you have the right to freedom of speech (though some would argue you can, which is why guidance is imperative). There are certain rules that everyone needs to follow in order for an online community to function. The first thing you'll want to do when guiding your community is... to create community guidelines. These guidelines must be visible and easy to access. There, you can lay out all the nitty-gritty rules you want, but essentially it should boil down to this: Be kind. Treat people with respect when posting and remember that there’s a person behind the user name. It's important not to hide behind anonymity just because you can. Being a part of the community means that all members must abide by these guidelines. Now what happens if someone "breaks the rules” or ignores these guidelines? As your community’s leader how do you proceed? You do so by creating actionable rules that can adversely affect a member’s standing in your community if they break them. I know that sounds kind of threatening, but it's important to establish to your community that you're there for them and that your priority is to hear them out, but at the same time you must take action to keep the peace. Invision Community has automatic moderation tools and a warning system section baked into the software. Below is a snapshot of Invision Community's administration panel where community leaders may set up custom automatic moderation rules: Tap here for more specific information on how to implement community guidance/moderation to your community. One important component to these rules is that you enforce them across-the-board to all members and do so consistently. If you leave the door open for one member and not another, it's going to create an unwanted hierarchy and instigate chaos. One of the best ways to be consistent is by walking the walk. Show your community how you want them to post by posting and contributing that way yourself. What that does is it sets a visible precedent. From there, you'll begin to notice other community members contributing in a way that is similar to you (lead by example). This is a great opportunity to consider them to join a new moderators team. Whether they are paid moderators or are volunteering their time, you still want them to be mini leaders inside your community. It's important that you are a positive role model for them. Watch the video up top, then drop us a line in the comments! And hey, while I've got you... check out what our own community has to say about moderation (aka community guidance ). Remember, guiding your community starts from the top (a.k.a. you!). Now get out there and moder-... guide! Stay tuned for more Invision Community video content coming soon! View the full article
  15. That was Josepha Haden Chomphosy on WordPress is Free(dom) episode of the WP Briefing Podcast, speaking about the four freedoms of open-source software. Those four freedoms are core to how WordPress is developed. A lot of the updates we bring you this month will resonate with those freedoms. WordPress now powers 40% of the web W3Techs reported that WordPress now powers 40% of the top 10 million websites in the world! Every two minutes, a new website using WordPress says, “Hello world”! For the top 1000 sites, the market share is even higher at 51.8%. Over the past 10 years, the growth rate has increased, which is reflected by the fact that 66.2% of all new websites use WordPress! WordPress release updates February was an eventful month for WordPress releases! WordPress maintenance releases — version 5.6.1 and version 5.6.2 — came out this in February. Update to the latest version directly from your WordPress dashboard or by downloading it from WordPress.org. Members of the Core team are working hard on WordPress 5.7, due in March. Beta 1, Beta 2, and Beta 3 versions of WordPress 5.7 launched in February. The first and second release candidates of WordPress 5.7 are also out! You can test the Beta versions and the release candidate by downloading them from WordPress.org or using the WordPress Beta Tester plugin. To know more about WordPress 5.7, check out its field guide. Want to contribute to upcoming WordPress releases? Join the WordPress #core channel in the Make WordPress Slack and follow the Core team blog. The Core team hosts weekly chats on Wednesdays at 5 AM and 8 PM. UTC. You can also contribute to WordPress 5.7 by translating it into your local language. Learn more on the translation status post. Gutenberg celebrates its 100th release with version 10 The 100th release of the Gutenberg plugin — Version 10, launched on February 17th, more than four years after the project was first announced at WordCamp US 2016. Matias Ventura’s post offers a bird’s eye view of the project over the last four years. Version 10 adds the basic pages block and makes the parent block selector visible in the block toolbar. Version 9.9 of Gutenberg — coincidentally, the 99th release of the plugin, which is also the latest Gutenberg release that will be featured in WordPress 5.7, also came out in February. Key highlights of the release include custom icons and background colors in social icons, a redesigned options modal for blocks (which is now called block preferences), and text labels in the block toolbar. Want to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group. Full Site Editing updates Full Site Editing (FSE) is an exciting new WordPress feature that allows you to use blocks outside the post or page content. The main focus of the Core team for 2021 is to merge FSE into WordPress core. Here’s the latest on the Full Site Editing project: The second call for testing as part of the Full Site Editing outreach program is out! To participate, check out the second testing call on the Make/Test blog and join the #fse-outreach-experiment Slack channel. Deadline: March 5, 2021. In case you missed participating in the FSE outreach program, you can now test FSE anytime —check out this handbook page on testing FSE to learn more. Contributor teams are asking for help from local WordPress Communities to support the FSE Project. Learn more on how you can contribute. Check out these answers for the most common FSE questions on the Make/Test blog. @chanthaboune has provided an update on the current status of the FSE and themes. Decision-making checklist for in-person meetups The Community Team has published handbook pages and a decision-making checklist for organizers to restart in-person meetups at areas where it is safe to do so (e.g., countries such as New Zealand, Australia, and Taiwan, where there are lower COVID-19 risks). However, WordPress meetups and WordCamps in most parts of the world will remain online due to COVID-19. Further Reading The Polyglots team has kicked-off a proposal to create a working group of contributors to develop training resources for translation contributors. The Meta team is actively working on a tool to help the Themes team automate the theme testing process. The team has already shipped a proof-of-concept of the Theme Review Action tool to test the process and is looking for feedback. The Meta team is also working on reducing the Plugin team’s workload by improving the code scanner tool used for scanning plugins. The Themes team met with the WordPress project leadership team (Matt Mullenweg and Josepha Haden) about improving the Theme directory. They decided to reframe the theme review process by adding “review guard rails” with automated tooling. The Plugin Review Team reiterated that forked premium plugins are not allowed in the Plugin directory. After three weekends of celebrating WordPress, WordCamp India 2021 concluded on February 15. WordCamp Prague 2021 took place on February 27. WordCamp India videos are already available, and videos of both camps will soon be uploaded to WordPress.tv. Several online WordCamps were scheduled this month. WordCamp Centroamérica, WordCamp Greece, and WordCamp North East Ohio are scheduled for April 2021. WordCamp Japan takes place in June and has opened-up their call for speakers in English and Japanese. Meanwhile, the inaugural WordCamp Cochabamba (Bolivia) runs in July!. The Community Team wants feedback on how to improve online WordCamps. The team has also announced a revamped 2021 Global Community sponsorship program to support online events. The Design Team is reviewing the user experience for learn.wordpress.org. Please share any design-feedback that you have as comments on the post. The Accessibility Team is working on publishing the updated accessibility standards document (with regard to WCAG 2.1 changes) alongside the WordPress version 5.7 release. The team has also started brainstorming goals for WordPress 5.8 and beyond. The Support Team is rethinking the use of the master list used for troubleshooting recurring issues. The team is also removing plugin/theme names used as topic tags in forums. The Training Team has kicked off their March 2021 sprint planning to work on their goals. The WP Notify project working group (which is working toward a better notification system for WordPress) has completed the first version of the requirements document, and officially kicked off active development of the feature plugin. Contact the team in the #feature-notifications Slack channel if you would like to contribute. You can start by reviewing the list of the current issues. Pooja Derashri of India was featured in February’s People of WordPress series. A cross-team initiative led by the Marketing Team with support from HeroPress, the series aims to highlight lesser-known stories of WordPress contributors. The Contributor Story series is collecting new features. If you are an active contributor to a WordPress.org team or a local WordCamp, contact the Marketing Team in the #marketing Slack channel for more information. Have a story that we should include in the next “Month in WordPress” post? Please submit it using this form. The following people also contributed to this edition of the Month in WordPress: @adityakane @chaion07 @courtneypk @kristastevens and @psykro. View the full article
×
×
  • Create New...