16 Sep 2024

feedWordPress Planet

WordPress.org blog: WP Briefing: Episode 86: My First WordPress Experience

Join us this week as Josepha takes a personal journey down memory lane to her first encounters with WordPress. In this episode, she shares the story of her very first WordPress website, the excitement of getting involved with WordCamps, and how those early discoveries shaped her rewarding path in the WordPress community. Whether you're a seasoned user or new to the platform, Josepha's reflections will inspire you with insights from her earliest days in WordPress.

Credits

Host: Josepha Haden Chomphosy
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod

Show Notes

Transcript

[00:00:00] Josepha: Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I'm your host, Josepha Haden Chomphosy. Here we go.

[00:00:28] (Music intro)

[00:00:39] Josepha: Folks, this week is WordCamp US, and over the past week or so, I spent a fair amount of time talking to people about that first-time experience. And as with any person who's talking about their version of a shared experience, I started thinking back to mine.

I think my first experience of WordPress was not typical, though. I had never even heard of WordPress when I first went to a WordCamp. I think, I think most of the time people have heard of it before, but I was just there for the plot. So, like many people in my generation, all of us old people of the internet, I was first online with things like Angelfire and GeoCities.

[00:01:16] Josepha: When I went to college, I was keeping friends and family up to date on what I was up to with a little, like, newsletter? And then Xanga made it to our college campus, and eventually, so did Facebook. And I was one of those kids kind of like half-breaking sites with HTML and CSS I found online. I was changing layouts like every week to suit my mood.

Then, when I graduated and found myself in a city with more talent and more competition than I'd actually accounted for, and started to realize that this online stuff I'd been doing for fun might actually be something that I needed to use as a tool professionally. So, I first went out and reserved my screen name everywhere I could think of.

[00:02:01] Josepha: And we're talking, like, LiveJournal, WordPress.com, Blogger, all the things, and eventually wound up building my first site on Weebly. And it was super ugly. I'm not able to design things. I have an okay sense for a design that is good, but like, left to my own devices, it's gonna be what that was, which is like a tie dye background for some reason, and had everything organized into little, like, blocks, I guess? You know, like, old magazine layouts? And it technically had everything that I wanted, but it wasn't necessarily the best version of any of those things either. I could write a little bit about myself and my services, I could add a few photos, there was a way to contact me, and I could do it all by myself.

And so it was a good place to start. Not long after that, though, I graduated into the need for a more professional-looking website, and it was beautiful. I received a website; someone built it for me. It was beautiful; it had this elegant design. Had a lot of custom functionality, but it was built using ColdFusion. I couldn't do anything to it. I couldn't change anything. All minor changes just had to kind of wait until there was enough to make sense to use that maintenance time, that maintenance retainer that I had. It really was just kind of formal. It was an isolated snapshot of all of the sorts of information that was required to be on the web at that time.

[00:03:28] Josepha: And then, later that year, I went to my first WordCamp, and I moved my site over to WordPress. And for the first time, I had that kind of mixture of professional expression that was on top of something that enabled my own expression. And honestly, I didn't learn much more about the software for a few years. It was doing what I needed it to do, how I needed it to be done, and that's really what mattered to me.

And when I skip a few years ahead after that, a few years later, when I was learning by organizing Meetups and WordCamps that had speakers that I wanted to hear from, that had topics that I felt like I needed to learn more about, what I remember most about that learning period for me is that I knew that I wasn't the first person to run into any of my problems, which meant that a solution was probably already out there, and I could find someone to come and teach us about their solution.

[00:04:23] Josepha: And also, I knew that if we were running into a new problem and started breaking things left and right, there was always a way back. I was never really too far away from success. Like I felt like I might be lost, but I still was pretty much findable. And I guess I always want that for new users of the open web now, like new members of our WordPress community.

I want them to feel like the breaking of things is fine and safe and that no mistake is irretrievable. I want us to have some place where perfection isn't the point. Now listen, I know the software is complex right now. The admin is a little mismatched, your first choices are huge choices, and there are a million places to start.

[00:05:03] Josepha: So, all I can say is, start with what you need, and once you've got that, like the back of your hand, move on to what you need next. And keep doing that, bravely and messily, until what you've got is all you ever wanted. I'm gonna leave for you, in the show notes, a link to something called WordPress Playground.

It's gonna launch a little WordPress site in your browser. There will be no host. It's just all in the browser itself. And it will have the latest bundled theme on it, Twenty Twenty-Four, and the latest version of WordPress. And that's it. Go in there and click around on the left-hand menu. Start a post, change a page, modify the theme.

Just play around a while. See if it's something that seems fun to you or valuable, or if it's something that you can use as a time capsule for your kid because that sounds like a nice little mix of fun and work. And remember, sometimes perfection's not the point.

[00:05:57] (Music interlude)

[00:06:04] Josepha: That brings us now to our small list of big things.

Folks, as I mentioned at the top, WordCamp US is happening this week. It is September 17th through 20th this year, quite a few more days. But that also means that we'll have quite a bit more stuff to do. If you have your tickets and haven't looked at all of the presentations occurring over the four-day event, remember to take a look at the schedule and pick out topics that are interesting. And remember, just because you picked it out before you went doesn't mean that if you get in there and it doesn't work for you. You can't choose a different topic while you're there. And as a bonus, if this is your first WordCamp that you've ever attended, I have you covered. You can check out my previous episode on all the things to remember for your first time attending a WordCamp. And we have a pretty active community as well. If you just have questions or want to get in there and say, 'Hey, I'm going to a vegan restaurant for lunch; who wants to join me?' You can do that, and you can definitely find somebody.

Also, there are some upcoming WordPress meetings. So, if you're not attending WordCamp US but still want to connect with the community, there are a ton of team meetings that are happening. You can find those on make.WordPress.org/meetings, I think. So really, really easy URL to remember. You can join your fellow community members and contribute to the WordPress project there.

[00:07:18] Josepha: And I also wanted to just call your attention to a few really big projects that still need a little bit of help around the project. So, on the one hand, we have Data Liberation. That is still a really big project, but specifically, we are nearly ready to start working on some user-facing elements of that. It is being powered by Playground, and because the data liberation, the migration of one site to another, is so complex, once we get those elements built into Playground, I think it also stands to fix a bunch of the problems that we have across our user flow, our user experience for the project. Things like having better theme previews and being able to get a sense for what a plugin functionally will do for you versus what it says it's going to do for you. And getting a sense for what the admin looks like, all of those things. And so, anyone who wants to learn more about contributing to Playground or to Data Liberation, I absolutely encourage you to go check out those meetings, see what's happening, and get your hands a bit dirty with that.

[00:08:26] Josepha: We also have a bunch of stuff happening in our community space. If you had received this podcast from somebody because they were like, hey, I know someone who might like WordPress or who has just learned WordPress and has never been to an event or any other reason that you are listening to this but don't yet know the community, there is an easier option than just jumping straight into a WordCamp like I did. You can go to a meetup. You can see there's a widget in your dashboard that'll tell you what your nearest event is, but if you put your location into that widget, and nothing comes up. Technically, that means that you have an opportunity to bring a bunch of people together to teach you stuff you wish you knew about your site right now. So you can wander over into your dashboard and see those, or you can also head over to the community area on make.WordPress.org and anybody over there is happy to help you get started. And let me tell you, it is a very low-effort sort of thing to do. Here again, perfection's not the point. And so that, my friends, is your small list of big things.

[00:09:28] Josepha: Don't forget to follow us on your favorite podcast app or subscribe directly on WordPress.org/news. You'll get a friendly reminder whenever there is a new episode. If you liked what you heard today, share it with a fellow WordPresser. Or, if you had questions about what you heard, you can share those with me at WPBriefing@WordPress.org. I am your host, Josepha Haden Chomphosy. Thank you for tuning in today for the WordPress Briefing, and I'll see you again in a couple of weeks. Or tomorrow if we're all going to WordCamp US.

[00:09:58] (Music outro)

16 Sep 2024 12:00pm GMT

HeroPress: WordCamp Nairobi, Call For Speakers

WordCamp Nairobu Banner

I noticed recently that WordCamp Nairobi is on the calendar for 1-2 November. Then I noticed their Camp slogan is "Beyond the Savannah: Connecting the Kenyan WordPress Community to the World", and I thought "Yes! That's so perfect for HeroPress!" So much so that it's going to help drive the mission of HeroPress in the future.

At the moment we're simply a Media Partner, so I'm here to tell you that the call for speakers is open! If you can attend you should apply to speak, we need as many voices as possible.

I recently met with Moses Cursor Ssebunya, Patrick Lumumba, and Emmanuel Lwanga, all organizers of the WordCamp. If you see them, say hi and shake their hand for me. It sounds like it's going to be a great event.

Moses CursorMoses Cursor Ssebunya
Patrick LumumbaPatrick Lumumba
Patrick LumumbaEmmanuel Lwanga

The post WordCamp Nairobi, Call For Speakers appeared first on HeroPress.

16 Sep 2024 8:00am GMT

15 Sep 2024

feedWordPress Planet

Gutenberg Times: Gutenberg Changelog #107 – WordPress 6.6.2, Gutenberg 19.2, Data Views and Design Systems

In this episode, Maggie Cabrera and Birgit Pauli-Haack discuss Developer Hours, Playground, WordPress 6.6.2, Gutenberg 19.2, Data Views and Design Systems

Show Notes / Transcript

Show Notes

Special Guest: Maggie Cabrera

Announcements

Developer Hours

Developer Blog

WordPress 6.7 & 6.6.2

Community Contributions

Gutenberg 19.2

What's discussed or in the works

Stay in Touch

Transcript

The transcript is in the works.

15 Sep 2024 9:26am GMT

14 Sep 2024

feedWordPress Planet

WPTavern: Five for the Future Site Relaunched with a Block-Based Design

After revamping the WordPress.org homepage, Theme Directory, Plugin Directory, Pattern Directory, and HelpHub, the Meta team has now updated the Five for the Future site. Members of the Meta, Design, and Community teams collaborated to redesign and launch the site in time for WordCamp US 2024.

A Fresh New Look

Developer Relations Advocate Nick Diego shared, " This visual update is part of an ongoing effort to create a consistent design language across WordPress.org… This change marks the beginning of modernizing Five for the Future."

New Home page

The update features a block-based child theme built on top of the shared WordPress.org parent theme, streamlining aesthetics and simplifying future updates. Key changes include:

What's Next?

Future plans include adding new features and content, such as case studies and more testimonials from participating organizations. A Five for the Future blog and newsletter are also in the pipeline.

Nick Diego added, "Forthcoming updates will aim to improve organization profiles by listing activity, automating emails, enhancing onboarding, and adding options for sponsored contributors. The goal is to showcase the strength and impact of Five for the Future with a refreshed, feature-rich website."

You can suggest improvements or report issues with the new theme by opening a ticket on GitHub. For updates on upcoming WordPress.org changes, join the #website-redesign Slack channel.

14 Sep 2024 6:23pm GMT

Gutenberg Times: #WCUS, Gutenberg 19.2, Plugin + Data, Playground Guides — Weekend Edition #304

Hi there,

WordCamp US is upon us, even for those of us not going: We can watch talks on the livestream, depending on the timezones. We can shut down our social networks to avoid FOMO (Fear of missing out). We can enjoy the calm on other platforms, and start testing a few things coming to WordPress 6.7, or we can catch up on Learn.WordPress interactive learning paths.

On a different note, I have been diving more into AI Essentials, prompt design and the testing of various tools. It's such a brave new world. I had excellent results in making some of my work easier by using an AI tool: a draft outline of a presentation in a second language (Claude) , getting a tailored list of sightseeing activities in a new city (Perplexity) , or correcting code examples to WordPress Coding Standards (ChatGPT), are only three examples of well executed AI assistance. I also took a glimpse at Google's AI Studio, that allows you to build apps or integrations that tap into Google Gemini AI. All very fascinating, I found.

My latest go-to AI tool replaces Google search for me. Google gives me short snippets and the links, I still have to weed through and spend some time finding the right information. Perplexity provides the answer with details and sources. No further trip around the Internet necessary.

What is your day-to-day experience with AI? What did you test lately? Please let me know in the comments or hit reply on the email.

And now back to regular programming….

Have a lovely weekend, and if you are traveling to Portland, Oregon, have a safe trip.

Yours, 💕
Birgit

Developing Gutenberg and WordPress

This year, the State of the Word will take place on December 16, 2024, at 09:00 UTC and will be live-streamed from Tokyo, Japan. Matt Mullenweg will provide a retrospective of 2024, demos the latest in WordPress tech, and comments on the future of the WordPress open-source project.

This week, the design team published the landing page for the event, where you can request an in-person ticket for the Tokyo Node Hall. Soon you can find a list of local watch parties. I saved the date in my calendar to watch the live stream from my living room, a week before Christmas.


Lauren Stein invites you to Tour the New Learn WordPress site. In her post she offers a 2- min YouTube video and student testimonials about the new site and the ever-growing learning path courses and tutorials.


Joen Asmussen posted his Design Share #63 (Aug 26-Sep 6) to update us all on the wonderful work the WordPress design team produces. He highlighted:

Screenshot Stylebook for classic themes


In this month's edition of the What's new for developers? (September 2024) on the WordPress Developer Blog, I highlighted for several key updates in WordPress Core, Gutenberg, and Playground. You'll also find details on upcoming developer-focused events and resources.

Subscribe to the Developer Blog, and you'll never miss a post again.

Upcoming Events

September 19, 13:00 UTC: WordPress Playground Block code editor theme support with Jonathan Bossenger.

September 24, 15:00 UTC Developer Hours: An Introduction to Data Views with JuanMa Garrido, André Maneiro and Nick Diego

As a reminder, JuanMa Garrido published recently Using Data Views to display and interact with data in plugins on the WordPress Developer Blog.

WordPress 6.6.2

The maintenance and security release of WordPress 6.6.2 came out on Tuesday of this week.

Jyolsna JE has the skinny for you in WordPress 6.6.2 Released with 26 Bug Fixes on the WPTavern.


Gutenberg 19.2

The latest version of the Gutenberg plugin was released on September 11, 2024. 193 PRs, 58 bug fixes, 59 Enhancements by 54 contributors, 6 of them first time contributors. Release lead, Vicente Canales, highlighted in his release post What is new in Gutenberg 19.2 (11 September)

Extensible Preview Dropdown


Jyolsna JE also covered the release for the WPTavern in Gutenberg 19.2 Released with Enhancements and Bug Fixes."One of the most significant updates in Gutenberg 19.2 is removing the experimental flag from the Block Bindings UI. This feature, now fully integrated into the editor, allows users to link block attributes with external data sources seamlessly. " she wrote.


This week we also recorded an episode of the Gutenberg Changelog podcast (107), My special guest, Maggie Cabrera and I enjoyed chatting about WordPress 6.6.2, Roadmap 6.7, the next default theme, Design systems and Gutenberg 19.2. The episode will drop into your favorite podcast app on Sunday. If you enjoy listening to the podcast, please write us a review on any of the podcast directories (Spotify, PocketCasts, Apple etc.)

Maggie Cabrera and Birgit Pauli-Haack, recording the Gutenberg Changelog podcast episode 107

WordCamp US Showcase talks

It's more and more difficult to glen from session description how relevant certain talks will be for Gutenberg enthusiasts. It's become so mainstream that most talks about WordPress will include block related content. The full WordCamp US schedule (in PDT) is available on their site. There are way over 50 talks scheduled for this year's WordCamp US and the time difference is nine hours for me.

If you wish to put your own list together, you'll find the respective livestream links for the three days and four rooms on the official WordPress YouTube Channel > Live.

The many hours of livestream out of each room will be online for a couple of weeks, until the AV team manages to separate each talk into individual videos. The video of Matt's Q & A will probably online within the hour and available the next day. Many talks will be past my bedtime. I will wait for the individual videos to show up and catch up in the following weeks.

Birgit Personal Watch List (as per 9/14)

With below list, I leaned into my self-centered personality and publish my personal watch list. haha. The times are in UTC. This is not a list of all the talks I want to watch. These are the talks I might be able to watch on the live stream. The links under "Room" point directly to the YouTube Live stream for this room on the particular day.

Date Time UTC Talk title Room
9/18 16:15 UTC Disney Experiences' Magical Transformation with Gutenberg Rose City
9/18 17:30 UTC Unlocking Disney's Digital Evolution: Navigating the Gutenberg Era Stumptown
9/18 18:30 UTC How WordPress Powers The New York Post Stumptown
9/20 16:00 UTC How TIME Uses Patterns to Drive Recirculation and Engagement Mt. Hood

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

Bud Kraus has good news for you! In his post for GoDaddy Pro, A primer on WordPress block markup for the non-programmer, he wrote: "Understanding the fundamentals of any WordPress block is not as difficult as mastering PHP as you would have back in the pre-Gutenberg era." Following along you'll learn about the various concepts of the modern WordPress theme, template and patterns, and of course, blocks. Then he continues to give you a glimpse under the hood and shows you some block markup code and teaches you what attributes are.

It feels similar to when my dad showed me how to exchange spark plugs on my car or start my car with a jumper cables or replace a tire. I never aimed to be a car mechanic, but having a bit of knowledge can save you when you get stranded in a foreign place with no cell phone reception. Although you are not a programmer, knowing a bit about the underlying code base, can go a long way.


