WordPress Planet

January 16, 2023

WordPress.org blog: WP Briefing: Episode 47: Letter from the Executive Director

On episode forty-seven of the WordPress Briefing podcast, Executive Director Josepha Haden Chomphosy shares her vision and current thinking for the WordPress open source project in 2023. Rather read it? The full letter is also available.

Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.

Credits

Editor: Dustin Hartzler
Logo: Javier Arce
Production: Santana Inniss
Song: Fearless First by Kevin MacLeod

Show Notes

make.WordPress.org/core
Join the 6.2 Release!
Submit Topics for the Community Summit!

Transcript

[Josepha Haden Chomphosy 00:00:00] 

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.

[Josepha Haden Chomphosy 00:00:40] 

Last month at State of the Word, I shared some opening thoughts about why WordPress. For me, this is an easy question, and the hardest part is always knowing which lens to answer through. Though I always focus on the philosophical parts of the answer, I know that I often speak as an advocate for many types of WordPressers.

[Josepha Haden Chomphosy 00:01:00] 

So as we prepare ourselves for the start of a new year, I have a few additional thoughts that I’d like to share with you, my WordPress community, to take into the year with you. 

Firstly, the Four Freedoms. If you have already listened to State of the Word, you have heard my take on the philosophical side of open source and the freedoms it provides.

But if you didn’t, then the TL;DR on that is that open source provides protections and freedoms to creators on the web that I really think should just be a given. But there are a couple of other things about the Four Freedoms, and especially the way that WordPress does this kind of open source-y thing that I think are worth noting as well.

One of those things is that WordPress entrepreneurs, those who are providing services or designing sites, building applications, they have proven that open source provides an ethical framework for conducting business. No one ever said that you aren’t allowed to build a business using free and open source software, and I am regularly heartened by the way that successful companies and freelancers make the effort to pay forward what they can.

[Josepha Haden Chomphosy 00:02:02]

Not always for the sole benefit of WordPress, of course, but often for the general benefit of folks who are also learning how to be entrepreneurs or how to kind of navigate our ecosystem. And the other thing that I love about the Four Freedoms and the way that WordPress does it is that leaders in the WordPress community, no matter where they are leading from, have shown that open source ideals can be applied to the way we work with one another and show up for one another.

As a community, we tend to approach solution gathering as an us-versus-the-problem exercise, which not only makes our solutions better, it also makes our community stronger. 

As I have witnessed all of these things work together over the years, one thing that is clear to me is this: not only is open source an idea that can change our generation by being an antidote to proprietary systems and the data economy, but open source methodologies represent a process that can change the way we approach our work and our businesses.

[Josepha Haden Chomphosy 00:03:01] 

The second big thing that I want to make sure you all take into the year with you is that we are preparing for the third phase of the Gutenberg project. We are putting our backend developer hats on and working on the APIs that power our workflows. That workflows phase will be complex. A little bit because APIs are dark magic that binds us together, but also because we’re going to get deep into the core of WordPress with that phase.

If you want to have impactful work for future users of WordPress, though, this is the phase to get invested in. This phase will focus on the main elements of collaborative user workflows. If that doesn’t really make sense to you, I totally get it. Think of it this way, this phase will work on built-in real-time collaboration, commenting options in drafts, easier browsing of post revisions, and things like programmable editorial, pre-launch checklists.

[Josepha Haden Chomphosy 00:04:00] 

So phases one and two of the Gutenberg project had a very ‘blocks everywhere’ sort of vision. And phase three and, arguably, phase four will have more of a ‘works with the way you work’ vision.

And my final thought for you all as we head into the year is this, there are a couple of different moments that folks point to as the beginning of the Gutenberg project. Some say it was State of the Word 2013, where Matt dreamed on stage of a true WYSIWYG editor for WordPress. Some say it was State of the Word 2016, where we were all encouraged to learn JavaScript deeply. For a lot of us though, it was at WordCamp Europe in 2018 when the Gutenberg feature plugin first made its way to the repo.

No matter when you first became aware of Gutenberg, I can confirm that it feels like it’s been a long time because it has been a long time. But I can also confirm that it takes many pushes to knock over a refrigerator. 

[Josepha Haden Chomphosy 00:05:00] 

For early adopters, both to the creation of Gutenberg as well as its use, hyperfocus on daily tasks makes it really hard to get a concept of scale.

And so I encourage everyone this year to look out toward the horizon a bit more and up toward our guiding stars a bit more as well. Because we are now, as we ever were, securing opportunity for those who come after us because of the opportunity that was secured for us by those who came before us. 

[Josepha Haden Chomphosy 00:05:33] 

That brings us now to our small list of big things. It’s a very small list, but two pretty big things. The first thing on the list is that the WordPress 6.2 release is on its way. If you would like to get started contributing there, you can wander over to make.WordPress.org/core. You can volunteer to be part of the release squad. You can volunteer your time just as a regular contributor, someone who can test things — any of that. 

[Josepha Haden Chomphosy 00:06:00] 

We’ll put a link in the show notes. And the second thing that I wanted to remind you of is that today is the deadline to submit topics for the Community Summit that’s coming up in August. That comes up in the middle of August, like the 22nd and 23rd or something like that. 

We’ll put a link to that in the show notes as well. If you already have chatted with a team rep about some things that you really want to make sure get discussed at the community summit, I think that we can all assume that your team rep has put that in. But if not, it never hurts to give it a second vote by putting a new submission into the form.

And that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.

by Santana Inniss at January 16, 2023 12:00 PM under wp-briefing

WordPress.org blog: Letter from WordPress’ Executive Director, 2022

Last month at State of the Word, I shared some opening thoughts about “Why WordPress.” For me, this is an easy question, and the hardest part is knowing which lens to answer through. The reasons that a solopreneur will choose WordPress are different than the reasons a corporation would. And while artists and activists may have a similar vision for the world, their motivations change their reasons, too. That’s why I always focus on the philosophical parts of the answer because I know that I am speaking as an advocate for many types of WordPressers. I have a few other reasons, too, which you may not be aware of as you use our software every day.

Why WordPress?

Most importantly, the Four Freedoms of Open Source. If you have already listened to State of the Word, you have heard my thoughts on the philosophical side of open source and the freedoms it provides. If you didn’t, then the tl;dr on that is that open source provides protections and freedoms to creators on the web that should be a given. There’s an extent to which the idea of owning your content and data online is a radical idea. So radical, even, that it is hard for folks to grasp what we mean when we say “free as in speech, not free as in beer.” Securing an open web for the future is, I believe, a net win for the world especially when contrasted to the walled gardens and proprietary systems that pit us all against one another with the purpose of gaining more data to sell.

A second reason is that WordPress entrepreneurs (those providing services, designing sites, and building applications) have proven that open source offers an ethical framework for conducting business. No one ever said that you cannot build a business using free and open source software. And I am regularly heartened by the way successful companies and freelancers make an effort to pay forward what they can. Not always for the sole benefit of WordPress, but often for the general benefit of folks learning how to be an entrepreneur in our ecosystem. Because despite our competitive streaks, at the end of the day, we know that ultimately we are the temporary caretakers of an ecosystem that has unlocked wealth and opportunity for people we may never meet but whose lives are made infinitely better because of us.

And the final reason is that leaders in the WordPress community (team reps, component maintainers, and community builders) have shown that open source ideals can be applied to how we work with one another. As a community, we tend to approach solution gathering as an “us vs. the problem” exercise, which not only makes our solutions better and our community stronger. And our leaders—working as they are in a cross-cultural, globally-distributed project that guides or supports tens of thousands of people a year—have unparalleled generosity of spirit. Whether they are welcoming newcomers or putting out calls for last-minute volunteers, seeing the way that they collaborate every day gives me hope for our future.

As I have witnessed these three things work together over the years, one thing is clear to me: not only is open source an idea that can change our generation by being an antidote to proprietary systems and the data economy, open source methodologies represent a process that can change the way we approach our work and our businesses. 

WordPress in 2023

As we prepare for the third phase of the Gutenberg project, we are putting on our backend developer hats and working on the APIs that power our workflows. Releases during Phase 3 will focus on the main elements of collaborative user workflows. If that doesn’t make sense, think of built-in real-time collaboration, commenting options in drafts, easier browsing of post revisions, and programmatic editorial and pre-launch checklists.

If Phases 1 and 2 had a “blocks everywhere” vision, think of Phase 3 with more of a “works with the way you work” vision. 

In addition to this halfway milestone of starting work on Phase 3, WordPress also hits the milestone of turning 20 years old. I keep thinking back to various milestones we’ve had (which you can read about in the second version of the Milestones book) and realized that almost my entire experience of full-time contributions to WordPress has been in the Gutenberg era.

I hear some of you already thinking incredulous thoughts so, come with me briefly.

There are a couple of different moments that folks point to as the beginning of the Gutenberg project. Some say it was at State of the Word 2013 when Matt dreamed of “a true WYSIWYG” editor for WordPress. Some say it was at State of the Word 2016 where we were encouraged to “learn Javascript deeply.” For many of us, it was at WordCamp Europe in 2017 when the Gutenberg demo first made its way on stage.

No matter when you first became aware of Gutenberg, I can confirm that it feels like a long time because it has been a long time. I can also confirm that it takes many pushes to knock over a refrigerator. For early adopters (both to the creation of Gutenberg and its use), hyper-focus on daily tasks makes it hard to get a concept of scale.

So I encourage you this year to look out toward the horizon and up toward our guiding stars. We are now, as we ever were, securing the opportunity for those who come after us, because of the opportunity secured by those who came before us.

Rather listen? The abbreviated spoken letter is also available.

by Josepha at January 16, 2023 12:00 PM under General

Do The Woo Community: Finding Team Members to Fit Your Companies Culture

Marius Vetrici has built a process to bring in new employees that are drawn to fit his companies values, and to grow with them as a team member.

>> The post Finding Team Members to Fit Your Companies Culture appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at January 16, 2023 10:09 AM under WooBuilder Blog

January 14, 2023

Gutenberg Times: Box Shadow, Newsletter Theme, Testing Call 20 and more – Weekend Edition 241

Howdy,

Last week’s Live Q & A on Layout features went really well, with numerous participants. The post and the show notes are still in the works. The recording is available on YouTube, should you want to revisit parts of it or missed it entirely.

Now that feature freeze for the major WordPress release is only three weeks away, the contributors would appreciate it if you could heed the 20th call for testing from the FSE Outreach program. You can help find quirks, bugs and annoyances, so they can be fixed before February 7th and during the round of beta version of the release.

Have a lovely weekend!

Yours, 💕
Birgit

Developing Gutenberg and WordPress

Gutenberg 15.0 release candidate is available for testing. Sticky positioning, resizable Site editor, updated to the Page List block, modify block style variations from global styles, and a lot more refinements are coming to the Gutenberg plugin

🎙️ New episode: Gutenberg Changelog #78 -State of the Word, WordPress 6.2, Gutenberg 14.8 and 14.9 with Birgit Pauli-Haack and special guest Hector Prieto

Last April, a group of contributors started working on research on how to best implement an API for to make blocks more interactive. This week, JuanMa Garrido shared a progress report: Update on the work to make building interactive blocks easier.

The resources linked in the post are mostly code internals, so they are definitely very technical at this point. With that said, understanding how the new API works, will not be necessary for developers to use this new standard. A standard proposal will be published the next few months. So for now, this is all bit technical and architectural. The work on the underlying framework is shared on this GitHub Repository


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

Munir Kamal, GutenbergHub, shows you in his latest post How to Find and Use Block Patterns in WordPress. You learn, how to find patterns in the post and site editor, how to navigate the WordPress Pattern Directory and how to install the patterns via the plugin Extendify Patterns and Templates

If you want to create your own patterns, but don’t know how to code them, you can use the plugin Blockmeister – Block Pattern Builder.


Sarah Gooding reports on the Lettre Newsletter Theme Now Available on WordPress.org, It can be used with the newly release newsletter feature in Jetpack plugin or as a stand-along theme. “The theme puts the focus on the subscription form, which is the most important thing a newsletter landing page can do – make it easy for people to sign up. Beneath the form there is a link to read all the posts, followed by another subscription form. All of these elements in the home page design are blocks, making it easy for them to be removed or rearranged.” Gooding wrote.


Will Morris explained the three ways add a Table of Contents in WordPress in is post for the Torque Magazine. The three ways are:

  • Install a plugin
  • Use on the Custom Table of Contents blocks
  • Create you Table manually in the Block Editor.

Soon you will be able to use the core Table of Content’s block once it comes out of the experimental stage. It’s already available via the Gutenberg plugin.

Theme Development for Full Site Editing and Blocks

In his post, Justin Tadlock, walks you through the layout classes in WordPress 6.1. With the latest release of WordPress, the software has now centralized its layout definitions, created semantic class names, and reduced code duplication on container blocks. “Originally, this post was intended to be a quick look at the changes to the system for theme authors. However, given the heftiness of the topic, it has evolved into a full overview of the layout framework.” Tadlock wrote.

In his second post published on the Developer Blog, Using the box shadow feature for themes, Justin Tadlock took a look at the box shadow support, that what just released in Gutenberg 14.9. As it happens with similar features, the first iteration of box shadow support is only available via code. The interface for the site editor screens are still in the works.

 “Keeping up with Gutenberg – Index 2022” 
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. 2021 on. Updated by yours truly. The index 2020 is here

Daisy Olsen held her inaugural live programming session on Twitch this week. The recording is now available on YouTube. In this stream, she talked about:

  • using LocalWP for local WordPress development,
  • the Create Block Theme Plugin, and
  • took a look at the code from a couple of existing block themes.

You need a Twitch account and follow DaisyonWP to get notified when she goes live.

In his latest post for CSS-Tricks: Styling Buttons in WordPress Block Themes, Fränk Klein, takes a detailed look markup of various buttons and how to style them via the theme.json properties.

Building Blocks and Tools for the Block editor.

Tom McFarlin continued his series A Backend Engineer Learns to Build Block Editor Blocks with Part 5 in which he covers adding color controls to a custom block for the use case, when you want to give the user the option to select the colors for the block themselves.

McFarlin, recommend the previous articles first as they build on top of each other. So far, he published:

  1. Required Tools, Plugin Structure, Dependencies, Block Metadata
  2. The Backend, The Frontend, Functionality, Styles, a Working Demo
  3. Block Attributes, Editable Content, Components, Editor Styles
  4. Saving Data, Styling the Frontend

Phil Sola create a Custom Color Picker for WordPress. Sola added some improvements to the existing color picker. It’s more an experiment rather than a full-fledged solution. His exploration might also be an inspiration for others to start experimenting with WordPress component library.


Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.

GitHub all releases

Upcoming WordPress events

February 4 + 5, 2023
WordCamp Birmingham, AL

February 17 – 19, 2023
WordCamp Asia 2023 

Check the schedule of WordCamp Central of upcoming WordCamps near you.

Learn WordPress Online Meetups

January 17, 2023 – 3pm / 20:00 UTC
Patterns, reusable blocks and block locking

January 19th, 2023 – 10:30 ET / 15:30 UTC
Live stream: Building an Advanced Query Loop block variation plugin w/ Ryan Welcher @ryanwelchercodes

January 19, 2023 – 7 pm ET / 24:00 UTC
Let’s make custom templates in the Site Editor!

January 20, 2023 – 3 am ET / 8:00 UTC
Let’s make custom templates in the Site Editor!

January 20, 2023 – 10:30 am 15:30 UTC
Block Themes and WordPress: Live Stream w/ Daisy Olsen @daisyonwp

January 23, 2023 – 10 pm ET / 1 am UTC
Patterns, reusable blocks and block locking (APAC time zone)

January 26, 2023 – 10:30 am ET / 15:30 UTC
Live stream: Reviewing developer-focused features in Gutenberg 15.0 w/ Ryan Welcher @ryanwelchercodes

January 31, 2023 – 3pm ET / 20:00 UTC
Creating a photography website with the block editor


Featured Image: Amit Patel: Mango Shake Orange Sweet found in WordPress.org/photos


Don’t want to miss the next Weekend Edition?

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

Thanks for subscribing.

by Birgit Pauli-Haack at January 14, 2023 10:30 PM under Weekend Edition

WPTavern: WooCommerce 7.3 Introduces New Products Block in Beta

WooCommerce 7.3 was released this week with the new Products block now in beta. In December 2022, the Products block went into testing in WooCommerce Blocks version 9.1.0. It’s based on the Query Loop block and is intended to replace all of WooCommerce’s current product-displaying blocks.

This first beta version of the Products block allows users to list products based on specific criteria and their layout in the list or grid.

Version 7.3 also introduces three “commerce-adjacent” patterns for building WooCommerce store pages. These are patterns that do not tap into WooCommerce store data but allow store owners to customize the images and the links. These patterns were also tested in WooCommerce Blocks 9.1.0. They include an alternating image and text block pattern, a product hero with two columns and two rows, and a “Just Arrived” full hero pattern.

image source: WooCommerce 7.3 release post

This release also brings store owners a new multichannel marketing experience in beta. Under the Marketing menu in the admin, users can now view a list of recommended marketing extensions without leaving the dashboard. These can be installed directly from the Marketing page.

Other notable features in WooCommerce 7.3 include Pinterest and Codisto extensions added to the onboarding wizard, a new warning banner when the tax settings have a conflict, and an improved UI for creating product attributes and uploading product images.

Check out the release post to see the template changes and all the new actions and filters available for developers. The full 7.3 changelog is available on GitHub.

by Sarah Gooding at January 14, 2023 04:25 AM under woocommerce

WPTavern: Lettre Newsletter Theme Now Available on WordPress.org

Automattic has published its Lettre theme to WordPress.org. The company launched its newsletter product at the end of December 2022 using Lettre as the default theme. The self-hosted version of this block theme is for those who want to publish a newsletter using Jetpack.

The theme puts the focus on the subscription form, which is the most important thing a newsletter landing page can do – make it easy for people to sign up. Beneath the form there is a link to read all the posts, followed by another subscription form. All of these elements in the home page design are blocks, making it easy for them to be removed or rearranged.

Lettre comes with 15 block patterns for building different pages and designs, including about the author(s), a bold color signup, a two-column signup, various designs for the newsletter intro with light and dark background images, newsletter signup with media on the left, newsletter signup with logos for the background, a list of posts, an in-post article promo, three columns of text, and more.

A live demo of the theme is available on WordPress.com. The menu items on the demo give a few examples of the different signup patterns in action.

Lettre is designed to be used with Jetpack’s Subscription block, which uses WordPress.com’s infrastructure to manage emails and subscribers. If you like the design but are already using another newsletter service, the Jetpack Subscribe block can be replaced with any other block, including the shortcode block for newsletter services that haven’t yet made their subscription forms available via a block. Be advised, you may need to write some custom CSS to ensure that the subscribe form matches the original design.

Lettre is one of the only themes in the WordPress Themes Directory that was made to be a newsletter landing page and certainly the only block theme dedicated to this purpose. Combined with Jetpack’s subscription feature, this is one of the most seamless ways to distribute a newsletter without all the extra steps of copying the content into a newsletter service’s editor. Lettre is available for free download from WordPress.org. I wouldn’t be surprised to see more themes like this pop up now that WordPress.com has launched its newsletter service.

by Sarah Gooding at January 14, 2023 02:50 AM under free wordpress themes

January 13, 2023

Do The Woo Community: Taking a Deep Dive Into the Current State of Social Media with David Bisset

David Bisset and I share our current experiences with Twitter, Mastodon, Linked, Tumblr, the Fediverse and open source.

>> The post Taking a Deep Dive Into the Current State of Social Media with David Bisset appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at January 13, 2023 10:58 AM under WooBits

WPTavern: New Video Explores Site Building Progress from WordPress 5.9 to 6.2

WordPress 5.9 “Josephine” was released in January 2022, but that seems like ages ago when you compare the advances made in site building over the past year. Anne McCarthy, an Automattic-sponsored contributor who heads up the Full Site Editing Outreach Program, has published a short video that tours the important changes in WordPress over the past few major releases. The video also doubles as a preview of some of the features coming in 6.2.

If you are using the Gutenberg plugin and have been tracking the relentless progress of the Site Editor, you will notice how limited the design options are in 5.9 and how much more consistent and expansive they are today. In 5.9 users users can only add a Front page template, and the site building interface is disjointed and less polished.

McCarthy demonstrates how WordPress 6.2 will introduce smoother interactions with browse mode. It will also greatly expand the template options available for users to add and includes a new colorized list view.

The Navigation block has had a long, rocky journey but seems to be reborn in 6.2. McCarthy showed how much more intuitive it has become with the new experience of editing navigation in the sidebar, and repositioning via drag and drop with live previews.

The instant that Style Variations were introduced in WordPress 6.0, it seemed they were always with us. Looking back at 5.9 in the video, the Site Editor appears so bare without them. WordPress 6.2 will extend this even further with improved block style previews, a style book, and a new zoomed out view that makes it easy to see changes at a glance.

Everything coming in 6.2 is converging towards better usability and more design options for site editors. The challenge here is to continue introducing new features without the interface becoming cluttered and chaotic. Many of these features are still being ironed out. For example, McCarthy mentioned that the Edit button is still a work in progress and may soon be relocated to be more prominent in the Site Editor.

This video gives a quick visual summary of what is being done to wrap up the full-site editing phase of the Gutenberg project before contributors move on to Collaboration. It is worth a watch to see the site building progress that contributors have made in just one year.

If you want to get involved in making sure all these features in 6.2 are ready for prime time, check out McCarthy’s latest FSE Testing Call: Find Your Style. It will plunge you into the new features of the Site Editor to perform a few tasks. It’s essentially a guided opportunity to explore the new interface while contributing back to WordPress, and you will earn a fancy testing contributor badge that will display on your WordPress.org profile.

by Sarah Gooding at January 13, 2023 03:56 AM under WordPress

January 12, 2023

Post Status: On OpenAI And WordPress With Jannis Thuemmig Of WP-Webooks— Post Status Draft 136

Jannis Thuemmig, founder of WP Webhooks, joins Cory Miller to discuss Open AI and WordPress. Jannis is passionate about utilizing the power of technology to increase efficiency. WP Webhooks is exploring the ways Open AI can be used to revolutionize website processes and management. It seems we are only at the tip of the iceberg for what is possible when working with WordPress and Open AI.

Estimated reading time: 2 minutes

Transcript

In this episode, Jannis Thuemmig, serial entrepreneur and founder of WP Webhooks, dives into the world of automation and Open AI with Cory Miller. Together they look at what is currently possible within the world of integration and automation within WordPress. Then they lean into what is unfolding as Open AI finds its way into the mainstream and discuss what this might mean for the WordPress community.

Top Takeaways:

  • Integrations & Automations to Save Time: Everyone is in need of some kind of automation. Our main goal is to save time by creating automations wherever there are pain points. Rather than doing things manually, WP Webhooks enables you to automate them within your dashboard.
  • Avoiding Automation through Software: Using software as a service partner means hosting your data on their platforms. Using Webhooks for integration and automation allows you to keep things on your server and within your complete control.
  • Possibilities with Open AI Integration: Webhooks is focused on using Open AI as an advantage to speed up processes by creating integrations between services and generating original content. They are working on finding cool use cases and understanding the actual power of what it makes possible.

Founded in 2006, WordPress VIP is the agile content platform that empowers marketers to build content both faster and smarter so they can drive more growth. We empower content and development teams with the flexibility and ubiquity of WordPress—the agile CMS that powers more than 40% of the web—while ensuring the security and reliability organizations need to operate at scale

WordPress VIPWordPress VIP

🔗 Mentioned in the show:

🐦 You can follow Post Status and our guests on Twitter:

The Post Status Draft podcast is geared toward WordPress professionals, with interviews, news, and deep analysis. 📝

Browse our archives, and don’t forget to subscribe via iTunes, Google Podcasts, YouTube, Stitcher, Simplecast, or RSS. 🎧

Transcript

GMT20230105-161248_Recording

GMT20230105-161248_Recording

