04 Feb 2025

feedWordPress Planet

Akismet: Version 5.3.6 of the Akismet WordPress plugin is available now

Version 5.3.6 of the Akismet plugin for WordPress is now available. This update contains the following improvements:

To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins directory.

04 Feb 2025 9:11pm GMT

Do The Woo Community: Balancing Features and Focus: Avoiding Feature Creep with Bryce Adams

In this episode, Katie and Adam discuss feature creep in product development with guest Bryce Adams. They address balancing new features with core integrity and engaging customer support effectively.

04 Feb 2025 4:28pm GMT

03 Feb 2025

feedWordPress Planet

Do The Woo Community: Marketing Across the Stages of Your Woo Biz with Emma Young and Adam Weeks

In this episode, Emma and Adam discuss marketing strategies across business stages, emphasizing the importance of owned, earned, and paid media, audience understanding, and confident branding.

03 Feb 2025 1:54pm GMT

02 Feb 2025

feedWordPress Planet

Gutenberg Times: Gutenberg Changelog #114 – Reflections on Gutenberg Times and Do the Woo

As Gutenberg Times celebrates its 7th anniversary, we discovered an amazing coincidence: Bob Dunn, better known as BobWP, launched the DoTheWoo network in the exact same week back in 2018. Today, Bob and I take you behind the scenes to share the origin stories of our WordPress journeys, explore how key ideas took shape, and reveal the unexpected lessons we learned along the way.Today, Bob Dunn is the host, and I am Bob's guest.

Show Notes / Transcript

Show Notes

Stay in Touch

Transcript

**BobWP:**

Well, I'm here with one of my favorite people in the WordPress world. Well, actually outside WordPress. You may know her from Gutenberg Times. How are you doing today?

**Birgit:**

Well, hey, Bob. Oh, that's so sweet. Yeah, well, I remember that we did some luncheon in Torino, and there was outside the workroom, we were talking about so many other things. Yeah, well, I'm really glad that we can do the show together.

**BobWP:**

Yeah. So I happen to see, and I don't know if you had mentioned it somewhere or something, and I saw that you were coming up on seven years or something like that. And I thought, well, I wonder when that is. And it was in January, the same as what we've just celebrated. So I thought, wow. Then we can say 14 years combined. It sounds even more impressive.

**Birgit:**

Well, and if you do it times three, seven times three, it's 21. That's WordPress celebration. Yes, it's the 21st.

**BobWP:**

So I just thought we'd get on here and talk a little bit about, I don't want to go into the whole journey, but some of the things maybe we've learned or whatever along the way. And I always wonder when somebody comes up with something, is it more or less a name that comes across in your brain, you think, oh, you just think of this and you wonder what I could do with that? Or is it a concept you have? I want to start this. I want to know which way you did it, and if it was what you wanted to do first-the concept of the idea-and then how did you come up with the name? Was it easy to come up with?

**Birgit:**

Well, yeah. So I started at the end of June 2017 to curate news about this new thing that everybody hated-kind of the block editor. And I said, it can't be that everybody hates it, but it's really amazing and it's going to be changing WordPress so much. And I saw it at WordCamp Europe in Paris, and it was kind of a really great-it wasn't a live demonstration; it was just kind of a video showing how you do blocks and how you can add 'em to a post and all that. It was very early on. I think the first Gutenberg commit on GitHub was just in February, four months earlier. So it wasn't really, but it was absolutely fascinating to me. And I wanted to learn what other people do with it, what the plugin developers-if they are interested in it-what they're talking about, what the developers are talking about, and where this is going and what the new features are. And I was really trying it out and seeing what's coming up, and I wanted other people to know about it.

So I put a Storyfy out. I dunno if some of you might remember Storyfy. That's kind of a curation tool where you can embed things like posts and pictures and have just a running list of things. And that was very easy to do. And just when they published a blog post or showed off one of the little things that they found cool about the block editor or where a new feature was showcased, I just put it into the Storyfy. And there was up until probably October of 2017, and then I heard the news: Adobe had bought Storyfy and announced that they would end its life in May of 2018.

I said, well, I'm not going to wait that long. I need to put it on a website. Well, I'm a web developer. There was this fun thing, WordPress; I should use that. It's kind of the first one of many lessons I learned: that you have to put it on your own grounds and not do it on rented land.

So I thought about it, and then I also had some requests from users in the space that they would like to have a newsletter-like an email newsletter that comes every week or something like that-because they cannot always go to a page. It's just something new, typical publishing problems that people are not coming to your website to see what's new. You need to pull 'em over there. And so that was kind of the thing that came together.

Because it was all about Gutenberg, I kind of just thought about, okay, what are names of things? And Gutenberg Times came up. Somebody else at the same time had a Gutenberg Hub-that was Munir Kamal-and then there were other people out there. But I really liked the Gutenberg Times kind of name, and it was available. So I registered it in January of 2018, and that's how it came about. Then I migrated all the Storyfy updates into the site, and it took a while and I had some people to help me with that. And then I started the newsletter. It was actually pretty easy to kind of follow along because it was kind of that vision that I had.

**BobWP:**

Yeah, for sure. Mine was kind of erratic when I started focusing. I think I actually dabbled in WooCommerce when it first came out-2011 or something like that. I think it was 2011, I'm pretty sure. Anyway, so I was writing a lot of stuff about it. I actually found on my blog, when I was more into affiliates, people were more willing to buy and spend for their e-commerce site on the plugin. So I just started writing about it, and I did a podcast in 2014 for a little over a year called *The WordPress Breakdown*.

**Birgit:**

What?

**BobWP:**

*The WordPress Breakdown.* And I did it with kind of a twist on words. I was breaking down stuff, but then some of them had a WordPress breakdown.

**Birgit:**

Yeah, it's troubleshooting.

**BobWP:**

And what I did basically was I was just doing 15-20 minute podcasts with just myself. I was talking about plugins or themes and stuff like that-some of the stuff I came across. I did it for, like I said, about 13 or 14 months. And it was just becoming… I just felt like this is boring. I'm on there by myself. I'm talking about this stuff, and it's really stuff I'm already writing about, and I'm just kind of regurgitating it now through a microphone. And I thought, okay, I'm just going to quit it. I stopped it and I told myself that I wouldn't start something until I had a really good idea.

So in 2016, I thought of *Do the Woo*. I thought, okay, what's out there in the landscape? What would be good to talk about? And I thought, well, there's really nothing that focused on WooCommerce. And I knew the team there. I knew a lot about it. And so I thought, well, why don't I go ahead? I got the name. It was one of those things-I wanted something a little bit fun.

**Birgit:**

Yeah, definitely it is. But it's also that creation in there-*Do the Woo.* I really love it.

**BobWP:**

And so the name just came to me. So I contacted WooCommerce and I said, "I want to do this. Is it cool to have Woo in the name?" And so we kind of verbally agreed on it. And so I started that. And about three or four episodes into it, I thought, well, is there enough to talk about with just WooCommerce right now? So I actually changed it to *The WP eCommerce Show* and ran that for two to three years, did quite a bit with that. So I was talking about a lot of stuff, and it was a lot of Woo in it.

Then in 2018, I decided to kick *Do the Woo* back up in January, and I was actually doing both podcasts at the same time. And it just was becoming too much. So I said, I've got to drop one of these. And the WP eCommerce seemed like the one to drop. And so I just took off with *Do the Woo* again. And by episode-I was just saying on the episode before we started doing this one-I think it was episode five, I had Brad Williams come in as co-host because I realized I needed a co-host. It was more fun, whether we have a guest or not. And then it just kind of went from there.

And the interesting thing is, when I actually came up with the site itself, what, two, three years ago? Whenever. Because it was all done under BobWP.

**Birgit:**

There…

**BobWP:**

At that point, I wanted to get the domain, and *Do the Woo.io* was available. So I went back to Woo and I said, I wanted to buy this domain, but I'm stepping into another space here as far as having that in a domain. And so they said, "What was the agreement before?" And I can't remember who it was at Woo, but we made an agreement-basically a verbal agreement-and they were cool with it and everything. But then when, like I said, I got the domain, it became a little bit more of a legal thing. So I negotiated with their attorney. They came up with a contract and something that was an agreement of what I could or couldn't do, or should or shouldn't do, or something like that. And it was perfectly fine. It was great. So I signed that, and then I was able to use that for the domain.

**Birgit:**

It's quite the journey.

**BobWP:**

Yeah, yeah. Well, you know me too well. My journeys are never nice, straight, narrow journeys with nothing happening.

**Birgit:**

Nice, quiet, but that's perfectly okay. You need to stay in the moment, and then all of a sudden creativity strikes.

It was, so in April of 2019, I started thinking… I had a podcast in the nonprofit space. So all my life before that was nonprofit space. I had just founded three years earlier a nonprofit technology company-a 501(c)(3)-to help nonprofits with technology because the social justice people are not equipped in doing technology. It's all self-taught, and they needed a little bit more strategic approach to it. And I was really helping, trying to help with that. And I had a show called *What's New in NP Tech*, with Ruth, a co-host, and Jim O'Reilly. And he had this wonderful radio voice as well, and he was very polished.

I'm more about talking off the cuff, starting sentences and never finishing them. And he was very polished. So it was a very good contrast. And I said, okay. And in 2018, he had to stop doing the podcast. And by 2019, I was missing that energy-that you have somebody to talk through things and what's new and what you want to kind of try out and what's the purpose of it, then why that and not that?

So I thought, okay, Gutenberg has a two-week release cycle, and every time there's so much in it beyond what's in the release post. In the release post, the release lead-whoever leads it-highlights six, four, or five things, but there's so much other stuff in there that might be good for developers or theme builders. So I talked with a design director from Automattic at that point, and asked if he would spend every two weeks, two and a half hours or something like that, on our changelog. We'd go through the changelog, highlight things that we want to talk about that are very important, and talk about more than the six things that are highlighted in the release post.

**Birgit:**

And that was really fantastic to put it together. We had a certain rhythm to it; we had a certain outline. We also talked about what other people do in the space-if there was a great plugin coming along or a question from listeners. So that was really a great start. We started-I think the first, the zero episode-was in June 2019.

Since then, I've had a most regular biweekly kind of rhythm. Mark Re did about 40 episodes with me, and then he left Automattic-that was, I think, December 2020 or something like that, after a year of the pandemic kind of thing, or January. And then Greg Ziolkowski from Poland, who was also a Gutenberg developer, kind of came on for another 25 shows or 20 shows.