Kathryn Presner and Helena Artmann recorded their online workshop on Exploring the Query Loop block. "The Query Loop block might sound bland, but it's actually the driving force behind the layout of modern WordPress blogs. Dive into this critical block together with Presner and explore ways to show off your content and learn how to configure it to get the result you want. They also cover the different types of blocks you might want to nest inside it. Finally, you uncover some lesser-known ways to use the Query Loop block, to display pages and other types of content besides posts."


Mike McAlister from Ollie WP just dropped a cool tutorial on how to build smarter and faster with synced patterns. He shows how you can use synced patterns in WordPress to make site building a breeze. With these patterns, you can tweak multiple parts of your site at once, making your workflow smoother and keeping your design consistent.


The number of Block themes in the Themes directory was 942 this morning. You find now a great collection of themes for businesses, writers, photographers, agencies, and products. The newly released pattern browser you can use when clicking through a single theme page gives you a great insight in how various parts of your website will look, when using a theme. Many themes showcase, services, FAQ, content form, or about us patterns, that, make building a site a streamlines process.

The latest five Themes approved were:

Hello Blocks by Md Ataur Rahman of Wpmet, builder of the GutenKit and other WordPress plugins. This is their first theme in the WordPress Repository.

Margarethe by the theme builders at Automattic and built for site owners in the interior design space. It's the latest of 209 block themes built by Automattic's designers.

Happening, also out of the workshop at Automattic, designed for events and ceremonies.

TributeToGovPress by Tommaso G. Scibilia from Italy it's his second block theme published in the repository within the last few weeks. This theme seems to be the block theme version of one of his favorite themes: Gov Press by Govfresh, that hasn't been updated since August 2019.

Eternal by Uxl themes, a theme, opinionated about its design and suitable for all screen sizes and the patterns offer design for business websites, like services, price lists, process steps or for the about page. It's the 23rd theme from Uxl in the repository and their eighth block theme.

Block themes in the WordPress Themes directory


On WordPressTV, Wes Theron posted a new video Use the Create Block Theme plugin for exports, and theme variations. You'll learn how to use the Create Block Theme plugin to customize, save, and export a WordPress theme. You'll explore how to apply changes to colors, fonts, and layouts and export your modified theme as a zip file for use on other websites.


Adam Jones, HumanMade, identified Five key features for enterprise users in the upcoming version of WordPress 6.7. Those are:

Theme Development for Full Site Editing and Blocks

Simone Maranzana, co-creator of Advanced Columns, built the Figma plugin Block Flow that "allows you to easily convert your designs into WordPress blocks. This plugin is designed to simplify the process of transforming your visual projects into functional WordPress code. The exported blocks do not contain inline styles and rely solely on the logical attributes of the supported blocks. You can read more details in her X-Thread.


"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

In this week's Developer Hours, Justin Tadlock and Nick Diego took a first look at the Template Registration API in WordPress 6.7 and explored how to register custom block templates in your plugins. This long-needed feature lets you create default front-end output that plays nicely with themes while also being customizable from the Site Editor by users.


Alex Standiford shared publicly how he made his WordPress Archive style different post formats, using the Block Visibility plugin and a short code snippet. More in his post. There is also a discussion on the topic
Bring post formats to block themes on GitHub, you can follow along and chime in.


Siddharth Thevaril, working for 10up, shared his experience in Building an extendible WordPress admin Settings page with Gutenberg Components. Thevaril covered setting up a custom settings page, using React for the interface, and integrating Gutenberg UI components for a clean, responsive design. The tutorial includes code snippets and practical tips for developers.


Ajit Bohra, an early Gutenberg contributor, announced the latest project he has been working on with the team of Lubus, a web development company out of Mumbai. WPUI is "a design pattern library built upon WordPress components which gives you the building blocks you need to build your react-powered WordPress plugin or app" (quoted from their site). The project is built in public and available on GitHub. "It was born to avoid the mundane task of assembling UI for WordPress." Bohra tweeted.


Daniel Bachhuber, CEO of WordPress.Com (the commercial WordPress hosting company) announced on X (former Twitter) a new prototype of plugin that offers building Custom Content Models from within the Block Editor. The plugin is available on GitHub from Automattic's repository. It's open-source and can be extended or forked. It's more a proof of concept rather than production-ready code, and for the developers it seems to be just an exercise, of "would it be possible" than actually geared towards getting into WordPress Core?


Brain Coords tells the story around his contribution to the Custom Content Model in his video Custom fields and post types inside the block editor - with WordPress.com. WordPress.com invited Coords to explore and build the prototype. In his video, Coords takes you through the genesis of the project and the approach the development took. He also gives you a demo and answers audience questions.


Matt Medeiros sat down with Mark Szymanski in their episode 65 of the WPMinute podcast to discuss Was The Create Content Model Prototype Good Enough?


WordPress Playground

JuanMa Garrido announced, that three new guides published in the WP Playground Docs

The hope is that these resources can help inspire and guide theme and plugin developers to fully take advantage of WP Playground's potential.

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.

14 Sep 2024 9:39am GMT

13 Sep 2024

feedWordPress Planet

WordPress.org blog: Tour the New Learn WordPress

The reimagined Learn WordPress experience launched just over a month ago. It introduces Learning Pathways, a new approach to educational content from the Training team.

In case you haven't explored the updated Learn WordPress site yet, take a peek at what you've been missing in this short and sweet virtual tour:

The reception of the new experience and Learning Pathways courses has been positive, with the average learner rating at 4.5/5 since the site's relaunch. Here's what learners have been saying:

"The beginner course did a fantastic job of introducing all the key terms I needed to know. It really set me up with a strong foundation to build on in the future…"

Carlos S.

about the Beginner WordPress User course

"This series of lessons is exactly what I am looking for: it improves my knowledge at an intermediate level, especially for the newer features in the Site Editor."

jpgoem

about the Intermediate Theme Developer course

"The Beginner WordPress Developer course provided exactly what I needed to return to web design and WordPress after years of web application development."

Hugo V.

about the Beginner WordPress Developer course

"This course was a great overview that also gave links for more reading. It's making learning much more fun, thorough, and structured…"

Heather A.

about the Intermediate WordPress User course

The Training team is working hard to add more Learning Pathways to the existing roster, with the Designer and Intermediate Plugin Developer Learning Pathways already in progress. In the meantime, explore the four Learning Pathways at Learn WordPress.

There's always more to learn.

13 Sep 2024 7:26pm GMT

12 Sep 2024

feedWordPress Planet

HeroPress: You Did This

Hands on a pottery wheel.

Just the other day Lana Miro wrote her HeroPress essay from from Mykolaiv, Ukraine. In it she gives some credit to the WordPress community for helping her literally not lose her mind while bombs fell in her neighborhood. Additionally she credits her company, which builds tools for WordPress.

In the past I've said "WordPress won't help you. It's software, it just sits there." But if that software hadn't been just sitting there, a group of people in Ukraine wouldn't have been able to make this company, to become friends and co-workers, and support each other.

WordCamp Crazy is a group of men from Pakistan, India, and Bangladesh that travel together to WordCamps around the world. If that doesn't seem odd to you then you don't know the history of those three countries. On the whole they don't get along. Yet because WordPress exists these men met on common ground and became friends. Sure it's just a small group of people, but it's one step in healing the wounds between their countries. How many other groups or even just two people around the world are like them, that we never hear about?

There are almost 300 stories on HeroPress now, we've been building it for 10 years. But there are so many more stories that I've heard that never made it to the site. So many lives changed.

I think "How did this happen?" and I look at WordPress as a tool. Who built it? So many people. Thousands? Hundreds of thousands? Millions? Not just core, not just plugins, themes, hacks, tweaks and code. All the support questions answered, all the talks given, all the translations, tutorials, blogs, videos, events, and simply time sitting quietly explaining something to one person who needed it.

Here's my point, right here.

If you've ever contributed to WordPress in any way, YOU did this. I did this. WE did this.

Think about that, and about your impact on the world. Because of your actions, the world is a better place.

Thank you.

Photo by Quino Al on Unsplash

The post You Did This appeared first on HeroPress.

12 Sep 2024 9:04pm GMT

WPTavern: Gutenberg 19.2 Released with Enhancements and Bug Fixes

Gutenberg 19.2 was released on September 11, 2024. This latest release includes notable changes such as Block Bindings UI, enhancements to the Zoom Out mode, an experimental client-side media processing feature, and some bug fixes.

Here's a rundown of the key features and changes:

Block Bindings UI Moving Out of the Experimental Phase

One of the most significant updates in Gutenberg 19.2 is removing the experimental flag from the Block Bindings UI. This feature, now fully integrated into the editor, allows users to link block attributes with external data sources seamlessly. By default, only admin users can create and modify bindings, ensuring greater control and security.

Vicente Canales from the Core team has shared this video in the announcement post.

Preview Options Extensibility

The new release also adds extensibility to Preview Options via the Plugin API.Plugin and theme developers can now introduce custom preview options in the block editor's preview dropdown. This allows users to preview content in different formats or environments, offering more flexibility in how they view their creations.

Enhanced Zoom Out Mode

The toolbar now has an "Edit" button, making it easier to switch between modes. Users can also exit Zoom Out mode by double-clicking on blocks and the "Shuffle" block toolbar button has been removed.

Content-Only Mode Enhancements

In Content-Only mode, top-level locked blocks now support block styles, providing more consistent designs. Block icons are also now displayed in the toolbar for easier identification.

Experimental Client-side Media Processing

Gutenberg 19.2 introduces an experimental client-side media processing feature. This reduces the server load and potentially improves performance and efficiency.

Other notable highlights include:

There has been one reported issue with this release, where it causes problems with the Web Stories editor. WordPress Core Committer Pascal Birchler has confirmed that the issue is related to Gutenberg and not Web Stories. Interested users can also check out Riad Benguella's post on Gutenberg development practices and common pitfalls.

12 Sep 2024 8:47pm GMT

Do The Woo Community: Enterprise in the WordPress Ecosystem with James Giroux

Avalara: providing cloud-based and scalable global tax compliance that is hassle-free, safe and secure plus topped off with enterprise-class security.

Episode Transcript

Brad:
Hey everybody. Welcome back to another episode of Scaling Enterprise WordPress: The Inside Track. I am one half of your co-hosting duo, back for another really fun episode. We have a really awesome guest, which we'll get to in just a second, but as always, I want to welcome Tom, the other half of this show, to the episode.

Tom:
Hey, Brad. Hey, great to be here. Excited to be doing another episode. For those that listened to Karim's last episode, unfortunately, I couldn't be on that one as I was on vacation up a mountain with very poor internet, so glad to be back home on the fiber.

Brad:
Yeah. Well, we're happy to have you back, and this is going to be a really fun episode, so I'm glad you're here because we have a really special guest whom we'd like to introduce now. James Giroux is joining us on the show. Hey, James.

James:
Hello. Hello, everyone.

Brad:
Very excited. If anyone who's been in the WordPress industry for a while has probably crossed paths with James at some event or some online endeavor. James, you have a really cool kind of history of your path through WordPress, and one of the reasons I want to set the context of why you're on the show about enterprise, I think that's important, but then we'll dive quickly into how you got there because I think it's a really fun journey, and I want to hear a little bit more about it. What really caught my eye, James, was back in July you posted a tweet and a blog post announcing that you started a new role at WordPress VIP under Automattic, and you're learning enterprise deeply. So right away that caught my eye because I had never quite heard that phrase, "learning enterprise deeply," but I was like, we got to get James on the show because he is literally doing what we're talking about within WordPress and the inside track around enterprise. You have a really great blog post about it, which we'll talk about and we'll share in the show notes, but I'd love to hear a little bit about your journey through WordPress, kind of quickly how you got to where you are now. You've touched so many different parts of the WordPress ecosystem that brought you to VIP and the enterprise level side of it. So, let's talk about how you got there real quick.

James:
Sure, yeah. I have been in the WordPress ecosystem for, oh, 15-plus years at this point, so it's been a long time. Not maybe as long as the two of you, but I'm chasing your heels a little bit. Like most folks, I got started just looking for something that I could use to build a website. So, that's kind of how I got started tinkering, and from there I like to call it the "four bases of WordPress." You've got Marketplace, Agency, Product, and Automattic. Those are the four bases as far as I'm concerned in WordPress. My journey is like that. That's why I called it a home run, but I started out really just on the freelance side, on the agency side, doing work for customers, clients, all that kind of thing. Then from there, I ended up working with a product called PageLines, which was one of the early pioneers of this whole page builder concept.

Brad:
I remember PageLines. Yeah, that was a long time ago.

James:
A very long time ago. So I worked there developing themes and plugins for that ecosystem, and that's really what kind of launched me into WordPress at a community level, was my involvement there. I was hired by PageLines eventually as their Director of Operations, working with developers and things like that. From there, I met some folks from Envato at PressNomics. I was at PressNomics 3, hanging out, driving around, and ended up hearing about a role at Envato. So, I joined Envato in 2016 as their WordPress evangelist, which was great. I could continue to go to all the events that I really wanted to go to and get paid for it, which was a really neat and novel thing at the time. After about five years there, I moved to Gravity Forms and worked at one of these pillar product companies in the WordPress ecosystem. Then I was at StellarWP, working with all the folks over there. I was a Director of Brand and Product Marketing there, then transitioned out of that, and now I am at Automattic in WordPress VIP as a Technical Account Manager. Bit of a career swap, but I'm loving it.

Brad:
Very cool. Yeah, no, I think one thing that stands out about your story is just, and I like to talk about the community and the impact of engaging, meeting people, and going to events. I know things are a little different than they were maybe 10 or 15 years ago, but there's still a lot of value in those events. Like you said, your career path was just by attending and being present, meeting people, and talking to people. It shaped your career and kind of opened some doors that maybe otherwise would've been harder to open, going in without any kind of a warm lead or knowing people within that company or within that industry. So, just want to touch on that, get out there because it can absolutely help in the growth of your career and what your goals are and your aspirations, which is another reason why I love this community.

So, going into really focusing on where you're at now and some of the goals that you're looking to accomplish, going back to that "learning enterprise deeply." You posted this a few months ago, so I have to imagine you have not learned everything about enterprise in a couple of months. I think you probably have a little bit further to go, but I'd love to hear a little bit about early on-it's been about a month and a half since your post and you've kind of dug into this a bit-but what are some of the things that really stand out? Maybe some of the challenges, or things that were unexpected or maybe even expected, but what really stood out just in the last month and a half, two months since you've been in this new role?

Certainly! Here's the continuation of the transcript with corrected spelling and punctuation:


James:
I think one of the things about enterprise that folks on the outside maybe don't understand is you really don't know what you don't know. I think that for me has been the first little bit of learning here-it's learning what I don't know. I didn't really know what a DXP was before joining WordPress VIP-that's a Digital Experience Platform, for those who don't know. I didn't really understand the role that WordPress played in larger enterprise infrastructure and how it integrates, and the kinds of complexities at a technical level that a lot of enterprises deal with. Nor would I, because so much of my past experience has been very direct WordPress, where you have one application, you have one WordPress installation that you're responsible for, and you have to be concerned about that at a very small scale. In terms of traffic, all the concerns are very different, and looking at how do I scale that thinking out and look at the kinds of challenges that exist. So, that's been really interesting. The sales cycle has been interesting. The role of technology service providers, or technology platforms like VIP, and the relationship they have with agencies, and how those work together. The role they play, and the relationships they need to develop with product companies as well, and how that factors into how we deliver solutions to customers and clients. It's a very interesting nut to crack, and I'm enjoying it. Yeah, it's so much to learn.

Brad:
We could probably do an entire show on sales cycles, couldn't we, Tom? I mean that's, oh boy. That might be a little bit of a trigger for both of us as agency owners in this.

Tom:
Yeah, we're both jealous of you not knowing about them.

Brad:
Yeah. It's interesting you mentioned not knowing what you don't know, and I think when the larger community hears "enterprise" and "WordPress" specifically, I think the assumption is it's a big website with a lot of content, a lot of writers, most likely a lot of users in the backend, and a lot of traffic, which is by and large pretty true, but there's a lot more than that. That's kind of the surface level of what enterprise entails. All the behind-the-scenes stuff of integrating with SSO and different providers and APIs, and all the security requirements that go into it that are well outside of Core WordPress. It can absolutely work with WordPress, but it takes more advanced teams to make those things happen. So when you really get under the hood of what the enterprise work is with WordPress, it's so much more than just big websites with a lot of traffic-a way I like to describe it. But there's a lot more than that when you start peeling back that onion.

James:
Absolutely. It's been really interesting looking at the number of people that need to be involved, and you can't really get away from it. You think, "Oh, it's just a big website with more traffic." But no, I mean it's bigger projects, there are more stakeholders, there are more moving parts that you may or may not understand or know about. There's a lot of extra discovery that goes into it. It's been really interesting watching different projects that we've gotten different customers on. So, we've got customers that are just starting and getting ready to launch and going through that process of migrating from maybe an existing build they have on a different platform or on a different WordPress installation over onto the VIP architecture. And then you've got those that have been on VIP architecture for a while and sort of what maintenance looks like in that cycle and how that goes forward. It's really, really interesting. And just the number of people involved at all different levels and the ongoing work and the constant communication that needs to happen at an enterprise level is way different from running a local restaurant or running a local e-commerce retail shop's website. It's very, very different.

