01 Apr 2025

feedWordPress Planet

WordPress.org blog: WordPress 6.8 Release Candidate 2

The second Release Candidate ("RC2") for WordPress 6.8 is ready for download and testing!

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it's recommended that you evaluate RC2 on a test server and site.

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.8 is the best it can be.

You can test WordPress 6.8 RC2 in four ways:

Plugin Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the "Bleeding edge" channel and "Beta/RC Only" stream).
Direct Download Download the RC2 version (zip) and install it on a WordPress website.
Command Line Use the following WP-CLI command: wp core update -version=6.8-RC2
WordPress Playground Use the 6.8 RC2 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.

The current target for the WordPress 6.8 release is April 15, 2025. Get an overview of the 6.8 release cycle, and check the Make WordPress Core blog for 6.8-related posts in the coming weeks for further details.

What's in WordPress 6.8 RC2?

Get a recap of WordPress 6.8's highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since RC1, you can browse the following links:

Want to look deeper into the details and technical notes for this release? These recent posts cover some of the latest updates:

How you can contribute

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world's most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is critical to ensuring WordPress is performant and stable. It's also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.8. For those new to testing, follow this general testing guide for more details on getting set up.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Search for vulnerabilities

From now until the final release of WordPress 6.8 (scheduled for April 15, 2025), the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project's security practices and policies outlined on the HackerOne page and in the security white paper.

Update your theme or plugin

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

Thanks for continuing to test your themes and plugins with the WordPress 6.8 beta releases. With RC2, you'll want to conclude your testing and update the "Tested up to" version in your plugin's readme file to 6.8.

If you find compatibility issues, please post detailed information to the support forum.

Help translate WordPress

Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ? You can help translate WordPress into more than 100 languages. This release milestone (RC2) also marks the hard string freeze point of the 6.8 release cycle.

An RC2 haiku

Testing, 1, 2, 3
It's almost April fifteenth
Squashing all the bugs

Thank you to the following contributors for collaborating on this post: @michelleames, @tacoverdo, @jopdop30, @vgnavada.

01 Apr 2025 3:53pm GMT

Do The Woo Community: Host Adam Weeks Covers CloudFest 2025

Our host Adam Weeks was busy during CloudFest and the Hackathon. And on top of that he was making sure we had content to share while he enjoyed the event. So kudos to Adam and here are recaps of his episodes. Episode 621: Inspiring Innovation through Hackathons A peek into the CloudFest Hackathon with insights […]

01 Apr 2025 10:30am GMT

31 Mar 2025

feedWordPress Planet

Do The Woo Community: Engaging Young People in the WordPress Community

The WordPress community must engage younger generations by simplifying onboarding, providing education, promoting career opportunities, and fostering connections, ensuring sustainable contributions to the platform's future development and growth.

31 Mar 2025 9:10am GMT

29 Mar 2025

feedWordPress Planet

Gutenberg Times: Field Guide, No-Code Theme, Pattern Library, why you might not need a Custom Block — Weekend Edition 323

Hi,

Spring is here. On the weekend I saw Forsythia bushes in full bloom all over the city. Yesterday, I passed the National Museum and saw their Magnolia trees blooming as well. The temperatures are still too low for my taste, but not for long. 🌤️

"Isn't this a WordPress newsletter", you might think. I know, I know. Let's get on with it, then. Carpe diem! 🤗

Have a fabulous weekend!

Yours, 💕
Birgit

PS: The links for mentioned people are now going to their Blue Sky profile, and if I couldn't find them, it's till their X (formerly known as Twitter) profile.

Follow us on Bluesky @bph.social and @gutenbergtimes.com


The Page Builder summit 2025 is on the calendar now: Anchen le Roux and Nathan Wrigley announced the eighth edition of the virtual conference will take place from 12th to 16th of May 2025. Save the date, and add your name to the Waitlist, to receive info, when registration opens. "The summit is a 5-day event that will help WordPress developers, designers, freelancers, and agencies to build better websites faster and more efficient. As well as learn more about the page builders and the awesome things you can do with them. ", they wrote.


Web Agency Summit 2025 will happen April 7-11, 2025. "Learn proven strategies top agencies are using today to scale sustainably, streamline operations, attract high-value clients, and stay ahead of the curve."


WordSesh returns May 13-15, 2025. It is a virtual conference for WordPress professionals. Its host, Brian Richards, is a seasoned virtual conference producer and WordPress educator. His speaker and session curation is top-notch. Sign up to receive updates on the next event.

Developing Gutenberg and WordPress

WordPress 6.8 Release Candidate 1 is now available for testing. Final release is scheduled for April 15, 2025

The latest Dev Notes for WordPress 6.8


Gutenberg 20.6

George Mamadashvili released Gutenberg 20.6 RC 1 version, and it's ready for testing. What to expect in this version?

Plugins, Themes, and Tools for #nocode site builders and owners

Wes Theron created a video tutorial to teach you How to Build a WordPress Theme the No-Code Way. He shows you where to update your colors, choose your fonts, modify the Single page template and then use the Create block Theme plugin to save all the settings into a new theme's file structure.


In this short video on X (former Twitter), Jamie Marsland shows us How to create a One-Pager website with WordPress, using the site editor, core blocks and some custom CSS.


MahdiAli Khanusiya, is the designer behind the PatternWP plugin that offers a big library of WordPress block patterns and full-page templates. Using it will instantly increase the range of designs and layout you can offer your customers, and streamline your production process. There is also a pro version available.

Theme Development for Full Site Editing and Blocks

Latest six block themes in the WordPress repository:

"Keeping up with Gutenberg - Index 2025"
A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2024 on. Updated by yours truly. The previous years are also available: 2020 | 2021 | 2022 | 2023 | 2024

Building Blocks and Tools for the Block editor.

In his post How to extend core WordPress blocks with Blocks API, Joel Olawanle, technical editor at Kinsta, introduced you to the basic extension methods like Block Styles and Block Variations with code examples and multiple ways to accomplish the tasks.


Alfredo Navas, web developer at WebDev Studios, wrote a tutorial on how to use the Block Bindings API and why you might not need a Custom Block. Navas walks you through registering a Custom Source, how to create a Block Variation with custom data and making it all work in the editor and on the front end.


In last week's livestream, Ryan Welcher created a new WordPress block theme for the Block Developer Cookbook and gave it a new look. You can watch him turning change his color scheme and turn his existing theme into a style variation.


Brian Coords found a way to create Dynamic WordPress Playground Blueprints with Cloudflare Workers and shared in his video how he built a system to spin up demo WooCommerce stores. The code lives on GitHub

Need a plugin .zip from Gutenberg's master branch?
Gutenberg Times provides daily build for testing and review.

Now also available via WordPress Playground. There is no need for a test site locally or on a server. Have you been using it? Email me with your experience

GitHub all releases

Questions? Suggestions? Ideas?
Don't hesitate to send them via email or
send me a message on WordPress Slack or Twitter @bph.


For questions to be answered on the Gutenberg Changelog,
send them to changelog@gutenbergtimes.com


Featured Image:


Don't want to miss the next Weekend Edition?

We hate spam, too, and won't give your email address to anyone
except Mailchimp to send out our Weekend Edition

Thanks for subscribing.

29 Mar 2025 9:21am GMT

28 Mar 2025

feedWordPress Planet

Do The Woo Community: Christian Taylor Joins as Co-Host of the Creative Sparks Show

BobWP announces new co-hosts for the Content Sparks show, video content expert Christian Taylor.

28 Mar 2025 11:40am GMT

Do The Woo Community: Do the Woo Friday Shares, March 28, 2025 v12

This content highlights our carefully selected information and resources from the Woo and WordPress community, aiming to provide valuable insights and updates for users and enthusiasts in the digital space.

28 Mar 2025 8:42am GMT

27 Mar 2025

feedWordPress Planet

Do The Woo Community: WordPress Flexibility and Simplicity: Building for Users with Ben Ritner