And then I started to rotate co-hosts, and that made it much more fun to think about what other people are doing in this space. Can I bring that into the show and still talk about the changelogs? Yeah. We had Tammie Lister and Fabian Kägy, Ryan Welcher, Nick Diego, or Peter Tasker. One show was actually also with Mathias Ventura when he had this new phase of the site editor to announce.

And with all the phases in Gutenberg, we always had something to talk about. And it was funny-this friend with whom I did the previous podcast, he's still a very good friend of mine-and he kind of had the question for me: "So you call it the Gutenberg Times, so when Gutenberg is done, what do you do then?"

And I said, well, once Gutenberg is merged to Core, wouldn't your site be completely obsolete? I said, no, I don't think so. There are a lot of other things that are going to come along. But it was really interesting to see how that, in other people's minds, kind of made it, okay, it's done now. But we all know it's not done.

In December 2018, it came into Core. And what are we now, 2025? And we are still working on phase three of the Gutenberg project. So it was kind of interesting to see.

**BobWP:**

Yeah, I think a lot of people, they think of not an end in sight, but they don't think of how to now twist it to this way or twist it to that way. Some people are very, I'm going to go to this point, and then this is the point I feel like there's nothing else to be said, at least from my perspective.

But you're like me. I mean, when I had Brad come on-I don't know how long it was just Brad and me-and then I had Jonathan Wold and Mendel Kurland from GoDaddy back then. They came on. So we started rotating because, again, like you said, it was fun. And then we were bringing in guests too.

And then just after a while, I started thinking, well, could I build on this? And the more I got into it, the less I wanted to be on the podcast. I just thought-because it started coming to the point where it was, yeah, we're talking about this and that and all these different things-but also I was seeing people that come on a podcast for the first time as a guest and, after, I mean, they were freaking out at the beginning. But then at the end, or later on, they said, "Wow, that was so much fun and stuff." And I thought, well, I'd like to get more other voices and have other people talk about stuff, and pick out hosts to have their own specialty and their own knowledge and stuff.

So it's been kind of crazy. Some people look at me like…

**Birgit:**

Yeah. When did you start with the network of shows? Was that two years ago? Three years?

**BobWP:**

Brad came on. Then, on January 9th, 2020, I brought Jonathan in, and Mendel came in. And then, I think it was January 30th, 2021, I brought Zach in, and Ronald joined. Then after that, I just kept thinking, how far can I take this?

And then, I think it was when I actually launched it as its own site. I had somebody design it. And then after about two years of that, I started doing some other stuff, and I thought, I want to make this more of a-I want to call it, I don't really know-a network, but a collection of shows with all these different people. So then I had to look at redesigning everything.

But yeah, it was just… for me, I mean, I'm at a point where I've got to kind of just deal with what I have here now. And all the hosts are volunteers, so they always know. We've had a few that have had to leave for one reason or another. They're getting busy with their business, and they just said, I don't have the bandwidth anymore. And I say…

**BobWP:**

Thank you for what you've done. And I have a hall of fame on my post page and stuff for those that were on before and moved on. So it's been very flexible with them, scheduling everything. Everybody's busy and stuff, so we just kind of deal with stuff. We get things all scheduled in for a year, but then we move things around and people have times they can't show up. Sometimes it's a little crazy, but they all seem to enjoy doing it, and I'm lucky for that.

**Birgit:**

Yeah, I have started rotating through. Well, I started to see, okay, the WordPress space is still a little bit more male-oriented, and I see it also in my audiences. Yeah, it's all 65% male, between 35 and older, or it's 80% on the podcast. I said, well, I guess I'm in a situation where I can actually also bring some more female voices, especially female engineer voices, to the space.

And it's a real joy for me to work with the engineers at Automattic, or other agencies, or other hosting companies. And I kind of want the person who comes on to not only be a one-time guest-if they want to, that's okay-but if they are on multiple times, they get their own routine for that. And it's much easier for them to say yes now than for the first time when they don't really know what to expect.

So I am really happy to have about 10 to 12 women engineers that kind of rotate through. Most of them are actually in the community. They're all very knowledgeable about the subject anyway, but then they've also put in the grind in theme development or plugin development.

So it's really interesting to see what they do, and they bring a different perspective to the whole thing. When I was having a conversation with Greg, who is on the development team, I said, well, I could bring the user questions. What were you thinking? And then he would explain it quite nicely, and I learned a lot when talking with the volunteers-what software development is actually about. It's… you have the architecture, but there's so much behind the scenes that you can't bring to the forefront. And if somebody says to content creators, it's just, "What? Just change?" If I hear somebody say, "Well, it's just an easy fix…" Yeah, that was kind of…

**BobWP:**

What?

**Birgit:**

…what I had when I was running my agency. It was never just an easy fix.

**BobWP:**

Never.

**Birgit:**

It's always more. Yeah. So it's interesting to see and bring other voices in there.

**BobWP:**

Yeah. Yeah, definitely. I know for me, the hosting has always been… I try to keep some kind of balance in some way, but I'm also asking-the person has to be willing to commit. Somebody. I've approached a lot of different people, and a lot of people just don't have the time to commit or they just don't. And also, it does take a certain comfort level to be a host. I mean, you want to be able to do it.

And if you're almost on the edge just going in as a guest-I mean, I give them the benefit of the doubt. Some of them have come in a little bit reluctant, and they ended up just loving doing it after a bit. So it's kind of… And yeah, it's good. All the different voices. I mean, I've had a lot of guests on. I swear that probably 65%, 70%, or maybe it's higher-I don't know-are first-time podcast guests. They've never been on. And sometimes I have to talk them into it a little bit, and often they're surprised how much they can talk when they don't think they can, and they get going.

**Birgit:**

Yeah, it really depends on the questions.

**BobWP:**

Yeah, for sure.

Want to be a hero when it comes to your clients? You've built a site, and now you want to make sure that with your client's Woo shop, they are ensured that they have accurate sales tax rates in place, especially in case of an audit. Avalara is a leader in automating sales tax and compliance for businesses selling online, both big and small.

If you're setting up a new WooCommerce site, get your client set for sales. If you currently manage several client sites, it may be time to make that recommendation. Either way, get their WooCommerce extension and let your clients take advantage of a 60-day free trial. There are also great resources for either you or your clients on their site, where you can learn more about sales tax calculation, among other services like returns and exemptions. So for peace of mind, Avalara.com has you covered.

**Birgit:**

I have found that everybody brings something to it, and even if they're missing knowledge, you can fill that in a conversation. It fills knowledge gaps for other people who are listening. And so I always have appreciation for things that don't go well because those are the most important moments when you learn things.

**BobWP:**

Yeah.

**Birgit:**

Exactly. And I never really had anything that didn't go well. Sometimes it was just… yeah, we had one the other day where we had 20… that's a horror story. If you have a rundown that's 29 pages because you have a changelog from three plugin releases because you had a holiday break.

**BobWP:**

Oh, geez.

**Birgit:**

Yeah. That is kind of the horror story where you say, okay, you need a special guest for that, who deals with that. And even then, you sometimes get lost. Am I on page 15 or 25? Where am I? Because you scroll so fast. Yeah, we cut that out and regrouped and then came back to it. So it's great.

**BobWP:**

I had somebody… a couple of times this happened. One of the guests didn't get recorded in the track. It just wasn't there. It looked like it was recording and everything. So when I went to play it back, they were out.

**BobWP:**

It looked like it was recording and everything. So when I went to play it back, they were out. And I believe one time, one of the hosts actually said, "Well, send me the episode, and I'll fill in those spots. I'll listen to it, and then I'll reply, and then I'll see what I asked next." And they did it, and it worked fine, but it was a nightmare for them. Then I had to go in and put everything in.

But I did have a guest once, and I felt so sorry for them. We don't do a lot of upfront questions on ours, and sometimes people will request it. And this plugin developer was really pretty nervous about being on. So I said, "Well, let me send you a few questions about what I'll talk about." Well, I could tell even when we started, it wasn't for them.

**Birgit:**

So brilliant.

**BobWP:**

And I always tell my guests, if you need to start over on something, it's recorded. So I'm not live. I can go in and edit. And this poor person actually had created the answers for all the questions and was reading them. But he was so nervous that when he was reading them, he kept stopping and saying, "Oh, I got to start over." And I could just feel his tenseness. And I wanted to say, if this isn't comfortable, but then I didn't want to. So we did it. I went in and did some editing, and it turned out fine, but I felt for him.

I thought, oh, I know that feeling when you think something might be easier for you or something, and you get in there and you just don't have it in you or something. And I don't blame them. There are a lot of people that just refuse to come on the podcast. They'll just say, "Ah, no, I can't do it." And I'm like, "Yeah, cool."

**Birgit:**

Yeah, I take that no very seriously because you don't want to… yeah. But the other part was the horror stories only start when I screw up.

**BobWP:**

Yeah, that's when I did.

**Birgit:**

So at the beginning, I think I missed the record button with my mouse, and we had to do the show again.

**BobWP:**

I had one of those.

**Birgit:**

I think everybody has. But I have a very good editor who goes through that. She's been a radio producer all her life, and she helps me with that. So now I just kind of record and record on QuickTime as a backup. So even if I screw up the Zoom recording… but now with Zoom, you actually get two tracks. And that's really helpful because sometimes we just talk over each other. It happens when you're in the moment and you want to-it's something you're excited about-then you talk over each other, and it's hard.

**BobWP:**

I have a few people that have been that stuck almost. And I'll shift tracks, then I shift them and stuff. And I did have the one that I forgot to record-it was when I was doing my other e-commerce podcast. And she ran this company that sold cosmetics, and she was in Ghana. And it was just-she had a Woo online store. That's why I brought her on. But she would give jobs to local women to go out because they would have to get the ingredients for it. So she provided jobs for a lot of the women there.

It was a fascinating story, and I finally was able to get her on. And the most embarrassing thing is when you find out in the middle-I looked down, I thought, wow, that record button isn't going. And I thought, now I have to tell her this right in the middle. Which is… I don't know what's worse: going through the whole thing and then saying, "Oh, sorry, it didn't record." So I kind of paused. I said, "Well, I have an interesting situation here. Obviously, I didn't push the record button." And she actually laughed, and she said, "Well, go ahead. We can do it again. Just send me your calendar again." And she was real cool about it, but my heart just sunk.

**Birgit:**

Yeah, imagine no recording, especially when it was a good show and there was a good groove, and then all of a sudden I destroyed it. Oh, man.

**BobWP:**

It's interesting too because some people, when you were talking about somebody asking, "Well, what about when it goes into Core and the goal's over?" It sounds like you've been through a lot. I have been over the seven years. You flex with whatever works. It's like, okay, is this going to continue? Yeah, well, I can continue it.