Brad:
Yeah, no doubt. Tom, what do you got over there? I don't want to monopolize this conversation.

Tom:
Well, I'm keen to dive a little bit into some of the stuff that you raised in the blog post that you wrote calling on the WordPress ecosystem to embrace enterprise. So, why'd you write it? I guess this phrase "learn enterprise deeply"-we've typically reserved that phrase for pretty important things. I think Matt's only used it twice, for JavaScript and then for AI. So, why do you think enterprise is that important to the WordPress ecosystem?

James:
Well, as a community, as a content management system platform and open source, we've done a really good job of hitting the ones and twos, right? We are really good at being a first choice for a lot of folks that are looking for a website that delivers minimal traffic concerns, no compliance, no security-none of that kind of stuff. But if we want to grow the ecosystem beyond the ones and twos to the hundreds and the thousands, we really need to look at where a lot of folks work. They work in government, they work in large enterprise, they're on marketing teams of thousands rather than marketing teams of five. There are intranets and extranets and all of that kind of stuff where WordPress has an opportunity to flex its muscles. And we have maybe not fully understood that or cared so much about it. Like all folks, we take the path of least resistance. We go for what's easiest first. We've done easy. We've accomplished easy. And now it's time to accomplish what's maybe a little bit harder. My whole pitch, my whole thinking behind that is, if we want to see WordPress grow to 80% market share-which I know is probably a pipe dream-but if we want to double what we're currently at, 43%, and get to 86%, then we need to get into these enterprises because that's where young people are going to work as well. They're not all going into startups, they're not all building apps for themselves and doing things for themselves. They need to find a job, and they're getting jobs in banks and pharmaceutical companies and all these other places. If the tooling that they're being provided is Sitecore or Adobe, whatever Adobe is running with, they're not getting the best of what the web can be. And so, that for me is one of the reasons, because once they're experienced with WordPress in work-when they're paid to use WordPress in their day-to-day-that's going to leak out into their side projects because that's the platform they're most familiar with. That's how we grow adoption. That's how we grow WordPress in my opinion, and actually get it to a place where it's solving the really hard problems of the web that folks have.

Tom:
That's a super interesting take, because it's like actually probably a lot of the early growth of WordPress was almost the opposite of that, right? People were not using it at work, but they were discovering it and using it for their own stuff. They were blogging, they were using it for their kids' football team or whatever, and a lot of the early penetration into business was people using it for their side projects and then bringing it with them, fighting the good fight internally: "Why don't we use this WordPress thing for our site? I've been using it, it's great." Maybe we're transitioning out of that, and actually it needs to become the default at work so that all these young people who get jobs are introduced to it there. I love that take. I've never really quite thought of it in those terms.

Brad:
I think even early on, as WordPress really started transforming from a blogging platform to a true CMS, back when custom post types were introduced and it really became an option for the enterprise, getting some of those early enterprise clients also really helped validate it for everybody. I know it made my job easier as an agency owner when I said, "Hey, we just launched something on microsoft.com with WordPress." So, everybody we talked to at that point, the idea of "Is it secure? Can we use it?"-those questions really went out the window once we said, "Well, Microsoft's using it, and they did a full-blown security audit on it." So that in some way also helped, I think probably more in that mid-market, to say, "Hey, we can actually use this when we just thought it was a blogging platform." So, I think even that early on, just getting a couple of those key large enterprise brands on WordPress, and we could all point to them as a community and say, "Look what these brands are doing," that really helped accelerate WordPress into the CMS market and has continued to, because I still use those examples. But we don't have to answer those questions anymore, or certainly not as often. "Is it secure? Is it a blogging platform?"-those are long gone, right? The enterprise has helped squash that, in my opinion.

James:
Yeah, I completely agree.

Tom:
I'm interested in enterprise WordPress's place within the wider ecosystem, the awareness of it, the role it plays-maybe what your perspective was on that or your awareness of it before, and how that's shifted since. And maybe, therefore, what you think we need to do more as an enterprise WordPress community, as the subset of the WordPress community that's focused on enterprise, to better showcase actually how successful WordPress is in enterprise. You were saying you joined VIP, and you get exposed to quite a lot of stuff, and you're like, "Oh, I perhaps didn't actually know WordPress was being used

in these ways or the level of complexity." It's a bit of an iceberg problem I think we have, where there's quite a lot more happening than perhaps people realize.

James:
I think there are a couple things to that. Before I really dove deep into enterprise, I couldn't find anything on WordPress enterprise. There was nothing out there I could read, there's nothing out there I could go to. I mean, I could go to events-and I did-and I'm very grateful to folks who would invite me to show up at their enterprise events. But I didn't know how to even jump into those conversations or start them, and that's a big part of it. I couldn't go to a WordCamp and get a 101 talk on enterprise. We joke about the sales cycle, but it's so intimidating. But where's the opportunity for agencies that are looking to build out their freelancer bench to talk about what does it actually take to become an enterprise freelancer or to work in this space? Or how can we equip you to be able to jump into what we need? There's none of that. And so, I think that's one of the reasons why I wrote that blog post-to sort of wave a bit of that flag and say, "Hey, I can't even find anything to help me get started on the path toward enterprise." And the reality is that what's going to end up happening is folks that are really good at Drupal-not that that's bad-but that's sort of where enterprise is, or they're really good at Sitecore, and they're going to go, "Okay, well, we'll expand our toolset, maybe we'll look at WordPress," but they're not really going to be from the community. They're not going to be part of the story of what we've been, and it's going to make it harder for those of us who truly understand what WordPress is all about to get in front of these enterprises that are looking, possibly, at WordPress as a tool, and helping them understand what this ecosystem and this community is all about.

So, that's one thing. I think, what can enterprise folks be doing? You need to get out there more. This is hard because I've been here a couple months now, and I haven't written a blog post since my announcement post because my brain is so packed with all of the things that I'm trying to learn and understand, the complexities, and just all the things that I'm finding it hard to sit down and write. What do I write about? What do I talk about now? So, I need to get out there and do that. And that's what we need more of. We need more enterprise champions showing up at WordPress events, at WordCamps, doing things like this podcast-which I think is fantastic-and just really talking through what does it mean to be enterprise WordPress? What are the challenges we're facing? How do we invite folks in? How do we get product folks in who maybe have no idea how their product is being used in an enterprise setting? I've got a call coming up with one product company that has no enterprise pricing, no enterprise service level, but their product is being used in a really intense way on a customer's website. What's really cool is being able to facilitate that as somebody who's got both the community side and the enterprise side now, but we need more of those relationships to develop between WordPress product companies and enterprise agencies and enterprise infrastructure companies-I would call VIP. Let's get them all around the same table and talking. The product companies don't have any clue how their products are being used at scale.

Tom:
Yeah, I mean that's definitely a common problem I see.

Brad:
Yeah, and thank you for calling out the podcast because honestly, one of the reasons we're doing this is because there aren't enough people in the WordPress ecosystem, WordPress space, talking about enterprise and sharing our knowledge and information. Getting people like you, James, on to share your experiences, your learning, and where you're at, because there just hasn't really been a lot of this, even going back across the 15 years or so that we've all been doing this. There hasn't really been a lot of dedication around enterprise, talking about it, challenges, what can we do to help push it? It's another reason why we're all really excited, and Tom and I are both a part of the Scale Consortium, which for years I think many of us kind of looked at Automattic, and maybe even VIP in a sense, and said, "Help us, sell us in the enterprise. Help push us into the enterprise." But the reality is it was on all of us to do that. So, it took a little bit of time, but finally all the agencies were able to get together that work in that space, in the WordPress enterprise space, and say, "Look, if we work together on helping spread positive information and what people are doing in WordPress enterprise, it's going to help all of us." And so now the Scale Consortium exists exactly for that reason. We're really pushing into the space to help spread awareness, spread information, help people learn around enterprise, have events at WordCamps or other webinars, share that information. Because you're right, I think many of us agency owners especially, it's trial by fire. Did I start WebDev thinking I want to get into enterprise? No. But when Microsoft walks through your door or a big brand walks through your door, you learn it real quick, right? Not going to tell them no. So, I love that you call that out. Exactly why we're doing this. We're hoping to get more of this in, between the show we're doing here, and then with Karim and Tom. Even though we're early, I feel like the information we're getting out there-these are conversations that have not been happening in the public, and they need to be happening. So, I love it, and I'm hoping that the audience is also understanding what we're trying to do here and getting some value out of it.

Tom:
Yeah, I mean I hope that you do keep blogging as well, James, actually, because I've read your blog for a long time, long before you were writing about enterprise, so I'm kind of even more excited to read it now that you're in enterprise, which is a space that's even closer to my interests. The listeners to this show should all go and start reading it-that'll add to the pressure for you to then give them some content that's relevant.

James:
I don't know if it's writer's block or if it's just my brain is full of all the things, but I've been challenged. I'm going to WordCamp US and I'm looking forward to the conversations. WordCamp US is really exciting for me this year because of Showcase Day, and because it's a really good opportunity for enterprise to have its moment in the sun, so to speak, and the spotlight. We get to see innovation, we get to see scale, and it's so exciting that somebody's starting to pick that up a bit. I'm looking forward to the kinds of conversations it spurs. I'm curious what I'm going to be thinking about after.

Tom:
Yeah, I think it's going to be super interesting. I mean, I agree, it's a really exciting evolution. I know even last year there was the NASA keynote, which was almost a precursor to this Showcase Day, and that's a really great evolution. It's going to be interesting-probably the first time there's going to be a day with all of those people who are doing this kind of work, all there, showcasing together. The conversations afterward-I'm pretty interested to see what the floor traffic is like, and the kind of conversations that come off the back of that, the collaboration. Hopefully that opens up.

Brad:
There'll probably be some surprises in those showcases, too. There are going to be some things that kind of blow us all away-like, "Oh wow, look what they built, look what they did." I mean, just WordCamp last year with NASA.gov and the big push there and the presentations was honestly digging into understanding the amount of data and what they worked through was pretty mind-blowing. And obviously, it was all behind the scenes until they presented that. So, it was just fun to hear more of the challenges, more in how they worked through those with NASA, especially with the amount of content, which was absolutely insane, that they had to migrate into a block-based system. So, it's fun sharing that stuff, it's fun hearing it. I'm glad it is more focused. I know Matt used to-Matt Mullenweg-used to mention some highlights in his State of the Word, but he's kind of gotten away from that, and probably for good reason, because he doesn't want to play favorites when you're showing off what other companies did. That could come off as playing favorites. So, I'm excited about that, too, because I'm sure there are going to be some interesting surprises-projects none of us knew were even out there, things that happened, and we'll be like, "Oh, wow, I'm going to be telling some of my clients about that because that's cool." Sharing the information around enterprise, sharing out there. I know it's not all enterprise-it's just showcasing WordPress-but I have a feeling there'll be a few big showcases in there.

James:
I'm excited to see our enterprise customers and clients in the WordPress ecosystem having their time to present what WordPress means to them and how they're using WordPress from their mouths, from their perspective, and what will it mean. The WordPress ecosystem is very different from the

way the rest of the world operates. We're kind of nice. And because we're kind of nice and because we're kind of kind to folks, the way we operate and interoperate together is a little bit different, and that can throw folks for a loop that are coming from other industries. And so, it'll be really neat to see what happens when you get these big publishers that are competitors in the publishing landscape together, showcasing how they're using the same technology platform to achieve their goals and do things, and what's going to happen when they start talking to each other off the stage and see some of that WordPress culture, that WordPress community vibe sort of leak into how they interact with each other. There's just something really cool about that that I'm looking forward to seeing happen, too.

Brad:
And honestly, just in WordPress in general, I feel like that is the vibe. People want to share. And maybe honestly, it's the open-source vibe. It's not just WordPress. It's like if you're into open-source and you're into it enough that you're going to attend an event about a piece of software, I've got to believe there's some passion behind it. You're proud and excited about what you're doing, and you want to share it-even if you're sharing it with competitors, you want to say, "Hey, look at the cool things we're doing over here." And they're probably, like you said, sharing some things they're doing that you weren't aware of or you might be interested in. It's similar to what agencies are doing and freelancers-we're all showing off our work, like, "Look at this cool thing we built." So, you're right. Seeing actual owners of websites, publishers, really showing off and sharing information is going to be pretty neat. It's just open-source. We're all out there trying to build and help each other and just build an awesome platform that we can all use. So, I'd like to talk just a little bit about some of the goals. What are some of your longer-term goals within this new role? What kind of impact are you looking to make around organizations, clients, or just WordPress in general? We've talked about it being just a month and a half-it's still a fairly new role for you-but long-term, your vision, what kind of impact are you looking to make?

James:
Well, I've packed up 15 years of marketing experience and taken that hat off and put on the account management hat. It's a bit of a career reset for me, which is kind of neat to do. Long-term…

Brad:
Maybe a little scary too, huh?

James:
Yeah, it is. It's very scary. You're sort of starting from ground zero again, but with 15 years of experience, it's kind of cool actually to do that. My first goal is to become the best technical account manager in the world. So, that's maybe the entrepreneur in me going, "Take over the world!" or whatever. But I want to be the best.

Tom:
I like that. That's only the first goal.

James:
Yeah, that's the first goal: be the best I can be, be the best that I can do, support my team, be somebody they can count on, bring all of the knowledge and depth of experience I have across the WordPress ecosystem into this role and add value to these relationships, and add value. That's the number one thing. Maybe selfishly-we don't really have a lot of-this sounds so funny to say-but enterprise WordPress influencers. Why not be an ambassador for enterprise WordPress? We need more folks that are championing the transition from one side of WordPress to the other and opening those doors, and it's something I did all throughout my career in the rest of WordPress, so I don't see why I couldn't do that at the enterprise level and just connect folks to each other, connect partners. So many of our product companies just need a door to be opened for them or exposure to what's going on in enterprise.

Tom:
Yeah, I mean I'd love to do an episode actually on enterprise for WordPress product companies. Of all the parts of WordPress, I think they're the ones that seem to have cracked enterprise the least. But like you say, there are lots of enterprise companies that are discovering their stuff and using it, and there's a lot of opportunity there.

Brad:
Please start charging more for products because enterprise, they don't want to pay $99 a year. They just won't trust it if it's that cheap.

James:
But the issue isn't the $99, it's the fact that they're not going to get the level of service and access to a team that they need. Every build is unique. We think that folks in enterprise are just using WordPress as vanilla WordPress-they're not. They're taking WordPress, and they're molding it and shaping it into something that works for them. They're rebranding it internally. They have different names for it as a tool, and they can do that because they're paying millions of dollars a year to do that. So, yeah.

Tom:
Well, yeah, there we go. Add that on the list, Brad, for a future episode because…

Brad:
Yeah, I love that idea, Tom. I love that. And talk about enterprise influencers. I mean, I've got to be honest, Tom's got the look, he's got the style, he's got the voice-just lacking the influence! The stars are aligning, Tom, I'm telling you. But I do think I love it because, like we talked about, getting more content out there-and honestly, even YouTube and videos are so popular now, more popular than ever, and it's really gaining traction. And within the WordPress space, there's just a lot of great video content out there, and I expect that's only going to continue to grow, especially in the enterprise space too, as that usually catches up once the masses are out there doing it. But yeah, more content, more information, sharing resources, getting people talking about more of the challenges, talking about the FUD that's out there from other platforms, talking about WordPress and how we kind of speak back to that and alleviate those concerns. So, enterprise is a big topic, and there is a lot to dig into, which is one of the reasons we're doing this. We bring on awesome people like you, James, and really understand where you're at, your experiences. And what I would love to do is have you come back on the show maybe in six months, maybe next year at some point, and really circle back through your progression. What has transpired? Did you expect it? What have you learned? Things like that. Since you are a little bit new into the role, I think it'll be fun to have you back on a little bit later next year and kind of dig back into where we're at.

Tom:
When you're a grizzled and tired enterprise WordPress expert.

James:
After the honeymoon period is over and I'm into the day-to-day grind. Yeah, exactly.

Brad:
Yeah, after the old honeymoon period. But it's pretty exciting. Just to wind down a little bit, any kind of final thoughts around the enterprise space and really what's just top of mind for you, James? We talked about short-term goals, some longer-term goals, but really what's top of mind for you in the space and where you're looking to go?

James:
I think, like that blog post says, we've got a lot of opportunity to help people get a better grasp of what enterprise actually looks like. I think WordPress is ready. I think a lot of our product companies and even our hosting companies that are maybe more downstream are ready to make the leap. They just need some help figuring out what that looks like. I would like to see more of that happening. Maybe I'll write about that. Actually, that's a good topic for me to sort of follow up on. What am I thinking about? What are my final thoughts? I'm curious to see how we as CMS folks-not just as WordPress-start to navigate thought leadership more broadly. WordPress, we're competing against Adobe, we're competing against some other proprietary platforms. We're going up against these monolith DXPs, and we're advocating for composability-all words that make sense to folks that are in enterprise, but maybe don't make sense to anybody outside of it. But we have an opportunity to lead the pack when it comes to innovation. AI, we're so much more agile than a lot of these other platforms are, and I would love to see us moving more in that direction as well, more broadly, and bringing more folks who maybe have sold themselves to these other platforms to come over and see what it's like. The grass is very much greener over here. So, yeah, those are the things I'm thinking about.

