WordPress Planet

March 16, 2025

Do The Woo Community: CloudFest Hackathon. Behind CMS Freedom with Patricia BT and Dennis Snell

Patricia and Dennis discuss their CMS Freedom project at the CloudFest Hackathon, aiming to simplify system transitions and preserve online content. They emphasize teamwork, learning, and the value of contributions beyond coding.

by BobWP at March 16, 2025 01:20 PM under Hackathon

March 15, 2025

Matt: Dalio & Benioff in Singapore

With the world changing so quickly, it’s hard to find alpha, but the best way is by following the brightest thinkers. This CNBC interview with Ray Dalio and Marc Benioff is good, but it’s way better if you go to the livestream about 25 minutes in and see the full discussion without the editing. You hear what these great thinkers actually think, rather than what an editor thought you’d enjoy. A little bit of friction gets you a lot more information.

by Matt at March 15, 2025 08:46 PM under Asides

Gutenberg Times: WordPress 6.8 Dev Notes, WP:25, new Blocks and sites — Weekend Edition 321

Hi,

This week I will feel a lot of FOMO as I had a chance to attend CloudFest but had to bow out at the last minute, to give my busted knee a rest. My doctor is convinced that I had overdone the walking in Manila and WordCamp Asia. So going to an amusement part and another trade show, would not be wise. Unfortunately, there are no live-streams to participate remotely. 🤷🏼‍♀️

Meanwhile, I have been testing WordPress 6.8 and although there are no new ones, the updates to existing features are amazing and make content creation so much easier. Next week on Tuesday, in time of Beta 3 release, I’ll publish the Source of Truth, while Anne McCarthy is on sabbatical. The release team started to release Dev Notes already. You’ll find the list below.

This week, I have many updates again in this edition. Enjoy!

Yours, 💕
Birgit

Tom Willmot, CEO of Human Made posted the WP:25 Recap: The Future of WordPress with links to the recorded session. WP:25 was a virtual conference, hosted by Human Made with some awesome speakers and panels. I wanted to highlight two of them:

Tammie Lister speaking on The power of FSE, in which she took the audience “through the incredible transformation Full Site Editing is bringing to WordPress. Tammie made it clear: FSE isn’t just another feature—it’s a fundamental shift in how teams build and manage content.”

Mary Hubbard, executive director of WordPress, and Noel Tock chat about what’s next for the world’s favorite CMS in the coming year. WordPress in 2025. “AI is reshaping the way we interact with content, and WordPress is embracing AI in every way, any way that can enhance it, without replacing the human creativity aspect. So I think this right now, we’re at a pivotal point, not just for what it means for open source, but actually, what it means for the project itself.” – Mary Hubbard.

You’ll find the other WP:25 sessions on this YouTube Playlist

Developing Gutenberg and WordPress

WordPress 6.8 release cycle is progressing as schedule to Beta 3 next week. WordPress 6.8 Beta 2 was released this week.

And a reminder to Help Test WordPress 6.8 to figure out if all features work as supposed to and report bugs. The instructions provided Krupa Nanda are excellent to get a head start on many things updates in WordPress 6.8

The first Dev Notes are now available on the Make Core blog:

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

In his latest post, How to disable and lock Gutenberg blocks, Bud Kraus takes you on a deep dive into content governance topic and how to provide guardrails to authors and enforce editorial guidelines for your site. It’s comprehensive coverage of the topic and includes explanation on how UI tools work as well as enforcing block locking with PHP and via theme.json.


ICYMI, After a longer beta period, GenerateBlocks 2.0 was released Mid-February with the aim of providing “fundamental changes to GenerateBlocks with a streamlined and robust system to make building fast and effective sites easier” Kathy Zant wrote in the announcement post Introducing GenerateBlocks 2.0: A New Era for High Performance Websites . The post also provides a migration path from version 1 to version 2 and outlines many changes for the plugin.


Diane and Yann Collet created a great resource at WP Gallery featuring beautiful websites designed with the Gutenberg Block Editor. It’s a fantastic place for inspiration.

Twentig also a creation of Diane and Yann Collet, was also updated last month. The plugin is a toolkit designer working on Block Themes and has over 25,000 users. It provides Starter content, more Gutenberg Blocks and hundreds of patterns. You can browse the changelog of the latest version on the Twentig website.


Bhargav (Bunty) Bhandari posted on X (former twitter) about his work on a new block to add LinkedIn-like work experience information to a site. With it, you can showcase professional experience, with option to add a title, company name, description. The plugin is on its way to the WordPress plugin repository, and it might take a few weeks to be released. Meanwhile, you can download it from GitHub repo.

Djordje Arsenovic created a Typewriter block, and it is now available in the WordPress plugin repository. Use the block to make text appear on the fronted as it was typed out on the old-fashioned typewriter machine.

Theme Development for Full Site Editing and Blocks

Is your theme.json getting too big? Iulia Caza, developer at Dekode, built an npm package called Create Theme JSON that lets you split up the theme.json into multiple files in a theme-json folder and the build script assembles it into your theme’s theme.json file, when ready. “It definitely makes development much easier and faster.” Caza wrote on LinkedIn.


Anne Katzeff published a new tutorial on how to add categories to a Block Theme menu and guides you through accessing the menu editor and adding custom links for categories by copying their URLs from the WordPress dashboard. Katzeff also demos the steps in this YouTube video


Ryan Welcher worked on a new WordPress block theme for the Block Developer Cookbook during his live stream. You can watch how he creates a new skin for his theme (aka Style variation) and also add different block style variations. Welcher also prompts Cursor AI to make changes. The code is available on this GitHub repository.


Joshua Siagia announced the arrival of WindPress – a platform-agnostic Tailwind CSS integration plugin for WordPress that allows you to use the full power of Tailwind CSS within the WordPress ecosystem, streamlining workflows for developers. It supports Tailwind CSS v3 and v4, offers features like autocompletion, HTML-to-native conversion, and class sorting, and ensures lightweight performance with optimized CSS caching. Seamlessly compatible with popular builders like Gutenberg and Bricks, it simplifies customization while maintaining speed. WindPress is ideal for developers seeking efficient Tailwind CSS integration in WordPress projects. It is now available in the WordPress plugin repository: WindPress

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

Building Blocks and Tools for the Block editor.

Save the date! Nick Diego and Ryan Welcher will demo on March 19th, 2025 How to build incredible WordPress Blocks with Cursor AI on YouTube Live hosted by Jamie Marsland. They will explore the power of AI in crafting exceptional WordPress blocks. In this session, you’ll discover practical techniques, pro tips, and AI-driven tools to enhance your block-building skills and streamline workflows. Whether you’re a developer or looking to expand your WordPress expertise, this is your chance to unlock new possibilities for your WordPress site!

Bart Kalisz, JavaScript Engineer at WooCommerce announced in his post WooCommerce Blocks client files relocated to complete monorepo merge. As of March 5, 2025, WooCommerce Blocks client files have moved from plugins/woocommerce-blocks to plugins/woocommerce/client/blocks, completing the monorepo merge initiated in December 2023. This change enhances codebase consistency and repository organization. Developers with existing pull requests need to rebase their branches. End users will not experience any functional differences. The build process remains the same, ensuring a smooth transition.


Do you want to jumpstart adding AI to your site? Felix Arntz has you covered with his plugin AI Services from the WordPress repository. The plugin provides a “central infrastructure that allows other plugins to make use of AI capabilities. It exposes APIs that can be used in various contexts, whether you need to use AI capabilities in server-side or client-side code.” The latest update comes with AI image generation, starting with OpenAI’s DALL-E and Google’s recently published Imagen models! The plugin page also lists a few code examples on how to integrate it using PHP or JavaScript.


Developer Advocates, Brian Coords and Nick Diego were experts on this week’s InstaWP webinar: Building WordPress Plugins with AI with founder Vikas Singhal to “reveal game-changing insights for leveraging AI to build powerful WordPress plugins.” Both developers demo’d their workflow programming with Cursor AI.


This post Introducing Preview Sites: Pushing the Limits of Collaboration with Studio, Antonio Sejas catches us up on the latest features of Studio, WordPress’s local development tool. “Demo Sites” are now “Preview Sites” with increased storage (2 GB) and more sites allowed (10). Personalized URLs are introduced, and sites remain active for seven days after the last update. These changes enhance collaboration and testing for Studio users.


Geoff Graham built Baseline Status in a WordPress Block and published a blog post about his approach, from scaffolding, settings, supports, rendering front and back end and styling. The plugin is available on the WordPress repository
Baseline Status

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: Wasserburg am Inn – Photo by Birgit Pauli-Haack


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.

by Birgit Pauli-Haack at March 15, 2025 05:15 PM under Weekend Edition

March 14, 2025

Do The Woo Community: Do the Woo Friday Shares, March 14, 2025

This weeks curated shares from the community.

by BobWP at March 14, 2025 10:28 AM

March 13, 2025

Gravatar: SEO-Friendly Author Bio Pages: Essential Tips

If you’re an author, chances are you’ve come across terms like E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness). These concepts are critical for improving your visibility in search engine results, but putting them into action can feel like a daunting puzzle. Whether you’re a book author, a blogger, or someone with a diverse portfolio of written work, creating a strong web presence is essential to establishing your authority.

Author SEO goes beyond just writing great content – it involves technical elements like schema markup and consistent author profiles to signal credibility to search engines. But how do you bring all these moving parts together to create an effective strategy?

In this guide, we’ll explore actionable steps to optimize your author bio pages and build a consistent online presence. From Gravatar integration to schema markup, these techniques will help you strengthen your E-E-A-T signals and achieve better search rankings. 

Building author E-E-A-T through optimized bio pages

Establishing E-E-A-T is essential for authors striving to improve their visibility online. According to Google’s Search Quality Rater Guidelines, high E-E-A-T pages are deemed more trustworthy, which can directly impact rankings.

Your author bio page is a prime opportunity to strengthen your position. Here’s how to optimize each component:

  • Experience: Share milestones like years of writing, notable projects, or awards. This helps showcase your firsthand knowledge, making your expertise relatable and credible.
  • Expertise: Highlight qualifications such as degrees, certifications, or industry recognition. These reinforce your authority on your subject matter.
  • Authoritativeness: Link to your published work on reputable platforms, which positions you as a trusted source. Tools like Gravatar ensure your online presence remains consistent.
  • Trustworthiness: Build trust by including testimonials or reviews. A professional headshot and clear contact details further enhance reliability.

Keep in mind that an optimized bio page is more than just an introduction to your readers – it signals your credibility and authority to search engines and readers alike. 

Now that you have a strong bio page in place, the next step is integrating tools like Gravatar to maintain consistency across all platforms. 

Creating consistent author profiles with Gravatar

Gravatar homepage

Being consistent across all your digital profiles can help you build a solid and trustworthy online presence, and Gravatar simplifies this process. This platform links your profile picture and key details – like your name, bio, and website – to your email address, ensuring that your information is automatically updated across supported websites.

Example of a completed Gravatar profile – Ronnie Burt

For authors, Gravatar eliminates the hassle of managing profiles manually on multiple platforms. Whether it’s a WordPress blog, an online portfolio, or a comment section, Gravatar ensures your professional identity remains uniform, building trust and reinforcing your E-E-A-T.

Setting up Gravatar is straightforward: Create an account, upload a professional photo, and fill in your details. 

Example of the Gravatar profile dashboard – Editing the About section

From there, Gravatar takes care of the rest, providing flawless integration and a polished, consistent online presence. This not only saves time but also enhances your credibility, making it an essential tool for any author looking to strengthen and monitor their digital footprint.

WordPress integration and cross-platform syncing

According to W3Techs, “WordPress is used by 62.0% of all the websites whose content management system we know. This is 43.6% of all websites.” So, it’s no wonder that so many authors, writers, and contributors go with WordPress as their platform of choice. 

Gravatar integrates perfectly with WordPress, automatically displaying your avatar across the WordPress ecosystem wherever your email address is linked, such as in blog posts, comments, or author pages. This standard integration helps maintain a consistent online identity with minimal effort.

However, for authors looking to go beyond the basics, the Gravatar Enhanced plugin offers additional features. Unlike the default Gravatar setup, which only pulls the profile picture, this plugin provides greater customization options, allowing you to display more detailed author profiles, including links to your social media and published works. 

Example of a customized profile block with the Gravatar Enhanced plugin

You can also control how your Gravatar appears on various sections of your WordPress site, such as post bylines and author widgets.

On top of that, with Gravatar you can create multiple profiles each linked to a different email address, and you can pull any of these easily with the Gravatar Enhanced plugin. This is invaluable if you write across different genres or target audiences (more on that in a second). 

If you’re tech-savvy or have the budget to work with a developer, and have many people contributing to your website, you can also take advantage of the Gravatar REST API. This gives you more flexibility and granular control over exactly what data gets imported and displayed on the website. It also makes it much easier for guest authors to contribute – their Gravatar profile information will be automatically imported. 

This applies to every single platform that has integrated Gravatar, including GitHub, Slack, OpenAI, Figma, Zapier, and many more. 

Logos of websites that have integrated Gravatar

Managing multiple author identities

For authors who write across different genres or target diverse audiences, managing multiple online identities can be a challenge. Gravatar simplifies this with its ability to associate multiple email addresses with unique profiles. Each profile can feature a distinct avatar, bio, and contact details, allowing you to tailor your online presence to specific audiences or platforms.

To use a different profile with Gravatar Enhanced , you just need to put the email address corresponding to that profile. 

Importing a Gravatar profile through email and the Gravatar Enhanced plugin

For instance, if you write technical guides under one pen name and fiction under another, Gravatar ensures your profiles stay separate and relevant. By linking each email to a unique profile, you maintain consistency and professionalism for both identities without any crossover confusion.

This flexibility helps you maintain your E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) across different niches, ensuring that each identity aligns with its intended audience while reinforcing your credibility.

Technical SEO essentials for author pages

Optimizing the technical side of your author pages can help your site rank well in search engine results and provide an easy and memorable user experience. Here are some key areas to focus on:

Page speed and mobile responsiveness

Fast-loading, mobile-friendly pages are a must. Use tools like Google PageSpeed Insights to identify performance bottlenecks and ensure your site is accessible on all devices. Reasons for a slow website include: 

  • Large image files – High-resolution images that aren’t optimized can significantly increase load times.
  • Too many HTTP requests – Each image, script, or CSS file requires a separate HTTP request, slowing down the site.
  • Unoptimized JavaScript and CSS – Heavy or poorly written scripts can delay rendering, especially if they aren’t minified or compressed.
  • Lack of browser caching – Without caching, users have to download site elements repeatedly, even if they’ve visited before.
  • Slow server response time – Poor hosting or high traffic can lead to delays in how quickly the server processes requests.
  • Bloated plugins – Excessive or poorly coded plugins can slow down the backend and frontend of the site.
  • Unoptimized database – A database cluttered with unnecessary data, like old revisions or spam comments, can slow query times.
  • High traffic without proper resources – A sudden spike in visitors can overwhelm your hosting plan, leading to slowdowns.

Whatever the issue is, make sure you fix it on time since most users access the web via mobile, a responsive, clutter-free design helps with usability and improves your search rankings. 

Schema markup for author pages

Implementing schema markup helps search engines understand your content better. Use the “Author” schema to display rich snippets, such as your name, bio, and image, directly in search results. 

Example of an author page on Google Search Results

Canonical URLs and structured navigation

Ensure each author page has a unique, canonical URL to prevent duplicate content issues. Structured navigation, including breadcrumbs, helps search engines and users understand your site’s hierarchy, improving crawlability and the user experience. They are also essential for screen readers and users who only use keyboards to navigate. 

Secure and accessible design

A secure site (HTTPS) is critical for building trust with both users and search engines. Additionally, ensure your content is accessible to all users, including those with disabilities, by adhering to Web Content Accessibility Guidelines (WCAG). Here are some of the main areas you need to consider: 

  • If you have a shop for your books, events, or services, make sure that users can successfully complete a purchase with any assistive technology, including screen readers and keyboard navigation. 
  • Create functional and descriptive alt text for your images and files. Users should be able to understand the main idea behind each image and if it’s only decorative, just leave the alt text tag empty. 
  • Make sure your link texts make sense – “click here to book a spot for my book signing” is much better than just “click here.”
  • Use accessible fonts and ensure that users can scale text up to 200% without the loss of functionality and content. 

Meta descriptions and optimized headings

Every author page should have a compelling meta description and properly structured headings (H1, H2, etc.). These elements improve click-through rates and help search engines identify the page’s main focus. They are also essential for accessibility: The meta descriptions and titles are what the assistive technologies will read out loud to people who use them and want to search online. 

Implementing author schema markup

Schema markup helps search engines understand the structure and content of your author pages, boosting visibility in search results. By implementing author-specific schema, you can enhance your E-E-A-T signals, making your pages more appealing to both users and search engines.

Example of a rich snippet of an author website

For blog authors, use the Article schema to mark up your blog posts, including details like the headline, author name, and publication date. For book authors, the Book schema is ideal. It highlights properties like the book title, ISBN, and author information, making your work easier to find​.

Example of a book Google snippet

You can then implement the schema on your website with the Google’s Structured Data Markup Helper or WordPress plugins like Rank Math and Yoast. You can tag relevant sections of your page, such as your name, bio, and links to your published works, and generate JSON-LD code for seamless integration​. 

To get the most out of schema markup, make sure you: 

  • Include key details: Author name, profile image, and links to verified profiles.
  • Stay consistent across platforms by syncing with Gravatar, which adds a professional touch to your author bio.
  • Validate your schema with Google’s Rich Results Test to check for errors and ensure all required fields are present.

Measuring and improving author page performance

Optimizing your author pages doesn’t stop at implementation – you need to measure their performance and refine them over time. Here’s how:

Key metrics to track

  • Organic traffic – Use tools like Google Analytics to monitor how many users find your author pages through search.
  • Bounce rate – A high bounce rate could indicate poor user experience or irrelevant content.
  • Time on page – Longer time spent suggests that visitors find your content engaging and valuable.
  • Search rankings – Track keyword rankings for your name, book titles, or blog posts using tools like Google Search Console, Ahrefs, or SEMrush.

Improving author page performance

  • Enhance content – Ensure your bio includes relevant keywords, links to authoritative publications, and an engaging summary of your work.
  • Optimize for mobile – Many visitors will access your page from mobile devices, so ensure your layout is responsive and user-friendly.
  • Leverage internal linking – Link to related blog posts, books, or interviews to keep users engaged and improve site navigation.
  • Update regularly – Add new publications, awards, or noteworthy achievements to keep your page fresh and relevant.

Use heatmaps and session recordings

Heatmaps (e.g., from tools like Hotjar) show which parts of your page users interact with most, helping you refine layout and content. 

Example of a Hotjar heatmap

Session recordings provide deeper insights into user behavior, highlighting any obstacles they encounter.

Enhance your author authority now

As AI-generated content continues to flood the web, a verified and consistent author profile is the best strategy to help you stand out and maintain reader trust. A strong, recognizable presence builds credibility and helps search engines and audiences alike see you as a reliable source.

With the tips outlined in this article, you’ll lay a solid foundation for optimizing your author website. Start with a polished bio, leverage schema markup for better search visibility, and use Gravatar to maintain a consistent online identity. With its “Update Once, Sync Everywhere” functionality, Gravatar ensures your avatar and profile details are synchronized across platforms, saving you time while keeping your branding professional and cohesive.

The key to successful author SEO lies in the trinity of a professional bio and website, technical SEO, and an up-to-date Gravatar profile. Ready to boost your authority? Learn more about Gravatar today!

by Ronnie Burt at March 13, 2025 06:49 PM under Gravatar Guides

Do The Woo Community: Meet Some of Our Hosts at CloudFest 2025

Make sure and say hi to some of our hosts if you are attending the CloudFest event or the Hackathon.

by BobWP at March 13, 2025 12:03 PM under Hackathon

Do The Woo Community: A New Show, Content Sparks, with Regular Host BobWP

BobWP introduces "Content Sparks," a show focusing on content creation insights, featuring tips from his 18 years in the WordPress space combined with my hosts experiences.

by BobWP at March 13, 2025 09:27 AM under Content

March 12, 2025

WPTavern: #160 – Rahul Bansal on Success in Enterprise WordPress

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, creating a successful business in enterprise WordPress, and working to foster the WordPress community.

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 Rahul Bansal.

Rahul is the founder and CEO of rtCamp, a large agency that specializes in enterprise grade WordPress projects. He began his journey quite differently, starting as an individual blogger back in 2006, discovering WordPress in 2007, and gradually transitioning from being a publisher to a freelance developer, before founding rtCamp in 2009.

Today, rtCamp is an enterprise grade WordPress consultancy agency operating globally and trusted by clients such as Google, Meta, Automattic, News UK and Al Jazeera.

Rahul sheds his light on working with enterprise clients in the WordPress space. Many of us are familiar with WordPress in the context of small businesses and blogging, but the enterprise space demands additional layers of security and scalability. Rahul explains the factors that set enterprise projects apart, and why meticulous code reviews, and security audits are essential when working at this level.

He talks about the opportunities in the enterprise space, recounting how rtCamp initially stumbled into enterprise level projects, not even realizing their potential until a client’s high expectations led to a decision to market themselves as an enterprise agency.

We also discussed the role of WordPress in enterprise environments, from why Gutenberg has become a credible selling point due to its powerful editing capabilities, to how the platform’s flexibility supports varied enterprise needs.

Rahul also gets into the importance of positioning. How historical context offers advantages, and the expanding market that makes WordPress a compelling choice for large clients today.

Towards the end, we explore rtCamp’s innovative intern program, aimed at growing the WordPress talent pool, and the way they’re contributing back to the WordPress project, a win-win for the business and the broader community.

If you’ve ever considered what it takes to work with WordPress at the enterprise level, 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, Rahul Bansal.