Cory Miller: [00:00:00] Hey everybody. Welcome back to Post Status Draft. This is another interview and discussion in our Product People series, and I've got someone I've met, let's see, last year or the year before Giannis and doing good work, but we were talking about AI and that led to OpenAI and something they're doing with WP Webhooks.

So that's what the conversation is gonna be about today. But Giannis, welcome to the draft podcast. Would you tell us a little bit about yourself and your work and WordPress?

Jannis Thuemmig: Sure, totally. Thanks for having me here. Uh, it's always an honor. Uh, my name is Giannis. I'm from Germany originally, but started traveling a long time ago and since then, I basically work as a digital dumper from anywhere.

And I would say with a, with a very, very deep focus on web. And specifically in automation. This is where W P Airport comes from. So we are basically focused on connecting different services and WebPress plugging to let them talk to each other and kind of just automate the [00:01:00] system and get rid of the human error and save everyone a little bit of time and money, which is really interesting nowadays.

Cory Miller: Yeah, I, and I love it. Uh, one part I'll just sidebar real quick is I know when you say digital notepad, uh, the several times we've had zooms, I'm like, where are you in the world today, y'all? It's like, . Um, so I, I love that. I love to see the nude, like landscapes you're in every time we talk. Um, okay. So WP Webhooks, um, I know you've been, so automation is key.

It's about efficiency, um, like really saving that time. In the processes you're doing, um, what, tell me what all does WP Webhooks do?

Jannis Thuemmig: So basically it allows you to use a set of redefine integrations to let other services and WebPress plugin specifically talk to each other. So let's say there's, um, a woo commerce shop, for example, and you have a, a custom programmed plugin that has no integrations [00:02:00] whatsoever.

You can use our plugin as a middleman to allow sending data in between, and that works with mostly any kind of WebPress plugins as well as external data like, uh, external services, something like Zapier or make or integrated. So the, the basic main goal is to just make them compatible, which they, in a lot of cases, aren't from the beginning. Or if they are, they're often very limited, which is something we realized as well. So we just want to kind of get that interoperability to WordPress, which is something that was just lacking over the last couple of years.

Cory Miller: Yeah, I, I love that. I know Zapier has used quite a bit uh, obviously we've used it in the past at, at Post Status because of all the external services, and you're trying to link these and do some things that certain pieces of software doesn't do out of the bat.

So I, I love the premise of web hooks for sure. Uh, WP Web Hooks, what are you seeing or finding? Customers are gravitating to webhooks [00:03:00] for, like is there specific tasks that stand out that people are using these over and over and over and going, this is what I need. I don't want to pay for Zapier or some other alternative, I wanna do something here with my WordPress site.

What are you seeing from your customers?

Jannis Thuemmig: So I'd say that's not a specific use case. There's, uh, quite a lot. So everyone, literally, everyone who's in the, in the, has a web presence or has an online shop or something related and does something with website. Everyone is in in need of doing some kind of automations.

Let it be to automatically book orders into your accounting system or synchronize your properties from a property management website with your WebPress website. Or let's say you have a Teachable account and you sell online courses and you want to synchronize your students with a WebPress website to give them extra features.

This is stuff that they are using it for. So basically wherever there's a pain point and there's some time that just can be avoided by automating it through software. This is something where we are, um, jumping in [00:04:00] and it's specifically interesting right now for people that are very critical about privacy because especially in Europe, a lot of people don't want to use software as a service partners like Zapier or Integra.

Because they are hosting their data on other platforms, right? So they have no full control over it, which comes very handy with our plugin because you have your own server, so everything runs on your own server. You are in full control where your data is, what your data does. And this is a very, very critical point that is, uh, always, always well seen at the moment.

Yeah.

Cory Miller: Yeah, yeah, for sure. I, you went to a subject I didn't even think about, which is if you don't want your information out there on another service, having it in in WordPress, something you control. I think that's a key facet. Before we start talking about, uh, AI and specifically OpenAI, what are you most excited about with webhooks this year?

Jannis Thuemmig: Ooh, for sure. Bringing that AI space model [00:05:00] web. Because we had so much fun over the last couple of months trying these things out, seeing in which direction it goes. And it's just incredibly fun to, to play around with it because the possibilities are really endless. And we are, we are fully about saving time.

Right? And this is something we can even use to leverage more time out of our daily task, which is really, really good. Okay.

Cory Miller: Well let's roll into that because I think that's one of the most, uh, uh, Interesting themes in our community is ai. I've seen a couple tweets saying AI is gonna revolutionize, um, a lot of stuff with a website by the end of 2023.

I can't remember who said that online. And I was like, well, I've been paying attention enough. But talk to me about ai, OpenAI and what you, you see on the horizon for, um, for WordPress particularly, and opportunities and possibilities. . Yeah,

Jannis Thuemmig: so ai uh, specifically in our case with OpenAI, uh, there's, uh, a little differentiation.

So [00:06:00] right now it's very much hyped, the G P T three. So the, the kind of chat ai as you can, as you can, uh, think of, which is basically you just type in something and it, it gives you like a very human answer back, which is really, really incredible. And, uh, we specifically talk about the, the OpenAI api, which kind of allows you to.

Communicate data on a programmatic level, which means you basically don't even need to type something yourself, but you can already use a service to let these things run through the web automatically without ever touching this kind of data. And this is, this is just something that that works very well with, with the automation part.

Right. So we are, we are basically looking into bringing more possibilities that AI through non-static data, and, uh, what I mean by non static data, it's probably interesting to, to understand what an AI actually is. So it's a pre-trained network, right? It has the data that was feeded to it at some point. And with OpenAI, it's made from [00:07:00] mostly 2021.

So it has no actual new data. If you ask it something like what happened yesterday, for example, it could probably not give you an answer to, you could give it the information if you have it yourself. But it can never give you like the, the news and accurate information. And using things like automation, you can basically bring a whole new word to it because you can kind of give the AI the possibility through response and, uh, requests to send data through automation, uh, validate it somewhere else and send it back to the AI and tell the ai, Hey, look, there's new information.

We can use that, uh, or, or learn about that and, um, send me some more information or summarize me something. So it's, it's just a very interesting time in, in regards to giving the AI actual information that you can feed it, uh, that is currently not within its its own, um, possibilities.

Cory Miller: So you said something there.

Um, I, I haven't even gotten that in depth with OpenAI, but So in [00:08:00] 2021 they fed it a ton of data you're saying, and then trained it to be able to, to answer questions and things.

Jannis Thuemmig: Yeah, exactly. So basically they had a, a huge dataset or couple of datasets for sure about the information that they fitted. And the AI can basically make.

An answer that is, uh, in a human real reform, and that seems like it is made from a human, but the data that was fed is all from 2021, right? So it is a static data if we, if we want to hear it or not. So if you're gonna ask the ai, what is the latest model of iPhone, for example, it'll probably tell you something like it's the iPhone 13, because I don't think it has information about iPhone 14.

That would be something cool to try, but I guess it must be, uh, outdated information. And with that gap of, of using that, that automation in, in connection with ai, you can kind of close that gap and you can actually feed it real time data and use that data to, to do certain things within the AI [00:09:00] and, uh,

Cory Miller: I see, thats a new one.

Yeah, it does. Um, totally to me, and I'm asking as a newbie to all of this, um, because I've used it and I'm like, this is pretty dang fast. And I'm like, how the heck are they doing that? That makes total sense. And then from the training side, um, the model itself is, I was like, gosh, if this had access to that, and you could just ask it questions like that.

It's the, it's the a hundred times better Google. Yeah, because, yeah, it, like, I was, I, I mean I asked what are the strengths and weaknesses of WordPress, for instance, and it came back. Um, but knowing it's, it's a little bit lag on the data side is interesting to me. Um, but I saw the potential for this to truly.

Revolutionized some things on the web. Um, so it's, it, it's been really intriguing and I mean, I asked it all kinds of questions that I was just actually curious about and seeing what, not just from the what, [00:10:00] how the model would work, but the answer. And I was like, this is like a perfectly uh, formatted.

Informative, um, short essay that I would've gotten in college, you know, so that's

Jannis Thuemmig: intriguing. It's actually you can, you can write like on demand stories for your kids based on your own characters. Just type in a sentence, say you run a short story and it spits you out a short story that you can read them from going to bed.

It's amazing. It's just like incredible.

Cory Miller: I'm gonna have to try that today. I, I continue. This subject fascinates me and I think it's something we need to be thinking about and looking at and talking about in WordPress and Post Status, because this new technology coming and then how WordPress is placed in this.

And for years, I think this is a segway to talk about OpenAI and WordPress specifically. But you know, I've either built sites for people or known a bunch of people that build sites for clients. And you turn on this awesome, it's like you turn this car over, you pull this car up to 'em, and [00:11:00] you're like, here's your car.

But you gotta drive it with content, with things inside the site, and it's such a great vehicle for that. But oftentimes people get hung up on that part of. Oh, I don't know what to, I don't know how to drive my car. Right? Like these, you know, WordPress sites with the right architecture, the right things can really drive and make a dent.

That's our kind of thing with WordPress is like it's magic like that. But you still have to like, Drive it, you have to put gas in it and drive it, uh, with content. So that's a compelling angle for me with OpenAI. And I've heard about all these things. Before we segue specifically to the integration you've done too and some possibilities there, what, where do you see all of this and WordPress going?

Jannis Thuemmig: Like, that's a very interesting question. Yeah, yeah. Uh, I think, I think it will be in relay, I mean, it's, right now we are specifically in the content age, right? So I, I've seen a lot of people. [00:12:00] Going into the space where they try to create on demand articles using an ai, which is probably a terrible idea just through plagiarism because it's very easily detected if you don't lose like a rewriter and you use your very own wordings in between.

So this is something that we will see switching, definitely. But what I see as an advantage in the future with WebPress is that people will use to. We, we learn to use AI for the advantage in the sense of speeding up their process. So it's also kind of a, a way of automating things, uh, in the sense that they don't need to write their content anymore from scratch, or they don't need to write a, think about copywriting that much.

They just ask the ai, it's bit something out. They put it in, maybe adjust it, tweak it in their own way so that it has their very own style. And they probably just make the, the way of, of riding blocks 10 times a hundred times faster than it's right now. So we'll definitely see like a, a boost in performance and [00:13:00] probably block block posts over the long term.

Cory Miller: Okay. Well, so that leads into this specific integration you have and the tutorial I, I was looking through before we started. Um, so you saw OpenAI has an api and tell us, tell us about that in WP Web Web Hook.

Jannis Thuemmig: So, yeah, we, we basically started, um, after trying a couple of times how OpenAI works to, um, to integrate it with our plugin.

So we, we usually go for creating integrations for different services and plugins, and, uh, in that case it's, it's once separately for OpenAI, which makes it compatible with all of the other services and, uh, plugins. We are integrated. And the main goal was just to provide the integration, right? Because it's so new, barely anyone understands the actual power of it and what is possible.

So we, we just kind of created it out of the blue with a thought of, Hey, it would be cool to just have it, you know, let's see what, what's going to happen. And right now we are basically just [00:14:00] working on finding cool use cases. And, uh, there are definitely a couple, uh, like I've, I've, uh, showed you earlier.

We already have a blog post on our. That basically describes how you can auto generate method descriptions using OpenAI and Yost seo. So you basically just feed it in the title and it spits your order, perfectly made method description that you can just use or adjust as you want. And these kind of things, they just now come through trial and error basically.

And, uh, it's, it's very interesting to see where it goes. And I can see that with these kind of automat. Um, we can also provide what I mentioned earlier, that that possibility of feeding the AI new information that is not available within the AI itself. So because we can make these kind of workflows, um, if that makes sense.

And this is, uh, this is mostly what we are trying to do right now. We basically just working on, on use cases, see what's possible, trying out different things and it's a super, super exciting. [00:15:00]

Cory Miller: Yeah, absolutely. Because I mean, you talk about this car, you some a a site builder turns the car over and they start to use it.

But that meta, uh, description is one thing. Like I honestly confess, I never do, you know, but it's, it's helpful, it's vital. And so like that one little use case in the bigger picture of what I can do, I think starts to step us into this and it is really interesting. Um,

Jannis Thuemmig: oh, totally. Yeah. This is, this is literally just the, the tip of the iceberg.

If you want, you can basically let the AI create a, a full schema, uh, like a shima for your, for your website. So whenever there's a blog post, it can write the how-tos and everything in, in kind of adjacent format and, uh, spits your order perfectly well formatted SEO description and, and everything keyboards, the, the, the whole how to, and this is just, it's just such a time saver.

It's incredible.

Cory Miller: Well, okay. Do you have a tutorial on that [00:16:00] too? Because that's really interesting. Um, , or if you don't, we need one. Um, but so you're going into OpenAI or chat GPT or whatever, and then you're saying you're asking a question or something like that, and then it's gonna give you back those things.

Jannis Thuemmig: Yeah, exactly. It's just you literally ask it just a humanly written question, something like, give me back adjacent with each of these information. And it spits you out adjacent with each of the information. And Jason, you can always use on a technical level, right? So we can just leverage that out and use it through our plugin to use it in different automations and do different things.

Cory Miller: Oh, that's super cool. Well, what do you have anything you wanna share about what you're doing next with this WP WebHooks?

Jannis Thuemmig: Um. As a, as a use case, it's a, I mean, we, we definitely, for, for now we really try to just work on the OpenAI things mm-hmm. and try to find some cool use cases there. Uh, we had a lot of, um, a lot of actually customers reaching out about the possibilities as well and how exactly it works because the models [00:17:00] and the configuration is a bit complicated if you, if you're not fully aware of it.

But, uh, yeah, we, we just follow the standards and, uh, things should be fairly easy. But yeah, for us, it, it's mostly, mostly OpenAI and creating new integrations. That's something we're, we are hardly focused on at the moment.

Cory Miller: I, I really think this is, like you said, the tip of the iceberg that, um, I'm really intrigued by our WordPress community post at Post Status to go, okay, here's this cool technology.

How do we translate this into practical? Um, uses for the end client, the end user in WordPress. Um, so that, that's, that's interesting. We'll be excited to hear what, what you find in explorer and launch launch next.

Jannis Thuemmig: Yeah, you should just see the block post, uh, our, our, our block. There will be a couple of more tutorials coming.

They're already in the making, so in the next days we should see someone there.

Cory Miller: Okay. Perfect. All right. Um, okay. So. You, you [00:18:00] showed me something as like this. I think this is just showing the power of what it could do when we start to get these types of integrations into WordPress. Do you mind showing me the one you were telling me about?

Jannis Thuemmig: Totally. Yeah. Not a problem. Of course. I'm just gonna share my screen, probably this one. Yes, so I, I was basically just fooling around the other day on. With our integration, trying to find some new cool ways we can use to, to present the OpenAI integration. And, you know, like, like I mentioned earlier, you can kind of ask the AI to create adjacent format, um, with specific data.

So Jason is basically just a structured way of presenting data within the web that is something that the, the browser or the, the server can. And in our case, we, we, we wanted to have like, like in here, uh, just a simple field that you can write something and based on whatever you write, it updates the block post of [00:19:00] your choice.

So in our case, we just created a quick contact form seven form as we have an integration with contact as well. And we connected that with open. To create a so-called Jason and update a block post based on a specific information. So I can just demonstrate it here. You can see I have three block posts available and let's just take this one.

I just need the ID because that's the way we wrote it. So we have ID 97, and what I would like to do is, let's say I want to update the, the title of this post, right? So I can, I can write something like, Update the post with the id, let's say post title

with ID 97 and change it to, um, this is a new title based on OpenAI. So it's, it's basically what we read as a, as a human tech, [00:20:00] right. But if I submit that and I let our workflow. The AI basically interprets that and, uh, changes it based on our parameters within, uh, Jason. And when I refresh here and, um, the flow ran, it should display it.

See if it doesn't, no, it doesn't. Uh, so the thing is, because it depends what you feed the ai. So the AI basically needs to understand what you do. And, uh, in some, in some cases, that's, that's the problem with ai. It fits you out text, right? So you try to, you need to, to format. And kind of use the text in a different way so we can see.

Okay. Just didn't follow it. Just what I'm gonna do is, so to, to just, so the very same example, I just tried to type the similar thing again. Let's try it again. So, um, update the post with the ID 87 and change the title to, [00:21:00] um, OpenAI. Something new. Let's see now

Cory Miller: I always love live demos, . Yeah, I know. When you were showing me before I was like, wow, that's super cool.

Jannis Thuemmig: Yeah, it really depends on the AI, if I, if I do it right or not. Um, but it seems like you see that it's not completed. So basically something stopped within the AI and uh, yeah, I would need to, I would need to see what.

Cory Miller: Yeah, so you were showing, you were showing just now the webhooks, uh, pro dashboard. Do you mind taking us for a spin around the Webhooks Pro dashboard?

Jannis Thuemmig: Uh, yeah, totally. So it's basically like, you know, standard WebPress plugin and stuff. On the site menu we have, uh, our W2 Web Hooks Pro, um, menu item, and basically it's, it's separated into two main things, which is the automations, the flows, and the web. So there's, there's kind of a difference in between, because originally we came from the web website, which means it's kind of like a [00:22:00] one-way street for information to present.

Let's say you, you update a, a post on your WebPress website and based on that post you can send data into a, a certain direction, like directly and instantly to inform another service about that there's a new post. But then we realized that there's more of a need to actually automate kind of certain work.

And then we created something called Flows, which basically allows you to connect the, or create a consecutive order of triggers and actions. So web book triggers and actions to do certain things in a, in a specific flow as we call it. So I just head into it, uh, into one, which is the human posture. This was the example I tried to show you, which, uh, was currently not working out because of something that I need to see. Um, but what we have basically, within the floor. You can see we have a trigger, right? The trigger fires on a contact form seven. Within the settings, we basically selected the form that we created earlier, which is [00:23:00] embedded in, in the site.

And we don't want to send the email as we just want to send the data to OpenAI. And it was tested. We set up some conditionals, um, stuff that's not really important for now, but, uh, this is, this is basically what causes the actual workflow to fire, right? So, This specific trigger comes along with all the data that was sent within this form, and we then reuse the data in the other kind of actions here.

And as you can see, the first action is something, uh, is our OpenAI integration, where we basically sent that information that we had earlier, as you can see here, to OpenAI as a, as a text. And this is, this is what we read. So it basically says, get the posterity and the PostIt from the JSON, uh, in the JSON format.

This is the sentence, and the sentence basically is a dynamic string that comes from the input that we sent within this form. So it makes more sense if, if we go through it logically while, while building it. But, um, [00:24:00] when you click into a field like this, you will see it shows a dropdown, and inside of the dropdown you will see all of the information that was sent within the trigger, including the question like, change the title of the post idea, ???

So this is basically what we selected here. And this is kind of more details about the OpenAI stuff. Sure. And yeah, when you, when you continue safe, you can test the action directly within here. That's something I can try, um, just as an example to see what comes back. So basically right now I'm sending a real request with the data that we got earlier.

And this is basically the response. So we can see, we got some text back from the AI, which looks a bit weird as it's text. But within our plugin we have something like a formatter, which allows us to format the data and change into something readable. So I'm just gonna quickly do that to, to give you a better example of what we get back.

So as you can see, this is what we get back from the AI or from the formatter, which came originally from [00:25:00] the OpenAI. And this specific information we want to then use in another action to actually update the post. And this is, this is literally everything it does. You can just think it of simple steps that, like we have a trigger.

The trigger causes, uh, runs whenever the, the specific contact form was sent, then we sent the data to OpenAI. We format it in a certain way, and then we update the post based on whatever data we got back from the OpenAI. Excellent. So, yeah, exactly. This is, this is basically it for that.

Cory Miller: What, what are some of the automations.

Yeah, I, I saw the create the automation. So what are the, some of the things that webhooks can do from the automation side?

Jannis Thuemmig: Uh, you mean some examples for example? Ah-huh. Yeah. Yeah, yeah. Like I say, you can, you can, for example, connect the different services together. Let's, for example, say you have newcomer, right?

So you can go to the, to the integration [00:26:00] screen. You can install any kinds of integrations that you, you are working. So we have around hundred right now. And let's, for example, say you have commerce installed, right? So you can then install commerce once it's, once it's available on your website and within one of those automation workflows, you can then say, whenever commerce fires, then send the data using, uh, a WebBook, for example, to mm-hmm.

your bookkeeping system. Or send, send an email using the WordPress integration. So in here I can show you. Click send email, and then you have the possibility to send an email directly from your WebPress to the customer whenever, whenever, uh, an order was created. So it basically, it basically just allows you to do certain things that you would manually do within your dashboard.

Mm-hmm. ? Yes. In an automated way

Cory Miller: There's a bunch of those things for the Post Status setup out the way. I'm like, oh gosh. Yeah.

Jannis Thuemmig: I can't imagine. Same here.

Cory Miller: And, and what are, what are workflows to, uh, or I'm sorry, it's [00:27:00] webhooks. Oh, I thought that's a workflow somewhere. I read that wrong. Okay. Yes. So what

Jannis Thuemmig: I can show you, it's, it's basically separated in two parts.

It's sent data and received data. What it basically means is these are kind of the triggers available, right? So whenever a user created, or when a user was deleted or when a form was submitted, you can send data to a specific url. Let's say, for example, I want to send a URL to my website, um, I cannot call it demo, and I, I add my api endpoint here and I edit, and then you can see it here. Which basically means when ev, every time a user gets created, you can send a direct webhook request to this url and you can test it, you can customize it with, with more features, more setups, um, based on your needs. Gotcha. And this is, this is what I mean earlier, like a, a direct connection.

And the receive data is basically the exact opposite. So instead of sending data out on a specific event, you send data in and to do something specific. So you can, for example, activate a plugin. As you can see, you can call a PHP [00:28:00] function, you can create a comment, a post a user. So we have basically mostly all of the options of WebPress available through, uh, web as well.

Excellent.

Cory Miller: You don't have a Slack integration, do you by chance ?

Jannis Thuemmig: Um, that's the, that's the thing. Depends what Slack has as an api. Um, if they truly have an API and if they have an api and it can be integrated with something like an API key or a hero token, it can also be used with our plugin. Um, and that's an interesting point.

That's good that you mentioned that we have something like,

Cory Miller: um, it's a, it's a. Post Status specific thing, but I think a lot of membership sites, which is a big trend too. People building membership sites, course sites, you know, a lot of people like us obviously use Slack. Being able to, um, one, this is a nuance and I'm, uh, sorry for sharing, but this is like create a private group or something like that.

I've looked in some of the Slack API and. I'm using us as a [00:29:00] test for a second to say it is a broader thing. I think a lot of membership sites, they're using Circle, for instance, maybe they want to use something else. So I, I stopped you though. Keep going.

Jannis Thuemmig: Oh, no problem. No problem. Um, yeah, but what I, what I mentioned earlier is that, like you say, with, with, uh, slack, we can kind of integrate with any service that allows, like simple API calls or web and uh, we have an integration available that is called Web itself.

So, When you install one like that, for example, and you go to, let's say an automation workflow, I can, I can come within here, add a new action, and you see I have a WebBook endpoint available, which basically allows me to send data or send a request to a specific site. So if you have Slack, you would, you would uh, add your Slack U URL here, for example, right?

Slack API or something, and then you. Select the method you want to use to send data, and you can send the data and add it here along. [00:30:00] So if there's a, a service out there that just follows the standard rep hook or api, um, standards, you can integrate them as well with our plugin. So there's not directly, uh, integration necessary. Basically.

Cory Miller: Excellent. Well, one thing that's intriguing about this is for as long as I've been in WordPress, I, it, it has led the way in truly democratizing publishing, but over the years, you see Facebook, Twitter, what name, whatever default. Closed wall type garden come out. And um, I just did an interview with Mattias who does activity plug plugin for the Fed averse.

And I was like, the, you, you think about what you're doing here with webhooks and then the Fed averse is kind of bringing that power back to the. To the user and saying, okay, fed averse can help. To me, I just see the potential to go, let's, let's decentralize some of the social [00:31:00] networks. So when a billionaire buys the next thing, or they change their policy at one of these closed set social networks, you're, you know, all these people are affected by it.