And you've tried different hosts and you've found that sweet spot. So I think both of us-I was going to ask about, did they ever change for our sites during the seven years? And they probably did in the sense that, yeah, we shifted to this a bit and nothing real maybe. I know that when I moved it to its own domain and kind of focused more on the bigger group of hosts, that was probably a big shift. But it was in my brain for nine months. I was working on stuff.

**Birgit:**

Well, there wasn't really a big shift. So I think I changed the theme once, and it's definitely overdue for a new one because I'm still on a classic theme and I should go on a block theme because then you can do a lot more. But I just didn't have the time yet to migrate over.

**Birgit:**

But I think I'm also… up until 2021, in summer 2021, it was all a hobby kind of thing. I did it alongside my agency work, and it was up and down in terms of how much time I could spend there. During the pandemic, I had about six-well, four-months of burnout because I had so much work to do, and I didn't have a break. I had to take my break.

And the only thing that I did during that break was keeping up with Gutenberg, keeping the Weekend Edition going, and keeping the podcast going. But I wasn't doing any agency work. The developers and freelancers that I worked with-they were so good at taking over. I said, "I can't deal with it, and if I have to step in, I'll step in. But you know how we work." And they were all many years with me.

So it was between November 2020 and February 2021. I was only doing the Gutenberg Times, and I was really amazed to see how that always kept my excitement going. And there's a lot of personal stuff that got in the way afterward. So we moved to Sarasota; we sold the house in Naples, renovated the house. There was a lot of non-work and non-publishing kind of stuff getting in the way.

Then we organized our house in Sarasota, and after two years of not seeing our parents, we traveled to Europe in 2022. We met in Porto, and you were also moving. So I think we did this pretty much at the same time-moving back to Europe.

And I was really happy that I got a job at Automattic. And part of that job is keeping Gutenberg Times and the Gutenberg Changelog going as a Developer Advocate. So having that was a real blessing for myself and for me because I couldn't migrate my agency. I closed the agency when I knew I was going to Europe. And so keeping that going was really good. I'm very grateful for working with Automattic on that.

**BobWP:**

Yeah. Yeah, I didn't know that part of it. I mean, how that just seamlessly all worked, and you were able to bring that right into it. Yeah, that's cool. And I think the big change for me probably was when I went to the bigger network of shows and everything, and started bringing more people in.

And then at the same time, I was given the gift of a redesign of the site from the Special Projects team at Automattic. Matt gave that to me, which was phenomenal. For a few days, I was just thinking, is this really happening?

**Birgit:**

Is this real?

**BobWP:**

I mean, it took us quite a few months to put it together and stuff. And I have one funny story about the launch. We had kind of a soft launch because…

**Birgit:**

And?

**BobWP:**

I was at CloudFest, and I got a message that said, "Your site is live." And I'm like, oh, really? I had not planned for that.

And the ironic part of it-we got such a kick out of it-was my site prior to that had Beaver Builder on it. And I was hanging out with Robbie from Beaver Builder when I got the message, and I told him. And we took this picture. We were having a beer, celebrating and everything. But it was so funny-he just got a kick out of that. I basically removed Beaver Builder, and here he was celebrating with me and stuff. But Robbie's great.

**Birgit:**

The new websites…

**BobWP:**

But yeah, it still is amazing-the support and everything I get with that side of stuff. A couple of times I've really messed it up. I keep saying, maybe I should just let you do more things. I shouldn't be touching stuff.

**Birgit:**

You don't know where the boundaries are unless you kind of push past them. So yeah, what's your own knowledge-you want to kind of kick it a little bit.

**BobWP:**

Yeah, yeah. I poke around a bit to kind of understand. Some of the stuff is custom work, so I don't want to mess that up. But some of it's adding stuff. I've probably learned more about the block editor and everything than I ever thought I would be-just getting in to try to figure out, okay, this has to be a small change. And it's like, okay, an hour later… now what happened there?

**Birgit:**

Yeah, I was doing that actually on WordPress.org. I am part of the editor of the Developer Blog that launched in late 2022. And then I got the note from the Meta team that the Developer Blog now has a block theme, and I have access to it.

And then I said, "Oh, I can change the navigation." And I went in there, changed the navigation, and it kind of dropped the whole navigation and added all the navigation to the top-level navigation too. One is the overall WordPress.org, and then on the subsites, you have the own navigation. All of a sudden, my UI was jammed. So it took about two days to fix it. But I said, okay, I'm not going to touch that anymore.

**BobWP:**

Yeah, yeah. I've kind of learned now that I did screw something up recently again, and having them look at it… I even tried revisions, and it seemed like the more revisions I went back to, the worse it got. So it was like, okay, this is hopeless. I don't know where this stuff went, but it's not here anymore.

**Birgit:**

And here goes a half a day of your life.

**BobWP:**

Yeah, yeah.

**Birgit:**

But that's web development. I think it has… yeah, it's always happened. Since when are you doing web pages? How far back is that going?

**BobWP:**

Oh, so actually I started doing… let's see, when did I first do? We still had our previous marketing and design business around in 2000-I dunno-2005, 2006, somewhere around there.

**BobWP:**

…somewhere around there. I started doing-well, actually, it might've been even earlier than that-doing little HTML sites. We were doing print design. We started in 1993, the business. And so I had to kind of kick and scream and be pushed into it. And I made these godawful HTML sites with… oh, was it Adobe-what was it called? It was one of the…

**Birgit:**

Was it Dreamweaver or was it FrontPage?

**BobWP:**

Dreamweaver, yeah.

**Birgit:**

Dreamweaver, yeah.

**BobWP:**

And I remember I made one of our first sites, and I had Flash on there. Oh, it was just horrifying-bouncing letters, dancing around, or some crazy thing. And then, 2008 or 2009-I think 2008 or 2009-I got into WordPress, started dabbling in playing around with the blogging stuff. And I went to iThemes and got one of their themes there, and we did our business site.

And it was like, wow, that took me one-hundredth of the time it took me to do any other site because it was… I mean, it actually looked good, and it would function well and stuff. So yeah, I did that till about 2014 or 2015, I think, when I finally quit designing. I was into content, and I knew what I wanted to focus on. I was tired of the design client side of things.

**Birgit:**

So what was your first?

**BobWP:**

Oh, yeah. Well, I don't want to say… this was 1996. Yeah, I did a German site. It was all HTML tables-kind of horrible. Well, it's still out there because it's a reference site for books and all kinds of things in Germany. But yeah, so that was in 1996. I started-that was as a citizen in Munich-and I learned about it, and I learned about HTML.

I found it so fascinating that you can put it up on the web and everybody can see it almost immediately. And that's such a different experience from printing, where you have to wait till it comes from the printer and then you need to distribute it. That was instant distribution, and I really loved it.

But then what I found was that all the neo-Nazis and Holocaust deniers were all on the German part-they were all in America on servers-and there was nothing in Germany that holds against it, what really happened. And we were a group of two people, each one of us had our site and started a site about the Holocaust and all that information.

And mine was called *Shoah Project Internet.* And we collected information about the concentration camp in Dachau, before the concentration camp had their own website in 2000 or something like that. I connected with authors who had published poems and also some nonfiction about the wealth of Jews that was taken away by the government, and about the resistance in Germany.

It was all in German, but there was no equivalent otherwise from private citizens to actually put this out. That really made me… and then there was this big discussion-there was an exhibition, a traveling exhibition. There was this myth that the German army had nothing to do with the concentration camps, but that was a myth, and it wasn't true. And there was an exhibition that actually showed all the facts, and there was a big brouhaha and uproar.

And it was traveling, so everywhere I was kind of picking up the snippets from the online sites, from websites. So it was kind of an interesting…

**BobWP:**

I think I started using computers in the early 80s-or probably mid-80s. And I actually went to community college in the States in, I think, maybe the mid to late 80s. I took a year of computer programming, and I did learn-what was it?-BASIC, COBOL, Assembly…

**Birgit:**

Wow, yeah.

**BobWP:**

There was one other thing. And after a year, I remember we had this great guy from…

**Birgit:**

Fortran?

**BobWP:**

Yeah. Oh no, that was another one. Yeah, we had to dabble in all those in 12 months. And at the end of the 12 months, the instructor-he was great-he was a Brit, and he just had the craziest sense of humor. He said, "Well, now you've learned all this. It's all going to be obsolete by the time you step out this door."

And we were like, "What?" And I discovered after a year of that, that was not what I was going to become-a computer programmer, I thought. But it gave me the comfort level to use computers. I was really comfortable with that. So that was good. But yeah, crazy times.

So what's going to happen in the next year for you, do you think?

**Birgit:**

Well, the Weekend Edition is going to be quite interesting every time. And I see that in the community-that the block editor is more in the forefront more and more. And there's some great stuff coming out with Playground and with Studio to do staging sites and to just play around with WordPress.

So I know that Gutenberg-the Core contributors of Gutenberg-are still going to do the biweekly releases. So we are going to do maybe a monthly release podcast. And we'll invite a few more people from the space that work with Gutenberg. There is now also… quite a few people have adopted the block theme space quite a bit on multiple levels.

It's for enterprise levels, which started very early. But on the agency level, WebDevStudios, for instance-Jesse Palm was on the show recently, who had the starter theme that's a block theme for WebDevStudios-and they start every project with it.

So these kinds of things show me that there's quite another level of adoption happening about the Gutenberg project. And of course, I'm still hoping for a Google Docs-like real-time collaboration or async communication with comments.

There are some great experiments in the Gutenberg plugin that I want to dive into quite a bit as well. So we'll see what happens.

**Birgit:**

So we'll see what happens. Yeah, WordCamp Asia is going to be more of a research trip for me-to talk with the plugin developers and talk with some of the engineers and kind of see what's next for them. And I'm sure I'll find a few interview partners that I can make a show with in the space, because I already have. Some of them have left the space; some of them are coming back. So it's really interesting to see.

**BobWP:**

Very cool. Yeah, it's interesting because I think of… there was a point where I started adding some shows that were more WordPress-based. What I've found with some of these shows is, everything always comes back to WordPress or WooCommerce. And a lot of it-the similarities kind of weave in and out of all this stuff. It's good to be knowledgeable of other things, no matter what you're doing.

So I'm hoping we're going to be stepping more into videos. I've been talking about it-we're going to be doing more video with some of the shows, and we might do a little bit of live stuff here and there. I've kind of kicked and screamed into that, so that's another piece that's going to hopefully grow. I'll be trying to focus a little bit on that part of it-what I do with that and how I present it and all that stuff.

**Birgit:**