I am joined on the podcast today by Rahul Bansal. Hello.

[00:03:47] Rahul Bansal: Hello.

[00:03:48] Nathan Wrigley: It is very nice to have you on the podcast today. We’re going to talk about the enterprise, which I confess is something that I only really know about because people talk about it. I’ve never worked in the enterprise, I’ve never worked with enterprise clients. So Rahul is here. He’s very much in the enterprise as you’re about to find out, and he’s going to educate me all about that.

So Rahul, I wonder if you wouldn’t mind just for a minute or two minutes, just tell us who you are, what you do in the WordPress space, where you work, your position there, and so on. A little potted bio.

[00:04:18] Rahul Bansal: Currently I am founder and CEO of rtCamp, which is a large agency specifically dealing in enterprise grade WordPress projects. I started quite differently, like I started as a individual blogger, back in 2006.

In 2007 I found WordPress. I started developing with WordPress in 2007. And slowly from being a publisher, I become freelance developer, and then around 2009 rtCamp started. So I’ve been with rtCamp for the last 16 years.

[00:04:46] Nathan Wrigley: That’s been quite a journey. I see the name rtCamp everywhere. And we should just say, so it’s spelt, lowercase r, lowercase t, and then Camp with a capitol C, a m p. Go and Google that, and have a look at what the team over there doing.

How big has the team grown to? How many employees, staff do you have over there now?

[00:05:05] Rahul Bansal: So currently we are 230 people, all spread over.

[00:05:08] Nathan Wrigley: That is truly an enormous agency. So bravo for growing that. That’s really incredible.

The first question that I want to ask though is, when does normal WordPress become enterprise WordPress? At what point do we cross the Rubicon where a site is, I don’t know, big enough, or your agency is working with a different type of client? Can you define what you think that means? And I’m sure that if you’re on the cusp of being an enterprise agency, this is something that, you know, may be slightly confusing.

[00:05:37] Rahul Bansal: Firstly, there is no formal definition to that. Many agencies believe they’re serving enterprise space when they’re not. Some people are actually serving enterprise space, but they don’t realise it.

So in my opinion, it’s where the requirement changes a lot. Like, for example, if we’re building a small WordPress site, which I don’t consider as an enterprise site, we will be tempted to pick first theme and plugin that matches our need, like if it works, if it gets a job done, that’s it.

But then in enterprise space, there is a lot of security and scalability concerns. These two concerns are very big. Something might be working all right, but then when you look at the code, you realise that there’s going to be a security issues, or there could be scalability issues. Many times, indy developer person, they design small WordPress plugins. They don’t have data or big enough site to test it on a large installation. So those things are not tested on really high traffic website. So enterprise can mean really high traffic website, with a lot of scalability requirement.

On the other hand, the traffic can be less, but the security requirement can be enormous. Consider the White House website. It was on the WordPress with the previous administration, and it’s again, on the WordPress with the new administration. So in both cases, I don’t think White House, like a website we can classify as a very high traffic website, but it is a very sensitive website.

It would be a lot embarrassing if that site gets hacked. So every piece of code that goes into White House website, which agency is working on it, will be thoroughly checked for security attack, for audit, for all the compliances. And this additional efforts is what makes it enterprisey, in my opinion.

[00:07:12] Nathan Wrigley: Okay, so it’s not necessarily the size of the client, or the fame, for want of a better word, of the client. It’s more about the kind of work that you’re doing in the background. So custom code largely, because you simply at that scale cannot have something off the shelf.

[00:07:28] Rahul Bansal: So we can have things off the shelf. The thing is, you cannot just take it and use it. You still have to own it in that sense. Like, for our clients also, we go and use many things from WordPress plugin directory. But then when we put it on this website, it is kind of like signed by us. So it’s like we have to verify, even if it is not coded by us, we have to verify line by line that it is following best coding practices, database queries will scale with high traffic, if it is a high traffic website.

There are many checks and balances in place. So no matter if you are doing in-house, like as a custom coding, or we are buying a premium plugin or using a free plugin, everything has to go through certain checks. And those checks are very expensive to do, because that’s a human labor. You have to literally go through things line by line. And in many cases, you have to put extra efforts to make it scalable with their existing system.

Because usually a large enterprise won’t use just a website in silos. It’ll be part of multiple system like authentication system, where if an employee joins a large organisation based on some rule, they might get automatic access to their website. Likewise, if they leave organisation, their access should be automatically revoked, or they have some CRM integrations, data integrations, some kind of asset, like digital asset management solution integration.

So all these have to be connected, and this all need to work together. So a lot of effort goes in doing these extra things, which are either don’t exist for small websites. So, enterprise website that I’m talking about, this can be really unknown website. We have a client which is basically a government public origin fund. Common people don’t even know about them, but they basically want pretty much all the big companies we know. Like, they have stake in all the big companies. Their asset is something like $400 billion in under management.

Most people don’t even know that company. But then it’s very sensitive because that money they’re managing is public money, it’s not like VC fund. It’s actually state reserve. Now, seriousness, we need to demonstrate in the security is very high, because if something gets hacked or somebody uploads the wrong investor report or something like portfolio report, it can have a lot of consequences.

[00:09:32] Nathan Wrigley: It kind of sounds to me as if the assurance that you are giving an enterprise client is basically that what we’ve built is, as far as we can tell, it’s bulletproof. We’ve gone through it line by line. We may have custom coded bits and pieces, but certainly the bits that we didn’t custom code, we are totally guaranteeing that this is going to be robust.

And also it’s sounds a bit like, if a client at an enterprise level approaches you and they say, can you do this? Your answer is yes. Basically, yes, we can do it. We can do it with WordPress. There may be a cost, but we can do it. There’s almost no scenario where a client would come to you and say, can you do this, forget the money, can you do it? The answer’s never no. The answer’s always going to be yeah, yeah, we’ll figure it out.

[00:10:15] Rahul Bansal: So that’s the thing, like if the budget has no limit then there is no limit on technology. Most often, like even where enterprise agency, WordPress has this large spectrum. So we end up with a lot of low quality leads, where somebody knocks on an enterprise agencies’ door and they really have budget constraint. They really want something really good out of the box, but they don’t want to pay for it. Or they don’t want to pay as high as it’ll require to deliver that kind of solution.

For some enterprises, budget is no limit, but then we try to be mindful of resources. For example, many enterprise agencies, including us, if you go to their GitHub account, they would have list of published themes and plugins. Most commonly plugins, themes rarely are used off the shelf. So we will build these plugins to ensure that the cost of rebuild project is less, like if we have to deliver another project, we try our best that we reuse as much as possible.

And that’s the open source spirit, that the entire WordPress committee follows. We use many times solutions that are already put in open source by our competing agencies. They also use our solution. So that’s where the enterprise solution with WordPress is also affordable. The right enterprise client that we target, usually have higher budget than we would need to develop because we are competing against a lot of experienced managers, which are very expensive, super expensive.

And when I is super expensive, I’m just talking about licensing fees. Before you hire an agency to write custom code for you, you have already paid a lot of money just for the right to use the software. With WordPress, that right to use costs zero. And then all the nice agencies in WordPress space, big, small, no matter what size they are, try their best to reuse existing solutions, to bring the cost down.

So enterprise WordPress, relatively, cost less than other enterprise CMS, but then it certainly costs a lot than building a small website. Like, you cannot go to an enterprise agency and expect in $500 your site to be built perfectly, because the requirement gathering phase, like talking to all stakeholders and understanding all the solutions they use inhouse can take like many days.

[00:12:15] Nathan Wrigley: So you may have answered this question just now with what you’ve just said. I feel that you’ve definitely gone into this territory, but it sounds like there’s a lot of line by line checking of everything. So for example, if you use a plugin off the repo, you’re going to go through that one line at a time. And you said this can be an expensive process. You’ve also said that obviously there’s benefits of using WordPress because you can take things that other people have used and so on.

But I guess at some point there’s got to be some sort of tipping point where you think, okay, WordPress is going to be good for this project, but it might not be good for that project. Is it always WordPress for you? Do you always lean into WordPress, or does there come a point where you say, do you know what, with the custom things that this particular client wants and what have you, lets just build the thing ourselves, let’s not rely on the CMS, or do you always lean in on WordPress?

[00:13:01] Rahul Bansal: Maybe it’s the nature of our positioning that we rarely get things that we cannot do in WordPress, so we always do things in WordPress. The boundary varies with how much off the shelf WordPress we’ll use, and how much custom we’ll use. In one of the project, I remember there was a specific data crunching process that we needed to build. And we felt that it’ll be better if it is built as a microservice and run independently.

So we built that in Python, but then it was talking to WordPress REST API. So that freedom we have from client, for example like that microservice, that microservice was never visible to any of the client’s editorial team. Everything they were doing, their only interface was WP admin. There was no second login or no second interface to them. It was just something was running on some server and magically data was going inside and outside WordPress.

And that’s the power of WordPress. It has so many APIs to communicate with outside world, like rest API, GraphQL, and even from the traditional XML-RPC. That WordPress can coexist with other systems very nicely. And that’s where we never face that, can we do this on WordPress or not? It’s like, can we do everything on WordPress, or do we need to put some minor things outside WordPress?

And those decisions are not the engineering limitation. Like, that microservice, we could have put it in WordPress also, but we felt that its architecture was more suited for independent microservice. That was the right call, it turned out to be right call. Much later that microservice grew independently.

[00:14:26] Nathan Wrigley: If we rewind the clock to the beginning when you were just beginning with WordPress and beginning the agency that ended up being rtCamp with your 230 odd employees, did you intend for what’s happened to happen? Did you always know that you wanted to grow something to the point where it became, air quotes, enterprise with many, many employees, or did it just evolve over time unexpectedly?

[00:14:49] Rahul Bansal: Yeah, it all happened unexpectedly. Like, I started as a professional blogger. I used to make money from advertising, affiliate marketing. So it’s like, I wasn’t doing anything remotely related to agencies.

So one thing led to another and then I started freelancing. Then even after freelancing, when I started rtCamp as an agency, because I was coming from bloggersphere, most of my initial client were bloggers, like independent bloggers. Somebody wanted a theme, somebody wanted a plugin, somebody wanted a sidebar, which sidebar just used to be a lot more popular in those early days of blogging. Like, people used to have MySpace, like experience on the web, like lots of widgets, email submission form, this pop up.

So in fact, the first enterprise client that walked into our door, that’s why I said like many agencies don’t even realise when they mingle with enterprise space. I kind of felt very irritated because they asked so many questions. They got our reference from LinkedIn. We had zero, we were not even using enterprise word anywhere in our branding, marketing, anywhere at all. But back in 2010, also, we made a good name for ourselves.

So anybody who shouted, hey, any WordPress references, our name used to pop up on social media. So we got that. And they sent us a very large procurement checklist, which we never heard of. All of our projects were like email exchange, two, three emails, money via PayPal, and emails used to be contact. Like, whatever you committed on email is the contract.

And suddenly there comes like this long PDF, Excel sheets with check boxes. Do you have a data storage policy? This policy, that policy. If we end up filling this, we’re not going make any profit with this project. So then one of my teammates said, let’s price in that. Let’s price in and see if they can afford it. So we literally added another zero to our pricing, literally like 5 times, 10 times. And we said like, hey, this is our minimum, do you want to go ahead?

I said, sure, like this is peanuts. And they were worried like, do you understand the project? You are quoting very less, your starting point is very less than our internal budget. So they came to our office, they were based in India. Luckily they were in the same city. They came to our office to audit us physically. They put like remarks like, you don’t have a fingerprint scanner in your biometric sensors in your office entry. There is no employee log.

But we are not storing any of your data. So this office is not the building where your data will reside. Your data will reside on AWS, or all those cloud servers. And then they got convinced. WordPress was very small then, and we were the only known agencies, which was fully committed to WordPress at that point. So they didn’t have choice two, three, so they kind of crossed the fingers and gave us that project.

It took six months to close. I was very pessimistic. It’s only after two, three years that we realised that they’d become our largest client by a huge margin. All my blogger friend put one side, and this single client, one side. And that revenue was growing very nicely, year on year. Renewals, they had this retainers, every year they were renewing without asking questions.

So I realise that it’s very hard to win these big clients, but once you are in it becomes very smooth journey, henceforth, like after that point. And then I think 2014 around, after two, three years data, when I saw that this client was consistently, for the last three years in a row, our biggest client. Zero sales effort, zero account issues, no negotiation on pricing, and everything was smooth.

So then I thought like we should go in to some enterprise space, and luckily around that time I had a call with Chris Lema. Chris Lema used to be available for consulting calls on Clarity. I’m not sure if that service is still around. And I still remember it was exactly 33 minutes that I talked to Chris. He repositioned rtCamp. In 33 minutes he gave me some amazing breakthrough idea.

And after that call, first time we told ourselves, we are enterprise WordPress agency from today. Until 2014 we were not identifying ourself or branding ourself as an enterprise workplace agency. That moment was the first time when we put in bold letters on our homepage, in SEO Meta, everywhere we added, we are enterprise, enterprise, enterprise WordPress.

[00:18:35] Nathan Wrigley: Can you remember that moment? So if you cast your mind back, when you added the zero and sent it, and there was obviously some suspicion in your mind that nothing’s going to come of this or what have you. Can you remember the feeling? So it’s an odd question because I’m asking you about your feelings, but can you remember the feeling when they came back and said, oh yeah, this is not as expensive as we’d imagined? That really must have opened up an entirely new world for you.

[00:19:00] Rahul Bansal: Yeah. So firstly, it was very unexpected because we were selling like WordPress projects for $100, $50, $500. The biggest was $1,000. We still remember we built a complete BuddyPress plugin for $900. And we were like so happy when that client sent us $100 tip. He rounded up to $1,000 and we were partying, like with that extra $100, we throw a party to our team.

And suddenly this client comes and they said, $5,000 is okay? Are you kidding me? Because they sent so much data I didn’t want to fill in, so I just thought, let’s just give them a number and they will walk away. We’ll not appear as a company who didn’t want to fulfill their data request. I thought, I will give them a reason to walk away, but then it didn’t walk out.

Initially I was still skeptical because they really demand too much data. Just imagine, we were like some 20 people agency at that time, and we spent three to six months in back and forth sales call. We didn’t have typical sales team at that point. Writing those long answers. We were not even understanding questions. The problem was not that we didn’t want to give data or we didn’t take security seriously, there were things that we never heard of.

It was all like foreign language to us. What are they asking? Why do they want to do that? I was not expecting lifetime revenue, that concept was not in our books then. So it was project, money in, money out, end of email, site goes live. Then the recurring revenues hosting companies. We were not into selling maintenance contract.

So it was a project kind of thinking like big, big economy mindset. So even with 5,000, I thought like, the amount of effort they’re putting us, we won’t be left with any decent margin after this project. And that was a true case. For first year there was not much margin left because they had put us through a lot of work to fulfill that project. And then we realised we underquoted after that also, because when the data, we had to talk to their Microsoft vendor. They were using Microsoft SharePoint. There were many rough edges that we had no idea could happen to us.

In year one, they were the highest revenue, but project was in loss. It’s only a year, two, three, it was very good profit. And then we have the strategy that we call now land and expand. Land big accounts, no matter whatever price point you wanted to do, go aggressive, and then once you are in, then you spread within the organisation.

[00:21:08] Nathan Wrigley: Oh that’s an interesting insight. So land and expand. Land the client, the big fish, if you like, with the knowledge that if you maintain the relationship over many years, the profit can build up. Not necessarily year one, but maybe a bit in year two, and year three, and year four, it’s beginning to mature.

And, it sounds like such an interesting story. And, again, I’m going to rewind back to before 2014, so before you added enterprise to your website and have you. Do you think if you had begun your journey today, that you would have the same capability to expand in the same way? Because it feels like there are now quite a few players. Perhaps when you began that was less of the case. You were competing in a much less crowded marketplace.

But it feels like everybody’s intent now is to become an agency which can call itself enterprise. And I’m imagining that you got your foot in the door at a really nice time where you became a name that everybody could trust, and the recommendations come in because of prior work, but maybe that would be more difficult now.

[00:22:08] Rahul Bansal: The market is much bigger now. In fact, just imagine WordPress market share. When we were building the first initial websites, there was not even custom post types that were present in WordPress. So all the WordPress plugins, we used to do a lot of hacks. There was not standardisation. So a lot of things happened with WordPress as a platform. WordPress evolved. The market share has become so big. It’s easier to sell. We have so many examples like from White House to large publishers. And globally, it’s not like just the American companies are using WordPress. India’s second largest publisher also uses WordPress. So does Al Jazeera in Qatar.

So there are many big websites all over the world so it makes WordPress easy to sell. The market is big. There is a precedence where you can pitch somebody, this is WordPress used by so and so. I believe that no matter which lead you are dealing with, so if you have a lead from a certain industry, a certain geography, you will find a WordPress success story in their geography. You will find WordPress being used by your prospect’s competition. That makes it easier to sell WordPress.

So, yeah, the competition is more because opportunity is bigger. The pie is a lot bigger. Otherwise we would’ve stuck to the same size. Every year we are adding more people because we are able to get more work for them, even with these new agencies coming up. In fact, it’s easier to build WordPress agency, or any kind of enterprise grade agency now, because the recipe is quite clear. Because we can look at how other agencies are doing and you can take some lessons from them.

At that time we had no idea. Like, in fact, we didn’t have the idea that we should position ourselves enterprise grade agency, that was the call with Chris. Before that call, we had no idea that we should be labeling ourselves as an enterprise grade agency.

[00:23:42] Nathan Wrigley: If clients approach you, and it sounds like this may not be the case. It feels like people are approaching you because you build WordPress, not inquiring whether or not you would do a WordPress project for them. What are the one or two bits that you always bring out when a client says, well, why would we go with WordPress? What are the one or two top line items which you think, okay, if we’re going to build you a website, we’re going to choose WordPress, and here’s the best reasons at enterprise? So we’re not talking about a mom and pop store, that it really doesn’t matter if it goes down a bit. What are the one or two things which you bring out when an enterprise client wants to know why WordPress?

[00:24:18] Rahul Bansal: First we want to reassure them that WordPress is the right platform. So this is a difference between a product company and agency. A product has a landing page, which is more similar, it gets us to a lot of people. But an agency pitch is tailored for every client, every prospect. So our first goal is to find competition. So which are the competitors for this particular client, prospective client, and see if they’re using WordPress. If your competition is using WordPress, you will feel a lot more comfortable going after it, because nobody wants to be first, especially in large enterprises.

Another way we define enterprise is that, when you are not buying from out of your pocket. In a large organisation, your job is not to save the money or find cheapest solution, your job is to deliver result so that it can go very nicely in your annual review report. I still believe people, especially in enterprise, are looking for safety as a first because they know that they have budget to build anything under the sun.

So usually we say less like, WordPress can do this, WordPress can do that. Because for everything that WordPress or any platform doesn’t do out of the box, they have budget. What they need to know is that it’s secure, it’s safe, it’ll scale well. And if some government approaches us, so we show that public sovereign fund, that they’re managing. So that client has a special permission with us, like we cannot refer them publicly, that government agency, but we can refer them to other government agencies in private conversations. So that is how we convince like, okay, this is similar people to you who are using WordPress.

And I think safety is still the first thing that people are looking for because, it’s not even WordPress, it starts with open source. There is something, somebody did some marketing where people believe or have this misconception that open source will be easy to hack, because you can see the code, you can easily hack. That is our first step. If client mentions it explicitly, we go all in. Even if the client doesn’t mention it, if the prospect says that we are looking for rating interest, we still will verify. Are you sure that you are sorted on WordPress being safe? Any concerns, any doubts?

And then features, because WordPress has no match. And I’m not saying this as a WordPress agency. The Gutenberg editor itself alone is miles apart. If you go to any other platform, the editing capabilities are nowhere close to Gutenberg editor. Gutenberg editor demo itself is a deal breaker in many cases. We just show them Gutenberg editor, and they’re like, wow, is this possible? Is this thing real? Is this some mockup? No, this is website. After the call, we are going to send you a URL, go and try your hands on. This is no fake, that vaporware demo where you see something on my screen, but in reality it doesn’t work like that. This is the real website. Go and try it.

[00:26:53] Nathan Wrigley: That’s really interesting because in the non-enterprise, that message hasn’t necessarily landed. Gutenberg is, it’s very divisive issue, isn’t it? Whether you use it or not. And it’s curious that you are saying that it’s one of the key things which leads to the success.

Can you just dig into that a little bit? What are some of the aspects of Gutenberg which make the clients think, okay, this is great, this is perfect, this is just what we need? What are some of the features that you draw out of the block editor?

[00:27:19] Rahul Bansal: So I think the main difference that we feel like compared to the consumer WordPress, I would say. The consumer WordPress access technologies on very different platform, like proprietary. Just imagine somebody is using Instagram to create reels. With that mindset they come to WordPress Media Library and expect video editing experience like that to happen in WordPress, they will be disappointed.

But here we’re talking to people in large companies, very large companies, using legacy systems, probably from the nineties. They might have a desktop application to update a webpage, some ugly looking forms. We even have a memory where a client, their publishing workflow they had to write an article using a very poorly designed HTML web form, and they had to upload images via FTP. And then they had to reference images in document. There was no drag and drop interface.

So now if somebody like this person comes to Gutenberg, it’s like an iPhone moment for them. With that being said, Gutenberg itself is a very powerful editor. We haven’t come across a case where somebody said, oh, this is not flexible. As I said, like enterprise have a very good balance around the feature versus maintenance. For example, so Gutenberg may have one or two features less compared to a third party page builder, but then being part of Core, they’re assured that five years down the line, it will be very well maintained.

Security is more important to them because one less plugin means one less attack vector. Less things to break, less things to train, less things to maintain going forward. We as an agency develop so many sites on Gutenberg that we have our own libraries and our own patterns. So it’s like, whenever a requirement comes, we can easily map it to Gutenberg.