And, and taking some of that control. So that's where I see FE averse. And then I go, what's the power here is. Ground zero for what you're doing is your WordPress site, and with things like tools like this, then you can start, I don't know, it's just helping bridge that gap of power. There's so much usability and features that these closed gardens have, but tools like webhooks and potential with the Fed averse is like bringing some of that power back, and I see WordPress truly being in the space to lead and innovate and bring that power back to the users.

Jannis Thuemmig: Totally. Yeah, I fully agree with you. The, the, an interesting point about that is actually that using our plugin, for example, you can use it kind of as a standalone on WebPress. So if you say you want to make automations, you don't necessarily need to use WebPress, but [00:32:00] you can just set up a WebPress environment and install our plugin and you can.

Automate external services through WebPress. Right? So you can use it kind of as a middleman for yourself without actually using WebPress.

Cory Miller: And you still maintain control

Jannis Thuemmig: in a lot of ways you have full control. Yes.

Cory Miller: Even if it's not a public facing site where you have content on like using that, that's the power, that's the other side of WordPress.

Do this has been become this huge power powerhouse of a, you know, a software. I talked to a lot of people on the enterprise and they mentioned. the connections. There's a, um, my friend Kareem at Crowd favorite talks about WordPress being the open source hub to connect services. So, like your example there.

I, I resonate with it cause I just talked to Kareem a couple weeks ago. I love that example. Yeah. Yep. Well, Gianni, anything else you wanna share, um, that you all have going on or you're excited about or anything I forgot to.

Jannis Thuemmig: Uh, yeah, I'm excited to make this tutorial work, so I think the next blockbuster [00:33:00] will see is probably about this example.

Okay. .

Cory Miller: I love it. Just to have, I love it. That's the beauty of being a part of this community as I get to ask cool, smart people that can do these things and see, see how they go. But I, I'll be playing around with open api. OpenAI's, API's, mouth, um, just cuz I was playing with that and like, wow, this is powerful and I love this kinda stuff and I love there's people like you experimenting with it, testing it, and giving users, um, that opportunity to do that.

Um, so thanks so much today for being on the Post Status draft podcast. Uh, this is under our product People series. I love our innovators in our community like you, and so thanks for joining me today.

Jannis Thuemmig: My pleasure, really. So it's an honor. Thank you very much as well for inviting me.

This article was published at Post Status — the community for WordPress professionals.

by Olivia Bisset at January 12, 2023 02:44 PM under Yoast

WordCamp Central: WordCamp Entebbe: First Wordcamp to happen in Africa in 2023 is on!

WordCamp Entebbe 2023 is set to be a major community event for WordPress developers, website designers, online publishers, students, and teachers to come together and share knowledge and experiences, network with other WordPress users, and gain inspiration for their work. Taking place on Friday, March 10th and Saturday, March 11th at the Uganda Wildlife Education Centre (UWEC) in Entebbe City, this WordCamp will be the first to happen in Africa and is poised to be a memorable event for all attendees.

The event will feature a range of activities, including beginner’s training, inspirational talks, showcases, best practices, and the latest trends in WordPress development. In addition, there will be a Women in Tech panel discussion, aimed at inspiring and empowering women-led businesses to thrive in the technology industry. A Teacher’s Workshop will explore the integration of WordPress in the local education curriculum, providing teachers with the tools and resources they need to introduce WordPress to their students for web design projects and assessments.

Attendees will also have the opportunity to take a free tour of the Uganda Wildlife Conservation Education Center, where they can learn about the animals of Uganda and the ecosystems in which they live. The center, which was founded in the 1950s to accommodate confiscated and injured wildlife, has grown considerably in recent years and is considered a premier facility for showcasing wildlife on the African continent.

Accommodation options are available for those traveling to Entebbe for the first time. Attendees can find a list of hotels and guest houses through booking.com https://bit.ly/entebbehotels or by contacting the WordCamp team at entebbe@wordcamp.org for more information and guidance. The full schedule of activities will be published soon, and we look forward to welcoming you to WordCamp Entebbe 2023!

Get Involved

There are several ways to get involved! Check out the details below:

Join the discussion via #WordCampEbbs hashtag on Twitter

by Kasirye Arthur at January 12, 2023 11:58 AM under Wordcamp Entebbe

Do The Woo Community: Reflecting on the Past and Embracing the Future for WooCommerce with Paul Maiorana

It's that time of year again when Paul Maiorana, CEO of WooCommerce, joins us for a review of the year and a looking into 2023.

>> The post Reflecting on the Past and Embracing the Future for WooCommerce with Paul Maiorana appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at January 12, 2023 11:29 AM under WooCommerce.com

Matt: Thirty-Nine

The last year of my thirties! WordPress turns twenty this year. Automattic is now ~2,000 people across 98 countries. There’s so much that has happened in the past decade yet it feels very much like we’re on the cusp of something even more exciting.

This morning started well; I pulled the hammock out of the garage (it had been hiding from the rain) and read for a bit, trying to get my 5-10 minutes of sun in the first 30 minutes like Huberman suggests.

Candidly, the last year was a really challenging one for me personally. There were some beautiful moments, and I consider myself the most lucky in my family, friends, and colleagues, yet among that same group there was a lot of loss, existential health challenges, and that weighed heavily on me. It’s also my last year to get on 40 under 40 lists! 😂

Usually when people ask me what I want for my birthday I don’t have a good answer, but this year I do! As Heather Knight wrote about in the SF Chronicle, the beloved Bay Lights are coming down in March. This has to happen — the vibrations and corrosive environment of the Bay Bridge is taking lights out strand by strand. Fortunately it’s now been a decade since the lights first went up, and there’s much better technology both for the lights and how they’re mounted and attached to the suspension cables. Finally, the lights were not visible from Treasure Island or the East Bay before, but this new version 3.0 will be, which is why the artist behind the lights, Leo Villereal, is calling it Bay Lights 360.

Like the Foundation series, we can’t stop the coming period of darkness from happening, but if we raise $11M we can bring the lights back. If we raise it soon we can shorten the time they’re down to just a few months, so I’m working with the 501c3 non-profit Illuminate to help fundraise. The idea is to find ten people or organizations to put one million each, and raise the final million in a broader crowdfunding campaign, to re-light the Bay Bridge and give an incredible gift to the people from every walk of life that see the bridge, and hopefully have their spirits lifted by the art. I’ve heard 25 million people see the Bay Lights every year.

It’s a lot to raise, but every little bit helps so please donate here, and if you are interested to do a larger gift please get in touch. I’m committing a million dollars to the fundraise, and myself, Illuminate director Ben Davis, and the artist Leo Villereal are happy to personally connect with anyone considering a larger donation.

Because of some family health reasons I’m back in lockdown, so going to try and throw an online party tonight in the “Matterverse.” We’re going to party like it’s late 2020. 🎉

All birthday posts: 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39.

by Matt at January 12, 2023 04:37 AM under Asides

January 11, 2023

WPTavern: Automattic Launches Blaze Ad Network for Jetpack and WordPress.com Sites

Automattic is bringing Tumblr’s Blaze ad tool to WordPress sites with its launch today on WordPress.com and Jetpack. Blaze made its debut in April 2022, to the delight of Tumblr users who will gladly shell out cash to get people to look at their cat or promote a game they made. It’s an affordable way to attract new followers or just send out something funny into the universe, starting at $5/day.

WordPress.com users can now to go to wordpress.com/advertising, select a site, and promote content with Blaze. Jetpack users have access to the ad network inside the WordPress.com dashboard.

After selecting a post, users are taken to the design wizard where they can add an image, title, a snippet, and a destination URL. The URL can be the post or page or it can direct visitors to the main website.

When Blaze first launched on Tumblr there was no way to target the promoted content – it just displayed to random users. Now there are a few more options. When promoting content from WordPress.com or a Jetpack-enabled site, users can narrow the audience by device: mobile, desktop, or all devices, select from a few main geographic areas (continents) or serve it everywhere. There is also a dropdown with topics of interest, but they are fairly general, e.g. Arts & Entertainment, Automotive, Business, Education.

After selecting the audience, users can set the budget for the campaign, starting at $5 with a max daily budget of $50. With a minimum of $5/day for a week users can expect an estimated 5,900 – 8,000 impressions. For $25/day, users can expect 29,700 – 40,200, and up to 59,500 – 80,500 for $50/day. Site owners can monitor the success of their ads in the Campaigns tab.

Content sponsored by Blaze will be promoted across WordPress.com sites and Tumblr pages, an audience that accounts for an estimated 13.5 billion impressions per month.

Blazing has become somewhat of an art in the short time it has been available on Tumblr. It will be interesting to see how ads originating from WordPress.com and Jetpack go over with the Tumblr audience.

Creating advertising content that works across the disparate audiences between WordPress and Tumblr-powered pages may be a challenge for some site owners. Tumblr users can only target audiences by location for blazed posts. It’s possible that WordPress’ additional targeting options can help funnel the ads to sites where they will be most well-received, but the announcement says ads will be promoted across WordPress.com and Tumblr.

Blaze campaigns require approval to be in compliance with Automattic’s Advertising Policy before being published. They are currently moderated in approximately 30 minutes but this may change in the future as more users try out Blaze.

Automattic is treading new ground in creating its own ad network that any user across Tumblr and WordPress can tap into. It’s a strategic move to extend access to the world of WordPress, given that it’s such a large audience, and it will be interesting to see how the company improves the targeting options to meet the challenges of serving both audiences.

by Sarah Gooding at January 11, 2023 10:52 PM under wordpress.com

Post Status: Improving 5ftF Contributor Journey • Building Interactive Blocks • Layout Classes • WP20

This Week at WordPress.org (January 9, 2023)

Share your feedback about how to improve the Five for the Future contributor journey. Check out work underway on how to make interactive blocks easier to build, and take a walkthrough of layout classes in WordPress 6.1. It's time to start planning; how will you celebrate WordPress' 20th birthday?

News



Thanks for reading our WP dot .org roundup! Each week we are highlighting the news and discussions coming from the good folks making WordPress possible. If you or your company create products or services that use WordPress, you need to be engaged with them and their work. Be sure to share this resource with your product and project managers.

Are you interested in giving back and contributing your time and skills to WordPress.org? 🙏 Start Here ›

Get our weekly WordPress community news digest — Post Status' Week in Review — covering the WP/Woo news plus significant writing and podcasts. It's also available in our newsletter. 💌

Post Status

You — and your whole team can Join Post Status too!

Build your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. ✉ Listen to podcasts. 🎙 Follow @Post_Status 🐦 and LinkedIn. 💼

This article was published at Post Status — the community for WordPress professionals.

by Courtney Robertson at January 11, 2023 06:08 PM under WordPress.org

WPTavern: ClassicPress Community Votes to Re-Fork WordPress

In December 2022, the ClassicPress community voted on whether to re-fork WordPress or continue on with the project as-is. As WordPress continues to evolve, ClassicPress fell behind in pursuit of PHP 8+ compatibility. The fork is based on WordPress 4.9 and users are increasingly limited in what plugins will work with the five-year-old codebase.

In a discussion limited to ClassicPress core contributors, Viktor Nagornyy, one of the project’s directors, announced the results of the vote: “The option to re-fork has 20 votes while continue-as-is has 18.” Nagornyy summarized previous discussions and suggested an approach that would be more realistic for the project’s limited contributors:

ClassicPress can’t be WordPress without Gutenberg, but it also can’t be its own CMS with a small core team at this time. There are simply not enough developers to make progress without backporting code from WP to move away from WP.

An almost even split in the poll suggests the best option might be a hybrid one, find a compromise solution that will satisfy both sides.

With a small core team, we have to find ways to be more efficient, to get more done with less. The only way to do that is to leverage all the work that’s done by WP contributors. As the core team grows, we can always explore the possibility of splitting away from WP but at this point in time, it’s simply not feasible.

Some participants in the previous discussion saw re-forking as postponing the inevitable, kicking the can down the road until the next re-fork, but it is the only option if users want to retain compatibility with the rest of the WordPress ecosystem.

“If you read recent threads, you find out that the community expects plugin compatibility with WordPress… another reason for the re-fork option,” ClassicPress core committer Álvaro Franz said.

Franz, who is also the author of the WP-CMS fork based on WordPress 6.0, previously said he would be unwilling to help with a continuation of the current version based on WordPress 4.9.

“It [ClassicPress] doesn’t have to be a competition (and it never could compete with WordPress anyways), but it can be a leaner version, for people who are already disabling Gutenberg via plugins, for developers who want a different approach to the way they develop their projects (closer to ‘the classic’ experience, but yet… modern!),” Franz said.

“Eventually, it won’t make sense to run a fresh copy of WordPress to then go and install a plugin that ‘disables’ half of it. What’s the point? Why not have a version that covers that specific use case?”

As part of Nagornyy’s proposed hybrid approach, he suggested the project retain some changes that were introduced in ClassicPress in v1.x, such as the privacy-oriented changes (anonymizing data CP sends to APIs), the news widget, and ensure that all API endpoints use ClassicPress APIs as in v1.x.

The discussion continues around how to proceed with the fork. ClassicPress contributors are leaning towards using Franz’s WP-CMS fork based on WordPress 6.0 but have not finalized the details yet.

by Sarah Gooding at January 11, 2023 03:10 PM under classicpress

WPTavern: #58 – Lax Mariappan on How Headless WordPress Works

Transcript

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

Jukebox has a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, how Headless WordPress works.

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 forward slash feed forward slash 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, well, I’m very keen to hear from you, and hopefully get you or your idea featured on the show. Head to WPTavern.com forward slash contact forward slash jukebox, and use the form there.

So on the podcast today, we have Lax Mariappan. Lax is a web developer based in the Philippines. He’s an open source enthusiast and lover of all things WordPress. Lax has been tinkering with websites since high school. But it all changed when he discovered WordPress in 2010. Lax currently works as a backend engineer at WebDevStudios.

We talked today about Headless WordPress, and it’s a complex topic. Headless is the concept of decoupling the WordPress admin from the front end of the site. WordPress will continue to work as expected, but the presentation layer will be done by a different technology. React Gatsby and Remix being some popular choices.

This implementation of WordPress is complex, requires technical knowledge above and beyond that needed for a more typical WordPress install. But it has its benefits.

Lax talks through all of this in great detail. How keeping on top of all the additional dependencies Headless WordPress requires can be time consuming. How it can create difficulties for content editors who don’t always get to see what their work will actually look like in real time. Why this approach to WordPress can take more time and resources during the build.

Lex explains how these problems typically crop up, and how it’s possible to plan ahead and build in solutions for all the problems that you might encounter.

If you’ve ever thought about going headless with WordPress, then the podcast today is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast. Where you’ll find all the other episodes as well.

And so without further delay, I bring you Lax Mariappan.

I am joined on the podcast today by Lax Mariappan. Hello Lax.

[00:03:30] Lax Mariappan: Hello, Nathan.

[00:03:30] Nathan Wrigley: Very nice to have you with us on the show today. I have to commend you for your staying power, because Lax and I have tried to record this episode a couple of times and he’s been incredibly, incredibly thoughtful about getting his, all of his equipment and everything working. So thank you, first of all, I would like to express my gratitude for you staying the course.

But before we get into the podcast, Lax, I wonder if you wouldn’t mind spending a moment just introduce yourself. Tell us who you are, where you are, who you work for, how long you’ve been using WordPress, all of those kind of things.

[00:04:06] Lax Mariappan: Thank you. It’s good to be on WP Tavern, it’s one of my favorite publications, and also the favorite podcast. So I’m Lax, Lax Mariappan. I’m from India, and also I’m from Philippines. So I would say I live in both countries, and I use WordPress since my school days, like 2009. So I was looking for a platform to build a website for an event or something, and then I found out Blogger versus WordPress, and I liked WordPress more even that time.

So since then, I’m using WordPress almost every day. And my first job I got started working as a PHP developer, I would say, and then fully focused on WordPress. And I wrote my first plugin in 2011. It’s a very simple one. It’s now kind of obsolete because Facebook changed it a lot. So I wrote a plugin for something to fetch Facebook feed. So, and then my journey goes on. Right now, I work as a backend engineer at WebDevStudios. So where I get a chance to learn and work more with headless CMS every day almost.

[00:05:09] Nathan Wrigley: Your work at WebDevStudios, I don’t know a great deal about the company, but my impression of the company is that you work with, how should we describe it? Enterprise clients. You’re dealing with fairly large projects. I would imagine sizable budgets. Those kind of things, right?

[00:05:27] Lax Mariappan: Yeah, yes. Enterprise level.

[00:05:28] Nathan Wrigley: So when we decided we were going to have this conversation, Lax introduced the subject to me of headless WordPress. Now this is a word which I imagine some of you have heard before. Maybe some of you have never heard the word before. Perhaps there’s a subset of you which have experimented with it, but I’m expecting that the majority of WordPress users have not.

So, first of all Lax, would you mind giving us a very, in depth I suppose is the right word. Give us an analysis of what headless WordPress is because I’m sure many people think they know what it is, but perhaps they don’t.

[00:06:06] Lax Mariappan: So headless, or decoupled CMS, so first we all know content management system, right? So WordPress, we are using WordPress now as a content management system. It started out as a blogging platform. We used it mainly for blogging. And then WordPress introduced custom post types, taxonomies and all that sort of stuff.

So we are now using WordPress to build simple to complex websites. Forums. Some people use it for their colleges, universities as a social media platform, and some of them use it for a job board and everything, right? So we have plugin for everything and we can customize it and we use it.

So when it comes to the traditional CMS, we call that as monolithic. I hope I’m not using too much jargon here. Monolithic in the sense it has everything into it. So for example, if you go to a website, the header, footer, the sidebar, and the content that you see and the forms and everything that comes from the same CMS itself. So it is going to be, let’s say, in the case of WordPress, it’s built mostly with PHP and JavaScript.

So everything is going to be PHP template with a bit of JavaScript and CSS to it. But when you say on the contrast, headless CMS, it means, so you can consider that as a, I would not say person. Maybe something like, you can imagine something that doesn’t have a head. So in the sense the body is the same, head is different.

So you can imagine that as, you are going to use the same admin panel and you are going to have the same WordPress features. You can add the content, you can add menus, you can edit anything, you can add users, all that stuff. But when I view the website, so it’s not going to be your theme. So it’s not the typical way of how WordPress gets rendered.

So instead we will be decoupling it. So that is WordPress admin will stay on another site. It can be on a subdomain or a sub folder, but the front end is going to be a different platform. So it’s going to be hosted in a, mostly a JavaScript based stuff. So you can use either React based frameworks like React itself or Gatsby, Next.js or Remix, or anything that you like.

And also you can either go in another route as well. So you can make it like a fully static website, or you can render it on every time as a server side rendering as well. So every call will go to the server and renders.

Okay, so now we can call that a small intro about headless. You may already know this one. It became a buzzword a couple of years ago, right? But now everyone wants to go as headless. I see that company goes headless, or my competitor goes headless. So I want to go that way. But, unpopular opinion. Maybe you might hear some other people say that too. Headless is not for everyone, or I would say not for every use case.

It depends on how much content that you publish. What are your goals and what you want to achieve. So headless is good, it’s performant, it’s fast, secure, and it gives you more freedom and flexibility, especially in terms of performance it’s really good. But I would say it’s not the something like you should go headless. It’s not the answer.

[00:09:10] Nathan Wrigley: So essentially you’re saying that there are scenarios where this is desirable, but there’s going to be other scenarios where WordPress, in the traditional sense of the word. The regular WordPress that you download, perhaps use a hosting company and it’s all driven by PHP. The normal way of doing WordPress. That might be the best solution for lots of people.

Okay, so we’ve got our WordPress website, which we can interact with, and then the content that comes out of that website is pushed to something else. And probably we’ll get into what the options are there. But let’s take the use case of a company which comes to you and says, okay, we’ve heard this buzzword. We think that we want to go headless.

What are the benefits of going headless? Let’s forget about all the problems that might be associated with it. Can we just iterate through the things that you will gain if you manage to pull off a headless WordPress website. Now, I know there’s going to be all sorts of different scenarios there, but maybe just pick out the low hanging fruit. Some of the things which you believe are really beneficial.

[00:10:17] Lax Mariappan: Yeah. The first and foremost, or the popular one, is the performance. So WordPress uses PHP templates. We will do everything with PHP and Javascript and also a little bit of caching to render our traditional CMS like traditional pages. If you use a normal WordPress installation with a theme. So that’s how it’s get rendered.

So there you can see it depends on the hosting company as well, and also how much plugins that you use and how you configured them. So that affects the performance of a site. But when it comes to headless everything is going to be bundled, and there will be how a normal JavaScript based application gets rendered.

So it’s going to be a modern web application where you have control over, for example, if your page doesn’t use certain CSS classes, those CSS will not get loaded for that page. So I would say the assets that are loaded, it will be less. And the images will be more optimized. In either case, like in traditional too you can optimize images, but it’s like the performance is the first one, I would say.

It’s going to be both developers will love it and also the site owners, and also, let’s say marketers, Everyone will like the performance aspect of it. And in terms of headless, I would say developers will like it, especially in terms of, so you can repurpose the content. So if you are having a CMS, WordPress as a headless CMS, you can use that same endpoint, get the data and display it in a different formats quickly.

Other than a WordPress theme. So for example, if you’re using a WordPress theme, you have to create multiple templates. So this is a template for mobile, and this is something that, for example, if you want to use it for a landing page, you may have to do some small or extra changes. But when it comes to headless, you can just customize it in a way that you want to.

For example, I want to have a landing page. I don’t want certain stuff to be there. So you can turn on, off certain components, that’s it. So it’s like you can render the blocks and render the content faster. So developers and designers will like it. And also, in terms of the security, that’s where I’m more interested in cybersecurity especially. When people say WordPress sites are not secure, that triggers me actually. Yeah, I do get angry.

So it’s like, you don’t have to worry about that. So you don’t have to worry about changing your login page url. Adding captcha to your login form, all that stuff. Because that URL is going to be safe and secure. No one knows where you are hosted your CMS.

[00:12:49] Nathan Wrigley: Can I just interrupt there? So could you explain that, because I imagine there’s a bunch of people scratching their head at this point. Because normally, let’s say you have a website, it’s example.com. You’re going to go to example.com/wp-admin, and there is your login page. But there’s something in between here. I’m not sure that we explained that quite. So just explain why the login is secure. Explain where it is and why it’s not normal WordPress.

[00:13:19] Lax Mariappan: Yeah, so I mean, normal WebPress is also secure but people can guess it, right? Say example.com/wp-admin, so they know. They can see from the source code and the page source, they can see oh, this looks like a WordPress site. And then they can guess the admin url. So slash wp-admin, it’ll redirect them to the login page, right.

But when it comes to headless, the example.com will be hosted somewhere, and the front end that you see will be different. So for example, let’s say CMS is your WordPress installation, all WP. So you can call that like wp.example.com. So that’s where your WordPress stays in. But when you go to the example.com, that’s your front end, so that’s just JavaScript and html. So it’s like, if somebody wants to hack your site or somebody wants to, just guess what will be the admin url. So they cannot.

[00:14:10] Nathan Wrigley: It’s a difficult concept to understand if you haven’t encountered this before. But what you’ve got basically is a WordPress website, which is the container for the content, but it isn’t the website and we’re not used to that in traditional WordPress. You go to example.com/ wp-admin, get redirected, log in, do all the things, and click publish, and as soon as you click publish, it will be present on the website. That’s not the way that this is working because the WordPress website is completely decoupled from the thing which is presenting it to the world, right?

[00:14:48] Lax Mariappan: Yeah. Yeah. Completely decoupled.

[00:14:50] Nathan Wrigley: So given that, there’s no connection between, okay, here’s my website at example.com and where I might log in. And because of that there isn’t the capability to just guess the login page and then bruteforce an attack and so on. So in terms of security, it offers that benefit. The thing which people are most worried about, somebody getting your admin password going in and spoiling your site. That’s highly unlikely because they simply won’t know where to look.