I have heard from quite a few people that there's a generation out there that doesn't read anymore. I know. They want to go on YouTube and be entertained or at least shown things. And of course, with software, if you want to teach somebody, you need to show it. That's very hard to do on the podcast.

**BobWP:**

Yeah, it is. Yeah. So who knows what? Maybe we should make this a tradition now-every January. We come in and catch up and see what we did, what we blew, everything-what broke and what didn't work.

**Birgit:**

I would love to do that. Yeah, sure. Absolutely.

**BobWP:**

We'll make it a January tradition. So anyway, we have WordCamp Asia coming up. Like you said, you and I will both be there. In fact, you're going to be joining-you'll be coming and co-hosting the table, doing the little booth, I believe, for an hour.

**Birgit:**

Yes, absolutely. Yeah. Friday, I think.

**BobWP:**

If you haven't caught up with her, you haven't caught up with me. I'll post when she's going to be at the table, and that way you can tie her down because sometimes chasing people around… you know how that goes.

**Birgit:**

Yeah, no, no, absolutely. Yeah, no, I'm looking forward to WordCamp Asia. Also, I'll be at CloudFest this year for the first time, so I'm not going to be at the hackathon. But there are too many people from Automattic going already that actually have a project. And then WordCamp Constance-that's a camp with German speakers. So it's really going to be interesting.

**BobWP:**

So you'll be at the regular CloudFest event and stuff? Yeah, I know there's going to be a little bit more WordPress stuff going on, and that'll be fun. So yeah, we'll be seeing each other next month and the month after.

**Birgit:**

Yeah, yeah, yeah. I appreciate it. I'm really loving it.

**BobWP:**

Okay, well, we've said it enough times, but Gutenberg Times-and probably the URL is very easy and stuff-but do check that out. Is it *gutenbergtimes.com*?

**Birgit:**

Dot com. And yeah, you can also find me on the Twitters and on the Bluesky and the… I still call it Twitter.

**BobWP:**

Sorry.

**Birgit:**

…on the Bluesky and also on Mastodon. And of course on the WordPress Slack and WooCommerce Slack. So I'm everywhere.

**BobWP:**

Yeah, everywhere.

**Birgit:**

Well, thank you so much. It was wonderful chatting with you.

**BobWP:**

Yeah, well, thank you. Yeah, this was definitely a must-do show for January, so I appreciate everybody listening and…

**Birgit:**

Happy anniversary.

**BobWP:**

Yeah, happy anniversary. And come back next January for our second Nova. I'm sure you'll see Birgit more than-or sooner than-next January, for sure.

**Birgit:**

Well, thank you.

**BobWP:**

Well, take care. Bye-bye.

02 Feb 2025 2:50pm GMT

Matt: My First Million

I had a great chat with Sam Parr and Shaan Puri on their podcast, My First Million.

02 Feb 2025 1:18am GMT

01 Feb 2025

feedWordPress Planet

Gutenberg Times: The anatomy of a CMS, the state of block themes and WordPress 6.7.2 — Weekend Edition 318

Howdy,

It's already February. 8.33% of 2025 is done. Phew. 91.67% to go. Most of my week I spent testing things. Maybe I jinxed it with my mind set, I didn't come across something really cool. I am excited about WordCamp Asia where I can browse this huge sponsor hall and go exploring all the cools things there.

What saved me a ton of time, this week, was using Claude AI. I used it to audit Playground blueprints in the Gallery. I pasted the description of the merged PR of modification on how blueprints work, then fed it code to rewrite using the new way. Doing this a few times, I created a tracking issue with the necessary changes to implement next week. I felt really lazy.

That was all off-set by trying to have Cursor AI write a block with some user input sections. It made great progress, but for some reason, it still doesn't work. Sometimes debugging the AI is even more tedious than looking at your own code.

This week, we have a few strategic posts and practical tips for you in this newsletter. Enjoy!

Yours, 💕
Birgit

Developing Gutenberg and WordPress

George Mamadashvili made Gutenberg 20.2 RC1 is available now for testing. Final release will be on February 5, 2025.


Aaron Jorbin announced that WordPress 6.7.2 will be released soon. RC will be released on February 4 and final release will hit the WordPress site near you on February 11.

🎙️ Latest episode: Gutenberg Changelog 113 - WordPress 6.8, Gutenberg 19.9, 20.0 and 20.1 Plugin Releases with special guest Tammie Lister 💕

Tammie Lister and Birgit Pauli-Haack recording Gutenberg Changelog episode 113

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

Darren Ethier and James Kemp from WooCommerce talk about Building WooCommerce in Public in the latest episode of DoThe Woo Network They explore WooCommerce's current state and future direction, with Darren highlighting his connection between Gutenberg and WooCommerce. They stress the importance of community and communication in development, discuss the significance of WordCamps, the need for key features, and WooCommerce's evolution for better experiences. They also mention how changes in WordPress affect WooCommerce's plans and the need for flexible, no-code solutions for developers. This conversation provides insights into WooCommerce's development approach and plans.


On Learn.WordPress.org, Wes Theron published the lesson: Explore synced pattern overrides. It's part of the Intermediate WordPress User course and covers what's patterns are, and how you can maintain stylistic control while the content of a pattern.


In his post, Create a Custom Author Page Ronnie Burt introduces you to multiple ways how you can make use of the Gravatar profile for your website. He also explains why spending a moment on the design of an author page is very important for a company blog. Then he walks you through the various method how you can use the user information stored on a self-hosted site can be used to expand on the normally neglected and thinly populated author information.

Upcoming events beyond WordCamps

Apart from WordCamps, additional conferences are on the schedule for this year.

February 24 - 28 2025 The 2nd Annual WP Publisher Success Week will take place. You can learn best practices from leading experts in the field of WordPress for publishers.

March 17 - 20, 2025 CloudFest, Europa Park, Rust, Germany. As Bob Dunn, DoTheWoo reports, there will be a WPZone and a WPDay.

April 23 - 26, 2025 PressConf a conference for WordPress professionals will take place in Tempe, Arizona, USA. Speakers are among others Mary Hubbard, Matias Ventura, Rich Tabor, and Tammie Lister.

September 25, 2025 LoopConf returns to London, UK as a conference for WordPress developers.

Theme Development for Full Site Editing and Blocks

In his latest blog post, Nick Diego wants theme developers to stop struggling with cumbersome theme.json files. He shares how he and his new buddy, Cursor AI succeeded in building a compiler/bundler to combine separate json file into an overall theme.json for a theme. Diego shares a video of the process and the final script, you can adopt for your workflow.


Hendrik Lührsen found that WordPress themes are facing a crisis. The introduction of Full Site Editing (FSE) has brought about complexities that are causing challenges in the WordPress theme ecosystem. This situation appears to be related to the rapid evolution of WordPress technology, particularly the implementation of the site editor, which is impacting how themes are developed and used.

While calling it a crisis makes the post viable for the successful spread via outrage advertising economies, Lührsen is not wrong, lamenting about all the short-comings of block themes. His suggested paths to improve the situation can be walked by every theme developer building sites for clients on top of WordPress, except the discoverability of themes on the repository. A standardized onboarding process, was discussed among Themes team members. Turns out that the many, many use cases are not easily pulled into a cookie-cutter closed system. It's the nature of the 21-year legacy of WordPress. It also means, any developer can fill the gaps for their clients, and if they want to go the extra mile, share it all back to the community. WordPress is not a one-size fits all system. Flexibility and extensibility is a feature, not a bug.


In his YouTube video, David McCan looks into the current state of block themes, reviewing popular themes available in the WordPress repository, Then he looked under the hood to understand block themes. "I have a better understanding of block themes after going through this process." McCan wrote in the description. If you rather read a blog post reader than watch a video, got here to read McCan's thoughts


In his post Transitioning to FSE: A low-risk, high-reward move for enterprises HumanMade's account director, Adam Jones, tells the story of how Human Made, "guided enterprise organizations through this process and seen the transformative benefits firsthand." Adapting to the site editor and block themes allows businesses to enhance digital capabilities with minimized risk through careful planning and testing. Key benefits include improved scalability, workflow, and reduced reliance on developers, making full-site editing a valuable investment in digital infrastructure. Also on that topic: The three competitive advantages of full-site-editing by senior account manage, Lorna Lim.

"Keeping up with Gutenberg - Index 2024"
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

Building Blocks and Tools for the Block editor.

Riad Benguella, architect on the Gutenberg projects, explains in his latest post The anatomy of a CMS and why any web developer should attempt to build a CMS just once. The magic happens through four key parts: how content is stored, how it looks, how you edit it, and how it gets shown to the world. Whether you want to create a personal blog, an online store, or a company website, a good CMS adapts to your needs. Benguella took a detailed view into the various parts of the WordPress CMS: block rendering, style engine and the fields system. If you wish to know how it all fits together, grab your favorite beverage and start reading.


What's new in Playground

Check out this article by Ján Mikláš, Demo your Woo extension with WordPress Playground, where he breaks down how to set up WordPress Playground just for your needs. You'll find out how to tweak your blueprint.json file with settings and steps, plus how to create a custom landing page and hide those pesky WooCommerce onboarding screens.

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: AI generated.


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.

01 Feb 2025 1:26am GMT

31 Jan 2025

feedWordPress Planet

Do The Woo Community: Friday Shares Fadeout. Sign Up for Our New Newsletter.

In this episode of On WPCommunity, BobWP announces the conclusion of his regular Friday share posts on the blog due to time constraints and his new plans. He explains that after WordCamp Asia in February, a new newsletter will be launched alongside the release of version 5.0 of their site. The newsletter will feature actionable […]

31 Jan 2025 1:30pm GMT

30 Jan 2025

feedWordPress Planet

Do The Woo Community: State of Enterprise WordPress 2024 Report with Brad Williams and Tom Willmot

In the latest Scaling Enterprise podcast episode, Tom and Brad discuss the 2024 State of Enterprise WordPress Report, highlighting trends in adoption, usage, and decision-making dynamics within organizations.

30 Jan 2025 1:12pm GMT

29 Jan 2025

feedWordPress Planet

WPTavern: #154 – Anna Hurko on Managing a Growing Plugin Business

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 managing a growing plugin business.

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.

So on the podcast today, we have Anna Hurko.

Anna is the CEO of Crocoblock, a company with a suite of dynamic plugins designed to help developers build complex websites. With a background in computer science, Anna transitioned from support roles to leading Crocoblock, and has been with the company for over 11 years.

Anna quickly rose through the ranks due to her technical knowledge and effective communication skills. Crocoblock, which started with just a handful of team members, has now grown to 85 employees. They offer a wide range of specialized plugins, such as JetEngine, JetSmartFilters, JetBooking, and more, primarily aimed at agency and freelance developers.