[00:28:51] Nathan Wrigley: I think that’s the difficult thing to imagine if you’ve never built your own block or you’ve never delved into patterns. But certainly at the enterprise level, if a client comes to you and said, we have this repeatable thing, and we need to put this repeatable thing on page every time. And honestly it’s real chore. And you can build a block, and they drop the block in, and now they just fill out some fields, drag an image in here, and suddenly, boom, it’s exactly on the front end what were expecting.

It’s that kind of thing, isn’t it? It’s that, almost like an app inside of an editor. So we’ve got a block which consumes perfectly the content that you want, and we can adapt it if your needs change. But if you’ve never really gotten into that, it’s hard to imagine. It’s just a bunch of paragraphs and images, but it’s not, it’s so much more powerful than that.

[00:29:34] Rahul Bansal: One thing I would say that, if you look at any large corporation, they have something called design systems, where they have their brand guidelines across products, not just websites like, across mediums like print and everywhere. With Gutenberg, it is very intuitive and easy to map the design system into WordPress. So that is where Gutenberg shines, that you can create patterns, you can create theme json. You can give them a starting point which blends very well with their existing design system.

That is where half of the job gets done. Like, compared to indie hackers or small businesses, large enterprises are not running after lots of plugins. They don’t want to try a hundred plus blocks plugin, a plugin with 200 blocks. They want to restrict number of choices. They want to have less number of blocks, but properly weighted with the user’s guidelines. So it’s like, the freedom they demand is easily given by Gutenberg, and with the assurance of, it is going to be around long term. It’ll be very well maintained. It’ll be very well supported, and performance. I still feel Gutenberg has much better performance, the markup, SEO qualities, top notch.

[00:30:35] Nathan Wrigley: I think it’s just the constraints that you can put around that editing experience. So if the client comes and they want this inexperienced user to be able to create content but have boundaries so they can, I don’t know, they can add an image here and it will be, it doesn’t matter, they just put it in and it will output perfectly. And here’s where the text goes, but they can’t change the fonts, you’re not allowed to change the color and what have you. All of those kind of constraints around the editing experience. It’s just miraculous really what’s possible.

And I think it gets lost because the majority of people, I’m imagining using WordPress are sort of tinkering with Core blocks and it can become confusing. There’s lots of choices. You try one thing and it doesn’t work out, and you throw your hands in the air. But if you’ve built the perfect thing, then all of those guardrails are in place and it will output the perfect thing every time. I think that’s really interesting.

How do you grow, and how do you find your next employees? Because I’m guessing at the level that you are now at, you must have some fairly exacting specifications when you put out a job description. And WordPress is becoming an increasingly JavaScript based thing. Lot more technical difficulties. Where do you find your talent, and is it becoming harder to find?

[00:31:40] Rahul Bansal: This would be unique to literally us. We have what we call our own training center where we, every year we take some 50 students from college, who recently graduated. Every six months we take 25 to 30 students from colleges. We put them through six months of training, like a complete, they get paid to learn WordPress for six month. They have no obligation to continue with us. They can join our competition, they can do anything with the WordPress.

But we really get this talent and this job is very popular in India. So this training we run, the pay scales are very popular in India. So last year also we had some 90,000 applications for 60 positions. We literally have to build a platform. So we have a campus adding platform, its name is Chitragupta. Chitragupta is basically is responsible for managing the ledger of your good and bad work. So in Hindu mythology. So we built  Chitragupta, which basically scans your GitHub repos and assigns your grade.

And those 9,000 people gets graded. And then we interview from top to bottom until 60 positions gets filled. So last time we had to interview some 1,200 students, by the time 60 students got selected.

Then we put them to the six month training. Our course is public, so people know what is going to be in the course, and so we find a lot of passionate people. Many times by the time they join our course, I’ve already gone through it from the public website that we have learn.rtcamp.com. From there, they already have checked it. And then we put them through the six month training. After that, this thing we started this year only. After six month training, we put them six months into the WordPress.

So WordPress Core has a mentorship program running on for new contributors. So this year we enrolled 10 people, managed by Automattic and Google employees, senior employees. So they are mentoring this people for further. So first year we, we invest them heavily. Zero revenue, only investment in year one.

And then from year two, we start getting, like some client work done from them. And this is something turned out to be very great for us from last three years. At some point we felt, there are same number of people switching between agencies, and net new addition to the WordPress worker pool was getting stagnant, especially around Covid.

I felt the way people used to discover life with WordPress, or a professional life with WordPress was mostly through WordCamps or meetup groups, and when that Covid happened, we suddenly missed those years, when new people didn’t come to the WordPress, as many as they used to come before.

So there was this gap that started hurting large agencies, like us. Because if we look at a small website, then the enterprise budget appears a lot, but there’s always a limit. No company approves unlimited budget for any venture. Like for every project there’s a budget. It’s usually large enough, but there’s always a number and, as talent was getting more expensive, WordPress was getting unaffordable at some point.

So I talked to some medium publishers, medium sized publishers, not the big ones, who complain a lot. Like the good WordPress agencies are either sold out or too expensive. It’s like WordPress is suddenly getting unaffordable, and that is when we started in this hiding experiment, where we onboarded people every year. And this is, we are doing from last four years.

So we have been hiring for many years, but early it was 5, 10 people. This massive scale of hiring we started from last three to four years. And, it turned very well for us. Like all these people in second year clocked, like in agency billable hours is a very big metric, and in second year, these people clock 90%, more than 90% billable hours.

[00:35:08] Nathan Wrigley: That’s incredible. What a great idea. Can I just ask, just to clarify with that, is that an in-person thing? So you come to a place where 60 people gather, and the tuition is taking place in the same room, or is it an online thing or?

[00:35:23] Rahul Bansal: So before Covid it was, it used to be in the same room, but the scale was 20 people at that time only. After Covid, we made it completely remote. It’s now completely remote. It’s still in the same time zone because, these are the Zoom calls, recordings. The time zone synchronization is needed. So that’s why it’s currently India only. But we are expanding it to other territories, and we are seeing like if we can create similar talent pool in other part of the world. Because,early it was in n office, then it went remote over Zoom. And this year, it is going async. We have a dedicated department, which is called Learning and Development Department.

So our agency head has implemented most lessons in a synced way, so that people can wake up at different time. And so it’s like they won’t get blocked. They can learn asynchronously, they can complete this six month course asynchronously.

[00:36:11] Nathan Wrigley: It just sounds like the appetite is incredible. The numbers that you just mentioned there, I think you said something like 1200 or something like that, people for 90 places. That’s just remarkable. So the appetite really is there. It seems like such a commendable project as well, in that you are putting out a limited, you know what, you can manage. 60 people out into the workplace. Some of them may end up working with you. Some may end up working with your competitors. But you’ve put 60 people out there who are really credible at pushing the boundaries of what WordPress can do, and hopefully just making a start on their career.

[00:36:44] Rahul Bansal: Yeah.

[00:36:45] Nathan Wrigley: But I know that it’s not just limited to that. And, I would like to get into this just before we finish, because I think this is important. Over the last few years we see these metrics every year of companies who put time into the WordPress project in general, in a whole manner of different ways. They may be sponsoring events. They may be committing staff to Five for the Future and what have you.

And the company, your company, rtCamp, it always seems to be right at the forefront of that in a growing way. I’d just like to applaud you for that and give you an opportunity to say what it is that you do so that we’ve got an impression of just how much good you are doing apart from obviously, having a very profitable agency and what have you, how much good you’re putting back into the community as well. So just outline your commitments to the WordPress project.

[00:37:29] Rahul Bansal: So, as I mentioned that, so we have multiple ways of contributing. So as we hire a lot of from college, unfortunately we cannot have a lot of Core committers with us, but we take care of the other end. For example, these 10 people, we have a commitmentt now internally that every six months, so we will put 10 people full-time, like full-time as in literally full-time. A hundred percent of their time will go in working on WordPress project for six months.

And then this will be rotated by next batch. So in rotation there will be at least 10 people. As we grow further, then we’ll make it 15, 20. And we want to keep this ramping up this number. So there will be always, WordPress Core will have enough junior people to pick the task. So, that good first issues will, somebody will be looking at them.

Then we have a QA people, work into the QA team, other teams. I myself as WordCamp organizer, for WordCamp Asia. We have other people contributing to different part of WordPress.

We have a training course, which is public domain, in public domain. We started that much before learn.wordpress.org is there. Now  learn.wordpress.org is there, it is much better resource. But then this course was there for many years, and many other agencies use it. So that is one of the way to build human capital. So this word actually drives me a lot. We want to consciously put our efforts in developing human capital of WordPress.

Because in the end, it’s people that do the job, no matter how fancy it is. You need a human to put a prompt to the AI. ChatGPT won’t build things on its own. You need to, you need a human to ask creative questions. And we want to ensure that WordPress economy continues to grow, and it never falls short of people. So we hire a lot of junior people. We put into the workplace. We publish our videos tutorial. We publish our training material also in the public domain.

Many companies use it, and we expect no link back, also, no credit. Because sometimes they have a apprehension that if they know, this is why rtCamp course will, for, example, our training course site doesn’t require registration. So if you’re sending your employees to learn WordPress on our site, we won’t track them. We won’t solicit them. We have no way of knowing who’s learning. Google Analytics just shows traffic. A lot of traffic is coming to those training sites, but we have no personally identify information tracked there.

[00:39:45] Nathan Wrigley: I would imagine that in every aspect of your business, except this, maybe, there’s gotta be some measurable ROI. Okay, we put this in, we get this out. Do you have any metrics to measure your commitment to the community, or is it just putting your finger in the air and thinking, okay, last year, our business did this, let’s put, I don’t know, whatever it might be. Do you have a pro forma that you stick to? A number of hours, a number of people? Or is it just, yeah, this feels right this year. Because you can’t measure this. And in some cases, I imagine people would think, yeah, they’re probably overdoing it a little bit over there and what have you.

[00:40:21] Rahul Bansal: So, we have a top line mandate that, so it’s like, internally we divide engineers in three categories in rtCamp. The junior ones were like less than two years in rtCamp. The senior ones like two to five years. And lead levels were like more than five years with us. The junior one, we target 20% of their time for WordPress Core. And the medium level, the seniors, 10%, and lead level is 5%. Lead level is very hard, because we have very less lead engineers. The demand supply gap is more evident on senior and lead level. But then, these metrics are, so our office structure is that we have some called business needs.

So every people need to submit their 20% report. Not only they need to submit the hours report, like they have their hours went into the WordPress Core or different part. They have to compile what are the issues they solved. It’s not like you’re just making time entries. You have to tell in the leadership quarterly review that I have 50 people in my business units, and together they clock 3000 hours. And this is what we achieved in 3000 hours. And this is approved. The props messages we see in WordPress Slack, those screenshots, if our employee names is mentioned, are taken screenshots and filing into those review reports.

Three people got props from my team. The WordPress Core release notes, like with major releases. So those contributor list also presented by them. If somebody’s doing some make WordPress blog post or activity, those are also tracked by them. So the heads compile this report, from like bottom ups and then present in leadership meeting. So this is not accidental.

The material ROI is very hard to measure. We cannot say that, oh, we made like X dollars because of this effort. I think, as a salesperson, when I tell a client like, hey, I’m going to give you an engineer who knows WordPress very well. I’m more confident if that person has contributed six months to the WordPress Core. And their patches is weighted by some amazing people in WordPress community, especially senior ones. It’s like a win-win situation for all. This gives me a very, very well trained people to sell.

[00:42:16] Nathan Wrigley: That’s exactly how I was just thinking about it. This kind of win-win cycle of you put people into WordPress, and obviously at a junior level, more time and I can understand that. That makes sense. Presumably the ones who are more experienced, they’ve got other work to be doing. But also they’ve probably gained a ton of experience doing those prior years of extra hours.

So you put the hours in, but also they contribute to Core, but they get experience back out. They’ll be exposed to all sorts of different things that your projects would never have put them in front of, presumably. So they’ll be touching on subject matters. Getting into plugins, themes, blocks, code, Core, whatever it may be in a whole range of different ways than they would be. So like you say, it’s like you slap my back, I’ll slap yours a little bit. Win-win. WordPress wins, you win.

[00:43:06] Rahul Bansal: There are three wins here. The person, that student, who came right out of the college, and usually in college, people here, people have some negative perception about professional life. That companies are evil. You are going to do labor. Somebody will steal your credit, and here they’re on their own. Like they go into the WordPress community on their own. They sign a patch with their name. They file a Trac ticket with their name. They get props in their name. They get treated very well by contributor. If somebody makes mistakes, WordPress committee is full of nice people. Nobody’s going to pull them down. Nobody’s going to shout at them.

Everybody corrects them with respect and compassion, and that helped them grow as a person. Like, they become better human. They become better coder. And that empathy, we see that, when they become senior engineers, and when they’re reviewing some junior’s code, they remember that, hey, when I was, it was my first day in WordPress community, and I made that patch. I made one mistake, but somebody was nice to me, so I have to pass it on. So that niceness cycle continues.

And, the biggest win is that these people like, who has an incredible job satisfaction. They love open source more. Many of them don’t join for the love of open source, they’re at a point when they, join rtCamp, they’re at a point when their college is ending. They just want to get a job, and secure a financial life. Whatever jobs comes their way, they’re okay with it. Open source, closed source, not much preference. But once they’re in, and then we take them through this one year of tour, like six months in training center, then six months in WordPress community, they become the advocate of open source for life.

And that is a very most important win for us because we want people to believe in open source. We don’t want them to say open source is good because their company is selling it. We want them to have that faith that open source is the right way to do things. And that faith is very important for growth. You cannot mug up your mission statement and stand for it.. You have to believe in something to stand for it.

[00:45:00] Nathan Wrigley: What a profoundly interesting thing to have said. I think that’s just fabulous. I think your company is doing so many interesting things. It’s obviously, financially it’s working out, but just the position that you’ve painted there of the way that you are treating your employees, and the autonomy that you’re giving them, and the future opportunities that you are giving them. And the training opportunities giving them, just remarkable. And I’m profoundly impressed by what you’ve been doing.

Unfortunately, time is our enemy. We’re going to call it a day there. Rahul, thank you so much for chatting to me today. That has been an incredible journey. Long may it continue. I wish you and rtCamp all the success that you can possibly have the future.

[00:45:39] Rahul Bansal: Thank you, Nathan. Thanks for having me on this podcast.

On the podcast today we have Rahul Bansal.

Rahul is the founder and CEO of rtCamp, a large agency that specialises in enterprise-grade WordPress projects. He began his journey quite differently, starting as an individual blogger back in 2006, discovering WordPress in 2007, and gradually transitioning from being a publisher to a freelance developer, before founding rtCamp in 2009. Today, rtCamp is an enterprise-grade WordPress consultancy agency, operating globally and trusted by clients such as Google, Meta, Automattic, NewsUK, and Al Jazeera.

Rahul sheds light on working with enterprise clients in the WordPress space. Many of us are familiar with WordPress in the context of small businesses and blogging, but the enterprise space demands additional layers of security and scalability. Rahul explains the factors that set enterprise projects apart, and why meticulous code reviews,   and security audits are essential when working at this level.

He talks about the opportunities in the enterprise space, recounting how rtCamp initially stumbled into enterprise level projects, not even realising their potential until a client’s high expectations led to a decision to market themselves as an enterprise agency.

We also discuss the role of WordPress in enterprise environments, from why Gutenberg has become a credible selling point, due to its powerful editing capabilities, to how the platform’s flexibility supports varied enterprise needs.

Rahul also gets into the importance of positioning, how historical context offers advantages, and the expanding market that makes WordPress a compelling choice for large clients today.

Towards the end, we explore rtCamp’s innovative internship program aimed at growing the WordPress talent pool, and the way they are contributing back to the WordPress project; a win-win for the business and the broader community.

If you’ve ever considered what it takes to work with WordPress at the enterprise level, this episode is for you.

Useful links

rtCamp

White House website

Al Jazeera website

Campus at rtCamp

rtLearn

by Nathan Wrigley at March 12, 2025 02:00 PM under podcast

Do The Woo Community: Effective Collaboration with Clients and Teams: A Chat with Zach Hendershot

In this episode, Adam and Emma discuss effective collaboration with Zach, CEO of Miruni, focusing on setting clear expectations, minimizing manual tasks via automation, and enhancing communication for better client and team interactions.

by BobWP at March 12, 2025 09:49 AM under SaaS

March 11, 2025

Gravatar: Top Strategies for Reducing Friction in Sign-Ups

Creating effective sign-up flows presents a challenging balance. Users expect quick, frictionless experiences, but businesses need quality data to better serve their customers. To get this information, they often overload the sign-up process, leading to high abandonment rates and lost opportunities.

Thankfully, there is a way to find balance – and we’re talking about more than just user-friendly designs. Advanced strategies like intelligent data collection timing and progressive disclosure techniques help maintain healthy conversion rates while gathering essential user information. These approaches, combined with AI-driven personalization, can transform a standard sign-up process into an engaging experience.

Reducing friction while maintaining control over data collection might seem daunting. However, by implementing strategic optimization techniques and tools like Gravatar’s developer API, you can significantly reduce friction points in their sign-up process. 

So, let’s see how you can do just that while still collecting valuable user data that allows for personalization and improves the overall user experience.

Essential strategies for reducing sign-up friction

When talking about sign-up friction, a common topic is form optimization, but that’s only the beginning. You need a bit more if you want to create better sign-up experiences and reduce drop-off rates while still maintaining high data quality.

First, progressive profiling allows you to collect user information gradually rather than overwhelming new users with lengthy forms like these: 

 Example of a bad sign-up form with loads of information

Instead of requesting all details upfront, ask only for essential information during sign-up, and additional data can be gathered as users engage with your product.

Example of progressive profiling in a sign-up

You can also use email-based profile systems like Gravatar to make the process even easier. By integrating Gravatar into your sign-up flow, you can automatically populate user avatars and profile information using just an email address. This eliminates several manual entry steps.

Delayed email verification keeps users engaged by letting them access your app immediately after sign-up. ChargeBee is a great example of this approach: 

  1. New users enter the platform right away by filling in the more important details. 
Chargebee sign-up page
  1. They verify their email address only after signing in.
Chargebee email confirmation message

Finally, smart forms with predictive error prevention catch potential issues before submission rather than returning users to a form with error messages. This real-time validation helps users complete sign-up forms correctly the first time.

Example of predictive error prevention on Chargebee’s sign-up page

Intelligent data collection: When and what to ask 

Making smart decisions about when to request user information can significantly impact sign-up completion rates. A strategic approach starts with distinguishing between essential and non-essential data.

Essential information typically includes:

  • Email address (for account creation).
  • Password.
  • Username (if required).

Non-essential information such as company name, last name, job title, team size, and phone number can definitely wait. 

Custom triggers help time additional data requests effectively. For example, only ask for team size after users show interest in collaboration features. Or request company details when someone visits the enterprise pricing page.

Example of custom triggers for additional data

Profile enrichment through integrations and APIs offers another powerful approach. By combining email-based profile services like Gravatar with progressive data collection, you can build comprehensive user profiles without overwhelming new users.

Gravatar’s API can automatically populate non-essential information from a user’s email address, eliminating the need to ask for basic profile details during sign-up. This approach maintains high conversion rates while still gathering valuable user data.

How Gravatar simplifies user onboarding

Gravatar for developers – Profiles-as-a-Service homepage

Gravatar transforms the traditional sign-up process by automatically populating user profiles through a single email address. This approach eliminates multiple manual entry steps that often cause users to abandon sign-up forms – according to a 2020 study by Wyzow, 80% of users have deleted an app because they found the initial setup process too complex.

This is why major platforms like GitHub, OpenAI, and Atlassian use Gravatar to enhance their sign-up experiences. 

By implementing Gravatar’s REST API, developers can instantly access a rich set of user information:

  • Display names and avatars.
  • Professional information.
  • Biography and location.
  • Language preferences.
  • Pronouns.
  • Social and professional links.
  • User interests.
  • Work history.
  • Social connections.

This enriched data collection happens without requesting additional information from users during sign-up. Instead of presenting new users with lengthy forms asking for profile details, applications can pull this information automatically through the Gravatar API.

The benefits extend beyond the initial sign-up. With comprehensive profile data available immediately, applications can create personalized experiences from the first interaction:

  • Customized welcome messages using the user’s name.
  • Interface language set to user preferences.
  • Content recommendations based on stated interests.
  • Contextual features based on professional background.
  • Team collaboration suggestions using work history.
  • Social connections through matched interests.
  • Location-based content and recommendations.

Implementing Gravatar also helps solve common onboarding challenges:

  • Reduces form abandonment by minimizing required fields.
  • Eliminates the need for users to upload profile pictures.
  • Maintains consistency across multiple platforms.
  • Allows users to update their information in one place.
  • Supports both individual and role-based personalization.
  • Enables automatic profile updates across integrated services.

The system respects user privacy by letting individuals control what information they share. Users can maintain multiple profiles with different levels of detail tied to separate email addresses, giving them full control over their online presence while still providing valuable data for personalization.

Example of privacy settings for a Gravatar profile – toggle switch for API access

For developers, integration is straightforward through the REST API, with comprehensive documentation and support available. And since Gravatar is free for both users and developers, it offers a cost-effective way to enhance sign-up flows and improve user engagement from the start. The API’s design focuses on developer experience, making it simple to implement and maintain while providing powerful personalization capabilities.

Real-world examples: Successful Gravatar implementations

Let’s see how different websites use Gravatar to make signing up and getting started super simple. 

OpenAI offers a perfect example of a streamlined approach: 

  1. Users sign up with their email and create a password.
Creating an account on OpenAI
  1. Their profile picture automatically appears from Gravatar. 
Profile picture on the OpenAI website 

No extra steps are needed. This small touch adds a personal element to their AI platform experience right from the start.