In today's Woo ProductChat, co-hosts Katie Keith, founder and CEO at Barn2, and James Kemp, the core product manager at WooCommerce, sit down with Ben Ritner, the Senior Director of Product at StellarWP. They dive into the intricate balance between customizability and simplicity in WordPress products, particularly focusing on Ben's work with the Cadence suite. […]

27 Mar 2025 4:39pm GMT

Do The Woo Community: Leveling Out the Audio on a Podcast with Multiple Guests

Podcasting requires managing sound levels effectively, especially during livestreams. Auphonic, with its Loudness Normalization feature, simplifies post-production, ensuring balanced audio quality and saving valuable time for creators, plus a lot more.

27 Mar 2025 12:26pm GMT

BuddyPress: BuddyPress 14.3.4, 12.5.3 & 11.4.4 Security Releases

BuddyPress 14.3.4, BuddyPress 12.5.3, and BuddyPress 11.4.4 are all now available. This is a security release. Please update as soon as possible.

14.3.4, 12.5.3 & 11.4.4 fixed two bugs:

For complete details, visit the 14.3.4 changelog.

You can get the latest version by clicking on the above button, downloading it from the WordPress.org plugin directory or checking it out from our Subversion repository.

Many thanks to our 14.3.4 contributors

emaralive, jjj, and dcavins.

27 Mar 2025 2:22am GMT

26 Mar 2025

feedWordPress Planet

WPTavern: #162 – Jo Minney on Website Usability Testing for WordPress Projects

Transcript

[00:00:00] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, the efficacy of website usability testing for WordPress projects.

If you'd like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice. Or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you'd like us to feature on the podcast, I'm keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

Today I bring you the first in a mini series of podcasts I recorded in person at WordCamp Asia in Manila. This flagship WordPress event brought together hundreds of WordPress professionals, enthusiasts, and all manner of interested parties under one roof for a three day event. One contributor day, and two days of presentations.

I tracked down several of the speakers and workshop organizers and recorded them speaking about the subject they were presenting upon. I hope that you enjoy what they had to say.

So on the podcast today, we have the first of those conversations, and it's with Jo Minney.

Jo based in Perth, Australia, is passionate about user experience, data-driven decision making, cats, pockets, and travel. She's a small business founder, and works with organizations creating digital platforms with WordPress. She also freelances as a UX consultant. She volunteers with Mission Digital to address social issues using technology, and is an ambassador for She Codes Australia, promoting tech accessibility for women. Recognized as a 2023 Shining Star by Women in Technology, Western Australia, Jo is an international speaker on topics like user experience, accessibility, and gender equality. She's committed to ensuring a seamless user experience, and today shares her insights from practical, everyday usability testing.

Joe's presentation entitled, Budget Friendly Usability Testing for WordPress, helped attendees understand what usability testing is, and clarified why it differs from other testing methods. She shares examples from her work showing how small changes can significantly impact user experience, which is better for you, the website builder, and your client, the website owner.

We also discuss how usability testing can transform a website's effectiveness by improving conversions. Joe explains the importance of recruiting novice users for testing, and highlights how usability testing pushes for real, user-centered, improvements.

Towards the end, Jo share's practical advice on when and how to integrate usability testing into your process. Advocating for early and iterative testing to preemptively address potential issues.

If you're looking to gain a deeper understanding of usability testing and its benefits, this episode is for you.

If you're interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast where you'll find all the other episodes as well.

And so without further delay, I bring you Jo Minney.

I am joined on the podcast by Jo Minney. Hello, Jo.

[00:04:06] Jo Minney: Hi. It's good to be back again Nathan.

[00:04:08] Nathan Wrigley: Yeah, you've been on the podcast before. But this time it's different because this time we're actually facing each other. Last time we were doing it on, you know, something like Zoom or something like that, but here we are staring at each other because we're at WordCamp Asia. We're in the Philippines, Manila. It is the second day of the event, kind of. We had Contributor Day yesterday. Today is presentation day. It's the first day of the presentations, and you are doing one.

[00:04:29] Jo Minney: I've done one actually. I did it at 11 o'clock this morning.

[00:04:33] Nathan Wrigley: How did it go?

[00:04:34] Jo Minney: It went really well, I think. I had very good feedback from it. Half of the things on my slides didn't work. I think that's normal for a conference though, and I'm pretty experienced now at just winging it, and rolling with it anyway, so. It was really exciting because it's a topic that I'm super passionate about and I haven't had a chance to speak about it at a conference before. So, yeah, it was really nice to be able to share something that I do on a day-to-day basis and can stand up there and really confidently talk about.

[00:04:58] Nathan Wrigley: I don't think I've ever spoken about this subject before in any of the podcasts that I've done. That is quite nice, and it's novel. I'll just introduce the topic. The presentation that you gave was called Budget-Friendly Usability Testing for WordPress. And obviously that sort of sums it up. We're going to talk about usability testing.

But before we do that, Jo, just to nail your colours to the mast a bit, tell us about you. Where you're from. What you do for a job, and anything that you think is relevant to this podcast.

[00:05:22] Jo Minney: Okay, I really like cats and pockets.

[00:05:25] Nathan Wrigley: I saw that in your show notes. Why pockets?

[00:05:27] Jo Minney: Okay. So I think pockets are a great example of something that can be both a fantastic and a terrible user experience. You are like, oh yeah, maybe I know what you're talking about. But, let me ask, do you live with a woman?

[00:05:39] Nathan Wrigley: I do.

[00:05:39] Jo Minney: I know that's a very personal question, sorry Nathan. But, how many times on average a month does she complain about not having pockets in her clothing?

[00:05:48] Nathan Wrigley: Never, she carries a bag.

[00:05:50] Jo Minney: Yeah, but why do we have to carry a bag, right? She has to carry a bag because her clothing doesn't have pockets. So I spoke at a conference late last year, and I asked this question. This has been a life goal of mine, was to speak about pockets at a conference. And I managed to do it. I asked all of the women in the audience, hands up if you've ever thrown out clothes or gotten rid of them because they didn't have pockets in? And every single woman stood up and was like, yes, I've gotten rid of clothes because they didn't have pockets in.

Most of the people that were there were men. And I said, stand up if you don't have pockets in your clothes right now. And 400 men stayed seated. But this is an example of something where, yes, there's a subsection of the population that's experiencing this problem, but it's a big problem for us. It's very frustrating. You're at a conference, you don't want to have to carry around a handbag. So, pockets. They're a great example of user experience.

[00:06:45] Nathan Wrigley: Okay, I get it. I understand now. Tell us a little bit about your sort of day-to-day work, though. You work with WordPress, I guess.

[00:06:51] Jo Minney: I do. So I run a small agency. We're what I usually call a micro agency, and we have only three of us that are working on the WordPress team. We do website development, but specifically for charities, nonprofits, cause-based organisations, so a lot of social enterprises and that sort of thing.

On top of that, I also do consulting for user experience research. I'm not a designer. UX and UI often get lumped together. They're very different. UI is about the interface and what people see, and UX is about user experience and how people use things. And they can't be completely separated, but they're also very different.

So I am lucky because I work in the niche that I work in, that I'm able to do a lot of usability testing and it's something that a lot of people don't get the experience to do. And so I thought I would share what I've been able to learn over having this sort of unique opportunity to do so much usability testing, and share with people how they can do it more cost effectively, but also the benefit that it can have for a project.

[00:07:54] Nathan Wrigley: Let's dig into it and I'm going to actually crib the questions which you posed to the audience today. You put four questions surrounding your subject. And the first one is this. And I'm sure that the listeners to this podcast, if they're anything like me, they'll probably have some impression that usability testing is a thing that you could do. And I think the word there is could, as opposed to do, do.

I imagine most people have an impression of what it is, but whether or not they do it is another thing altogether. But that would then lead to this. What even is it? So what is usability testing, and what are you actually testing for? So that was a question you posed to the audience and now I'm throwing it right back at you.

[00:08:34] Jo Minney: Yeah, it's a good question. It's probably the sensible place to start. So usability testing is not the same as user testing, or user acceptance testing. And it's focusing on, how do we identify what the problems are with something that we have created?