[00:15:23] Lax Mariappan: Yeah. And also, so for example certain normal pages like comments, so that’s where we get a lot of spam, right? So comments will go to comments.php. When you submit a form without any data, or maybe if it’s spam data, it just goes there, right? But when it comes to headless, we will be using some extra customization for the comments and everything.

So it’s not going to be the data will store as comments in the database, and it’ll be, you can view them as comments in the admin panel. But when you are viewing it in the site, so you are reading a blog post, you have a comment form, so that form is HTML and JavaScript. So that’s not how a typical, a normal WordPress form, normal comments form.

So that’s where you will get less spam as well. So you don’t have to worry about that too. Like people submitting spam data and also any other form. So that’s another thing. And you don’t have to worry about any other security related stuff, because it’s just static.

So people cannot do anything or manipulate data. So it’s going to be just HTML stuff. Whatever they can do is just view the data. So I would say in the headless, so if you are viewing some pages or we are in a archive page and post archive, news archive, any archive page or any other page that does the data and fetches the data from the database, all that stuff.

So all that stuff will be protected routes. So people cannot easily guess. Sometimes you might encounter database related attacks, right. So you may hear cross site scripting attack or any other stuff like, somebody trying to get data either they pull your data or they want to insert some other data to the database. That’s not the case.

Everything is going to be static, like just html, and it’s only read only. So people are not going to input any data. And the input will be just maybe a comments form, contact us form, something like that. And that will be handled. It depends on what form provider you are using, or how you configure it, but still it’s more secure that way.

[00:17:25] Nathan Wrigley: So just to reiterate the point one more time, just in case anybody hasn’t been paying attention. We have our WordPress website. It is used by the developers, by the content creators, by the editors. They do their normal work inside of WordPress, but the thing which is being viewed on the front end by the population at large is completely separate.

You’re just sucking the data out of WordPress and putting it into whatever you like. The security’s fairly obvious, you’ve explained that really well. The performance, obviously, if all that you are showing is static html, essentially. That’s going to load really, really quickly. Nothing needs to be built at the time that the page is viewed and so on and so forth. It’s already been created.

This all sounds amazing and of course that raises the question, why aren’t we all doing it? And you have given us, in the show notes you’ve given me, three different things which we perhaps should talk about, and some of them, you explained the problem and then we’ll get to the solution.

So the first one that you talk about is dependency hell, you’ve described it as. And, I’m guessing that having a headless site is not straightforward. We’re very used in WordPress to, novices can install WordPress incredibly quickly. You basically upload a zip file and unpack it and connect it to a database, and these days, you know, you go to a hosting company and not even that. You just click a button and, wow, there’s your WordPress website 30 seconds later.

I’m guessing that this is not the case for headless. There must be all sorts of complex layers of things going on in the background, and you say that in many cases it can become very difficult. Dependency hell. So describe the problem of all the dependencies.

[00:19:13] Lax Mariappan: So when you have a WordPress installation, we will be installing plugins, right? You might be, if you are using WordPress for a while, you are already aware of the jQuery migrate plugin. All that stuff. So WordPress uses jQuery even now. So jQuery is a dependency that WordPress requires. WordPress depends on jQuery in admin panel, and also on the front end.

So if you want to get rid of jQuery, it’s kind of, WordPress may not be the same, if you want to eliminate that. Because WordPress depends on it. So it’s something like, let’s say you cannot say that as a oxygen, but it’s something that we all need it. So we need that to survive. So WordPress needs jQuery to work normally.

So similar case, when you are building a headless site, you will be requiring a lot of frameworks, libraries, and also packages. So for example, if I’m going to choose Next.js as my front end platform, front end framework. So Next.js is built with React. If I want to use Next.js, I may want to use some other Next.js related libraries.

So it is something like if you are on Android, you may want to add extra apps on your phone. If you are an iPhone, you’ll be adding some more extra apps to extend, right? It’s the same case. Similar to plugins. Instead of that plugins, we will be adding packages. So that packages helps the developers to add extra features that we need.

So the problem here comes in is, everything gets stacked in and one will be dependent on another. So, for example, if someone is installing a package like for SEO, and maybe that package will require something else. And let’s say if Nathan is maintaining SEO package and I installed it, and for example, for whatever reason, Nathan becomes a musician and he doesn’t, he is not interested in SEO anymore.

So he may not be more active in maintaining that dependency, maintaining that plugin or that package. So what happens is I’ll be waiting for him to fix the bug or some errors. Or I will waiting for him to upgrade to the lightest version. But it’s not the case, right? So, my Next.js package will be waiting for Nathan, so it’s like I’m depending on him, but he’s not available. So in that case, I have to go and do that work as well. So that adds to our development timeline.

And then, so this is just one package and one scenario. So this happens with multiple packages and stuff. And this is not just Node or NPM packages. It also happens to WordPress stuff as well. So, for example, let’s say we have a popular forms plugin, or we have a popular slider or any other plugin.

So you will install that plugin and you want that plugin to work with headless. So how we are using headless, it’s the data is stored in the WordPress, and we want to get the data through either Rest API. It’s a method that we, you know, you go to a url, you ask the WordPress, hey, give me this data and it’s going to give. Or you’ll be using GraphQL. It’s the same. You go to an endpoint and you’re going to say, hey, I’m looking for this post. I want five posts from this date. So it’s going to give that data as well.

So either you use Rest API or GraphQL. The problem is a plugin that you are using, your popular forms plugin, your popular slider, or any other plugin that you’re using. LMS plugin, E-commerce plugin or any plugin, like a payment gateway. So you have a plugin and you want to use it with headless. So that plugin should work with the Rest API or Graph QL. So if that doesn’t work, if that doesn’t give you the flexibility, and then you are still stuck there.

Because you cannot go and create everything on your own, right? So we cannot reinvent all the wheels. We don’t have time to create everything from scratch. So that’s where it’s like that becomes a bottleneck. So you are like, hey, I found the plugin. I started working on it. It works up to this mark, but it’s not a hundred percent. So it’s like it does its job 80%. Now I have to go fill in that 20%. It adds to the budget, it adds to the development timeline. So that’s the dependency hell.

[00:23:15] Nathan Wrigley: Yeah. So in the case of all of the technology, which is in the background if you like, which we haven’t really talked about too much, but like you said, the things which you are requiring from third party developers. There’s a dependency there, and it’s very similar to the dependency that you may have on plugins, you know, you want them to be updated and so on, but you are adding extra dependencies. And of course, the more dependencies you’ve got, the more costly, time consuming it is.

I’m guessing that most of the things that you are depending on, in addition to WordPress and you described what a few of those were, you could, I suppose, do some due diligence and figure out which projects have been well maintained, updated frequently, and so on. And I guess in the open source world, much of the dependencies that you’re using will be open sourced, so you could fork them. But again, you are creating probably a large amount of work for yourself and your team.

[00:24:13] Lax Mariappan: Yeah that’s true. Well said. So it’s like, since it is open source, it’s good. Like lot of reviewers. We have a lot of eyes on the code, and you can fork it. You have the freedom to do whatever you want. But still you are looking for a solution and that becomes a problem. You have to fix that as well. And that adds to the, another dependency, another dependency. It becomes a cycle that you cannot escape sometimes.

[00:24:36] Nathan Wrigley: I guess this is a bit like a seesaw. You know, on the one hand you described all of the benefits, performance, security, and so on, of headless. And then on the other side is, is all of the things that we are now describing. You know, the dependencies and so on. You’ve got to weigh up at the beginning of the project whether one thing is worth all of the time and effort that may be required to do it.

And I’m guessing in many cases, certainly at the enterprise level, the answer’s going to be yes, because the budget is there, we can put enough bodies to work to make all of this happen, and if we need to fork things, there’s enough people on the team that can do that and maintain the project, which has fallen into disuse. But for a little project the seasaw may tip heavily against something like headless just because of the things that you’ve described there.

Okay. So that was our first thing, dependency hell. The second thing that you wanted to talk about was the fact that in the WordPress world, especially in the last five or six years or so, we are really used to what you see is what you get, WYSIWYG. You save something in WordPress, you publish something and you have almost a hundred percent certainty of what it’s going to look like. The backend looks like the front end, especially with things like page builders and so on. But you say that that’s not always the case with headless solutions. Why is that?

[00:25:55] Lax Mariappan: We will be creating custom blocks. So, either there are a popular way of building now custom blocks is with ACF. So you all might be aware of and using it, even though you are not a programmer, you might be using it, right? So ACF is easy to install and create some custom fields. So you can use ACF to block, to build blocks for the site.

So those blocks can be used or you can build your own custom blocks. You can use any block starters like, frameworks that are available now. Or you can just follow our, WordPress comes with packages that you can on build command, so you can just build your block in a matter of seconds.

But still, all this stuff. So for example, if you are having custom blocks, I’m not talking about just normal blocks, like where you add a paragraph or image or something very simple. That is easy to build and that’s easy to see. That’s different. But I’m here talking about something complex.

So for example, you can imagine that as an Elementor widget or, some other items that it comes with the page builders. So, let’s say a slider, maybe tabs, accordions, all that stuff, right? So that can be added through the blocks itself. But you cannot preview them, because when you add them in the admin panel and we add them in the content. Those content gets, you know, you can choose like, oh, this is the tab title, this is the content.

And you can keep adding the content, but you don’t know how it’s going to render in the front end. But let’s say if you are using some, there are a lot of free blocks and also even premium blocks available. So if you are using a block to build them, and then using the normal WordPress installation. Or you can use WordPress with the full site editing, the modern themes, or the hybrid themes, like old plus full site editing themes.

Still they both work well. Like you can preview, oh, okay, this is the tab I added this content. I can’t view this one. But when it comes to ACF blocks or other certain custom built blocks, you cannot preview them.

So when a editor or a user adds content, they may get lost. So I have a slider. I want to add three, four images to it. I may get lost. Oh, what’s the third image? What I have added there, and how it looks? Is the images correct? Is the text rendered properly or should I reduce any title or text or anything, right? So all this stuff becomes a little tricky. And also sometimes it becomes a pain for the content writers, content editors, and also the site owners.

[00:28:24] Nathan Wrigley: So in the normal, traditional WordPress, let’s say we’re creating a page, we add a page, and we use whatever tool it is that we want to use for that. We add in some blocks. We are perhaps using Elementor, whatever it may be. And we click publish and then we are able to immediately view that because WordPress is working in the traditional sense of the word. The page gets pushed through the templating engine and it’s rendered with its template and we can see it right away.

But because that’s not happening here. And the mechanism for rendering that page is entirely different. You can’t necessarily view it immediately. Have I kind of encapsulated that? What you are doing in the backend, because it’s decoupled with the presentation layer on the front end, you can’t necessarily always see it?

[00:29:16] Lax Mariappan: Yeah, so that’s the challenge. So the solution here is to customize the way you built. So for example, we can give them a preview button so they can preview what are the slides, and how they look. And they can see that immediately in the editor itself. Like when they are adding content in the block editor, they can see it.

And also the other way is to have a button, a preview button. So that will preview before the content gets published. So, you can change the workflow. So if somebody hits, instead of publish, you can have like a preview button or keep it as a draft. So that way it’s like nothing goes to the front end without your approval or preview, right? So you have to preview it and see, oh, make sure everything looks correct, and then you can say, hey, I want to publish it. Yes, confirm, publish it, and then it goes to the frontend.

[00:30:04] Nathan Wrigley: That’s fascinating. That’s really ingenious. So, because we can’t necessarily see it on the frontend, you and your team have built a custom preview system. So on a block by block basis, you can see what that block will look like when it’s rendered. So in the example of your slider, presumably where we’ve got three or four fields. We’ve uploaded maybe some text, we’ve uploaded an image, and it’s just a bunch of fields. Normally we’d click publish and we’d go to the page and preview the page and we’d see it right away. But in your scenario, you are going to hit a button inside the block to show what that block and that block alone will look like. Have I understood that?

[00:30:48] Lax Mariappan: Yeah, that’s what we did. Because the users, they are used to the traditional WordPress. And especially that was with classic editor, I mean the old editor. So if you insert an image, they can see it’s an image. And if you insert something, you can see. And we are all used to the page builder era, right? So if you add a accordion, you can see how the accordion is going to look.

But when it comes to headless, all this stuff is going to differ. So, the tabs, accordions, sliders, and also anything else, any other custom stuff that we built, we added a preview button, and when you click on the preview, you can see that right away.

Then you can make sure like, oh, the colors are correct, the image is correct, and everything renders properly. Because sometimes if you are not looking at the content and adding content, you might miss some data, right? So you might have missed a small setting that says full width, or you know, boxed. So then you feel like, oh, why this looks so awful. Oh, I’ve missed this full width button. So that’s how the preview button works.

[00:31:49] Nathan Wrigley: So if I’m looking at the block and it’s a, let’s stick with the slider just for the sake of it, and I’ve uploaded my images and whatever fields were required and I click the preview. Does it literally happen inside that block? Or is this some kind of modal which pops up and shows things? Or is it, is it literally taking over the block itself?

[00:32:09] Lax Mariappan: Ah, it’ll be within the block. Like it will replace, so for example, if you have a block and you are adding some content to it, and when you click on the preview, it’ll replace where you are adding the content, right? It’ll replace the form. Form of the block where you are saying like, hey, this is the title, this is the subheading, this is the description. Instead of that, it’ll just render the titles, heading and description.

[00:32:32] Nathan Wrigley: Right, and then you toggle that off again once you’re, once you’re happy. So, ah, that’s really interesting. So the workflow there is really very different. And I’m presuming that after a period of time, the people who are editing, creating this content, that just becomes part of the process? They just understand that, okay, rather than viewing the whole page or whatever it may be, post whatever, I’m just viewing this little bit, and I’ve done it several times now and I’m confident that if it looks right inside the block preview, then I can click publish, wait for everything to happen, and hopefully that page will go live. And, it’s just a different workflow that you have to get used to. But once you’ve done it several times, it’s, familiar and normal.

[00:33:14] Lax Mariappan: Yeah, it becomes part of the workflow. And also, like we discussed earlier, your site will be like, CMS.example.com. And the front end will be on example.com. Sorry, every time you have to go to example.com/about, example.com slash contact us. Instead of that we will have a preview button. So, you can preview each block and you, if you, or feel like, hey, I want to see how the whole page looks like, you can click that preview, and that will take you, or that will show you immediately, oh, this is how the front end, like example.com/the page will look like.

[00:33:45] Nathan Wrigley: Yeah, that’s a good point. We’re so used to the preview button being connected to the URL in question, because it’s being rendered by WordPress. You click the preview page button or whatever it may be, and it takes you to the correct place. In this case, there’s no connection between what the URL will be and where you currently are, so yeah, that’s fascinating.

Just as a bit of an aside. We haven’t got into this, but I think it would be a good topic to discuss for a couple of minutes. If WordPress is separated from the presentation layer, this sort of headless notion. How often does the website get regenerated, if you know what I mean? So for example, if we click publish in our headless WordPress website, what is typical there? Are you going to generate the page immediately and store it as static html? Or do some clients have different expectations there? You know, for example, if you are a, a site which needs to publish things regularly, perhaps you need that capability.

I click publish. I want that page to be live within a matter of moments. Or it may be that you’ve got a website where it doesn’t really matter if the pages are not built, I don’t know, three hours, six hours a day, whatever it may be. Do different clients have different expectations there?

[00:34:56] Lax Mariappan: Yeah, that depends on how the publication frequency is. If you want to publish immediately, we can do. If you are okay with publishing the changes after two, three hours, still we can do. So it’s about how you want to set, how you want to build the things.

So here, few things to consider. You can go with static, fully static website. That’s just static and only when a page gets updated. So for example, you have a hundred page. All of them are static and those pages will not be regenerated. So if you change just the about page and only that 99 pages will remain the same. Only that about page will get regenerated again. You can go that route.

And also you can go with, every time in the page gets rendered, you can go server side rendering. So every time that’s new, so you can go that route as well. So that depends on how you want to render the data and everything has pros and cons. The normal way is like how Next.Js does now. Because it is like, keep everything static and if you want to render something, you can still regenerate the specific page.

So this way it’s like you don’t have to build everything all the time. So you can build what has changed in the WordPress. You can see that in the headless frontend. And also you don’t have to wait for it. So, for example, if I go make some change and click update and you can see that immediately.

[00:36:21] Nathan Wrigley: Really interesting, because there is no exact way of doing this is there? You can just build it in whichever way you think is most beneficial, or whatever the client needs. You know, if, if it’s a newspaper website where, really I need to click publish, and within a few moments I need that page to be live because the content that we’re creating is tremendously important to be fresh and new and so on. But it may be that, yeah, you don’t have that expectation and you’re quite happy to have it work in a different way and publish on a, a much less frequent basis. I can’t really imagine a scenario where anybody would say no, I’d rather it was published less frequently, but maybe there are scenarios where that’s beneficial. I don’t know.

Okay, and the last point that you wanted to talk about was, the whole conversation has proven to be really interesting, but it’s pretty clear that there’s a lot more work involved in this kind of website. And so your first point was about the fact that the dependencies, lots of dependencies. Your second point that was that you don’t always get to see what you see is what you get in operation. And the third one is basically the amount of time it takes, the amount of resources it takes. You’ve described this as headless asks for more. Tell us about that.

[00:37:34] Lax Mariappan: Yeah, so when it comes to creating a normal WordPress, like a standard WordPress theme. So what you do is like, you start with your prototyping tool. Like it can be Figma, Adobe XD or anything. So you have your design ready, right? You are creating mock-ups, discuss with the client, and then create a mock-up and then find the variations, all that stuff. And you are settling in, hey, this is my design. And now I’m going to create the theme.

So, I want to create this many templates. I want to create this many menus, all that stuff. When it comes to traditional stuff, it’s like, you don’t have to consider too many things. So it’s kind of straightforward process and like designers and developers can, the engineers can work hand in hand. And it’s, you can follow Agile like, build stuff, reiterate and just deliver it.

So that’s how that works. But when it comes to headless, so you have to consider a lot of things. I would say the first thing is the knowledge or, you know, expertise. With WebDev Studios, we are, I would say kind of one of pioneers and also experts in WordPress plus headless stuff. So we have launched, it’s a open source like we have Next.js starter template. So if you want to try out Next.js a headless frontend for your WebPress site, you can just take a look at WDS Next.js starter. It’s free and it’s in GitHub, so you can just start using it.

So, expertise comes one, like whether you should be, have sound knowledge in that. So you can go and fix stuff. You know what you are doing and you know what to expect and all that stuff. But this requires something like, for example, I am a backend engineer. I have limited React knowledge. I’m now catching up with React, Next.js, all that stuff. But I would, I would not say I’m an expert at it. I build stuff, I still use Next.js every day, but it’s like, I won’t say I’m an expert at it.

So expertise is one. So your team should have sound knowledge in the framework or anything that you do. Or even if you don’t have sound knowledge, let’s say if you are doing something like, something very new, like Remix got released only one or two years ago, right?

So if you want to go use Remix, You should be an expert in React and you should play around with React. So that’s the time. So my point is like time, it asks for expertise and it asks for time. So when it comes to just normal WordPress theme, probably you might finish the theme, let’s say, in a few weeks, or at least a few days even sometimes. With page builders finish it in few days or few weeks, right?

But maybe if you are building it from scratch and you are doing a lot of customization, it may take a while. But when it comes to headless, may take even longer. So more expertise, more time, and all this adds up to more budget.

This may sound like, oh, well should I do all this stuff? It’s kind of worth it. So you don’t have to, for example, if you have your, the front end components ready you may be having your storybook, like where you want to see how the button should look like, how the elements, how the panels are. Let’s say how each component will look like and how they render, all that stuff, right? So when you have all these parts ready, you can go from, for example, today I’m using Next.js, sooner I can move to something else, like I can use Remix. Or I can use something else that’s going to be hot in the market in future.

But when it comes to the typical WordPress, you are going to change everything from scratch. So if you want to add a new theme, so maybe if you want to change the look and feel, that’s different. So everything has pros and cons, but the short answer is the headless CMS ask for more.

[00:41:13] Nathan Wrigley: Yeah. It does sound like not only do you need more time to develop all of this for the reasons you’ve just described. It’s more complicated, so it takes more time. There’s more moving parts, shall we say. And it may also be that you need to spend some of that time not just building the thing, but learning how all of this hangs together, because there’s an awful lot going on in the backend here. And if you don’t have expertise in that, presumably things could go pretty wrong.

With that just before we end. You’ve obviously decided at WebDevStudios that this is an approach. I don’t know if you build the majority of your sites in this way or subset or a proportion of them, not sure. But, typically what is the amount of time longer it would take to get a website out? Let’s say, for example, that if you were just going to use WordPress as is a normal WordPress website, and you built an exact same website, but did it headless. And let’s imagine a site with, I don’t know, several different custom post types.

It’s got hundreds of pages. I’m just kind of making up something off the top of my head. But typically, you know, does it take twice as long, three times as long, 50% longer? What, what are we looking at?

[00:42:28] Lax Mariappan: I’m going to answer just like other engineers do. It depends. But it’s like, I would say it takes a long, maybe you can say, maybe you can say double, but it should not take more than double or something. So that’s where I would say start with more of research. So you should not change frameworks or libraries in between. Like once you started as React, go with React. And if your team is, they are very comfortable and they’re knowledgeable in React, use that. If you are going to use Vue.js or Astro or any other framework. When you start with something and you can go with it.

So, it is a matter of discovering what the client needs and where the goals meet. How we can achieve it. And once we are very clear on that, you can start developing. And during the development phase itself, we can see what are the possible, you know, the bottlenecks or what causes the issue, what could be a problem, and we can figure out other different approaches and solutions.

So, for example, you don’t have to let’s say, PayPal is not the only payment provider right now, right? The payment gateway. So we are using so many different stuff and they do the payment integration quickly. But before those days, let’s say 10, 15 years ago that case was different, so now we have more options.

So similarly, you don’t have to create a form and you don’t have to wait for someone to, the third party or some other open source in a package or something to be ready. So either you can build something on your own if you have time and budget, or you can fork something and then you can adjust to it.

Or the other way is, I would say you can go with some existing third party or SaaS or any other solution, which is just already there and you can see how you can use it with WordPress. So these are the stuff that can reduce your development time.

So when you say if you are, I don’t know exact hours or something, let’s say a thousand hours. So if you say a thousand hours for a normal WebPress installation, so headless may take a little longer, 1,500 or 2000 or anything. But it depends on what the client wants and what framework you choose and your expertise, like, I mean, the whole team’s expertise. And also how well we plan, organize, and go.

So sometimes it’s like just the client takes so long to respond, or sometimes it’s just like, even the client is clueless or what’s happening. So that adds up to some stuff. And I would like to also highlight, when you hear all this stuff, somebody listening is, they will be scratching their head like, so headless is yay or nay.

So, recently, I cannot say the client name and stuff, but I would say, how we figured this out and how it is kind of helpful. So we had to publish more than 20 websites. That’s for a single client. And all of them are different, and all of them are headless, but that’s for a single parent company.

So what happened is, we had the architecture ready, right? So we, we know what happens when you publish. We have everything ready. I mean, the back end and the front end ready. So things become more easier that way. The development time is actually just for one site and then other sites, it’s just like, it was fast.

But we had enough configuration and enough options we given to the client. So every site is not going to look exactly the same. They have their own customizations. But still it’s like amount of development time is the same or is actually less when you compare to traditional. But it depends. It depends on what’s the use case? How, what you are trying to build and everything.

[00:45:52] Nathan Wrigley: Yeah, it really does sound, there were so many good perspectives at the beginning where, you mentioned performance and so on where this is definitely going to be worth it. I guess if the client is willing and the budget is available and the expertise is there, then this sounds like an incredible option. Steep learning curve probably, but a lot of benefits on the backside of that.

Lax, just before we round it up, if somebody has been thinking about playing with headless and they’ve listened to this and they think, okay, I’d like to take that a bit further. Couple of things, firstly, where can they get in touch with you? But also have you got any guidance about resources that they may find useful?