WordPress.com takes this integration even further. When someone signs up, the platform automatically pulls in everything from their Gravatar profile – their bio, display name, social links, and even their location and interests. 

Profile information on WordPress.com

This means new bloggers can jump right into writing instead of spending time filling out profile forms. Plus, any changes they make to their Gravatar profile automatically update across all their WordPress sites.

Other popular platforms also use Gravatar in creative ways to make things easier for their users:

Developer platforms:

  • GitHub shows Gravatar avatars next to code contributions, helping developers build recognition in open-source communities.
Profile picture on GitHub
  • GitLab uses Gravatar to personalize project dashboards and team features.

Collaboration tools:

  • Figma automatically loads team member profiles to help people connect faster.
  • Slack shows profile pictures in chat to help teammates recognize each other.
  • Trello adds Gravatar photos to cards and boards to make project tracking more personal.

The best part? Users only need to update their info in one place – their Gravatar profile. That single update gets reflected everywhere they use these tools, making it super convenient to keep a consistent online presence.

Optimizing mobile sign-up experiences

Making sign-ups work smoothly on mobile devices has become essential, with mobile traffic now exceeding 60% of all web visits. But mobile users face unique challenges – smaller screens, touch interfaces, and often spotty connections. Here’s how to create a mobile-friendly sign-up flow that gets results.

Start with the basics: optimize every element for touch. 

  • Buttons need to be at least 44×44 pixels, with enough spacing to prevent accidental taps. 
  • Make forms finger-friendly by adding ample padding between fields. 
  • Stick to readable font sizes – 16px minimum for text inputs to prevent automatic zooming.

Smart keyboard handling makes a big difference too. Set the right input types (email, tel, number) so users get appropriate keyboards. Group similar fields together to minimize keyboard switches. For example, keep all text fields together, then numeric fields.

Simplify data entry by:

  • Enabling autofill where possible.
Example of autofill during sign-up
  • Offer social login options optimized for mobile.
Example of user-friendly social media sign-up buttons on mobile devices
  • Using Gravatar to auto-populate profile info from email addresses.
  • Adding real-time validation to catch errors early.
Example of real-time validation of a password

Break up longer forms into logical steps with clear progress indicators. Each step should fit comfortably on a mobile screen without scrolling. And remember – every field you require is another chance for users to abandon the process. Only ask for what’s absolutely necessary.

Finally, test your flow on multiple devices and screen sizes. What works on a large iPhone might be frustrating on a smaller Android phone.

Get started with Gravatar’s developer tools

Ready to streamline your sign-up process with Gravatar? Their developer tools make integration surprisingly simple. The new REST API gives you instant access to user profiles with just a few lines of code.

Getting started takes just three steps:

  • Register for a free API key at Gravatar’s Developer Dashboard.
  • Use the interactive console to test API endpoints.
  • Follow the comprehensive documentation to add Gravatar to your app.

The API lets you fetch rich user data like:

  • Profile pictures and avatars.
  • Display names.
  • Professional details.
  • Social links.
  • Location preferences.
  • Custom profile fields.

Best of all, users control what information they share. You just need an email address to start pulling available profile data. This balance between functionality and privacy makes Gravatar great for both developers and users.

Want to explore more? Get in touch with our team today, and we can discuss specific integrations for your platform. 

by Ronnie Burt at March 11, 2025 10:19 PM under User Experience

WordPress.org blog: WordPress 6.8 Beta 2

WordPress 6.8 Beta 2 is now ready for testing!

This beta version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites.  Instead, you should evaluate Beta 2 on a test server and site.

You can test WordPress 6.8 Beta 2 in four ways:

PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)
Direct DownloadDownload the Beta 2 version (zip) and install it on a WordPress website.
Command LineUse this WP-CLI command: wp core update --version=6.8-beta2
WordPress PlaygroundUse the 6.8 Beta 2 WordPress Playground instance to test the software directly in your browser.  No setup is required–just click and go! 

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

Catch up on what’s new in WordPress 6.8: Read the Beta 1 announcement for details and highlights.

How to test this release

Your help testing the WordPress 6.8 Beta 2 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important.  This detailed guide will walk you through testing features in WordPress 6.8.

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

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

Vulnerability bounty doubles during Beta/RC

Between Beta 1, released on March 4, 2025, and the final Release Candidate (RC) scheduled for April 8, 2025, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Beta 2 updates and highlights

WordPress 6.8 Beta 2 contains more than 14 Editor updates and fixes since the Beta 1 release, including 21 tickets for WordPress core.

Each beta cycle focuses on bug fixes; more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 1 using these links:

A Beta 2 haiku

Second wave refines,
Lines of code like rivers flow,
WordPress finds its form.

Props to @ankitkumarshah @vgnavada @krupajnanda @michelleames @audrasjb @marybaum @ecgan for proofreading and review.

by Jeffrey Paul at March 11, 2025 03:46 PM under releases

Do The Woo Community: What’s a WordPress Site Without a Blog?

In September 2024, we relaunched our community-focused blog, emphasizing its importance for site substance while highlighting the relevance of blogging amidst evolving technology.

by BobWP at March 11, 2025 11:01 AM under Blogging

Do The Woo Community: Securing the Supply Chain, Insights from the WordPress 6.8 Update with John Blackbourn

John Blackbourn discusses significant security enhancements in WordPress 6.8, notably switching to Bcrypt for password storage. The conversation highlights evolving perceptions of open-source security and upcoming events like the CloudFest Hackathon.

by BobWP at March 11, 2025 10:08 AM under Security

March 09, 2025

Gutenberg Times: Gutenberg Changelog 115 – Gutenberg Releases 20.2, 20.3, 20.4, WordPress 6.8 and WordCamp Asia

Birgit Pauli-Haack and Jessica Lyschik talked about Gutenberg Releases 20.2, 20.3, 20.4, WordPress 6.8 and WordCamp Asia

Show Notes / Transcript

Show Notes

Special guest: Jessica Lyschik

Community Contributions

What’s released

What’s in active development or discussed

Stay in Touch

Transcript

Birgit Pauli-Haack: Hello and welcome to our 115th episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about Gutenberg releases 20.2, 20.3, and 20 .4, and a little bit of WordPress 6.8 and WordCamp Asia. I’m your host, Birgit Pauli-Haack, curator at the Gutenberg Times and a WordPress developer advocate working for Automattic and still recovering from my cold that I brought back from Manila.

And today, I’m happy to get to chat again, it was Jessica Lyschik, front-end developer at Greyd and also core contributor to the WordPress open source project. We both just returned from WordCamp Asia.

Hello, Jessica. How are you today? How is your jet lag?

Jessica Lyschik: Hey, thanks for having me. I think the jet lag is, by now, done, I would say. So I’m back to the European time zone, but I also caught a bug after returning and had to take off a couple of days to get better. But by now, it’s like another week has passed. I’ve been working normally and yeah, I’m back to normal and preparing for the next event next week, which is CloudFest.

Birgit Pauli-Haack: You’re going to CloudFest. Wonderful.

Jessica Lyschik: Yeah.

Birgit Pauli-Haack: I had to cancel my participation in CloudFest because I have a bum knee. And my doctor said, “Well, going to another congress where you run around like crazy from one thing to the next, it’s probably not conducive to your healing that bum knee.” It sucks at one point, yeah. But on the other hand, “Okay. I don’t have to travel.” It’s another… Yeah, I can concentrate on some of the work again.

Jessica Lyschik: And get enough sleep, which is something you do not get on conferences and stuff like that.

Birgit Pauli-Haack: Right. Especially, CloudFest. I think every evening there is a festival or a party or something.

Jessica Lyschik: You can actually make it work. I do it the same on WordCamps. It’s the same for me. So it’s just when you are deciding where do you want to go, maybe not just be there as the first person and leave as the last person. But come late, leave early, and then just try to make it work for you. And it’s, of course, different for everyone. Some people are just like, they want to be everywhere and they need to go everywhere. And I’m more like, I need some breaks in between because otherwise that’s not going to work.

Birgit Pauli-Haack: Yeah, I’m pretty much the same way. However, sometimes I’m just so present in the moment, in the conversation, that I can really lose track of time. And then these are people I’ve never going to see for the next year or so, or maybe two. So at least, that was at WordCamp Asia. Where you’re only going to go to that particular family reunion and almost feels like that. Once a year and you need to catch up on what happened with other people, and there were so many good things to happen.

WordCamp Asia                                                       

So, what are your takeaways from WordCamp Asia? Do you have anything that will say, “Okay. Yeah, that was very surprising”? Interesting. New.

Jessica Lyschik: It has been my first time to the Philippines, I don’t know about you, but I think it has been a very interesting couple of days there in Manila. I did not get to see so much about Manila itself, unfortunately. The jet lag coming to Manila also hit me very hard. So the day I had planned to do something, go out somewhere did not happen. But I saw the Mall of Asia, which was like a gigantic mall where you could get your daily steps in very easily and not walk around the same circle for 10 times or something like that.

What I found very interesting was the food. I think the food was pretty good there. There was a lot of variety. We had a lot of Filipino food during the conference days, which I found pretty amazing. There’s a lot of seafood and fish in there. I’m not such a fan of seafood, but I tried the other things and they were all pretty good. So, I did not have anything that I didn’t like.

Birgit Pauli-Haack: Yeah. I was really… Not surprised, but it was quite unusual that the vegetarian as well as the vegan options are so particularly tasteful and very… I have a big variety there.

Jessica Lyschik: That’s true.

Birgit Pauli-Haack: And I got to chat with Dan, who is a former chef, who was on the organizing team and responsible for all the food. And he just has such a passion for the Filipino food and knows everybody in Manila to pick the right caterer for the events. It was really interesting, yeah. I also got to talk with a lot of Automatticians, but they all had the same T-shirt on, so all of a sudden, I was recognizing my fellow, my coworkers. And we don’t get to see each other during the year, especially in other teams so much. So, it was really interesting for me.

I like to hang out at the Do The Woo. Bob had… I think he started that last year in WordCamp Europe, that he is actually a sponsor and has a spot in the sponsor hall where people can hang out. And he invites his cohorts to spend an hour there. Or other people that he collaborates with, to just spend an hour there. So they can also say to their friends, “Okay. If you want to talk to me, I’m at that hour, at the Do The Woo booth.”

Jessica Lyschik: Oh, nice.

Birgit Pauli-Haack: But that was an interesting experience, yeah. So, I did that. And I was surprised how many people are actually in my talk because the such a niche topic which was about Playground and how to create demos with blueprints. And being the last session before Matt’s keynote and Q&A, I thought maybe they’re not going to be a whole lot of people in that talk, but I was surprised. There were, at least, 50 or 60 people there. Yeah, it was cool.

Jessica Lyschik: Yeah. Well, that’s nice.

Birgit Pauli-Haack: Yeah.

Jessica Lyschik: I was there too, I have to say.

Birgit Pauli-Haack: Oh, right.

Jessica Lyschik: I was at the very far back. Yeah, but it was quite interesting to go back and see, “Okay, this is…” I already know what blueprints are so it’s not that big of a deal, but going into the details again, it’s like, “Oh yeah, I remember that. Oh, I forgot this. Oh, okay.”

So, it was a very good thing.

Birgit Pauli-Haack: That was good. Yeah, good. So it was something for beginners, for the intermediate, and for the advanced. I was hoping about that. We will have WordCamp Europe.                                                       

Oh, I’m not saying that. It’s not out yet. But yeah, announcements will come.

Jessica Lyschik: Nice. I had a pretty good Speed Build as well with Nick, and that was a lot of fun. Nick tried to tackle the website with AI, or at least the top part with the slider with AI. Unfortunately, people said I won. I think Nick also did a great job. I felt a bit sad. Everyone’s clapping for me and cheering for me more than for Nick. It was like a bit disappointing. It’s like he tried. I would’ve never tried this with AI because I do not have the patience in 30 minutes to create something with AI. So I decided just to go, “Okay, do it in normal stuff. Just build some blocks, build some patterns there and do it.” But it was a lot of fun and it was great to see that afterwards, Nick also tried to not fix it, but further enhance it to make it an actual usable block.

That was pretty cool to see. He showed me the demo the next day. That was very nice.

Birgit Pauli-Haack: And I think he blogged about it.

Jessica Lyschik: Yes, he did.

Birgit Pauli-Haack: So, I’m going to share that link in the show notes when I find it fast. Yes, Speed Build Carousel Block. Because people are always asking for carousel blocks. Why isn’t that in community, I say. I’m going to put it in a community contributions. You’ll find it in show notes.

I think the two of you saying, “Okay, I’ll go back to what I know, what is fast, and what I know how to accomplish.” And then the other approach was that, “Well, let’s, under pressure, do something new.” But it’s also the, how do you approach learning new things? And sometimes you say, “Okay, I’m not going to learn it because I need to get my stuff done, and I know how to do this and I get it done.” When you learn new things, your task becomes more as an inspiration rather than the success because you might not end up accomplishing your task with the new thing. Because of course you are in a learning mode, you need to learn a lot.

So, I compare that with my first experience with the spreadsheet on the computer, MultiPlan was that. So I’m dating myself, but yeah, it was in the early ’90s. MultiPlan was even ahead of Excel from Microsoft. I had a big spreadsheet from the accountant and I said, “Oh, that should be much easier to be done in a spreadsheet on a computer.” So I spent all day, or all night actually, learning how to do this and put the spreadsheet in. But of course, it took me 6 or 8 hours. And if I would’ve done it just with a calculator, I would’ve calculated the whole spreadsheet probably in two hours or something like that. So, it’s not how long it takes to do something the first time when you learn this. It’s how long it takes when you do it a second time, because you need to discard the first time most of the time.

And I found that a lot of people who learn block development, what took me a half an hour with short code took me three days in doing it as a block. I said, “Yeah, that’s the first time you learn of things. Of course, it takes longer. Of course, it takes… You’re all going to changing your brain into the new paradigm. But how long does it take the second time around? Is it faster or is it better?” Anyway, this is the philosophical Birgit in a horsey voice. Let’s go back.

So WordCamp Asia, it was the first time for me in the Manila, and I actually planned a couple of days. Not a couple, a few days. Four days. Did some sightseeing, so I went to the historic sites of the Spanish occupation. I saw the monument for the atrocities that happened in the Second World War, and I learned about the current contemporary arts in two art museums. And I went downtown to the new business district there with a nice park and shops left and right on the street. It’s a pedestrian area. It’s beautifully done. And I also discovered a few street art that were purposefully put on that place as well.

So, that was quite interesting. Of course, I overdid it and I got my bum knee from there. So yeah, it was a little painful than going on the conference and going in the… The venue was quite vast, I found. 

Jessica Lyschik: You had to walk a lot?

Birgit Pauli-Haack: Yeah, you had to walk a lot. But I found all the escalators, so that was good. I didn’t have to do stairs so much. But yeah, it was a walk a lot. I like the Automattic booth was really big, but there was other… Hostinger was really big out of the usual. I also saw Mark Westguard of this WS Forms. He is on every flagship and shows off his plugin. I have to think really hard to get back to that because there’s the whole week, two weeks after that that already took over my life.

Community Contributions                                                       

Which brings us back to, “Okay, let’s record that rest of the show.” So, we had a few releases. So on the developer blog, Robert Meszaros published an article on customizing WordPress embeds to match your theme. And I think that’s very interesting to an approach to make sure that all the embeds that you use are actually matching your theme and you don’t use it out of the box. So he has some nice examples in there, and some great code snippets in how to do all of that. It’s definitely something to go back to, to make a better theme or a better site view for that.

Jessica Lyschik: Yeah, I think it’s a nice finishing touch when you’re creating a new website that really embraces embeds. I didn’t know about this, to be honest. I just saw it today. And I think it’s really great. It’s not something super big, but when you have a brand new website and have put so many thoughts and hours into the design, and then there comes this embed that just looks like it’s not meant to be on this website, then I think this is a great example of how tweaking the sites essentially can make an embed also look like it’s part of the website and not just some part of default WordPress that just pops up somewhere.

Birgit Pauli-Haack: Yeah, that hasn’t gotten a whole lot of love.

Jessica Lyschik: Yeah, that’s true.

Birgit Pauli-Haack: So, he shared this. For instance, one example is that out of the box, the featured image of a post that you embed has some border around, and he just shows you how to make that image go all the way to the corners. That’s such a small little detail, but it shows the attention to detail. And when you have all your cards that you have, your postcards in the query loop all having the same design, and all of a sudden, the embed doesn’t… It really stands out. It doesn’t… And it also distracts the reader from, “Why is this different? What I haven’t seen yet?” It has some nice little features on how to change things. Some great sailing pictures here. So, take a look at that and spruce up your site with some of the little things and big things.

What’s Released – Gutenberg 20.2                                                       

All right. So now, we come to Gutenberg 20.2 that was released in January, to be exact.

Jessica Lyschik: End of January, I think.

Birgit Pauli-Haack: Do you want to start out with what we are talking about?

Jessica Lyschik: Yeah. So, this was one of the two. I think I did the Gutenberg blog post on this one. So yeah, this wasn’t such a big release. It was rather small compared to the previous ones. Also, it was combined with, I think, 21.

Birgit Pauli-Haack: 21, yep. And we talked about that.

Jessica Lyschik: 20.1 release? Yeah. So, there isn’t that much going on in this release. It’s rather smaller bug fixes and some polishing overall. And I think one of the interesting things was that in the post content, you can now define the heading colors on a more global level. I think this was also a highlight from my blog post when I remember correctly.

Birgit Pauli-Haack: Mm-hmm. Yeah, I really like that you can now have the details block be more like an accordion with a name attribute. So it’s not in the UI, but you can do it in the… It’s in the UI, but you have to go to the advanced section to give all.

Jessica Lyschik: Oh, okay.

Birgit Pauli-Haack: Yeah, to give it all. To get this all done. It’s not for someone who doesn’t know what to do, that kind of thing. It’s not intuitive for site builders, so you need to give it a block name so it shows up as a summary. A block name about a name attribute.

Jessica Lyschik: Oh. So, when you give it the name.

Birgit Pauli-Haack: Sorry. Yeah, you need to give it a name attribute in the advanced section so the CSS that is built knows, “Okay. This is all one section. And one is open, the other ones are closed.” So, it kind of has accordion package.

Jessica Lyschik: So they all need to have the same name in this name tag, so then it automatically brings this only one of these sections is open. Okay, got it. Apparently, I missed that one.

Birgit Pauli-Haack: Well, great.

Jessica Lyschik: But it’s okay. Now, we talked about it.

Birgit Pauli-Haack: Right. Yeah, that’s what we’re here for. Two eyes see more than one. Four eyes see more than two.

Jessica Lyschik: Definitely.

Birgit Pauli-Haack: I also wanted to point out that the WP env local development tool now has WP-MyAdmin support as well as Multisite support. It had it before, but now it’s also documented so you know how to use it. That’s why I wanted to point it out because…

Documentation

Jessica Lyschik: Oh, I didn’t know it had this. You had this phpMyAdmin in the WP env.

Birgit Pauli-Haack: Yeah.

Jessica Lyschik: I’m not using PHP. We are so confused. I’m not using WP nth Multi… Multisite or WP env fit-all?

Birgit Pauli-Haack: WP env.

Jessica Lyschik: Ah, okay.

Birgit Pauli-Haack: Yeah. It’s when you’re working on Gutenberg, on your Gutenberg, something you can do. Just WP nth and it spins up a local WordPress instance with that particular folder. It also supports Multisite that came with 20.8.

Jessica Lyschik: Interesting.

Birgit Pauli-Haack: Yeah, you’re right. There were quite a few bug fixes in there and some polish in terms of previews. And also, some panel changes that have been in the last few Gutenberg releases, and also for the ones for the next. That’s a refactor of things. It was 20.2. I don’t think there’s anything else.

Jessica Lyschik: It’s a bit tricky with the numbers of 20.

Birgit Pauli-Haack: Yeah. God.

Jessica Lyschik: … in the brains of WordPress people.

Birgit Pauli-Haack: Yeah. So that brings us to 20.3, which was released just two weeks ago.

Gutenberg 20.3

Jessica Lyschik: We were all hanging out in Manila.

Birgit Pauli-Haack: Well, it was actually before or right on February 18th and it was released. Yes, we were all hanging out already. On travel, on planes. Yeah, my plane was… I was…

Jessica Lyschik: On planes, yeah.

Birgit Pauli-Haack: So, it was 12 hours to Singapore and then there’s another 3 1/2 hours from Singapore to Manila.

Jessica Lyschik: Oh, I did the same route.

Birgit Pauli-Haack: It was kind of 15 hours flight, but then you have to be 2 or 3 hours earlier at the airport. You have a layover in Singapore, and then you have to transfer from the airport to the hotel and…

Jessica Lyschik: Yeah. I think I calculated something, like 23, 24-ish hours door to door, so it’s not just like a 15 hour flight. But yeah, you have to count in all the waiting time. I had to travel to Munich airport two hours, so that all adds up to this whole ordeal of…

Traveling to Asia is easy. No, it’s not.

Enhancements

Birgit Pauli-Haack: No, it’s not. Yeah. So Gutenberg 20.3 also has a not particular big features coming in, but some nice additions. And one of them is that the social links now of a Discord logo that you can add to it. The query block now, that is really nice. It has an option to ignore sticky post. It took a while to get the sticky post into the filter, but then there’s also the need that sometimes you need a query loop that ignores the sticky post.

Jessica Lyschik: Yeah. It’s definitely something that you’re used to this when you’re doing classic themes and just have all the opportunity with the WP query nth function. And it’s great to see that these little things and… Even if you do not use them that often, that these are still now available. That just makes transitioning to block themes and block inside it are so much better because you finally have all the options. But maybe not all yet for the query loop, but we are getting there. Let’s put it like that. We are getting there.

Birgit Pauli-Haack: For sure, yeah. There was a major push in that.