So a lot of UX research is focused on what we call quantitative testing. So, meaning we're looking for quantities of something. It could be the amount of time it takes someone to do an action. It could be using heat maps. So we have a thousand users, let's see where their cursors most often are going. Let's see how often they scroll down the page. And quantitative testing is really good at showing you comparisons of whether one thing or another thing works better, but it's not actually good at identifying what the problem is, only that there is a problem.

So you can do a lot of testing and still not know what the problem is. Usability testing is different because it's what we call qualitative testing. So it means that we're not looking for big numbers, we're not looking for lots of data. We are looking for really deep user experience examples. And in a nutshell, the way that that works is you recruit some participants, usually five people per round is ideal. And often I get asked, well, how can you have statistically significant data with only five people? That's not the point of qualitative testing. The point of qualitative testing is not to have statistically relevant data, it's to have the actual user experiences.

So you recruit your people, you come up with your research questions and that's the problem that you're trying to solve or the question you're trying to get an answer to. So, an example might be, are users going to recognise this label that I've used in my navigation? Is this button going to get clicked if I put it in this location? It's often a thing that, if you're working with a customer to develop a website for them, what we find is that often the things that we are testing for in usability testing are things that the customer and I disagree on, or things where they weren't sure when they made the decision in the first place. And they're a great example of things that you want to test for.

But the research questions are only the first part because if I say, the example I used in my talk today is that we had a support service directory. And this was for people who are experiencing family domestic violence. And they didn't want to use the term directory because it's a very harsh term. So they had called it support services, which sounds, on the surface like a good idea, but a lot of the people that are using their platform are not English first language. And they also tend to be in a really stressed out state as you can imagine.

And so what we actually found is that when we said to them, can you imagine you're helping someone, can you help them find a legal service that will enable them to get a restraining order or something like this? What we found is that repeatedly they didn't go to support services to start with. The minute we changed that to service directory, they started to find the thing that we wanted them to click on.

It's such a small change, but it made a huge impact, the usability. Now, we found that out after the second test, which meant that we were able to change it after the second test, and then we had three more tests where we could show that every time they were able to find the thing that we wanted them to be looking for.

So this is an example where the research question and the research task or the activity that we're giving to the user, they're not the same thing. If we said to them, find support services, find the service directory, if we use that language, obviously they're going to look for that label. But instead we asked them to do an activity that would hopefully take them to the place we wanted them to go to.

And then finally the last step is to iterate that and to actually take that data and make decisions, and make improvements to the project iteratively to try and make it better. That's the goal, right? Is to find what the problems are and fix them. So we still have to work out how to fix them, but at least we know what the problems are and not just that people were not clicking on the button and we don't know why.

[00:12:27] Nathan Wrigley: I have a couple of follow up questions. First thing isn't the question, it's an observation. So that's really cleared up in my head what it is, so that's amazing. But one of the things that I want to know from that is, do you filter out people who, let's say for example, you've got a website, the kind that you just described. Do you filter out people who are not the target audience? So in other words, I don't know, maybe that's not a perfect example. But let's say, on some websites, would it be better to have really inexperienced users of the internet as your five candidates?

[00:12:59] Jo Minney: That is exactly the ideal person.

[00:13:02] Nathan Wrigley: So people who are just, I've never come across this before. You want people who are potentially bound to be confused. If somebody's going to be confused, it's you five.

[00:13:10] Jo Minney: That is the ideal participant for a usability study. And often people say, I want to start learning how to do usability testing. Where should I start? And my advice to them is always the same, with your mum.

Recruit a person that's a generation older than you, because I can guarantee that in most cases, sorry to generalise, but they tend to be less efficient and less used to technology because they haven't grown up with it. So for millennials and younger, we have had technology for all of our adult lives and most of our childhood.

For my parents' generation, they have had to learn that technology as an adult, and so their brains have a different mental model, and they don't take for granted things that we take for granted. Like, when I click the logo, it will take me back to the homepage. I know that, you know that, your mum might not know that.

And I think that is something that is really valuable is to understand the benefit of testing with people who aren't as experienced with technology. Who don't speak English as a first language. Who are experiencing some kind of accessibility challenge. Whether that's using assistive technology, being colorblind. Things like that are really good things to try and get some cross-sectional representation in your testing participant pool.

[00:14:25] Nathan Wrigley: So the idea then is that you've got these novice users who hopefully will immediately illustrate the point. And it's driven by questions. So it's not just, we are just going to stand over your shoulder and watch you browse the internet, and when you do something and describe, you're looking for something and you can't find it, that's not how it's done.

It's more, okay, here's a defined task, do this thing and we're going to ask you to do five things today, we want you to achieve them all and describe what you're doing, but it's more of that process.

And then the idea is that you go from an imperfect website, slowly over time, iterating one problem after another towards a better website. The goal is never reached. It's just an iterative process.

[00:15:01] Jo Minney: That's it. Perfection does not exist.

[00:15:03] Nathan Wrigley: Okay, so that's interesting. So we start with the novice. We've got a small cohort of people. We ask them specific questions, and we get feedback about those specific questions.

So the other thing that I wanted to ask then is, when do you do it? Because it feels like you need to build the website first, then show it to people. So there's got to be something. This isn't process of discovery prior to the website. You need pixels on pages. Buttons that are potentially mislabeled or what have you. Is that the case? Build first, then usability test afterwards. There's no usability testing prior to the initial build.

[00:15:37] Jo Minney: It's kind of a trick question because you can usability test at most stages. Probably the only stage you can't usability test at is when you don't yet have a site map. Having said that, my recommendation is, assuming you had unlimited budget and unlimited time, I would do at minimum two rounds of usability testing, and I would do one before you have any design, and I would do it just using wire frames.

So we build interactive wire frames using WordPress. So for the demo that I did today, I spun one up. I used InstaWP. You can get like a seven day website or something through there. It took me 42 minutes to build out the website in just the block editor, with no design or anything, just the layout of it. And I was eating a loaded potato at the time. So if I can do that in 42 minutes, eating a loaded potato, and that's not my job, I think it's a pretty efficient and cost effective way of being able to do early usability testing.

And often the thing that we're testing for there is like, have I got the right navigation structure and hierarchy? Are the labels that I'm using sensible for people? Do they fit with the mental models of what our users are actually expecting? And the benefit of doing it that early is that when you don't have a design applied, it's a lot easier to identify problems.

Because there is a thing that happens in human psychology, and there's a lot of psychology in user experience. And there's a thing that happens where if something's pretty, we will say that it is easier to use. Our experience is that it's easier to use because it's nice to look at. And that's great. That means that UI is really important, but it also means that, if you have a really nice UI, it can mask problems that you have in the background. It is great that things can be easier if they're pretty, but imagine how much easier they would be if they worked well and were pretty, that's what we should be aiming for.

So typically we would do one round of usability testing when we just have a framework and just have the navigation. When someone lands on a page, sometimes we'll just write a message on there and say, congratulations, you found the service directory where you can find this thing, this thing, this thing, this thing, and then we put a little button there. When they click it, it releases confetti on the page. So they get a dopamine hit and it's like, yay, I completed the activity. You don't have to have all of your content in place to be able to do testing, and identify early that you've got problems that you need to fix.

[00:18:02] Nathan Wrigley: It sounds almost like an overly complicated design is the enemy of usability. We are drawn towards beautiful, but sometimes maybe beautiful just is overwhelming. You know, there's lots of colors on the page, the buttons get hidden, there's just too much text on there. Looks great, but it might be sort of masking the thing that you're really trying to show. And it feels like there's this tight rope act of trying to balance one thing against the other. Yeah, that's really interesting.

So, with the wire frame thing, in that case, you are really just testing, can the person find the thing? But I'm guessing once you've move beyond the wire frame stage and you've got a website, it's literally out on the internet, it's functional. It's exactly what we hope would be the perfect version, then you're drilling into more detail. You know, can a person find this resource? Do they know that this button is what we are intending them to click? Those kind of things.