Brad:
Come on over. We're very friendly.

Tom:
I mean, that ties back perfectly into the need for more influencers, right? Because I think actually the biggest need for influencers is to project that vision that we have-that WordPress has for enterprise-out into the world. At the moment, most of the buzzwords and categories and descriptions of what enterprise CMS is are set by our competitors, set by the analysts. And we tend to play catch-up, and we tend to say, "Oh, WordPress could do that," but they're the ones that came up with what that is. And then we're scrambling to try and prove WordPress could do it.

James:

That's exactly right.

Tom:
Actually, perhaps with folks like you getting out and saying, "Well, actually, this is what WordPress's vision for enterprise CMS is," that's super exciting. I think if we can start doing that-that's a great point, Tom. That's the next era of growth.

Brad:
Awesome. Well, this has been a really fun show. Appreciate you coming on, James. You mentioned you're going to be at WordCamp US coming up, which is September 17th through the 20th out in Portland, Oregon. I will be there as well. Tom, are you going to make the trek over?

Tom:
I will be there, absolutely.

Brad:
Yeah, you'll be there. It's a long flight for you.

Tom:
It's a long flight for me, so I'm stopping in New York on the way, so I'm not coming as far.

Brad:
Okay, well, that'll help break up the flight a little bit. But anywhere else people can find you online, James? You want to plug your blog or any social networks where people can interact with you if someone wants to chase you down and say hi?

James:
Yeah, absolutely. My blog, JamesGiroux.ca is a great place. My handle pretty much everywhere is JamesGiroux, so you can find me on X (formerly known as Twitter), LinkedIn, or give you my Gravatar-yeah, so it's all there.

Brad:
Very cool. Well, I look forward to seeing you in person there. I'm definitely going to track you down at WordCamp US and get a little FaceTime. Really appreciate you coming on the show, James, and we're looking forward to following your progress and really rooting for you and rooting for the enterprise. And we're here to support, however, as obviously, this is important to all of us, as well as a lot of people out there. So, I'm excited we're doing the show. I'm excited we're talking about it, we're getting people like you that are talking about it, blogging about it, and right in the middle of it. So, this is exactly what we're looking to showcase with this platform. It's been a lot of fun. So, Tom, anything you want to plug before we head out?

Tom:
No, just to say thank you for the work that you've been doing so far, especially the blogging and the influencing. That's, I think, a big gap. So, keep doing that. And yeah, looking forward to talking more about WordCamp US.

Brad:
Awesome. Well, for Tom, I'm Brad Williams. This is Scaling Enterprise: The Inside Track. We will see you on the next episode. See you, everyone.

In this episode of Scaling Enterprise WordPress: The Inside Track, co-hosts Brad Williams and Tom Willmot discuss the evolving role of WordPress in the enterprise space with special guest James Giroux, Technical Account Manager at WordPress VIP.

James shares insights from his 15-year journey through the WordPress ecosystem, touching on his experiences across freelancing, product development, and enterprise-level projects.

The conversation covers key topics such as the challenges and opportunities of scaling WordPress for large organizations, the importance of community and networking in career development, and the future of WordPress in the enterprise market.

They also highlights the need for more enterprise WordPress champions, the role of thought leadership in driving adoption, and the exciting developments to come at WordCampUS.

Takeaways

The Importance of Enterprise in WordPress Growth: James emphasizes that for WordPress to continue its growth and dominance in the CMS market, it must break into enterprise-level organizations, which house large teams and complex systems. The WordPress community has historically catered to smaller users, but scaling up is necessary for future growth.

Learning Enterprise Deeply: James shares his experience transitioning into the enterprise space, learning about complex systems, technical challenges, and the unique needs of large-scale organizations. He introduces terms like DXP (Digital Experience Platform) and highlights how enterprise WordPress involves more than just a large website-it's about integrating with systems, APIs, security, and compliance.

The Role of Community and Networking in Career Development: All three hosts stress the importance of attending events, engaging with the community, and making connections to advance in the WordPress ecosystem. James credits much of his career growth to attending events like WordCamp and building relationships within the community.

Challenges in the Enterprise Space: There are many moving parts when it comes to WordPress in the enterprise-more stakeholders, longer sales cycles, complex integrations, and technical requirements. James points out that many people in the WordPress community might not realize the depth of these challenges until they dive in.

The Opportunity for Product Companies: WordPress product companies often don't realize how their tools are being used at an enterprise level. There's a need for more collaboration between product companies and enterprise organizations to align pricing models, service levels, and support structures that suit large-scale projects.

Influencers in the Enterprise WordPress Space: There is a growing need for WordPress "enterprise influencers"-people who can champion WordPress as a solution for large organizations and communicate its advantages to a broader audience. By doing so, WordPress can challenge competitors like Adobe and Sitecore more effectively.

The Value of Events Like WordCamp US: Events like WordCamp US provide a platform for showcasing what WordPress can achieve at scale. Presentations like NASA's website migration highlight WordPress's capabilities for handling massive projects, and these showcases help promote WordPress as a serious contender in the enterprise CMS space.

Long-term Goals in Enterprise WordPress: James is focused on becoming a top-tier Technical Account Manager while also serving as an ambassador for enterprise WordPress, bridging the gap between the community and large organizations. His long-term goal is to help more companies adopt WordPress by educating and advocating for its enterprise capabilities.

Links

12 Sep 2024 9:18am GMT

Matt: Inside Out 2

It's a tough pick, but I think Inside Out 2 might be my favorite Pixar movie. Just everything about it was just so well done. How they incorporated the different aesthetics, neuralinguistic concepts, everything. Chef's kiss.

12 Sep 2024 2:31am GMT

11 Sep 2024

feedWordPress Planet

WPTavern: WordPress 6.6.2 Released with 26 Bug Fixes

WordPress 6.6.2, released on September 10, 2024, brings 15 bug fixes to Core and 11 to the Block Editor. Led by Tonya Mork and Vicente Canales, with Aaron Jorbin mentoring the team, this is a short-cycle maintenance release ahead of WordPress 6.7, scheduled for November 12, 2024.

Core Fixes

This update addresses 15 Core issues, including CSS specificity changes in certain themes and the resolution of Button Block CSS conflicts. Other notable improvements include:

Block Editor Fixes

This release addresses 11 issues in the Block Editor, including improved layout style specificity in the non-iframed editor and fixes for pseudo-element selectors in custom block CSS. The release also reduces the specificity of the default featured-image block style rules and prevents the duplication of template parts in non-block-based themes. Post Editor has received multiple improvements.

Tonya Mork's post gives the complete list of bug fixes in WordPress 6.6.2.

Websites with automatic background updates will automatically get updated to WordPress 6.6.2 while others can download it from WordPress.org or update the website via the WordPress Dashboard.

11 Sep 2024 8:56pm GMT

Gravatar: Meet the ‘Gravatar Enhanced’ Plugin for WordPress

Meet the all new and improved Gravatar Enhanced - a plugin that brings more Gravatar goodness to WordPress while keeping privacy at the forefront.

What's in the box? Let's take a look inside:

Gravatar Privacy Shield

Your users' privacy matters. That's why we've built robust privacy features into Gravatar. We're not in the business of tracking or selling data. Instead, we're focused on helping you share only what's necessary and curating your profile for the open web.

Our Privacy Shield features of the Gravatar Enhanced plugin give you control:

These features are a direct response to feedback from the WordPress community. We're committed to transparency and putting you in control.

Learn more about the proxy service here.

Gravatar Profile Block

Gravatar is evolving beyond avatars. Our new Profile Block lets you showcase user information anywhere on your site. It's dynamic, it's sleek, and it's effortless.

Here's what you get:

Think of the possibilities:

Right now, the block displays a default card. But we're cooking up something special. Soon, you'll be able to customize both design and content.

Want a sneak peek? Check out these upcoming patterns we're working on…

Once you've enabled the plugin, just look for the Gravatar Profile block in the editor to get started.

Additional Enhancements

There is more to the plugin that you will want to explore:

Watch this space, as there is a lot more to come soon!

Questions or feedback? Drop them in the comments below.

Get Gravatar Enhanced today.

11 Sep 2024 3:30pm GMT

WPTavern: #136 – Matthias Pupillo on Enhancing WordPress With AI Translations

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, enhanced WordPress with AI translations.

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 Matthias Pupillo.

Matthias has extensive experience in the technology and creative sectors, and is currently working as the co-founder of FluentC AI, an AI powered language technology company.

With a background in technology, he's focusing on developing solutions to enhance communication across different languages and platforms. He's been involved with WordPress since its early days, around version 1.2, and has a rich history of web design and consulting, having worked on hundreds of WordPress websites. But it's only recently that he's become more engaged in the WordPress community through events like WordCamp Buffalo.

In the podcast today, we talk about AI driven language translations, particularly focusing on Matthias's work with FluentC, which is his translation plugin for WordPress. It supports multithreaded simultaneous translations of up to 140 languages, enabling your pages and posts to be offered in other languages in just a few moments.

We covered the differences between AI models designed for translation, such as ChatGPT, and Llama, which aren't specialized for this task, and how his platform builds a contextual layer above those.

He emphasizes the importance of context and diverse multi-lingual data in producing high quality translations. FluentC's functionality involves local storage of translated content in an effort to maintain website speed. This is done using native WordPress hooks, and URL modifications.

Matthias also offers his thoughts on the ongoing multi-lingual support phase of the Gutenberg project. And his hopes for FluentC to evolve from a standalone plugin to an API, which could be used by WordPress Core.

We get into the broader implications of AI in translation, the need for open source models to compete in this rapidly evolving space, and the parallels between AI evolution and past trends like blockchain, and web 2.0.

If you're interested in the intersection of AI and WordPress, or looking to enhance your website's multi-lingual capabilities, this episode is for you.

If you'd like to find 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 Matthias Pupillo.

I am joined on the podcast today by Matthias Pupillo. How you doing Matthias?

[00:03:54] Matthias Pupillo: I'm doing fantastic, Nathan.

[00:03:55] Nathan Wrigley: Very, very nice to have you with us. We had a little bit of a chat before we pressed record, and in that chat, Matthias revealed to me that he's got a long history with WordPress, but not necessarily the WordPress community.

Matthias, we're going to be talking about AI, transcribing, transliteration, multilingual, all that kind of stuff today. Before we do, would you just give us a quick potted bio of your history with tech, WordPress, however far you want to go back.

[00:04:19] Matthias Pupillo: Oh yeah, absolutely. So I've been a software, I have to say commercially, building software for 25 years. I've been recreationally building software for 35 years. So I started pretty much when I was eight building code.

And I started in WordPress with 1.2. I was writing hand coded HTML in Microsoft notes, and so it was a dramatic shift back then in 2002, 2003.

And I was running my own consulting firm, doing web design professionally, and found WordPress by, it was a divine intervention one day. Someone wanted to pay me for editing, and I didn't know how to write software, besides HTML, CSS and Java. And Java back then was not building a website. It was a complicated journey and it was fun.

The day WordPress 2.5.5, when we had tabs, that was great. And then we got 2.6 and it went horizontal menu, that was a fun day. It's been a long road with WordPress. I think I've built two or three hundred websites with it, maybe more. Not to mention coaching, staffing, and like guidance from an architecture standpoint.

[00:05:22] Nathan Wrigley: That's a really long and storied, well, a really long story basically, so that's lovely. But however, one of the things that you said a moment ago was that, although you've been using WordPress for a long time, the community side of it is more recent I think. Only in the fairly recent past that you've got yourself out to events, and started to interact with the community more. Is that right?

[00:05:41] Matthias Pupillo: Yeah, that's right. Yeah, so I built the translation company FluentC, we built for apps, and GraphQL, and other integrations. And I forgot WordPress, I really did. Our website was built in WordPress, our marketing flow, our CRM, everything was in WordPress, and I forgot to build the engine.

So, out of my shame of forgetting that, I rapidly built the plugin. Then spent four months trying to get it approved, and then joined the community in person. And my first WordCamp was in Buffalo this last May.

[00:06:09] Nathan Wrigley: You alluded to it earlier, but I might as well get the URL out there. So FluentC is the URL, but it's not what you are thinking, I suspect. I imagine you are thinking it ends in a Y, but my records here show that it's fluent, and then the letter C, so F-L-U-E-N-T-C, dot io. So, fluent, the letter C, dot io. What is this service? And we'll come to the WordPress component in a moment. But obviously you built the SaaS version, if you like, first. What is its MVP, if you like?

[00:06:39] Matthias Pupillo: Yeah, so it came out of a problem that, I've built a lot of apps for healthcare, and it always offended me that they were only in one language. And the cost, time and effort to build a multi-language app was just always put to the back end of the priority list. And in healthcare it's incredibly important that the patient knows what the directions are, knows what the medications are, knows what their appointments are.

And so I built FluentC to handle that, and to build that multi-language, make it app developer friendly, our SaaS component is a no code solution, no code translation. If you want it native, are built into the app itself, use our GraphQL, and our i18next integrations. And then it was just, it just had to exist because of, patients need that native touch, and it needs to be super easy.

Developer tools are always built by people who aren't developers, it has always been a sore point my side, that people just cannot, developers are not the first thought. Like you have to write code for a living, we have to make this easy for you. So we built that first.

[00:07:41] Nathan Wrigley: Can I just ask, in the US, given that you've mentioned the healthcare industry, in the US is there an obligation for that particular industry to have things translated into multiple languages? Here in the UK where I'm based, if you are going to produce something and it's going to go into a hospital, for example, I think there is legislation around that. I don't know what the cornucopia of languages are, but I know that there is some responsibility there. Is the same true in the US? Does it cover a particular bunch of languages? Is there a minimum requirement that you can have before you can say that's done?

[00:08:13] Matthias Pupillo: Yeah, there is a minimum number of, relative minimum number of, languages. It varies state by state, and it's for the in-person experience. If you show up to the hospital and you only speak Spanish, they have to have someone in the building that speaks Spanish, or a translator available by phone. Or if you speak Russian, or Czech, or Slovakian. And they have to take care of you, and they have to treat you, and they have to give you care, and then they hand you the directions to leave in English.

They send you your email notifications in English. After just saving your life in Croatian, they then hand you an English sheet of paper with the directions on how to get your next step care.

The obligation, you know, Canada has that hard list obligation of two languages, French Canadian and English. But the US is sort of the in-person experience, but not the digital experience. Not your emails, not your text messages, your notifications. None of that is compelled to be in multilanguage.

[00:09:05] Nathan Wrigley: Let's turn our attention away from healthcare and just think about, I don't know, like an e-commerce store or something like that. I guess this whole idea of getting things translated just makes perfect sense over there as well. Because for the last 10 years we've been all getting more and more into buying things online from our mobile phones, in the comfort of our own homes, sitting in an armchair and what have you.

And increasingly, a lot of the properties are crossing international borders, so it's not difficult for me to buy from a US company, or a European company that isn't based where I am, knowing that the shipping and everything will be taken care of. But I guess the language component, for me, I am only an English speaker. So if I, for example, was to come across a great deal on a French website, I wouldn't know what it was because it would simply be in French. So I guess there is a real good economic argument if you are hoping to participate in international trade, there's a really good compelling argument to get behind this.

[00:10:01] Matthias Pupillo: There really is because e-commerce is one of the ones that is, once you fulfill the product, you're done. You've shipped it. Some amount of people will call support, some will email, some will use chat. For the majority, overwhelming majority, of e-commerce sales, it's ship it, and you're done. You really don't care if the person that spoke only German. You ship them the great product, maybe you have multi-language directions if they need directions, we should be designing products that don't need directions, like a T-shirt.

But yes, the ability for a website and e-commerce to have those additional keywords in those native languages adds billions of potential customers. We did the analysis, and if you just cover Hindi, Chinese, English, French, and German, it's about five languages, you add about 4.2 billion potential customers. You're adding millions of new keywords. You've spent so much time, most of our WordPress, and the Woo people, spend so much time optimising their titles, their descriptions, their framework for communication on their products, and then that's it, it's in one language. And it's perfect, it's beautiful, but it really doesn't serve them for 4 billion customers.

We support about 140 languages. There's about 40 languages that cover 8 billion people. Those searches are the key. You can expand at no cost, your SEO presence, just by having the translations built in in a search engine optimised way. And e-commerce fulfillment, all your tools, that's an email and chat. The phone one, you're going to struggle with, you may have to build some extra capabilities. That's where the 4 billion customers need to make enough revenue for you to have some support for them. But if you have 4 billion new customers available to you and you don't have the revenue, I'd like to question your product.

But from an e-commerce standpoint, selling globally is super easy now. Woo handles the transactions, handles the currency, you can get some plugins for that. You can do the fulfillment. It's super easy to cover all the taxes, but you forgot the descriptions. You forgot the titles, the tags, the meta tags, all of that stuff. And the AI translation these days, because you need a special language model, you're using special descriptions, and they're really good at this. It really is a known thing to translate, and it's super easy to adjust and bring in that new traffic. And I think that's the important thing about e-commerce, yeah.