Do you want to take the next one?

Jessica Lyschik: The yet another one of completing the options that you have on block is the RSS block got border and spacing support. And also, duotone settings got improved, they now have a reset button and improved toggle rendering. Let’s have a look what this does.

Birgit Pauli-Haack: Yeah, the reset button has gotten quite the attention now that it was missing on a few of those color pickers or so, or panels. So, what did you find out?

Jessica Lyschik: Oh. I think it’s also, these are such tiny changes. But once you have them, you realize it’s so much easier to clear colors or remove something that you would have needed another four clicks or something, and then it’s just one. So it doesn’t seem like big things, but it slowly improves over time. And I think this is what the editors actually need right now, this refinement. Because there’s always been in the past pushing big projects, new features, and now it’s more like, “Okay, we are in the situation, but the best we can do is basically to do the housekeeping and fix the smaller things and polish it.”

Birgit Pauli-Haack: Yeah, and the smaller things.

I think it’s for the user. Very important to have a consistent interface. So, if you put a background color in and you have a reset button, why don’t you have a reset button on the shadows? So, shadow panel. Or why can’t I have a reset button on the text color, for instance, if it was missing. So it’s definitely, you cannot take that cognitive load. You lower that quite a bit by having an inconsistent interface. Also, with border and spacing support, if the block doesn’t have it and all of a sudden it doesn’t match what you want, then you go over looking for things. And the spacer block is not always the best solution for things. It’s not a bad solution, but it’s not the best because once a panel gets or a block gets spacing support, now you have to chase down all the spacer blocks to take them out. So, it’s kind of interesting.

Jessica Lyschik: That’s true, yeah.

Birgit Pauli-Haack: The next one is there was a bug fix or maybe a revert on the quick inserter, that it didn’t search the patterns anymore when you put a search parameter in there. And that has been restored. So I think although that’s bug fix, or I think it’s bug fix, it’s definitely worth pointing out. So, a missing feature comes back. Yay.

Jessica Lyschik: We just talked about it having the same options on blocks. Like, archives and categories got the color support. So, you can now have select colors on the archives and category blocks. Yet another one of those because then, people try.

If you do not have them, it’s like, what do these blocks do not have? Why can I not change the color there? Then, people go to CSS and then it’s not needed actually if these settings would just be provided right from the start. But yeah, it’s like a living project. So, here we are.

Birgit Pauli-Haack: Or what I always did when I didn’t have color support, I put it in a group block, and then of course it blows up the nesting of my blocks. So there are always ways around it, but once things then come into the editor, you need to think about how your workaround needs to be worked around.

So, I think those were the few things that I wanted to point out. Did you see anything else that you wanted to point out?

Jessica Lyschik: No, I don’t think so, but I’ve been just scrolling through it. It’s been a good chunk of bug fixes, some accessibility improvements, some performance improvements, good quality tools.

Gutenberg 20.4

Birgit Pauli-Haack: All right. That brings us to Gutenberg 20.4, which is also the last Gutenberg release for which the enhancements made it into 6.8. After that, it’s all bug fixes that go into the release, and any new enhancements coming into Gutenberg will be reserved for the next release. What is it? 6.9? We don’t know yet when that’s going to be, but…

So, what’s in there? There is a conditional enable the new default rendering mode for pages. I highlighted that. And I heard from quite a few people that they like that there is a default rendering mode for pages, but I have not seen yet the use case for it. So, why are people so excited about this? But yeah.

Jessica Lyschik: That’s a very good question. You already had this show template. That’s already in there. That’s a good question. Why it’s so hyped? Maybe, I need to test it out. That’s probably a problem.

I haven’t gotten to looking at the latest releases on an actual site yet because WordCamp Asia, being sick, being busy at work, life happens. I only heard this week, things were a bit off, and template parts were actually missing from if you had 6.8 Beta 1 running. So there have been some hiccups there as well,

Birgit Pauli-Haack: Yeah. We definitely need to track that down here. So now, there is a persistence. So you could have a show template preferences, but now there are also sport, which is pretty cool. There was a time where you started with a new page, and first you saw all the patterns that are labeled for new pages, page layouts. That modal was removed, and now it’s back. So, it’s a 50/50 thing what people want and what don’t want when they use that. So, that’s also an interesting development.

Jessica Lyschik: I mean, the problem with the modal… I mean, it wasn’t removed. There was an option, because I worked on this part as well. It got an option to be disabled in the settings when you’re on a site where you have to add new pages over and over again, and you know what you want to put on a page. You do not need this modal popping up every time. So, it was more of a user enhancement so that you can decide, “Okay, do I need this model every time or do I just turn it off?” So, there was that part.

I’m not aware if it’s back yet. I heard people saying to remove it completely. But yeah, there’s a lot of different use cases how you would like to… Some people want the model always to be on because they don’t know what they are doing, basically. They just want to pop on a template or a pattern there and are good to go. And there are people who would like to just start writing first. There are people who maybe, want to use it but don’t want to be bothered all the time. It’s one of these things where a lot of different use cases clash together, and then it’s just so hard to actually find what is it, where is the…

Birgit Pauli-Haack: The middle ground there.

Jessica Lyschik: What’s the thing? Where’s the middle ground that we can go and implement it that way? So, kind of everyone or the majority of people is okay with it. There will always be people who are like, “I don’t like this. I want it to be different.”

Birgit Pauli-Haack: Right.

Jessica Lyschik: But that’s basically impossible to make it happen for everyone.

Birgit Pauli-Haack: Right, yeah. Another problem was when you say, “Oh, I don’t want the starter modal,” it was hard to get the layouts, if you wanted, to get to patterns and get the layouts because there was no category for that. So, you had to assemble them from a list of patterns or from multiple pattern categories to put those page layouts together. And I think… I don’t know if it’s here or it was in an earlier version where they restored or created a category for patterns for the starter content. I think that was part of that, or how can we do that better for our users.

So there is now a pop-over on the left-hand side to show post template. If there is one to give you additional options, I think there. The next thing is that pull quote finally has the assignment styles that was missing for a long time. That you couldn’t do left, right and all of that, or wide. So, it has it now. It’s all about persistence. And border control got the reset button.

Jessica Lyschik: Yes. It’s, again, these tiny things that make or break something, or your experience.

Bug Fixes

Birgit Pauli-Haack: Right. And post comments count also have received border support. That’s cool. So now, you can have it stand out some more. Post formats have still be a little bit of a hit-and-miss with the block themes, but sometimes somebody says, “Okay, well let’s fix that some of the things.” And now, you see title and description for post formats in your templates. So in the list of templates, you can now see which are the templates for your image formats, for your link format, and if they are templates for that. So, that’s really cool.

And there’s an interesting bug fix that drove me nuts for a while, was that the text and color picker were overlapping each other in the format library. And that is fixed, thank God. Thank you so much. 

Documentation

And then there are some documents updates. There’s obviously, the problem that a lot of features come in and the documentation hasn’t been updated. So, that has been rectified for the block variations using get_block_type_variationblock. And then also, removes the nodes for block hooks that it only supports static theme elements because that’s not true anymore. Block hooks also support dynamic blocks. All right.

Jessica Lyschik: Yeah, nice.

Birgit Pauli-Haack: So, that was that for 20.4. That was just released this week, and we are recording this on March 7th. Just to say that.

What’s in Active Development & Discussed – WordPress 6.8 Beta                                                       

So, what’s an active development? And discussion brings us to WordPress 6.8 in Beta has been released. Beta 1 has been released. And you can follow along on the WordPress.org announcements or news. So, there will be Beta 1, Beta 2, Beta 3 and Release Candidate 1, 2, and 3 before the final release on April 15th. The test team has published, for the last few releases, always a Help Test, the next release. And this one is not different. There’s Help Test WordPress 6.8, and it helps… Well, you can help making this release the best that it can be. Finding all the bugs, not all of it, but report them. Find as much many. Try to break it as often as you can. Report the bugs.

And I have found another incentive on, actually, heeding to the call for testing is to learn more about the new features because instructions are very well done, compliments to Krupa Nanda, to learn more about the new features or the enhancements and how are they supposed to work so you can distinguish them. So, is it me that I don’t know how this works? That I don’t get it? Or is that a bug? So, they went to great lengths to do that.

You can also use Playground to test things. You don’t have to spin up a new WordPress staging site or something like that to test things. Yeah, you can go to make.wordpress.org/test to find the post or you look for the show notes on the Gutenberg Times and click on that link.

So Jessica, the WordPress 6.8 is characterized as a polished release. Is there anything that stands out for you coming to 6.8 that you’re excited about?

Jessica Lyschik: I do. It’s a polishing that I think is… I mean, as I said before, given the situation that we are in, I think this is the best that we can do. And yeah, I’ve been just scrolling through these Call for Testing blog posts that you just mentioned. And it is really thoroughly, so I would actually be excited to dive into this and do the testing because this is pretty well done.

And I think about 6.8 and the coming releases… I haven’t been paying too much attention to what is in 6.8 apart from a few things that we highlighted today, and I have probably forgotten again because I was just out of the office for two weeks. 

Speculative Loading in 6.8

I think what’s also interesting is this speculative loading thing. I think there was also just a blog post these days. So, this speculative loading is, when I understood correctly, something like a browser? Like, the browser offers this API and WordPress has added its performance improvements. The performance team will probably come after me if I do not say this correctly. But from what I understood, it’s improving overall performance of a WordPress website by using these speculation rules. So it’s about what can be prefetched or what makes sense to be prefetched next, so that when you actually click on a link on the website, it loads faster because it already knows what I have, what the browser has to load in this case.

I think this is something very interesting that might be bumping up the performance of a few websites. So, that will be interesting to see what the actual impact will be once 6.8 is out.

Birgit Pauli-Haack: Yeah, I’m excited about that too. I think the browsers are now pretty well caught up with that. Not all browsers have all the features all the time, but this is something that, I think, has a big footprint around all the browsers being Firefox, Safari, Google Chrome.

I link in the show notes too, Felix Arntz has published… Has worked on this feature, in the feature plugin before. And now, it’s coming to 6.8 and the dev note has been published now.

Jessica Lyschik: I just checked on Can I Use, and it’s actually Safari and Firefox do not support it at the moment. Chrome, Edge, and Opera do. So, there is still a bit of a… It’s not a hundred percent on all browsers, but a good chunk of browsers already support this. So I hope these other browsers, Safari and Firefox, will catch up on this because it sounds pretty promising from a performance point of view to use these speculation rules.

Birgit Pauli-Haack: I keep scrolling through the dev notes that have been published. They’re not in bulk coming out until Release Candidate 1, but John Blackburn also published a dev notes about the new encryption for the password hashing.

Jessica Lyschik: Oh. Yes, I forgot this one.

Birgit Pauli-Haack: Which there’s not a whole lot of things for users to do or even for developers. It’s just to know that the passwords are now hashed differently and increase the security of any of the passwords quite exponentially, which is really good. So, thank you for Felix and John to publish the dev notes early for that.

All right, I’m sure we are going to talk about WordPress 6.8 some more on our next show when we know a little bit more what’s in there and what’s not in there. Thank you so much, Jessica, for being here. As always, the show notes will be published on GutenbergTimes.com/podcast. This is episode 115. And if you have questions and suggestions, just send them to Changelog@GutenbergTimes.com.

And now, a plea for all those who use Spotify for their podcast pleasure, you can leave comments there. And also, check some of the stars so people know what they can expect on the show when they discover that on Spotify. Shopify. Well, yeah. So, thanks for listening and goodbye until the next time. Thank you, Jessica.

Jessica Lyschik: Thank you. Bye.

Birgit Pauli-Haack: Bye.

by Birgit Pauli-Haack at March 09, 2025 09:21 AM under WordPress 6.8

March 08, 2025

Matt: Real WordPress Security

One thing you’ll see on every host that offers WordPress is claims about how secure they are, however they don’t put their money where their mouth is. When you dig deeper, if your site actually gets hacked they’ll hit you with remediation fees that can go from hundreds to thousands of dollars.

They may try to sell you a security plan that for example at Godaddy goes from $300 to $700 a year on top of your hosting. (Don’t be fooled by the low entry price, look at renewal.) It’s heartbreaking to hear stories of non-technical people forced into these high fees to fix something their host should have prevented in the first place.

When a host is powered by WP.cloud, it doesn’t need to do this because hacks are so incredibly rare. (That’s why it may appear more expensive, but the total cost of ownership or being a WP.cloud-powered host is much lower when you factor in human time.)

One problem we’ve had on WordPress.com is we do all these amazing things and don’t tell anyone about it, something we’re trying to change with our focus this year on developers and developer tooling. One great example is we’re so confident about our security, if your site gets hacked we’ll fix it for free! We’ve actually been doing this for the better part of a decade, just never mentioned it anywhere.

Pressable (which is WP.cloud-powered) does a better job talking about these things and has a nice landing page on malware cleaning and hack recovery that says essentially the same thing.

WordPress has done a ton over the years to move the hosting industry around upgrading PHP and MySQL, PHP extensions, free SSL, and in general using our clout to advocate for user rights and freedoms from even the largest hosting companies, and I’m proud to say there are a good number, for example the ones you see at WordCamps, that have not just embraced these values but actually been more commercially successful as they’ve done so. I hope security and auto-upgrades not just for core but for plugins and themes becomes the next standard. (Jetpack does this for free, some hosts charge $100/yr per site.)

by Matt at March 08, 2025 11:07 AM under WordPress

Gutenberg Times: WordPress 6.8, Studio updates, Customize Embeds, and other Theme Design notes — Weekend Edition 320

Hi there,

That was quite a long pause in February. Did you miss me? I am back now and have a ton of great updates, videos, tutorials, and products for you in this newsletter. I won’t catch up on everything that was going on in the last four (😮) weeks. Most of it is fairly timeless.

So how have you been? What have you been working on? Hit reply and clue me in! I missed you and your emails.

Have a fantastic weekend!

Yours, 💕
Birgit

Developing Gutenberg and WordPress

We had a few Gutenberg plugin releases and WordPress 6.8 is progressing nicely.

WordPress 6.8

WordPress 6.8 release cycle goes into the hot phase. WordPress 6.8 Beta 1 was released this week and is, in general, characterized as a polish release, with user enhancements throughout incorporated into the latest Gutenberg updates. “WordPress 6.8 brings a luster and gloss that only a polish release can.” Jeffrey Paul, release co-coordinator wrote in the release post. WordPress 6.8 RC1 is scheduled for March 25, 2025, that’s also the time around which the Fieldguide will be published. The final release will be on April 15, 2025.


Test team rep, Krupa Nanda, published the Help test WordPress 6.8. This release offers a chance to find and report bugs while learning about the new features in WordPress’s next major version. Nanda’s instructions and short videos help you understand how these new features work.

Gutenberg Plugin releases

Jessica Lyschik posted a summary of two Gutenberg plugin releases. In What’s new in Gutenberg 20.1 and 20.2? she highlighted:

  • Content preview for pages in DataViews
  • Menu name shown in list view
  • Color pickers in Navigation, Social Icons and Post Featured Image get Clear control
  • Content block: color options for headings added
Content Preview for pages in Dataviews

Fabian Kägy published the release post What’s new in Gutenberg 20.3? (18 February) and highlighted two new updates:

  • Ignore sticky posts in query loop
  • Add social icon block variation for Discord
Screenshot of the sidebar option to ignore the sticky post in a query loop block.

Gutenberg 20.4 is now available for testing. It marks the last Gutenberg version to make it into the upcoming WordPress major release.

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

It’s been a while since we saw a new plugin with a collection of Blocks makes it into the plugin repository. Thanks to WP Weekly‘s Davinder Singh Kainth, for discovering it. It’s called Frontis Blocks and created by the team called WP Messiah (What a name! 🤦‍♀️) and provides 27 Blocks. It’s works with all themes, among them the Frontis theme by the same developers.


Bud Kraus shares in his blog post for Hostinger How to customize WooCommerce templates with Gutenberg blocks. He explains the shopper journey and how to access and change templates like the Product Catalog, Single Product, Cart, and Checkout pages. Customization involves adding or changing blocks in these templates. However, some templates, like Cart and Checkout, have limited options to keep them functional. The tutorial shows WooCommerce’s move towards an editing experience that allows non-programmers to customize their online stores.


Get inspiration from the Automattic Special Projects team, that just published their new site. You can browse a selected list of projects and learn how they built it. You’ll find on the list Seth Godin’s blog, the Buckminster Fuller Institute or Noma. The team also started sharing their tools, the plugins, and blocks they built and open-sourced. I am particularly intrigued by the Accordion block and the infinite scroll query loop variation.


Speaking of tools, the ClassAct plugin by Dave Ryan might be useful for theme developers and Sitebuilder. It’s a microplugin for acting on Additional CSS classes per-block in the WordPress Editor. On X (former Twitter), Ryan shared a video of how it will show up in your block’s sidebar.


Theme Development for Full Site Editing and Blocks

Henrique Iamarino, WordPress Theme designer at Automattic, discusses a new approach to designing WordPress themes in his article Beyond Templates: Reimagining WordPress Theme Design. He focuses on moving away from old, static templates to more flexible and dynamic design systems. The article highlights the need to give users tools for greater customization and creativity in creating websites. By changing the design process, Automattic aims to make WordPress themes more adaptable and user-focused while ensuring they are accessible and easy to use.

Bud Kraus had an awesome month! In his Kinsta post, he shared how to Build a block theme using the Create Block Theme plugin. This plugin is a must-have for whipping up WordPress block themes. You can start from scratch, clone something you like, or create child themes, all within the WordPress Site Editor. It lets you save theme changes, play around with style variations, and even export your themes as zip files. Plus, you can tweak theme metadata, check out the theme.json file, and reset your theme whenever you need to.

 “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.

James Le Page, AI lead at Automattic, has worked on the Excalidraw Block. It is a custom WordPress block that allows users to embed an Excalidraw editor directly into the post editor. This block provides a seamless way to create and edit diagrams within WordPress. On X (former twitter) LePage posted a short video to show off the block’s capabilities. The code is available on GitHub put needs a build step to install it successfully on your WordPress site.


JuanMa Garrido wrote about his Understanding how WordPress Hooks work from a Stack Trace. He shared how to use stack traces to analyze WordPress hooks, helping developers see how hooks work, find errors, and improve their use in plugins and themes. By looking at stack traces, developers can track function calls, identify triggered hooks, and fix plugin conflicts. This method is essential for troubleshooting complex WordPress sites where multiple hooks operate at once, ensuring everything works well together and aiding in debugging custom code related to hooks.


In his the video “Cooking with AI: Creating New Recipes with Cursor AI“, Ryan Welcher set out to improve his use of AI tools for developers in 2025. Specifically, he’s setting up Cursor AI to help him generate new recipes for the Block Developer Cookbook more quickly and with better examples.

Aslam Multani of Multidots recently published How to Develop Custom Gutenberg Blocks for WordPress: A Step-by-Step Guide. This blog post explains how to create custom Gutenberg blocks, covering everything from setting up your development environment to debugging block code. It starts by detailing what Gutenberg blocks are and the requirements, such as having a local WordPress installation and knowledge of HTML, CSS, JavaScript, React, PHP, and WordPress plugin development.
To make a custom block, it suggests using the create-block tool to set up a new plugin and explains the necessary file structure, including build/, src/, edit.js, save.js, and block.json. The post guides you through installing the block plugin and automating the build process with npm start, highlighting the functions of Edit and Save and using the RichText component for user interaction.
It also covers customization options like adding support for color and spacing, setting default properties in block.json, and creating nested blocks with the InnerBlocks component. Lastly, it touches on internationalization (i18n) using the __() function and provides an example of a testimonials block to demonstrate these ideas. However, it misses discussing when to use different tools, such as block styles or variations, before creating a Custom Block.


A new version of the local development tool, Studio, was released: Introducing Preview Sites: Pushing the Limits of Collaboration with Studio. The WordPress.com blog post highlights upgrades to “Demo Sites,” now “Preview Sites,” enhancing local development and simplifying sharing with clients and teammates. Key improvements include:

  • Increased Storage: Expanded from 250 MB to 2 GB.
  • More Sites: Doubling from 5 to 10 preview sites.
  • Personalized URLs: Shorter, user-specific URLs.
  • Timeline: Available for seven days post-update.

The name change to “Preview Sites” emphasizes their role in showcasing work-in-progress and collaboration. Enhanced Preview Sites are available to all Studio users, with existing Demo Sites converting automatically.

WordPress Developer Blog

Two new post on the Developer Blog might catch your attention:

Troy Chaplin took on the monthly round up What’s new for developers? (February 2025). The post mentioned WordPress 6.7.2 with bug fixes and enhancements, and took a look ahead to WordPress 6.8’s data view and performance improvements. Gutenberg celebrated its 8th birthday with versions 20.1 and 20.2, introducing enhancements to blocks and UI customization. Updates include improvements to the Navigation, Page List, and Social Links blocks.


Róbert Mészáros guides you through his tutorial on how to customize WordPress embeds to match your theme. He discusses different ways to adjust WordPress embeds to fit a site’s theme and branding, covering basic CSS styling, advanced changes like modifying excerpts, ensuring uniform image formats, adding features like a “like” button or publication date, and creating custom embed templates. The article also reviews the history of WordPress embeds, the default embed view, and loading template files from a plugin, encouraging developers to try these options and enhance WordPress embeds.


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

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

GitHub all releases

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


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


Featured Image:


Don’t want to miss the next Weekend Edition?

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

Thanks for subscribing.

by Birgit Pauli-Haack at March 08, 2025 12:45 AM under Weekend Edition

March 07, 2025

Do The Woo Community: Do the Woo Friday Shares, March 7, 2025

WordPress continues to lead in enterprise solutions, showcasing new tools, addressing gender inequality in leadership, and enhancing WooCommerce functionalities while promoting community events.