[00:18:49] Jo Minney: Yeah. So I think things like searchability and discoverability are much easier to test for in the early stages when you're just doing, say, using like a wire frame or a prototype. And things like usability, you really do need to have the complete designed product to be able to test for them well. And I say that, there's actually kind of four categories of the different types of tasks that we can do. I'll give you the link to the blog post that I wrote that has all of this in detail because we do not have time to go deep into that today.

But things like, does my search form work the way that I want it to? They're the sorts of things that you do have to do some development to be able to get them working. So it's not always practical to do that at the very early stages when you do want to start testing your navigation and stuff like that.

Something that you can do is if you've only got enough budget, or enough time, to be able to do, say, five usability tests total, you could do two of them early, and then you could do three of them towards the end, after you have the majority of the design and the development work in place. Users are pretty forgiving when they're doing a usability test. If you say, this is still a work in progress, there might be a couple of pages that look odd and aren't quite ready to go live yet. If you get somewhere and you're not sure, you can just go back, it's okay.

It's not meant to be a perfect experience. The point is that you are getting their real time thoughts and feedback as they're doing it. So it's really important that you try and encourage them to follow the think aloud protocol, which is really outlining every single thing that goes through they're head, just brain dump on me please. Like, I just want to hear all of your thoughts and thought processes.

And the only thing as the facilitator that I will say during a usability test is, tell me what you're thinking. And other than that, I am completely silent. So even when it comes to giving them the activity, so if I'm asking you to do an activity like help somebody find a legal service that they can use in this particular state. I would actually send that task to you via the chat or something like that.

I would send the task to you via the chat, and then I would get you to read that task back to me, because I don't want you to be thinking about how I'm saying it. I want you to be able to go back to that task and look at it, and think about it, and process everything inside your own head. But I want you to be telling me all of that.

So often we'll find people ask questions during that, like, what should I do next? And the answer to that is really hard to train yourself out of replying to them with anything other than, what would you do if I wasn't here? And I think that's the hardest thing about learning to facilitate a usability test.

[00:21:24] Nathan Wrigley: Yeah, and in a sort of an ideal scenario, you wouldn't even be in the room. But in some strange way, you'd be able to just get into their head and say, okay, now I want you to do this, but every time you've got problem, just figure figure it out, and we'll watch. But you have to be there because you have to be able to listen to what they're saying and what have you. Yeah, that's curious.

[00:21:40] Jo Minney: Yeah, and we do, at the end of each activity, we'll then ask them for feedback on how they found it. If they had any suggestions or things that they didn't say out loud while they were doing it that they wanted to share with us. How confident were they with the activity, and did they think that they were successful in it, which is a really good way of telling, I wasn't really sure what the activity was meant to do. Or I wasn't really sure if what I found really met the needs that I was looking for.

Then we ask them, how certain are you with the answer that you just gave? And if they're like, three out of five, you're like, alright, this person didn't understand what it was that I was asking them to do in the first place. Maybe the problem is actually with my question and not with the website.

[00:22:18] Nathan Wrigley: Okay, so the whole process is, you're not just asking for feedback about the website, there's a whole process of asking for feedback about the process as well which is, that's kind of curious. Meta, meta processing.

[00:22:27] Jo Minney: Very meta, for sure.

[00:22:29] Nathan Wrigley: We're in an industry where at the moment everything is trying to be automated.

[00:22:32] Jo Minney: Is this the AI question?

[00:22:34] Nathan Wrigley: Well, no, this feels like it's a very human thing. You need actual bodies on the ground. So it's really a question of economics. Because I'm wondering if this often turns out to be a fairly expensive process. And because of that, I wonder if people push against it, because the budgets may not be there. If this is something that clients typically would say, well, okay, tell me how much that's going to cost. It's a nice idea but, okay, it's going to cost us X thousand dollars because we've got to put five people in a room and we've got to pay for your time to moderate the event, and come up with the questions and so on.

How do we manage that in an era of automation where everything is, the dollar cost of everything has got to be driven down. This feels like the dollar cost is going up because there's humans involved.

[00:23:14] Jo Minney: Yeah, it's a great question. Have you ever run a Google ad before?

[00:23:17] Nathan Wrigley: It's expensive.

[00:23:18] Jo Minney: It's very expensive. It's very expensive to get a new lead. It's a lot more cost effective to convert a lead than it is to get a new one. And the point of usability testing is to improve conversion of people being able to do the thing that you want them to do on the website.

So my first answer to that would be, look at the cost benefit analysis. It's worth it in most cases to do usability testing. Something that we've found with positioning of usability testing is that if we offer it as an add-on, then people don't want to do it because they don't want to pay for it. They see the value in it necessarily. However, we don't offer it as an add-on.

We actually have it just as part of our proposal right from the start where we're like, this is part of the point of difference between what you get when you build with us versus when you build with someone else. They'll tell you what they think is the best way to do something. If we are unsure about the best way to do something or we disagree on it, it's not going to ultimately be me making a decision or you making a decision. We're going to test and we're going to get real evidence from customers.

And they're the ones that are going to be developing it so you know that the final result that you get is going to be the best possible version of the website. And often we might be more expensive than our competitors, but people will go with us because we are not competing on price. We're competing on offering a service that nobody else is offering. I asked today in the presentation who has done usability testing before and not a single person put their hand up.

[00:24:42] Nathan Wrigley: That would've been my assumption actually.

[00:24:44] Jo Minney: Yeah. And honestly, I don't think any of the people that we're competing against in the industry that I'm in are doing the same thing as what we're doing. And so it is very much a point of difference. I think it's not a well understood technique, but it's so valuable that it is a really easy way to position yourself as being different, and really actually do a better job for your customers, for the people that you're building websites for. Because ultimately you are going to have a better result at the end of it.

[00:25:12] Nathan Wrigley: The interesting thing there is, when I say usability testing, somehow in my head there is a connection between that and accessibility. And that's not where I'm going with this question, but there's just something about it being unnecessary. And I'm not binding that to the word accessibility. What I'm saying is clients often think, I don't need to do that. Obviously, we're moving into an era where legislation says otherwise. But I can just leave it over there. I don't need to worry about that, usability testing, not for me.

However, the lever that you've just pulled, it completely changes the dynamic because you've pulled an economic lever, which is that if we can get everybody to follow this action, I don't know, fill up the cart with widgets and then press the buy now button, and go through the checkout process. If that's the thing that you're usability testing, you've made direct line. You've joined up the dots of, okay, user, money.

So it's not just about it being a better website so that people can browse around it all day. It's also about connecting the economics of it. So the usability is about people buying, converting, getting the resource. And so there might not be an economic transfer there, but it will be some benefit to your business. There might be downloading that valuable PDF that you want everybody to see or whatever.

So that's kind of interesting. That's changed my thoughts about it a little bit. And it is more about that. It's getting an understanding of what you want out the website, getting an understanding of what you think should be happening is actually possible and happening. Have I sort of summed that up about right?

[00:26:40] Jo Minney: Yeah, I think that's a really good summary it. I think the only thing I would add there is that a lot of the times the conversation around accessibility and the conversation around usability do have a lot of crossover. They are fundamentally different, but one of my favorite examples is actually something that I think applies to both.

So two of the common problems that we find very early on in design is often to do with colour. And so one of them is colour contrast and the other one is colourblind accessibility. And I think it's a great way to get people to change their thinking, and their perception of the way we have these conversations is, if you have an e-commerce website, Nathan, what would you say if I said to you, I can instantly get you 8% more customers?

[00:27:23] Nathan Wrigley: Yeah, I'd say that's great.

[00:27:24] Jo Minney: And I'd be like, cool, change your buttons so that colourblind people can read them, because 8% of men are colourblind. So actually it's only 4% of people because assuming half of them are men, then you've actually only got 4%. But still 8% of men are colourblind, that's a big percentage of the population. So if your button is red and green, then you're going to have a problem. People are not going to be able to find the thing that you want them to click to give you their money.

Likewise, if you want people to be able to use your website when they're outside and using their phone in sunlight, then you need to have good colour contrast on your website. So often this conversation is around, well, I don't have people who are disabled, I'm not trying to cater to people that are using screen readers. It doesn't matter because not very many people that are using my website are blind. And I'm like, well, I'm not blind but I still struggle when I'm looking at something where the text is too faint, and I'm looking at it on my phone, and I'm standing outside in the sun because we naturally don't visualise as much contrast there.