[00:12:22] Nathan Wrigley: If we rewind the clock, I don't know, 25 years or something, before the internet had taken off, apart from a bunch of really nerdy academics at CERN or something like that, the idea of owning a shop which would be communicating globally was really more or less pie in the sky. You know, there are a few giant companies that we all know of that were crossing international boundaries, car manufacturers and things like that, these giant entities.

But people who had a regular shop, which you might describe as a bricks and mortar shop, they're not going to be doing that because they're locally based, there's no prospect of doing that, all of it is completely out of bounds.

And then along comes the internet. Suddenly the boundaries are collapsing. And although it's still probably out of bounds for many people, it's becoming increasingly obvious to any store owner that you can ship things. All of that shipping capability has been taken care of, the logistics can be taken care of by somebody else.

But there's this missing piece. And I guess, again, if we rewind the clock about 25 years. The idea of translating things must have been fabulously expensive, because for every piece of text that you wished to translate, presumably you had to get a human being to read it, spend time wrangling it, and then giving you the translation, which you would then need to print in some way.

But now, the advent of AI, and I know that AI is all the rage at the moment, but it does seem like a lot of the AI stuff is kind of hype. And some of it might have utility, but much of it doesn't seem to have utility. But it really feels like the translation piece is really credible. I don't know how perfectly accurate it is, whether it's 95% from English to French, say, or 99.9, I don't really know, but because that's such a logical thing to do, it does seem like an area in which a computer could excel at. Is that the case? Is translation from one language to another, do computers do this increasingly well, accurately?

[00:14:18] Matthias Pupillo: Yeah, computers are doing it very well. And it is a different AI than the ChatGPT. ChatGPT, Llama, some of those things are terrible at translations, you need a special one for it. And the special ones are getting of standard, by the book translations very good. They're still very bad at a couple of things, colloquialisms. We have a great phrase, six of one, half a dozen of the other, that doesn't make any sense in Spanish.

We lose such great things, like there's a wonderful Spanish word, an event called the quinceañera, which is your 15th birthday party. There's cultural significance in language that we lose. And we are trying to fix that. Everyone's trying to fix that. It's as bad as it's going to be. But as far as formal communication goes, if you were setting a date and a time for an event, or you were describing what is best be described as a pair of shoes, or fixed product file folders, or something like that, it does very good at those things.

It doesn't do good at tone and colloquial mannerisms. But other than that, it's pretty good. The AI translations are getting so good. And the cost to review them. So I was once on a project years ago, and this is before this. They built an app, then they sent it to a translation company with no context, so it didn't say what was on the page. So there's this wonderful place in the world called Turkey. There's also a wonderful piece of food from a bird called turkey. And so here you are with the word Turkey, the country, or turkey, the meat, being all across your website. So even humans without context get it wrong. And so you really need that context engine.

We also have this wonderful thing in most websites called the back button, we do that. We also as humans have a part of our body called the back. So in other languages, those aren't the same word. And those type of things, humans get wrong so often because they just see the word back, and they just see the, most translation tools that send them over to the company to even manually do it, they do it one word at a time. One line at a time. And there's no context, so they're just like, I guess it means the country, it's capital, I guess we're not talking about food, but it was a recipe guide and it's your turkey dinner. And so those are the type of things that even humans get wrong still.

And then the management of it, back to developer friendly. Could you imagine getting emailed a spreadsheet every week as you're trying to go to prod? You're building a website, here you are, new post, new blog, new product. Okay, I got to email, and I got to check my email, and then I got to save it on that one, and I gotta create a new one, and then I got to save it again because, oh no, I changed the description, now I have to go back to the translator.

Because in your native language, every keystroke, comma, everything matters. So the human translate, I got to go back, and now I have an entire workflow added to my post and pages. And I love my post and pages, I just want to go in and type and hit save. I barely want somebody else to review it. This is WordPress, we're cowboys, we go right to prod. We hit save, we hit publish, we hit draft for a little bit, but we're going to prod. And that's the difference with these older systems and how to do this is that. With humans involved, you either have to have a huge team or you have to do it yourself, and it still impacts your workflow.

The real problem with translations is it's so time consuming. It's so much effort. We thankfully have a connected enough world that we can find a chain between every language on Earth. We can find a person who speaks English to French, we can find a French person who speaks German, we can find a German person who speaks Polish, and we can connect the whole world, great.

That's got to get much faster, and we have to connect the world. If we could talk to each other like this, this is where we want to go. This is what I want to do. I want this multi-language, Star Trek had it right. The universal translator built into our ears is the correct technology. Every interface you look at is in your technology, localised to your context. That's the vision. That's what I'm working on.

[00:18:06] Nathan Wrigley: You were talking about a workflow there. The AI presumably is significantly quicker, because if you were to be employing humans to do this, presumably you'd send an email with the text, wait a little while, maybe a day, or a week, or whatever it may be, and then it comes back, and then you've got to then copy and paste that into the blog post. And I realise that there are WordPress plugins out there that will handle that more or less seamlessly on the back end of your website as well.

But I'm guessing that AI can handle, let's say you've got a, I don't know, 1500 word article or something, I'm going to guess, I actually don't know, but I'm guessing that it could translate that in moments. Be it with all the caveats of how accurate it is and what have you. It's a fairly straightforward amount of time, so that you could see the results in seconds. Is that accurate?

[00:18:49] Matthias Pupillo: Yeah, as a software architect, I can no longer abide by anything longer than three seconds. So our average response time is 1.2 seconds, over at FluentC, and then we are trying to see if we can get that down. That seems too slow to me. And so 1.2 seconds for a whole article.

[00:19:05] Nathan Wrigley: Can you translate multiple languages simultaneously? Maybe on the FluentC backend, it's actually queuing them and doing them one at a time. But would I be able to, for example, say, okay, my target audience is the Chinese market, the Japanese market, the Philippines market, throw in, I don't know, Vietnamese and a bunch of other things, you know, languages that I'm really not that familiar with. Can I get the same result? 1.2 seconds later or thereabouts, they will all be taken care of and ready to go.

[00:19:30] Matthias Pupillo: Yeah.

[00:19:31] Nathan Wrigley: It's phenomenal.

[00:19:32] Matthias Pupillo: Yeah, we built a multithreaded. We have different channels for each language, and basically you can hit 140 languages, don't do it, you don't need some of these languages. Some of these are like, we're thinking about adding Klingon and Kardashian, we're talking about mythical languages. If you'd like to speak Elfish from Lord of the Rings, we're working on that too. We do parallel processing. So we handle all of them in about 1.2 seconds. So in about one second, two seconds, you'll be able to have all 40 languages, five languages, downloaded to your copy of WordPress.

[00:19:59] Nathan Wrigley: You mentioned that ChatGPT, which is the one I think most people are familiar with, you mentioned that that is not quite as robust for the language translation. What is the difference then between the one that you are using? What is that one called, and how is that different? Is it just purely built to do the job of translating one language to another?

[00:20:17] Matthias Pupillo: Yeah, so the regular ChatGPT, the Llama, they're only fed documents in certain languages. And they can read, they're fed French documents, it's all about access to data. This is why we have an accidental bias in AI. We're only feeding it English content and, you know, we'll say Western languages because that's all we have access to.

We have very limited documentation written in Swahili. There are very few books. There are very few books in Hebrew. The Arabic books do not have the wealth of digital knowledge. There are so many books in Arabic that are not digital. They're handwritten books, they're handwritten things from historical precedents. But every book written by Charles Dickens is online. Almost everything written in the King's English, every bit of Shakespeare.

But some of these other cultures do not have the digital free access for these AI companies to ingest. And their models, their tokenisation, their transformers, all of that stuff on their side is not designed to go from token to language, it's designed to go from token to token. So you need a specific large language model, and a neural net just tied to multilanguage. So Google Translate, DeepL, AWS Translate, those are the big players in the game. And then what we've done is we've built a layer on top of them. And we've built the FluentC LLM to be context driven.

So instead of translating one word, we're sending in FluentC context. So because we're connected to your WordPress site, we know all of your pages. We know all of your about. We know your tagline. We know your title. We know all of that stuff about your site, and we can include that, and we process the context to make sure we have the context right.

And then we do a scoring algorithm across the big cloud translation engines to really drive a good output. So we'll know if it's a bad translation. And then, you know, we've just recently launched an edit capability, so if you do notice, you can just go in and hit edit, and change. But yeah, the ChatGPTs do terrible translations, and it's just not designed for it.

[00:22:12] Nathan Wrigley: So when this podcast episode airs, I will use an AI, and we're both speaking in English, and it's pretty good with the UK accent that I have, and I have no doubt that it will be excellent on the accent that you have. So I will feed the audio into that, and within a minute, less than a minute, it will have transcribed that audio. And it will have done, to my eye, about 95, somewhere between 95 and 97% accurate. There's always little bits, for example, it'll just mishear the slur between one word and another, and so it'll misunderstand that word, but it'll do a pretty good job.

The thing about that is, it's just trying to do one word at a time, you know, discreetly. What's that word? What's that word? What's that word? But then if I was to get that translated, let's say, into another language, French, German, whatever we pick. When I've had the opportunity live to use Google Translate, it's kind of interesting watching that happen because on the screen as I'm saying English, I'll see the Italian words being printed out, and then there'll be like a little pause, and things sometimes get deleted in real time. And so somehow it's thinking, okay, that word wasn't what I thought it was.

So what I'm trying to say is, when it's translating, it's not taking one word strictly at a time, because that would just be junk. We know that the order of French sentences, for example, is entirely different. They put words before other words and so on. The order in English is completely different to the order in French. Presumably you have to take that into account. So it's not just, if we were to watch this happening, it's not linear. It must take the whole sentence as a whole, and then have a guess, and then rewrite its guess. How does that all work?

[00:23:49] Matthias Pupillo: Yeah, and it works by, the more you give it, the better it is. So a one word translation, turkey, meat, country, in English. But if you give it a paragraph, and you start talking about a city in Turkey, and you start talking about a neighborhood, and you give it context. You have to have context of everything else you're talking about.

A word, a phrase, you're at a bar versus you're at church. You're at your doctor's office versus just walking down the street. Those are contextual elements you have to give to those models so they know who you're talking to. If you put relationships between two people, a producer and a customer, a transaction. Or a mother and a daughter. Those are different contexts, and they're going to speak differently to each other. And you have to feed all of that in.

That's where pre-processing translations is a really important thing. The Google Translate on Chrome does a great job, it just doesn't have all the context. But the context of translations is key. Where we're talking, why we're talking, when we're talking, those are all different things in every language.

[00:24:51] Nathan Wrigley: So, do you have a plugin which is linking up to your SaaS backend to do this? And how does that interface with, I don't know, let's say the block editor. How do I, for example, if I created just a post, or a page, or something like that, how does it all look? Do you have a version on the repo, or is this just a premium thing? How does it work?

[00:25:10] Matthias Pupillo: Oh yeah, the FluentC plugin is on wordpress.org, and that was a big challenge for me. Coming back to the community, I was unaware that there were standards, and that took a few months. I didn't know comments had to end in a period. That was a long-term feedback in my first publication, I'd go a week and then I'd have comments wrong. It's like, okay then, I don't think that's critical to the app.

But the FluentC plugin works in the background. Every time you post or publish anything, we pick it up, and then on that traffic we then store the translation locally to your copy of WordPress without object duplication.

The other thing that, being in WordPress so long, WPML and Polylang have been running the game for, I don't know, since the beginning. And the object duplication was always a problem to me. I can't grow WordPress to enterprise scale if I have a German version of the page and an English version of the page, I can't integrate that content. If I have an e-commerce flow, we talked to some people, and I have a backend not in WordPress, and I'm feeding WordPress and Woo in my front end, I can't have five copies of the same product. I can't have object duplication. I need product number seven, I need all my backend systems to go to number seven, I can't have a different order ID and things like that.

And so we really built the plugin to solve that problem. And the FluentC plugin, it's on wordpress.org, and you just download it, install it, sign up, pick your languages. We're giving away a free language still, so there's one free language out of the gate, and then you can add and subscribe to more of those, though one language is free.

[00:26:39] Nathan Wrigley: So let's say, for example, I've got a product with an ID of seven, and I want that product to have five languages. We don't need to get into which ones, but five languages. Is the product ID for all of those seven? You are saying, does that differ from other solutions that may be out there? And we're not going to get into the competitive differences and what have you but, is there, a difference there?

Some of the options that are available, they might create different IDs because they'll have the German one, and the Spanish one, and what have you. Whereas you are saying, it's all handled in ID of seven. And if that is the case, how does it do the translation? How does it pull out the English text and swap it for the German on the fly?

[00:27:16] Matthias Pupillo: Yes, thankfully the fantastic developers in the community at WordPress has given us hooks. And so as the hooks render the front end, and as they're done, we intercept the hooks, we run some processing on it, and then we store up right before it's viewed. So we have tricked WordPress into thinking there's a German page. We have modified the URL, so it'll be dash de, and then it'll be the product name. And so we have tricked WordPress using hooks and standards.

The block editor is super fun. That was super fun to get that all integrated. Because for most of the cases, we found that most people actually don't speak Japanese. Most English producers of content do not speak Japanese, so they don't want to be bothered by it. And then as you go through that workflow, what always bothers me is anything that gets in the way of publishing. We're independent free thinkers, we're self publishers, right? The whole goal of WordPress is independent publishing, right? It was originally a blogging platform, and it was meant for us to get our word out there and communicate in an internet that didn't support it. But FluentC plugin is designed to be seamless, and if you want to control it, you can. But other than that, you just ignore it. And I hope you just go to my app and hit subscribe, and then you never touch it again.

[00:28:25] Nathan Wrigley: How do you, on the backend, how do you see, are you able to see the German translation? Does it sort of store the German in a meta field somewhere, or?

[00:28:33] Matthias Pupillo: Yeah, actually we just published it yesterday, that you're actually able to, as of yesterday, go in and see all of the translations. We use transients, and so we're using transients in the WordPress database, and it's super fast because you never hit my cloud. Once it comes a way back to you during that initial load, that 1.3 seconds per page thing like that, then it's right from your page, and right from your server. You don't call back. You're not dependent on me after you get the translation, so it's super fast.

As a software architect, I've been doing that for 20 years, performance is key. If we slow down all of WordPress because we want to support more people, that's counterproductive. We can't add billions of new people to our sites and then, oh yeah, everyone's now one and a half, two seconds slower.

[00:29:15] Nathan Wrigley: I don't know how closely you keep your eye on the roadmap for WordPress, but we're in phase three of the Gutenberg project. And at the moment that, broadly speaking, could be categorised as collaboration. There's a whole bunch of other things thrown in there as well, but the idea of having some interface which we can communicate with in real time with other people, and that's yet to happen.

But the fourth phase is all about this topic, is all about multilingual and what have you. And I imagine that there is an opportunity there, but also maybe there's a little bit of trepidation. Because, although the scope for this phase four hasn't been exactly ironed out really, and there's a little bit up in the air because we haven't got there yet. I don't know what your thoughts are, whether or not you are building a business which may end up being completely upended by WordPress Core. Or whether you think actually there's a opportunity for me here because I'll be able to bolt into whatever is built. So that question is, it's not very targeted, but hopefully you've got an intuition. Phase four is coming, it's going to be exactly in the ballpark of what you are doing. So does it offer you an opportunity, or is it something to be worried about?

[00:30:24] Matthias Pupillo: We are looking forward to participating in phase four. Now that I'm actively in the community, I'd love to help with phase four. We are dreaming of a world where you just use FluentC's backend, you don't need to install our plugin, be fantastic. If we could get standardisation among the hooks, the translations, the power to do it and edit it, that would be fantastic. We view all of the phase four talk as a super impactful, important upgrade to WordPress, to make it really global publishing software,

[00:30:55] Nathan Wrigley: So in that scenario, perhaps the intention for you is to pivot away from being a plugin, more to being an API basically. You know, you go to your service in the same way that you do for ChatGPT, for example, and you get a key. And you paste that into some core component of WordPress, which ships with vanilla WordPress, and then your translation has just happened on the fly. That's interesting. So that's a potential direction you are hoping it might go in, right.

[00:31:22] Matthias Pupillo: Yeah, that would be great. If we end up that WordPress does it so well that all of the translation plugins are irrelevant, and now we're competing on API qualities, I'm perfectly fine with that. I'm perfectly fine with building a better mousetrap and helping WordPress. Honestly, I just want the world to get smaller and make this easier.

So I think we're going to do fine in that world. I think we're going to be proactive, I think the developer tools we're coming out with in the next few months, to actually automatically get all of your language files ready to go, and at least one version of translation ready to submit with your plugin, will make the world smaller.

I think having multi-language themes with 1.2 second response time is pretty good, so that theme developers can start to plug in. We think there's still an area around WordPress that'll make it better, and then if WordPress can standardise the way it thinks about multi-language, standardise the control mechanisms. We've had to invent a lot of stuff that, once it's standardises we think it'll be better for everyone. And yes, it will allow more up market entrants, and yes, it will be more open, but that's WordPress.