by BobWP at March 07, 2025 09:59 AM under WordPress Core

March 06, 2025

Do The Woo Community: Designing Products Users Love, A Deep Dive with Shahjahan Jewel

In this episode, James, Katie, and guest Jewel discuss user experience in product design, the importance of customer feedback, team dynamics, and the growth of WP Manage Ninja's innovative products.

by BobWP at March 06, 2025 03:17 PM under Product Makers

Do The Woo Community: Making the Right Decisions for Your WordPress Business

Building a business in the WordPress and WooCommerce ecosystem requires careful decision-making. Here are some insights on pricing strategies, plugin vs. SaaS choices, and the benefits of strong partnerships for growth.

by BobWP at March 06, 2025 10:48 AM

March 05, 2025

WPTavern: #159 – James Kemp on WooCommerce Innovations and Trends in Selling Online

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 WooCommerce innovations, and trends selling online.

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 James Kemp. James is the Core Product Lead for WooCommerce. After working with WooCommerce, running a plugin shop for 10 years, he joined the team at the end of 2023 to help shape the future of e-commerce.

James talks about his journey with WordPress and WooCommerce, and explains his role at Automattic, where he’s tasked with connecting the community’s feedback to the developments in WooCommerce, ensuring that the Woo platform continually evolves and improves.

He discusses the innovations within WooCommerce, the challenges of balancing the needs of small and large scale stores, and how the team navigates an environment filled with both competitors and opportunities.

He gets into the positive impact of WooCommerce’s recent rebranding, and how the system positions itself amidst the ever-growing competition from SaaS platforms like Shopify.

James shares his insights into the trends shaping e-commerce, like the seamless integration of newer technologies and consumer buying habits.

If you’re keen to understand the breadth of WooCommerce’s impact on e-commerce, or are curious about the direction of online shopping, 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 James Kemp.

I am joined on the podcast by James Kemp. Hello James.

[00:02:50] James Kemp: Hello, how are you?

[00:02:51] Nathan Wrigley: Yeah, good. Nice to speak to you. James is on the podcast today to talk all things WooCommerce. And he really is a very, very credible person to talk about WooCommerce, because James is the Core Product Lead for WooCommerce over at Automattic.

However, when I say that title, James, I don’t really know what it means. Will you just enlighten us? And also, if you feel like throwing some other biographical information at us about your history with WordPress and things like that, feel free.

[00:03:17] James Kemp: Of course. Yeah, I mean, we’ve spoken a couple of times on a podcast like this. I don’t know if we’ve done the Tavern one before.

But yeah, as a quick introduction, I started using WordPress in 2009, and I started building with WooCommerce in 2011. And from that time I worked with customers and specifically like building websites for customers who needed websites.

And in that time I built up a collection of plugins, which I sold on a premium basis, which eventually turned into IconicWP, which was a WooCommerce plugin shop with 14 or 15 premium plugins. Sold that, well, that was acquired in 2021 by Liquid Web, Stellar. And I stayed there for a couple of years, carried on working. My whole team came over with the acquisition. We carried on just working as we were really, but under this kind of bigger brand of products and WordPress software, which was quite nice. It was nice to kind of get that experience from companies selling products like we were, but they were at a much bigger scale than we were at the time. That was a nice experience.

And then, yeah, towards the end of that, I reached out to Paul, who was the CEO, at the time, of WooCommerce, and just kind of said, I feel like I could have a good impact on WooCommerce itself, is there anything there for me? And I was kind of open to whatever that might look like. There was no job description that I applied for. I just kind of reached out and said, this is what I want to do, this is what, I like doing, this is what I’m good at. And then, yeah, here we are just over a year since I joined.

I joined as a product manager. And like you say, now I’m a Core Product Manager, which is a new role within WooCommerce. So a Product Manager would be, and for context, there’s eight or nine Product Managers within WooCommerce. When I joined, we each kind of had an area of focus. So my area was order management. So any project or improvement or just, my day to day would be looking at order management and, how can we make this better? It kind of shifted outside of that a bit as well into other areas. But each Product Manager has that kind of role where they’re focused on one kind of key area of WooCommerce.

But there was never really any product manager that had an overall vision of the whole product. And that’s what the Core Product Manager role is. So I’m less focused on one specific area, and more focused on just, how can we make the whole thing better? And part of that role is kind of connecting the dots a bit. One team’s working on this, another team’s working on that, how do they overlap? But also connecting the community dots to the stuff that we actually put out there. So, what are people asking for? What are the common kind of requests that people have, or the complaints that people have? Or even the positives that people have and, how can we make those things better?

[00:06:12] Nathan Wrigley: So is there just one of you? So there’s one Core Product Lead. There’s not multiple of those.

[00:06:18] James Kemp: Correct.

[00:06:18] Nathan Wrigley: Oh gosh, that’s really interesting. So you’ve got like the 10,000 mile high view of the entire project. And so you are kind of open to suggestions, innovations, improvements, tweaks, that all comes under the purview of your job.

[00:06:32] James Kemp: Correct, yeah. There’s different areas. There’s what we call product, which is kind of the user facing experience. And by user I mean merchant, and probably customer as well, so the visual aspects of the product that people interact with. And then there’s the platform side of things, which are backend architecture and performance and all those kinds of things.

So I’m primarily focused on the front end aspect, not front end but, you know, the core experience we call it. I am actually focused a lot on the platform side of things at the moment as well, because the person who usually does that is on sabbatical, so I’m kind of helping out a bit there. And it’s quite nice to have, you know, that understanding as well, for approaching core experience type things. And it also encompasses the WooCommerce app and many of our premium extensions, many of our marketplace extensions, premium or free.

[00:07:22] Nathan Wrigley: I’m guessing that if you ask anybody the question, is their inbox pretty full? You know, the to-do list that you have is pretty full, everybody would probably say, yeah, I’ve got plenty on my plate. But it sounds as if you may well have a lot on your plate.

Now, I don’t know if there’s a lot that you’ve got to deal with in there, and you’ve got a lot of ideas, and innovations that you’d like to push forward. But is it fair to say that there’s a ton of innovation still to be done inside of WooCommerce?

[00:07:46] James Kemp: Yeah, for sure. It’s something that I’m still trying to figure out. Like, how do you stay on top of all of these things and, where is my input within this most valuable? Because I’m still working alongside all the other product managers.

And actually that’s been really nice to kind of connect with a product manager that’s working on something specific, and work with them to make that the best it can be for WooCommerce.

But yeah, I’m still trying to figure out how to like organise all of these things so they’re not just in my head, but they’re out there in a manageable way.

[00:08:18] Nathan Wrigley: How do you get intelligence about what needs to be done? I mean, obviously there’s the team within Automattic that you deal directly with, I would’ve thought of, but do you keep your door of your office kind of half open a little bit? Are you prepared to listen to community suggestions?

And again, I’m not trying to get you to give out your email address or anything, but is there that element still? Do you still listen to people out in the community, users, and what have you? Do they come directly to you, or is there some kind of filtration process which people have to go through in order to get ideas in your head?

[00:08:46] James Kemp: There’s many ways. Yeah, I think one of the things that I love most is talking to the people that actually use it. And I do that primarily on X or Twitter. I talk to a lot of people over there.

The downside to that is the majority of them are agencies and developers. It’s not a downside, the downside being that I don’t get that kind of open communication necessarily with merchants directly. So if I want to talk to a merchant that’s more of a filtered, as you say, it’s an intentional, you know, I have to reach out to a merchant and schedule a call and all that kind of stuff. There is the occasional merchant on X, but it’s not their stomping ground.

So yeah, I’m also in the Slack, the WooCommerce community Slack. Some of what I’ve implemented is these kind of external channels within our own Slack. So one example of that is a project we’re working on for fulfillment statuses, where I got Becca from Kestrel WP and Patrick Garman from Minesize into one of our internal Slack rooms to discuss and kind of help shape this project. So they’re directly involved in that way in stuff that we’re working on.

And I think something that we really want to do is be really transparent with like, this is what we’re working on. You may well have seen over the course of the last year or so that that has been the case, via GitHub discussions, via the Developer Blog, via Slack, the community Slack. But yeah, I love getting feedback from people on Twitter. I still don’t know what to call it, Twitter or X.

[00:10:18] Nathan Wrigley: I often wonder if the sort of inside baseball of WordPress is a little bit hard to penetrate, because I’m imagining there’s a lot of people who use WordPress that in a million years have never opened up the WordPress Slack, GitHub is not a thing for them. And I’ve always wondered how people such as yourself, you know, in senior positions get that information. How does it get to you? And X, Bluesky, whatever the alternative is, that’s a really interesting way of kind of completely circumventing that process. I will make sure that your profile, your X profile is linked in here and then people can reach out on that basis. Yeah, that’s great. Thank you.

Let’s just paint the picture of Woo, and how big it is because we keep hearing the statistic. The one that everybody talks about is this 43%, which is the WordPress statistic. And I never quite know how to manage that in my head, what that exactly means. But a fairly sizable number is also the e-commerce side, the WooCommerce side of WordPress.

Where are we at in terms of the web, and in terms of WordPress, how much of WordPress is WooCommerce, and how much of the internet is Woo? And every time I hear this number, it changes a little bit. But every time I hear it, it’s still breathtakingly large.

[00:11:24] James Kemp: Yeah, that’s an interesting one actually. In terms of how much of WordPress is Woo, I’m not sure on that. I think we could probably calculate that based on the figures I do have, which is how much of e-commerce is WooCommerce, and that is 37%.

[00:11:41] Nathan Wrigley: 37%. Okay, so whatever the percentage is, be it the top million websites or the top 10,000 websites, whatever that metric is, let’s assume that that’s solid and safe. 37% is done on a WooCommerce platform. That is breathtaking.

[00:11:56] James Kemp: Which is a huge amount, for the listeners, and for you if you want to check it out later. If you go to woocommerce.com/newsroom, we update these numbers every month. We have some numbers there, like there’s 3.6 million live installations. 37% of e-commerce sites are powered by WooCommerce. There’s 1,000 plus official marketplace extensions. That’s actually going to grow, I think substantially this year.

And then, yeah, some other stats that are listed there, which I think are useful to keep an eye on. And there’s, I believe the team that updates those numbers kind of, they take the data primarily from Store Leads, which is a data gathering outfit. And I think they kind of dial them back a bit, rather than, you know, inflating them, I think they actually go the other way.

[00:12:41] Nathan Wrigley: In terms of the trend of that, so the 37%, I’m not looking at that chart at the moment, but is your impression that, has it stagnated, has it gone up broadly in the last, let’s say five years, something like that? Is WooCommerce basically growing, stagnating, declining?

[00:12:54] James Kemp: Over the five year, I would expect it’s gone up. There’s no graph to look at. There probably is somewhere, but I don’t have it in front of me now. But I do know that this was updated this week, I believe. And it was updated from 35% to 37. So there’s definite growth there. And I would expect, just the nature of e-commerce in general, that that number’s grown over the course.

[00:13:16] Nathan Wrigley: When you say that, what’s the thing in your head which is promoting you to say the nature of e-commerce? Because I really don’t follow e-commerce, but I have this impression that during the lockdown period, 2019 and on, it felt like everybody, for very credible reasons, had to move whatever they were selling to an online format. So I imagine there was a bump there.

But also it feels like the world is now inundated with pocket size technology, which means that I can buy anything 24/7, no matter where I am. And so it feels like high streets in the UK, the shutters are going up. Bricks and mortar shops seem to be closing. Certainly where I live, that is a broad trend. It’s not particularly rapid, but it’s definitely a trend.

And I’m imagining that the confluence of mobile technology, ubiquity of internet connection, computers available all over the place, certainly in the country where you and I both live. It feels like this inexorable rise, this trend towards purchasing things at 4 o’clock in the afternoon, sitting on a sofa, a bus, wherever you might be. It does feel like that’s the way the world is moving. Are those kind of the intuitions that you have when you say WooCommerce is rising for obvious reasons?

[00:14:23] James Kemp: Yeah, exactly. I think just the nature of the internet and the online world has kind of exponentially grown since its inception, right? And I would expect that e-commerce will grow with it.

I think one of the greatest things about the internet is that you can buy online. I should look into the history actually, but I can’t imagine what the thought process was back when the internet was invented. Did they imagine that e-commerce would be a thing? That people would buy stuff, even from the other side of the world, and have it shipped out to them in a matter of days or weeks.

And I just think as technology evolves, and we’ve seen the boom in AI, and just the boom in like generational development on computers, and coding and all of that is advancing, and I think e-commerce will follow suit as well.

[00:15:12] Nathan Wrigley: Yeah, it feels like there’s no place but an upward trend for e-commerce. Now, whether or not WooCommerce fits into that landscape perfectly in the next decade, we’ll see. But it feels like I, and I can really only rely on myself, I feel like I’m going to buy more things online in the decade to come than I am this year. It feels like each and every year, my desire to get on my bike and go into the town centre dwindles, and I’m far more likely to buy things online.

And now the merchants have pivoted their offerings so that, you know, if you don’t like it, you can freely return it and things like that. So even the impediments that were there have suddenly changed, and it’s just remarkable.

And also the mere fact, just capture in your head for a moment, the fact that you can get all of this for no money down. The WooCommerce platform, and I know, in order to get the best out of it, you will definitely want marketplace things, third party, but other places as well. But the thing is free. It’s completely free. And I find that utterly remarkable. I just think that’s breathtaking in all honesty, that that’s available.

[00:16:15] James Kemp: Yeah, I think it’s one of the key selling points about WooCommerce is that you can get started for free, as close to free as possible, when you account for hosting and transactional fees that naturally come with any platform.

But on top of that, with WooCommerce specifically, and with the age of AI now, you could make WooCommerce do what you want it to do for free. And every site could be tailored to specific needs, and like a specific execution of functionality without too much technical knowledge, which I think is really interesting.

And you’ve seen people are building apps, and I’ve built a few as well, specifically for needs that they want to solve. I saw one yesterday, I think it was Maddie on, Twitter, I can link to it. She built an app to automatically put an emoji over faces in photos. I don’t know if you’ve seen, when parents share photos of other people’s children and that kind of thing, they typically put an emoji over the face. She said she was getting annoyed at having to do that with every photo. But we’re in that era now where you can kind of roll these things with no technical knowledge, whether the output is good, I think is questionable, but it’s pretty good.

[00:17:24] Nathan Wrigley: Does the advent of AI, and what you’re suggesting, you can add your third party stuff, if you like, for want of a better word, to WooCommerce with the assistance of AI. Does that undermine the longevity of the free, open source WooCommerce project? Because I imagine that there’s a lot of underpinnings there, you know, the marketplace that WooCommerce, as I imagine those plugins that are sold to add different functionality and what have you, that must in some way pay for the freeness of it all.

Does AI, does that concern you? You know, that if we erode the need to purchase third party software in order to get out what you desire, yeah, does that erode the possibility of WooCommerce being free in the future?

[00:18:05] James Kemp: I don’t think so. I think it assists. I think it depends what you’re making. Like, I wouldn’t want to build out a full subscriptions platform just using an AI prompt. And maybe that will become more advanced in the future. I think as someone running a business, you don’t want to be dealing with this code yourself, maintaining it, making sure it stays up to date. And I think that’s the case for, or that has been the case since e-commerce software existed. There used to be a trend of rolling your own e-commerce solutions, and I think that’s less likely to happen these days.

[00:18:39] Nathan Wrigley: Yeah, it’s a good point. If you think about just a regular WordPress website, if it’s just a brochure site with no e-commerce attached, go with the AI, you know, it seems like there’s loads of scope there. But obviously if you’ve got the compliance, and the financial obligation, and all of the law that underpins an e-commerce shop, I imagine there are impediments in people’s heads which will say, wait, did an AI make that? Are we really going to trust that? So maybe it inoculates itself given the nature of the websites which are in question.

Okay, just moving on, tell us a little bit about the kind of people that are using WooCommerce. Now, I know this is a very, very broad question, but in my head, for some reason I have it, that a significant amount of people that are using WooCommerce will be small stores. But I’m guessing also maybe WooCommerce really does dig deep into the enterprise as well. Does it run the gamut of everything? Or is there a kind of focus for you, and teams within Automattic because there’s a certain type of clientele which largely consume WooCommerce?

[00:19:37] James Kemp: Yeah, it does kind of span everything. So people just starting out either want low cost, in which case WooCommerce is an obvious choice. You can start setting things up, especially for brand new e-commerce, whereas they’re just selling single products. There’s nothing too technical there that would require an expense of some kind. So it’s super easy to spin up a WooCommerce site and test it out pretty much free.

So yeah, we have that audience. It’s not necessarily our focus, our focus is primarily the higher revenue, higher traffic e-commerce stores, because that’s the aspiration for anyone selling, right? They want to become successful, they want that to be their business, is e-commerce. And those are the users that we’re focused on. And then naturally anything we do for them is going to trickle down to benefit the people who are just starting out with the platform.

So it does span a wide range of users, but we do focus in on the higher revenue and high product volume, high traffic, those kind of things. Or at least that’s what we’re focusing on this year. That target evolves over time. But that’s been our focus for most of my time since I’ve been here. So it’s nice to have that vision of who’s using it and what we can do to make the platform as good as possible for them.

[00:20:52] Nathan Wrigley: We have this expression in the UK, Jack of all trades, master of none. I don’t know how that works outside of the boundaries of the UK, but it basically means if you try to be everything to everybody, you sort of succeed at nothing. It’s something akin to that basically.

And I’m wondering if there are bits of WooCommerce which you have to manage those sort of trade offs. Like, okay, if we build this thing, which feels like it’s a real enterprisey thing, how is that going to work with our more modest users, let’s say?

Or if we really focus on the more modest users, how are the enterprise going to feel like that? And it not being a niche, and it being the full spectrum of sites out there, yeah, at times that must be actually quite frustrating, I would’ve thought.

[00:21:29] James Kemp: It’s a challenge, yeah. It’s something that we’re working on at the moment, is making the base of WooCommerce have the majority of features for the majority of users, the features that you’d expect in an e-commerce platform, which I’ve touched on in other podcasts if you want to go and find them.

But it’s a process called More in Core, which is the kind of code name for it. Where we’re just trying to build out the base product to have the majority of things that merchants and builders need, without needing to go and find all these plugins and custom development and things like that.

But the challenge is which features. The features that people need are going to change depending on what type of store they’re running. So I’ve seen a lot of people want subscriptions in Core. And then I’ve also seen the complete opposite where people don’t want subscriptions in Core because they see it as bloat. There’s a challenge there for sure, to figure out what that kind of sweet spot is without being bloated, but also without nickel and dimming, and making the average number of plugins required too high or too low.

[00:22:28] Nathan Wrigley: I’ve often thought that if I worked at Microsoft on Windows, the software, the OS, it would be my constant annoyance that I had to think about every possible permutation of hardware that could ever be used. Whereas if I worked for Apple and was working on the Mac OS project, it’d be like, there’s just this one set of hardware, it’s just so much more straightforward, we build it.

And I imagine that commercial rivals, things like Shopify, and we can get into that in a moment, probably have it easier in that sense because there isn’t this, well, I know that they have an ecosystem of sort of third party apps, I believe they’re called. But there isn’t this whole backwards compatibility thing that 5,000 different plugins that bind into WooCommerce and what have you. And so I guess you’ve always got to be taking real careful steps when you develop a new feature or tweak anything, which maybe the other platforms don’t have to think about in quite the same way.

[00:23:16] James Kemp: Yeah, I actually posted about that exact thing on X or Twitter earlier. I’m just going to call it X. I want to call it Twitter, but I’m going to call it X. It’s a challenge because, and this touches on the 37% number, like any update we roll out is affecting over a third of all e-commerce stores online, which is a crazy number.

It has to be backwards compatible, it has to be rolled out in a way that isn’t going to break things. There’s a lot more consideration that needs to happen because of the multitude of environments that could exist. There could be bad hosting, there could be good hosting. There could be low performance, high performance, number of products, different plugins, different themes.

For a platform like ours, that is one of the greatest challenges, but also one of the greatest strengths as well, because of how flexible it is. In a platform like Shopify, like you say, they have an app marketplace, but it’s a lot more restricted. There’s only really a handful of ways to do something. Whereas with WooCommerce, you’ve kind of got full control because you are hosting it yourself. You can pretty much do anything. Which, like I say, is a challenge, but also a strength.

It requires navigation, and I touched on this in a, I do a monthly, Inside wooCommerce podcast. The last one that went out was with Julia, who is the lead for our release process. And it’s worth a listen, because it’s quite interesting to hear, now, how we roll out releases and how we’re able to test and watch for signals for issues that might arise. And be able to roll it back, fix that, and then roll out the updates. There’s quite a nice process there now, which we’ll obviously refine as time goes on, but yeah, it’s a challenge.

[00:24:59] Nathan Wrigley: More recently, and we don’t need to get into the story behind it, but there is a story behind it. But the Automatticians, so the people that work for Automattic, have in some cases been repurposed. So their work that they’ve been doing for many years in one direction has now been pivoted. And I think it’s probably fair to say that focusing on things which generate revenue is a crucial part of the decision behind that.

I’m wondering if that’s had an impact. So this whole thing is not really that old, it’s maybe only five, six weeks old, something like that, so maybe it hasn’t yet. But I’m wondering if it’s had actually a positive impact on the teams that you work with, or maybe there’s steady away, no change.

[00:25:38] James Kemp: I would say there’s no change actually. I mean, WooCommerce has always been, we’re building a free product, but we are also a business, and we’ve always been a business. We wouldn’t be able to afford to put out a product and not have any money coming in to continue developing it. There’s always been a business aspect to WooCommerce.

But yeah, the teams that have kind of moved off of the open source contributions that they were making previously, I haven’t seen any of them come over to WooCommerce. And maybe they have, if they come in as engineers, then I probably wouldn’t see that anyway. But yeah, in my day to day, I haven’t seen an impact. But, you know, Automattic has multiple products and experiments and things that exist outside of WooCommerce, and I honestly don’t dig into them too much. I’m very focused on the WooCommerce side of things.