Anna shares her journey and discusses the growth of Crocoblock. She highlights the company's flexibility and commitment to meeting developers' needs, adapting to both the rapid changes within WordPress and the increasing demand for dynamic site capabilities.

Anna also talks about the company's marketing strategies and their active, and growing, participation in the WordPress community through WordCamps and Meetups.

If you're interested in how a company evolves within the WordPress ecosystem, and the challenges and successes that come with it. 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, Anne Hurko.

I am joined on the podcast today by Anna Hurko. Hello Anna.

[00:02:53] Anna Hurko: Hi Nathan.

[00:02:54] Nathan Wrigley: Very nice to connect with you. I should probably say at the outset, Anna has several names. So if you know Anna better as Vanessa, or any combination thereof, it's the same person. So do you just want to clear that up? How is it that you've got two different names?

[00:03:09] Anna Hurko: So it's from the beginning. I have started to work as a supporter, and it was like tradition to choose a nickname for support agent. And I decided like okay, I'm already Anna, I want something other, but which will suit me. And I decided to be Vanessa.

And for a few years I was Vanessa, but somehow all my colleagues remembered me as Vanessa, and we used it till now, even if I don't need it anymore. And that's how it works. But now I feel more Vanessa than Anna because in whole work, so even financial departments, they say Vanessa, not Anna. Even the ex coworkers who are not anymore working with me, but they're my friends, even their children say I'm Auntie Vanessa.

[00:03:46] Nathan Wrigley: So several names, but hopefully by the time this podcast is finished, you'll have figured out, dear listener, who it is that we're talking to. But I'm going to go with Anna because that's probably the easiest thing for me to say.

So Anna, we are a WordPress podcast, so I guess it would be a good idea right at the outset to give you an opportunity to just tell us who you are, where you come from in terms of the geography and maybe the company that you work for, things like that. So really it's a short bio moment. So could you just tell us a little bit about yourself?

[00:04:13] Anna Hurko: Yes, sure. So I'm from Ukraine, from south of Ukraine, and the company is the Crocoblock is project I'm working with now, and it's located in Ukraine as well. All our team members are in Ukraine, in one city actually. So now a little bit different. So I'm CEO of Crocoblock and I work for the holding company about 11 years for now.

[00:04:32] Nathan Wrigley: So, what is Crocoblock? And I hope I've pronounced that correctly. By the way, everything that we mention will be linked in the show notes. So if you head to wptavern.com/podcast and look for the episode with Anna in it, then you'll be able to find all the show notes. But, what is Crocoblock and what does it do?

[00:04:49] Anna Hurko: So Crocoblock, I have always a long and short answers. Crocoblock is project who is making plugins for developers to build dynamic complex websites. And the idea was to have ecosystem which has all tools for developers needs.

But for me as a CEO, Crocoblock is a team. So it doesn't matter which technology will come tomorrow and what happened to WordPress, we are a team who can build products. So that's why I have two answers.

[00:05:14] Nathan Wrigley: Now, you mentioned at the outset that you are from the Ukraine originally, but just before we hit record, you talked about the fact that you are no longer in the Ukraine. But maybe that would be an interesting way to begin this podcast properly.

I'm guessing that from the description, living in the south of Ukraine, that you moved against your will, possibly. You've had to move because of the situation over there.

[00:05:36] Anna Hurko: So the are three years of the situation. I was in Ukraine, I just moved in September after WordCamp US. I just didn't come home and then stayed in Europe because I am trying to visit more WordCamps and WordPress meetups. And if you're in Ukraine, it takes too long time to get out, because you don't have planes and you need to go with a bus to Europe and to take plane, and every country in Europe takes me two days to move.

So I decided to stay in Romania because it's kind of in the center and then can visit more events. So last year I visited about seven WordCamps, because I want to go closer to community, to customers, to speak offline with them, and we have results. So we have already ran a little bit growing in comparison.

[00:06:20] Nathan Wrigley: The situation in Ukraine in terms of web development and tech, it always seems like Ukraine punches above its weight. I don't know if there's a particular kind of, I don't know, like drive in school or anything like that to head towards technology and software development. But it seems, when I look at the about page of a lot of products, especially in the WordPress space, but technology more generally, it always feels like Ukraine is overrepresented with the amount of companies. I don't know if that's something that you think is true or if that is true.

[00:06:53] Anna Hurko: It is true, but I think it's not because of good reasons. Somehow we didn't have good factories and job places, and web was very easy for people to just find a job and to have good salary because a lot of companies working as outsource, or they have customers from US and Europe. For example, like Crocoblock, we don't work with Ukrainian market actually, we work with Europe and US.

And it's not something, we have good studying in school and university. Unfortunately it should've developed better. For example, I have studied computer science, but it was like old technologies in university. Just because we don't have normal working places, people starting to self-educate and they work in IT. And somehow it's very good now. So even government programs, they're all digitalised.

So from my phone, I can pay taxes, I can marry now from phone, but only with Ukrainians, of course. I can get any document I need, I don't need to go anywhere. So now, for example, I'm outside of Ukraine, but I can have any document, new driver license. I can sell car with one application. So it's somehow built in us.

[00:07:59] Nathan Wrigley: So the propensity of Ukrainian web developers is as a result of people looking to improve their own lives and finding that distributed work was something that they could do, and they could earn a good, in air quotes, good salary if they took the initiative and did, what? Self-taught learning, that kind of thing.

[00:08:17] Anna Hurko: Yes, yes. Because in university, school, it's really bad now, I'll say. It's not practical. But, for example, as I have studied computer science, it was all technologies. It was like Pascal Delphi, if you even know, C++. Something very difficult and not attached to WordPress, for example. But it gives me understanding how database works, for example. And it helps me a lot, even now, I don't work with WordPress itself, so I don't build product, I mean. I work with a team. It helps me to understand my developers and how it works.

[00:08:46] Nathan Wrigley: Okay. Yeah, well, it's a nice idea that the CEO of the company actually has a background in technology. I think that's interesting to be able to speak to the developers on their level.

How did you start in the WordPress space then? I think you said that you started working with the support side of things over at Crocoblock. And if that's the case, going from support to where you are now, CEO, that's a pretty big move. How did it all begin?

[00:09:09] Anna Hurko: First I need to say that I didn't realise it's a big move before attending WordCamps. Because it's for me everyday life and it was kind of 10, 11 years. So when I have studied computer science, by side I was in NGO and Youth Politic. And I told, I will never have anything with programming languages, or with IT, or even with websites because we had website building in university as well, but it was, you know, when it was on the tables and HTML and so on. And the teacher was so awful. So I told, I will never do it, and now I'm here.

So after I finished with Youth Politic, I have started to just looking for a job which need English language. So because I didn't want IT and I sent a CV for everyone with English knowledge, and they picked up me in the holding company as a support member because I knew English. But somehow as I knew computer science, it was very easy for me to deal with WordPress. And in three months I was already a night shift team leader and I have started to mentor people and so on. So I have started with support, but my background with computer science helped me to be very good, very fast.

So until now, I think it was the best thing I can do in my life is to be a supporter. Even now I think so. And because I have done Youth Politic, I had soft skills which helped me to communicate with customers in a nice way. And we have started to rebuild the support team as well, and there are rules in support and so on.

[00:10:31] Nathan Wrigley: So you started out in support, and fairly quickly you rose through the ranks. And you mentioned just there that, you called it the, what did you call it?

[00:10:38] Anna Hurko: Holding company.

[00:10:39] Nathan Wrigley: The holding company, that's it.

[00:10:40] Anna Hurko: Yeah, we have holding company, it has several projects on side. And now Crocoblock is totally separated project.

[00:10:45] Nathan Wrigley: So what's the holding company, and is it a sort of WordPress thing, or is it just technology in general?

[00:10:50] Anna Hurko: It's a recent WordPress thing. So we have started as a team in Template Monster. And, yeah, I was a support member in Template Monster first. Our developers started as well with templates before the templates were starting to die.

[00:11:04] Nathan Wrigley: And do you have a background in using WordPress, or has your experience with WordPress been on the journey in Crocoblock?

[00:11:12] Anna Hurko: I don't have my private experience, so I never worked for an agency. But what I need to say is that in support, when I have started support, it was not like just us answering general questions. I was very technical support member, very quick. And customers in Crocoblock even now, but even before when I was working, they come with the real projects. And they just come and say, I don't know what is wrong, just do something. And you log in on the website and you start building it.

And that time, to start working in support, we had training for one month. About four hours theoretical training, and then five hours of homework. And this first month, I never went out of my house, only for my grandmother's birthday. And what we have done, we haven't learned WordPress, we have learned CSS, JavaScript and HTML. We have built websites, and working with database was as well. So somehow I started to work with the websites first, but just I don't have commercial experience, I think.

[00:12:07] Nathan Wrigley: And what's the structure of Crocoblock then? How many people do you have deployed into that project? If you are the CEO, I guess you're at the top of that pyramid, how many people are working with you, for you? However you want to describe it.

[00:12:18] Anna Hurko: We have started six years ago with five people, five, seven people. We don't know exact number. All of us have different story of it. Now it's 85.

The story begins when we were in Template Monster and we have built templates. In some point we had new people for it and we needed more amount of it and so on. And we have started to build frameworks to speed up the process, and to have less errors because if every quarter developer makes it in own style, we have too much issues with it.

And then we started to sell it. So because it was product for ourself, but it was too good and we have started to like, okay, can we just start to sell plugins? And then we have started it, it was enough, seven people. It was developers, one support member, and guy who was before me, the CEO.

[00:13:00] Nathan Wrigley: So if I go to the Crocoblock website, which is crocoblock.com, and I look at the products that you've got. It opens up a fairly giant mega menu, and there's literally dozens of things in there.

When I first heard the word Crocoblock, firstly I assumed that it was plural, that it was Crocoblocks, and my assumption was that, okay, that'll be a suite of WordPress blocks. So you'll download a plugin, and then you'll have a bunch of blocks that you can put into the block editor.

And you go to the website and you realise, no, that's really not what it is. That's not even close to what it is. So what is it that you are offering into the market? What are the different products that I can find in your product section? I mean, there's too many to talk about, but maybe just pick your favorites or a few that are particularly popular.

[00:13:47] Anna Hurko: Yeah, so short answer is, well, it will be JetEngine and JetSmartFilters. But the issue is that we have invented the Crocoblock name before Gutenberg. There were no blocks, it was Crocoblock, and we have it because it was an old project that we had already some traffic and we left it.