So I think being able to position it in a way where people can see the value to themselves. I want to use a website that has better contrast, and so it makes that conversation easier with a customer.

[00:28:32] Nathan Wrigley: I hadn't really drawn the line between accessibility and usability, but it seems like they're partner topics, basically. There's like a Venn diagram, accessibility over here, usability over here, with a massive overlap somewhere in the middle.

[00:28:43] Jo Minney: A hundred percent. That's why we always encourage having that sort of intersection between accessibility and usability in our testing pool. So we always try and have one person who experiences some kind of accessibility challenge, whether that's being colourblind, hearing impaired, if we've got a lot of video on the site, for example. And I think that it can be a really valuable way of collecting multiple data points at one time.

[00:29:04] Nathan Wrigley: When you have a client that comes to you and they've obviously, by the time that they've signed the contract with you, usability is already part of the deal it sounds like. How do you decide, what's the thing in round one that we're going to pick up on? Is there sort of like a copy book that you go through? Is it like, I don't know, buttons or the checkout or colour or? Where do you go first? And sort of attached to that question a little bit, this process never ends, right? In theory, you could do usability testing each month. But I was wondering if you did it like on an annual cycle or something, yeah.

[00:29:34] Jo Minney: If you're not changing stuff super often, I would say, there's probably more cost effective ways that you can collect information about it. Typically we encourage, long-term, have things like heat maps and stuff like that. They will help you identify if there is a problem. If you know that there is a problem, let's say you've got a heat map and you're like, why is nobody clicking on our buy now link? That is a good instance of where you would do some usability testing to figure out what the problem is.

But if everything's working and you're getting conversions, then probably doing usability testing isn't the most valuable thing that you can do. If you're looking at making significant changes to the way that your website works, that's another good time to introduce a round of usability testing. So we don't do it just for the sake of doing it. We do it because we need to do it, and because there's value in it for our customers.

[00:30:18] Nathan Wrigley: Do you keep an eye on your customer's websites so that you can sort of get ahead of that, if you know what I mean? So let's say that you put heat maps in, very often that would then get handed over to the client and it's somebody in the client's company's job is to check the heat maps. Or do you keep an eye on that and, oh look, curiously, we've seen over the last 12 months, yeah, look at that. There's not much going on over at that very important button over there. Let's go back to the client and discuss that. That could be another round of usability testing.

[00:30:44] Jo Minney: Yeah, so I think we're not uncommonly, a lot of agencies now do have some kind of retainer program where they will maintain communication and assistance for their clients. So we call them care plans. I know everyone has a different name for it. I think it's pretty standard now in the WordPress ecosystem. It's a very common thing to do.

As part of our care plans we have scheduled meeting with our clients once every three months or six months or 12 months, depending on how big the site is. And one of the things that we'll do at that time is review their analytics, review the heat maps, that sort of thing.

Ask them, have they experienced any problems? Have they noticed a downturn in the people signing up for the memberships? Or have they noticed, have they had any complaints from people about something? Is there anything that they're not sure about? Are they going to be changing the way that they operate soon, and introducing something new into their navigation that we need to consider where does that fit in the grand scheme of things?

I find if we're having those conversations early and we are the ones starting those conversations, then often we are coming to them with solutions instead of them coming to us with problems.

[00:31:46] Nathan Wrigley: I think that's the key bit, isn't it? If you can prove to be the partner that comes with, we've got this intuition that there's something that we can explore here. You are proactive, you're going to them not, okay, anything you want? Is there anything we can help you with, you know? And the answer to that is always, not really.

Whereas if you go and say, look, we've got this idea, based upon some data that we've seen, we've got heat maps and what have you, shall we explore that further? That seems much more credible. You are far likely, I think to have an economic wheel which keeps spinning if you adopt that approach, as opposed to the is there anything you want doing, kind of approach?

[00:32:18] Jo Minney: Absolutely. I think every developer's worst nightmare is having a customer come back to them and say, I've just noticed that I haven't had anyone send through anything in my contact form for the last three weeks. And I've just noticed, when I went and tested it, that the contact form's not working anymore.

I'm sure I've had that nightmare at least once. And I think if you can avoid being in that situation where they're coming to you with something like, oh my God, it's broken, how do I fix it? If instead you can go to them and be proactive about it and just kind of keep your finger on the pulse.

Yes, there's a little bit of ongoing work, but like honestly, I jump on, I check all of the analytics maybe once every three months for my clients. I set aside one day to do it. Go and have a look through that. If I notice anything, I can usually fix it, make sure that we're collecting the data again before it becomes a problem.

And then that way when there is an issue, we've got data that we can back up and we can start from there and go, okay, yes, we've identified, here's where we need to do more research. And then we can apply something like usability testing to that.

[00:33:16] Nathan Wrigley: How much of your time on a monthly basis, let's say as a percentage, do you spend on usability of existing clients? Is this something that is a lot of the work that you do? What I'm trying to figure out here is, for people listening, is this something that they can turn into a real engine of their business?

Because you might get two days, three days work a week just on the usability of pre-existing clients. So in a sense, you've created interest and work out of thin air, because these clients already exist, they're in your roster, but there's a whole new thing that we can offer to them. So, how much do you spend doing it?

[00:33:50] Jo Minney: Yeah, so it's a great question. I would say it's cyclical. I couldn't really say like, I always spend this much amount of time. There might be entire weeks that go by where my whole life is usability testing, and there might be a month that goes by where I don't do any. And it really does often depend on where our projects are in the life cycle at any particular time.

So we're often working on projects that will span over years. And because of that, they might introduce a completely new part of their project. And that's a good time to reintroduce that usability testing. As I said, like you don't really want to do it just for the sake of doing it, but at the same time, if you can show that there will be value in making a change, if you can show that there is a lost opportunity somewhere, then a hundred percent you can sell that, the value to them of, hey, you could spend $1,000 now, but you could be earning $5,000 more every month for the next several years. That's a no-brainer, right?

People are happy to make investment if they can see that there's going to be a cost benefit for them in the future. Or if the thing that they're trying to do is maybe their government website or something, and they've got a particular thing that they need to meet, they've got KPIs. If you can show that you are able to help them meet those KPIs, then they are going to invest in doing that thing that you're trying to offer them.

[00:35:02] Nathan Wrigley: We talked about the Venn diagram of accessibility and usability, and the fact that there's a lot of an overlap. In the year 2025, this is a year where, in Europe at least anyway, accessibility, the legal cogs are turning and the screw is getting tighter. So accessibility is becoming mandated in many respects.

And I was wondering about that, whether there was any kind of overlap in legislation on the usability side. The accessibility piece is obviously easier to sort of define in many ways, and it's going to become less optional. But I was wondering if there was any usability legal requirements. I don't know quite how that would be encapsulated.

[00:35:41] Jo Minney: Sort of. An example that comes to mind is that there are a lot of practices that historically have been really prevalent on the internet, and they've been identified as being really bad for usability. And they've actually now been identified as being so bad that they're almost evil. And they've started to crack down on those.

And an example of that is, have you ever tried to unsubscribe from a gym? It's basically impossible. And so now if you, at least in Australia, I know if you have a subscription on your site, you legally have to have a way of people being able to unsubscribe without having to call someone or send an email somewhere.

And that is an example where that is actually usability. And I think there are definitely things where we are picking up on stuff that is maybe a shady way of working, and a shady way of developing websites. And those things are starting, we're starting to cut down on them.

I'm not sure if that is purely usability, or just like not being being a bad person. But I think that there is definitely, the only reason that we know that those things are a problem is because we have all had those bad experiences. And ultimately that's all user experience is, it's just how good or bad is experience of using a platform.

[00:36:49] Nathan Wrigley: I share your frustration with those kind of things because I've been through that process. Not just canceling a subscription but, I don't know, something that you've got yourself accidentally into and you don't want to be on that email list anymore. Seemingly no way to get off it.