[00:32:29] Nathan Wrigley: What's the nature of the LLMs? I know that you drew a distinction between the LLMs that you've decided to use and the layer that you've added on top, and the ones that we're all familiar with, ChatGPT and what have you. What I'm meaning by this is that it feels like a lot of money, in many cases, tens of billions of dollars is pointing towards things like ChatGPT. And we know that Google has deep products.

Are we worried about a future where only a few of these AI companies are able to offer services? Simply because they've been the ones that have invested so much, and they've become the defaults. Does anything like that concern you at all? That we're sort of building something where there's going to be a few incumbents, and their AI is going to be so superior to anything else, that we won't have an opportunity to use rivals, because they just won't be worth it.

[00:33:14] Matthias Pupillo: Yeah, that's all around tech though. We have our big six tech firms, they have more money than anyone thought they should have. They have so much power, they have so much control. They could buy all of the competitors in the entire space for less than they lost buying coffee. And that consolidation, that's going to be a real problem.

There almost has to be a WordPress for AI. We have to get an open source AI model that actually is contributed by other people. We have to do, maybe Matt wants to start another thing. And we have to go at this because WordPress and this open source, it serves a real valid purpose. It does keep everyone in check, it does keep everyone in line. The reason it's not $25,000 to run out a basic website is because WordPress exists. Self-publishing, open source tools exist.

If the AI goes private, we'll call it 1980s versions of software. The eighties existed, we've already seen this. We've seen languages, coding languages that were proprietary. Software that's proprietary. We have Java. We know how this goes. We have Objective-C. We have whole languages locked down by a company. If they lock down the AI, we're all not going to be able to use it unless we pay them.

There is not a competitive landscape. We need that openness, we need the WordPress people to really get involved in this because it's going to be out of our control, and it's going to get self consolidated. It's how capitalism works. The market drive to a single winner. It drives unless there are other values than money, and people who see other value, community value, network value, people that actually just want to win and communicate.

Like all of this stuff that we get out of WordPress, all of the joy and happiness. We were so happy, I was just at WordCamp Ottawa. It was such a happy place. We're all just there to learn, and talk, and teach, and do, and be together, and it's so fantastic. And I really love that about WordPress, and we do need that for AI because it is going to get controlled by these mega companies. I mean, Microsoft spent $10 billion, yeah, billion.

[00:35:15] Nathan Wrigley: My understanding is that they're potentially also building a $100 billion data center in the very near future as well. You know, just eye watering amounts of money that the likes of you and I, really it's difficult to understand the levels that these companies are on. And you imagine that, the more that they can pour into it, the more that they pull ahead in the race, and make themselves so indispensable.

And actually that leads me to another, and probably final question. If you are in the technology space, for the last 50 years, it's been a tough thing to keep up because technology changes so fast, but some things don't change too quickly. Like the CSS spec doesn't change all that quickly. So you're building, I don't know, a page builder, you've at least got a bedrock there and you can work on it.

How is this for you, in the AI space, trying to keep up? Because it feels like, you know, you blink and things have changed. From one day to the next, something that was working is no longer working. Something which was cool is no longer cool. Some company that you'd never heard of is now worth a hundred billion dollars, you know. How do you keep up with all of this?

[00:36:18] Matthias Pupillo: Yeah, so we focus on things that I personally, and our company, focus on value. We do not respect this slideware, vaporware version of AI. We have lived through blockchain. We have lived through Web 2.0. I have been doing this for 25 years. I had an AOL disc, I used to use dial up internet.

So we are driving to things that actually create value. And those things we're chasing, duplicating, replicating, incorporating. And we've gotten good at identifying the stuff that's just fluff. And that's going to be hard for new people to come in in tech, that they can't identify it.

But we were here through all of this. Like we have been here since containers, when containerisation was going to change the world. And it sort of did, but it sort of didn't. And it's now just on the tool belt, and it's another button in the servers. But it's not really, it didn't change the world, it didn't solve everything.

[00:37:07] Nathan Wrigley: Yeah, it kind of feels to me that, I really don't know, I think you could almost flip a coin and see whether AI will be used everywhere, or the opposite. You know, people will just get fed up with it and think, actually, do you know what, the human touch is much better. But it does feel like you are on fairly steady ground because the capacity for AI to do the translation job is so profoundly obvious. It's really straightforward. There's a direct line between, I don't know, the amount of time that it takes and the cost, and what have you. It really seems like a really sensible place to be.

We're kind of going to have to knock it on the head because of the amount of time that we've got available for this podcast. But just before we go, would you mind just dropping a few details about where people can find you? That could be, I don't know, a social handle, it could be a website, or an email. What's the best place to find you if people want to talk about translating in WordPress with AI?

[00:37:56] Matthias Pupillo: Yeah, I'm on the Make WordPress Slack. Our website FluentC.ai is our WordPress focus website, F-L-U-E-N-T-C dot A-I, is our WordPress focus website. That's a great place. I'm on LinkedIn. But Slack and wordpress.org are great places to go.

[00:38:13] Nathan Wrigley: Okay. Thank you so much for chatting to me today. I really appreciate it.

[00:38:16] Matthias Pupillo: Thank you.

On the podcast today we have Matthias Pupillo.

Matthias has extensive experience in the technology and creative sectors, and is currently working as the co-founder of FluentC.ai, an AI-powered language technology company. With a background in technology, he's focusing on developing solutions to enhance communication across different languages and platforms. He's been involved with WordPress since its early days around version 1.2, and has a rich history of web design and consulting, having worked on hundreds of WordPress websites. But it's only recently that he's become more engaged in the WordPress community through events like WordCamp Buffalo.

In the podcast today we talk about AI-driven language translations, particularly focusing on Matthias's work with FluentC, which is his translation plugin for WordPress. It supports multithreaded, simultaneous translations of up to 140 languages, enabling your pages and posts to be offered in other languages in just a few moments.

We cover the differences between AI models designed for translation, such as ChatGPT and Llama, which aren't specialised for this task, and how his platform builds a contextual layer above those. He emphasises the importance of context and diverse multilingual data in producing high-quality translations. FluentC's functionality involves local storage of translated content, in an effort to maintain website speed. This is done using native WordPress hooks and URL modifications.

Matthias also offers his thoughts on the ongoing multilingual support phase of the Gutenberg project, and his hopes for FluentC to evolve from a standalone plugin to an API which could be used by WordPress Core.

We get into the broader implications of AI in translation, the need for open-source models to compete in this rapidly evolving space, and the parallels between AI evolution and past trends like blockchain and Web 2.0.

If you're interested in the intersection of AI and WordPress, or are looking to enhance your website's multilingual capabilities, this episode is for you.

Useful links

FluentC website

FluentC plugin

ChatGPT

Llama

Google Translate

DeepL

AWS Translate

WPML plugin

Polylang plugin

Matthias on WordPress.org

11 Sep 2024 2:00pm GMT

Akismet: How to Stop Contact Form Spam on Any Website (99.99% Accuracy)

If you have an unsecured contact form on your website - one that doesn't use any kind of spam-prevention technology - you'll likely get a lot of time-wasting, irrelevant submissions. That's because, without some sort of protection in place, contact forms are simply wide open for malicious actors and bots to submit spam.

There are several ways you can protect a contact form, whether you're using WordPress or not. You can add CAPTCHAs, make contact forms only available for logged‑in users, or add a smart, automated anti‑spam protection tool like Akismet.

Sites that care about the user experience and maximizing conversion rates should almost always choose a solution from that last category - one that stops contact form spam without annoying site visitors.

In this article, we'll go over the most effective ways to stop contact form spam. We'll also discuss why CAPTCHA is no longer the preferred tool for spam protection and show you what you should be using instead. Let's get to it!

The best solutions to stop form spam in 2024

In this section, we'll walk you through the best solutions to stop contact form spam. We'll explain how each solution works, as well as its pros and cons, to help you decide which option to implement for your website.

1. Akismet

Akismet homepage with the text

Over 100 million websites use Akismet to protect against form spam. Once you set up Akismet on your site, it will analyze submissions and determine what is real content and what is spam.

Akismet leverages machine learning to do this. The software has removed over 500 billion pieces of spam from the web. Every time it does this, it gets better at identifying spam. It's gotten so good, in fact, that it boasts an accuracy rating of 99.99%.

The best thing about Akismet is that it doesn't force users to solve puzzles or interact with elements on your site before enabling them to submit a form. Akismet does its work in the background and prevents contact form spam from reaching your inbox.

If you use WordPress, you can easily integrate Akismet with a plugin. Akismet also offers integration options for other content management systems (CMS), including Joomla and Drupal.

You can also integrate Akismet with other types of sites using its API. This makes it a near‑universal solution for spam protection.

2. CAPTCHAs

example of reCAPTCHA on a form

Completely automated public Turing tests (or CAPTCHAs) are tools designed to help block bots from being able to submit forms. CAPTCHAs are everywhere on the web, from login pages to comment sections and contact forms.

There are several types of CAPTCHAs you can use to protect a contact form. Google reCAPTCHA, for example, provides CAPTCHAs with visual puzzles that users need to solve or elements they need to click on to prove they're human. The latest versions of reCAPTCHA don't require interaction, but you're free to choose which option to use.

While CAPTCHAs are popular, they do have a few downsides. We'll explore the cons of using CAPTCHAs later in the post.

3. Honeypot

Using honeypots is a creative way to mitigate contact form spam for a website. This method involves setting up an input field within the form and hiding it from human users in some way (typically using CSS).

Although real visitors won't be able to see the field, they'll still be able to submit forms as usual. Spambots, on the other hand, are typically configured to fill out every field in a form, including honeypots.

This method can help you identify which form submissions come from bots. You can use that information to filter these messages and keep your focus on real submissions.

Although the honeypot approach can be effective, you'll still receive contact form spam, which can clutter your inbox. Plus, you'll need to understand basic CSS to hide a contact form field. If you use a CMS with a contact form plugin, it might not allow you to easily hide elements.

Some spambots are also capable of bypassing honeypot fields. And, you run the risk of real users stumbling into the hidden fields, which can lead you to think their submissions are also spam.

4. Session cookies

As you may know, some websites use session cookies to track your information and activity on their pages. This means you can also use cookies to identify bots due to the way they behave on your site.

Bot activity can be relatively simple to identify. Spambots often go straight for contact forms, fill them out immediately, and attempt to make multiple submissions. In contrast to how real users behave, they're also unlikely to interact with other elements on a site.

You can use this information to block form submissions for sessions that engage in suspicious behavior. But this only works if you're comfortable configuring cookies to detect suspicious behavior.

That process requires you to configure the cookies to flag behavior that you would typically see with spambots. There can be a lot of trial and error involved in this process, and it's arguably a lot more difficult than using an available tool or service to block contact form spam.

Typically, this solution is more common among enterprise websites and businesses that have the technical know‑how to implement advanced security measures. Even then, the results you get might not be worth the trouble when there are out‑of‑the‑box solutions you can use to achieve similar (or even better) results.

5. Email filtering

Most modern email clients offer some type of message filtering functionality. You can use these filters to flag emails from specific addresses or those that contain keywords you associate with spam.

filters and blocked addresses section of Gmail

In general, you shouldn't use email filtering tools to deal with contact form spam unless you get a very low number of messages. For this method to be effective, you need to decide what terms to filter and continue to add new keywords over time.

Flagging the wrong keywords can lead to situations where your email will falsely flag messages from real users. Identifying these false positives will often require you to spend time in your email's spam folder, which is precisely what you want to avoid.

Why CAPTCHA is not the best option

CAPTCHAs are one of the most common forms of spam protection on the web. You can see CAPTCHAs everywhere, but that doesn't mean they're the most effective spam protection method.

There are several reasons why using them may not be the best option:

It's important to note that your experience using CAPTCHAs can vary a lot depending on which service you use. Some CAPTCHAs, like the latest versions of reCAPTCHA, don't require users to solve puzzles or interact with elements on the web. Even so, it's safe to say that CAPTCHAs are becoming outdated.

Instead of using a CAPTCHA, consider a more powerful alternative to the contact form spam problem, like Akismet.

Akismet: the best anti‑spam solution

Most anti-spam tools focus on identifying spam content and bots before they can submit a contact form. Akismet does things differently.

The service uses machine learning to constantly improve its spam detection capabilities. That constant improvement has led to the point where Akismet can boast a 99.99% accuracy rate in detecting spam.

You can choose whether to save spam comments for review or let Akismet discard them immediately.

spam filtering settings in Akismet

Akismet will automatically detect contact form spam and filter it for you. The service also offers a host of other benefits, which include the following:

Keep in mind that if you want to use the Akismet API, you'll probably need to work with a developer to set up a custom integration for your site.

How to integrate Akismet on any website

Akismet offers different integration methods depending on what kind of website you run. If you're using WordPress, you can get Akismet up and running in a matter of minutes.

To start, install and activate the Akismet plugin. Then, Akismet will ask you to select a plan.

Hobbyists can select a Personal plan and pay a fair rate of their choice. Incredibly affordable commercial plans are available for other situations.

pricing plans for Akismet

Once you sign up for a plan, you'll get access to an Akismet API key. Enter that key in WordPress by going to Settings → Akismet Anti‑Spam.

entering your API key in WordPress

Click on Connect with API key and that's it. Akismet will activate and start protecting your site from spam immediately.

Note that if you're using Akismet with WordPress, the plugin integrates with some of the most popular contact form tools. That includes options like Jetpack's form blocks, Contact Form 7, and Gravity Forms.

As we mentioned before, Akismet also offers integrations with other CMSs, including Joomla and Drupal. Those integrations work differently than with WordPress, so you'll need to check the Akismet documentation to set them up.

You also have the option of using the Akismet API to integrate the service with any kind of website or application. This requires some level of development work, but enables you to leverage Akismet's spam detection and protection functionality on any website.

Frequently asked questions

If you still have questions about how to stop spam from website contact forms, this section will answer them.

What is contact form spam?

Contact forms are common targets for spammers and bots. If the form doesn't use some type of security feature, spammers are able to make all kinds of useless and potentially‑harmful submissions through the form. These can include links to other websites, promotions for fraudulent services and products, and automatically‑generated content.

How does contact form spam affect a website?

Contact form spam shouldn't affect your website on the front end, unless the form is open to some kind of attack that can compromise your site's security (like SQL injection).

In most cases, the biggest downside of contact form spam is having to deal with it. This spam can quickly fill up your inbox and make it harder for you to separate the real messages from the fake ones.

Why is Akismet considered the best solution for contact form spam?

Most solutions that focus on stopping contact form spam do so at the expense of the user experience. CAPTCHAs, for instance, force users to solve problems or click on elements before they can submit a form. This can reduce the number of people willing to use the form and can even make them inaccessible to those with disabilities.

Akismet is highly effective in stopping contact form spam, with a detection accuracy rate of 99.99% for spam content. Plus, Akismet doesn't impact the user experience whatsoever, as it works in the background during form submission.

What are honeypot fields, and how do they work?

A honeypot field is an element in a contact form that only bots should be able to engage with. You can create one by using CSS to hide a field in plain sight or through a plugin that will handle this for you. Regular users will skip the hidden field, but spambots won't.

Once the honeypot is set, you can filter all contact form submissions that fill out the field. You may also be able to blocklist the IP addresses that make the submissions, depending on which contact form tool you're using.

How effective is CAPTCHA in preventing spam?

CAPTCHAs are among the most popular solutions for protecting your website from contact form spam. Their popularity makes them a significant target for attackers, who are constantly devising ways to bypass them using automated tools.

It's also not uncommon for CAPTCHAs to flag real users as bots. Overall, CAPTCHAs can be highly effective, but they're not without several downsides.

Can spambots bypass honeypot fields and CAPTCHAs?

Yes, some spambots can bypass honeypot fields and CAPTCHAs. Attackers are constantly trying to bypass form security measures, and that means creating new bots and constantly updating them so they remain effective.

Akismet bypasses this problem by focusing its spam detection tools on the content of the form submissions. The service also learns from each submission, which makes it the most accurate spam detection and prevention tool on the market.

Can Akismet protect against all types of spam?

Spammers and bots tend to target any public form on websites. Akismet can protect all the forms on your site by monitoring submissions. It does this without you having to set up individual protection for each form, as is the case with CAPTCHAs.

Where can I learn more about Akismet?

You can visit the Akismet features page to learn more about how its spam protection functionality works. If you're ready to start using Akismet on your website, check out the available plans.

Stop contact form spam using Akismet

If you're spending time dealing with contact form spam, you may be missing out on submissions from real users. Using tools that enable you to stop form spam will free up your time for other tasks. Moreover, with the right tools, it's relatively easy to stop contact form spam.