So that could be a website or a book or whatever it may be. So let’s start off with resources and then we’ll turn to you to finish it off. So what resources do you recommend to learn about headless in general?

[00:46:49] Lax Mariappan: In general it’s like you can start with WP Engine has their own blog. They have stuff about headless WordPress and they also have some of packages and stuff they maintain. They have Atlas. It’s a platform they are planning to go full fledged on headless stuff. And also you can read about GraphQL, WP GraphQL. Their team is more active and they share a ton of stuff on how to customize and maintain stuff with headless.

And also you can, like a shameless plug. So I’d also highlight about our WebDevStudios blog. So you can see a lot of headless related articles, tips, and tricks. If you want to play around like, you know, you don’t have to spend something to test it out. So you can go with a lot of free starter templates.

So we have, WDS has like WebDevStudios has a starter template. We have Next.js starter. So that’s a headless thing. All you need is your WordPress, and then you can install that on a locally in your laptop or machine, and then you can just test it out, how it looks, compare the performance and everything.

And also, like other developers and writers have their own stuff. Like Colby Fayock is a popular WordPress developer. He has his own Next.js starter. So you can just simply Google WordPress headless starter, and you can find a lot of starter templates. If you are a developer, go this route or if you are a, you know, site owner or you are just hobbyist, you want to just try or understand a little bit more?

You can still do that reading the resources, right? You can actually check our blog as well. WebDevStudios blog. We have, I would say a couple of headless related stuff. That’s one of the popular article last year. Why headless WordPress is trending. So you can see why it is trending, what to expect. You can read more details in that blog.

[00:48:40] Nathan Wrigley: Thank you very much. And then finally, just to finish this off. Where could people get in touch with you? Are you available on social media? Maybe an email address? Whatever you’re comfortable with sharing.

[00:48:50] Lax Mariappan: Sure. You can find me on, you know, Lax Mariappan. I’m on all the social media like Twitter, Instagram, Facebook, and everywhere you can find me. So you can reach out to me as an email as well, laxman.0903@gmail.com. Anywhere like GitHub everywhere is the same. Luckily I got my name on all the social media, so you can find it.

[00:49:10] Nathan Wrigley: Lax Mariappan, thank you so much for chatting to me today. I really appreciate.

[00:49:16] Lax Mariappan: Thanks Nathan. It’s been great. So I’ve been listening to WP Tavern Podcast for a while. Especially, I like to catch up with what’s going on. The new stuff with WordPress. So it’s good to be on the show,

[00:49:28] Nathan Wrigley: Well, you are most welcome. It’s been a really interesting and informative episode. Cheers.

[00:49:34] Lax Mariappan: Cheers. Thank you.

On the podcast today, we have Lax Mariappan.

Lax is a web developer based in the Philippines. He’s an Open Source enthusiast, and lover of all things WordPress. Lax has been tinkering with websites since high school, but it all changed when he discovered WordPress in 2010. Lax currently works as a Backend Engineer at WebDevStudios.

We talk today about Headless WordPress, and it’s a complex topic. Headless is the concept of decoupling the WordPress admin from the frontend of the site. WordPress will continue to work as expected, but the presentation layer will be done by a different technology. React, Gatsby and Remix being some popular choices.

This implementation of WordPress is complex, requiring technical knowledge above and beyond that needed for a more typical WordPress install, but it has its benefits.

Lax talks through all of this in great detail. How keeping on top of all the additional dependencies Headless WordPress requires can be time consuming. How it can create difficulties for content editors who don’t always get to see what their work will actually look like in real time. Why this approach to WordPress can take more time and resources during the build.

Lax explains how these problems typically crop up, and how it’s possible to plan ahead and build in solutions for all the problems that you might encounter.

If you’ve ever thought about going Headless with WordPress, then the podcast today is for you.

Useful links.

React Library

Gatsby

Remix

WebDevStudio Next.js WordPress Starter

GraphQL

WPGraphQL

WebDevStudio Blog

Colby Fayock’s website

by Nathan Wrigley at January 11, 2023 03:00 PM under podcast

Do The Woo Community: 95% of Websites Have an Issue with Color Contrast

Even just by getting your color contrast right, which is very easy, anyone can do it. You just use a contrast checker.

>> The post 95% of Websites Have an Issue with Color Contrast appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at January 11, 2023 10:43 AM under WooBuilder Blog

WPTavern: WordPress Performance Team Working Towards Unbundling Performance Lab Plugin

WordPress’ Performance Team met this week with the express purpose of responding to Matt Mullenweg’s recent request to stop adding functionality to the Performance Lab plugin which could otherwise work as a standalone plugin.

At the end of December 2022, the Performance Team published instructions for how to test the new SQLite implementation, which was bundled into the Performance Lab plugin as a module. Mullenweg commented on the post, indicating he saw the SQLite functionality as better suited to becoming a standalone community plugin:

Can we please make this its own community plugin, hopefully to become a canonical one, and stop putting additional things like this into Performance Lab — it feels like we’re stuffing things into PL unnecessarily.

In mid-October I have requested that we stop this unnecessary bundling before with @tweetythierry around WebP, which was put into Performance Lab, so it is disappointing that another large function like SQLite was bundled into Performance Lab plugin.

In an effort to galvanize a base of testers for upcoming performance features, the Performance Team has leaned towards bundling new performance-related functionality into the plugin. Although they are already developed as self-contained modules so they can be easily extracted as individual plugins, the concern is that their visibility would be greatly reduced. The Performance Lab plugin has more than 30,000 active installs. Any standalone plugin would take time to build up to a user base, whereas functionality added to Performance Lab has an instant audience.

“Agreed that there are definitely valid use cases for stand alone plugins, remaining mindful of some of the advantages of a single hub plugin such as development/maintenance, adoption, promotion, developer onboarding/contribution etc. which the Performance Lab facilitates well today as a central performance focus community hub plugin,” Performance Team contributor Thierry Muller said in response to the unbundling request.

Muller outlined three different options contributors discussed in this week’s Performance Team meeting:

  • Option 1: Keep PL as is, but additionally deploy modules as individual plugins
  • Option 2: Make PL a “wrapper” focused on central infrastructure and recommendation of individual plugins
  • Option 3: Deprecate PL completely in favor of individual plugins

Option 3 seems to be the least attractive to those who participated in this week’s discussion, as it introduces more hurdles for discoverability. Performance Team contributor Felix Arntz noted that one benefit of option 1 is the plugin would continue to work as-is for the 30K people who currently have it installed and that option 2 “would require a complex migration that users likely would not understand.”

WordPress developer Jonny Harris suggested that having each functionality in its own plugin helps with testing but also asked what defines a module.

“Would the current Site Health checks all be together, for example?” Harris asked. “SQLite and WebP are clearly their own modules, but what about smaller things?”

Arntz suggested contributors continue the discussion regarding the scope of how the current modules could be distributed as plugins. He suggested every module could become its own plugin where some modules become standalone plugins and others would be grouped together into a few “topic specific” plugins.

Contributors are discussing the different approaches in more detail on a GitHub issue and will be voting on the best approach. The vote will be open until Friday, January 20, 2023.

by Sarah Gooding at January 11, 2023 03:34 AM under Plugins

HeroPress: Why small can be just the right choice

Pull Quote: WordPress has impacted where we live, who our friends are and which destinations we like to visit. Here is Ellen reading her own story aloud.

I feel honoured to write an essay for HeroPress. While thinking about what I should write about, I wanted to make sure it will be helpful to others.

Of course, everyone’s goals are different. My partner Manuel and I started to create WordPress products, because we saw the opportunity to build a small business and keep it a business we both felt comfortable to work in over the years. And that’s what we did. We love to travel and searched for a way to live the nomad lifestyle long before the term was even a thing. We travelled and worked on our blog and themes. And don’t get me wrong, it was not easy in the beginning. We had to build an audience first, so we wrote blog posts about everything we learned while keeping financially afloat with small client projects. We put endless hours of work into our blog, before even dreaming of one day earning income just with our themes. But we loved every minute of it.

We worked from Thailand, Sri Lanka and New Zealand, and we felt creative and free.

We went to WordCamps and creative conferences along the way and met so many new people with similar values and goals.

Having these experiences formed our way of thinking about the way we wanted to work moving forward. The benefits of being a small team of two seemed so obvious to us. We could make decisions fast and react to new trends without asking anyone for permission. As long as we built something others liked, we would always be ok. So that’s what we focused on. We built one theme after the other and loved the creative freedom this work gave us. The positive feedback and listening to the stories our customers shared on how our themes helped them reach their goals kept us going.

Living abroad

As we could work remotely from any location. We didn’t need an office or a local team. Keeping our business so flexible allowed us to move from Germany to New Zealand in 2015. After about two years working towards it, we were able to apply for a business visa and eventually for permanent residency four years later. Living away from family is never easy, but the opportunity to live in another country surely teaches us so many valuable lessons we would never want to miss. It’s a true gift, all made possible by our small WordPress business.

Reacting to changes

Fast-forward to 2018 and the WordCamp Tokyo, where we first got the chance to dig deeper into the Gutenberg project during contributor day. We knew changes were coming, and we needed to react with our business. Even before, we felt that building one theme after the other felt a bit tiresome and not like the most effective way for WordPress users to build their site design. We were never convinced by the page builder solutions, as it just seemed too bloated and untrue to WordPress core to bring a wow effect to us. We love to keep things flexible and minimal, and adding an entire framework on top of WordPress never felt like a great idea to us.

So here comes this Gutenberg thing, a promise to a more flexible, component based way of creating designs for WordPress.

We felt like this is meant to be for us. So once home from the WordCamp we started to build blocks and explore how this new WordPress would work. We did not realize back then how big these changes would become and how much it would impact our work and our business.

But it felt good to build something new and to try to find a better solution to offer for our theme customers. We struggled to gain footage for quite some time, as there were just so many new technical things to figure out and so much was unclear. But we still never doubted that we are on the right track, as with every new release the opportunities seem to get better and more stable.

And just now we are just about to relaunch our business websites with a brand-new block theme that is solely built with our blocks, WooCommerce blocks and WordPress core blocks. It finally feels like all the work comes together and themes and the Gutenberg project are ready to be merged into one and released for production.

Opportunity to pivot

During all these changes, we had the time to think about the future of our WordPress business and what we want our road ahead to look like. Many others around us have sold their independent businesses or took a job at one of the big WordPress businesses. I feel like it’s also a natural path of WordPress and all of us growing up.

For us, we feel like we are just getting started again, finally having found a way to have fun creating for WordPress again.

Building one of our last classic themes, we felt like we had lost the fun in designing for WordPress. We felt like themes were stuck, being either too inflexible and or way too bloated to be any good. It felt like we were trying to build, squeeze out a solution into a product that technically was never meant to be this way.

Block themes, the site editor, patterns, and blocks come as a chance for us to do it better. It’s a big shift and a difficult project to pull off, for sure. WordPress is used by so many people in so many ways. But block themes make WordPress lighter, and they don’t stand in the way of other add-ons as much as classic themes felt they were. It’s amazing how we can take all the components apart and mix and match them together. There are still missing pieces, but we are getting there.

For us, we are taking this shift that we are sort of making together with WordPress, as an opportunity to make things better. We always felt like we wanted to offer more support and help to our customers. But we never found the time. So with our upcoming relaunch, we are taking the chance to change that. We will offer new services and are exploring more ways to offer our customers what they actually need. It feels like a breath of fresh air to us, and we haven’t had so much fun with WordPress in a long time.

It’s funny, who would have thought that a piece of software can impact your life in such a big way.

WordPress has impacted where we live, who our friends are and which destinations we like to visit. We feel more open-minded because of WordPress, we believe in the power of open source projects and we believe that a group of people from all over the world can build something meaningful together.

The post Why small can be just the right choice appeared first on HeroPress.

by Ellen Bauer at January 11, 2023 01:15 AM

January 10, 2023

WordPress.org blog: WordPress is Turning 20: Let’s Celebrate!

2023 marks the 20th year of WordPress. Where would we all be without WordPress? Just think of that! While many technologies, software stacks, and fashion trends have come and gone throughout the past two decades, WordPress has thrived. This is due to the fantastic work and contributions of the WordPress community, comprised of thousands of contributors; and millions of users who have embraced the four freedoms of WordPress and the mission to democratize publishing.

Let’s celebrate!

Throughout the beginning of 2023, leading up to the official anniversary date of WordPress’s launch (May 27, 2003), a number of different events will celebrate this important milestone, reflect on the journey, and look toward the future.

Please join in!

Over the next few months, be sure to check WordPress’s official social media accounts along with the official anniversary website for updates on how you can be involved in this exciting celebration by contributing content, collecting cool anniversary swag, and much more. 

Use the hashtag #WP20 on social media so the community can follow along.

If you have something planned to celebrate that you would like to be considered for inclusion on the official website, please use this form to share the details.

by Dan Soschin at January 10, 2023 09:38 PM under WP20

Do The Woo Community: WooCommerce, Payments and Crypto with Keala Gaines and Dave Lockie

Keala Gaines from WooCommerce and Dave Lockie from Automattic chat about the relationship between WooCommerce and Crypto.

>> The post WooCommerce, Payments and Crypto with Keala Gaines and Dave Lockie appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at January 10, 2023 10:11 AM under Payment Gateways

WPTavern: Gutenberg Times to Host Webinar on How to Use New WordPress Layout Features

Gutenberg Times will be hosting a live Q&A webinar titled “Layout, Layout, Layout” on January 11, 2023, at 05:00 PM in Eastern Time (US and Canada) via Zoom. This event is open to WordPress users of all experience levels who are interested to learn more about how to use WordPress’ layout features when building sites with blocks.

Host Birgit Pauli-Haack will be joined by WordPress veterans Isabel Brison, Andrew Serong, and Justin Tadlock. Brison will be demonstrating different layout scenarios during the presentation, and attendees will be able to participate with questions.

Any user who has attempted to layout a design in WordPress has likely tried out container blocks that offer layout settings. These blocks include Columns, the Cover block, and the generic Group block.

The event will cover how to manipulate layouts by defining the width of post content, arranging blocks horizontally or vertically, right or left aligned, and inside container blocks.

“In terms of block styling, Layout is a complex feature because it affects child blocks in ways that go beyond CSS inheritance,” Pauli-Haack said.

WordPress 6.1 introduced more layout controls and flexibility in the block editor, but Pauli-Haack said the dev note on updated layout support was written more for developers.

“Feedback from users through the FSE program and other connections revealed that handling the layout settings for container blocks is not particularly intuitive and takes some trial and error to find the right combination,” she said. “The Live Q & A will bring a better understanding to users and #nocode site builders.”

When Pauli-Haack started the Live Q & A’s in 2018, she routinely brought in guests who were building the block editor, with the intention of having users meet them and discuss features like full-site editing, block themes, case studies, and discuss challenges.

“Since then, quite a few initiatives of the official WordPress project have come to life,” she said. “There is the highly successful Full Site Editing outreach program, spearheaded by Anne McCarthy, who now holds regular Hallway Hangouts with community members and contributors.”

People are also learning the ins and outs of site editing through the efforts of the training team, which began creating courses and lesson plans and hosting workshops on Meetup.com in 2021. These are also recorded and uploaded to WordPress.tv and YouTube. WordPress.org also launched a blog for developers in November 2022. With all these new learning opportunities, Pauli-Haack is changing the focus for her live events.

“For the Gutenberg Times Live Q & As, I am now looking at topics and discussions about more complex concepts, more case studies, and technology on the cutting edge,” she said. Most recently, the show featured the developers and digital strategies of the Pew Research Center, a high profile site that was built with a block-first approach.

“We are also in planning phase to hold a Live Q & A with the developers of GiveWP who are using Gutenberg as a framework to build the next generation of their popular donations plugin with the components and scripts that Gutenberg uses, but outside the post or site editor,” Pauli-Haack said.

She also has another Live Q & A planned with the WordPress VIP design team that works on design systems for companies that need a streamlined way to stay within their design standards. Pauli-Haack intends to talk with them about a plugin they created that lets designers automatically create a website’s theme.json file with all the styling pulled directly from Figma designs.

The upcoming Layouts webinar is free but attendees need to register to get the zoom link. An archive of all the past Live Q & A events is available on the Gutenberg Times website. The best way to stay informed about future events is to subscribe to Gutenberg Times’ Weekend Edition, as subscribers get an early invitation for the next Live Q & A’s.

by Sarah Gooding at January 10, 2023 03:37 AM under News

January 09, 2023

Matt: State of the Word

A few weeks ago, but what feels like a lifetime ago, I was in New York City with a few dozen extra special people from around the WordPress world. Alongside Josepha and the community we presented this review of how WordPress did in 2022, and vision for what’s coming:

by Matt at January 09, 2023 11:25 PM under Asides

Post Status: Support Inclusion in Tech with Winstina Hughes — Post Status Draft 136

In this episode, Winstina Hughes joins Cory Miller to talk about the  Support Inclusion in Tech project created to champion diversity, equity, and inclusion in the WordPress community by providing assistance to WordCamp speakers for travel and hotels.

Estimated reading time: 2 minutes

Transcript

Winstina Hughes  is a long-term community member and organizer within WordPress. She joins Cory Miller to discuss Support Inclusion in Tech, an effort to increase representation of minority and underrepresented speakers at WordCamp by providing needed financial support. This offers everyone in the WordPress community the chance to share their expertise and contribute resources so everyone has the opportunity to engage.

Top Takeaways:

  • Creativity is our common bond. WordPress is the playground where we all came to tinker and build for fun or business. It is the software magic where we discover what new things we can do each day, how to make ideas become reality, and how we might leverage what we learn to create a better world.
  • Ripple effect of inclusion: When you provide the ability for a large group of people to participate, travel, and network, the impact extends beyond the WordPress community to create the bigger changes we want to see in the world. This is our community magic.
  • Fifth Freedom in WordPress: We are all familiar with The Four Freedoms of WordPress. This is the 5th – full participation. Removing the financial barrier will bring us closer to the reality of being a truly inclusive community.

🔗 Mentioned in the show:

🐦 You can follow Post Status and our guests on Twitter:

The Post Status Draft podcast is geared toward WordPress professionals, with interviews, news, and deep analysis. 📝

Browse our archives, and don’t forget to subscribe via iTunes, Google Podcasts, YouTube, Stitcher, Simplecast, or RSS. 🎧

Transcript

Welcome to back to Post Status draft. I'm with a good friend of mine when Winstina hughes. I met with Winstina a couple years ago in the post status community. We've got to meet in person, talk numerous times, and, um, I'm excited about what we're gonna be talking about here. Um, she's got a new, a project called support inclusion in tech.com and we're gonna dive into that today.

But, uh, hi, Winstina. Hi. And pumped to finally have you on,

Winstina Hughes: I'm excited to be with you.

Cory Miller: Could you tell us what you do in WordPress?

Winstina Hughes: Okay. Um, What do I do in WordPress? every time I speak with, you know, every time I have one of these, um, you know, opportunities to speak with someone in the community, I end up like re repeating the question.

Um, cuz it really helps me. I am a community member, um, and I'm also, you know, a, an organizer, um, a meetup organizer and a board camp organizer. I started, um, going to [00:01:00] meetups in New York City and I transitioned into, Speaking, um, at Word Camp, New York City, and then I was invited to become a meetup organizer.

And so, um, my, you know, my participation in the community was, um, you know, like in the early, um, you know, 2010s. And then around 2015, 2016, um, I started, you know, speaking at, at New York City, and then I became an organizer. I meet up organizer. In 2018, I led my first word camp and my only word, camp , hundred twenties, um, a budget of 120,000, a team of 18.

Uh, it was an amazing experience. They were wonderful people and it was. Really tiring .

Cory Miller: Yeah. You know, over the years, Winstina, I've had so many dear friends that have been Word Camp organizers and really I go, oh my God, I love you so much because of what you're doing for the community. But I also go, I hope you [00:02:00] still like word this afterwards because it's a such a labor of love that I think, um, so often we don't really give the credit and thanks to the people, That do this voluntarily.

Yeah, like you're talking about all the stuff you're done. So anyway, I wanna say thank you because I've said it so many times to dear friends over the years going, thank you for what you're doing. I've always shied away from it because it's so much work and I see all the passion and energy that you and other organizers have and I'm really thankful cuz I think that is so critical to the entire community to have these, and now we're talking in 2022.

But we hear WordCamps are back. You and I got to see each other in San Diego at Word Camp US. Yes, yes, yes. So

Winstina Hughes: anyway, so Word, word camp Us. I was a co-organizer for Word Camp US this year. Um, and so yeah, you're right. Like we had a chance to teach other again there, and that was like, yay. That was awesome.

Cory Miller: It was, yeah.[00:03:00]

Yeah. A absolutely. Well, okay, so what drew you to, okay, how did you start with WordPress? Were you using WordPress for, uh, your own website, somebody else's website? How'd you get started with the actual software?

Winstina Hughes: So I started with WordPress in 2006, 2007. Um, I had a college course that was . Yeah, I, I had a college course.

Um, and our professor required us to add, um, you know, the work that we'd done, uh, into a wordpress.com blog. Um, it was a geographic information systems class. And, uh, we were looking at public health data at the census block level. Um, and so we were actually, you know, looking to see. You know, where, um, there were instances of like, um, I don't wanna say disease, but you know, like different illnesses.

And so what what's really interesting is that you can, that schools get access to that data and you can actually like, You can [00:04:00] essentially imagine, and I don't wanna go too far deep into it, but imagine you have like, you know, Google Maps, right? And like when you have Google Maps open, you can do street view.

So Google Maps lets you like go from that whole, um, like that map into like street view where you jump in as a person. So, uh, this data essentially took you away from just the geographic element, um, and the typography and like really. The census, you know, track level, like essentially, um, you know, looking at neighborhoods and, you know, the instances of disease in those neighborhoods.

And so he, you know, he gave that to us as our final assignment. Um, you know, we did some like, uh, some heat mapping to show where there were greater concentrations of a particular type of illness, , right. Um, or, um, you know, disease or, you know, Uh, I'm not exactly sure like what, what we [00:05:00] were calling it, but that's what our assignment was.

And, uh, he asked us to, you know, take like a picture of the map and to post it in wordpress.com and that's how it all started with that , with that assignment. Um, so we were you.

Cory Miller: We were using WordPress at the same time. That's the same year I started with WordPress when you started. I did not know you went that, that far back with WordPress.

So I love that. Uh, yeah, I do. Thank you. And then you said like in 2010 you started actually, uh, getting involved with community events. And this is relevant to us talking about support, inclusion and tech. So what drew you to start participating in volunteering and contributing to WordPress?

Winstina Hughes: So I went to New York City Meetups, um, and, uh, WordPress, New York City, uh, is the one that's in closest proximity to where I lived.

I could just take the train in. Um, and it was, it was great. Like I, I really felt, um, that the community there was, was [00:06:00] open, like the organizers were open and, and they were welcoming. Um, Dana, rendy, uh, those were organizers at the time, Steve Bruner, who was an organizer. Was he is the organizer, , he started it and he's, he's kept it, you know, um, really like strong, like, since its inception.

Um, and so like just going to these events and meeting these, these like wonderful generous people, these kind people, um, you know, meeting Kevin Cre, Christiana there as well. Um, and you know, just that environ. Was what led me to continue attending events. Um, and they really encouraged me to submit a talk to speak at New York City, um, ward Camp, New York City.

And I submitted a talk to speak there and, you know, since that time I've been more engaged in. Event organizing component, [00:07:00] um, or part of the community. So it moved beyond just, you know, um, Like learning, you know, to use Word Pro, you know, building sites and breaking them, uh, the best, right? Yeah. Like, that's the best way.

That's the only way you can really learn. I mean, I, I started, you know, with different hosting plans, I've had like four or five, like I have multiple domains. Like I think when you're in our space, you got a chance to really create. And, um, and that's what I was able to do and what I'm able to continue doing, and.

Now moved from just creating and building with WordPress to assisting with supporting, you know, our community through events like meetups and, uh, word camp organizing and supporting inclusion in tech is, is an extension of, um, of this work, this contribution that I've been doing. It, it, it pieces together so many different elements that I've come to, like I've come to see and I've come to understand [00:08:00] and. It's, it's a solution that I propose to, um, some current challenges that, um, I've heard being expressed. Yeah,