[00:37:01] Jo Minney: They've changed the unsubscribe link so it doesn't have the word unsubscribe in it. And now you just have to look for the word that's not underlined, or highlighted in a different colour. That when you hover over it, something pops up and you're like, oh, that's the link. That thing that says manage preferences down the bottom, hidden in the wall of text. That is a shady practice. That is a poor user experience just as much as it's just a bad thing to do.

[00:37:23] Nathan Wrigley: I think it's got the label of deceptive design now. It used to be called dark patterns, didn't it? But deceptive design. This notion of doing things in such a way to just deliberately confuse the user so that the green big button, which is the exact opposite of what you want to click, is the one which is visible. And then there's this tiny little bit of greyed out text, which is the one which, clearly, you've ended up at this page, that's the one you want. That's the enemy of usability in a way. But for the business, it may be exactly what they want because it keeps the economic engine rolling.

Yeah, that's interesting. I wonder if there'll be more legislation to tighten those things up so that they're not allowed. Yeah, that's fascinating.

Last question. We're running out of time. Last question. And it refers to something that we talked about earlier. I'm guessing this really never ends. This is a journey which you begin, you tweak it, you do a little bit, you fix, and then you start again a little bit later and what have you. Is there ever a moment though where you go to a client and say, we did it? This site, as far as we're concerned, is now perfect. Or is it never a goal? It's a journey and never a destination.

[00:38:23] Jo Minney: I think you'll probably agree with me here, Nathan, that it's basically impossible to be perfect, because ultimately someone is always going to have a different opinion. Someone's always going to think that your shade of purple is too dark. Someone is always going to dislike the font that you chose, because it's not loopy enough, or it's too loopy, right?

So I don't think there is such a thing as perfect. But through doing five usability tests, five people, you can pick up at least 85% of the potential problems with your design. And I'm not aiming for perfect, but I know that for me, if I can confidently say to my customers that I've been able to identify 85% of the potential problems that they might experience in their project, then they can confidently go away and say, hey, we're pretty happy with what we've got.

We can definitely improve on that over time. But that is a huge milestone to be able to hit. And being able to have enough data, and enough research to confidently say that, I think is a really big win both for us and for our customers.

[00:39:26] Nathan Wrigley: Sadly, Jo, time is the enemy, and I feel like we've just pulled back the lid a teeny tiny bit on the big subject of usability. Honestly, I reckon I could talk for another two hours on this at least. You know, because you've got into colours there and all sorts, and there's just so many tendrils that we haven't been able to explore. But we've prized it open a little bit, and so hopefully the listener to this has become curious. If they have, where would they find you? What's a good place to discover you online?

[00:39:53] Jo Minney: Yeah, so I think the best place is to hit up my personal blog, jominney.com. So it's J O M I N N E Y .com. And I have a lot of stuff on there about usability, usability testing. I have a blog post that I wrote specifically for this talk that shares all of the resources that I used to put together the slides and everything. The talk itself will be on WordCamp TV. If you're on socials and you want to hit me up, pretty much the only platforms I'm active on nowadays are LinkedIn and Bluesky, and I'm Jo Minney on both of them.

[00:40:23] Nathan Wrigley: Jo Minney, thank you so much for chatting to me today. I really appreciate it.

[00:40:27] Jo Minney: You're most welcome, Nathan. Thanks for having me again.

Today, I bring you the first in a mini series of podcasts I recorded in person at WordCamp Asia in Manila. This flagship WordPress event brought together hundreds of WordPress professionals, enthusiasts and all manner of interested parties under one roof for a three day event - one contributor day, and two days of presentations.

I tracked down several of the speakers and workshop organisers, and recorded them speaking about the subject they were presenting upon. I hope that you enjoy what they have to say.

So on the podcast today we have the first of those conversations, and it's with Jo Minney.

Jo, based in Perth, Australia, is passionate about user experience, data-driven decision-making, cats, pockets and travel. She's a small business founder, and works with organisations creating digital platforms with WordPress. She also freelances as a UX consultant. She volunteers with Mission Digital to address social issues using technology, and is an ambassador for She Codes Australia, promoting tech accessibility for women. Recognised as a 2023 Shining Star by Women in Technology Western Australia, Jo is an international speaker on topics like user experience, accessibility, and gender equality. She's committed to ensuring a seamless user experience, and today shares her insights from practical, everyday usability testing.

Jo's presentation, entitled Budget-Friendly Usability Testing for WordPress helped attendees understand what usability testing is, x and clarified why it differs from other testing methods. She shares examples from her work, showing how small changes can significantly impact user experience, which is better for you, the website builder, and your client, the website owner.

We also discuss how usability testing can transform a website's effectiveness by improving conversions. Jo explains the importance of recruiting novice users for testing, and highlights how usability testing pushes for real, user-centered improvements.

Towards the end, Jo shares practical advice on when and how to integrate usability testing into your process, advocating for early and iterative testing to preemptively address potential issues.

If you're looking to gain a deeper understanding of usability testing and its benefits, this episode is for you.

Useful links

WordCamp Asia in Manila

Jo's WordCamp Asia 2025 presentation: Budget-Friendly Usability Testing for WordPress

InstaWP

Think Aloud Protocol

Jo Minney's website

Jo on Bluesky

26 Mar 2025 6:37pm GMT

Do The Woo Community: Building Trust and Converting Sales with Simple UX Decisions with Marc McDougall

In this episode of Woo DevChat, hosts discuss UX design and CRO with Marc McDougall, who shares insights on common misconceptions, mistakes, and the evolving role of AI in enhancing user experience.

26 Mar 2025 3:58pm GMT

Do The Woo Community: Get Ready for the Atarim Web Agency Summit 2025

The Atarim Web Agency Summit 2025, scheduled for April 7-11, is a free virtual event for web professionals. Featuring over 40 expert-led sessions, it offers actionable insights for agency growth, networking opportunities, and access to industry leaders. Registration is free, with replay options available, making it essential for anyone in the digital space.

26 Mar 2025 3:08pm GMT

HeroPress: With open arms – friendships in the WordPress community – Su atviromis rankomis – draugystės WordPress bendruomenėje

Pull Quote: I am truly thankful that the WordPress community has welcomed me with open arms.

Šį rašinį galima rasti ir lietuvių kalba.

Truth be told, unlike my husband, I have never been the most social person. At a party, you'll usually find me talking to the dog (or cat). Throughout my life, I've only had a few close friends, and I'd rather be reading a book than going to a concert. While WordPress has been a huge part of the growth of my business, I'd like to take this opportunity to discuss something much more important - the friendships that I have formed through this wonderful community.

Due to WordPress, I have some truly spectacular friends in my life.

While we may have started as strangers, we moved into attending each other's weddings, laughing until we're crying while packing hundreds of swag orders, holding hands in a hospital bed and being there for each other through thick and thin. Being a privacy lawyer, I won't name any names here but you'll probably be able to tell pretty quickly if I'm writing this about you.

A little backstory

When I was finishing up law school, I worked at a small web design agency in Chicago as their COO. I met my husband, Hans, who was the owner of a different agency when he came to buy us out. It was love at first sight (yes, really) and we have been inseparable ever since. We shared our struggles and annoyances over dinner one night - writing Privacy Policies for clients was monotonous for me and he had no idea what to do when a client asked him about website policies. So we created Termageddon - an auto-updating website policies solution for agencies and their clients. Since we started an agency partner program, we knew that we had to find agencies who would be willing to try our new product and that's when we came across WordCamps and the WordPress community.

Our first WordCamp

WordPress has a huge community and going to a large WordCamp such as WordCamp US when you don't know anyone can be really scary (especially for an introvert like me) so we thought that we'd get our feet wet with a smaller WordCamp nearby. Enter WordCamp Jackson, Michigan.

Driving into the most adorable small city that we have ever visited, we were very nervous - what if no one wanted to talk to us?