[00:26:27] Nathan Wrigley: You’ve recently, I say you, WooCommerce recently had an entire upending of the branding. If you don’t follow it very closely, it may be that you haven’t seen this story, but maybe it was not that long ago in the last week or so. It feels like the message dropped that a lot of the branding has been redone, and I often look at rebranding and I think why all that effort?

What was really the point of that? What was the need to upend everything, and make people have to see something new? And I’m just wondering if you know what the point of that was? I mean, it’s nice. It looks lovely. Don’t get me wrong. I thoroughly love it. But I’m curious as to what the reasoning was. Did it feel stale previously? What was going on there? Do you know?

[00:27:06] James Kemp: All of the above, yeah. So I’ve known about the branding, in its current form of, what it’s gonna be like since maybe October last year. And it’s been really interesting to watch. If you compare what we had previously against this, it’s clear like why it had to happen. The branding that we had previously was the same branding that WooCommerce had when it was initially formed via WooThemes. If you compare it, it just looks out of date. The colors are flat and, not very inspiring. And the new branding now allows us to be a bit more modern, I think. It’s modernized the brand.

But it also opens us up to be able to go out and do more effective marketing and acquisition that we haven’t done prior. Branding isn’t just changing the logo and updating some colors. There’s a whole array of assets that come with it, and like a story behind the assets and what we’re trying to put out there into the world. Which we didn’t have before, we just had a logo and some colors.

[00:28:04] Nathan Wrigley: There’s this sort of nod to a shopping cart in the W of Woo, which is actually quite clever, I think. And you’re right, it does just smack of more modern.

Being a complete non-designer, I can never summon up the vocabulary to express why I think something looks good. But saw the new branding, and I saw the video that was associated with that, and I did think, yeah, that’s great. That looks really great, but I can’t for the life of me tell you why it looks great.

But interestingly though, was there a market push, not just because it was stale, and let’s move this conversation into the rise of the SaaS. Because over the last period, the Wixs, the Squarespaces, the Shopify and all of these other things, I’m sure there’s many more. They’ve brought to the market a fairly affordable alternative. There’s nothing free, as far as I’m aware, but it’s a fairly low monthly cost. And I imagine over time these companies are eating up some of the new people, maybe even taking people from WooCommerce. I imagine it’s a bit of ebb and flow and what have you.

But was it that, were they becoming more professional, more visible in the world? Super Bowl ads and all that kind of thing. Was there some of that in the rebranding as well?

[00:29:14] James Kemp: Yeah, I imagine so. I think if you look at our branding previously, I don’t think it was necessarily thought out as a brand as such. I think it evolved over time. Whereas this was, the rebrand was much more focused, who are we trying to connect with here? What type of customer are we trying to pull in? And how can we reach them? What do they want to see? And I don’t think we had that before.

And yeah, definitely it helps us compete with these SaaS solutions that are quite easy to pitch. You know, influencer can pitch this stuff, because they have cool branding and, it’s hard to say really.

Like I think you could say about any product, like if Apple had a really badly designed, like 3D Apple from the nineties as their logo. In this modern era of what you expect from a brand, and a brand that’s powering 37% of all e-commerce or, I don’t what Apple’s market share on mobile devices is, but I imagine it’s pretty high.

It’s just something that needs to be considered, and there needs to be a thought process behind why we look like we do, and who we want to attract with that. And we didn’t have that before with the previous speech bubble thing.

[00:30:25] Nathan Wrigley: I remember listening to, I believe it was Bill Gates, this is many years ago, and Bill Gates was asked a question by an interviewer and it was, what keeps you awake at night, in terms of the longevity of Microsoft? And he said three things. Google, Google and Google. And basically he’s terrified of Google.

I’m gonna pitch the same sort of question to you. Of the SaaS things out there, are there any bits out there which make the Woo team think, oh gosh, that’s interesting. We need to copy that?

Does the sort of gouging out of the pricing, their very affordable pricing, those kind of things. How do you cope with that? How do you compete with that, with something which is basically free? I don’t know if that keeps you awake at night.

[00:31:06] James Kemp: Obviously like any business has its competitors. There’s nothing that’s come up that we’ve been like, oh, we’ve got to copy that and we’ve got to get that in. It’s more like comparatively are we offering an equal playing field to a potential customer?

And this ties back into the More in Core stuff that I was talking about. Is there stuff that not just Shopify, but other platforms have in their core offering, and this may be like low priced or free plans, or there’s other self-hosted versions as well that exist. They are comparatively free. Are we offering the same functionality? Do we have those essential features available? Yeah, we do, but do we charge for them? Probably, if there’s stuff that’s missing, there’s probably a premium extension for it. Or there’s a free extension for it, but it requires the merchant to go out and find it, rather than like us presenting it to them as a solution when they need it contextually.

Yeah, things like that are definitely considerations. We need to be innovating, and we need to be keeping up as well. That could be said about any platform versus another platform that there’s always, again, going back to Apple, Apple and Samsung have this kind of to and fro.

So yeah, it’s a consideration for sure. The target audience of someone going onto Shopify versus someone going onto WooCommerce is slightly different. The kind of core things that they are looking for are what we need to be offering.

[00:32:31] Nathan Wrigley: Okay, that’s interesting because if I was a WooCommerce user, which as I explained I’m not, that would be the sentence I needed to hear, I think. The people working in the offices and the places where you are working is, okay, we are keeping an eye on what the competition are doing. And if something is a moving, shaking feature, which is upsetting the industry and everybody wants it, then you’ve at least got your beedy on it.

[00:32:55] James Kemp: That’s one part of it as well. What are the competitors doing, but also what are our marketplace sales saying? What are the trends saying in e-commerce, even TikTok, Amazon, like all those kind of things that aren’t directly related to what we do, that’s accounted for as well.

And also what are the customers saying? And we touched on it earlier, but we have a whole, what we call the feedback river, which is just a big database of feedback from everywhere. From within the plugin itself. From support. From reviews and from wordpress.org, and like all of these places combined into one database. So yeah, I think you have to keep an eye on all of it. And the challenge is figuring out is this essential? What percentage of users actually want this specific thing?

And actually that’s always been a challenge, like even working on much smaller scale products at Iconic, it was always hard if a customer reaches out and says, oh, I wish it did this, it was hard to say no to that, because you are excited that someone’s using it, and they want to adapt it to their own use case. But you have to take into account, is the effort to implement this going to be valuable for everyone? Is this the priority for the majority, or is it just going satisfy this one person? You have to do that at scale now, or I have to do that at scale.

[00:34:14] Nathan Wrigley: I know that time is short, so I’m just going to pivot just for one final question before we leave and it’s, it really has nothing to do with WooCommerce specifically, although it may? And that is, I’m just curious if you know of any interesting things which are happening around the periphery of e-commerce that you personally are finding interesting and engaging. Something that maybe our general audience won’t have come across, because they’re not deep in the weeds of it.

That could be inside WordPress. I dunno, the Interactivity API, or it could be something the browsers are thinking about doing, or third party vendors who’ve got some curious technology that we might not have heard of.

So, really just any interesting thing that James has spotted lately that you think we might want to look at?

[00:34:54] James Kemp: Yeah, I dunno whether I have anything that nobody’s ever heard of.

[00:34:57] Nathan Wrigley: That’s fine.

[00:34:58] James Kemp: There’s a definite rise in platforms offering their own e-commerce. So, TikTok, commerce and all that kind of stuff is growing. And you touched on, something before we started the call actually, which kind of relates to that, the ability to see something on a device and just purchase it there and then. And within TikTok you get that experience. Within a typical e-commerce platform, you have a flow that you go through. You’ve got the cart, and then the checkout. You’ve got to populate details. So yeah, I think there’s gonna be a, an evolution into how quickly can I buy something. And that’s what the merchants want. Whether it’s good for the population and spending habits, I’m not entirely sure.

I personally love the experience on, like Amazon, for example, and I don’t know how long they’ve had it, it’s been there a while now. But on product pages, you don’t need to go through the cart process, you can just click buy now. Although that has tripped me up a couple of times.

[00:35:53] Nathan Wrigley: Yeah, me too.

[00:35:54] James Kemp: You press buy now, and it goes on some card that you never use.

So yeah, I think that is a definite kind of trend, that I’ve seen a lot of. And I think we touched on something earlier as well, which I haven’t seen much in the way of solutions to it. But one of the key things about people buying from a brick and mortar is that they can try on the product and they can physically see the color of a product, and touch the product. Which is possible. You can order now and it’s getting a lot easier to return stuff. But can you do that with a sofa, for example? So, I expect that we’ll see some innovations around that.

[00:36:33] Nathan Wrigley: Sort of augmented solution, where you can drop room and, yeah, size it up, and things like that.

[00:36:38] James Kemp: Yeah. I don’t know what that looks like.

[00:36:40] Nathan Wrigley: No, and it will be sort of a strange simulation of reality, but probably enough to get a proportion of the people over the wire, I would’ve thought.

[00:36:48] James Kemp: Yeah, for sure. There’s been AR stuff for a while now, right?

[00:36:51] Nathan Wrigley: Yeah, and things like, you want to put a logo on a t-shirt, here’s what that look like on the t-shirt. Those kind of things.

I think for me, one of the most, most interesting things is what the mobile wallets have done to my capacity to spend. I just that is remarkable. Especially out in the real world where you take the Tube in London, the underground, and you just don’t do anything anymore. You just walk by a thing, and your phone’s in your pocket, and it registers it, and you walk out and at the end of the day you get a bill, and so these kind of seamless solutions.

[00:37:21] James Kemp: I don’t feel like you have that so much on a computer though.

[00:37:24] Nathan Wrigley: No, but I wonder if that’s coming with, I don’t know, biometrics. Like purchase this, put your finger print in, your done.

[00:37:33] James Kemp: I think that would be nice. I still populate, I use 1Password, so it does it for me, but I still populate the card.

[00:37:39] Nathan Wrigley: An intermediary, a trusted intermediary getting in the way. Yeah, it’s interesting. Again, I wonder if those kind of things might be handled natively by browsers, and things like that.

Anyway, we’re sort of staring into the future, and we’ve no idea. But I know that you’ve got to go in about 30 seconds time, so I will just round it off by saying James Kemp, fascinating chat about all things WooCommerce. I appreciate it, and all the hard work you and your team are doing to democratize e-commerce. Is there anything you want to add just before we round it off? Maybe a Twitter handle or something like that?

[00:38:08] James Kemp: I’m jamesckemp on most things. C, the letter C. Yeah. The only thing I’ll add is just, if you have questions, ideas, theories, my dms are open there, so I’m happy to hear it.

[00:38:21] Nathan Wrigley: Well, thank you very much, James Kemp. Been a pleasure chatting to you today. Really appreciate it.

[00:38:25] James Kemp: Thank you very much.

On the podcast today we have James Kemp.

James is the Core Product Lead for WooCommerce. After working with WooCommerce running a plugin shop for 10 years, he joined the team at the end of 2023 to help shape the future of e-commerce.

James talks about his journey with WordPress and WooCommerce and explains his role at Automattic, where he’s tasked with connecting the community’s feedback to the developments in WooCommerce, ensuring that the Woo platform continually evolves and improves.

He discusses the innovations within WooCommerce, the challenges of balancing the needs of small and large-scale stores, and how the team navigates an environment filled with both competitors and opportunities.

He gets into the positive impact of WooCommerce’s recent rebranding, and how the system positions itself amidst the ever-growing competition from SaaS platforms like Shopify. James shares his insights into the trends shaping e-commerce, like the seamless integration of newer technologies and consumer buying habits.

If you are keen to understand the breadth of WooCommerce’s impact on e-commerce, or are curious about the direction of online shopping, this episode is for you.

Useful links

WooCommerce

IconicWP

Kestrel WP

Patrick Garmen from Mindsize

Woo Newsroom

Store Leads

Details about ‘More in Core’

Inside Woo podcast

James on X

by Nathan Wrigley at March 05, 2025 03:00 PM under woocommerce

Do The Woo Community: Decentralized Social Networks & WordPress with Alex Kirk

In the episode of Open Web Conversations, Matthias talks with Alex about the Friends plugin, decentralized networks, and transforming WordPress into a social networking platform.

by BobWP at March 05, 2025 01:54 PM under Fediverse

Do The Woo Community: WP Day and WP Zone at CloudFest 2025

CloudFest 2025 will occur from March 17-20 in Germany, featuring the WP Zone to connect WordPress and cloud communities, offering networking, tools, and collaboration opportunities for attendees.

by BobWP at March 05, 2025 09:31 AM under CloudFest

HeroPress: From Warfare to WordPress: How We Survived and Transformed

Pull Quote: WordPress kept us afloat. It fed us. Here is Aleksandr reading his own story aloud.

Dedicated to the third sorrowful anniversary of the war. With gratitude to our European partners.

A Company Built in the Heart of Kharkiv

Before the war, our company was thriving in the center of Kharkiv — a large, developed, and beautiful million-strong city. We lived and worked just 45 kilometers away from what turned out to be a massive ticking time bomb.

We had just completed a beautiful new office renovation — a space filled with energy, collaboration, and ambition. At the time, DreamDev had two divisions: one handling large-scale projects with Laravel and Vue.js, and the other — a WordPress agency primarily working with Elementor and WPBakery.

We believed our future lay in big, ambitious U.S. projects. We chased tight deadlines, endured weekend calls, and thrived under pressure. It was exhausting and stressful, but we had no idea that the real challenge was yet to come.

February 24, 2022 – The Day Our World Collapsed

No one believed war was possible. Even as rumors spread, we convinced ourselves:

“This can’t happen. Not here. Not in the 21st century” 

Then, at 4 AM on February 24, our world turned upside down. Our work chats flooded with messages: “The war has started.” Explosions shook the city. The sky turned red with fire. Deafening sounds filled the air. We later learned they were Grad rockets, but at that moment, all we felt was shock, fear, and disbelief.

Our brand-new office stood empty. The streets outside looked like a scene from a dystopian movie — people running, children crying, cars were abandoned. As we hurried to gather what we could, Russian tanks were already at the city’s outskirts.

And just like that, a new chapter of DreamDev’s story had begun.

Survival Mode: When There’s No Plan, Just Action

We left Kharkiv, seeking shelter in an old house on the city’s outskirts — a place built before World War I. A war from another time, yet history was repeating itself. Our memories from those first days are scattered, and fragmented — banks stopped working, teammates went silent, chaos spread. We had no answers. But we had work. So, five days into the war, we sent out a message to our partners: “Please don’t worry. We are still working.”

Losing Everything – and Gaining Something Even Greater

Then came the real test. Most of our U.S. partners left. A major Norwegian project was scared to death of the news and canceled the team of 3 developers and a PM working for them. We lost our biggest contracts. But something we never expected happened:
Every single one of our European partners stayed. Not only that — they gave us even more projects.

They believed in us. They supported us. And because of them, we survived. Laravel projects disappeared. We lost key developers. But WordPress kept us afloat. It fed us. It fed our families in the hardest moments.

So we focused on what we did best: custom, complex WordPress development.

The team kept evolving. We became our own sales department, reaching out from a century-old house while watching missiles hit the heart of Kharkiv and fighter jets fall from the sky.

“I will never forget the sound of a plane flying over my head. The mushroom cloud rising above the Officers’ House. The windows in my home were blown out by the blast wave.”

At that time, only four of us remained in Kharkiv — two founders, our HR manager, and a project manager. Everyone else had left.

Back to the Office – And Into the Fire

After six months of working from home, we made the decision: Return to the office. Every commute felt like it could be the last. But we had no choice — we had to keep moving forward.

By the end of 2022, we fully committed to what we did best: custom WordPress development and complex UX/UI design

It was hard. It was frustrating. But it was stimulating. At this point, it felt like a survival game.

Blackouts, Bombs, and Business as Usual

As Russian missiles targeted Ukraine’s power grid, the country was plunged into darkness. The only sound? Generators humming in the streets. We spent hours hunting for an internet connection, sitting in gas stations, just to tell our partners:

“We are alive. Your project will be delivered on time.” 

With no electricity, no news, and no phone signal, we kept working. Our European partners kept us afloat.

The Team That Never Stopped

By 2023, almost our entire pre-war team was gone. New faces joined, but the spirit remained the same: Adapt. Survive. Deliver.

We worked without electricity, without water, without heating.

Some in Kharkiv, some in Poltava, some in Dnipro. But we never stopped building. Reflecting on the past, it’s hard to believe that we were able to endure and remain steadfast.

2024: WordPress Is Changing. So Are We.

This year, WordPress is evolving — the rise of low-code and no-code solutions is shifting the landscape. The war’s impact on the European economy’s growth and projects is slowing down. But our partners — the ones who stood by us — were still here. 

2025: The War Continues, But So Do We

The war isn’t over. And yet, the partners and teammates who believed in us never left. This is more than just WordPress development. This is resilience. This is survival. This is the future we are building together. 

Editor’s Note: The normal fee for the banner for this essay will instead be donated to a charity that supports Ukraine.

The post From Warfare to WordPress: How We Survived and Transformed appeared first on HeroPress.

by Aleks Bochlin at March 05, 2025 06:00 AM

March 04, 2025

WordPress.org blog: WordPress 6.8 Beta 1

WordPress 6.8 Beta 1 is ready for download and testing!

This beta version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, set up a test environment or a local site to explore the new features.

How to Test WordPress 6.8 Beta 1

You can test this beta release in any of the following ways: 

WordPress Beta Tester PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. Select the “Bleeding edge” channel and “Beta/RC Only” stream.
Direct DownloadDownload the Beta 1 version (zip) and install it on a WordPress website.
Command Line (WP-CLI)Use this WP-CLI command: wp core update --version=6.8-beta1
WordPress PlaygroundUse a 6.8 Beta 1 WordPress Playground instance to test the software directly in your browser. No setup required–-just click and go!

The scheduled final release date for WordPress 6.8 is April 15, 2025. Your help testing Beta and RC versions over the next six weeks is vital to ensuring the final release is everything it should be: stable, powerful, and intuitive.

How important is your testing?

Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—whether or not you have experience.  Details on what to test in WordPress 6.8 are here.

If you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac. You can also check your issue against this list of known bugs.

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

WordPress 6.8 will include many new features that were previously only available in the Gutenberg plugin. Learn more about Gutenberg updates since WordPress 6.7 in the What’s New in Gutenberg posts for versions 19.4, 19.5, 19.6, 19.7, 19.8, 19.9, 20.0, 20.1, 20.2, 20.3, and 20.4.

What’s New in WordPress 6.8 Beta 1

This is a polish release, with user enhancements throughout incorporated into the latest Gutenberg updates. WordPress 6.8 brings a luster and gloss that only a polish release can.

WordPress 6.8 Beta 1 contains over 370 enhancements and 520 bug fixes for the editor, including design improvements, polishing the query loop, and more than 230 tickets for WordPress 6.8 Core. Here’s a glimpse of what’s coming:

Editor improvements

Easier ways to see your options in Data Views, and you can opt to ignore sticky posts in the Query Loop. Plus you’ll find lots of little improvements in the editor!

The Style Book comes to Classic themes

The Style Book now features a structured layout so you can preview site colors, typography, and block styles more easily. You can use the Style Book in classic themes with editor-styles or a theme.json file and includes clearer labels, and you can find them under Appearance > Design.

Support for Speculation browser API

WordPress 6.8 introduces native support for speculative loading, leveraging the Speculation Rules API to improve site performance with near-instant page loads. This feature prefetches or prerenders URLs based on user interactions, such as hovering over links, reducing load times for subsequent pages.

By default, WordPress 6.8 applies a conservative prefetching strategy, balancing performance gains with resource efficiency. Developers can customize speculative loading behavior using new filters, since the API does not include UI-based controls. The existing Speculative Loading feature plugin will adapt to the core implementation, allowing deeper customization.  Please test this feature in supported browsers (currently Chrome 108+ and Edge 108+, with more browsers evaluating) and provide feedback on #62503 to help refine its implementation.

Major security boost

WordPress 6.8 will use bcrypt for password hashing, which significantly hardens WordPress. Other hashing is getting hardened, too, throughout the security apparatus. You won’t have to change anything in your daily workflow.

The features included in this first beta may change before the final release of WordPress 6.8, based on what testers like you find.

Get an overview of the 6.8 release cycle and check the Make WordPress Core blog for 6.8-related posts in the next few weeks for further details.

Caveat on testing 6.8 Beta 1 in versions older than 5.1

Due to an update made to the upgrade routine during this release, (see r59803), any upgrade from versions older than 5.1 will fail. Folks are working to resolve this specific issue, so please hold off on reporting on this while testing the Beta 1 release.

Vulnerability bounty doubles during Beta & Release Candidate

The WordPress community sponsors a monetary reward for reporting new, unreleased security vulnerabilities. This reward doubles during the period between Beta 1 on March 4, 2025 and the final Release Candidate (RC) scheduled for April 15, 2025.  Please follow responsible disclosure practices as detailed in the project’s security practices and policies. You can find those on the HackerOne page and in the security white paper.

Just for you: a Beta 1 haiku

March winds shift the tide.
Hands unite in open source;
WordPress moves ahead.

Props to @audrasjb @marybaum @mamaduka @michelleames @bph @jorbin @joemcgill @krupajnanda @desrosj @benjamin_zekavica @lysyjan87 for reviewing and collaborating on this post!

by Jeffrey Paul at March 04, 2025 05:09 PM under releases

Do The Woo Community: All Things CloudFest Hackathon 2025

In this podcast episode, hosts and guests discuss the upcoming CloudFest Hackathon, focusing on project contributions, collaboration opportunities, and the engagement of first-time partners to enhance outcomes.