Cory Miller: I, uh, I wanna scroll back for a second and say that when you're talking about create, I sometimes it, for as long as you and I have been in WordPress sometimes forget that magic of being able to create something on the web or in the, in the world.

See this cool tool called WordPress, so I appreciate that. I think that's what we rally around in the WordPress community and particularly to post status is helping build tools and projects and things on top of this magical thing we call WordPress. So that was a, when you said create, I was like, it's just little tingle of magic came up of that's, that's why we, I think that's our common bond in

Winstina Hughes: WordPress.

I agree. I agree. And I think that, uh, when we create as community members, um, and not necessarily [00:09:00] just as. Business owners or, or, um, you know, those who are providing like services. That's a component of creating. But, you know, in the middle of doing all that, I think, you know, I mean, I like to sit down and just literally play and see, you know, what could I do with it today?

and, um, I entered a com competition, um, held by Sustainable New Jersey, um, right around the time I completed graduate school. And there were municipalities that were seeking, um, solutions for challenges that they had. And there was the city of East Orange and they wanted like a marketplace, um, and a place for their planning department to, you know, add their documents and also something for their green team.

And when I saw this, I was like, I could use WordPress and e-commerce. So I created like a WooCommerce marketplace for them to sell, you know, for residents that would sell their products and services. And I demoed it. Um, and then I also had a website and also a Buddy press site. Um, and the buddy press site would be for their green team members.

And I think that [00:10:00] like, when, when we create with WordPress, like we're able to like see like, you know, These asks and really apply like our knowledge of what we know the c m s can do and then provide a solution. And the city was actually really happy with the solution. Um, and I made it to the finals of the competition.

Um, but there was another, uh, but there were other teams that that won it. Um, but it was, it was really exciting to show what WordPress, you know, software and what WooCommerce can. Uh, that's the

Cory Miller: dream. Um, that, that's so awesome. Thank you for sharing that backstory. As much as we've talked and stuff, I haven't got the chance to ask those questions and, um, it's a good reminder for me about, you know, I think if you go long enough in the community, you start to, well, I, I'll say I start to.

Forget some of these nuances, [00:11:00] like being able to go, here's a project idea, this could be done in WordPress, you know? And that the tools are mostly freely available. Yes. And you can start and build something online.

Winstina Hughes: Exactly. Yeah. You just, you know, download . Yeah. Yeah. Well, yeah.

Cory Miller: So that leads me to support inclusion and tech. And you mentioned you saw a problem or problems and challenges in our community that you wanted to help make some a solution to toward it that became support, inclusion and tech. But can you talk about that a little bit? Cause I know my, my understanding and you continue to help me expand my understanding of all this is it's not just one particular country with DEI, it's a global thing. But could you talk a little bit about the problems and challenges that you saw in the space.

Okay.

Winstina Hughes: Absolutely. Um, absolutely. So I, you know, really wanna, like, I wanna hold true to like, um, to how [00:12:00] I, um, shared it on my website. Um, but really the backstory is that. There was a conversation that erupted on Twitter, um, about the need for more diversity on Word Camp, um, organizing teams. And this started, uh, due to, um, you know, uh, some, some thoughts that were expressed about Word Camp Europe, uh, where WordCamp Europe's organizing team, um, not being.

Very reflective, um, of, you know, more ethnicities or a wider range of them. Um, it was a really difficult conversation that was happening. And my take on it really is that it's not where camp you're specific, right? Like, I mean, let's, you know, let's really step back and think about the fact that, you know, there's so many ethnicities around the world that have a ch [00:13:00] like it's really.

When you're in the minority as a group, Really up to the group that's in the majority to weave you into those experiences and those opportunities. Um, and when that doesn't happen, then you have groups that don't have an opportunity to be, to participate and to be involved and, you know, support inclusion and tech.

I mean, considering this was a conversation about word camps and our participation in them. Support, inclusion and tech really seeks to assist us in solving the challenge of, um, not having as much, you know, ethnic or, um, or just diverse representation within the Word camp experience. It doesn't seek to, you know, um, it doesn't, it doesn't seek, you know, to like solve, um, Like these, you know, the world that we [00:14:00] live in.

And it doesn't seek to solve like, um, you know, diversity and inclusion outside of the WordPress space. Um, but I believe that in, in providing these, um, these opportunities within our community, since we're so large, that the ripple effects can extend well beyond the WordPress community. I believe that when you, Absolut.

When you provide such a large group of people, the ability to, um, to participate in work camps, um, the ability to travel to them, the ability to network to them with, when you attend, um, the ability to like, you know, seek, um, you know, out more relationships, friendships, professional relationships. Then there's this ripple that extends outside of our community and I think.

That level of empowerment can extend outside of WordPress and those ripples can assist us in diversity inclusion beyond, [00:15:00] um, you know, our, our involvement in WordPress. But you know, this, this particular solution is intended to solve the challenge that I saw, you know, um, being expressed, you know, within our community.

And so the thought is really, Since, you know, since there's a take on it. And there's, it's a, I mean, it's an, it's an honest one, right? We don't see enough people of color. We don't see, um, enough, you know, people of, um, other minority groups, um, you know, uh, from other parts of the world. Um, You know, we are seeing an equal, more equal balance of, um, men and women.

Uh, you know, but when it extends beyond that into like, you know, more representation in terms of like, you know, a wide range of religions, which ties to ethnicity often. Um, and when you're looking at representation in terms of those of us who, um, have like neuro [00:16:00] diversion, you know, um, you know, like, uh, characteristics and those of us who, um, you know, who we choose to love, , you know, the what society, um, you know, asks of us , right?

Like, and um, and when we choose to hold true to that or when we're dealing with the physical limitations, um, that, you know, that we were born with or when we're in minority. Groups, you know, that have a harder time, you know, uh, receiving opportunities, um, to participate and to increase, you know, their reach and even, um, you know, the professional opportunities that are available to them.

You know, like this. What can we do to, um, to really like solve. To solve that. Mm-hmm. And I thought, what could I do within our community Yep. To, you know, to integrate, you know, like all of those of us who are, um, Either, you know, disadvantaged [00:17:00] or not as represented into WordPress programming and support, inclusion and tech, um, seeks to, you know, take away that financial barrier, which I believe is really what, you know, can limit our participation.

We want to participate, we want to speak, but if we can't afford to speak , right? I mean, if we can't afford to travel to the conference and if we can't afford a place to stay at the conference, um, then. Like, why would we even think to apply to speak at the conference? Right? Like,

Cory Miller: yeah. That's, that's really beautiful, Winston, because, um, there's a couple of takeaways I, I got from this.

Number one is, I, I've always believed, um, at least in my world, that WordPress has been. The, an inclusive place, ever growing inclusive community. That's like a mirror to my world, the way I want my physical world here in Oklahoma to be. And I have [00:18:00] so much learned from our community leadership, uh, over the years, um, that there's a cons.

Consistent push and drive from the entire community and the leadership to be truly diverse, truly inclusive in all those words. And I, I learn a lot from this. Um, so the mirror I, and I do think WordPress is, our community is so powerful cuz we're distributed all over the world. So if we make change in our community, in our WordPress, That should be, that should be reflected.

And I think that's another, we talked about the software magic. This is the community magic. Exactly. Uh, the other thing is, I, I love and I respect because I try to take too much on that, you said, Hey, here's something I'm passionate about, being an organizer, being at these community events, how special and valuable they are to you and other people instead.

I'm gonna make this dent first. Yeah. Like, I'm gonna, I'm gonna take on this aspect first. You. Beautifully and clearly [00:19:00] shared. This is the thing I'm trying to take on in this bigger, bigger, um, change that you wanna see. We wanna see in the world. Thank you. Okay, so we've got this now we've got a website. Um, you've got a website up to kind of share this.

Now. Take me through, if you would, I am, pretend for a second you're talking to someone that is in an underrepresented, uh, in, in tech. Of, um, situation. Mm-hmm. , how's the process to, to get on the, Hey, I want to go to these WordCamps. I want to speak, but I do need some assistance. What does that process look like for, for support inclusion and tech?

Winstina Hughes: So support, inclusion and tech. Um, also weaves into other initiatives in order to, to assist our speakers. Um, and so when you're accepted, support inclusion tech, it become, moves into the position to, to assist you once you're accepted into [00:20:00] Word Camp. Um, as soon as you get that, you know, acceptance, you know, go to https://supportinclusionintech.com/.

Um, and you're simply just, you know, gonna put in the word camp that you were accepted in. And then there are two components, um, in addition that they're suggested , right? Like you're encouraged to do this. Um, you know, uh, we're in the community of consent and so, um, you have, you know, um, You're gonna give, you know, the consent to be included in these other initiatives, um, you're not gonna be forced into it.

Uh, there's underrepresented in tech and there's also the WordPress diversity, speaker channel. Um, both of those, uh, are ways of. Further supporting diversity and inclusion and representation within the WordPress space and creating, you know, um, you know, successful opportunities for us to, um, to, you know, to put together great speaker applications and then to also, um, you know, move beyond just submitting [00:21:00] them. Um, but to being accepted.

The, the ask is that, you know, once you've been accepted to camp and you're starting the process of, you know, receiving funding through supporting inclusion and tech, that you also participate in those other two initiatives as well. Um, because you know, in the process of doing that, it's further supporting the work that we're doing in the WordPress community. Exactly as you said, Corey, that, you know, the word WordPress leadership already has been putting in, um, you know, the work to, you know, to assist us in resolving the challenges that face society as a whole. And so there are initiatives that currently exist and those two in particular, I think.

You know, are ways that we can continue to support underrepresented minority groups in the WordPress community. Um, and so in the process of, you know, uh, applying for the funding, uh, you're encouraged to, you know, to list yourself on underrepresented tech to join the, um, the, the diversity speaker channel [00:22:00] on make WordPress.

Um, and then once you've just put on, put that information in and you've identified the type of support that you're seeking, um, you just like, and it starts from there. Like I start, um, you know, pairing you with, you know, with a partner that you know can, can step in and provide, you know, the funding for you.

And so, you know, they're gonna cover your travel and they're gonna cover your hotel. Um, and that way in order for you to participate, you're not going to be paying anything really that you know, out of pocket. For that participation, um, in that WordCamp. And that's really the goal. Um, the goal is to remove the financial barrier to your participation.

Cory Miller: Yeah, that's fantastic. By the way, I wanted to sidebar for a second and say underrepresented in tech, uh, by Allie and Michelle Frechette. If, if you're listening to this and, uh, you also as a be becoming a member of underrepresented in tech, get a free [00:23:00] uh, professional membership at post status?

Winstina Hughes: Yes. Yes. I started, I and let's not also forget too, that like there are other opportunities as well as Post Status has been, um, you know, looking into as ways of increasing, you know, diversity and representation within the Post Status community. Um, so underrepresented tech and that membership, and I know that there's some other ways that you're working on it too, Corey.

Um, you know, I think, I think when we can pull all our efforts together. We have a stronger community. Um, and you are, you know, you're, you're offering that and then supporting inclusion and tech, you know, encouraging, you know, speakers to, to register and to participate in those two other programs. Strengthen all our efforts. Yes. Um, and, and that's, you know, that's the process of it. And so once you've submitted, you know, your. once you submitted that form, you know, just letting me know, like the speaker registration that you're seeking, the [00:24:00] support. Um, you're also gonna complete the blind directory listing and that blind directory really.

That Blind directory listing has the word camp that you'll be speaking at. Um, and it has the type of support that you're seeking, whether it's just beach travel or hotel, or both, and that's it. Um, no one in the community, um, you know, needs to know who you are. They don't need to know what your need is. Um, they don't need to know where you come from.

And they don't need to know what makes you underrepresented and what makes you a diverse speaker. Uh, it's simply a way for, um, for companies that are considering sponsoring to see that the need does exist. And it's also a way for our community to see that the need does exist, um, and that we do have members that are seeking the support.

Um, that, that blind directory listing is, is just a way, you know, for our community to see that, um, that our need is there. Um, yeah, and it's also a way of, um, uh, [00:25:00] keeping everyone up to date on the work that's happening.

Cory Miller: So I know we'll have two asks. The first ask is if, um, you need assistance, want assistance to go to a WordCamp to be sure to go to supportinclusionintech.com?

Winstina Hughes: Yes. Once you've been accepted, go to supportinclusionintech.com. Complete the form for speaker registration, and you'll, um, you'll be paired currently, um, with four companies, uh, that, um, that have partnered to work on this.

Cory Miller: That comes to our second ask. Yeah, that's right. Okay. So tell me how, um, now this is very relevant for post status because we're a bunch of professional and business members in our community.

So the second ask is, we need someone, one, participants, people that need and want assistance go and speak at Word Camps. And the second part of this is the sponsors and partners. Can you tell me a little bit more, more about that and [00:26:00] how that.

Winstina Hughes: Okay, so starting off, partners are sponsors, , um, partners are the first, um, you know, companies that expressed an interest in supporting this project.

Um, you know, this initiative. Uh, and so like that is my way of thanking you, um, by, you know, by acknowledging. that you came into this, um, wholehearted and opened armed. And so thank you to the four companies, um, that have done this, uh, that have stepped forward to say that they will support. Um, you know, it was really exciting once the call went out, um, from Word Camp US that they were seeking, uh, support for underrepresented.

Speakers. It was really exciting because Master wp, um, stepped in at that time, you know, to say that they thought that this was a great project. And, you know, they're the fourth company they joined, um, GoDaddy, Post Status, and Yoast, um, you know, the original three that said that, you know, that they would love to support this initiative.

And so, um, now we have, [00:27:00] we have four of them and there are also several companies as well that are providing in-kind donations. Um, and, you know, they're doing so, makes it possible for support, inclusion and tech, um, you know, to, to function, right? Because like, you have the website and then there are all these different like plugins that make it functional and make it possible, you know, for, um, for, for it to run and function the way that we need to.

Um, so if your company that wants to. Sponsor speakers, you know, you just have to go to the site. Um, there is a section there for you to register your support, um, your register, your desire to support. It'll ask you, um, you know, to provide, you know, like a contact. Um, it'll ask you the type of, uh, How you want to provide this support.

Um, would you prefer to reimburse speakers for their expenses or are you, um, ready and, you know, willing and able to pay for their, um, their travel and their hotel in advance of their trip? [00:28:00] Um, so, you know, once you've identified your contact, you know, your contact is the type of support that you want to provide, you know, then, you know, we'll have an opportunity, I'll have an opportunity, you know, to really. Sit down with you and for us to have a conversation about like, you know what would be your process, you know, what would make it easy or for you to be a part of this initiative? Um, this isn't a cookie cutter means of support for, for companies, because you're all different.

Um, how GoDaddy, you know, is providing support is different from how Post Status is providing support is different from how Yoss is providing support. And it's different from, you know, how, um, Master WP is and, uh, When I started this, and I, you know, I, and I wrote on my blog, like, really this proposal on https://winstinahughes.com/.

I went into it, um, you know, with the understanding, personal understanding is that it's gonna [00:29:00] take a couple years to understand the needs of our community and the ways, you know, companies and our ecosystem can support these needs. And in the last six months, Exactly what I, you know, anticipated, um, is what I've been able to, you know, to, to see.

And, you know, currently, um, there have been three, you know, requests, um, for, you know, to participate, you know, um, for funding, for support, for camps and, um, two unique, you know, individuals have, have made those requests. Um, and you know, so right now it's a question of. You know, like assisting them, you know, with the process of how, you know, our four partners, you know, can support them in that way.

Um, and I think that answers part of your question. Um, the second part of the question is like, so how is this financial component gonna work? Right? [00:30:00] Like, are companies giving me money? No, you're not , like, I'm not receiving, you know, um, any of the money. Is the financial support that you're providing. Um, instead it's looking at your company's processes, um, you know, your, your financial processes, your accounting processes for you to, you know, step back and think like, how could we as a company provide this level of support?

Um, you know, it could be that you already have an existing program. Yoast already has a diversity fund. Um, and so Yoast partnering with me is a way of, um, you know, kind of bringing the need that exists to them as well. Um, and so therefore they're able to like further serve the community, um, you know, through those who are expressing an interest through support inclusion and tech.

Um, the way Post Status, you know, is seeking the support speakers too, is different from Yoast. Um, and, you know, uh, [00:31:00] Yoast has a budget, um, and.

Has their own system and their own ways of support. Um, and so they also have a budget and then Master wp, they also have a budget. And so once that budget has been met, then you know the partners essentially gray out for that year. Um, and they become active the next year. Um, and so. , that is a way of making this sustainable.

You know, you, you pledge how much you can support, um, speakers financially, and once that has been met, then your, I mean, your capacity for the year is, is, is met. And then next year, once you've reallocated your budget, or not re reallocated, but once you've defined, you know, your budget, um, for the year, then you would go, you know, back into the process of supporting [00:32:00] speaker.

Cory Miller: And I wanted to say from personal experience here, that there's many way, there's, there's creative ways to support these speakers, uh, to go, you know, uh, you, you talked about hotel and flights. Yeah. And, um, I, I wanna, I wanted to say that one standard to say this is not an unapproachable. Opportunity to support d uh, diversity inclusion in tech.

Um, this is very manageable for most members at Post Status, by the way. So, you know, flight costs, uh, depending on where it is in the world. Um, I think the first question you asked me was, what's your budget? Yeah. And that's a great way. So as you come in and click sponsor, just be thinking of these things with when st for how you can.

Help support this amazing project. Um, and that there's creative ways to do that. And I, I think Winstina, most members, business members at Post Status can make a meaningful contribution in this way [00:33:00] through this, your project here. And I love the fact also, I know we talked about this too, you wanted to be real careful.

You wanna say you want the support to go to the person as best as possible. A lot of nonprofits have overhead. You have graciously generated your time and your talent to this project, and I, I, I love the way you've done it too, even though I go, gosh, Winston, I love that you have this passion. Um, but thank you so much for this.

But I know you give of your own time. For this particular project, but as you talk to Ena, if you're listening to this now, there's creative options and ENA is so good at helping you, helping understand where you're at, and then pair it with people that need assistance.

Winstina Hughes: Thank you. Yes, and that is, that is the goal.

In terms of my contribution to the WordPress community, burnout is so real and because of the fact that I work full-time outside of the WordPress space, the WordPress ecosystem, um, I'm really [00:34:00] cognizant of the fact that I need to perform well. And at a high level , right? Uhhuh , um, at work, you know, and in my personal life.

And WordPress fits into, um, you know, into that. And so I've been able to contribute in different capacities since I was in college and. Graduate school, first attending in college, um, or post-college in graduate school, moving into speaking and organizing, um, and now working, you know, professionally maintaining, you know, organizing as a meetup organizer and a WordCamp organizer, and understanding that this can really lead to burnout.

You know, um, my ultimate decision is, you know, that for the next two years, I'm not gonna be a WordCamp speaker, and I'm also not gonna be a. Organizer, you know, this, these are the ways that I can, you know, I can continue to contribute. I can contribute through support, inclusion and tech. Um, you know, but really pair, pair down all the other ways that I could burn out.

[00:35:00] And so by maintaining, Being a New York City meetup organizer and hosting at least a minimum of six meet meetups a year, and, um, really pivoting and concentrating my energy towards support, inclusion and tech. I can sustainably contribute to the community. And so this is a perfect opportunity to really share with you, um, that, you know, I want to meet with every speaker.

You know, that expresses the interest for support. So as you submit your, you know, your speaker registration and you join the directory listing, I will, um, you know, I'll ask to meet with you, for us to have a conversation, for me to understand your needs and to share. what it is I understand and I've learned over time, and also how our partners seek to support.

So we'll have that conversation. It's gonna be on the weekend. I hope you graciously incorporate that into your schedule. Um, because, you know, I, I work during the week, [00:36:00] um, and so, you know, we'll meet once. Uh, hopefully within a week or two of your registering as soon as possible. Especially it's, it's, it's ideal, uh, not ideal.

It's encouraged to register as soon as possible, um, because the closer you get to your ward camp, you're gonna. Most likely, um, be reimbursed if you apply much sooner, like a, like two or three months in advance. You know, there are companies that will be able to, you know, cover your, your, your costs, um, of participation in advance of your trip.

If you are reaching out like three to two. You know, to the time of, of your support that the time that you need, then you're looking at being reimbursed for your expenses. And so like, you know, that's, that's something to, to keep in mind when it comes to registering, you know, for this is that companies will be able to assist you with removing this.

It just might be [00:37:00] later. When your need is expressed closer to the time that you're speaking that it's more, it'll be a reimbursement instead. Um, and so that's something to keep in mind, the timing in which you submit your interest, and also the fact that, um, you know, that we'll be meeting on a weekend. Um, there's this speaker that just registered and he wanted to meet with me.

Um, On Christmas, he's in another part of the world. I mean, you know, like, so yeah. Um, and so I just, you know, I just like, I think when, and I had a con, you know, I just like responded and let him know that it's, it's Christmas for me. I'm, you know, I'm a Christian and I'm so celebrating my holiday today. Um, you know, and, you know, like, uh, let's, let's meet next week.

Um, so, you know, uh, we'll have like, you know, we'll have these conversations and we'll, we'll see. And you know how. Um, you know, how you and I can, can have that conversation and [00:38:00] meet and how your need can be met. And I'll also meet with, you know, companies that wanna sponsor as well. And I wanna tell you, I want you to tell me what's realistic for you.

Um, I want just, just to, just to give you a sense of how some of the companies are. In fact, um, you have, uh, of the four partner. You have one partner who seeks to provide support, um, you know, within the us. Um, as of our last conversation, you know, the desire is to support minority speakers, um, specifically people of color, um, specifically, you know, black Americans, um, to improve or those of black descent to improve, um, their numbers.

WordCamps in the US. Um, our last conversation was, you know, this is the direction that they wanna go. This is the greatest impact that they think that they can achieve. Um, and [00:39:00] I'm, I'm so glad that I get to listen to what everyone. Hopes to do, you know? Um, because it gives me a sense too that our community is really thinking through, like, this is how we're gonna solve it, right?

Like, this is how we're gonna make the dent that we wanna see. So this company already knows this is how we're gonna make the dent that we wanna see. And there, there. Process too, is that they're just gonna give you a blanket amount of money and they're not gonna micromanage how it is you spend it. Um, they just simply ask, you know, that you, not simply, the requirement is that you put it towards your WordCamp experience and that's where they are with it.

Um, there's, you know, another company host of course, has an established diversity fund and they have processes already in place for the support. And so you're simply gonna go through the existing process that, um, Yoast has established and they have a generous fund. Um, and their support, um, is something [00:40:00] that they've been offering the support for a long time, and they're very, um, they're really respected , you know, for that effort.

And, um, I've had an opportunity to like, you know, to speak with someone who has been a part of their support in the past or received it and they speak so highly of, of Yoast um, and that's, you know, Yoast has already thought it through and they've already walked through. You know, Corey and I, you and I have spoken about, you know, the budget, you know, that you're, that post status is set aside and, and you've already shared.

You know, what is the need? Like, we're not micromanaging, right? Like, let us know what type of support that you need, and we're just gonna provide that to you. Um, and so like you're, you are already thinking about like, how can we make this happen? Like, you know, if you need to, you know, it's a flight, you know, wherever it is.

It doesn't have to be domestic, right? Like, it doesn't have to be in the us it could be anywhere in the world. Um, and, and that's, you know, that's like, [00:41:00] Post Status is thinking, and then GoDaddy is currently working through their process. Um, and I do believe that because of the fact that they have teams around the world that GoDaddy's reach will also be of, um, I think GoDaddy's reach will also extend beyond like the domestic, you know, like within the US and they'll be able to provide support as well toward camps.

you know, around the world. I'm anticipating it's possible that, um, GoDaddy's like impact could, you know, be especially strong with, um, Uh, WordCamps, like Word Camp Asia or Word Camp US or Word Camp Europe. Um, you know, because they'll have team members there and when they have team members there that can help facilitate and smooth the process over for, for those that they're going to be supporting, but they're working through their processes to make this established as well.