There are several ways to stop contact form spam on WordPress and other platforms.. Akismet is the leading option since it doesn't impede navigation for real users. It's also easy to implement (particularly if you're using WordPress), and it has a 99.99% rate of accuracy for spam detection.

You can use Akismet for free on your personal website or choose from affordable plans for commercial sites, where spam protection becomes even more essential. Start using Akismet today!

11 Sep 2024 1:00pm GMT

Do The Woo Community: A Look at Asynchronous Communication with Adam and Emma

Episode Transcript

Adam:
This is Woo Biz Chat. Hi, my name is Adam Weeks, and this is…

Emma:
Hi, I'm Emma.

Adam:
Hey, Emma! Oh my goodness, it's been a little while. We're getting to catch up, and have we got a show for you?

Emma:
Oh, do we?

Adam:
Yes, yes, yes! This is Woo Biz Chat. This conversation came about because I was thinking of this topic, and I don't know that we've really talked about it much. However, I have a new contract, and I've been working with 10up. 10up is one of the biggest agencies in WordPress, and they've grown so much because they do certain things really well. I've been so impressed with the team.

One of the things I hear repeatedly is about that "last 10%." That's really what gets them over the finish line with some of these big enterprise projects. It's been a lot of fun getting to know this talented team. One of the people on this team, her name is Haley, and she is hilarious. She's a project manager and very good at communicating.

In fact, this morning I hopped on Slack, as you do, and she had a very succinct but thorough rundown of an event we needed to be updated on. She did it in a way that was clear, funny, interesting, and timely. So, let's talk about a few of those things we're going to discuss in this episode. If you're curious about asynchronous communication, this might be something unique-not to commerce so much-but in Woo, I imagine we have to work asynchronously. We're in our Slack, we're in our email, and we need to have a good foundation and a good way to communicate asynchronously. We're going to dive into all those topics.

Before we start, is it okay to swear? When can you be funny? When can you not? All these things-so that's what we're going to get into. Also, Emma, one of the reasons we picked this topic is that you are very good at it, and I'm going to learn from you today.

Emma:
Except for all of…

Adam:
Let's start us off. Tell me your general thoughts on asynchronous communication. Do you have a philosophy? What are your thoughts from a high level?

Emma:
That's such a loaded question! It's like, how do you pack everything into one nicely typed-out message as a response?

Adam:
It's hard, right?

Emma:
It really is. Practice doesn't make perfect, but it gets close. And everybody's different. One thing we can start off with is that there are so many different audiences, and people know you at different levels, so everyone will interpret communication differently. But just to quickly start off, for people who don't know-what even is async communication? Basically, it's communication where the participants don't need to interact in real-time. It doesn't have to be face-to-face. It can be messages or information exchanged on Slack, Messenger, Teams, project management tools, emails, etc.

This is different from synchronous communication, which is what we're doing now-calls, meetings, phone calls, live chat, stuff like that. Asynchronous communication is when a message is sent, and you deal with it when you can. So, what are the best ways to deal with it from there?

Adam:
Alright, asynchronous communication. We use it a lot in this industry because of the nature of the work. Time zones are another reason for async communication. Your day might not overlap with your coworkers or clients completely. It can be helpful to get something moving, and then when you go to sleep, someone else is waking up and takes it from there.

Alright, I'm going to ask you a few different questions. You're good at this! What is one thing you try to do when using async communication? What's a guiding principle for you?

Emma:
It's actually kind of funny because we communicate like this a lot due to our time zones. Yesterday, I sent you a message before bed like, "Here, check out these show notes," and then I checked it after your full day. But it wasn't always that easy. Well, with you, yes, but with other people, maybe not as easy.

I stand by this: over-communicating is never a bad thing when it comes to async communication, especially if the person has never met you before. Whether it's a quick "huddle" on Slack or Zoom, if someone's never put a tone or voice behind your words, they might interpret it in many different ways. So, clarity and context are essential. Sometimes, I reread a message I sent and think, "I know what that means, but maybe the person reading it doesn't." Over-communicating is never really over-communicating.

Adam:
You are never penalized for over-communicating. The person may be annoyed, but that's okay. They can skim it.

Emma:
Exactly. One person might say, "I already know all this; why did you write so much?" But maybe 99 other people reading it will go, "Oh, it all makes sense now. I don't have to ask any follow-up questions." Amazing!

Adam:
It's like taking notes in a meeting. You think, "Oh, I'll remember that." Nope, I won't remember that.

Emma:
No way.

Adam:
My brain doesn't work that well.

Emma:
My brain ain't braining.

Adam:
My brain ain't braining! And sometimes, you're taking notes for someone who wasn't at the meeting. If someone gets hit by a bus-this sounds terrible-and they weren't there…

Emma:
They'll have the notes communicated async. Just kidding! Because they're…dead. No, wait, sorry. Too far.

Adam:
Asynchronous communication. What was I saying?

Emma:
You were talking about taking notes for someone else.

Adam:
Right, your notes need to stand on their own for someone who doesn't have any context. You won't be penalized for over-communicating, and the person you're communicating with might also be forgetful. You won't be penalized for clarity.

Emma:
A hundred percent. But in addition, I'd recommend-depending on the type of communication-if you can, jump on a short call. Putting a voice behind the words they'll read on a screen helps, especially if it's the first time you're giving feedback. You don't have to do this every time, but I recently did this at work. I was in a call with some team leads, hosting a meeting. I can't remember all the details, but at the end, they asked for feedback.

I'd never given this person feedback in written form before, and I made sure there was enough context, examples, and action points in the message. But then I thought, "You could read this the wrong way." So I said, "Hey, can you hop on a quick call? I'll send this feedback afterward." It was just a quick Slack huddle. After that, the next time I sent feedback, it was clear, and I didn't need to overuse emojis.

Sure! Here's the continuation of the corrected transcript:


Adam:
Wait, wait…

Emma:
You couldn't see me, but I also did cat claws, like "rawr."

Adam:
Everyone's imagining that now.

Emma:
I thought, "She asked for feedback, so let me jump on a quick call to give it to her." After that, when I sent the written feedback, it was very clear. She could now imagine my personality behind the words, without me having to overuse emojis.

Adam:
Oh, all the emojis.

Emma:
Yeah.

Adam:
So you bring up a good point. We're talking about asynchronous communication and how to use it, but there's also the point of when not to use it. I've come up with this framework: information is shared quite well asynchronously-whether through emails or Slack-but if you're trying to connect with someone, solve a problem, or if there's some emotional element involved, it's better to hop on a quick Zoom call, or use Slack's huddle feature. Sometimes something that might take back-and-forth exchanges in Slack-or even be misunderstood-can be solved in two minutes over a call. Don't try to solve problems over a text message.

Emma:
I agree. If there's no quick decision being made or communication is being lost due to a lack of context, then move to another method. Whether it's a call, a huddle, or a voice note-even a quick voice recording can help bridge the gap.

Adam:
Oh yeah, voice notes are great. You can record a quick message. Another thing I don't use enough is video recording-where you record your screen and say, "Hey, this is what I'm seeing." They can hear your voice and see exactly what you're seeing, which can be super helpful. So, there are lots of ways to handle async communication.

Alright, so we briefly talked about emojis-emoticons? I don't know the difference. How do you use them? When do you find them helpful, or when are they annoying?

Emma:
One of the things I love about working with Hosting or switching to different Slack groups is the custom emojis they have. They've got all these little dancing characters. When I move to WordPress Slack, or back to our group, I'm like, "Where's the dancing cookie?" or "Where's the cat spinning on a Roomba?"

I also have a "Hall of Fame" of my own custom emojis, like Emma smirking, Emma flabbergasted, Emma disappointed. And I'm sad when I go to Messenger or another platform that doesn't let me use them. Sometimes, all you need is an emoji to express yourself.

Adam:
Okay, wait-Bob, if you're listening, we need to get all of Emma's custom emojis on Slack. I want them all!

Emma:
Yeah, I think I can make them myself. We'll have to see. But we kind of have this weird thing where the original smiley face-the one with no teeth-has turned into this passive-aggressive emoji for some reason.

Adam:
The thumbs-up emoji-is that okay?

Emma:
Oh yeah, thumbs-up is okay. We kind of use it as the end of a conversation, like, "This is done. No need to continue." It's like when you're dating and don't know how to hang up the phone-you hang up first, no, you hang up first. Someone sends a thumbs-up, and that's it. It's all good.

Adam:
It's all Gucci! What about the hands-raised emoji? You know, the two hands in the air?

Emma:
Yeah, we use that one a lot, along with the "grinning" emoji, which is like, "Oops, we've got to work on that now." And of course, the sweating smile when something doesn't go as planned. The shrug emoji is also a big one.

Adam:
I love the shrug emoji.

Emma:
Oh, totally. It adds a little bit of emotion to your communication. Sometimes, just a simple emoji makes the message more relatable-especially if you're trying to send kudos or hype someone up. But don't go overboard with emojis either, because then it can distract from the actual message.

Adam:
Too much emotion, not enough content.

Emma:
Exactly. And on that note, there are some emojis that don't age well or might accidentally offend someone. Sometimes an emoji or symbol might become controversial or inappropriate, and then someone calls you out on it. If it wasn't malicious, just delete it and learn from it. There are boundaries to emoji usage, but they can be a fun and helpful tool.

Adam:
So, the takeaway here is: use emojis, but don't overdo it. They're helpful in adding some humanity to otherwise black-and-white text. You can only use so many exclamation marks. Do you use exclamation marks a lot to add emphasis?

Emma:
I have this weird thing against exclamation marks. Stop shouting at me! Nobody's that excited. I tend to avoid using too many. However, I've caught myself doing it when I'm really excited. Someone once gave me feedback about that-because I tend to end messages with double periods or double stops, like ".." instead of a single period or an ellipsis. They said that it could come across as unhappy or cold if I didn't add more information or an emoji. So, I switched that up!

Adam:
Communication evolves, right?

Emma:
Yep, if you're trying to ensure people know you're happy or positive, throw in a smiley face or something.

Adam:
That's a great point-feedback can be really helpful for improving how you communicate. So, what we take away from this is: give feedback on how someone's async communication is going, and assume the best in them, especially when you don't hear back.

When someone doesn't respond after you've put effort into your message-there are crickets-how do you handle that situation?

Emma:
Yeah, that happens. Especially because my team spans 10 time zones, there's no way everyone is online at the same time. So, one thing we do is react to messages with an emoji once we've read it or acted on it. Sometimes that gets old, but it becomes second nature-react with a fun emoji so that people know you've seen the message.

Also, I'm all for tagging people. Not aggressively, but if 24 hours have passed and you know they've been online, tag them again. Ping them until they see it! It's easy to miss a message in Slack or Teams, especially if it pops up briefly and you lose it.

Adam:
Exactly. Sometimes you see a message, but then it disappears, and you can't find it again.

Emma:
Right, or if you accidentally open it on your phone, you're kind of out of luck. So don't feel bad about tagging people-ping them a few times. From my perspective, I've never gotten mad at someone for tagging me multiple times. If I missed it, I appreciate the reminder. You could also use a loading emoji, like "I'm working on it, but give me a minute."

Adam:
So, aggressively tagging-got it. Another thing I've found helpful is to avoid asking seven questions in one message. If someone knows the answer to six of them but not the seventh, they might delay responding altogether. Break it down to one or two key questions.

Here's the continuation of the transcript with corrections:


Adam:
So, break it down into one or two key questions, and when you get that response, they can address those first. When you overload someone with too many questions, they're more likely to ghost you-not because they mean to, but because it feels overwhelming.

Also, when you do get a response, you might see a little checkmark or a "done," or they might write "received" or "great question, let me follow up." That's something I try to do more of-if someone asks me something complex and I don't have all the answers right away, I at least let them know I'm thinking about it or working on it. It helps keep the conversation moving forward.

Emma:
Yeah, that's important. And if your company already has established procedures, emojis can be helpful for tracking communication, too. You can use a "loading" emoji, the eyes emoji, or a "working on it" emoji to show progress, and then update it when you're done.

I also want to touch on the formatting of async communication. If you need to ask more than three questions, it can get confusing. If you have a multi-part conversation, I recommend sending a separate post for each topic so they can each have their own dedicated thread. That way, less information gets lost compared to a giant message where everything is lumped together. Otherwise, you might end up having to schedule a call because there's too much going on in one message.

Adam:
That's a great tip. Another thing I picked up from my friend Haley at 10up is the importance of consistency and rhythm in communication. If you're managing a project and have a weekly meeting or update, try to send your agenda or summary at the same time every week. People appreciate predictability in communication-it helps build trust and reduces surprises.

Another good tip Haley mentioned was drafting your message in Google Docs and getting peer review before you send it out. What's your take on that?

Emma:
I think it depends on the message, but yeah, I definitely agree with using Google Docs for longer or more formal messages. I'm more comfortable writing in Google Docs because I have Grammarly and other tools to help catch mistakes. Also, if it's something important or if I need input from others, I'll ask someone to review it before sending it.

Sometimes, I'll ask for feedback like, "Does this have enough context? Does this sound like me? Do I sound upset or annoyed?" Having another set of eyes on a message can help make sure it's clear and professional before you hit send.

Adam:
Yeah, I love Grammarly Pro for the win! It's not just about catching grammar mistakes-it's also about ensuring that the message aligns with what you want to convey. Especially with important messages or anything client-facing, it's good to slow down and have someone else review it. Don't rush to publish it-take a beat, have someone look it over, and make sure everything's in order.

And one trick I've learned is to set expectations upfront. Instead of saying, "When you have a minute, can you look at this?" say, "I need to send this out by 7 PM; would you mind reviewing it before then?" That way, they know how urgent it is, and if they can't get to it in time, you're still able to send it by the deadline.

Emma:
Exactly! And it helps to be clear about expectations, especially in different time zones. Also, if something is optional for some people but mandatory for others, it's important to tag those people directly so they know they need to review it.

We had an example today on my team where someone sent a message with a summary and action points, and then said, "You have until the end of the day to challenge this, or I'm proceeding." That's a great way to set a clear timeline and let people know what the plan is.

Adam:
That's a great way to handle it-give a clear deadline for feedback and move forward if no one challenges it. There's a phrase I like: "It's unkind to be unclear." Sometimes we try to be too nice, saying, "If you have time," or "whatever works for you," but in the end, it just makes things more confusing. Being direct is better.

Emma:
I agree! It's like when I speak, I tend to say, "Maybe, possibly, kind of…" but in messages, I'm much more direct-"Do this" or "This needs to happen." It's about clarity and getting things done.

Adam:
Yeah, it's unkind to be unclear. You want to be kind and polite, but also clear. It's a balance-don't leave people guessing, but also don't be overly harsh. And if you're giving people a timeline, tell them when you need something done, and if it's okay if they don't respond, let them know that too.

Emma:
Exactly. And when you're writing these messages, also be aware of the language you use, especially when it comes to different cultures and inclusivity. You don't want to unintentionally offend someone, so choose your words carefully. And if you do make a mistake, apologize and learn from it.

Adam:
Yes, that's a great point-be mindful of your audience and the words you choose. And if you mess up, own it and apologize. We're all learning.

Alright, we've covered a lot, but we still have one more sensitive topic to discuss: swearing. Is it okay to swear? When is it okay, and when is it not okay? What's your take on dropping swear words in async communication?

Emma:
Personally, I have a bit of a potty mouth, so I'm used to swearing in my day-to-day life. But in async communication, it depends on the company culture. At Hostinger, for example, it's common for people to drop the occasional F-bomb internally, but I wouldn't swear in a message to someone I just met or on their first day.

I think swearing is something that comes with familiarity-it's more about knowing your audience. If it's internal and you have a good relationship with the person, swearing might be fine. But for external clients or more formal situations, it's definitely a no-go.

Adam:
Yeah, I agree. Don't be the first to swear. If you're building a relationship or working with a client, keep it professional. There's a time and place for it, and you want to be sure it's appropriate before you start using swear words.

At the same time, you want to be authentic. So if you're comfortable swearing in certain contexts and it feels natural, it's okay to do that-but be mindful of the situation.

Emma:
Exactly. Be yourself, but be cautious. And remember, in async communication, everything can be screenshot and shared. So, if you're swearing in Slack or anywhere else, be aware that it could end up somewhere you didn't intend.

Adam:
That's a great point. Always assume your message could be shared, even in private channels or DMs. If you wouldn't want your message to be forwarded, don't send it.

Another thing I try to do in async messages is start by being human. It's easy to get straight to the point in async communication, but it's nice to start with a "Hey, how are you?" or "Hope your week is going well" before diving into the business stuff.

Emma:
I agree! My greetings change depending on my energy levels. Sometimes it's "Hey," sometimes it's "Hello!" with lots of o's, or even a dancing cactus emoji. But I always try to start with a personal touch because we're not just talking to robots.

You should ask how someone's doing before diving into work, especially if you haven't spoken to them in a while. Just like in person, you don't walk up to someone and immediately ask them for a status update. Start with a greeting, then get into the conversation.

Adam:
Exactly. It helps build rapport and makes the conversation feel more human. It also shows that you care about the other person beyond just the task at hand. Any final thoughts as we wrap up?

Emma:
I had one, but it's gone now. My brain isn't braining anymore!

Adam:
The best part is you can tell me later-async communication!

Emma:
Yes, exactly! I'll ping you later. But seriously, if anyone listening has questions or specific scenarios where they want help improving their async communication, feel free to send me a message. I love helping with that kind of stuff!

Adam:
Absolutely! And if you, the listeners, have any tips or strategies you use for async communication that we haven't covered, please let us know. We'd love to hear from you.

Emma:
Yes, and if you have any other topics you want to discuss with us, we'd be more than happy to have you on the show. We can talk, and, you know, shoot the poo-uh, I mean, shoot the shit.

Adam:
And that is a sign that we're wrapping up this episode of Woo Biz Chat!

Emma:
This is why Emma doesn't close the show. Goodbye, and thanks to all our listeners!

Airwallex

Airwallex: With Airwallex merchants are no longer forced to convert their foreign incoming payments into their home market currencies and they can use the funds to pay suppliers internationally.

Omnisend: Whether it's for integration into your Woo product, or building sites for clients, Omnisend is the solution for email and SMS marketing with their CRM solution for WooCommerce shops and your own website.

In this episode of Woo BizChat, hosts Adam Weeks and Emma Young dive into the world of asynchronous communication, sharing insights on how to effectively communicate across different time zones and platforms.

They explore the do's and don'ts of async communication, the importance of over-communicating, using emojis and tone to convey clarity, and when to switch to a real-time conversation.

Adam and Emma also tackle the tricky topic of swearing in professional contexts, the value of getting feedback, and how to build rapport while keeping communication clear and human.

Takeaways

Over-communicating is better than under-communicating: In asynchronous communication, providing thorough context is essential, especially if the person hasn't met you in person or doesn't know your communication style. Clear, detailed messages help avoid misunderstandings.

Use emojis strategically: Emojis can add warmth and tone to otherwise cold, text-based communication. However, don't overdo it-use them to enhance clarity and express emotions without distracting from the message.

Break up complex messages: When you need to ask multiple questions or cover several topics, break your message into separate posts or threads to keep discussions organized and avoid overwhelming the recipient.

Timing and consistency matter: Whether it's a recurring meeting agenda or an important message, being consistent with when and how you communicate helps establish predictability and reliability in your workflow.

When to switch to real-time communication: If a conversation becomes too complex or emotional, it's often best to switch from async to synchronous communication. A quick Zoom call or Slack huddle can save time and prevent misunderstandings.

Be mindful of your audience: Different cultures and communication styles may require adjusting your approach. Always be respectful and considerate, especially when using acronyms, jargon, or informal language.

Feedback is key: Regularly ask for feedback on your communication style to improve. It helps you ensure that your messages are clear and interpreted as intended.

Set expectations clearly: Don't be afraid to set clear deadlines and expectations in your messages. It's unkind to be unclear-people appreciate knowing when something is due or when to take action.

Use peer reviews for important messages: When sending out important or client-facing communication, consider drafting in a tool like Google Docs and getting feedback from peers before hitting send.

Know when it's okay to swear: Swearing in async communication depends on the company culture and your relationship with the person you're communicating with. Keep it professional, especially in client-facing conversations, and avoid being the first to swear.


11 Sep 2024 9:38am GMT

HeroPress: How WordPress and My Work Help Me Stay on Board During the War – Як WordPress та робота допомагають мені залишатись на плаву під час війни? 

Here is Lana reading her own story aloud.

Це есе також доступно українською.

My name is Lana Miro, shortened for Svitlana. I'm a Partnerships Manager at Crocoblock. This article is my personal story about how WordPress and my work have been helping me stay on board during the war in Ukraine.

Brief Introduction

I'm 28 years old, born and raised in Mykolaiv, Ukraine. It's a peaceful, small city (before the war, about 400,000 people lived here). I never thought about moving because travelling and exploring other cities for short periods was enough for me. Mykolaiv was always my comfort zone, where I felt safe.

This city provides me with a sense of peace - the river, the parks… the river - yes, I'm a fan of water. 🌊

My Introduction to WordPress

I began my journey with WordPress in 2017 when I started an internship at TemplateMonster. That's when I discovered this incredible platform that captivated me with its scope and possibilities.

At TemplateMonster, I worked as a Partnerships Manager. At that time, the company's niche was templates for various CMS platforms. So, I'm well-acquainted with all of WordPress's competitors. 😄

During my three years with the company, I realized that WordPress was the largest and most interesting CMS for me.

Why?

In 2020, during the Covid pandemic, I started experiencing issues with my back and mental health, so I decided to take a one-year break. I left the project and rejoined another Holding project a year later - Crocoblock.

Crocoblock was a breath of fresh air for me because of its amazing community and cool plugins that I wanted to work with.

⚡My main tasks involved finding partners for collaboration, organizing events, and more. I've described partnerships in more detail in my free guide - WordPress Partnerships Basics.

Invasion: How to Work?

The war with Russia has been ongoing since 2014, so the Russian invasion in 2022 wasn't a surprise to us. However, what was surprising - that bombs, missiles, and artillery could be used with such intensity in the 21st century.

For the first two weeks, we were paralyzed. 😔

The beginning

The first two weeks of the war were a real shock. We were all paralyzed, but the Crocoblock team quickly came together, creating an operational chat to support each other. This was a time when words, actions, and even just being present in the chat meant so much.💙

For example, one of our employees immediately went to the army, so we collected money, and our developers bought everything he needed to start.

I checked my work email on the second day of the escalation. Lying in the basement, with the internet barely reaching, I decided, "I'm relatively safe, so I can respond to partners." I reviewed critical messages, and let them know that we were okay and would respond as soon as we adapted.

A few days later, we decided to write a blog post to let the Community know we were okay and to explain what was happening. 😥

After two weeks of lying in the basement (yes, my family of nine spent two weeks in the basement, occasionally sleeping in the corridor or bathroom for safety), a bomb was dropped near our street, and that became a critical moment for our family.

By a majority vote, we decided to move to the western part of our country.

Adaptation period

Once we were safe, I was able to start working at 100% (okay, maybe 80%, as 20% of me was still in shock 😣). Of course, the news, conditions, and stress affected me, but work helped me get back into a routine and begin to adapt.

Work became my lifeline.

It brought me back to life, giving me a sense of stability when everything around me was falling apart. We recorded a video message for our clients, which was an important step not only for synchronization but also for my personal recovery.

Not to mention the numerous words of support we received afterward.

We once again realized that Crocoblock clients are the best.💚

Part of the team immediately moved to safer cities or went abroad. But some stayed in Mykolaiv, and Anna, our CEO, was in an occupied city - Kherson. But that's her story. I was incredibly happy when she finally left the occupation, and we exhaled in relief.

After three months (which felt like a year), my husband and I decided to move closer to Mykolaiv to be near his parents. It was safe there, but due to the constant changes, my depression reached its peak.

Fortunately, part of Kherson was liberated, and Mykolaiv was being shelled less frequently, so we decided to return home. That's when I started treatment with a psychiatrist. She helped stabilize my condition and bring me back.⌛

💯 2022 was the hardest year for me and my family, but the ability to work and be part of the WordPress community helped me Just Continue. At the end of the year, I decided to thank everyone who supported me, asked how I was doing, joked, and was kind to me in a post on Medium.

Team changes

Of course, the war impacted our team, and I immediately noticed how management changed its approach to focus on caring for each team member.

🙌 We started having training sessions based on the team's requests (e.g., anxiety management), management helped with healing supplies (since there are blackouts or Internet issues in Ukraine), and relocation if needed.

During the war, our HR team introduced the IDP (Individual Development Plan), which allows you to outline your development for the year, focus, and receive better feedback. This helped me during my depression. The war brought changes, and I became more anxious, chaotic and found it hard to focus.

👩‍💻 The constant support from my manager was also crucial. My manager is Anna, our CEO. I regularly receive feedback from her, which is often needed to work better. She also supports my initiatives and ideas, which is incredibly motivating.

I try to implement her skills in managing my team of three wonderful women - Victoria, Community Manager; Nikki, Content Marketer; and Dashel, our blog Editor. 🙏

Crocoblock Team

Today

I'm writing this article on August 26, during one of the biggest attacks by Russia (just one day after our Independence Day celebration). More than 100 missiles and drones were launched this morning.

We woke up at 7:30 a.m. and saw the attack begin. Thanks to monitoring channels, we can continue to live and hide in shelters when they announce. I had breakfast, did some exercise, and started working with sirens in the background.

Next came the emergency electricity offs, as one of Russia's goals is to break our energy system and plunge our country and people into chaos. But besides anger and hatred, I no longer feel anything for them. We are prepared; we have power banks, EcoFlows, water reserves, and are ready to work full force so our country can survive.

💪 We are currently actively preparing for our 2nd WordPress Agency Summit in September, and this helps me feel like I can be useful to the community. Join us; it's free.

We're also trying to participate in more WordPress events. For example, this year we sponsored WordCamp Europe 2024, and we're planning to sponsor a local event in Spain for the first time. 👏

In general, I'm finding my place in the WordPress community, which inspires me with its kindness and support. The first step was my guide on partnerships. Next, I plan to:

Crocoblock Team in an airplane

What Helped Me

My strength comes from the support of my team, family, and the WordPress community. Along with that, therapy, household chores, and even simple joys like cafes or books helped me find inner harmony to continue living.

⭐My top glimmers:

Because only in harmony with myself can I help my country. 💙 💛

Lana's Work Environment

We asked Lana for a view into her development life and this is what she sent!

Lana Miro's Workspace

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


Як WordPress та робота допомагають мені залишатись на плаву під час війни?

Слухайте власну історію Лани вголос.

Мене звати Лана Міро, скорочено від Світлани. Я - партнерський менеджер у Crocoblock. Ця стаття - моя особиста історія про те, як WordPress і робота допомагають мені залишатися на плаву під час війни в Україні.

Короткий вступ

Мені 28 років, я народилась і проживаю у місті Миколаїв, Україна. Це спокійне, не велике місто (до війни, тут проживало близько 400 тис. людей). Я ніколи не задумувалась про переїзд, бо мені було достатньо подорожей і дослідження інших міст на короткий період. А от Миколаїв завжди залишався моєю комфортною зоною, де я почувала себе в безпеці.

Тут є те, що дає мені відчуття спокою - річка, парки… річка - так, я фанат води.🌊

Знайомство з WordPress

Я почала свій шлях з WordPress у 2017 році, коли прийшла на стажування до TemplateMonster. Тоді я відкрила для себе цю неймовірну платформу, яка захопила мене своєю масштабністю і можливостями.

У TemplateMonster, я працювала менеджером з партнерств. На той період ніша компанії - це шаблони для різних CMS. Тому я обізнана з усіма конкурентами WordPress. 😀

Протягом 3х років роботи в компанії, я зрозуміла, що WordPress найбільша і найцікавіша для мене CMS.

Чому?

  1. Ком'юніті та кількість людей, які створюють контент про WordPress - величезна!
  2. Різноманітність плагінів, шаблонів
  3. Цікавий і інтуїтивний дашборд

У 2020, під час Covid, я почала більше відчувати проблеми зі спиною і ментальним здоров'ям, тому вирішила зробити паузу на 1 рік. Звільнилась з проекту і поновилась через рік у інший проект холдингу - Crocoblock.

Crocoblock став для мене новим ковтком повітря, бо тут крутезне ком'юніті і класні плагіни, з якими хочеться працювати.

⚡Моїми основними завданнями було пошук партнерів для співпраці, організація заходів, і т.д. Більше про партнерства, я описала у своєму, безкоштовному посібнику - WordPress Partnerships Basics.

Повномасштабна Війна: як працювати?

Війна з росією триває з 2014 року, тому для нас не був сюрпризом наступ росіян 2022. Але сюрпризом було, що у 21 столітті можуть використовуватись бомби, ракети, та артилерія в такій інтенсивності.

Перші 2 тижні ми були паралізовані. 😔

Початок

Перші два тижні війни були справжнім шоком. Ми всі були паралізовані, але команда Crocoblock швидко згуртувалася, створивши оперативний чат для підтримки один одного. Це був час, коли слова, дії і навіть просто присутність у чаті значили дуже багато.💙

(наприклад, наш співробітник одразу пішов воювати, тому ми зібрали гроші і наші розробники купили все що йому потрібно для початку).

На робочу пошту я зайшла десь на другий день ескалації. Лежачи в підвалі, інтернет трошки дотягував, тому я вирішила - "Я відносно в безпеці, отже можу відповісти партнерам :D". Я оглянула критичні повідомлення, дала знати що у нас все окей і відповімо якомога скоріше як адаптуємось.

Через пару днів, ми вирішили написати блог статтю, щоб дати знати нашим клієнтам та партнерам - ми в порядку і що взагалі відбувається. 😥

Через 2 тижні, лежачи в підвалі (так, 2 тижні моя сім'я з 9 людей провела в підвалі, періодично сплячи в коридорі або ванній кімнаті дому для безпеки) недалеко від нашої вулиці скинули бомбу і це стало критичним моментом для нашої сім'і. І методом голосування - ми виїхали на захід нашої країни.

Період адаптації

Будучи в безпеці, я змогла почати працювати на всі 100 (ну окей, на 80%, 20% мене ще досі було шокована😣). Звичайно, новини, умови і стан стресу вплинули, але робота допомогла повернутись в режим і почати адаптуватись.

Робота стала моїм рятівним колом. Вона повернула мене до життя, дала мені відчуття стабільності, коли все навколо руйнувалося. Ми записали відеозвернення для наших клієнтів, що стало важливим кроком не лише для синхронізації, але й для мого особистого відновлення.

Не кажучи вже про численну кількість слів підтримки, яку ми отримали потім.

Ми ще раз зрозуміли - Crocoblock клієнти - найкращі.💚

Частина команди одразу переїхала в безпечніші міста або виїхала закордон. Але дехто залишався в Миколаєві, а Анна - наша CEO взагалі була в окупованому місті - Херсон. Але це вже її історія. Я була неймовірно рада коли вона нарешті виїхала з окупації і ми видихнули з полегшенням.

Після 3х місяців (для мене вони тягнулись як рік), я і мій чоловік вирішили переїхати ближче до Миколаєва до його батьків. Там було безпечно, але через зміни, моя депресія досягла апогею.

На щастя, звільнили частину Херсону і Миколаїв став менше обстрілюватись, тому ми вирішили повернутися додому. Де я почала лікування з психіатром. Вона допомогла стабілізувати мій стан і повернути себе.⌛

💯2022 рік був найскладнішим для мене та моєї сім'ї, але можливість працювати та бути частинкою WordPress ком'юніті допомогло мені вистояти та допомагати моїй країні. В кінці року, я вирішила подякувати всім, хто мене підтримував, запитував як справи, жартував, був добрим до мене, у своєму пості на Medium.

Командні зміни

Звичайно війна вплинула на нашу команду і я одразу помітила як менеджмент змінив підхід до управління з акцентом на піклування про кожного члена команди.

🙌У нас почались тренінги згідно запитів команди (наприклад, боротьба з тривожністю), менеджмент допомагає з засобами заживлення (так як в Україні бувають блекаути/проблеми зі світлом або зв'язком) та релокацією за потреби.

Під час війни, наша HR команда ввела IDP (Individual development plan), який дозволяє окреслити розвиток людини протягом року, сфокусуватись і отримувати кращий фідбек. Мені це допомогло під час депресії. Бо війна внесла свої корективи і я стала більш тривожною, хаотичною і важко було сфокусуватись.

👩‍💻Важливою є постійна підтримка менеджера. Мій менеджер - це Анна, наша СЕО. Від неї я постійно отримую фідбек, який так часто потрібен, щоб краще працювати. Також вона підтримує мої починання та ідеї, що неймовірно мотивує.

Я стараюсь наслідувати її навички у своєму управлінні моєю командою з трьох прекрасних жінок - Вікторія, Community Manager; Ніккі, Content Marketer, та Дашель, Editor.

Crocoblock Team

Сьогодення

Пишу цю статтю 26 серпня, в день однієї з наймасштабнішої атаки росії (буквально 1 день від святкування нашого дня Незалежності). Більше 100 ракет і дронів було випущено зранку.

Зранку ми прокинулись о 7:30 і побачили початок атаки. Завдяки моніторинговим каналам, ми можемо продовжувати жити і підглядати коли треба сховатись в укриття. Я поснідала, зробила зарядку і почала працювати з серенами на фоні (це значно краще ніж вибухи).

Далі почались аварійні відключення, бо одна з цілей росії - зламати нашу енергосистему і ввести нашу країну і людей в хаос. Але, окрім злості і ненависті я більше не відчуваю нічого до них. Ми підготовлені, маємо пауербанки, екофлоу, резерви води і готові працювати наповну, щоб країна вижила.

💪Зараз ми активно працюємо над підготовкою до нашої 2гої WordPress Agency Summit у вересні і це допомагає мені відчувати, що я можу бути корисною ком'юніті. Доєднуйтесь, це безкоштовно.

Також стараємось більше брати участь у заходах WordPress. Наприклад, спонсорували WordCamp Europe 2024, та плануємо спонсорувати вперше локальний захід у Іспанії.👏

Crocoblock Team in an airplane

В загальному, я шукаю своє місце у WordPress ком'юніті, яке надихає мене своєю добротою та підтримкою. Першим кроком був мій посібник про партнерства. Далі, я планую:

Що мені Допомогло

Моя сила - це підтримка моєї команди, родини, і ком'юніті WordPress. Разом з тим, терапія, побутові справи, і навіть прості радощі, такі як кав'ярні або книжки, допомогли мені знайти внутрішню гармонію, щоб продовжувати боротьбу.

Мої топ глімери:

Бо тільки у гармонійному стані я можу допомагати своїй країні вистояти. 💙 💛

The post How WordPress and My Work Help Me Stay on Board During the War - Як WordPress та робота допомагають мені залишатись на плаву під час війни? appeared first on HeroPress.

11 Sep 2024 5:00am GMT