by BobWP at March 04, 2025 03:46 PM under Hackathon

Matt: On Lenny’s Podcast

One of my must-read newsletters for the past several years has been Lenny’s Newsletter, probably best known for its writing on growth and product management, which really means it covered everything you need to create a great company.

It expanded into a really well-done podcast; Lenny has always had a knack for finding the best guests and asking the best questions, so when he invited me on I was very excited.

He really wanted to address some of the things that people said I wasn’t being asked, so we do touch on the WP Engine / Silver Lake attacks, but we also covered a lot of my philosophy of why open source is important, philanthropy, and why you should build a movement, not just a product.

You can watch it on YouTube, or listen to it on your favorite podcast app like Pocket Casts.

Some others he has done that I really enjoyed are Nan Yu from Linear, Marc Benioff from Salesforce, Katie Dill from Stripe, Mihika Kapoor from Figma, Drew Houston from Dropbox, and of course the famous Founder Mode one with Brian Chesky.

by Matt at March 04, 2025 02:19 PM under Press

Do The Woo Community: Marketing Strategies for Every Level of a Woo Business

Successful marketing strategies vary based on business stages. From solopreneurs to large firms, understanding owned, earned, and paid media, branding confidence, and purposeful engagement is essential for effective growth and communication.

by BobWP at March 04, 2025 11:00 AM

March 03, 2025

Do The Woo Community: From Idea to WordPress Product with Derek Ashauer

Mark Westguard chats with Derek Ashauer about his transition from client work to creating WordPress plugins, particularly focusing on his latest product, Conversion Bridge, designed for simplified conversion tracking.

by BobWP at March 03, 2025 04:11 PM under Plugins

February 28, 2025

Gravatar: How to Personalize Your Customer Onboarding for Better Retention

Getting your customer onboarding right can make the difference between long-term success and early user drop-off. But a generic approach won’t cut it – you need to personalize your message to keep users engaged and active.

Smart personalization strategies help users find value faster in your product. So, naturally, companies that tailor their onboarding see higher retention rates, increased feature adoption, and stronger customer relationships. Their users are more likely to become product champions and recommend the service to others.

And the numbers back this up. In research by Forrester, businesses that have invested in building better customer and prospect experiences see up to 20% more improvement in customer retention and 25% in customer lifetime value compared to businesses that don’t. 

Comparing customer, revenue, and employee benefits between experience-driven companies and non-experience-driven companies

This guide breaks down proven strategies to create personalized onboarding experiences that stick. From sign-up optimization to data-driven improvements, you’ll learn practical techniques to transform your onboarding into a powerful retention tool.

Step 1: Effortless sign-up process

A streamlined sign-up process sets the tone for your entire user experience. The challenge? Balancing the need to collect essential user data while keeping friction low. Too many form fields can drive users away, while too few might limit your ability to personalize their experience.

Start by identifying the minimum information needed to provide value. For most products, this includes an email address, name, password, and their role or use case. Many companies ask for the company website and department, as well. 

From the beginning of the process, you can use Gravatar to help you out. 

Gravatar – Profile as a Service 

For example, if you’re using WordPress to build your website, some level of Gravatar functionality will already be enabled. WordPress.org will automatically pull in user avatars, or profile pictures, connected to their Gravatar profiles.

Profile picture in WordPress.org

However, you can extend this in a massive way, through the free Gravatar Enhanced plugin to add features like the profile block, which is perfect for author pages and websites focused on creating a community. This block lets you automatically display user information pulled in from their profiles, such as their bio and verified links. 

Gravatar profile block

Another option to integrate Gravatar on a deeper level is with the REST API – and you can do this whether you’re on a WordPress website or not. This allows you to auto-populate user profiles instantly when someone signs up with their email address. This reduces manual data entry while still gathering rich profile information for personalization, which is especially effective with SaaS onboarding.

What makes this a gamechanger is that all websites that integrate with Gravatar pull in information from a unified source, which allows you to create familiar experience for users across multiple platforms while reducing sign-up friction.

Want to take it further? Use progressive profiling:

  • Collect essential information during sign-up.
  • Ask for additional details as users engage with specific features.
  • Use behavior patterns to build user profiles over time.
  • Allow users to import data from existing profiles.

Remember to test different form variations with real users. Track completion rates and drop-off points to optimize the process continuously.

Step 2: Automated welcome email

The welcome email acts as your first direct communication with new users. It needs to accomplish several goals while remaining clear and engaging. 

So, to make your welcome email effective, you need to first use an effective subject line. Here are some examples: 

  • “Welcome to [Product] – Here’s your next step”
  • “You’re in! Let’s get started with [Product]”
  • “[Name], welcome aboard! Your account is ready”

If you’re not sure what to include, you can structure the email content like this:

  1. Start with a personal greeting using their name. 
  2. Confirm their account creation. 
  3. Highlight one clear next action. 
  4. Include essential links without overwhelming them. 

For example, this is the welcome email we send to our users when they create a Gravatar profile: 

Hello!Your email now has a profile!There are two things you should know about Gravatar:Your email can introduce yourself

Anytime you share your email, it’s like handing over a digital business card. Your Gravatar profile automatically appears on any Gravatar-enabled site, so you can feel at home instantly. Your avatar and identity follow you seamlessly across the web. Say goodbye to filling out profile forms all over the web.

One link, all about you

Your Gravatar account comes with a free profile website.

It’s a brief introduction of yourself and the perfect way to share where people can find you online. Customize the design and your profile URL. Simple. Make it yours!

Any questions? You know where you can find us 😉 – Ask us anything! Or just reply to this email.

✨Pro tip: With Gravatar integration, you can personalize the greeting with the user’s preferred name and include their profile image, making the email feel more personal and familiar.

Step 3: Follow-up email to initiate the onboarding process

Send this email 24-48 hours after the welcome message. Its purpose? Moving users from sign-up to actual engagement with your product.

A strong follow-up email includes:

  • Recognition of whether they’ve logged in yet.
  • One specific action they can take right now.
  • Clear value proposition for that action.
  • Estimated time commitment.

Here’s a tested template:

Subject: Ready for your first [specific win] with [Product]?

Hi [Name],

Quick check-in: Have you had a chance to [specific action] yet? 
It takes just 5 minutes to [achieve specific outcome]. Here’s how:

1. Log in to your account
2. Click on [feature]
3. [Simple action step]

Tip: Users who complete this step see [specific benefit] within [timeframe].
Need help? Reply to this email or book a quick call: [calendar link]

Using Gravatar’s API, you can adapt this email based on the user’s professional background or location. For instance, customize examples and use cases that match their industry.

Step 4: Choosing the right onboarding strategy for your product

Selecting the right onboarding approach determines how effectively users will adopt your product. Let’s examine four proven strategies and when to use each one.

One-on-one onboarding

Enterprise software with complex implementations demands personal attention. This high-touch approach works best for products with annual contract values above $10,000 or solutions requiring custom workflows. The direct interaction helps catch potential issues early and ensures users extract maximum value.

Tips for successful one-on-one onboarding:

  • Record sessions for future reference.
  • Create custom agendas based on user roles.
  • Set clear milestones for each call.
  • Follow up with written summaries.
  • Track time to first value achievement.
  • Monitor customer satisfaction scores.

Group onboarding

Mid-market solutions and team-based tools often benefit from group sessions. This approach builds community while efficiently onboarding multiple users who share similar needs. It’s particularly effective for products where users can learn from each other’s questions and use cases.

Keys to effective group onboarding:

  • Segment sessions by industry or use case.
  • Keep groups small (5-8 participants).
  • Include hands-on exercises.
  • Encourage peer learning.
  • Schedule sessions across convenient time zones.

Self-service onboarding

Products with straightforward features or tech-savvy user bases thrive with self-service onboarding. This approach scales efficiently for high-volume, lower-price products where personal attention isn’t cost-effective.

Essential self-service elements include:

  • Interactive product tours.
  • Short video tutorials.
  • Progress tracking.
  • Clear success milestones.
  • Help documentation.
  • Chat support option.

Hybrid approach

Many successful products combine multiple approaches. Use self-service for basic features, group sessions for advanced functionality, and one-on-one support for custom needs. This flexibility lets you match support levels to user needs and value.

Implementation strategies:

  • Use data to trigger different support levels.
  • Monitor user progress automatically.
  • Offer easy ways to upgrade support.
  • Track which methods work best for different segments.
  • Adjust based on user feedback and engagement metrics.

Step 5: Setting initial goals and milestones

Setting clear goals with users creates momentum and drives engagement. The trick lies in balancing ambition with achievability – goals should stretch users while remaining within reach. Success starts by understanding what matters most to each user through direct conversations about the problems they’re trying to solve and their vision for the first 30 days.

Break larger objectives into manageable milestones. The first milestone should be achievable within 24-48 hours of signup, building confidence and showing immediate progress. Follow this with weekly targets for the first month, then transition to monthly milestones.

Simple gamification elements can boost motivation:

  • Progress bars showing completion status.
  • Achievement badges for hitting milestones.
  • Team leaderboards for group implementations.

Gravatar integration enhances this experience by displaying user avatars alongside achievements and in team views. This personalization makes the journey feel more engaging and tailored to each user.

✨Tip: Set up automated monitoring to flag when users struggle with specific milestones. This allows customer success teams to step in proactively with support. Stay flexible and adjust goals based on user feedback and behavior patterns.

Step 6: Strategies for personalized onboarding

Personalization transforms generic onboarding into targeted experiences that resonate with users. Advanced strategies go beyond basic segmentation, using real-time data and behavior patterns to adapt the experience for each user.

For example, you can use AI-driven paths to analyze user actions and modify the onboarding flow automatically. So, when a user struggles with a specific feature, the system can offer extra guidance or suggest alternative approaches. This dynamic adaptation ensures users get help exactly when they need it.

Integrating Gravatar adds another layer of personalization from the first interaction. The API provides valuable context about user roles and industries, allowing you to customize the UI,  examples, and terminology accordingly. A developer might see technical implementation details, while a marketing professional receives analytics-focused guidance.

Micro-segmentation takes this further by combining behavioral data with profile insights. For example:

  • Tailor feature introductions based on past product usage.
  • Adjust communication frequency by engagement levels.
  • Customize success metrics for different roles.

Remember that in-app guidance should feel natural and contextual. Rather than overwhelming users with information, show relevant tips when they’re most likely to need them. This might mean highlighting advanced features only after users master basics or suggesting integrations when usage patterns indicate they’d be valuable.

Step 7: Provide access to a detailed knowledge base

An effective knowledge base empowers users to find answers on their own terms. Rather than forcing users to contact support for every question, good documentation lets them solve problems at their own pace.

Here’s what we recommend: 

  • Build your knowledge base around user needs, not product features. 
  • Start with common questions and problems users face during onboarding. 
  • Structure content in a logical flow that matches the user’s learning curve – from basic setup to advanced features.

Video tutorials and interactive guides complement written documentation. Short screencast tutorials work well for showing complex processes, while step-by-step guides help users implement specific features. Keep videos brief and focused on single tasks.

AI-powered search helps users find relevant information quickly. Smart categorization and related article suggestions guide users to helpful resources they might have missed. Think of your knowledge base as a living document and update it based on common support tickets, user feedback, product updates, and usage analytics. 

Finally, track which articles users read most and where they spend time. This data reveals gaps in documentation and helps prioritize future content creation.

Step 8: Strategies for checking in with customers

Regular check-ins help spot potential issues before they become problems. The best check-ins feel natural, not forced, and happen at moments that matter to users.

The best strategy is combining automated and personal outreach based on user behavior. After major milestones, send congratulatory messages with tips for the next steps. If usage drops suddenly, trigger a friendly check-in to offer help. Schedule more detailed reviews after the first week and first month to ensure users stay on track.

Personal check-ins should focus on learning, not just status updates. Ask specific questions about their experience and goals. For example: “Has [feature] helped with [specific goal] yet?” or “What’s been the biggest challenge so far?” These conversations often reveal valuable insights about user needs.

You also should have either a live chat option, email support, and/or video calls because they each serve different purposes. Quick questions work well in chat, while video calls help build relationships and tackle complex issues. Use email to share resources and document action items.

Step 9: Iterate based on feedback

Feedback drives improvement, but only if you act on it systematically. Collect both quantitative data (usage statistics, completion rates) and qualitative insights (user interviews, survey responses) to build a complete picture.

  • Create feedback loops at every stage of onboarding. Short in-app surveys capture immediate reactions, while detailed questionnaires after key milestones provide deeper insights. User interviews reveal nuances that numbers alone might miss.
  • Take action quickly on clear pain points. If multiple users struggle with the same step, examine it closely. Sometimes, small tweaks, like clearer instructions or simplified workflows, make a big difference. Share improvements with users who provided feedback – it shows you value their input.
  • Build a systematic approach to evaluating and implementing changes:
    • Analyze feedback patterns
    • Prioritize high-impact changes
    • Test solutions with small user groups
    • Monitor results before rolling out widely

Enhance your onboarding with Gravatar’s developer API

A strong onboarding process keeps users engaged and helps them find value quickly in your service. By integrating Gravatar’s developer API, you can create a more personalized, friction-free experience from the first interaction.

Think about your sign-up process. Instead of asking users to fill out multiple fields or upload profile pictures, Gravatar automatically populates this information. Users who already have Gravatar profiles – and there are millions – get a faster, more familiar experience across platforms.

The API opens up creative possibilities beyond basic profile data. Use it to:

  • Create personalized welcome screens.
  • Show relevant examples based on user industries.
  • Build community features with consistent user identities.
  • Maintain professional profiles across multiple services.

Major platforms like WordPress and Slack already use Gravatar to streamline their onboarding, so what are you waiting for? 

Check out Gravatar’s developer documentation to see how easy integration can be. Focus on creating those meaningful first interactions that turn new signups into long-term users.

by Ronnie Burt at February 28, 2025 04:28 PM under User Experience

Gravatar: Essential Tips for an Effective Email Signature

Creating an effective email signature takes more thought than you might expect. Yes, it’s just a small block of text at the bottom of your emails – but it’s also a powerful tool for making memorable connections and building your professional reputation.

This is especially important if you’re reaching out to potential clients, applying for jobs, or trying to grow your network. Your signature can be the difference between someone remembering you or your message getting lost in their inbox.

But here’s the challenge: Finding the right balance. Add too little information and recipients won’t know enough about you. Add too much, and your signature becomes cluttered, potentially making your emails look unprofessional or even spammy.

Let’s explore how to craft an email signature that makes an impact, including a smart strategy for sharing more about yourself without overwhelming your recipients.

Checklist of elements to consider in your email signature

Before diving into specific elements, remember this: You don’t need to include everything listed below. In fact, that would be counterproductive. Pick the elements that matter most for your professional goals and match your personal brand. And as you’ll see later,linking to an online profile, such as your Gravatar, is a smart way to share additional information without cramming it all into your signature.

Here are the essential elements to consider:

  • Name and title: Format as “Name, Title” for quick scanning. This is non-negotiable – it’s the foundation of your signature.
  • Basic contact details: Include your primary phone number and email address. If you need multiple numbers, use standard notation: (o) for office, (m) for mobile.
  • Company information: Add your company name and department if relevant. For freelancers, your business name or professional title works well.
  • Visual elements: A small professional headshot or company logo can increase recognition. But keep it modest – aim for subtlety rather than flash.
  • Social proof: Choose 2-3 relevant professional profiles. LinkedIn is often essential, while other choices depend on your field. A portfolio site works well for creatives, while GitHub is a must for developers. And of course, if you need a versatile profile platform that can display a wide range of information, links, and media, all in a compact design, then a Gravatar profile is a must. 

Now, besides these basic elements, there are also some practical additions that would vary based on your needs:

  • Calendar booking link if you schedule lots of meetings.
  • Industry certifications for specialized fields.
  • Office location or timezone for global teams.
  • Languages spoken for international work.
  • Pronouns for inclusive communication.
  • Legal disclaimers if required by your industry.

Remember: White space is your friend. A clean, readable signature beats an overcrowded one every time.

Design Tips to make your email signature stand out

Email signatures need precise design choices to look professional across different devices and email clients. Here’s how to create one that works everywhere:

Size guidelines that prevent problems:

  • Keep the total width under 600px – this ensures your signature displays correctly on mobile devices.
  • Limit height to 150 or 200px maximum to avoid overwhelming your message.
  • Size company logos at 100x50px.
  • Set headshots to 80x80px square.
  • Leave 10px minimum spacing between elements.

Typography and formatting:

  • Set your name in 14-16px font size – it should be instantly noticeable.
  • Use 11-12px for contact details and other information.
  • Stick to standard, professional fonts like Arial or Helvetica.
  • Pick two brand colors at most, plus black or gray for text.
  • Organize information in order of importance.
  • Use simple separators like pipes ( | ) between elements.

Technical requirements to prevent display issues:

  • Apply inline CSS to maintain consistent formatting.
  • Structure elements to stack properly on mobile screens.
  • Test your signature in major email clients (Outlook, Gmail, Apple Mail).
  • Compress images under 40KB to ensure quick loading.

Hierarchy matters – put your most important information first. Think about what your recipient needs to know right away versus what can go below. A clear structure with proper spacing helps readers find what they need quickly.

Examples of well-designed email signatures

To help you get inspired, here are some interesting templates from Canva that really capture what makes a great email signature. 

  • Minimalistic signature without a headshot: 
Example of a minimalistic email signature for a manager
  • Elegant signature with a photo: 
Example of a simplistic email signature for a real estate agent 
  • Another design for a real estate agent with a cover photo. 
Example of an email signature for a real estate agent with a cover photo
  • A very unique approach for a graphic designer, allowing them to show their creativity even through their email signature. 
Example of an email signature for a graphic designer

Automating design with an email signature generator

While working with a designer gives you the most polished results, email signature generators offer a practical starting point. These tools handle the technical details and help you create something professional without diving into HTML or CSS.

Here are some reliable options:

HubSpot Email Signature Generator (Free)

Hubspot email signature generator
  • Provides clean, professional templates.
  • Easy to customize colors and layout.
  • Exports HTML code you can copy directly.
  • No account required.

WiseStamp

WiseStamp email signature generator
  • Offers multiple professional templates.
  • Integrates with major email clients.
  • Includes advanced features like banners.
  • Paid plans start at $5.80/month.
  • Also offers an email signature management service. 

NewOldStamp

NewOldStamp homepage
  • Built for teams and companies.
  • Manages signatures across departments.
  • Ensures brand consistency.
  • Team pricing available.

Canva

Example of a Canva editor with the brand kit feature
  • A wide variety of email signature templates. 
  • Interesting graphics and design tools. 
  • An AI writing and design tool for the PRO version. 
  • Versatile applications – use it for marketing campaigns, social media, blog posts, etc. 
  • Lets you create a brand kit to use on all your visuals. 

Why you should link to your Gravatar profile for more impact

Ronnie Burt’s Gravatar profile

An email signature has limited space, but your Gravatar profile can showcase everything about your professional identity, just like a dynamic business card. Think of it as an extension of your signature – one that updates automatically across all platforms where you use your email.

Your Gravatar profile becomes a comprehensive hub for:

  • Professional background and accomplishments.
  • Portfolio pieces and project highlights.
  • Complete set of social media profiles.
  • Full contact information.
  • Recent blog posts or updates.
  • Speaking engagements or events.

The magic happens in the synchronization. Update your Gravatar profile once, and those changes appear everywhere your email is used – including past emails. No need to update multiple signatures or worry about outdated information floating around.

This approach solves a common problem: Keeping professional information current across platforms. A hiring manager might find your year-old email with an outdated job title, but clicking your Gravatar link shows them your current role and achievements.

Crafting CTAs to your Gravatar profile in your email signature

One option is to add the Gravatar icon to your email signature as you would for any other online profile. This works well, though as Gravatar can be used for a wide range of purposes it might not give your recipients enough context about what they’ll find when they open it. Another option is to link to your Gravatar profile with clear, action-oriented text that hints at the value:

  • “See my complete portfolio and background.”
  • “Find my latest projects and contact info.”
  • “Connect with me professionally.”
  • “View my full professional profile.”

Match your CTA to your goals. If you’re job hunting, emphasize your portfolio. For networking, focus on connection opportunities. The right CTA tells recipients exactly what they’ll gain by clicking through.

Create an effective email signature with the help of Gravatar

Gravatar actually makes it super easy. Just login to your profile editor, copy your email signature code, and paste it in.

Here’s how:

  • Head to gravatar.com/profile
  • click on Email signature in the bottom left
  • grab the code and paste it into Gmail or your email client

Check out our quick setup guides for Gmail, Apple Mail, and other popular email tools.

Email signatures perform a delicate balancing act. Add too much information, and you risk looking unprofessional. Add too little and recipients miss important context about who you are.

Linking to a Gravatar profile offers an elegant solution. Your email signature stays clean and focused, while still giving recipients access to everything they might want to know about you. Plus, you never have to worry about outdated information lingering in old emails – your Gravatar profile updates everywhere, automatically.

Here’s what makes this approach particularly effective:

  • Recipients get a complete picture of your professional identity.
  • Your signature stays concise and professional.
  • Information stays current without manual updates.
  • Old emails maintain their relevance.
  • You control how much information to share.

A well-crafted email signature paired with a Gravatar profile helps you make stronger professional connections. Recipients can learn exactly what they need about you, whether that’s your latest work, professional background, or preferred contact methods.

Ready to enhance your email signature? Create your free Gravatar profile and start building a more effective professional presence.

by Ronnie Burt at February 28, 2025 04:27 PM under Personal Branding

Follow our RSS feed: 

WordPress Planet

This is an aggregation of blogs talking about WordPress from around the world. If you think your blog should be part of this site, send an email to Matt.

Official Blog

For official WordPress development news, check out the WordPress Core Blog.

Subscriptions

Last updated:

March 17, 2025 04:15 AM
All times are UTC.