And so I think [00:42:00] that, you know, just by me sharing that, you can tell that, you know, each of, you know, my partners are, are working within. Um, you know, like their business processes and their financial processes and also their vision for impact. Um, and I think that's really important.

Cory Miller: So to recap, here's what I've heard.

So support inclusion and tech.com is the bridge between those that want have the desire to share their exper experience and expertise at word camps, but need some financial assistance to get their flights and hotel. That's what f support inclusion and tech.com does. Second, as a participant, as someone.

Um, if you first need to apply and get, uh, approved to speak at work camp, then come to support inclusion and tech.com and, um, sign up, have a conversation.

Winstina Hughes: Mm-hmm. , once you've been approved.

Cory Miller: Have a conversation with we, Tina. [00:43:00] And then third, the third recap is our ask for, um, well buzzer asked in our community.

Uh, if you're looking to speak to Word Camp, go to support inclu or go apply, get approved, come to support inclusion in tech. And then second for those businesses out there. You know, you have a heart, you wanna support this. That's our community. That's who WordPress is. Uh, go to support inclusion and tech.

Click on the sponsor link and have a conversation with ena. Think about your budget. Think about what you wanna do, uh, when Cena is so creative in helping just make these connections happen so you can really make a difference in our community. Did I get it all right?

Winstina Hughes: You did. You did get it right And, okay.

And I think that support inclusion tech also. It goes through vetting process as well to confirm that those who are seeking assistance, you know, to participate actually have been accepted. And that's why, that's why the steps are what they are. Um, partners aren't gonna [00:44:00] question, oh, is this need real? You know, that vetting is gonna happen in advance.

So when you receive a speaker interest, You know that this is someone who has been accepted a Word camp, and they understand the process and they're working within, you know, your, your policies and your procedures, um, in order for them to participate. So it removes all those questions. Um, you know, so that and that, yeah, that's a part of it.

Cory Miller: Well, Winston, my friend, thank you so much for this important work, uh, holding the banner up. I know this takes a lot of time. I know you've got a full-time gig. I know you've got a life

Winstina Hughes: more,

Cory Miller: um, But I so much appreciate you post. I just appreciate you, our members do for doing this vitally important work and making a difference in our world that can, like we said, can be a reflection in all these thousands of communities we go out to, to say, how can I be more inclusive?

[00:45:00] How can I make sure everybody is represented as at least an opportunity to be represented? So I really appreciate you, Winstina, and your work and also just ringing the bell with me and teaching me and sharing, um, how we can make, make that difference. So I appreciate. Thanks for being. I'm thanks for being on.

Winstina Hughes: Sorry. No, no. I mean, I absolutely, like, this gives me life and it makes me wanna show up in the world, you know, different and energy. I wanna exercise more like , you know, like this is, this is, this is really in a lot of ways just like giving me energy to contribute. And so, um, to like, just to be able to like, work with you, you're, you're, you know, I'm, I think you're awesome

You know that, ditto. You're, you have a beautiful family. You know, like your energy is like, you have such great energy and so just a chance to work with you and like the amazing people that I've had a chance to, it, it just, it gives me life and it makes me want to live more, you know? So like, let's, let's [00:46:00] see what we can do to continue to support our community so that the four freedoms, you know, I think that it's, , it's creating a fifth freedom, which is, you know, for all of us to be able to participate in a truly inclusive, um, community.

And, you know, that speaks a lot to what the co-founders of WordPress. I think, um, you know, what, what they created and, and where they want, um, what their vision is and, you know, from their vision where we're, um, going and or how we're evolving as a community. I mean, to have 40% plus of a reach on the.

There's so many people around the world that are impacted by this project, you know? So, um, yeah, I love

Cory Miller: that. Let's, let's add the fifth Freedom. I love that win. Coined by Win, and I love that leadership vision for our community. We need it. Thank you. Thank you, ma'am. You have a good rest of your year and we'll see you in the next year.

For everybody listening, thanks for listening. Tune in, go to support inclusion in [00:47:00] tech.com, and also Winstina Hughes is in our post Slack community. So you can go at Wednesday and you can ping her and, um, get the conversation started there. So thank you, Eena.

Winstina Hughes: Thank you. Thank you, Brent.

This article was published at Post Status — the community for WordPress professionals.

by Olivia Bisset at January 09, 2023 07:17 PM under Yoast

Do The Woo Community: Do the Woo is Headed to WordCamp Asia

We are looking forward to attending WordCamp Asia and also are proud to be a media partner this year.

>> The post Do the Woo is Headed to WordCamp Asia appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at January 09, 2023 10:19 AM under WooBuilder Blog

January 07, 2023

Gutenberg Times: Gutenberg Changelog #78 -State of the Word, WordPress 6.2, Gutenberg 14.8 and 14.9

Birgit Pauli-Haack and Hector Prieto talked State of the Word, Gutenberg releases 14.8 and 14.9, WordPress 6.2 and beyond. 

Show Notes / Transcript

Show Notes

State of the Word

Gutenberg Times Live Q & A

Gutenberg Times Live Q & A: January 11th at 5 pm ET / 22:00 UTC Layout, Layout, Layout.

Isabel Brison’s talk at WordCamp Asia

WordPress and Gutenberg Releases

Stay in Touch

Transcript

Birgit Pauli-Haack: Hello, and welcome to the 78th episode of the Gutenberg Changelog podcast. In this first episode of 2023, I wish all our listeners a wonderful, happy, prosperous and healthy new year. In today’s episode, we will talk about Gutenberg releases 14.8, 14.9, WordPress 6.2 and beyond. I’m your host, Birgit Pauli-Haack, curator at the Gutenberg Times and WordPress developer advocate, a full-time contributor to WordPress Open Source project. My guest today is Hector Prieto, full-time contributor on the WordPress Core team, coordinating multiple WordPress and Gutenberg releases. And it’s a great pleasure to finally have you on the show, Hector. Having a conversation about Gutenberg and WordPress with you is a wonderful way for me to start this new year. Happy New Year, feliz año nuevo, Hector. How are you today?

Hector Prieto: Happy New Year. Hi, Birgit. I’m excited to join you on the podcast. It’s my pleasure.

Birgit Pauli-Haack: Oh, the pleasure is really all mine. Where are you right now? Did you have a great holiday break?

Hector Prieto: I’m currently in Alicante in Spain, very close to the Mediterranean Sea. And today we have a lovely sunny winter day with nearly 20 degrees Celsius. I had a few days to recharge and spend time with the family. What about you, did you enjoy your holidays?

Birgit Pauli-Haack: Yeah. Well, that’s some warm weather there in Alicante. I would love to have that. But here in Florida it’s balmy, too. It’s about 27 degrees, so we are in the air conditioning right now. Yes, my husband and I, we spent the week in Mexico City between Christmas and New Year’s. We saw some great art, powerful murals from the ’50s and ’70s and ’60s. And we had fantastic food and a fabulous New Year’s event. It was great, at a restaurant over the roofs of Mexico City, so we really liked it.

Hector Prieto: Wow, sounds really nice.

Birgit Pauli-Haack: Yeah. Well, Hector, as you are the first time on the show, maybe you can share briefly with our listeners your WordPress origin story. When did you come across WordPress the first time and what do you work on now?

Hector Prieto: Well, my first time working with WordPress was around 2015 when I worked at the startup agency building sites. However, it wasn’t until 2020 that I first moved into the contributor space, and here we are. I am currently sponsored by Automattic to work full-time in Core in project management-related duties and supporting the development of WordPress.

Birgit Pauli-Haack: That’s wonderful. Well, thank you. So 2015, that’s just about two years before Gutenberg was introduced into the community. Did you, at your agency, have Gutenberg on the radar already, or did you heed the call to learn JavaScript deeply?

Hector Prieto: It wasn’t until 2018 that we started using Gutenberg for the first time, when it was first released in 5.0.

Birgit Pauli-Haack: Yeah. Then the time between learning about WordPress and then starting contributing, that’s about five years. That’s pretty much the time that it took me to really embrace the contributing on WordPress, but I started at the Community Project in 2014. 

Announcements

All right, so there are a few announcements that were happening since the last podcast episode. If you haven’t watched it yet, the recording of Matt Mullenweg’s State of the Word is available on WordPress TV. The transcript and answers to the questions that didn’t make it into the recording can be read on the follow-up post, State of the Word Reflections. Josepha Haden Chomphosy kicked off the State of the Word with a reminder on the four freedoms of WordPress, that you are free to run the program, you’re free to study and change the code, you’re free to distribute your code and also redistribute WordPress.

She also recorded a separate WP briefing with her reflections in episode 45, State of the Word Reflections in which she highlights, among other things, learn WordPress, that 12,000 students actually went through the courses and the workshops already since the inception. And she also highlighted the WordPress Playground, which is a tool to run WordPress in the browser. You don’t need a server, you don’t need a database. You can run it in the browser and test plugins and themes. I think that changes how we approach some of the discovery for WordPress. We talked about it on the show here as well, but it’s definitely something that will have so many ramifications in the WordPress space later on when it’s still very raw and very not production ready. It’s just an idea that has already a proof of concept. And then the recap posts from the community are linked in the Gutenberg Weekend Edition 239 from December 17th, and you can check it out from there.

I also have a side note that the Pew Research Center received a shoutout for the politology quiz that they built with blocks and had one million people already taking it. Seth Rubenstein is the lead developer and was a guest on a Gutenberg Times Live Q&A last year. And he gave a great demonstration about their team’s work with the block editor, so as they went for the Gutenberg first approach building the website. The recording is available on the Gutenberg Times YouTube channel, and also we have a post here on the Gutenberg Times website as well. So as always, all these links are in the show notes of the 78th episode. So Hector, do you have any comments on this? What is your most exciting topic from the State of the Word? You had a few takeaways?

Hector Prieto: Yeah, there were a handful of them. I would actually highlight everything, starting with WordPress Playground. It’s such amazing technology and it’s going to open so many doors. But if I had to pick something, maybe for me because it is the thing I’m the closest to, it was a great recap about the progress WordPress made in the site editing front during the last year, to the point nowadays we can create themes directly in the editor just with blocks and patterns. This brings us very close to wrapping phase two and starting exploration around phase three in 2023. So it’s great to see that all these progress.

Birgit Pauli-Haack: Yeah, you’re right, you’re right. And it’s been such a long journey as well. I look back at some of the history on the Gutenberg Times and the Gutenberg podcasts, and we first started talking about full-site editing in January of 2020. That was even pre-pandemic, and we had quite a few developers on our live Q&A talking about the first concepts about that. So now, three years later, it’s almost finished and it’s really cool. There are still some things to be done, but I am really excited about the start of phase three of collaboration and I have been constantly trying to unify all the various tools and methods and interfaces to streamline my workflow to produce content for the web. And if I don’t have to use multiple tools to collaborate with people, I will have arrived on internet nirvana. Yeah, it’s a high calling of course, but yeah, we are all in a space where we could maybe make it happen. So I’m really excited about that.

Hector Prieto: Yeah. Also, it’s worth noting that even when we move to phase three and we can call a wrap on phase two, phase two will not be fully finished because there’s always going to be things to do related to site editing improvements, new tools. So I can see contributors working in new features for phase three and also iterating on phase two items. Another big takeaway for me during State of the Word was seeing how much Gutenberg itself has matured. And it’s now been used in more projects such as Tumblr, bbPress, and even in some mobile apps like Day One. Also, let’s not forget how WordCamps have made a comeback after COVID hit and stopped all the in-person events. And we went from one single WordCamp in 2021 to up to 22 in the last year, in 2022. That’s amazing.

Birgit Pauli-Haack: Yeah, that’s a nice iteration of the numbers. 22 WordCamps in ’22.

Hector Prieto: Exactly. Especially since the community is what makes WordPress what it is, it’s the most important part of WordPress. So that’s really good to see.

Birgit Pauli-Haack: Absolutely. Having the first WordPress in-person event in WordCamp Europe, I realized how much I missed interacting with everybody else in the community and seeing new faces and interacting with old friends. I looked up the number of WordCamps that were done in 2019, in-person WordCamps, and there were 148, or 145, something like that. So there is quite a bit of time to go between 22 to 142 or something like that.

But it’s coming back especially because all those WordPress meetups, the local meetups, are all coming back as well. I think there was a note in the State of the Word that out of the 500, 260 have already come back to in-person events. And we know that WordPress meetups are actually the prerequisite to actually have local WordCamp organizers together to organize a WordCamp. So yeah, it’s all coming back and I’m glad that it’s coming back because of the connection that you have in the community. Yeah.

Hector Prieto: As I mentioned earlier, I came to the contributing space in 2020. It was during the pandemic, so actually my first WordCamp was the only WordCamp in 2021. And my second WordCamp was for computer ware in last year. So it was really nice and refreshing for me to meet all the other contributors. It is something special, for sure.

Birgit Pauli-Haack: Absolutely, yeah. It was great to meet you, Hector, although we had so many meetings with people on Zoom. Yeah.

Hector Prieto: Fun times.

Birgit Pauli-Haack: Yeah.

Hector Prieto: Well, circling back to State of the Word, I would also like to point out that, last but not least, it’s really cool to see how Openverse has grown since joined WordPress about a year and a half ago. And I’m super excited to see that coming, Openverse integration in WordPress that will allow users to directly search and add images from Openverse into their WordPress site without leaving the editor at all. That’s super cool.

Birgit Pauli-Haack: Yeah, that’s super cool. And I think it would also be really cool to have that also go back to if somebody uploads an image to WordPress and checks the check mark, also put it into Openverse. I think that part would really make it to a 360 kind of integration. I also love that there’s not only for images, but there is a lot of audio already uploaded to the Openverse that you can use on podcasts or on videos, and add free without having to think about royalties and buying for it and all that. Yeah, so free to the community.

Hector Prieto: There’s so many possibilities there. The future is exciting.

Birgit Pauli-Haack: Yeah, it’s really exciting. And I’m glad that it’s all happening in conjunction with WordPress. The same with the WordPress photos library, where people can just upload their photos and have it be it in the public domain and make it available to the broader community. It’s really cool.

Hector Prieto: Yeah.

WordPress 6.2

Birgit Pauli-Haack: All right. So between Christmas and New Year’s, Hector, you published the release schedule proposal for 6.2. I think it was something we were all waiting for. Kind of, okay, how do we plan first quarter when we don’t know when the release is coming? So you provided. So if the release team concurs, what’s the plan? When will we see the first Beta?

Hector Prieto: If the proposed plan is approved, the first Beta release will be on February 7th, which is 10 days before the first of our WordCamp Asia takes place.

Birgit Pauli-Haack: Excellent. In the planning schedule, you also have a call for contributors to volunteer for the release squad. So if you, dear listeners, are inclined to take part in it and you already have a little experience in contributing, throw your hat in the ring by commenting on the release post on the scheduled proposal post. And also throw your hat in the ring also means for those who English is their second language, also means raise your hand, you want to volunteer to be part of it, and then the release team is coming together. When do you expect that you will have a final plan?

Hector Prieto: The call for volunteers is open as we speak. Considering the end of the year vacation people are taking, contributors taking, I think we won’t have anything until end of next week or the following one. We’re leaving some extra time for people to come back from the holidays and chime in.

Birgit Pauli-Haack: All right. Okay. Yeah, so there are only two more Gutenberg releases before the feature freeze, if I calculate that correctly. We better get started in reviewing all the great new features that are coming in, in a more consolidated way.

Hector Prieto: Definitely. I encourage all of our listeners to start testing and giving feedback. It’s always super helpful. Also, compared to the past releases, the proposed 6.2 schedule both include a fourth Beta release compared to the previous three ones to leave some extra buffer time between WordCamp Asia and release candidate one, which will be on March 7th for a final release on March 28th.

Birgit Pauli-Haack: Oh, okay. Yeah, so contributor day at WordCamp Asia is definitely going to be part of it and that is really cool to have. Maybe we need to organize some tables that do some testing there. I don’t know how far the work of Asia contributor day team is about that, but having that plan definitely gives us all focus on that contributor day. All right, cool. So to repeat that, final release could be March 28th, so that’s about three months from today. And we will have a 6.2 release, provided everything works out as we anticipate now.

And I have a reminder for our listeners now for next week. The Gutenberg Times Live Q&A, Layout, Layout Layout will be happening on January 11th at 5:00 PM Eastern. That’s 22:00 UTC. And in this show, Isabel Brison, Andrew Serong, Justin Tadlock and I will discuss the opportunities and challenges for all the layout features for site builders. And we will be available for questions and answer them.

And Isabel Brison will also give us a demo of the various layout scenarios to use. She has, with Andrew, been instrumental in building all the features into the site editor and the blocks, and it’s going to be a very interesting show. It’s also going to be a little preview on Isabel Brison’s talk at WordCamp Asia in February 2023. So join us, link us in the show notes, and don’t forget you need to register there and to be… We will have a recording, of course, with the show notes and as well as a transcript, but it’s always good to have your questions answered live by the experts on the panel, and we have some great experts there. 

What’s Released

So, that brings us to the latest Gutenberg releases. First, there’s Gutenberg 14.8. That was released in December 12th. Ryan Welcher was release lead and it had 167 PRs merged by 42 contributors, five of which were first contributors. So welcome to the project, first contributors. So Hector, what’s the most significant enhancement in this release?

Hector Prieto: Well, Gutenberg 14.8, so several changes to the site editor user interface, and introduce something I’m super excited about, which is browse mode. Thanks to this first iteration of browse mode, users can switch between editing and browsing modes in the site editor, making it much easier to navigate through templates and template parts or even add new ones through the sidebar. It’s a feature that has been long awaited and it’s finally here and I’m super excited.

Birgit Pauli-Haack: Yeah. And it helps you with where you land when you click on the site editor. You are now not landing into editing your homepage and so now you have a better entrance into the site editor. And I really like that because it gets you better settled into what you’re going to do.

Hector Prieto: It makes for a nicer onboarding and it’s less dangerous, let’s say, because it’s much more difficult to break your design just as soon as you land on the site editor.

Birgit Pauli-Haack: Yeah, totally. So the navigation block also had some enhancements, especially with the migration from the old menu. So if you have a location primary, it will now fall back to the navigation menu from the classic menu. That is really helpful on the transition. There are other fallback updates made that it also uses the most recently created menu from the classic theme when you start migrating to a block theme.

Enhancements

So that is definitely a good help for transitioning from a classic theme to a block theme. But also it kind of decreases the mental load that you don’t have to recreate all your menus when you switch out the theme, which is something that was sometimes really critical in the classic menu, in the classic theme space, where everybody had different menu locations. And so I don’t think that it’s completely solved yet, but this is definitely a first step.

Hector Prieto: Yes, it’s a step on the right direction. We all know building menus is one of the most challenging aspects of building your site. And contributors are making a huge step for making the menu building process much easier.

Birgit Pauli-Haack: Yeah, absolutely. Yeah. There’s also one that came with 14.8 that is for the query block. The parent block is they removed the color block support just because it was always clashing up against the other blocks that are in the query block for the post template for the title and the excerpt. You could kind of get lost in which color did we do, and where do we do that? So removing it from the wrapper query block is definitely a good choice because it removes some of that confusion of where colors are actually set.

Hector Prieto: Exactly. Contributors have seen a few inconsistencies when adding the color to the wrapper query block, between the title, between the navigation links. So now the colors block supports are all in the inner blocks and there’s no space for confusion.

Birgit Pauli-Haack: So what else do we see there? Yeah, I think that was it on the 14.8 release, on the highlights. There are certainly the sidebar tabs for the navigation blocks. There is great work on the experimentation that happened. So right now we have five areas of experimentation in the Gutenberg plugin and there is only two more freeze, two more releases to get them out of experimentation into the production of the Gutenberg plugin. One of them is the sidebar for the navigation block. The other one is the separated settings tab in the sidebar that separates the styles from the features. And then the others, I don’t recall right now. Hang on, I’m going to check them out. I just had it there and then I closed my browser because, I don’t know, sometimes I just randomly close browser tabs, which is a really good way to confuse myself.

Hector Prieto: The type interface is making good progress and it’s something we would likely see out of experimental very soon.

Birgit Pauli-Haack: Oh, yeah. And then is the global styles for custom CSS is actually in… We all wait for that, but it’s now in the experimental stage and need to be switched on through experiments menu item on the Gutenberg plugin. And then the other one is the color randomizer utility that lets you mix the current color palette randomly and change it out. That’s kind of a funky way of handling your website to do a randomized color palette, but it certainly is a proof of concept of something bigger. Was there anything else in the 14.8 you want to mention, Hector?

Hector Prieto: Well, there are a few other main highlights that you might have seen, our listeners might have seen in the release post. One of them is super interesting, which is the custom CSS rules for your site. There’s now a tiny CSS text field where you can add your custom CSS directly in the editor. As we all know, with great power comes responsibility. So it’s nice that you can add a custom CSS directly in the editor, but let’s not overuse the important.

Birgit Pauli-Haack: Yeah, that’s definitely a way to… But that was before, so site editors or site users or site owners who used the custom CSS piece found that that was the missing piece to actually sign on to the full site editing, because they couldn’t do those very fast changes like changing a font size somewhere or changing a space somewhere or change the color of a border very easily by just using the developer tools, identifying the marker, the selector, and then just change the color in a custom CSS. Yeah, it opens up the capabilities for that.

You need definitely have file editing capabilities on the server and that sometimes was not available to anybody. But those who used it, they really missed it in the file site editing, in the site editing features, so that is really a good thing. And there is also a… It’s not yet released and it’s not merged yet in, but I know that Carolina Nymark is actually working on custom CSS for single blocks. And I think that’s also a good way to, in the paradigm of getting atomic design going, that that’s probably a better approach than having custom CSS being pulled in for every site page or page with the custom CSS. Rather do it per block.

Either way, it’s kind of a interesting feature that people want to have some control or at least go back to that what they are used to do and figure out how they can change it. Well, that definitely was a changelog of 14.8. I don’t think we’ve forgotten anything. I think we, in the release post by Ryan, it was a reorganized…. Oh, the style book is definitely something that was in 4.8. We haven’t talked about it. So do you want to talk about it, what that does?

Hector Prieto: Oh yeah, definitely. The style book is a super cool new feature, which is extension of the style site editor. The style book in a nutshell gives you an overview of all the available blocks you have in a single place so that you can easily browse all the blocks you have available and play with their design.

Birgit Pauli-Haack: When Gutenberg first came out, there were quite a few initiatives where you could have a unit test for blocks, where I think Rich Tabor actually had a plugin and I also worked with some of our clients back then when that we had a list of all the blocks in a page and then looked at it, how the theme works with it. And that was kind of a block unit testing in design. And with the additional features that come with site editing, it was a hard time to figure out what is a change in color on the paragraph block will have additional ramification throughout the site, or when you change style variations.

So I’m really glad that the style book, that’s a menu item in the site editor. You can go there and then see all the blocks that you have. And you get an access to the style variations of your theme so you can select them and then see how the blocks change. And that is so powerful that you don’t have this save and surprise effect anymore. You really look at it and say, “Oh yeah, I like it.” And you also see where the style variations may not be entirely working for your site because there are some things that are left out. So this is so powerful for the experience with the block editor.

Hector Prieto: For our listeners to picture it in their mind, it’s like having a page with demo content with all the blocks. You have it registered either core blocks or third party blocks. So as soon as you install it, applying that provides blocks, all these third party blocks will appear in the style book. And you will be able to see all of them together, play with the global styles, play with the accelerations, and see how they affect all these first party and third party blocks in a single place as if you have demo content page but automatically generated for you.

Birgit Pauli-Haack: Yeah. So it really offsets the need for these block unit testings and it’s very, very powerful. Yeah, I so agree. I think we’ve got it all now. Let’s move on to the next release, which was 14.9. And it has at the time of this recording not been released, but it will come out any hour now. For those who use the Gutenberg plugin on their sites, it’s the first Gutenberg release for 2023. 132 PRs by 46 contributors. Again, five new contributors in there. Congrats for your merge of your PR, and welcome to the project. Thank you so much for your contributions, for all of them.