Now we have actually two names, Crocoblock and JetPlugins because all of our plugins are JetPlugins.

And the issue is that the project was started with supporters and developers. We didn't have marketer for a few years. So I have a head of marketing only last one year. That means we didn't thought about the things like name, and now we have a lot of difficulties with it.

And when I had started Crocoblock we have the first document with idea about what Crocoblock is, and it was one sentence that will make us laugh for even now. Crocoblock is not about dynamic, it's only about static and nice design. And what is fun about it? Because it's now only about dynamic plugins. So now we have big menu with a lot of plugins because it's like our history and we can't delete them, because people use them.

But our main focus is on dynamic websites, and that means JetEngine, which is a competitor for ACF, but it has much more inside. JetSmartFilters, JetThemeCore, and all plugins, which helps you to create complex structured websites, like real estate, multi-vendor and so on. You can track user data, and you can manage what to show to different users, or see the user behavior and connect to it.

[00:15:13] Nathan Wrigley: Yeah, there really is a lot in there. You really do run the whole gamut of what WordPress can do. So for example, there's something called JetBooking, which I'm imagining helps you with booking. And JetGridbuilder, again, it speaks for itself. JetProductTables, JetWooBuilder, JetProductGallery, Jet Appointments, JetFormBuilder. You get the idea. You've got your fingers in everything.

[00:15:35] Anna Hurko: The idea was to build this structure where developer has ever seen. We have started with Elementor. When Crocoblock was invented, it was few builders on the market, new builders. Elementor, Oxygen, and maybe, I don't remember, Brizy or something like that. And they were on the equal stage. And our previous CEO came to us, I'm like, what will we choose? He asked me, and he asked our CTO. And we choose, both of us choose Elementor because of user experience and because of the cleanness of the code.

Our idea was to build everything except hosting and page builder for building websites. So we have tried, at the beginning, to close all the tasks for users and it was very fresh. So we appeared at the same time when Elementor was developing. And Elementor had less features inside of it.

So first of all, we have tried to close all tasks, and now we're more specifically working on dynamic. For example, Elementor, in JetElements we haven't added any new features for few years, but it's still our best plugin in sellings. But we don't develop it because we don't like to develop, so I mean we're fixing bug issues or compatibility issues, but we don't add new features because Elementor has added all new features, HappyAddons. And we don't want to build, if it's already on market, we don't build it. It's a philosophy of Crocoblock. We don't want to build anything which already exists.

[00:16:54] Nathan Wrigley: So over there I can see, what is it? 21 on the mega menu, there's 21 things there. I'm guessing that, probably started with 1 went to 2, 3, 4, and we're up to 21 at the minute. How do you keep this going? Are you intending to go from 21 to 22, 23, 24? Do you keep adding products, or is this more a case of, okay, we've got what we've got. We've covered everything? How are you making decisions about what it is that you're going to do in the future?

[00:17:18] Anna Hurko: So as I came from support, when we invented Crocoblock, we had only one support member, and all developers were supporting as well. We have very tight connection with customers and what we're building, we're building after customer's request. So it depends. If it will be need on market to build one more plugin, we'll build it. If not, then not.

So I can tell you we have strategy for number of plugins. We have strategy to cover developers' needs. So now, for example, we have user interviews, some pools, research and market to find what else developers need. So it's not about number of plugins, it's about to close the needs.

For me, I don't want more plugins, so it's not the goal. But if it would be better to build it as a separate plugin, we'll build it. For example, the JetProductTables, it's a new plugin. It was a result of R and D departments, I would say. We have new department, new for one year and they made resource. It's like an experiment. So we don't have any goals and number of plugins. It's just to make developers life easier.

So we have some projects, for example, we have ideas for projects not related to plugins itself, but to developers. I can't tell you now what will it be.

So for me it's, you know, like CEO, I don't like a lot of plugins and I don't want to have more team members. It's always something you don't want, to have more, because it's easier to focus on one plugin. And as you say, it would be easier to focus only on JetEngine, but somehow Crocoblock can't stop.

[00:18:44] Nathan Wrigley: You mentioned at the start that you began the business with Elementor in mind, and Elementor, if you haven't been keeping a track, dear listener, Elementor really has had just the most astronomical growth since its inception, and I think really is singularly responsible for a large proportion of WordPress' rise.

Now, I don't know if that is the sort of page builder of choice that you've hooked yourself into, or if you've got into the sort of more WordPressy way of doing things. And what I mean by that is, you know, the Block Editor and Full Site Editing and things like that, because that's obviously where the Core of the WordPress project is focusing its energy. But obviously on the periphery of that, you've got all these different page builders.

What do you do with all of that? Do you hunker down and stick with Elementor, or do you decide you're going to go with like the Core way of doing things? How does that all fit in?

[00:19:33] Anna Hurko: So we of course love Elementor and it helps us in the beginning so much. We have the same philosophy as Elementor in a lot of things, like treating customers and so on. And I think it was right choice to start with. But once it was announced, the Gutenberg project, and then WordPress started with Gutenberg, the same in half a year or something like this, we have started to rebuild our plugins.

So all our main plugins, not design plugins, but all our main plugins for dynamic websites. So when the Gutenberg project was started, we rebuilt them, and they all are working with Gutenberg as with Bricks now and Elementor. So Elementor is just one of the builders customers need. And then Gutenberg is the core. So we have rebuilt inside the plugin, the code in the way it can work with Gutenberg and we can easily add other integrations. And we always perform something with WordPress and Gutenberg native features. It's in the core. So of course Elementor has grown up.

So the company itself, it's 20 years in market and we have all the 20 years experience. And we know it can shine as a star and it can die next day. But WordPress, we believe will stay for a long time with us. That's why all our main plugins are built for WordPress and Block Editor. And we try to connect it more natively.

The issues we have, it takes a long time. For some of our projects, for example, we have JetThemeCore, it's a plugin which builds templates for archive pages, WooCommerce card, profile page, so all sorts of pages you can make the structure with it. And for some time we haven't developed it because we were waiting for FSE, for some new features from WordPress itself. But it take too long time, and we didn't want to build something that WordPress will build natively. Or you need to wait or you build it, and then users will have it twice, once in Crocoblock and then in WordPress.

So we have these issues, but we're trying to work around. For example, we have JetStyleManager, it's a free plugin. It was created specifically for Gutenberg, because when we have made integration and compatibility for our plugins, Gutenberg was very new and it didn't have a lot of style options. And we have built separate plugin just for Gutenberg to make styles possible. And now users have this solution from every plugin provider different, and we will rebuild it because WordPress have changed and so on.

So what I wanted to say, and it took a long time, even if you use Bricks, Elementor, and we will add some other integrations for Builder, WordPress is in Core and we would never ignore it. We're part of WordPress, first of all.

[00:22:04] Nathan Wrigley: You mentioned a few sort of little frustrations there with the pace of WordPress. So for example, you may want a particular feature, and you know it's coming, but you take your foot off the pedal of your own project so that you're not building it twice as you said. But what about the way that Gutenberg and Full Site Editing, but Gutenberg in particular has changed over the last six or seven years?

I mean, there must have been times when, the fact that it was altering so rapidly, and in such a drastic way, you know, from one release to the next it might be an entirely different UI for a particular thing. And then you've got to scratch your head and think, okay, we just shipped something, and we did the documentation, and it all looked like that, and now it looks like this, we've got to redo all the documentation.

Being honest, has it been a straightforward process or has it been a fairly frustrating process? I mean, it could have been a bit of both, I guess.

[00:22:53] Anna Hurko: It's both. It was frustrating because we so believe in WordPress, and we have waited for some changes before, early, and it took too much time from our opinion. But it's part of WordPress life. So it's part of probably open source and so on, so we're okay with it. And I can say that probably we don't feel that frustration all the time because Crocoblock itself, growing and changing so quick as well.

In six years we started with five people, now 85. You can imagine how quick changes processes inside our team as well. Because every time, in marketing, you have few new people, you need new process. Or in developers teams, they have started like three, four developers and now 15. Every two, three, developers, you need to change the process. So what I mean, in our philosophy of Crocoblock, we are okay with changes. It doesn't frustrate us. What frustrates us, if nothing happens.

[00:23:44] Nathan Wrigley: Yeah. And over the last decade or more, we've just seen the line of market share for WordPress go up and up and up. And if I was a product maker in the WordPress space, that would've made me feel great. I've got a credible product, it works. We've got a load of people using it. And look, the amount of people who might use it just keeps rising. And then we get to about 43% of the web, whatever that means, I mean, we can ignore exactly what that means, but the point is the line just kept going up.

More recently there's more discussion about stagnation in the marketplace, and maybe that line tapers a little bit and it goes flat. Or, and I don't really want to get into that, we've got this period of change at the moment, there's a lot of politics inside of WordPress. I'm just wondering what your thoughts are on where the business is pitched. The fact that you are using WordPress is great, but do you have any concerns about the market share sort of stagnating, or do you feel that you still have a massive audience in WordPress that you're still yet to reach?

[00:24:41] Anna Hurko: We have different periods. For example, last years were very challenging for us. Because Crocoblock started, when we started it grows in geometrical progress, it was very quick growing. And then of course as a five, six years project, you have not so big changes in your revenue, but it's good, it works. And last few months we have very good results. So I think we don't feel that stagnation so much because we have started Crocoblock without marketing, it was selling itself, and of course with help of community influencers.

And we have just started last year to build a brand and to work with marketing. It means we have a lot of potential yet. So if market is stagnating or it still feels for us to develop our customer base and so on, because we didn't use it before. You know what I mean? So if you haven't selling in right way, then now we have started. So we still have a lot customers.

[00:25:32] Nathan Wrigley: Oh I see what you mean. So it was more kind of organic growth, or maybe it was social media or YouTube or what have you.

[00:25:38] Anna Hurko: We have started with product team, and that's why we didn't have real marketing. No one from us really understood the marketing itself, because we have just done what people need. And somehow the product was built first for ourselves and for our needs. That means we know our customers, not only from support team or interviews, they know them because they are we. So we didn't need marketing.

And it was a time in our Crocoblock life when we didn't believe in marketing. And we thought like, okay, marketing is just wasting of money. It changed. So last year we had head of marketing and I developed a marketing team as well. That's why it's very new for us and we still have where to grow.

And about market share, we could say something about stagnation, but after we see new numbers of Elementor, and we can see where is no stagnation. And about the drama and the situation with WordPress, which we had since September, we don't feel it.

So for me, it was surprising that my life was only about the drama and no one in Crocoblock community talked about it. So we have 30,000 people in Crocoblock community in Facebook, and it was only two posts asking about what happens, that's it. With five comments. So I think the companies care, but customers not so much.