These fears were quickly dispelled when we walked into a room with about 30 friendly faces. Even the mayor was in attendance! During a break, we all sat on couches and our new friends helped us come up with the design for our very first swag item: a t-shirt with a pirate asking "Arrrr you compliant?". I still smile every time I put it on. The next thing we know, the informative presentations are over and we're all piling into cars and going to an escape room. The friendships formed during that event have lasted many years. In fact, one of our friends from that very first WordCamp helped us build our chicken coop.

Come on over!

A while later, my husband went to London and met a friend through a non-WordPress event and they truly hit it off (seriously, they have a standing call twice per month for five years now). A few months later, it was time for our first WordCamp US and our friend flew from the UK to Chicago to stay with us and our plan was to take a road trip and drive from our home to the WordCamp. Well, it just so happened that his other friend who was also going to WordCamp (someone we haven't met before), missed his flight. Our friend called us to explain the situation and asked whether he could change his flight to Chicago, stay with us and join our road trip. We said "come on over!" Well, that missed flight led to the best trip of all time and a lifelong friendship.

I'll always remember him walking me to the store to buy some tea on a cold evening, all of us posing for a picture next to the St. Louis arch, hanging out in various hotels and Airbnb's throughout the years, sharing stories from our youth, marveling at the excitement and joy of growing families, and supporting each other's business ventures. We've seen each other many times throughout the years on various trips and WordCamps and I think of us as our core group at these events - a safe space amidst all of the chaos.

Better together

When you start establishing yourself in an industry or a community, you may think of other people in the space as competitors. While it's certainly not the best trait that humanity has to offer, I think that this happens more frequently than we would like to admit. When I was new in the WordPress community, there was an established privacy attorney who had been a part of that community for much longer than I have. Going to WordCamp US, I knew that she was going to be giving a speech on the California Consumer Privacy Act and how to comply with this privacy law. To be honest with myself and you, I was extremely nervous about meeting her. What if she thought that I was a competitor? What if she disliked me? What if there's not enough room for two privacy lawyers at this event? Should I just hide throughout the entire event to make sure that she doesn't see me?

It's true that we create these extreme scenarios in our minds but reality is usually much different (and less scary). We quickly bonded over the fact that we were the only two people there who knew what CCPA even is and, by the end of the night, we were jammed together in an Uber going to a bar. Throughout the years, we have supported each other's projects, participated in long evenings of conversations, shared our struggles and wins. Due to her kindness and welcoming nature, we did not head towards competition but are able to enjoy the benefits of a wonderful symbiosis and a true friendship.

Family for life

Hanging out with your friends at WordCamps is fun but it's even more fun when your friendship progresses to the point where your friends fly over to hang out at your home. Well, in this case, we only got to hang out for one day before my friend got very sick. Not the "I have the flu" kind of sick, the over a week in the ICU and months in the hospital kind of sick.

Throughout that time, we met her family, who stayed with us for a while as we live very close to the hospital. While this time was certainly grueling for everyone involved, it also shed a new perspective on how friends get through tough times. Whether it was rides to the hospital, sitting together, crying together, making home cooked meals, celebrating every win, no matter how small, the friendship, the community, and the knowledge that we were there for each other let us make it through this difficult time. The day that she got out of the hospital was truly miraculous.

And now, we are most certainly not just WordCamp friends, we're family - for life.

The little things

Up to this point in my life, I have been a part of many communities - from school, to dance groups, to attorney associations, to my local neighborhood, each community has had something special to offer. However, I have never been involved with another community that is as welcoming or that has led to the formation of so many wonderful friendships as WordPress. From sharing a beer (or a boot of beer), to attending our wedding through Zoom (2020), to making a flower crown, to eating so much sushi that I could barely walk back to the Airbnb, to corn mazes and petting zoos, and touring a submarine together, I am truly thankful that the WordPress community has welcomed me with open arms and I hope that I can do the same for others!

Donata's Work Environment

We asked Donata for a view of her office this is what she sent!

Donata Stroink-Skillrud’s Desk

HeroPress would like to thank Draw Attention for their donation of the plugin to make this interactive image!

Su atviromis rankomis - draugystės WordPress bendruomenėje

Tiesą sakant, kitaip nei mano vyras, niekada nebuvau pati socialiausia asmenybė. Vakarėlyje mane dažniausiai rastumėte kalbančią su šunimi (ar kate). Visą savo gyvenimą turėjau tik keletą artimų draugų, o knygos skaitymas man visada buvo malonesnis nei koncerto lankymas. Nors WordPress atliko didžiulį vaidmenį plėtojant mano verslą, norėčiau pasinaudoti šia proga ir pakalbėti apie kai ką daug svarbesnio - draugystes, kurias užmezgiau šioje nuostabioje bendruomenėje.

Dėl WordPress turiu iš tiesų nuostabių draugų savo gyvenime.

Nors pradėjome kaip svetimi, mes tapome tais, kurie dalyvauja vienas kito vestuvėse, juokiasi iki ašarų pakuodami šimtus reklaminių dovanų, laiko vienas kitam ranką ligonines lovoje ir būna kartu per storą ir ploną. Kadangi esu privatumo teisininkė, nemininesiu vardų, tačiau tikriausiai greitai suprasite, jei rašau apie jus.

Trumpa istorija

Kai baiginėjau teisės studijas, dirbau mažoje interneto dizaino agentūroje Čikagoje kaip COO. Ten sutikau savo vyrą Hansą, kuris buvo kitos agentūros savininkas, kai jis atvyko mus nupirkti. Tai buvo meilė iš pirmo žvilgsnio (taip, tikrai), ir nuo to laiko mes esame neatskiriami. Vieną vakarą dalinomės savo sunkumais ir nepasitenkinimais - man buvo nuobodu rašyti privatumo politikos dokumentus klientams, o jis net nežinojo, ką daryti, kai klientas paprašydavo interneto svetainės politikos. Taip gimė Termageddon - automatiškai atnaujinamas interneto svetainių politikos sprendimas agentūroms ir jų klientams. Kadangi pradėjome agentūrų partnerių programą, turėjome rasti agentūras, kurios būtų pasiruošusios išbandyti mūsų naują produktą, ir tada mes atradome WordCamps ir WordPress bendruomenę.

Mūsų pirmasis WordCamp

WordPress turi didžiulę bendruomenę, o vykstant į didelį WordCamp renginį, pavyzdžiui, WordCamp US, kai nieko nepažįsti, gali būti labai baisu (ypač tokiai intravertei kaip aš), todėl nusprendėme pradėti nuo mažesnio WordCamp netoli mūsų. Taip mes atsidūrėme WordCamp Jackson, Mičiganas.

Važiuodami į vieną mieliausių mažų miestelių, kokius tik esame matę, labai nervinomės - o kas bus jei niekas nenorės su mumis kalbėtis?

Šios baimės greitai išnyko, kai įėjome į kambarį su maždaug 30 draugiškų veidų. Netgi miesto meras dalyvavo! Per pertrauką visi susėdome ant sofų, o naujieji draugai padėjo mums sukurti mūsų pirmojo reklaminių dovanų daikto dizainą: marškinėlius su piratu, klausiančiu "Arrrr you compliant?" (Ar esate atitinkantys?). Vis dar šypsausi, kai juos apsivelku. Nespėjome apsidairyti, o jau po naudingų pranešimų visi susėdome į automobilius ir vykome į pabėgimo kambarį. Draugystės, užmezgtos šio renginio metu, tęsiasi jau daugelį metų. Tiesą sakant, vienas iš mūsų draugų iš to pirmojo WordCamp padėjo mums pastatyti vištų tvartą.

Užeikit!

Kiek vėliau mano vyras išvyko į Londoną ir susipažino su draugu per ne-WordPress renginį, ir jie tikrai susidraugavo (rimtai, jie kalbasi kas dvi savaites jau penkerius metus). Po kelių mėnesių atėjo metas mūsų pirmajam WordCamp US, ir mūsų draugas nuskrido iš JK į Čikagą, kad apsistotų pas mus, o mūsų planas buvo keliauti automobiliu nuo namų iki WordCamp. Tačiau nutiko taip, kad jo kitas draugas, kuris taip pat vyko į WordCamp (mes jo dar nebuvome sutikę), praleido savo skrydį. Mūsų draugas paskambino mums, paaiškino situaciją ir paklausė, ar jo draugas gali pakeisti skrydį į Čikagą, apsistoti pas mus ir prisijungti prie mūsų kelionės. Mes pasakėme: "Užeikit!" Tas praleistas skrydis privedė prie geriausios kelionės gyvenime ir viso gyvenimo draugystės.

Aš visada prisiminsiu, kaip jis lydėjo mane į parduotuvę nusipirkti arbatos šaltą vakarą, kaip visi kartu pozavome nuotraukai prie Saint Louis arkinio paminklo, kaip per daugelį metų leisdavome laiką įvairiuose viešbučiuose ir Airbnb, dalijomės jaunystės istorijomis, stebėjomės augančių šeimų džiaugsmu ir jauduliu bei palaikėme vieni kitų verslo sumanymus. Per daugelį metų matėmės daugybę kartų įvairių kelionių ir WordCamp renginių metu, ir aš mus laikau pagrindine grupe šiuose renginiuose - saugia vieta viso šurmulio apsuptyje.

Geriau kartu

Kai pradedate įsitvirtinti tam tikroje pramonėje ar bendruomenėje, galite pagalvoti, kad kiti žmonės šioje srityje yra konkurentai. Nors tai tikrai nėra geriausia žmonijos savybė, manau, kad taip nutinka dažniau, nei norėtume pripažinti. Kai buvau naujokė WordPress bendruomenėje, buvo viena pripažinta privatumo teisininkė, kuri buvo šios bendruomenės dalis daug ilgiau nei aš. Važiuodama į WordCamp US, žinojau kad ji ketina skaityti pranešimą apie Kalifornijos vartotojų privatumo įstatymą (CCPA) ir kaip laikytis šio privatumo įstatymo. Būsiu atvira - man buvo labai neramu ją sutikti. O kas, jei ji manytų, kad esu konkurentė? O jei jai nepatikčiau? O jei šiame renginyje nepakaktų vietos dviem privatumo teisininkėms? Gal man geriau viso renginio metu slėptis, kad tik ji manęs nepastebėtų?

Tiesa ta, kad dažnai kuriame kraštutinius scenarijus savo galvose, bet realybė dažniausiai būna visai kitokia (ir mažiau bauginanti). Greitai susidraugavome, nes supratome, kad esame vienintelės dvi moterys renginyje, kurios iš viso žinojo kas yra CCPA. Vakaro pabaigoje jau spraudėmės kartu į Uber važiuodamos į barą. Per tuos metus palaikėme viena kitos projektus, dalijomės ilgais pokalbiais vakarais, kartu išgyvenome sunkumus ir džiaugėmės pasiekimais. Dėl jos geranoriškumo ir svetingumo nepasukome konkurencijos keliu, o galėjome džiaugtis nuostabia simbioze ir tikra draugyste.

Šeima visam gyvenimui

Leisti laiką su draugais "WordCamp" renginiuose yra smagu, bet dar smagiau, kai draugystė tampa tokia stipri, kad draugai atskrenda pas jus tiesiog pabūti kartu. Na, šiuo atveju, mes spėjome pabūti tik vieną dieną, kol mano draugė labai susirgo. Ne "turiu gripą" lygio susirgo, o taip, kad teko praleisti daugiau nei savaitę reanimacijoje ir kelis mėnesius ligoninėje.

Tuo sunkiu metu susipažinome su jos šeima, kuri kurį laiką gyveno pas mus, nes gyvename labai arti ligoninės. Nors šis laikotarpis tikrai buvo alinantis visiems, jis taip pat suteikė naują perspektyvą, kaip draugai išgyvena sunkius laikus kartu. Nesvarbu, ar tai buvo kelionės į ligoninę, sėdėjimas kartu, verksmas kartu, naminiai patiekalai ar kiekvienos, net ir mažiausios pergalės šventimas - draugystė, bendruomenė ir žinojimas, kad esame vieni kitiems, padėjo mums išgyventi šį sunkų laikotarpį. Diena, kai ji išėjo iš ligoninės, buvo tikras stebuklas.

Dabar mes tikrai ne tik WordCamp draugės - mes šeima visam gyvenimui.

Mažos smulkmenos

Iki šiol mano gyvenime buvo daugybė bendruomenių - nuo mokyklos, šokių grupių, teisininkų asociacijų iki mano vietinės kaimynystės - kiekviena bendruomenė turėjo ką nors ypatingo. Tačiau niekada nebuvau dalis kitos bendruomenės, kuri būtų tokia svetinga ir kuri būtų padovanojusi tiek daug nuostabių draugysčių kaip WordPress. Nuo alaus bokalo (arba alaus bato) dalijimosi, iki mūsų vestuvių stebėjimo per Zoom (2020 m.), iki gėlių vainikų pynimo, iki tiek daug sušio valgymo, kad vos galėjau pareiti atgal į "Airbnb", iki kukurūzų labirintų ir gyvūnų ūkių lankymo, ir net povandeninio laivo ekskursijos - esu nuoširdžiai dėkinga, kad WordPress bendruomenė mane priėmė atviromis rankomis, ir tikiuosi, kad galėsiu padaryti tą patį kitiems!

The post With open arms - friendships in the WordPress community - Su atviromis rankomis - draugystės WordPress bendruomenėje appeared first on HeroPress.

26 Mar 2025 1:00am GMT

25 Mar 2025

feedWordPress Planet

WordPress.org blog: WordPress 6.8 Release Candidate 1

The first Release Candidate ("RC1") for WordPress 6.8 is ready for download and testing!

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it's recommended that you evaluate RC1 on a test server and site.

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.8 is the best it can be.

You can test WordPress 6.8 RC1 in four ways:

Plugin Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the "Bleeding edge" channel and "Beta/RC Only" stream).
Direct Download Download the RC1 version (zip) and install it on a WordPress website.
Command Line Use the following WP-CLI command: wp core update --version=6.8-RC1
WordPress Playground Use the 6.8 RC1 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.