Hector Prieto: It’s refreshing to see all these new contributors, even in these more maintenance oriented releases that happen during holidays. So congratulations to you all, and welcome.

Birgit Pauli-Haack: What are the highlights? What did you see, or what’s in the release?

Hector Prieto: There are a few changes. They’re mostly iterative, building on top of past features and enhancements. One of them, one very cool, is a new push to global styles button that appears in the cyber blocks, which allows users to, once they edit the blocks’ style and they like it and they say, “Hey, I like this how this is looking or how this image is looking. I would like all my image blocks to look like this.” It allows them to push those styles to global styles so that they automatically affect all the blocks of that type.

Birgit Pauli-Haack: Right. And that’s also why it’s good to have this style book handy so you can actually see if you made a mistake or something like that and said, “Oh no, I didn’t consider this, so let’s do one more time.” Yeah. So that’s a great feature. Yeah, absolutely.

Hector Prieto: Also, for those who like building patterns, now when registering patterns, there’s a new property that allows you to specify in which template a pattern makes sense. Let’s suppose, for example, we are building a 404 pattern. Previously it would be released everywhere, so it would appear everywhere in all kinds of templates. Now you can limit it to only appear on a 404 template, so it doesn’t bring noise to other templates where it doesn’t make sense. So this is going to improve pattern discoverability in general as patterns.

Birgit Pauli-Haack: And it also improves separation of concerns. As you said, it will not show up on every page where even if it’s not suitable for the pattern. But it also themes can then, or plugin can now create custom post types and that all, and just make those patterns available for certain custom post types. I think that is definitely a missing piece that has now been added to it. Excellent. Yeah, I’m really excited about that.

Hector Prieto: Yes, there’s a minor update following up on Gutenberg 14.5. So we are thinking, we’re looking at two months ago, three months ago, when the list view and the document outline were merged in a single panel. We have seen there are a few improvements that can be made in the design. So now, for example, the word count has been moved to the top of the outline for more clarity.

Birgit Pauli-Haack: Yeah, there was some confusion. Where is it now? Yeah. And then you didn’t see it at first because when you hit on update, you post and then the little notification ball totally covered that piece. So it took a while till that goes away so you see the word count and the time to read and also the block count. There were a few pieces missing. I don’t know why they’re missing, but they probably don’t seem to be very important for content creators to see. And the outline, having the other one on the list here in one it definitely makes sense to have that.

So if you haven’t seen that yet, it was in Gutenberg 14.5. It will come to 6.2, so checking it out through the Gutenberg plugin is definitely worth trying, worth a look so your site owners or the clients are prepared to find it in a different space. What I’m also very excited about is that there is now an option to import widgets from the sidebars into template parts. And that is in the whole idea of transitioning from a classic theme to block themes or make a site be better prepared to move to a site, to full site editing block theme. This is definitely a step forward. Any additional thoughts on that?

Hector Prieto: Oh yeah, absolutely. This is a very important milestone towards block adoption because it allows users to migrate from classic widgets to native blocks. It’s worth noting that it doesn’t work on template focus mode yet, it’s only available for the block inspector. But this is definitely a step on the right direction to increase block adoption.

Birgit Pauli-Haack: Excellent, yeah. And George Mamadashvili, who heads… That’s his PR. He also has a nice video on how he demonstrates how it’s going to work. So I hear quite a few people celebrating this piece to make the transition over. Another one is, this is minor thing, but the configurable settings for the fluid typography in the theme JSONs now has a minimum font size, so it can be anchored on the smallest font size. So the fluidity then can increase the font size on a bigger screen. There was a hard coded value of 14 pixels before, with no way to change. And now you can have the minimum font size, like 16 pixels or 18 pixels depending on your site needs. That’s a minor thing, but I think it is something that quite a few designers were missing.

Hector Prieto: Yes, absolutely. It’s a minor improvement, but we’ve seen lots of these minor improvements in the last, I don’t know, four or five Gutenberg releases building on top of free typography. And when you look at them altogether combined, you can see huge improvements on how the feature is becoming more and more powerful by the day.

Birgit Pauli-Haack: Yeah, absolutely, absolutely. I think that was at 14 point… No, one thing is still really important from the release and that is the adding shadow presets support for the theme JSON. So you can do box shadows on your blocks or wrapper blocks, and that is now available for designers of themes. There is no user interface for that yet. But as we said repeatedly here on the podcast, things will be…

Hector Prieto: It will come.

Birgit Pauli-Haack: Hmm?

Hector Prieto: It will come.

Birgit Pauli-Haack: But it’s important to make it work for the theme developers first. Before you have all the added implementation for site owners that want to change it, you first need to know how it’s actually working so you can see where the pieces are that need to be surfaced in a user interface. So there is a new setting object called shadow, and then you can add different palettes to it for natural and crisp and sharp and soft shadows. And the PR has quite a few information about how that’s implemented. It gives you quite a few use cases on how you can do the shadow boxes for the buttons, for cover block, for menu block. If you have a sticky menu, then you can put a little shadow underneath it to see the difference between the page and the menu. So there are quite a few design use cases to try that out.

Hector Prieto: I’m curious to see what designers come up with thanks to this new setting. I can see lots of 3D buttons and shadow buttons and all these cool things.

Birgit Pauli-Haack: You could even do the outlines of the shadows, kind of, if you have an outline… Yeah, there are some great designs out there right now. So, from the changelog we are on, anything else that you wanted to talk about here that we missed? I know that Tonya Mark has updated the tracking issue for the web fonts API. And what’s merged in this release is the change of architecture to use the Core’s dependencies API with the web fonts API. And there’s a call for testing out there, or it will be out there, and making sure that how you use it. She has an update where she asked how you can help. And that is if you have an idea about naming the API, should it be webfonts, or web fonts, two words, or just the fonts API, which I tend to be the fonts API, but there is a renaming before everything gets into the Core that we’ll be name things right.

And then the other one is a call to test the new architecture and share feedback on your testing reports and using the web fonts API. I’m not quite sure how the planning is because it seems to be still blocked furthermore through additional architectural work. Hector, do you think that that will come with 6.2, or is it now a little late for 6.2?

Hector Prieto: Well, Tony and the other contributors are making their best to have this feature land in 6.2, so I’m pretty positive it can make it in 6.2. And the best way to ensure it can land in that version is to help with testing and with feedback. That will help unlock the architecture redesign and the renaming and everything that’s currently being discussed right now.

Birgit Pauli-Haack: All right. Okay. Yeah, if you all are contributing to things, dear listeners, help getting that over the finish line. It definitely needs some testing. So I think that’s the end of talking about Gutenberg 14.9. We’re coming also up on the hour, so I think we can go to closing things. Are there anything that you want to point out that are on the roadmap for 6.2 that you want to have our listeners know? And if not, how can the listeners get in contact with you, where to best meet you online?

Hector Prieto: Well, you can reach out to me in WordPress Slack. Handle is Prieto. I guess it will be written in the show notes. So please feel free to ping me there or in GitHub or in Track. I’m using the handle everywhere, so that’s easy. I would just like to circle back to the 6.2 planning and reminding everyone the call for volunteers is open. So if you’re interested in participating in the squad, you are more than welcome. We will assist you if it’s your first time. If you’re an assistant contributor, you are also welcome and we can learn from you. So everybody’s welcome, that’s the long story short.

Birgit Pauli-Haack: Yeah. And the only thing that I want to remind you is about the next week’s Gutenberg Live Q&A with Isabel Brison, Andrew Serong and Justin Tadlock on Layout, Layout, Layout. January 11th at 5:00 PM Eastern and 20:22 UTC. That’s 10:00 PM on UTC. And as always, the show notes will be published on gutenbergtimes.com/podcast. This is episode 78. And if you have questions and suggestions or news you want us to include, send them to changelog@gutenbergtimes.com. That’s changelog@gutenbergtimes.com. So thank you so much, Hector, for joining me here for the first Changelog podcast in 2023 to spend the time on preparation as well as in the show. Thank you all for listening and goodbye and again, Happy New Year.

Hector Prieto: Thank you for having me and see you soon. Happy New Year, everybody.

by Gutenberg Changelog at January 07, 2023 07:14 PM under Gutenberg

Gutenberg Times: 209 Block Themes, Query Block Variations, Forms with Blocks, Block Art and more – Weekend Edition #240

Howdy,

Tomorrow is the 5-year anniversary of Gutenberg Times. It feels like I just started yesterday to be fascinated by the possibilities of the block editor. For many people, it actually was just yesterday that they dipped their toes into the world of the new thing. Not you of course. You have been a wonderful subscriber and reader for a while now, and I am infinitely grateful for your support. Thank you!

Welcome to all new subscribers this year. So glad you are here.

Let’s dive into the sixth year together, and learn what will be next for the block editor and what other people make with it and for it. The ecosystem seems to keep expanding quite a bit with the block editor.

Wishing you and yours a fabulous 2023. May you be prosperous, happy, and healthy!

Yours, 💕
Birgit

PS: Reminder: Hope to see you next week at the Gutenberg Times Live Q & A. Get your seats now for January 11, 2023, at 5pm / ET 22:00 UTC

Developing Gutenberg and WordPress

Hector Prieto published the WordPress 6.2 Planning Schedule Proposal, and it’s also a call for volunteers for the release squad. The 6.2 release squad will then decide on the final release schedule. For now, Feature Freeze and Beta 1 would be on February 7th, 2023. Tthere are four Beta releases planned before release candidate 1 will be available on March 7th, and a final release on March 28th, 2023.


Reminder: January 10, 2023, at 9:30 ET / 14:30 UTC: Hallway Hangout: Performance Considerations for Block Themes Anne McCarthy wrote: “At a high level, we’ll go through general intros (what each person does/focuses on), current work underway to address performance, what work is being done specifically for block themes, and general open Q&A. Hallway hangouts are meant to be casual and collaborative so come prepared with a kind, curious mind along with any questions or items you want to demo/discuss.”

From the WordPress Developer Blog

Justin Tadlock published a tutorial for building a book review grid with a Query Loop block variation. WordPress 6.1 introduced an extension to the Query Loop block, which allows plugin developers to filter existing functionality in core WordPress rather than building custom blocks to query posts. This tutorial shows how to build a WordPress plugin that display a list of book review posts including post_meta` data, using a block variation for the Query Loop and set up rendering it on the front end.

Nick Diego tweeted: I always knew the Query Loop block was incredibly powerful, but I had never explored integrating post metadata into custom block variations! Learn how in this fantastic article by @justintadlock on the new WordPress Developer Blog.


Micheal Burridge composed a Roundup post to review 2022 from a block developer’s perspective in is post. You’ll find a select list of resources, to get started or to catch up on the development from the last 12 months, via the Make Blog, WordPress TV and the Learn WordPress site.

Gutenberg plugin releases

Gutenberg 14.8 was released on December 22, 2022, and release lead Ryan Welcher highlighted in his post What’s new in Gutenberg 14.8? (21 December)

Sarah Gooding reported on the release as well via the WPTavern: Gutenberg 14.8 Overhauls Site Editor Interface, Adds Style Book


Gutenberg 14.9 is the first release of 2023, and release lead Justin Tadlock pointed out a few new features in his post What’s new in Gutenberg 14.9? (4 January):

On the WPTavern, Sarah Gooding took the version for spin and reported on the new magic: Gutenberg 14.9’s New Magic: Push Block Changes to Global Styles


In the upcoming Gutenberg Changelog episode 78, Hector Prieto was my guest. He is a full-time core contributor and coordinator of multi-release WordPress and Gutenberg releases. We discussed Gutenberg 14.8 and 14.9 as well as 6.2 release schedule proposal and other topics. The episode will hit your favorite podcast app over the weekend.

🎙️ New episode: Gutenberg Changelog #78 -State of the Word, WordPress 6.2, Gutenberg 14.8 and 14.9 with Birgit Pauli-Haack and special guest Hector Prieto

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


Sarah Gooding wrote about Block Protocol Announces New WordPress Plugin Coming in 2023 It will allow users to embed interactive blocks that are compatible with Gutenberg, and will include blocks for drawing, GitHub pull request overview, timer, calculation, and more. The plugin will also include new blocks powered by OpenAI DALL-E and GPT .

The Block Protocol project is open source and designed to be an open protocol, and WordPress hopes to integrate more with it in the future.


In the latest WPTavern Jukebox podcast episode, Damon Cook, developer advocate at WPEngine, discussed with Nathan Wrigley the future of website styling in WordPress. Wrigley wrote in the introduction: ” Block-based themes are revolutionizing website styling. You’re going to be able to change any aspect of your website from the UI that you’re familiar with. The hope is that it’ll make styling more accessible to a wider audience.

Damon talks about the fact that we’re in a period of flux right now. The documentation and tooling needed to work with website styles is maturing, but is by no means complete.”


Torsten Landsiedel scratched his personal itch and built the plugin Ignore block name in search, after finding that the WordPress built-in search included in the findings posts where the search keywords are in the HTML comments of blocks, and with that skews, the search result less relevant. It’s particular helpful when your blog is about working with the block editor or about content creation with WordPress. Landsiedel feels that the block editor makes the shortcomings of the built-in search feature worse because blocks contain full words, and not just HTML tags. It’s been a long-standing issue, that this plugin now solves.


209 Block Themes are now available in the WordPress repository with new submissions by Themeisle, sparklewpthemes, olivethemes, deothemes, sonalsinha21, Blockify, hamidxazad, WPZOOM.

Ana Segota of Anariel Design also announced Yuna, a block theme for Nonprofits that comes with 100+ Design Patterns, you can add to your page with a simple drag and drop. Use built-in options to arrange and style them any way you want. It also includes built-in styles for the popular GiveWP donations plugin and is also ready to house your ecommerce store.

Making Block Art

Curious about some art behind Matt Mullenweg during State of the Word? Below are those pieces designed for the Museum of Block Art which represent the creativity that Gutenberg blocks inspire. Be sure to stop by and experience the museum’s digital interactive exhibit.

You can see

Anne McCarthy, instigator and curator of the Museum of Block Art, wrote an insightful blog post about how she approached making art with the Block Editor. Take a look Behind the scenes of creating art with WordPress.

Chuck Grimmett has more examples of WP Block Art on his blog.


Rich Tabor and Courtney Portnoy discussed The creative side of blocks on WordPressTV. Rich Tabor walks the viewers through one of his block art creations. It’s quite inspiring to watch Tabor’s exploratory creative process using the block editor. I learned quite a few things about the power of the various color features: gradient, nested group blocks, and how to replace the theme’s primary and secondary colors for the whole site. You’ll also get an introduction to the Museum of Block Art, where Rich and other block artists showcase their creations. (also mentioned in GT 239)

Form Plugins working with Blocks

Two plugins emerged that take advantage of the block editor and its components and scripts so site owners and builders can use them to create forms.

Munir Kamal, created a block integration for the popular CF7 Forms. It’s aptly names CF Blocks and available in the WordPress repository. He wrote in the description: “With CF7 Blocks, you can easily create and customize contact forms within the familiar block editor interface. No more fiddling with short codes or HTML – just drag and drop blocks to build your forms exactly how you want them.” Sounds spectacular, doesn’t it?

In here article New CF7 Blocks Plugin Brings Blocks to Contact Form 7, Sarah Gooding, took a more in-depth look and shares her findings.


On Twitter, JR Tashjian developer at GoDaddy, introduced OmniForm, the next-generation Form Builder for your website. Sign up for early access now and be among the first to try it. The plan is to make the plugin available in the WordPress plugin directory at the end of January, with early access provided to users the week prior. Tashjian continues: “OmniForm embraces the block editor to the fullest extent and unlike any solution right now. The block editor is the future of editing in WordPress and building any kind of form will be no different from creating a post or page.” Tall order. Looking forward to doing some testing, too.

Theme Development for Full Site Editing and Blocks

Anne McCarthy has a new video up on YouTube: Building a site with WordPress 5.9 vs. WordPress 6.2 (in progress features) – To better show what’s changed with the Site Editor from when it was first introduced in WordPress 5.9, this video goes through both a demo of the original state and a brief look at what’s in place today and what’s to come, especially as 6.2 looks to wrap up much of the work around site editing/phase 2 of Gutenberg. Keep in mind that WordPress 6.2 is not out yet and much of what’s being shown is very much a work in progress with big opportunities to provide feedback along the way. Either way, I hope you enjoy taking a peak back and a look forward.


 “Keeping up with Gutenberg – Index 2022” 
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. 2021 on. Updated by yours truly. The index 2020 is here

In this video tutorial, Jonathan Bossenger gives you an Introduction to theme.json. You will learn how the theme.js file works, and how you can control these settings and styles.


Daisy Olsen started a new Live Stream schedule and will show off Block Themes in WordPress every Friday at 10:30 am ET / 15:30 UTC on Twitch.

The inaugural show took place Friday, January 6th, 2023 with the topic: Building a Block Theme. It’s a great opportunity to follow along with Daisy and ask questions along the way.

Building Blocks and Tools for the Block editor.

Munir Kamal takes you on a journey of From WordPress to the World: Intro to the Standalone Gutenberg Block Editor. In his new plugin, Kamal made the journey and found a few challenges along the way, overcame them and new put it all together for others to follow. Using the app ‘Isolated block editor, from the public repo, maintained by Automattic. Matt Mullenweg in the State of the Word emphasized that the block editor is also used outside of WordPress, with Tumblr, Day One app and with bbPress instance.


The team working on GiveWP went on a similar route on the revamp of the highly popular donation plugin. Post Status recently posted an article about that: The Future of GiveWP and the Block Editor

GiveWP will hold a Town hall event about the new version on January 25th, 2023 at 10am PT / 18:00 UTC – in case someone is interested. Learn more Town Hall: GiveWP Design Mode and What’s Next for 3.0


Kyle Johnson, JavaScript developer at GiveWP will present his talk: Using Gutenberg as a Development Foundation, Not Just a Block Builder at WordCamp Birmingham on February 4th, 2023. As far as we know, the talks will be recorded, but not livestreamed. So, they will show up on WordPress TV in the weeks after the WordCamp.


Mohammed Noufal of Hubspot wrote about How to Create Custom Blocks in WordPress, providing answers to the questions: why use a custom block, how to make Custom Block Templates and how to use custom blocks on your site.


Jonathan Bossenger‘s last section of his series: Let’s code: developing blocks without React!  is now also available on WordPress TV. Let’s code: developing blocks without React! – Review. If you followed along over the past few weeks, you would have learned to build a small WordPress block using plain (vanilla) JavaScript. In this session, we will review everything we’ve learned so far, by rebuilding the entire block from scratch.

The other editions for the series are in order of broadcast/

Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.

GitHub all releases

Upcoming WordPress events

January 10, 2023 – 9:30 ET / 14:30 UTC
Hallway Hangout: Performance Considerations for Block Themes with Anne McCarthy

January 11, 2023 – 5 pm ET / 22:00 UTC
Gutenberg Times Live Q & A: Layout, layout, layout
Panel discussion with Isabel Brison, Andrew Serong, Justin Tadlock and Birgit Pauli-Haack

February 4 + 5, 2023
WordCamp Birmingham, AL

February 17 – 19, 2023
WordCamp Asia 2023 

Learn WordPress Online Meetups

January 17, 2023 – 3pm / 20:00 UTC
Patterns, reusable blocks and block locking

January 19, 2023 – 7 pm ET / 24:00 UTC
Let’s make custom templates in the Site Editor!

January 31, 2023 – 3pm ET / 20:00 UTC
Creating a photography website with the block editor


Featured Image:


Don’t want to miss the next Weekend Edition?

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

Thanks for subscribing.

by Birgit Pauli-Haack at January 07, 2023 02:25 PM under News

WPTavern: WordCamp Europe 2023 Speaker Applications Open, Organizers Call for More Interactive Sessions

WordCamp Europe 2023 is being hosted in Athens this year with two conference days scheduled for June 9 and 10. The first day’s theme is “WordPress Now” (Everything that can be currently achieved with WordPress) and the second day is “WordPress Tomorrow.”

Organizers have opened the call for speakers and are especially interested in scheduling talks that “empower people to feel more comfortable using WordPress.” They are soliciting new voices this year with fresh perspectives.

After reviewing attendee feedback from the previous year, organizers have identified more than three dozen requested topics across the development, business, community, and design categories. These include many more development topics, such as security, CI/CD, headless CMS, ReactJS for PHP Developers / Building Blocks, and more. Attendees are also eager to hear about content monetization, recurring revenue, GDPR compliance, brand identity, and designing for accessibility, to list a few examples.

Presentation formats will include traditional talks, hands-on workshops, expert panels, and lightning talks. Organizers are encouraging speakers to add activities to sessions that will get the audience involved and avoid the afternoon slump. They cited a few examples, including a WordCamp in the Czech Republic where a security researcher installed a Wi-Fi honeypot in the venue and demonstrated how dangerous public wi-fi is when logging into a WordPress site that doesn’t have SSL.

WCEU has launched a Speaker’s support program to help fund selected speakers with financial barriers to attending. Organizers arrange for speakers and the sponsoring companies to connect but are not involved in selecting who receives the funds.

The call for speakers will close the first week of February and applicants will receive a response by the second week of March. Speakers will be announced in the second week of April.

by Sarah Gooding at January 07, 2023 03:18 AM under News

January 06, 2023

WPTavern: BuddyPress 11.0.0 Adds Filter for Improved JS and CSS Asset Loading, WebP Support, and New Ways to Fetch Activities

BuddyPress 11.0.0 is now available thanks to the efforts of 34 contributors. The release is named “La Scala” in honor of a pizza restaurant located in Issy-Les-Moulineaux, a Paris suburb.

Version 11.0.0 introduces a few important changes. BuddyPress has improved the way it loads its JavaScript and CSS assets with the addition of a new filter so that they are now only loaded on community pages. Previously, the plugin would load them indiscriminately on every page, a leftover from how they were loaded in the first Template Pack (BP Legacy). This change is being rolled out progressively, so users who want to take advantage of this improvement will need to add the filter to their bp-custom.php file.

add_filter( ‘bp_enqueue_assets_in_bp_pages_only’, ‘__return_true’ );

BP 11.0.0 also enables the use of use .webp images for profile and cover images, after a user requested it in a negative review. This feature requires WordPress 5.8 or newer.

This release introduces the ability to fetch activities for or excluding a group of users. For example, developers can now write code to fetch activities for a select few users based on user ID or block updates from some annoying users by excluding their user IDs.

“This change is simple but powerful!” BuddyPress core developer Dan Cavins said. “For instance, you could create custom interest activity streams, or build a mute feature to let your members take a break from other, too-chatty users!”

Version 11.0.0 also gives developers the ability to build custom xProfile loops including a specific set of profile field groups.

BuddyPress 10.0.0 introduced an add-ons section in the plugin administration screen for users to easily test plugins or blocks maintained by the BuddyPress development team and hosted on WordPress.org. BP lead developer Mathieu Viet said the team will soon be publishing a Community Media Attachments add-on and a block-based Activity Post Form that will “standardize the way to extend activity updates with richer and more engaging content.” These feature plugins are part of what Viet anticipates will be “a transitional year for BuddyPress” and may be published to the add-ons section independent of a major release.

BuddyPress users should watch for updates to the add-ons section and check out the full list of changes in 11.0.0 in the BuddyPress codex. Updating to the latest version will require WordPress 5.7 or later.

by Sarah Gooding at January 06, 2023 10:33 PM under News

Do The Woo Community: A New YouTube Channel and WooBits Format

WooBits now featuring guest hosts for a one-off chance to share their insights and perspectives on various topics. Plus a new YouTube channel.

>> The post A New YouTube Channel and WooBits Format appeared first on Do the Woo - a WooCommerce Builder Community .

by BobWP at January 06, 2023 10:54 AM under WooBits

Follow our RSS feed: 

WordPress Planet

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

Official Blog

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

Subscriptions

Last updated:

January 16, 2023 04:30 PM
All times are UTC.