We have some feedback from agency customers. So our customer is an agency or freelance developer. They had few issues from clients, but not so much. So the main reason is to keep ecosystem healthy and that's it.

[00:27:05] Nathan Wrigley: And now that you've moved into marketing, by the way, I think you were right about marketing. If you spend your marketing money badly, it probably is an absolute waste of money, but if you spend it wisely, it's probably the most effective money that you can ever spend. So where are you pitching that then?

So if I just rewind and re-ask that question, who is your audience? Who are the people that are using this? Is this a product which is used by agencies to deploy to their client websites? Do you find that you are being purchased by, I don't know, people who've just got one or two websites? Maybe it's just a solopreneur, something like that. Is there a segment of the market that you identify with?

[00:27:41] Anna Hurko: Yes, of course. First, when we have started, we were growing just naturally and we didn't ask ourselves these questions. Now, we have made a lot of researches, and it's the same answer. Our customers are agencies and freelance developers. They're about 30, 35, 40 years old with five, six years experience.

The issue is the Crocoblock is quite complicated solution. It gives you total freedom. You can build from admin panel anything, we have query builder where you can use SQL and other complicated stuff. You don't need to go to database. You can reach your SQL database from the admin panel, or complex relations and so on.

But to use it, even from admin panel by clicking buttons, you need to understand how it works. The learning curve is complicated. And our developers building product quicker is that all other 80 people can produce a content for it and tutorials. That means, so if you need one website, it's not a marketing answer, but if you need one, two websites, you don't need Crocoblock. It'll be too complicated for you. But Crocoblock will save your time and 50, 60% if you have more websites, if you're an agency.

[00:28:47] Nathan Wrigley: Right, I understand. So if you've got a portfolio of websites and you're willing to put the time in to learn over 2, 3, 4, 5, 10, 20 projects, you'll get a return on your time back. But if it's just one website, maybe the learning curve, unless you really into that kind of thing and you just want to learn for the sake of it.

[00:29:04] Anna Hurko: I have visited a lot of WordCamps last year and meetups, just to talk to our customers. And we have a lot of fans who paid us once lifetime, but they're still our fans and they talk about us on meetups and so on. Even unpaid, it's so pleasure when someone talked about you, about meetup, and had presentation and you never paid for it.

And it's always about four or five people in agency who are building websites. And because of Crocoblocks, they can build one website in a week, starting from design into the launch. It's very nice because we have components and query builder and glossary, so you can make some predefined elements and then reuse it all the time if you have some websites you built then, for example, booking and so on.

[00:29:47] Nathan Wrigley: So do you sell your products separately? So all of the different ones that I mentioned, plus all ones that I didn't have time to mention. Do you sell them as individuals or do you tend to sell it as a sort of bundle that people buy? How do you pitch that?

[00:29:58] Anna Hurko: You can buy them separately or a bundle. So it's a subscription for one year, but you can buy one plugin, we have custom subscription, you can choose a few plugins, so you can buy a lifetime with all the plugins or all inclusive yearly for all plugins. So it depends what you need. So of course the most popular is lifetime.

[00:30:16] Nathan Wrigley: Do you get yourself involved in the community? I know personally you said you'd been to a load of WordCamps and things. Does Crocoblock give back? Do you sponsor events maybe locally or some of the bigger ones? I don't know, maybe you even contribute time to Core in terms of developers or something, I don't know.

[00:30:30] Anna Hurko: So it was our plan. Honestly, we haven't started to contribute into Core, but we sponsor WordCamps and we attend a lot of WordCamps. We have started from last year, I think, but because of the war, we couldn't start before. So I mean, the Crocoblock started with all of these things. But from last year we started to sponsor big WordCamps and small WordCamps.

[00:30:50] Nathan Wrigley: I mentioned the URL earlier, but I'll say it one more time. It's crocoblock.com, so C-R-O-C-O-B-L-O-C-K dot com. That's where you can find all of the different bits and pieces that Anna's been talking about. If anybody wants to speak to you, Anna, personally, do you hang out on any social media platforms, or have a thing that you'd like to mention where people can find you?

[00:31:10] Anna Hurko: Yeah, Facebook or Twitter, but I'm as well in LinkedIn. And I can tell you the secret, and if you write in Facebook room community, you can find our CTO Andrew. And if you write him in DM, he will answer you as well.

In all WordCamps I told to customers if they have complicate, but interesting case, they come to contact Andrew, and if it's really interesting, he will help you. And even make some changes to plugin sometimes because of customer requests. So we are very reachable. I mean, all Crocoblock team will answer you if you write in DM.

[00:31:42] Nathan Wrigley: Well, thank you very much for chatting to me today, Anna. I really appreciate it. One more time, if you want to find out what they're doing, crocoblock.com is the URL. Anna, thanks so much for chatting to me today, I really appreciate it.

[00:31:52] Anna Hurko: Thank you.

On the podcast today we have Anna Hurko.

Anna is the CEO of Crocoblock, a company with a suite of dynamic plugins designed to help developers build complex websites. With a background in computer science, Anna transitioned from support roles to leading Crocoblock, and has been with the company for over 11 years.

Anna quickly rose through the ranks due to her technical knowledge and effective communication skills. Crocoblock, which started with just a handful of team members, has now grown to 85 employees. They offer a wide range of specialised plugins such as JetEngine, JetSmartFilters, JetBooking, and more, primarily aimed at agencies and freelance developers.

Anna shares her journey, and discusses the growth of Crocoblock. She highlights the company's flexibility and commitment to meeting developers' needs, adapting to both the rapid changes within WordPress, and the increasing demand for dynamic site capabilities.

Anna also talks about the company's marketing strategies and their active, and growing, participation in the WordPress community through WordCamps and meetups.

If you're interested in how a company evolves with the WordPress ecosystem, and the challenges and successes that come with it, this episode is for you.

Useful links

Crocoblock website

Anna on LinkedIn

29 Jan 2025 3:00pm GMT

HeroPress: Building a WordPress Career Without a Map: Lessons from My Journey

Pull Quote: Be open to change, focus on what you do, and don’t fear big goals. Here is Anna reading her own story aloud.

I never dreamed of being a CEO. Even now, when I am introduced as such, I feel a little shy. But every time I start thinking, "Am I enough? Doesn't the company deserve someone more qualified?"-I return to my journey.

I want to share this to inspire those who are just starting out, changing their path, or feeling lost along the way.

My career path looks like this:
Senior Technical Support Specialist → Shift Support Manager → QA Manager → Release Manager → Project Manager → Product Owner → COO → CEO

I started as a chat operator in technical support and quickly advanced to Senior Technical Support Specialist and mentor, later becoming Shift Support Manager. I transitioned to the production department as a QA Ma

Soon after, my responsibilities grew to include roles like Release Manager and Project Manager.

When we launched Crocoblock, I focused on product and strategic issues, working as a Product Owner, then COO, and finally, CEO.

However, my journey began even earlier.

A story that inspired me

When I was a teenager, my father changed careers. He worked as a land-line network engineer, but as technology advanced, the role became obsolete. At 42, he started from scratch in the gas industry. His persistence and willingness to learn left a lasting impression on me. A few years later, he became the CEO of a company in a completely new field.

Later, in 2014, due to war, he lost his job and started over again. Now, in 2025, after yet another wave of war, he has taken on a new role, proving to himself and others that it's never too late. This story ingrained in me the belief that "you can always find a new beginning."

How I entered IT

While studying at university, I promised myself, "I will never work with websites!" Before WordPress, web development with pure HTML didn't appeal to me.

However, in 2014, as the war began and tanks rolled past my house toward Crimea, I was looking for any job that required English. That's how I ended up in technical support. The training lasted a month, with me spending 5 hours on mentorship and about the same amount of time on homework every single day. During that time, I left the house only once to celebrate my grandmother's birthday-I was that captivated.

My technical education, understanding of databases, and soft skills from public activities helped me adapt quickly. I chose to work a six-day schedule to fully immerse myself in the new world.

A defining moment

After my internship, I was introduced to the KPI system that affected salaries: 30 metrics and a calculation formula. Instead of analyzing the formula, I focused on the tasks at hand. My goal was simple: solve customer problems as effectively as possible.

Two months later, I became the top chat operator. Within three months, I mentored newcomers, and in six months, I helped revamp the support system.

This experience was key for me. I realized it's not about chasing ratings or recognition-it's about focusing on the value you create, which ultimately leads to success.

The transition to production

After a year and a half in support, I wanted a broader impact. Thanks to regular reports and feedback I shared with the production team, they invited me to join their department. I didn't know which role suited me or cared about titles-I simply did what was needed.

Over time, I held several roles: QA Manager, Release Manager, Project Manager, and Product Owner. But none of them confined my scope of responsibilities.

My approach to work

One of the most important principles I followed was a willingness to help-without letting it hinder my main work.

I always ensured the problem was solved and remembered the solution. This helped me build a broad network within the company and become the go-to person who "knows everything."

Why I grew with the company

Throughout my career, I have never feared uncertainty. When responsibilities changed, I took them as challenges. My philosophy was simple: "I need to do everything to help the project grow, and I'll grow along with it."

Of course, there were periods of anxiety and doubt. Remembering my goal helped me push forward, work harder, learn faster, and adapt to changes.

How I became a CEO

With each new role, my understanding of the WordPress market and products deepened. My vision broadened, and my goals became more ambitious. This inspired me to build a strong team and take on more responsibility for decision-making.

As COO, I honed my skills in achieving goals. However, the key to transitioning to CEO was realizing I was ready to take responsibility for defining the goals themselves. As a CEO, your work results in the work of your team. The main tasks of a CEO are to maintain the vision, support the team, and create conditions for growth.

For me, being a CEO is about constant development, solving new challenges, and creating growth opportunities-not only for the company but also for the team. This role isn't the ultimate goal but a tool for achieving results that matter to us all.

Key takeaways

Over this journey, I've learned that it's important to focus on tasks rather than how one is evaluated. Good work speaks for itself.

When you do what you love and constantly strive for new challenges, time flies unnoticed. That's what happened to me: 10 years passed in the blink of an eye. And then, one day, I find myself still the same girl fighting in the name of customer happiness-but now, I'm also setting the budget for the entire project for the next year.

During this time, I've observed my colleagues and subordinates build their careers, and I strive to share my experience. At Crocoblock, we actively help support team members grow into developers, managers, and marketers, taking on new roles. This path is open to anyone willing to work, learn, and aim higher.
My lesson is simple: Be open to change, focus on what you do, and don't fear big goals. If you work toward them daily, they will become a reality.