The current target for the WordPress 6.8 release is April 15, 2025. Get an overview of the 6.8 release cycle, and check the Make WordPress Core blog for 6.8-related posts in the coming weeks for further details.

What's in WordPress 6.8 RC1?

Get a recap of WordPress 6.8's highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since Beta 3, you can browse the following links:

Want to look deeper into the details and technical notes for this release? These recent posts cover some of the latest updates:

How you can contribute

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world's most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is critical to ensuring WordPress is performant and stable. It's also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.8. For those new to testing, follow this general testing guide for more details on getting set up.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Search for vulnerabilities

From now until the final release of WordPress 6.8 (scheduled for April 15, 2025), the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project's security practices and policies outlined on the HackerOne page and in the security white paper.

Update your theme or plugin

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

Thanks for continuing to test your themes and plugins with the WordPress 6.8 beta releases. With RC1, you'll want to conclude your testing and update the "Tested up to" version in your plugin's readme file to 6.8.

If you find compatibility issues, please post detailed information to the support forum.

Help translate WordPress

Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? You can help translate WordPress into more than 100 languages. This release milestone (RC1) also marks the hard string freeze point of the 6.8 release cycle.

An RC1 haiku

March fades, nearly there,
Six-eight hums-a steady beat,
RC greets the world.

Thank you to the following contributors for collaborating on this post: @joemcgill @benjamin_zekavica @courane01 @mkrndmane @audrasjb @areziaal @ankit-k-gupta @krupajnanda @bph.

25 Mar 2025 4:19pm GMT

Do The Woo Community: A Continued Saga About the Life of Blog Posts

BobWP chats about the importance of adding content instead of removing it, expressing commitment to producing more podcasts, videos, and blog posts despite claims of blog irrelevance, valuing audience engagement over metrics.

25 Mar 2025 1:01pm GMT

Do The Woo Community: On the Floor at CloudFest 2025 with Adam Weeks and Christian Taylor

Adam Weeks and Christian Taylor explore CloudFest, assessing booth designs and marketing strategies. They discuss visual engagement, effective messaging, and the significance of interactive experiences in attracting attendees.

25 Mar 2025 7:46am GMT