The post Building a WordPress Career Without a Map: Lessons from My Journey appeared first on HeroPress.

29 Jan 2025 6:00am GMT

28 Jan 2025

feedWordPress Planet

Matt: Boom & Deepseek

What an exciting time to be alive. I was hipped to Deepseek by Andrej Kaparthy's tweet the day after Christmas, it was clear then that something big had happened and that it was truly open source and open weights (not this fake Llama stuff). It's been fun to see the rest of the world catch up to it, and how radically accessible and deployable these models will be for people to hack on. I don't have any comment on public markets or stocks.

The other super inspiring thing today was Boom's first supersonic flight. It's worth watching the video. We're 4-5 years away from halving flight times with supersonic flight. In that same timeframe we might have something even more dramatic from SpaceX, like Houston to Tokyo in 30 minutes. Really cool to see the spirit of entrepreneurship and innovation around all of these things. It's tempting to get distracted by drama (WPE and legal battles), but there's such freedom and joy in just continuing to build, to engineer, to solve problems. I'm so grateful I get to do so every day with such incredible colleagues at Automattic.

28 Jan 2025 8:15pm GMT

Do The Woo Community: AI, WooCommerce Changes, and the WordPress Community in 2025 with Robbie, Robert and Marcus

In this Woo AgencyChat, the hosts discuss AI's role in web development, WooCommerce advancements, e-commerce simplification, and the resilience of the WordPress community amidst ongoing drama, highlighting their hopes for 2025.

28 Jan 2025 12:38pm GMT

Do The Woo Community: Do the Woo is a Media Partner for CloudFest 2025 and the Hackathon

We are excited to partner with CloudFest again, featuring over 8,700 attendees and 250+ speakers at Europa-Park from March 17-20, 2025.

28 Jan 2025 10:00am GMT

27 Jan 2025

feedWordPress Planet

Do The Woo Community: Reflections on the WooCommerce Releases from 2024 with Marcel and Mike

In this episode of Woo DevChat, Marcel and Mike discuss significant WooCommerce updates from 2024, AI's impact, and their personal goals.

27 Jan 2025 11:20am GMT

26 Jan 2025

feedWordPress Planet

Gravatar: Create Unique Avatars With Backgrounds and Stickers!

Has it been a while since you gave your Gravatar a fresh look? We just rolled out some fun new editing tools that let you remove backgrounds, add new ones, and decorate with stickers. Your avatar travels with you across the web - now it can show even more of your personality.

Background Magic

Take any photo and instantly remove its background. Drop yourself onto a beach, in front of a cityscape, or keep it clean with a solid color.

That quick selfie can now look like a professional headshot.

Sticker Time

Add some flair with our collection of stickers. From sunglasses to speech bubbles, you can layer on elements that match your style. Use the search feature to find the perfect additions.

How to Use the New Features

  1. Head to gravatar.com/profile
  2. Click on Avatars
  3. Upload a new photo or click the three dots to edit an existing one
  4. Look for the Background and Stickers menus
  5. Start creating!

Pro tip: Try the search button in both the background and sticker menus - you might find something unexpected and perfect.

Backgrounds come from Pexels and stickers from Giphy. Or you can upload your own.

Why Update Your Avatar?

Remember, your Gravatar shows up automatically on millions of sites like WordPress, Slack, and Zapier. It's the face you show the world across the web. With these new tools, you can make sure that face is exactly how you want it.

Share your new look with us on X or Bluesky - we can't wait to see what you create!

26 Jan 2025 4:30pm GMT

Gravatar: Enhance Your WordPress Blog: Create a Custom Author Page

Author pages contain information about a person who has written, edited, or contributed to an article. This usually includes things like their name, picture, short bio, social media links, and then a list of all their published posts on the same domain.

If you have a blog, it's generally always a good idea to have dedicated authors and pages to accompany them. This is important for many reasons, but one of the main ones is that it instantly improves the credibility of the content. It's one thing to read a technical piece written by a credible software engineer than an anonymous user with no name!

Author pages not only encourage users to read and interact with your content (because they know a real person is behind it), but they are also great for improving your search engine rankings, along with E-E-A-T (Expertise, Experience, Authoritativeness, Trustworthiness).

Now that you're convinced how important author pages are, you're probably wondering: "Is there a way to customize them, make them look better and more engaging?"

Absolutely!

To help you do just that, we've created this useful guide that will explore the different ways of customizing the author template in WordPress, show you how you can create a custom page, use template tags, and take advantage of tools like Gravatar to take your author pages to the next level.

Customizing the default author template vs. creating a custom page

There are two main approaches when it comes to improving your author pages: Customizing the default author page template and creating a custom author page from scratch.

Let's take a look at both methods.

Customizing the default author template

Before we dive into this, it's important to mention that there is a difference between the author of an article and the 'Author' user role that exists in WordPress. Technically, the author of a blog post can also be the administrator, an editor, a contributor, as well as an author. So take into account that when we mention author, we mean any person who has written the specific piece of content.

Now, with that out of the way, let's get into the default author pages. The information they include is the data of the specific user profile, which looks like this:

User information settings in WordPress

You can add information like names, websites, and bio, along with the profile picture linked to their specific Gravatar profile. If they don't have a Gravatar profile, their profile picture displays as a mystery person.

On the front end, the author page will look different depending on the theme of your choice. For example, this is how it would look with the Bloghash WordPress theme:

Example of the default author page in WordPress with the theme Bloghash

Customizing the default author template is suitable for minor changes and maintaining a consistent design across your WordPress site. By utilizing template tags, you can modify the default template regardless of the theme you're using, without the need for additional plugins or custom code.

The benefits of customizing the default template include:

However, there are some limitations to this approach:

Despite these limitations, customizing the default author template can be a quick and effective solution for those who want to make minor improvements to their author pages while maintaining a consistent design across their WordPress site.

Creating a custom author page

A custom author page gives you full control over the design, the amount of information, and how it's displayed, and it also comes with extra opportunities for user engagement. It's a separate page that is then linked to this specific user and shows up when you click on their name.

Unlike the default author page, you're not restricted to the information fields on the back end and can add virtually anything. For example, you can include customized links to guest post contributions, client testimonials, extra information about services, a donation block, share buttons, and much more.

The only possible downfall of these pages is that they require more effort to set up and maintain, and depending on your goals, you might need technical knowledge or external tools and plugins for the job. The payoff, however, is worth it.

How to use template tags to customize the author template

The design of your WordPress blog is defined by the theme you are using, and themes are made of different templates. Template tags PHP functions built into WordPress to fetch and display dynamic content allowing you to customize your blog and make the pages look exactly how you want them to.

In this next section, we'll guide you through the process of using template tags for author page customization, including code snippets.

Creating the author.php file

The first step is to check whether there is an author.php file in your theme directory and create one if that's not the case. This is the file you'll be using to customize the layout and the content of the author pages.

Basic template tags for author information

There are a couple of tags you can use to access author information, including:

Combining template tags with HTML and CSS

You can display this data on the frontend of your website using the echo command, like in the example below:

<div class="author-info">
        <h2>About the Author</h2>
        <p><strong>Name:</strong> <?php echo get_the_author_meta ('display_name'); ?></p>
        <p><strong>Email:</strong> <?php echo get_the_author_meta ('user_email'); ?></p>
        <p><strong>Bio:</strong> <?php echo get_the_author_meta ('description'); ?></p>
</div>

Using conditional statements

The is_author function introduces conditional logic, where you can check whether a page has an author, and display their information if it does. Use the following format:

<?php if ( is_author() ) : ?>
// Your code here if it returns true
<?php endif; ?>

This is ideal for sites with a very simple URL structure where, say, a landing page and a blog post would have the same structure.

Pair this with the get_the_author_meta() command to retrieve the author's ID and display their information on the frontend, as shown above.

Building a custom author page on WordPress through Gravatar integration

Gravatar homepage

Gravatar, a service built by Automattic, offers a powerful solution for creating feature-rich and dynamic author pages on your website with minimal effort. While WordPress already uses Gravatar profile pictures for users logged in with the same email, you can take this integration a step further by leveraging Gravatar's Profiles-As-A-Service REST API to import entire user profiles and create fully customized author pages.

For example, all the blog posts written by yours truly (me, Ronnie) have a link to my Gravatar page:

Example of author link in a Gravatar blog post

This is so that when people click on my name, they are redirected to my Gravatar profile where I've put all important information about myself.

Ronnie Burt Gravatar's profile

However, the benefits of Gravatar integration go beyond simply linking to an author's Gravatar page. By utilizing the Profiles-As-A-Service REST API, you can create custom author pages on your website that display information imported directly from Gravatar. This offers several advantages:

So, if you want to leverage Gravatar to build a custom author page, check out our documentation for developers.

Customizing the WordPress author box with Jetpack and Gravatar

One of the most important parts of the author's profile is their bio - it's what gives the article credibility and entices readers to check out more posts or even connect with the author. Besides ensuring it's written well, you can enhance the bio's design even further with the Jetpack plugin and its Gravatar hovercard integration.

Customizing author info with Jetpack

Jetpack homepage

Jetpack comes with many additional features, that allow you to customize and add new functionalities to the author pages.

First, it fully integrates with Gravatar to pull author information and update it automatically. Besides that, it lets you enable the display of the author's name and bio or their Gravatar profile on single post pages with all the information directly pulled from their WordPress profile.

In this example, we've added a Gravatar profile widget to the sidebar next to the blog post.

The Gravatar widget in Jetpack

With Gravatar Hovercards enabled, when people hover over the profile with their mouse, they'll see a mini version of the profile as a hovercard.

This is how it would look in our example:

Example of a Gravatar hovercard

You can easily enable that by going to Jetpack > Settings > Discussion and then enabling the option named "Enable pop-up business cards over commenters' Gravatars"

Enabling Hovercards in the Jetpack settings

There are many other customization options, especially with Jetpack widgets. Still, we recommend keeping it simple and not cluttering the page with too many elements, as this may overwhelm readers. As always, balance is key.

Transform your WordPress site with a stunning custom author page

Custom author pages are essential for showcasing your authors' expertise, fostering reader connections, and enhancing user experience. While there are various approaches to creating custom author pages on WordPress, integrating with Gravatar's Profiles-As-A-Service REST API is the most efficient and effective solution.

By leveraging Gravatar's API, you can save time and effort, ensure data accuracy and consistency, provide a seamless user experience, and boost your blog's SEO and E-E-A-T. Learn more about how you can integrate Gravatar with your WordPress website and begin your journey toward a more connected and personalized user experience.

26 Jan 2025 4:24pm GMT