WordPress Planet

November 12, 2024

WordPress.org blog: WordPress 6.7 “Rollins”

Each WordPress release celebrates an artist who has made an indelible mark on the world of music. WordPress 6.7, code-named “Rollins,” pays tribute to the legendary jazz saxophonist Sonny Rollins. Known as one of the greatest improvisers and pioneers in jazz, Rollins has influenced generations of musicians with his technical brilliance, innovative spirit, and fearless approach to musical expression.

Sonny Rollins’ work is characterized by its unmatched energy and emotional depth. His compositions, such as “St. Thomas,” “Oleo,” and “Airegin,” are timeless jazz standards, celebrated for their rhythmic complexity and melodic inventiveness. Rollins’ bold and exploratory style resonates with WordPress’ own commitment to empowering creators to push boundaries and explore new possibilities in digital expression.

Embrace the spirit of innovation and spontaneity that defines Rollins’ sound as you dive into the new features and enhancements of WordPress 6.7.

Welcome to WordPress 6.7!

WordPress 6.7 debuts the modern Twenty Twenty-Five theme, offering ultimate design flexibility for any blog at any scale. Control your site typography like never before with new font management features. The new Zoom Out feature lets you design your site with a macro view, stepping back from the details to bring the big picture to life.

Introducing Twenty Twenty-Five

Endless possibility without complexity

Twenty Twenty-Five offers a flexible, design-focused theme that lets you build stunning sites with ease. Tailor your aesthetic with an array of style options, block patterns, and color palettes. Pared down to the essentials, this is a theme that can truly grow with you.

Get the big picture with Zoom Out

Explore your content from a new perspective

Edit and arrange entire sections of your content like never before. A broader view of your site lets you add, edit, shuffle, or remove patterns to your liking. Embrace your inner architect.

Connect blocks and custom fields with no hassle (or code)

A streamlined way to create dynamic content

This feature introduces a new UI for connecting blocks to custom fields, putting control of dynamic content directly in the editor. Link blocks with fields in just a few clicks, enhancing flexibility and efficiency when building. Your clients will love you—as if they didn’t already.

Embrace your inner font nerd

New style section, new possibilities

Create, edit, remove, and apply font size presets with the next addition to the Styles interface. Override theme defaults or create your own custom font size, complete with fluid typography for responsive font scaling. Get into the details!

Performance

WordPress 6.7 delivers important performance updates, including faster pattern loading, optimized previews in the data views component, improved PHP 8+ support and removal of deprecated code, auto sizes for lazy-loaded images, and more efficient tag processing in the HTML API.

Accessibility

65+ accessibility fixes and enhancements focus on foundational aspects of the WordPress experience, from improving user interface components and keyboard navigation in the Editor, to an accessible heading on WordPress login screens and clearer labeling throughout.

And much more

For a comprehensive overview of all the new features and enhancements in WordPress 6.7, please visit the feature-showcase website.

Learn more about WordPress 6.7

Learn WordPress is a free resource for new and experienced WordPress users. Learn is stocked with how-to videos on using various features in WordPress, interactive workshops for exploring topics in-depth, and lesson plans for diving deep into specific areas of WordPress.

Read the WordPress 6.7 Release Notes for information on installation, enhancements, fixed issues, release contributors, learning resources, and the list of file changes.

Explore the WordPress 6.7 Field Guide. Learn about the changes in this release with detailed developer notes to help you build with WordPress.

The 6.7 release squad

Every release comes to you from a dedicated team of enthusiastic contributors who help keep things on track and moving smoothly. The team that has led 6.7 is a cross-functional group of contributors who are always ready to champion ideas, remove blockers, and resolve issues.

Thank you, contributors

The mission of WordPress is to democratize publishing and embody the freedoms that come with open source. A global and diverse community of people collaborating to strengthen the software supports this effort.

WordPress 6.7 reflects the tireless efforts and passion of more than 780 contributors in countries all over the world. This release also welcomed over 230 first-time contributors!

Their collaboration delivered more than 340 enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress open source community.

!Benni · 75thtrombone · Aaron Jorbin · Aaron Robertshaw · Aaron Ware · aatanasov · Abha Thakor · abhi3315 · Abhishek Deshpande · Abir · acafourek · Adam Heckler · Adam Silverstein · Adam Wood · Adam Zieliński · Adarsh Akshat · Adrian · aduth · ah72king · Ahmar Zaidi · Ahmed Kabir Chaion · Ahmed Saeed · Ajit Bohra · Akash Dhawade · Aki Hamano · Akira Tachibana · Akshat Kakkad · Al-Amin Firdows · Alan Fuller · Albert Juhé Lluveras · Alessandro Tesoro · Alessio · Alex Concha · Alex Lende · Alex Stine · alex27 · Alexander Frank · Alexandre Buffet · Alexandru Horeanu · alexcu21 · Ali Ali · aliaghdam · allilevine · Alvaro Gómez · Alvi Tazwar · Amin Charoliya · Amir Abbas · Amit Raj · Amjad Ali · Anand Thakkar · Andrea Fercia · Andrea Roenning · Andrei Draganescu · Andrei Lupu · andreiglingeanu · Andrew Hayward · Andrew Ozz · Andrew Serong · Andrey "Rarst" Savchenko · André Maneiro · Andy Fragen · Angelika Reisiger · Aniket Patel · Ankit K Gupta · Ankit K. Gupta · Ankit Kumar Shah · Ankur Vishwakarma · Anne McCarthy · Anthony Burchell · Anthony Hortin · Antoine · Anton Vlasenko · Antonio Sejas · apmeyer · Ari Stathopoulos · Armando J. Perez Carreno · Armands · arnaudbroes · Art Smith · Artemio Morales · Arthur Chu · arypneta · asafm7 · Aslam Doctor · Autumn · Ayesh Karunaratne · Bård Bjerke Johannessen · Béryl de La Grandière · Balu B · Barry Ceelen · Bart Kalisz · Beatriz Fialho · Ben Dwyer · Benjamin Denis · Benjamin Zekavica · Benoit Chantre · Bernhard Kau · Bernhard Reiter · Bernhard Riedl · bernhard-reiter · berubenic · Bhavesh · bijit027 · Birgit Pauli-Haack · blindmikey · bobbyleenoblestudios · Bogdan Nikolic · Brad · brad hogan · Brad Jorsch · Brandon Kraft · Brent Jett · Brett Shumaker · Brian Alexander · Brian Coords · Brian Gardner · Brian Gosnell · Brian Henry · bridgetwes · brobken · Bruno Freiberger Garcia · Cambabutonono · Carlos Bravo · Carlos G. P. · Carolina Nymark · Carsten Bach · cbirdsong · Chirag Mathur · ChriCo · Chris Reynolds · Chris Trynkiewicz (Sukces Strony) · Christoph Daum · Christopher Finke · Christopher Kanitz · Christy Nyiri · Ciprian · codersantosh · Colin Stewart · Corey Worrell · Courtney Robertson · craynor · creativethemeshq · Cullen Whitmore · Cupid Chakma · cweiske · Cyrille · da5f656f · Dademaru · daleharrison · Damon Cook · Damon Cook · Dani Guardiola · Daniel Richards · Daniele Scasciafratte · Danny · dannyreaktiv · darerodz · Dareth NHANG · Darren Ethier (nerrad) · Darshit Rajyaguru · daveagp · David · David Ballarin Prunera · David Baumwald · David Biňovec · David Bowman · David Brown · David Calhoun · David Godleman · David Henriet · David Herrera · David Levine · David Rozando · David Shanske · David Smith · ddewan · Dean Sas · DEBARGHYA BANERJEE · Deepak Rohilla · Deepak Vijayan · Dekadinious · Dennis Snell · Derek Smart · Deryck · designsimply · Devansh Chaudhary · devspace · Dhananjay Kuber · Dharmesh Patel · Dhrumil Kumbhani · Dhruval Shah · Dhruvang21 · Dilip Bheda · Dilip Modhavadiya · Dion Hulse · Divi Banks · dj.cowan · djennez · Doni Kuntoro · Dor Zuberi · Drew Jaynes · Drivingralle · drzraf · Earle Davies · eballeste · eclev91 · Ed Beck · ejnwebmaster · elfu98 · Elio Rivero · Ella van Durpe · Elliott Richmond · Emmanue ATSÉ · Emmanuel Hesry · emmanuel78 · Enrico Battocchi · Enrique Sánchez · Eric Dye · Erik · erikiva · erikyo · Evan Herman · Evan Mullins · Fabian Kägy · Fabio Rubioglio · FahimMurshed · Faisal Ahammad · Faisal Alvi · Faizan Nabi · Farhan Ahmed · Fayyaz · Felix Arntz · Felix Renicks · Fernando Jorge Mota (a11n) · Firoz Sabaliya · Francisco · Fransisca H · fullworks · Gale Wallace · gansbrest · Gareth Elwell · Garrett Hyder · Gary Pendergast · Gaurav Tiwari · gauravsingh7 · Georg · George Mamadashvili · Gerardo Pacheco · Germán Freixinós · gmariani405 · GraemeF · Grant M. Kinney · greentreefrog · GreenWorld · Greg Ziółkowski · Guido Scialfa · Gyurmey · Héctor Prieto · Halil ESEN · hanneslsm · Hans-Gerd Gerhards · Hardip Parmar · Hareesh S · Harper Holsinger · Harsh Gajipara · harshvaishnav · Haz · hectorjarquin · hedgefield · Helen Hou-Sandi · Henrique Iamarino · Himanshu Pathak · hirschferkel · Hit Bhalodia · Hossein · htmgarcia · huubl · Huzaifa Al Mesbah · Ibrahim · Ibrahim Riaz · Imran Hossain (a11n) · Isabel Brison · IT Path Solutions · itapress · Ivan Ottinger · Jack Stevens · Jacob Cassidy · Jacob Smith · jagirbahesh · Jainil Shah · Jakob Trost · James Koster · James Osborne · James Rosado · James Wesley Goedert · Jan Pfeil · janak Kaneriya · Jarda Snajdr · jarekmorawski · Jarko Piironen · Jason Bahl · Jason LeMahieu (MadtownLems) · javad2000 · Javier Arce · Jawad Malik · Jay · Jayadevan k · jbrya029 · JD Ahir · Jean-Baptiste Audras · Jeff Chi · Jeff Ong · Jeffrey de Wit · Jeffrey Paul · Jenil Kanani · Jennifer Farhat · Jenny Dupuy · Jeremy Felt · Jeremy Herve · Jerry Jones · Jesko Bendmann · Jessica Lyschik · jetaldobariya1 · Jigar Panchal · jimmyh61 · Joe Dolson · Joe Hoyle · Joe McGill · Joen Asmussen · John Blackbourn · John Espiritu · John Godley · John James Jacoby · John Regan · JohnRDOrazio · Jon Surrell · Jonas · Jonathan Bossenger · Jonathan Desrosiers · Jonny Harris · Jonny Waters · jordesign · Jorge Costa · Jos Klever · Jose Varghese · Josepha · Joshua Goode · Jossnaz · Juan Aldasoro · JuanMa Garrido · julianoe · Julie Moynat · Juliette Reinders Folmer · Juned Sabaliya · Justin Tadlock · K. Adam White · Kaavya Iyer (woo-hc) · Kadim Gültekin · KafleG · Kai Hao · Kajal Gohel · Kamal Hosen · Kamran Hussen · Karan Gupta · Karol Manijak · Karthik Thayyil · Kartik Mehta · Kartik Suthar · kbrownkd (a11n) · Keffr3n · Kel Santiago-Pilarski · Kellen Mace · Kelly Choyce-Dwan · keoshi · Kevin Behrens · Kevin Taron · kevinswalsh · Khokan Sardar · Kira Schroder · Kishan Jasani · kisquian · Kjell Reigstad · kkmuffme · Knut Sparhell · Kowsar Hossain · kracked888 · Krishna Neupane · kristastevens · Krupa Nanda · Krupal Panchal · Kunal Madhak · Kunjan Gohel · Kurt Payne · Kushang Tailor · Lae · Lara Schenck · lastsplash (a11n) · Laura Byrne · laurelfulford · Lauren · Lawrence Joe · leemon · Lena Morita · Liam Gladdy · lifelightweb · Linkon Miyan · Linnea Huxford · liviopv · Louis Wolmarans · Lourens · Love Soni · Lucas · Luigi Teschio · Luis Felipe Zaguini · luisherranz · lukasbesch · Luke Carbis · Madhu Dollu · madpeter · Maggie Cabrera · Mahmudul Haque Nadim · Mai · Makarand G. Mane · manbo · Manesh Timilsina · Manuel Schmalstieg · Manzoor Wani (a11n) · María Anguas · Marc · Marc Armengou · Marcel Tannich · Marcelo de Moraes Serpa · Marcin Pietrzak · Marco Ciampini · Marco Pereirinha · marcwieland95 · Marek Železný · margolisj · Maria Yohana · Marie · Marin Atanasov · Mario Santos · Marius L. J. · mariushosting · Mark Howells-Mead · Mark Parnell · Mark-k · Martijn van der Klis · martin.krcho · marybaum · mat_ · Matias Benedetto · Matias Ventura · Matt Mullenweg · Matt Robinson · Matt Sherman · Matteo Enna · Matthew Boynes · Matthew Riley MacPherson · Matthias Kittsteiner · mattraines · maurodf · Mayank Tripathi · Mayur Prajapati · mcrisp1972 · Md Abul Bashar · Md Hossain Shohel · Md. Istiaq Hossain · mdviralsampat · megane9988 · Mehedi Hassan · Mehul Kaklotar · Mel Choyce-Dwan · meteorlxy · Micha Krapp · Michael Beckwith · Michael Bourne · Michael James Ilett · michaelpick · michaelwp85 · Michal Czaplinski · Michelle Bulloch · Miguel Axcar · Miguel Fonseca · Miguel Lezama · Mikael Korpela · Mike McAlister · Mike Ritter · mikeb8s · Mikey Binns · milamj · Milana Cap · Mitchell Austin · mklusak · mleathem · mlf20 · Mobarak Ali · Mohit Dadhich · Morgan Estes · Mosne / Paolo Tesei · mossy2100 · mreishus · Muhibul Haque · mujuonly · Mukesh Panchal · Mumtahina Faguni · Nadir Seghir a11n · Naeem Haque · Nagesh Pai · Narendra Sishodiya · Naresh Bheda · Nate Finch · Nate Gay · Nazmul Hasan Robin · Nebojša Jurčić · nek285 · nendeb · neo2k23 · neotrope · Nicholas Garofalo · Nick Bohle · Nick Diego · Nick Halsey · Nick the Geek · Nicole Furlan · nidhidhandhukiya · Nihar Ranjan Das · Nik Tsekouras · Nikita Solanki · Niraj Giri · Nirav Sherasiya · Nithin John · Nithin SreeRaj · Noah Allen · Noruzzaman · nurielmeni · obliviousharmony · Olaf Lederer · Olga Gleckler · Oliver Campion · Olivier Lafleur · Omar Alshaker · Oscar Hugo Paz · p15h · Paal Joachim Romdahl · Pablo Hernández · Pablo Honey · Pamela Ribeiro · pander · Paolo L. Scala · Paragon Initiative Enterprises · Parin Panjari · Parth vataliya · Pascal Birchler · Pat O'Brien · Patricia BT · Patrick Lumumba · Paul Bearne · Paul Biron · Paul Kevan · Paul Schreiber · Paul Wilde · paulcline · Paulo Trentin · Pavan Patil · pcarvalho · Pedro Mendonça · perryrylance · Peter Rubin · Peter Wilson · petitphp · pevogam · Phi Phan · Phil Johnston · Philipp Bammes · philwebs · Pieterjan Deneys · Piotrek Boniu · Pitam Dey · Plamen Georgiev · Pooja N Muchandikar · pooja9712 · porg · ppolo99 · Praful Patel · Pranit Dugad · Pratik Kumar · Presskopp · prettyboymp · prionkor · pwtyler · Rachel Baker · Rachel Winspear · Rafael Fischmann · Rafael Gallani · Rafiqul Islam · Rahmat Gumilar · rahulharpal · Raj Patel · Rajin Sharwar · rajkumar shashwata halder · Ramon Ahnert · Ramon Corrales · ramon fincken · Ramon James · Ramswarup Rathod · Raul Martinez · rcneil · realthemes · Rejaul Alom Khan · Renatho (a11n) · reputeinfosystems · retrofox · Riad Benguella · Rich Tabor · Rick Hellewell · Riddhi Patel · Rishi Mehta · Rishi Shah · Rishit Gupta · rithik56 · Robert Anderson · Robert Biswas · Robert Ghetau · rocket.works - Dominik Friedrich · Rodel Calasagsag a11n · Rodrigo · Rodrigo Primo · Rohan Jha · rohitmathur7 · Rostislav Wolný · Roy Tanck · roygbyte · royho · rpf5573 · rslee · Ruchir Goswami · Rufaro Madamombe · Ryan Boren · Ryan Leeson · Ryan Urban · Ryan Welcher · S P Pramodh · Sébastien SERRE · Sérgio Gomes · Sören Wünsch · sadmansh · Saeed Piri · Sagar Tamang · sahiladit · Sainath Poojary · Sakib Mohammed · Sam Toohey · samiamnot · Sampat Viral · Samuel Sidler · Samuel Silva · Sanne van der Meulen · Sarah Norris · sarahricker · Sarthak Nagoshe · Sathiya Venkatesan · Satish Prajapati · Saul Fougnier · Saulius Vikerta · Saxon Fletcher · Sayedul Sayem · scholdstrom · Scott Buscemi · Scott Kingsley Clark · Scott Reilly · Scott Taylor · scottculverhouse · seanavers · Seif Radwane · Sergey · Sergey Biryukov · Serhiy Zakharchenko · Seth Rubenstein · Shail Mehta · Shalin Shah · Sharon Austin · sheulyshila · Shoe · Showrav Hasan · Shreya Agarwal · Silas Köhler · siliconforks · Simone Maranzana · Siobhan · smerriman · Sneha Patil · Sophie - a11n · Souptik Datta · Sourabh Jain · Sourav Pahwa · staurand · Stefano Minoia · stein2nd · Stephen Bernhardt · Steven Lin · Steven Thompson · Stoyan Georgiev · styleshit · Sudip Dadhaniya · Sumit Bagthariya · Sumit Singh · Sunil Prajapati · Sunny · superchlorine · Sybre Waaijer · Syeda Fahima Jannath · Takahashi Fumiki · Takashi Irie · Tammie Lister · Tanbir Ahmod · Tanvirul Haque · Tapan Kumer Das · Taylor Gorman · tdrayson · thejaydip · thelmachido a11n · them.es · Thomas Kräftner · Thrijith Thankachan · Timi Wahalahti · Timothy Jacobs · Tirth Doshi · tmanoilov · toastercookie · TobiasBg · tobifjellner (Tor-Bjorn “Tobi” Fjellner) · Tom Cafferkey · Tom de Visser · Tom J Nowell · tomhine · tomllobet · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · tropicalista · Troy Chaplin · Trupti Kanzariya · tunetheweb · twstokes · Ugyen Dorji · Umesh Gupta · Umesh Singh · up1512001 · Uttam Kumar Dash · valer1e · vertisoft · Vicente Canales · Vijaysinh Zala · Viktor Szépe · Vinit · Vipul Ghori · Vipul Gupta · vipulpatil · Vraja Das · vrishabhsk · wbdv · WebMan Design | Oliver Juhas · webwurm · wesrapyd · Weston Ruter · Will Skora · William Alexander · williampatton · wongjn · WPeople · wpsoul · wzieba · xipasduarte · Yani · Yann · Yannis Guyon · Yogesh Bhutkar · ytfeLdrawkcaB · Yui · Yukinobu Asakawa · Yuvrajsinh Sisodiya · Zack Krida · zeelthakkar · zitaruksergij · Zunaid Amin

More than 40 locales have fully translated WordPress 6.7 into their language making this one of the most translated releases ever on day one. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200 languages.

Last but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide.

Get involved

Participation in WordPress goes far beyond coding, and learning more and getting involved is easy. Discover the teams that come together to Make WordPress and use this interactive tool to help you decide which is right for you.

by Matt Mullenweg at November 12, 2024 09:35 PM under releases

WPTavern: Automattic Launches ‘WP Engine Tracker’ to Monitor Sites Leaving WP Engine, Sparking Controversy

The ongoing WordPress-WP Engine dispute has escalated with Automattic launching a new website – WP Engine Tracker, to track the number of websites leaving WP Engine hosting.

“An Automattic thingamajig,” this website tracks WP Engine hosting migrations from September 21, 2024, and also provides a downloadable CSV list of websites currently hosted on WP Engine, dubbed “sites ready for a new home.”

Other details on this single-page website include links to promotions offered by other hosting providers for migrating from WP Engine and the number of websites each hosting provider gained via migration. Pressable is the top gainer, followed by Bluehost and SiteGround. 

Ironically, the site’s URL is wordpressenginetracker.com as the whole WordPress-WP Engine dispute started with Matt accusing the hosting company of misusing the WordPress trademark. Also Automattic had opposed WP Engine’s lawsuit claiming their allegations regarding lost customers should be viewed with skepticism. 

Search Engine Journal reported that the website was blocked by Cloudflare for “suspected phishing,” but it is now up. It also reported about someone registering the domain name WPEngineTracker.com.

Eric Karkovack of The WP Minute tweeted, “Sort of like Ford tracking everyone who switched from Chevy. Doesn’t matter to me, I’m a Honda guy.” WordPress developer Brian Coords shared this: “This has nice design/dev, but it’s sad to see talent and resources poured into increased negativity in the community, criticism without substance, tearing down instead of building up. Just sad that’s what WordPress is becoming a symbol for.”

Security researcher Daniel Ruf dubbed it “amateurish”. He continued, “I’m not sure what the goal of this website is and what Matt tries to achieve. But the community is getting increasingly annoyed of such unprofessional behavior of Matt and in the security community some also think about dropping 0days for WordPress and related plugins/themes due to this whole situation. The feedback under the tweet from the official WordPress account and in the reddit community shows, what most of us think. The whole situation hurts everyone more than needed.”

Another person commented, “So Automattic has put together a list for spammers and hackers to use to target a bunch of sites who are no longer doing business with Matt Mullenweg’s nemesis. That’s… shortsighted. This will surely result in legal action from one or more of these sites?” 

As of November 12, 18,280 websites have left WP Engine according to this website.

by Jyolsna at November 12, 2024 07:25 PM under wp engine

WPTavern: Design Team Unveils New WordPress Design System Figma Library

Automattician James Koster has announced the launch of a new WordPress Design System library for Figma, the popular tool the design team uses to create mockups and prototypes for WordPress. “The intention of this resource is to streamline the design process for folks working in the WordPress ecosystem,” he explained. 

The design library offers a comprehensive range of components, including buttons, forms, icons, and menus, bringing everything you need into one place. It also includes style tokens that allow you to easily manage visual details like radius, elevation, color, and typography. For added convenience, the library provides handy stickers for individual components, and more extensive UI elements like the full-screen editor and site editor.

James also revealed that the “intention is to publish a new version of the library in line with each Gutenberg release, and from 6.8 each major WordPress release too.”

For WordPress Design Team members, the library will be automatically enabled in all new design files within the WordPress.org community Figma organization. Designers working in other Figma organizations can access it by duplicating the file from the community page and publishing it in their own organization.

For those new to Figma, the WordPress Design Team recommends checking out Figma’s “Learn” platform, which offers a comprehensive “Get Started” section to help users become familiar with the tool.

You can leave your feedback in the source file or on the Gutenberg repository on GitHub

The community has responded positively to the new library. WordPress committer Tammie Lister shared, “It also is a step towards the true design system needed. Figma is a part of the system, but an important piece when updated regularly.”

Courtney Robertson, Open Source Developer Advocate at GoDaddy, tweeted, “#WordPress just stepped up its design game with a brand-new Figma Library as part of its Design System. Designers, it’s time to explore a more seamless workflow!”. 

by Jyolsna at November 12, 2024 04:38 PM under design

Do The Woo Community: Strategies for Selecting Effective Marketing Channels with Afshana Diya

In this episode of Woo BizChat, Katie Keith and Afsaneh Diya discuss effective marketing strategies for WooCommerce and WordPress businesses, emphasizing audience understanding, community engagement, and diverse marketing channels.

by BobWP at November 12, 2024 09:00 AM under SocialMediaMarketing

Matt: RIP Quincy Jones

Quincy Jones had such an impact on the culture that it’s impossible to summarize. His discography is amazing. I feel so lucky to have met him in 2012 when I was much earlier in my career, and he didn’t have any reason to give me time, but he treated everyone as if they were important. We talked a lot about his Count Basie and Frank Sinatra days. If you’re unfamiliar with him, the Quincy documentary on Netflix is a good start. His musical fingerprints are everywhere, including the super-catchy theme songs for Sanford and Sons and Austin Powers.

He passed away last week, on November 3rd. As a tribute, here are ten albums he was involved in from the jazz side that have been big parts of my life. I’ll link to Spotify, but find them wherever you can:

  1. Sinatra at the Sands, Quincy arranges and directs the Count Basie band. This live album is great to listen to, you also get Frank doing stand-up comedy.
  2. It Might As Well Be Swing, Frank Sinatra.
  3. Julian “Cannonball” Adderley.
  4. Sonny Stitt Plays Arrangements from the Pen of Quincy Jones.
  5. Ella and Basie.
  6. The Genius of Ray Charles.
  7. For Those in Love, Dinah Washington.
  8. Dizzy and Strings, Dizzy Gillespie.
  9. Quincy Here We Come, Benny Bailey. (The track Meet Benny Bailey has an excellent tribute on Manhattan Transfer’s Vocalese.)
  10. Social Call, Betty Carter.

I put all ten into one Spotify playlist if you want to check them all out.

by Matt at November 12, 2024 05:57 AM under Music

November 11, 2024

Gravatar: 7 Actionable Steps to List Your Social Media Handles Effectively

Social media handles are your digital name tags – they help people find and connect with you across every platform. When chosen and used strategically, these identifiers do more than just label your accounts; they make your brand more recognizable and help grow your following. 

From major corporations to personal brands, the right social media handle can be the difference between getting lost in the crowd and standing out online. These handles are like a unique fingerprint across platforms, and their presentation on business cards, websites, product packaging, and marketing materials can leave a lasting impression.

While it may sound like a simple thing, there is a strategy to it, and we’re here to show you exactly that. This guide walks you through seven actionable steps to list your social media handles effectively. 

From crafting consistent handles to harnessing modern tools like QR codes and integrating your profiles into video content, you’ll discover practical strategies to boost your brand’s following and make your social profiles easily accessible.

Step 1: Choose consistent and memorable social media handles

Being consistent with your social media handles builds recognition and allows your audience to find you across different platforms. Think of your handle as your digital signature – the more consistent it is, the more memorable you become.

Inconsistent handles, on the other hand, could confuse your audience. Imagine a small business called “Green Leaf Gardens,” which has different handles on each platform:

  • Instagram: @greenleafgardens
  • Twitter: @GLGardens2023
  • Facebook: @greenleaflandscaping
  • TikTok: @thegardeningexperts
  • LinkedIn: @green-leaf-gardens-llc

The mix of abbreviations, numbers, and different business names confuses potential customers and dilutes brand recognition. Using @greenleafgardens consistently (or a close variation if the exact handle isn’t available) would create a stronger, more memorable online presence.

So, how can you prevent that? 

  1. Pick a handle that’s up for grabs on all the platforms that matter to you. We’re talking Instagram, Twitter (now X), Facebook, LinkedIn, TikTok, and any niche networks where your audience hangs out.
  2. Keep it short and sweet. The simpler your handle, the easier it is to remember and type.
  3. Make sure it reflects your brand. Your handle should give people a taste of who you are or what you do.

💡Pro tip: Start with the social platforms where your audience spends most of their time. But don’t stop there – grab your handle on emerging platforms, too, even if you’re not ready to use them yet – you might need them in the future.

Use Namechk and KnowEm to ensure handle availability

Before you commit to a handle, take it for a test drive. Free tools like Namechk or KnowEm can show you if your dream handle is available across multiple social media platforms and domains. 

If your first-choice handle is taken, don’t panic. Get creative with variations that still keep your brand identity intact. Maybe add your location or an industry keyword. For example, @JohnDoeBakeryNYC tells people who you are, what you do, and where you’re based.

And here’s a crucial step many folks overlook: check for potential trademark issues. The last thing you want is a legal headache down the road. A quick search of your local trademark office can save you a world of trouble.

💡Pro tip: If you’re unsure about potential trademark conflicts, it’s worth chatting with a legal pro specializing in intellectual property.

Step 2: Optimize handles for each platform’s format

Each social media platform has its own handle requirements that you need to be aware of. 

For example, the character limitations are different. Twitter (now X) has a 15-character limit, while Instagram gives you a bit more breathing room with 30 characters. LinkedIn takes a different approach, using URLs like linkedin.com/in/username without the “@” symbol.  Sometimes, you might need to tweak your handle slightly to fit a platform’s requirements. That’s okay, but try to keep it as close to your brand name as possible. 

Now, let’s talk symbols. On most platforms – Twitter, Instagram, TikTok – your handle starts with an “@” symbol. It’s like a universal “hey, this is a social media handle” sign. However, platforms like LinkedIn and Facebook often skip the “@” and use the full profile URL instead.

Here’s a hot tip: avoid unnecessary symbols or numbers in your handle unless they’re essential to your brand identity. Sure, @JaneDoe_123_NYC might be available, but it’s a mouthful to say out loud and a pain to type. Keep it clean and simple.

Different platforms have different purposes, and your handle should adapt accordingly. LinkedIn, for instance, is all about professional networking. So, your handle there might be more formal than your fun, casual Instagram handle. 

Finally, don’t forget to create a custom URL where possible. On LinkedIn or Facebook, you can often set up a custom URL (like linkedin.com/in/YourBrandName) that aligns closely with your handles on other platforms. It’s an easy way to keep your brand consistent across the board.

Step 3: Display social media handles on marketing materials creatively

Your marketing materials are a great opportunity to plug your social media handles and are often the first thing people look for in business cards, brochures, and product packages. Here’s how to make the most of it:

  • Use clear, readable fonts: Choose fonts that are easy on the eyes, especially for smaller spaces like business cards, and make your handles stand out without overwhelming the design.
  • Incorporate social media icons: Place recognizable icons (Facebook, Instagram, Twitter, etc.) next to your handles and in your email signatures. They have to be high-resolution and align with your overall branding.
  • Showcase handles on product packaging:  If you sell physical products, use that space to encourage social engagement. For example, you can include your handles with a call-to-action like “Tag us on Instagram!”
  • Leverage event materials: Print your social handles on banners, posters, and promotional merchandise. You could also use items like T-shirts or tote bags to encourage attendees to follow you online.

Step 4: Display your social handles in one place with Gravatar

Promoting your social media handles across platforms can complicate things for your target audience, so the best course of action is to use a centralized page where they can find everything. 

Gravatar is a free tool that lets you create a dynamic profile and include different types of information for your audience to see, including your verified social media profiles and other important links. 

Gravatar verified accounts section

The most important feature of Gravatar is its automatic synchronization – update your profile in one place, and it will reflect across all connected platforms, which includes Slack, OpenAI, WordPress.com, GitHub, and more! 

On top of that, Gravatar allows you to verify your accounts, adding a layer of trust and authority. This is especially valuable for online personalities, entrepreneurs, CEOs, artists, and other professionals. 

In short, this is the perfect place for you to add all your social handles and easily share them across your website, email signatures, business cards, and marketing materials. You can do this by adding your personal Gravatar .link URL or generating a QR code directly from the platform. 

Gravatar QR code

This can be extremely useful as it provides users with instant access to all your verified social profiles with one quick scan.

Gravatar lets you create a cohesive, professional online presence that boosts your brand’s visibility and credibility. It ensures that your audience knows they’re connecting with the real you, no matter which platform they’re on.

Step 5: Leverage QR codes to simplify access

Speaking of QR codes, here’s how to utilize them effectively. 

  • Use reliable, free QR code generators such as QR Code Generator, Scanova, or Bit.ly to create scannable links for individual platforms or a single page listing all your profiles (e.g., a Gravatar profile or Linktree page). As noted above, if you have a Gravatar profile, you get a QR code for free and won’t have to use external tools. 
  • Always test your QR codes before implementation to ensure they direct users to the correct destination.
  • Include QR codes in physical assets like business cards, product packaging, in-store displays, printed advertisements, and flyers.
  • Develop platform-specific QR codes. If your target audience favors different social networks, create separate QR codes for each platform. Alternatively, use a single QR code to direct people to a central page listing all your social handles.
  • Opt for dynamic QR codes when possible. Unlike static codes, dynamic versions can be updated after printing, providing flexibility if you need to change the destination link. This feature lets you modify your digital information without reprinting materials if you update your social handles.

Remember, QR codes are most effective when paired with clear instructions and a compelling reason to scan. Provide context for what users will gain by scanning – whether it’s access to exclusive content, special offers, or a comprehensive view of your social profiles.

Step 6: List social media handles on your website and landing pages

Your website and landing pages are prime real estate for showcasing your social media handles. By strategically integrating these handles, you can create a true connection between your web presence and social profiles.

Include social media icons in key website locations

Social media icons are a standard and effective method to display your handles on your website. These icons typically link directly to your social profiles, allowing visitors to follow you with a single click, which is why it’s good to place them in prominent areas like the header, footer, and contact sections of your website. This ensures visitors can easily access your handles regardless of which page they’re on.

It’s also recommended that you use branded, recognizable icons to maintain a professional appearance and keep the user experience consistent. Still, make sure that they fit your website’s design and color scheme.

Embedding live social media feeds

Display live content from various platforms, such as Instagram posts, Twitter/X updates, or TikTok videos on strategic pages. For example, if you’re a food blogger, you could include an instagram feed with mouth-watering content that will entice people to follow you there. 

What’s important here is to make it as easy as possible for readers to find you, and the best way to do this is through CTA buttons. Place them at the end of blog posts, on product pages, or in pop-ups. Direct visitors to your social platforms with clear, actionable prompts.

Optimize social media links for mobile users

With a significant portion of web traffic coming from mobile devices, remember to make your social media links mobile-friendly. Here’s how to do that: 

  • Make links easily tappable: Icons and links have to be large enough for easy interaction on mobile screens. Avoid clustering links too closely together to prevent accidental taps.
  • Ensure responsive design: Verify that linked pages are optimized for mobile browsing and test the user experience across various devices and screen sizes.
  • Consider load times: Slow-loading social media elements can frustrate users and decrease engagement, so don’t forget to optimize icon images and linked content for quick loading on mobile networks.

Step 7: Promote social media handles in video and audio content

Incorporating your social media handles into video and audio content can significantly boost your online presence. This approach allows you to reach audiences across multiple platforms and encourages cross-platform engagement.

Display social media handles as text overlays in videos

Text overlays are an effective way to make your handles visible without disrupting the main content of your videos.

  • Use lower-thirds for handle display
    • Place your handles in the bottom section of the video, commonly known as lower-thirds.
    • Ensure the text is clear and easy to read on both desktop and mobile devices.
  • Match branding with font choice
    • Select fonts that align with your overall brand aesthetic.
    • Keep the text professional and easily legible.
  • Balance visibility and subtlety
    • Make sure your handles are noticeable without overwhelming the video’s visuals.
    • Consider using semi-transparent overlays to minimize distraction.

Add social media handles to the description box of video platforms

Video platforms like YouTube, TikTok, and Vimeo offer valuable space in their description boxes for promoting your handles.

  • Prioritize handle placement
    • List your most important handles at the top of the description.
    • Use clickable links to make it easy for viewers to follow you immediately after watching.
  • Tailor approach for different platforms
    • On TikTok, where space is limited, focus on your primary handle in the caption or on-screen text.
    • For YouTube, utilize the expanded description space to list multiple handles and provide context.

Mention handles verbally in video and audio content

Verbal mentions of your social media handles can reinforce them and prompt your audience to follow you. However, you need to be strategic: Include handle mentions at the start, during transitions, or at the end of your content. For longer content like podcasts, naturally incorporate handle mentions during topic transitions.

We also recommend briefly explaining what kind of content followers can expect on each platform and using a call-to-action approach, encouraging listeners to connect with you on social media.

Include social media handles in end screens or outro segments

End screens and outros are prime locations for promoting your social media handles, as viewers often decide what to do next after finishing a video.

  • Create branded end screens
    • Design clear, visually appealing end screens that prominently feature your handles.
    • Include CTAs like, “Follow us on Instagram @YourHandle for behind-the-scenes content.”
  • Utilize platform-specific features
    • On YouTube, use the end screen feature to display clickable social media icons alongside your handles.
    • Ensure these elements are easily clickable on both desktop and mobile devices.

Promote social handles during live streams

Live streams offer real-time opportunities to promote your social media handles while interacting directly with your audience. Use a persistent on-screen graphic showing your primary social media handles and rotate different handles throughout the stream if you’re active on multiple platforms.

You can also verbally encourage follows by periodically reminding viewers to follow you on other platforms and highlighting exclusive content or benefits available on specific social media channels.

Utilize social media handle watermarks in visual content

Watermarks ensure your handle remains visible even if your video is shared across different platforms. Place the watermark in a corner of the video where it won’t distract from the content and ensure it’s noticeable enough for viewers to remember and easily read.

Remember to be consistent! Use the same watermark design across all your video content for brand recognition. Consider using your primary social media handle as the watermark for maximum impact.

Take control of your online presence with Gravatar today

Effectively listing and promoting your social media handles is crucial for building a strong online presence. Consistency and visibility are key, but so is efficiency. Managing multiple social media profiles can become time-consuming, especially when updating handles or ensuring consistency across platforms.

Gravatar offers a straightforward solution for organizing your online presence, making it easier for others to find and follow your profiles without having to manage multiple platforms. With Gravatar, you can:

  • Create a centralized profile listing links to all your social media accounts, website, portfolio, and other online presences.
  • Link to your Gravatar profile in email signatures, websites, business cards, and even physical marketing materials using a QR code.
  • Verify your social media accounts and links, adding a layer of trust and authority to your online presence.

Whether you’re a small business owner, entrepreneur, or social media manager, Gravatar provides a streamlined solution to keep your social media handles up-to-date and visible across your digital footprint.

Take the first step in simplifying your online presence management. Create your Gravatar profile now and start showcasing your social media handles across all platforms with ease.

by Ronnie Burt at November 11, 2024 09:56 PM under Digital Identity Management

Do The Woo Community: How to Follow Do The Woo on the Fediverse

Do The Woo has joined the Fediverse, allowing users to engage with episodes and blog posts across decentralized platforms like Mastodon and Threads.net.

by Matthias Pfefferle at November 11, 2024 09:42 AM

November 08, 2024

Gravatar: Gravatar’s Guide: Crafting an Outstanding Digital Business Card

Imagine that you’re at a networking event, eager to make connections, but you’ve run out of business cards. Or worse, you hand someone a card only to realize it has outdated information. Situations like these highlight why professionals are turning to digital business cards. These modern alternatives offer a dynamic way to share your contact details and personal brand, complete with rich media content and real-time updates.

Digital business cards shine in both online (as a link in bio tool, in the footer of contact pages and emails) and offline (in-person networking and contact sharing) settings. So, whether you’re adding them to your email signature or sharing them at in-person events, they make networking and follow-ups much easier. 

🌱 As a bonus, they’re environmentally friendly, reducing paper waste.

However, creating an effective digital business card comes with challenges. Many solutions can be costly, and designing one without the necessary skills can be daunting. Thankfully, Gravatar exists – a completely free and powerful platform for crafting digital business cards.

This guide will show you how to use Gravatar to create a professional, eye-catching digital business card – no design expertise required!

Necessary features and design elements for your digital business card

While it’s good to be creative and unique with your digital business card, you still need some essential elements. Let’s see what they are: 

  • Profile photo: It’s often the first thing people notice, so choose a clear, well-lit, high-quality headshot that reflects your professional persona.
  • Contact information: Include the essentials such as name, job title, company, email, and phone number. Remember, digital cards allow for easy updating if any details change.
  • Social media links: Add links to your relevant social profiles. This expands your networking reach, allowing connections to engage with you on multiple platforms.
  • Personal website or portfolio link: Showcase your work and drive traffic to your site by including a link to your personal website or portfolio.
  • Brief bio or tagline: Craft a concise personal statement that encapsulates your professional identity or unique selling point. Keep it short, sharp, and memorable.
  • Customization options: Your digital card should align with your personal brand, especially the visuals, such as the color scheme, fonts, and overall design. For example, you could use the same font as you would on your website but also include an effective one-liner like you would on LinkedIn. 
  • Sharing methods: Ensure your digital card is easily shareable both online and offline. For example, you can create your own QR code that people can scan and access your card in seconds. Online, the most effective way is to have a nice, short, custom URL
  • Easy follow-ups and contact: Your business card needs to make it easy for people to follow up and contact you when they want to. That means including your email signature in your business card, or links to contact forms. 
  • Privacy controls: Make sure you can control what information is visible and to whom. This flexibility allows you to tailor your card for different professional contexts.
  • Integration capabilities: Consider how your digital card might connect with other tools you use regularly, such as CRM systems or other professional platforms.

Create a stunning digital business card with Gravatar – no design skills needed

Gravatar homepage

Enter Gravatar: your free ticket to a globally recognized digital identity. This platform is a powerful tool for managing your online presence across thousands of websites and services. Think of it as your universal digital business card and personal branding hub all rolled into one.

Ronnie Burt’s Gravatar profile

What sets Gravatar apart? Its simplicity. You don’t need to be a design guru to create a standout profile. Just upload an avatar and fill in your details, and you’re good to go. But don’t let the ease of use fool you – there’s plenty of room for customization. You can play with background colors, tweak button hues, or add a custom-branded header and footer. 

Demo profile in Gravatar

You can even rearrange the layout to suit your style. And for those who want to go the extra mile, why not embed a video introduction? It’s all about making your digital card uniquely you.

Here’s what you can pack into your Gravatar profile:

  • Your chosen avatar image (make it a good one!)
  • Name and a snappy biography
  • Contact information (email, website)
  • Links to your social media profiles
  • Other relevant links (portfolio, projects, etc.)

But here’s where Gravatar really shines: automatic synchronization. Update your profile once, and those changes instantly appear across all connected platforms  – no more scrambling to update multiple online profiles when you change jobs or contact details. This ensures your personal brand stays consistent everywhere you appear online, from professional forums to project collaborations. 

And for those in-person networking moments, you can generate a QR code for your Gravatar profile and watch as people scan their way straight to your digital doorstep.

Android and Apple Wallet Support, Too

Never fumble for a business card again. Your Gravatar profile now lives in your phone’s wallet!

Quick Setup:

  1. Log into your Gravatar profile
  2. Click the ‘Share profile’ button
  3. Select ‘Add to Apple Wallet’ or ‘Add to Google Wallet’
  4. Tap to add – you’re done!

Why You’ll Love It:

  • Always on hand – even when your phone is offline
  • Share your profile with a quick tap
  • Updates automatically when you change your Gravatar
  • Looks sleek in your digital wallet
  • Perfect for conferences and meetups
  • More eco-friendly than paper cards

🌟 Here’s a neat trick: Gravatar integrates with comment systems on many blogs and news sites. This means your digital business card can pop up alongside your online contributions, turning everyday interactions into potential networking gold.

Responses to comments in Gravatar

So, ready to create a digital business card that works as hard as you do? Let’s dive into how you can make Gravatar work its magic for your professional brand.

Future-proof your networking: Create a digital business card with Gravatar

Gravatar isn’t just another digital business card platform – it’s a revolution in online networking. Its unique email-based system allows you to manage multiple online identities effortlessly. And with thousands of integrated platforms, your Gravatar profile becomes a centralized hub for your digital presence.

Worried about design skills or costs? Gravatar eliminates these common hurdles. It’s free, user-friendly, and doesn’t require a degree in graphic design to look professional.

Head to Gravatar.com and create your free profile using your email address. It’s time to build a digital business card that works as hard as you do!

by Ronnie Burt at November 08, 2024 10:13 PM under Digital Identity Management

Do The Woo Community: Friday Shares: This Week’s Must-Reads and Community Highlights, v3

This week’s highlights include WordPress 6.7 updates, community events, sponsorship calls, new resources, and insights into web development and e-commerce strategies.

by BobWP at November 08, 2024 10:42 AM

WPTavern: WooCommerce Set to Launch New Logo in 2025

WooCommerce is all set to roll out a new logo in early 2025. Tamara Niesen, Chief Marketing Officer at Woo told WP Tavern, “We saw an opportunity to evolve the brand so it aligns with our new product vision and gives us a solid foundation for continuing to grow our business. The new direction helps us stand out. It’s bold, fresh, and communicates what we do and who we’re for.”

The updated logo, featuring a lively purple and white color palette, has already sparked a buzz in the WordPress community. It showcases “WOO” in white against a deep purple background, sometimes transitioning into a shopping cart, with the “O”s doubling as wheels—perfectly representing a platform that powers millions of online stores worldwide.

Jay Walsh, Director of Communications at WooCommerce.com, shared that they recently discussed plans around the Woo and WooCommerce brand and identity during the keynote session of this year’s WooSesh. The team teased a refreshed WooCommerce logo treatment during the keynote, which is part of the wider effort to make the Woo brand, voice, and identity bolder and more engaging for current and future merchants. 

“Evolving our brand and our main product is crucial to our strategy of growing new stores, reaching new merchants, and maintaining our position as the world’s most popular commerce platform”, he explained. 

The animated logo has been a hit, drawing comments like “one of the best logos I’ve seen in a while” to “This is so darn cool.” BobWP of Do the Woo Podcast tweeted, “In case you missed this. And coming from someone who used to design logos professionally, the simplest ideas, which now seem obvious, are the hardest. Great job!” 

Remkus de Vries of Within WordPress newsletter, shared his excitement saying, “It’s very rare to see a rebrand with a new logo where I immediately go “Wow, that’s a huge improvement, I love it”, but when I saw this last week, that’s exactly what I thought.”

Despite the enthusiasm, a few critics questioned the color choice, but WooCommerce Product Lead James Kemp has assured that “the whole rebrand is super vibrant and the purple has been enhanced.”

by Jyolsna at November 08, 2024 08:35 AM under woocommerce

November 07, 2024

Gravatar: Choosing the Right Personalization Tool: Top 7 for Your Website

Are you struggling with high bounce rates and lackluster conversions on your website? You’re not alone. Many businesses find it hard to create engaging, relevant experiences for their online visitors, leading to missed opportunities and lost revenue because, as shown in a recent McKinsey report, 71% of consumers now expect personalized interactions from companies

If you don’t provide them with one, you’re losing business, plain and simple. 

Thankfully, there are many website personalization tools that are transforming how businesses connect with their audience online. These tools enable companies to deliver individualized experiences that resonate with each visitor, going beyond traditional segment-based approaches. 

In the following sections, we’ll explore the top 7 personalization tools and their features, showing you how to unlock new levels of engagement and business success. 

Introducing the top 7 website personalization tools

1. Gravatar

Gravatar homepage

Gravatar is a unique tool in the world of website personalization. It simplifies user profile management and enhances personalization based on users’ email addresses, offering a distinct advantage by utilizing data already provided by users. This approach allows developers to personalize site experiences without extensive data collection.

Gravatar offers two powerful APIs for integration:

  1. The Avatar API that is designed specifically for requesting avatars.
  2. The Profiles-As-A-Service API, which enables developers to import comprehensive profile information.

These APIs create a centralized hub where users can update their information once, and it syncs across all Gravatar-integrated sites. Gravatar has also introduced Interests, allowing users to list specific topics they’re interested in – something that can change the game for website owners looking to understand user preferences. 

Gravatar Interests section

For example, an e-commerce site could show personalized product recommendations based on these interests.

Best features:

Example of a Gravatar profile page
  • This profile automatically appears on any Gravatar-enabled site, providing a consistent identity across platforms.
  • Users can add important information such as avatar, bio, pronouns, and job info – update once, sync everywhere.
  • Gravatar is natively supported by WordPress, enabling effortless avatar management for WordPress users and developers without additional plugins or code.

For developers looking to import user profiles, integration with Gravatar’s profile API is needed. To streamline the user experience, it’s recommended to explain to users that they can control their avatar and profile information directly from their Gravatar profile.

Use cases: Gravatar is particularly beneficial for developers, bloggers, and business owners. It provides a consistent brand image across platforms and maximizes engagement by offering personalized user experiences.

Used by: Gravatar integrates with popular platforms like WordPress.com, Slack, OpenAI, Figma, and Mailchimp, demonstrating its versatility and wide-reaching impact.

Price: One of Gravatar’s standout features is its pricing model – or lack of. It’s a completely free service for site owners, developers, and users, and is run and supported by Automattic. There’s no paid version and no usage limits, making it an accessible option for businesses of all sizes.

2. Dynamic Yield 

Dynamic Yield homepage

Dynamic Yield is a powerful player in the website personalization arena, known for delivering personalized onsite experiences through AI-powered targeting and real-time analytics.

Best features:

  • Contextually relevant content: Delivers personalized content based on user behavior and preferences. For instance, a returning visitor interested in sports might see sports-related content prominently displayed on the homepage.
  • Product recommendations: Uses AI to suggest products based on browsing history and purchase patterns. An online retailer could use this to show complementary items to those in a user’s cart.
  • Personalized messages: Tailors messaging based on visitor behavior and characteristics. A travel website might show different promotional messages to first-time visitors versus frequent bookers.
  • Real-time personalization: Adapts content in real-time as users interact with the site. For example, a news site could reshuffle article placement based on what the user clicks on during their visit.

Dynamic Yield integrates well with other tools to enhance personalization efforts, particularly Twilio Segment, a customer data platform enabling real-time data collection and action.

Use cases: Businesses can use Dynamic Yield to increase engagement and conversion rates, such as personalizing homepage experiences for returning visitors.

Used by: McDonald’s, PacSun, Cotopaxi, among others.

Price: Dynamic Yield offers a customized pricing model tailored to each client’s specific needs and scale. For detailed pricing information, you’ll need to contact their sales team directly.

3. Optimizely

Optimizley homepage

Optimizely is a leading digital experience platform that empowers businesses to create, experiment, and personalize user experiences.

Best features:

  • A/B testing and multivariate testing: Allows testing of different page versions to identify the most effective elements. An e-commerce site could test different product page layouts to see which leads to more purchases.
  • AI-driven optimization: Uses machine learning to automatically optimize experiences. This could involve automatically adjusting the placement of call-to-action buttons based on user interaction patterns.
  • Personalized content delivery: Serves different content to different user segments based on their data. A software company might show different feature highlights to enterprise visitors versus small business owners.
  • Integrations: Make the most out of Optimizely by combining it with tools like Twilio Segment, Google Analytics, and Adobe Experience Cloud.

Use cases: Businesses can increase engagement and conversion rates by running A/B tests on different versions of their product pages to identify the most effective elements.

Used by: eBay, American Express, Dolby, Fjallraven, among others.

Price: Optimizely offers a customized pricing model tailored to each client’s specific needs and scale. Contact their sales team directly for detailed pricing information.

4. HubSpot 

Hubspot homepage

HubSpot is a popular all-in-one CRM platform offering many powerful tools for marketing, sales, and customer service, with a strong emphasis on website personalization.

Best features:

  • Smart Content: Dynamically adjusts website content based on user attributes and behavior. For example, a B2B site could show different case studies to visitors from different industries.
  • Personalized CTAs: Displays different call-to-action buttons to different user segments. A SaaS company might show a “Start Free Trial” CTA to new visitors and an “Upgrade Now” CTA to existing customers.
  • Automated workflows: Creates personalized user journeys based on user actions and characteristics. This could involve sending a series of targeted emails based on which resources a user has downloaded.

Use cases: Businesses can use HubSpot to increase engagement and conversion rates by delivering targeted CTAs to specific visitor groups.

Used By: Tripadvisor, Eventbrite, WeightWatchers, and more.

Price: HubSpot offers tiered pricing plans for their different products, which include marketing, sales, service, content, operations, and commerce. All of them start at $15/month per seat and can go up to $3,600/month, depending on what you need. They also have many free tools, so you can get a taste of the platform before you commit to subscribing. 

5. Hyperise

Hyperise homepage

Hyperise is a personalization platform that allows businesses to dynamically personalize images and content across various digital touchpoints.

Best features:

  • Dynamic image personalization: Customizes images based on user data. A real estate site could show property images with the visitor’s name on the “For Sale” sign.
  • Personalized text overlays: Adds personalized text to images or videos. An online course platform could add the user’s name to certificate images in promotional materials.
  • CRM integration: Pulls data from CRM systems to personalize content. This allows for using detailed customer information, like past purchases or support interactions, in personalizing the web experience.

Use cases: Businesses can use Hyperise to create personalized landing pages for different audience segments, enhancing relevance and engagement.

Used by: G2, Placer.ai, SalesLoft, and Orca Security

Price: Hyperise offers various pricing plans, depending on what you want included. Their Images plan costs $69/month per seat and lets you create personalized images for your outreach. The other two tiers include adding a website and videos. 

6. Marketing Cloud Personalization by Salesforce

Salesforce marketing personalization homepage

Salesforce, formerly known as Evergage, is a comprehensive customer data platform that now also includes a personalization engine as part of its marketing tools. Businesses can use their tools to create individualized experiences across multiple channels, including web, mobile, and email.

Best features:

  • Real-time segmentation: Groups users based on their current behavior and historical data. An airline website could segment users based on their typical flight patterns and current browsing behavior.
  • Dynamic content personalization: Adapts content in real-time based on user segments and behavior. A media streaming service could adjust its homepage layout based on the user’s viewing history and current trends.
  • Journey orchestration: Creates and manages personalized customer journeys across multiple touchpoints. A bank could create different communication sequences for customers based on their life events, like buying a house or starting a business.

Use cases: Businesses can use Salesforce for personalized product recommendations and content tailored to individual shopping behaviors.

Used by: General Mills, Formula 1, Accenture, among others.

Price: This service comes in three tiers: Marketing Cloud Engagement, Marketing Cloud Account Engagement, and Marketing Cloud Growth Edition. The first two tiers go for $1,250/month, while the third is $1,500/month per organization.

7. Yieldify

Yieldify homepage

Yieldify is a platform designed to optimize customer journeys through personalized experiences and conversion rate optimization, focusing on e-commerce businesses.

Best features:

  • Personalized overlays and pop-ups: Creates targeted messages that appear based on user behavior. An e-commerce site could show a discount pop-up to users who are about to leave the site without purchasing.
  • Behavioral targeting: Tailors experiences based on user actions and characteristics. A fashion retailer could show different promotional banners to users based on the categories they’ve been browsing.
  • Data-driven insights: Provides analytics to help understand user behavior and optimize personalization strategies. This could help identify which personalization tactics are most effective for different user segments.

Use cases: Businesses can use Yieldify to reduce cart abandonment through exit-intent pop-ups and promote special offers based on user behavior.

Used by: Lacoste, Kiehls, Clarins, The North Face, among others.

Price: Yieldify offers customized pricing based on specific needs. Contact them directly to get started and obtain pricing information.

Selecting the ideal personalization tools for your website

Choosing the right personalization tools for your website is crucial for maximizing engagement and conversion rates. Here’s how to approach this important decision:

Step 1: Understand your needs

Before selecting a tool, identify your specific goals and challenges. Are you looking to improve user engagement, increase conversion rates, or streamline user profile management? Assess your current marketing stack and identify integration needs to ensure quick and easy implementation.

Step 2: Evaluate key features

Create a list of essential features you need in a personalization tool. Consider factors such as:

  • Ease of use and integration
  • A/B testing capabilities
  • Real-time analytics
  • User-friendly interfaces to reduce the learning curve for your team

Don’t overlook the importance of data privacy and security. Tools like Gravatar emphasize user control over personal information, allowing users to edit their public profiles and share only what they’re comfortable with. Ensure the tool complies with regulations such as GDPR and CCPA for legal data handling practices.

Step 3: Analyze cost and ROI

Consider both short-term costs and long-term value when evaluating tools. Low-cost and free tools like Gravatar offer high value and low risk, making them excellent starting points for personalization efforts.

Step 4: Success stories

Look at real-world examples of companies successfully using personalization tools to drive growth. For instance, a great example of successful personalization is the plant-based cosmetics brand Clarins which increased conversions by 20% using Yieldify. Some of the strategies they implemented include: 

  • Adding virtual consultations to help users find the best products. 
  • Guiding users to book a complimentary phone consultation with a specialist on category pages. 
  • Re-engaging shoppers who try to change tabs with special overlays that include basket reminders and introducing Clarins’ three complimentary products that they offer with each order. 

Looking at examples like this will show you the full potential of the specific platform and maybe even give you some ideas on how you can implement similar strategies in your own business. 

Step 5: Make an informed decision

Finally, whenever you can, take advantage of demos to better understand each tool’s capabilities before making a decision. Weigh the risk versus reward, keeping in mind that tools like Gravatar offer easy integration and are free to use, making them a low-risk option to start with.

Unlock the potential of your website with personalization tools 

Website personalization tools are powerful assets in enhancing customer engagement and boosting conversion rates. By tailoring user experiences, these tools provide a significant competitive advantage. In fact, companies excelling at personalization generate 40% more revenue than their counterparts.

When choosing personalization tools, consider factors like powerful features, integration capabilities, and ROI measurement. 

Gravatar stands out with its unique advantage of utilizing existing user data for personalization without extensive on-site data collection. Its Profile API allows developers to create more detailed and personalized user experiences by integrating additional user information into their websites.

As you explore the tools we’ve discussed, consider how they align with your business needs. Remember, Gravatar is an excellent starting point – it’s both highly useful and free. 

So what are you waiting for? Take the best out of website personalization and create experiences that your users will love! 

by Ronnie Burt at November 07, 2024 05:33 PM under Digital Identity Management

Do The Woo Community: Do the Woo is Trailbazing the Fediverse with Matthias Pfefferle and Derek Hanson

Do the Woo is on the Fediverse with multi-authors, audio distribution and more to come.

by BobWP at November 07, 2024 10:15 AM under fediverse

November 06, 2024

Do The Woo Community: Press Release: Do the Woo 4.0 Official Launch, Elevating Voices in the WordPress Community

Press Release: The official launch of the Do the Woo Podcast Channel 4.0 takes place during WordCamp Europe in Turino, Italy.

by BobWP at November 06, 2024 03:00 PM

WPTavern: #144 – Damon Cook & Seth Rubenstein on the Transformational Interactivity API

Transcript

[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast, which is dedicated to all things, WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, how the Interactivity API will transform your WordPress websites.

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

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

So on the podcast today we have Damon Cook and Seth Rubenstein.

Damon Cook is a developer advocate with WP Engine, and previously worked as a front end developer at several WordPress focused agencies.

Seth Rubenstein began his WordPress journey in college, and is now the lead engineer at the Pew Research Center, where he works on interactive WordPress applications.

This is the last of the podcast recorded at WordCamp, us 2024, and our focus today is the interactivity API. You may not be familiar with what this is and why it matters, so Damon and Seth will break it down, and explain how it might transform your WordPress websites in the future.

Damon starts off by defining what an interactive website is, giving examples such as single page applications, and dynamic elements like tabs and accordions. Seth adds his perspective on how interactivity aids both the end user, and website editors. Making for a more compelling user experience and efficient content creation.

We get into why WordPress needed an interactivity API, even though the platform already supports libraries, like React. The interactivity API provides a standardized way to create dynamic content, which is essential for modern web expectations.

We also highlight real-world examples, including faceted searching and filtering, which have been successfully implemented using this API.

The conversation also touches on performance improvements brought by the API, emphasizing how it can offload server resources by only updating necessary content.

Towards the end we explore how the API is being used in Gutenberg blocks, and how it supports both developers and site builders.

Damon and Seth also discussed the project’s development, encouraging more contributions and feedback from the community.

If you’re intrigued by improving your websites’ interactivity and performance, this episode is for you.

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

And so without further delay, I bring you Damon Cook and Seth Rubenstein.

I am joined on the podcast today by Damon Cook and Seth Rubenstein. Hello.

[00:03:40] Damon Cook: Hey, how’s it going?

[00:03:41] Nathan Wrigley: Yeah, really, really nice thank you. That’s Damon.

[00:03:44] Seth Rubenstein: Hello, I’m Seth.

[00:03:45] Nathan Wrigley: Thank you so much. We’re at WordCamp US, it’s happening in Oregon. It is the month of September 2024, and I’m being joined by Damon and Seth so that we can talk about the Interactivity API.

Before we get into that, I think it’s probably important to paint a picture of both of you, what your background is with WordPress technology, et cetera. So we’ll just keep this very brief. Let’s go for Damon first. Damon, just tell us a little bit about you, your potted bio, if you like.

[00:04:10] Damon Cook: Sure, yeah. Well, I started out as a WordPress front end developer at WordPress. There’s several different WordPress focused agencies, and now I’m a developer advocate with WP Engine.

[00:04:21] Nathan Wrigley: Thank you very much. And Seth?

[00:04:23] Seth Rubenstein: My first time using WordPress was in college. I converted all of our websites to WordPress multi-site, as like the assistant web developer. And from there I just kept going, and that was just my career track from then on, just WordPress all the time. And now I am the lead engineer at the Pew Research Center, where we have a WordPress platform that we’ve made ourselves, and we work on a lot of interactive WordPress applications.

[00:04:43] Nathan Wrigley: Just staying on your bios just for a moment, what does the Pew Research Center do? I’ve not heard of them before.

[00:04:49] Seth Rubenstein: We are a non-partisan, non advocacy social science research organisation. So we basically study the American public and where they are, what they think on certain issues. And we do a lot of public polling and things like that, and we report that back. So we’re kind of like a nonprofit news organisation.

[00:05:04] Nathan Wrigley: Gosh, okay thank you. That’s really interesting.

Okay, let’s open it up and talk about the subject at hand today. So we’ve got both of these gentlemen here to talk about the Interactivity API. I think probably we should first deal with the topic of, what is an interactive website?

Probably, dear listener, if you’re listening to this, you might know this already, but I have an intuition that some people won’t. So, what are the benefits of having an interactive website? And whoever wants to answer that, pick up the mic and go for it.

[00:05:30] Damon Cook: I think the classic example is that of a single page application. So the idea of being able to navigate from page to page, or section to section even, and just have things that seem seamless, so the page isn’t refreshing, that is a pretty common scenario. But there’s also lots of other interactive pieces like tabs, accordions, all that stuff gets really helpful when you reach for the Interactivity API in creating stuff like that.

[00:05:59] Seth Rubenstein: I don’t have anything to add to that. I guess what I would say is, on the other side of it besides the front end user, the kind of, your visitor, I think the interactivity part of a website kind of also can help out your editors, and how they’re building content, and making more engaging content.

I think this will be interesting because I think, you know, Damon might have a kind of perspective of the front end user, and I’m definitely coming from a perspective of, how can I scale up my editorial team’s ability to create interactive content? And not so much like what it looks like on the front end.

[00:06:27] Nathan Wrigley: So there’s an interesting distinction there. So, does the work that you are doing touch on both the front end and the back end? So it’s not just for the forward facing, user facing part of a WordPress website. This is things that you can do in the back end, the admin side of things too.

[00:06:40] Seth Rubenstein: Yeah, it’s how editors create interactive bits of content, and how those interactive bits of content might interact with each other. Because I think right now, without the Interactivity API, that kind of content is static and siloed on the page.

[00:06:52] Nathan Wrigley: We will link in the show notes to all of the different places, and no doubt one of the first links will be to the project itself, the Interactivity, API. But I guess I have to ask the question, why is this even a project in WordPress? Is it that WordPress historically wasn’t particularly adapted towards interactive content?

I mean, we know how to publish posts and pages, and once you’ve done that, that’s kind of it. You’ve done it, and there’s no interactivity there. Is this something that has been, I don’t know, more recently thought was necessary? Is this something that you think should be in Core? Let’s just take that. Has WordPress been bad at interactivity historically?

[00:07:28] Damon Cook: I don’t think that it’s been bad historically, I think that it’s more of kind of a, I guess a technology trend of leaning into libraries like React or Preact, which Interactivity is built upon. So I think it’s more of a trend, but also, yeah, a necessity in Core, because folks are trying to build these types of experiences, and we want to have a standardised way for them to be able to do that, and not have to pull in a bunch of different libraries. And although they still can, you know, there’s a standardised and backwards compatible way for them to do it. So that’s the idea.

[00:08:05] Nathan Wrigley: Thank you. Seth, anything to add?

[00:08:06] Seth Rubenstein: Yeah. I don’t think WordPress has done a bad job on interactivity in the past, you know, ships with jQuery, ships with React, that’s all available to you. I think the Interactivity API is kind of looking at how developers have been creating front end experience with React, and narrowing that down to be like the right tool set for blocks and for block developers specifically.

[00:08:26] Nathan Wrigley: So it’s about having the right tooling. Something standardised that everybody can get their teeth into, that every developer understands.

[00:08:32] Seth Rubenstein: Yeah, and something that fits the blocks kind of model I think, a little bit better than some of these other frameworks.

[00:08:38] Nathan Wrigley: Okay, that’s great. So give us some examples of good interactivity on the internet. So we could limit ourselves to WordPress, but let’s not do that. Let’s just go out there and try to pick good examples.

Really, I guess we could be talking about Google Docs, we could be talking about websites, we could be talking about anything. Do you want to just rattle off a few things where you’ve seen and you’ve been impressed, and thought, ah okay, there’s a good example. The only reason I’m asking this really is so that the listener can just get an idea of what interactivity means.

[00:09:05] Damon Cook: Sure. And I’m actually going to set up Seth, because I think a lot of the things that his organisation is creating are representative of what folks kind of need. So I’ll set him up for that.

[00:09:17] Seth Rubenstein: And I’ll say the word that he’s probably thinking of, facets. Amazon, you’re browsing Amazon, you want to narrow down the content that you’re looking at. Those facets on the left hand side, filters, aggregations, whatever you want to call them. I think this has probably been our biggest success with the Interactivity API, is developing out facet blocks.

And with the Interactivity API what that would let you do is just server side hydrate data before it gets back to the client. And you can browse through all this content, and do it in a performant way that you just couldn’t do before. Or you could, but it would take a lot of work on your part to build out the framework and the technology to handle all that.

And so now that’s just in the box in WordPress free to use. So we can probably touch on facets a little bit more later, but I think that’s probably the best use case for the Interactivity API thus far.

[00:10:00] Nathan Wrigley: Let’s dig into that a little bit. So when you say facets, my head is immediately going to things like, I don’t know, the posts and pages, table layout, or something like that. And the fact that, if I want to get to post number 11, I might have to click a button, wait for a moment whilst the page refreshes, there’s obviously something going on there, page refresh, I’m contacting the server and what have you. Is the idea here that, a bit like, I don’t know, if I scroll on Google, I would be able to automatically upload more pages, more posts, that kind of thing? And then be able to, I don’t know, say filter them, show me only the ones that are authored by me, or ones with featured images, and that would all happen on the fly.

[00:10:35] Seth Rubenstein: Yeah. So, you know, you can filter by author, by taxonomies, category, custom taxonomies, whatever, date, et cetera. And those results just update in real time, without you having to refresh the page.

You can paginate through those results without having to refresh the page. That, of course, is great for the end user, but it’s also great on the backend because you’re saving server resources without having to re-render that entire page every single time. So you’re only rendering out what’s changed.

So in that way, great for the end user and great for you as a website operator, because the Interactivity API kind of offloads some of that performance overhead that way.

[00:11:07] Nathan Wrigley: Yeah, okay. I have children, and they have been born in a world where the mobile phone is completely ubiquitous. And the idea of anything refreshing to them just seems like an anathema, just a pointless thing. You know, you want to open an app, and from that moment just everything happens. You scroll, there’s more to see, you press back, it just immediately loads and what have you.

Is that kind of where we’re going with the internet? And what I mean by that is, sites where you’ve got to click a button to see another further piece of content, or for your shopping cart to be updated, or whatever it may be, that just seems like the 1990s almost.

Is it a bit of that? Is it just we’re kind of keeping up with the times? And the expectation from the next generation of users is going to be, well, if it isn’t interactive, I’m not sticking around. So if I’ve got a, I don’t know, a WooCommerce store or something like that, it’s going to be painful for a user to have to refresh, click a button to go to a cart, wait for it to load and all that. It’s just, like I said, the 1990s.

[00:12:05] Damon Cook: Yeah, I think a lot of it does touch on that and, yeah, just reaching out to that kind of experience. But, yeah, I think Seth touched on this, but the performance impact is pretty great about the Interactivity API because you’re only updating the sections, or components on the page that are really relevant to what the user is doing. So that has a performance impact. It makes things feel seamless, faster, and I think that’s a lot of probably what we’re all looking for at the end of the day.

[00:12:30] Nathan Wrigley: It feels like something more native to the device that you are on. So it feels like a Mac app, or a Windows app, or an Android, or an iPhone app. Does that kind of make sense? It just feels like we’re in the modern world, not in the old world where any kind of refresh just seems bizarre, frankly. Anything to add, Seth?

[00:12:46] Seth Rubenstein: You know, I think the coolest part about this is it basically lets you take a PHP application and turn it into a single page JavaScript app. I mean, that’s really what the Interactivity API as a whole is doing. And I think that’s what developers are looking for these days. Look at, you know, Next.js, and frameworks like that that are really grown and are really popular. And I think that this kind of API just is an answer to those for WordPress developers.

[00:13:06] Nathan Wrigley: So if I were a developer and I was, I don’t know, creating plugins, themes, blocks, whatever it may be, where do I go and find out about this? How do I get my teeth into the project? So you might want to drop a URL at this point, wherever you want to point us.

[00:13:20] Damon Cook: Sure. Well, I can tell you how I find it because I Google it. I Google it myself. Interactivity API Handbook, I’m pretty sure that’s where you’ll find it, and developer.wordpress.org. The documentation is very thorough, and up to date, and complete. And I think that’s what’s excites me about this API because it’s a very discreet project that kind of got pulled together and, yeah, the documentation is really up to date and great, so that’s where I’d go.

[00:13:47] Nathan Wrigley: Okay, I will link to that in the show notes. And probably a good idea, dear listener, to pause at this point, go and check that out and then come back and hit play.

So from the developer sort of point of view, how baked is it? How complete is it? Is there a lot that you have achieved already? Is there a big roadmap for things that you want to achieve?

I know that’s going to be difficult to encapsulate in a few sentences, but just tell us the state of the project now for developers listening to this, they might have some intuitions as, okay, that sounds like something I could use right now, as opposed to the roadmap features that are still going to come.

[00:14:17] Damon Cook: Sure. No, it is quite complete and ready to use, and the documentation can even step you through how to integrate it into an existing block. You can even spin up a new block with the Interactivity API already baked in.

Some of the future roadmap areas is, I know that we’re still working on like client side navigation, and then pulling in kind of different modules. Like I know one experiment that’s being explored is, there’s a package for accessibility. So just the general idea of speaking, screen reader, passing along. So these APIs have been in WordPress for a while, like some of the accessibility packages. So there’s explorations in kind of porting that over, and pulling it in, because the Interactivity APIs uses JavaScript modules for a lot of this. So it’s kind of re jigging, I guess, some of the code and pulling in some of these packages so that developers can use kind of those old, not old, but accessibility features, and have all that compatibility baked in.

So that’s some of the areas that are still getting integrated, and I’m excited for them. And I think that’s on the roadmap right now, and there’s folks contributing towards it.

[00:15:24] Seth Rubenstein: The modules area is probably, I think probably the area that it needs the most work, and hopefully the most amount of work is going into. I would say that’s probably one of the roughest parts of the Interactivity API right now is, if you need to use an external script, or kind of library, or framework, it’s a little difficult to get that in. So I think that’s probably where the most amount of work’s going to be going.

And I think there’s some work going on WordPress URL, bringing that in as well. And there’s a few more directives too, to the API, that are being added like wp-show which should be interesting, that should let you dynamically hydrate elements on the page in a different way. I won’t go to like all the technical details on that, but there are some additional features that are coming to the Interactivity API, beyond just the module stuff. So there are, in the Interactivity API parlance, there are new directives coming soon.

[00:16:05] Nathan Wrigley: I think for anybody who is a developer, you’re going to be fine looking at the documentation. But if I say any acronym on this podcast, I always get some pushback from people who are not developers, WordPress end users. So let’s address that.

Is there going to be functionality within the Interactivity API, although it’s there, and it is part of the Interactivity API, will be available to just builders of websites? People who have their own blog, or their own property, they’re not interested in WordPress from a technical point of view. Is there anything that they can do with it so that they can have this sort of dynamic content? Or is it mainly going to be through the work that developers do, through plugins, and blocks, and what have you?

[00:16:44] Seth Rubenstein: Right now. It’s live, already on your site if you’re running kind of the latest version of WordPress. The light box in the image block is using the Interactivity API. So site builders are already gaining that Core query, already has interactivity built in. So does the pagination block. So your publication pages can already be kind of a single page JavaScript app. So Core is adding that stuff in and, yeah, obviously plugin developers will also hopefully add interactivity to their plugins, but it’s already there for site builders.

[00:17:11] Nathan Wrigley: It feels like we’ve gone down the road in WordPress where everybody’s done their own thing with interactivity. The page builders have done, well, not just the page builders as one block, but each page builder has done a different thing. You’ve got these multitude of plugins that do the sort of facet searching and all of that kind of thing.

The idea that there’s just going to be this one thing, I suppose in a sense you kind of want the Interactivity API to not really be that well known about. The idea is for it to sort of fade into the background and nobody even realise that there’s a thing. Is that sort of doing down the project a little bit, or is that kind of the point? If nobody knows it exists, but it works, that’s kind of the ideal.

[00:17:45] Damon Cook: Yeah, I mean these APIs are in the background, yeah, for developers to explore, and use, and pull in, and integrate. But yeah, at the end of the day, the end user shouldn’t know about it, have to know about any of this, and just, have a great experience. So yeah, I think that’s the idea.

[00:18:00] Nathan Wrigley: Where do you learn what you should be working on? So the team of volunteers and seconded people that are working on the Interactivity API, who are you listening to? Where do you get your feedback from? And I know in the open source world, it’s hard to get that feedback. And you might be just listening to a dozen voices, interested people, or there may be, I don’t know, hundreds of people talking to you. But to drive it forward, who are you listening to? Where do you get your intuitions as to what should be on the roadmap?

[00:18:25] Damon Cook: There is a Make Slack Group, it’s Interactivity API I believe, or Core Interactivity API room. But there’s some great contributors in there, and I’m probably going to mess up all their names but there’s Jon Surrell, I believe, and Greg Ziółkowski. I apologise Greg, I tried. But they are very active contributors and I probably feel like the least contributor. But, yeah, they’ve been doing a great job.

I think what it comes down to historically, the Frontity team, I’m not sure if you’re familiar with that project, but back in the day they kind of got integrated. All these smart folks into Automattic as full-time contributors, and a lot of them have been driving this project daily and contributing towards it, and they’ve been doing an amazing job. Some other folks, I think from Google, also contribute a lot towards Interactivity API. So that’s what I follow, they’re all in that room a lot and very active.

[00:19:20] Seth Rubenstein: That’s almost everybody. I don’t know if you mentioned Luis, he’s kind of my main point of contact. I ping him with questions, or ideas or, hey, we’re going to try to do this, does this sound crazy to do with the Interactivity API? And he’s pretty receptive.

[00:19:32] Nathan Wrigley: Would it be fair to say that you could do with some more helpers though? I think in the open source world we could always use some more people flocking around any particular given project. Is that something that you’d be interested in? I don’t know, one of the intentions of a podcast like this is to make things like that happen but, yeah, is that a thing?

[00:19:47] Seth Rubenstein: I would like to see a lot more people using an API. You know, we’re trying to push the limits of the API, and I think it’s important that we all kind of try to push the limits and see where it needs additional work, or where we might need extra functionality. So I’d love to see a lot more people using it because I just don’t think it’s gotten kind of the critical mass yet.

[00:20:04] Nathan Wrigley: Can you give us some nice examples that I could link to in the show notes of situations where you’ve seen, specifically the Interactivity API. We mentioned earlier about, you know, general websites and what have you.

Are there any good examples where you’ve seen somebody using it, so that if there is a developer looking at this, they can go, oh okay, that’s the kind of thing we’re talking about.

[00:20:21] Damon Cook: I certainly can share some links. I have some repos on GitHub where I’ve built custom blocks and I’ve done, I believe there’s a YouTube, at least a recording of a presentation where I’ve gone step through building, some of these custom blocks and they’re all in my repo.

I was going to hand it off to Seth, I guess again, because I know one block that stood out to me that him and his team have created is like a, well, I think you have a poll, but also like a table filtering. I mean, I think those are pretty common experiences that we see on sites, and they’ve done a great job in creating that seamless experience of filtering.

[00:20:56] Seth Rubenstein: I can just gush for a moment. If you want a good example, www.pewresearch.org, almost everything that you’re going to see there is using the Interactivity API. Mega Menus, MailChimp newsletter signups, facets, pagination, table of contents. That updates as you scroll through the page, because the chapter blocks report using the Interactivity API to the table of contents block, which is separate, their position. Data tables, charts, quizzes, you name it, pretty much everything that we have on our website is using the Interactivity API at this point.

There’s a few plugins that we still have to convert, it’s actually only two. But almost everything that you see there is using the API, and almost all that code is available for free open source on github.com/pewresearch.

[00:21:39] Nathan Wrigley: Did you do that yourself because you are knee deep in the weeds of this, and so you could understand easily how to do that? Or would it be true to say that the developer documents that you’ve just mentioned would steer any, air quotes, competent developer to be able to achieve that? Or is it just that you know, you’ve got the Interactivity API, you also work for this organisation, so the two met.

[00:21:58] Seth Rubenstein: I think it’s because we wanted to provide learning resources, we wanted to provide a use case of, here’s what is possible. Obviously I’m talking about a lot of blocks that are interactive, but one of the things that I could really go into is our concept around the Interactivity API.

I think a lot of examples that people can point to, it’s a very specific use case. This block is a collapsible block, you click on it and it expands. We’ve taken a different approach, something that we call Atomic Interactive Blocks. And so we’ll make a block and it will have some interactivity instructions and functionality, but the point of that is to be dropped into another block, which has its own interactivity, and instructions, and functionality, and so on and so forth.

And so what we’ve really done is made a library of interactive blocks that kind of act like React components, and that you can drop them in other use cases and style them however you want, but what they do is defined maybe higher up.

Yeah, so I think to me that’s really the power of the Interactivity API, because what that allows us to do is, as developers, is just maintain a small library of blocks that are programmed to do a lot of things, and interact with a lot of other blocks, but then hand off styling, and content, and all that stuff to designers and other people.

For me, that’s been the coolest part about the Interactivity API, is this abstraction out of a block of what it does. We can go into it more, but the interactive stores can communicate with one another, and so you can have block A do a very specific thing, you click on it and it opens. And maybe you put that inside of block B, and block B is aware, well, when block A is set to be open, when its state is set to be open, I need to do this. And so, you know, you can imagine, you can make a button block, and use that in infinite applications.

The way that we approach it though, that block can dynamically target an interactive store rather than statically being set to just do this one thing in this one interactive store. So all of those GitHub repos will provide examples of how that kind of system works, and how you might approach the same thing for your organisation or website.

[00:23:48] Damon Cook: I think what Seth touched upon is interesting because I think it says a lot kind of to how the API has been built to abstract some of these ideas, and just shared state between components. So like you touched on, a button can be shared, and so many are used in so many contexts, but to be able to abstract that and share state, and the interactivity between these components is, it shows a lot of, the API has been built smartly so that it can be explored and experimented with, which is neat.

[00:24:19] Nathan Wrigley: I think one thing about this topic is that it is possible, probably, to go a bit overboard with being interactive. I’ve got the API, I know how to use it now, I’m going to make everything interactive. And I guess there’s a point where you’ve got to tell yourself, slow down, not everything needs to be interactive. So let’s just go into that. Are there any uses which you would say, yeah, you could do that interactively but we probably shouldn’t? Are there any times where you think, let’s put the brakes on?

[00:24:45] Damon Cook: I mean, I think any developer will kind of realise when they’ve maybe over-engineered something. There’s always going too far and making everything, yeah. You’ll know I think if you’re trying to make everything interactive, every paragraph or, you know, it’s just kind of pointless. But the exciting part is that you can experiment and explore, interact with these APIs and see what you can do. And find the edges of what you can do, and what you should do, or shouldn’t do, that’s the fun part.

[00:25:10] Seth Rubenstein: Yeah, I will say that, is it possible that you can do too much? For sure. Technically speaking though, is it possible that you can do too much? I don’t think so. Like I said, we have a lot of interactivity blocks on a page, and the performance has been great. So I don’t think there should be a concern of like, oh, I’m overdoing it with using the Interactivity API in terms of performance. I think the more things you make with the Interactivity API, the better performance you’re going to get.

[00:25:33] Nathan Wrigley: Let’s just speak to the performance side of things because you mentioned technically how it’s achieved a little bit, but could we just develop that a little bit? And you’ve definitely said performance isn’t affected, or performance is really great a number of times. What does that actually mean? So if I’m using this, is it a more performant website because it’s, I don’t know, it’s loading content asynchronously or what have you?

Has there been any situations where you’ve had to, I don’t know, refactor things because the performance took a dip. Performance at the moment is everybody’s big worry, isn’t it? Because, you know, Google takes those metrics and ranks you accordingly. So we kind of want to know that if we make this thing interactive, it’s not going to suddenly impact our score. And I know that Google does take note of these kind of things.

[00:26:11] Seth Rubenstein: Yeah, I think on the performance bit, I mean, to get a little technical, what makes it so performant is kind of that idea of server side hydration, right? You click on something and that element changes, and that can happen client side, but if it needs a new data, that in the past has meant refreshing the page or doing something really kind of complex and technical.

Now when the data changes and when that element needs to change, that one element re renders on the server, and then it’s returned back to the client, not the whole page. So that right there is an immediate performance savings because you’re not having to render a whole page out again, just to get this one little bit of changed information on a page.

[00:26:45] Nathan Wrigley: Let’s get into probably the final thing for today, and that is the accessibility perspective of things. It’s become the watch word I think of 2023, 2024, and probably it’ll carry on, rightly so.

Has there been any accessibility concerns? Because obviously if you’re updating content live on the page, is there anything that we need to be concerned about if we’re developing with the Interactivity API in terms of the accessibility, I don’t know, screen readers or other assistive technologies.

[00:27:12] Damon Cook: Sure, yeah. I think it’s always a challenge in building your components, and making sure they’re interactive. So I think that it’s really kind of just abstracting things, trying to figure out what your HTML is, what your CSS is, and then layering on the Interactivity API. I know that some of the extensions of pulling in like strings of information that are being updated on the page, like some of the older packages, like the accessibility, or a11y, for the acronym. Some of these packages that have been in Core for a while, they’re being ported over into the Interactivity API.

That’s something that’s kind of on the roadmap and being explored right now, so that we can have some of these screen reader updates for components, and on the page be integrated with the Interactivity API. So that’s, yeah, definitely something that’s being explored.

But also, yeah, a lot of it is more of just the approach because just the markup and the CSS alone, having the knowledge of how to make that accessible is always a practice, an art form, and something that is always, can be improved.

[00:28:17] Nathan Wrigley: Okay, thank you. Anything, Seth?

[00:28:19] Seth Rubenstein: I think that there’s actually probably better accessibility that you’re going to get out of the Interactivity API. You know, I know that screen readers and assistive technologies have come a long way, but if a lot of your website relied on React, and other JavaScript frameworks that render after the page has been rendered, that could pose a problem for accessibility technologies. Here, all that stuff is pre-hydrated and pre-rendered before the page even loads. So your markup’s ready to go as soon as the page loads, which is actually great.

[00:28:46] Nathan Wrigley: I think probably time has caught up with us. But before we go, we did mention the URLs and where you can find the project. Let’s just, firstly, go through where we can find you individually. So that might be an email, a Twitter handle, or whatever it might be. So let’s go to Damon first. Where can people find you if they’re interested in catching up?

[00:29:03] Damon Cook: I think probably the easiest is X, I still call it Twitter. I am dcook. I’m always open. Yeah, reach out. I think 99% of my Twitter timeline is sharing WordPress ideas, outreach links. So yeah, you’ll find me for any WordPress stuff there.

[00:29:21] Nathan Wrigley: Thank you so much. And, Seth?

[00:29:22] Seth Rubenstein: You can also find me on Twitter, which I refuse to call X. Twitter.com/sethrubenstein. And I also share a bunch of Interactivity API and WordPress stuff.

[00:29:29] Nathan Wrigley: Thank you. So this is the bit where I ask, is there anything that we missed? Is there something that you desperately wanted to get across that I failed to ask?

[00:29:36] Damon Cook: To go back just a little bit, he was touching on performance. So one thing actually I wanted to speak to was the idea of the Interactivity API is a standard means for developers to pull in these kind of libraries and do interactivity experiences. And so using this API, you’re relying on, you know, a simple small bit of source code that is going to be integrated on every page. So that performance impact of not having to pull in an entire library, so it makes it a smaller source code that’s being pulled in, so that has a huge performance impact as well.

On the podcast today we have Damon Cook and Seth Rubenstein.

This is the last of the podcasts recorded at WordCamp US 2024, and our focus today is the Interactivity API. You may not be familiar with what this is and why it matters, so Damon and Seth will break it down, and explain how it might transform your WordPress websites in the future.

Damon starts off by defining what an interactive website is, giving examples such as single-page applications and dynamic elements like tabs and accordions. Seth adds his perspective on how interactivity aids both the end-user and website editors, making for a more compelling user experience and efficient content creation.

We get into why WordPress needed an Interactivity API, even though the platform already supports libraries like React. The Interactivity API provides a standardised way to create dynamic content, which is essential for modern web expectations.

We also highlight real-world examples, including faceted searching and filtering, which have been successfully implemented using this API. The conversation also touches on performance improvements brought by the API, emphasising how it can offload server resources by only updating necessary content.

Towards the end, we explore how the API is already being used in Gutenberg blocks and how it supports both developers and site builders. Damon and Seth also discuss the project’s development, encouraging more contributions and feedback from the community.

If you’re intrigued by improving your WordPress site’s interactivity and performance, this episode is for you.

Useful links

Pew Research Center

Interactivity API Handbook

WordPress Developer Resources

Frontity

Pew Research Center on GitHub

Damon’s X

Seth’s X

by Nathan Wrigley at November 06, 2024 03:00 PM under podcast

Do The Woo Community: The Future of Distributed Social Media on WordPress with Robert Windisch and Matthias Pfefferle

In this episode, Abha discusses WordPress's potential evolution into a distributed social media platform with Matthias and Robert, emphasizing community engagement and new tools.

by BobWP at November 06, 2024 10:23 AM under social media

WPTavern: WordCamp Asia and WordCamp Europe Added to Kim Parsell Memorial Scholarship Program

As announced at the 2024 WordPress Foundation Meeting, the Kim Parsell Memorial Scholarship has been expanded to include WordCamp Europe and WordCamp Asia. Traditionally supporting a woman WordPress contributor to attend WordCamp US, the scholarship now assists women facing financial challenges in attending these three flagship WordCamp events.

The scholarship honors Kim Parsell, a cherished member of the WordPress community and regarded as one of the first “women of WordPress”. Known fondly as #wpmom, Kim was a dedicated volunteer who devoted countless hours to the WordPress project and was a strong advocate for women entering the tech industry.

In 2014, Kim received a travel stipend from the WordPress Foundation, allowing her to attend the WordPress Community Summit held alongside WordCamp San Francisco—a transformative experience she cherished.The WordPress Foundation now offers this scholarship in her memory.

The announcement post states: “ This expansion honors Kim’s legacy and her dedication to inclusivity and diversity within the WordPress community, making it possible for more community members to attend these inspiring events.”

To qualify, applicants must:

  • Identify as a woman
  • Actively contribute to the WordPress project
  • Have never attended WordCamp Asia or WordCamp Europe before
  • Require financial assistance to attend WordCamp Asia or WordCamp Europe 2025

Applications are open until November 30, 2024, for both WordCamp Asia and WordCamp Europe, with notifications sent by December 21, 2024. Applications for WordCamp US will open in the coming months. The scholarship covers travel to the host city, hotel accommodation for the event duration, and a WordCamp ticket. It does not include airport transfers, meals, or other incidental expenses.

The scholarship’s inaugural recipient in 2015 was Anyssa Ferreira, a Brazilian designer, feminist, and WordPress community activist. Last year, it was awarded to Cynthia Norman, a WordPress developer and Web designer, with a background in training and education.

by Jyolsna at November 06, 2024 04:48 AM under Kim Parsell Memorial Scholarship

November 05, 2024

Matt: I Voted!

It was a huge pain in the butt, because my mail-in ballot didn’t register properly, but I found a last-minute flight to Houston and this morning walked over to Congregation Emanu El and voted. It is our most sacred duty as a citizen. I encourage every American to vote.

by Matt at November 05, 2024 11:04 PM under Asides

WordPress.org blog: WordPress 6.7 Release Candidate 3

The third release candidate (RC3) for WordPress 6.7 is ready for download and testing!

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

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

You can test WordPress 6.7 RC3 in four ways:

PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).
Direct DownloadDownload the RC3 version (zip) and install it on a WordPress website.
Command LineUse the following WP-CLI command:
wp core update --version=6.7-RC3
WordPress PlaygroundUse the 6.7 RC3 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup.
You can test the RC3 version in four ways.

The current target for the WordPress 6.7 release is November 12, 2024. Get an overview of the 6.7 release cycle, and check the Make WordPress Core blog for 6.7-related posts in the coming weeks for further details.

What’s in WordPress 6.7 RC3?

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

How you can contribute

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

Get involved in testing

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

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

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

Search for vulnerabilities

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

Update your theme or plugin

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

Thanks for continuing to test your themes and plugins with the WordPress 6.7 beta releases. With RC3, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.7.

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

Help translate WordPress

Do you speak a language other than English? ¿Español? Français? Русский? 日本? हिन्दी? বাংলা? You can help translate WordPress into more than 100 languages.

Release the haiku

RC3 arrives,
Final polish, last bugs fall,
Six point seven calls.

Thank you to the following contributors for collaborating on this post: @peterwilsoncc, @joedolson, @sabernhardt.

by David Baumwald at November 05, 2024 05:02 PM under releases

Do The Woo Community: Do the Woo WooSesh Recap, Day 2, with Robbie, Marcus and Brian

The episode covers insights from WooSesh on motion design, e-commerce localization, accessibility, payment security, customer success, and lifetime licenses in plugin development, emphasizing enhancing user experience and trust.

by BobWP at November 05, 2024 10:20 AM under Podcast

November 04, 2024

WordPress Foundation: Kim Parsell Memorial Scholarship Expands to WordCamp Asia and WordCamp Europe!

We are thrilled to announce that following the latest WordPress Foundation Board meeting, the Kim Parsell Memorial Scholarship will now be available for WordCamp Asia and WordCamp Europe, in addition to WordCamp US. This expansion honors Kim’s legacy and her dedication to inclusivity and diversity within the WordPress community, making it possible for more community members to attend these inspiring events.

The scholarship is designed to support those who are passionate about contributing to WordPress, especially individuals who might otherwise face financial barriers to attending. By extending the scholarship to WordCamp Asia and WordCamp Europe, we aim to further empower community members around the globe to engage with and grow the WordPress community.

Scholarship Requirements and Application

The requirements for applying and the application forms for WordCamp Asia and WordCamp Europe are available below.

Eligibility Information

There is one scholarship position available to each flagship event (WordCamp Asia, Europe and WordCamp US). To be considered, applicants must meet the following criteria: 

  • Is a woman
  • Is an active contributor to the WordPress project
  • Has never attended WordCamp Asia/Europe before
  • Requires financial assistance to attend WordCamp Asia/Europe 2025

If you meet the above requirements and would like to be considered, please apply as soon as possible. Applications will be accepted until the closing date of 30 November 2024 for both WordCamp Asia and WordCamp Europe. 

All applicants will receive notification by December 21, 2024.

For more information, please visit the WordPress Foundation’s page about the Kim Parsell Memorial Scholarship.

Stay tuned, as applications for the Kim Parsell Memorial Scholarship for WordCamp US will open in the coming months!

We look forward to welcoming more of you to these incredible WordPress events and celebrating Kim’s legacy together.

by Isotta Peira at November 04, 2024 04:43 PM under Announcements

Do The Woo Community: Do the Woo WooSesh Recap, Day 1, with Courtney, Jonathan and Brian

In this episode, hosts recap WooSesh day one, focusing on WooCommerce's rebranding, UI enhancements, community engagement, and enterprise scalability.

by BobWP at November 04, 2024 01:40 PM under Podcast

Do The Woo Community: WooCommerce Developers, Keep On Top of It

Keeping on top of Woo as a developer is important. Here are the resources you'll find over at WooCommerce and here on Do the Woo.

by BobWP at November 04, 2024 09:45 AM

WPTavern: WordCamp Europe Seeks New Host City for 2026

WordCamp Europe is now seeking a host city for its 2026 event. Teams with experience organizing one or more WordCamps in a European city are encouraged to apply. Although hosting the world’s largest WordPress event may seem challenging, applicants will have the support of an experienced core organizing team. The organizing team will work collaboratively for around nine months before the event to ensure all preparations run smoothly.

Applications are open until Friday, 15 November 2024. The final decision on the 2026 host city is expected by Friday, 29 November 2024. Applicants should consider an appropriate venue that can accommodate 1,500 seats in a main auditorium-style layout, with additional spaces for breakout tracks and workshops, as well as around 15 rooms for support functions.

The Host City Selection Committee is committed to fairness, providing equal assistance to all applicants. Applications will be evaluated based on survey responses, with rankings used to determine the final selection. Preference will be given to countries that have not previously hosted WordCamp Europe, as past events have taken place in the Netherlands, Bulgaria, Spain, Austria, France, Serbia, Germany, Portugal, Greece, Italy, and Switzerland.

The team from the selected city will be invited to join the organizing team for WordCamp Europe 2025 in Basel, where they will gain valuable insights. The current organizing team will provide guidance on processes, offer ongoing support, and ensure a smooth handover for the 2026 event.

Check out the call for host cities announcement for more information.

by Jyolsna at November 04, 2024 03:47 AM under WordCamp Europe

November 03, 2024

Matt: Michael Palmisano on Collier

I’ve been obsessed with Jacob Collier since I first saw his Don’t You Worry ‘Bout A Thing cover on YouTube, and one of my favorite genres of videos is genius musicians breaking down the incredible musical stuff Jacob is doing. (He even has his own instrument now.) This reaction and breakdown from Michael Palmisano, who is an incredible musician, go through Jacob’s amazing Little Blue video is amazing.

by Matt at November 03, 2024 08:19 PM under Asides

November 02, 2024

Gutenberg Times: Inline comments, new Playground blueprints, block bindings and more — Weekend Edition 310

Howdy,

This week, I started my month-long hiatus from social media. It’s a completely arbitrary timing of my bi-annual ritual. Gutenberg Times post will be shared on LinkedIn and Mastodon, automatically posted using the built-in Jetpack feature. I’ll be back after Thanksgiving Nov 29th for a few weeks before I start my year-end vacation. You might see me posting from Core Days in Rome, Italy, though. I am excited to meet contributors there and post one or two selfies.

Speaking of Rome: it will be my first time there, and I booked a tour of Vatican City at 7am to beat the crowds. I got a few chuckles of disbelieve from hubby and other family members as I am normally not an early riser… I’ll let you know how it turns out.

Have a splendid weekend ahead!

Yours, 💕
Birgit

PS: Voting for WP Awards 2024 is now open, produced by Davinder Singh Kainth. Consider giving your vote to the “Gutenberg Times” in the blog category and to “Gutenberg Changelog” in the podcast category, please. 🤗

PPS: Reminder: November 5th at 17:00 UTC: WordPress 6.7 Highlights and Q & A with Jamie Marsland, Nick Diego and Rich Tabor Live on YouTube.

Developing Gutenberg and WordPress

Nathan Wrigley of WP Builds invited me to start a new podcast series called “At the Core” and to discuss with him what next for WordPress. The first episode arrived on people’s podcast app this week: At The Core with Birgit Pauli-Haack – Episode 1. Wrigley is a master moderator and host. It was a great pleasure being on this show with him. We discussed a heap of information: about WordPress 6.7, WordPress Playground, Gutenberg experiments, and the 2025 default theme. And a lot more. Listen in.

Collaborative Editing: Inline comments

Pooja Bhimani, developer and project manager at Mulidots, together with other core contributors released the first and experimental version for inline commenting to the block editor. Before you can explore it, you need to enable the experiment “Block comments” on the Gutenberg plugin. It will be released with Gutenberg 19.6 next week. You can already take a peak via the Gutenberg Nightly on Playground.

Once enabled, you see an new menu item on the 3-dot-menu from the block toolbar, that opens a box in the sidebar to add your comment. A new icon appears in the toolbar once a comment is associated with a block. Then you can open, edit, delete or reply to the comment or ‘resolve’ the issue. When you click on the canvas, you can view all the comments for this particular post. Using the star on top of the comment sidebar, you can pin the icon to the top of the screen for easy access. You can use comments on pages or posts or any other custom post types. Once the post is published, inline comments are disabled.

As an MVP (minimally viable product) it works very well, apart from a few tiny quirks. Make sure to share your findings on GitHub or in the #outreach channel. The team also provides a list of what’s next for the inline commenting in this GitHub tracking issue

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

On YouTube, Jamie Marsland, teaches you in WordPress Layouts! A Beginner’s Guide, how to master content widths and page widths for stunning layouts. Discover the 4 essential widths: Normal width, Wide content width, Full width and Custom width via Global Styles and learn how your various container blocks adapt to the settings.


At our friends over at WordPress.com, Tanya Thibodeau shared Five Powerful Gutenberg Blocks for Developers to Create Custom Layouts and explained how best to use the Group, Columns, Cover, Spacer and – my new favorite – the Query Loop block. Thibodeau has instructions and demos for each of them.


Justin Tadlock has updated the free X3P0: Breadcrumbs plugin with the option to remove the first breadcrumb. He also added a Markup Style option for selecting between plain HTML, Microdata, and RDFa (default) markup. Developer can also find new hooks that act as extension points.


Rob O’Rourke, principal engineer at HumanMade, introduced Lottie Lite for WordPress animations It’s a lightweight alternative to the Lottie Files plugin and is designed to offer a simpler, more efficient solution for WordPress users. O’Rourke shared in his post the genesis of the project as its key features and how they work. Check out Lottie Lite over on Human Made’s GitHub.

Theme Development for Full Site Editing and Blocks

Carolina Nymark, core contributor sponsored by Yoast, and Juanfra Aldasoro are the lead developers for this year’s WordPress default theme, Twenty-Twenty-Five. During this week’s Developer Hours they gave a behind-the-scenes insight into the making of the theme. The recording is available on WordPress TV: Developer Hours: Exploring the Twenty Twenty-Five Theme.

They also shared links to dive in:

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

Building Blocks and Tools for the Block editor.

In his tutorial, Building Custom Block Theme Templates: A Plugin Developer’s Guide, Ajay D’Souza, walks plugin developer through the process to providing templates to block themes. WordPress 6.7 will come with a new API for this use case, though. However what are plugin developers to do when they want to support older WordPress version, too? D’Souza has you covered. You learn about the nature of block theme templates and how to build a template handler, define your loading methods, and put it all together in an real-life examples.


ICYMI: The Recap: Hallway Hangout DataViews and DataForm Components is now available with the recording, a summary, details, shared resources and a transcript. Riad Benguella, André Maneiro, and I discussed with Nick Diego the evolution and future of DataViews and DataForms in WordPress. The overall focus of the demonstration was to showcase the current capabilities of DataViews and DataForm, as well as the plans for future extensibility and integration with the broader WordPress admin experience. The recording is available on YouTube


In Justin Tadlock‘s latest tutorial on the WordPress Developer blog, Getting and setting Block Binding values in the Editor, he walks you through making the data from your custom binding sources appear in the Editor and also letting users edit that data from the connected blocks.

This week in WordPress Playground

WordPress Playground is an exciting new platform that is the basis of a few features and tools around WordPress. Recently, it received a new, much more intuitive interface, that looks familiar to site editor users. You can learn more about this change from the new Make Blog of the Playground team. Running Multiple Playgrounds with WordPress Playground by Brandon Payton.

screenshot playground instance

Jonathan Bossenger, developer educator on the WordPress training team, added a blueprint to load the Create Block Theme plugin automatically to the next Playground instance. That way you can instantly start working on a new theme. Try it out.

Alex Kirk, web developer from Vienna, added a blueprint to turn Playground into a feed reader with the Friends Plugin. Using it allows you to read feeds from the web in Playground, and even via ActivityPub. Start reading (Add the Gutenberg Times via it’s feed URL https://gutenbergtimes.com/feed)

Jason Bahl, developer of WPGraphQL, didn’t wait long to add a blueprint that loads WordPress with WPGraphQL active and defaults to the WPGraphQL IDE page to allow users to test GraphQL queries and explore the GraphQL Schema.

There are a few other blueprints for Playground are waiting to be discovered in the Blueprint Gallery. You can browse the list on GitHub or on any new Playground instance.

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

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

GitHub all releases

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


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


An interior decoration of a restaurant by wooden pieces. Malappuram, Kerala, India, by Sithara Koramparambil on WordPress 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 November 02, 2024 03:00 PM under playground

WPTavern: Automattic and Matt Mullenweg Push for Dismissal of Key Claims in WP Engine Lawsuit

Automattic and Matt Mullenweg have filed a response asking the court to dismiss counts 1-6 and 9-11 of  WP Engine’s lawsuit. WP Engine had filed a motion on October 18, 2024 for a preliminary injunction in a Northern California court, seeking restored access to WordPress.org and a reversion to conditions as of September 20, 2024. 

In response, Automattic has filed three key documents: a Motion to Dismiss WP Engine’s Complaint, a Motion to Strike, and the Opposition to WP Engine’s Preliminary Injunction.

Automattic also tweeted, “Today, in order to protect the community from the threat posed by @WPEngine’s conduct, we have filed three documents with the court. These documents respond to WP Engine’s cherry-picked versions of events with critical context not found in their legal filings.”

Let’s take a look at the main points in the documents.

Motion to Dismiss WP Engine’s Complaint 

The Motion to Dismiss begins with the introduction, “Contrary to the allegations in WP Engine’s Complaint, the perpetrator responsible for the harms against the WordPress community is not Automattic or Matt Mullenweg (“Matt”). It is WP Engine itself. Despite its own (mis)conduct, WP Engine’s Complaint now asks this Court to compel Matt to provide various resources and support to private equity-backed WP Engine for free, in the absence of any contract, agreement, or promise to do so. The Complaint also seeks to restrict Matt’s ability to express openly his perspective that WP Engine’s practices negatively impact the WordPress software platform and community—a platform and community that has been his life’s work. There is no legal or factual basis for the Court to compel such access or restrict such speech.”

The motion argues that “WP Engine’s complaint is full of sound and fury, but WP Engine’s allegations ultimately signify nothing. Beneath the Complaint’s tone of indignation lies an utter absence of any factual allegations that do or could plausibly state a claim for relief. The Complaint strains mightily and misleadingly to conflate the WordPress software with Matt’s Website and with the WordPress trademarks, but it is devoid of any facts establishing that Matt has any obligation to provide the resources on the Website to WP Engine.”

It states that “WP Engine’s misleadingly curated Complaint focuses solely on the events of the last two months, but this story actually begins over two decades ago, when Matt created a new way to build websites.”

“Contrary to the allegations of the Complaint, Automattic, founded by Matt in 2005, does not own the WordPress software but rather offers three managed WordPress hosting services, WordPress.com for everyday users; Pressable, for agencies and developers; and WordPress VIP, for high-end enterprise sites including WhiteHouse.gov, NASA, Salesforce, and CNN. The WordPress ecosystem is also supported by the WordPress Foundation (“Foundation”)—a 501(c)(3) public benefit corporation dedicated to educating the public about WordPress and open source software. The role of the Foundation is charitable, educational, and scientific.”

The motion details the significant time and resources that Matt and Automattic contribute to WordPress.org. “Matt is the owner of the WordPress.org domain name. Matt created the Website to support the WordPress community and software. Over time, the content the Website provides has become more robust. It takes significant resources from Matt and others to maintain the Website. For example, Matt and other employees of Automattic contribute over 3,500 hours weekly to support and maintain the Website, including the core software and other features offered through the Website.”

The motion accuses WP Engine of leveraging WordPress resources for profit while failing to contribute meaningfully back to the community and profiting off the goodwill of the WordPress and WooCommerce trademarks. It alleges that WP Engine’s shift in practices began in 2018 when private equity firm Silver Lake took majority control, leading to intensified trademark use and an increased profit-driven focus. 

Alleging trademark violations since 2021, the motion claims that WP Engine and Silver Lake have attempted to profit from WordPress’s reputation without bearing a share of the responsibilities. Matt had requested that WP Engine either license the WordPress trademarks or dedicate eight percent of its revenue to the further development of the open source WordPress software, but WP Engine declined.

When it became abundantly clear to Matt that WP Engine had no interest in giving back, Matt was left with two choices: (i) continue to allow WP Engine to unfairly exploit the free resources of the Website, use the WordPress and WooCommerce trademarks without authorization, which would also threaten the very existence of those trademarks, and remain silent on the negative impact of its behavior or (ii) refuse to allow WP Engine to do that and demand publicly that WP Engine do more to support the community.

The motion also states, “The mere fact that WP Engine made the risky decision to base its growing business on a site to which it has no rights or guarantee of access, without making backup plans, is not enough for it to conjure a claim out of legal thin air. Similarly, WP Engine’s business decision to rely on Matt’s Website does not provide any legal or factual basis for muzzling Matt and preventing him from criticizing WP Engine for acts that he believes are damaging the WordPress community.” 

It continues, “The real unlawful activity here is WP Engine’s infringement of the WordPress and WooCommerce trademarks. This infringement was so egregious that in the days prior to filing this lawsuit, WP Engine scurried to delete various unauthorized uses of the WordPress and WooCommerce trademarks from its website—a tacit acknowledgement of their infringing nature.”

In short, WP Engine’s complaint fails to state claims concerning intentional interference with contractual relations, tortious interference with prospective economic advantage, Computer Fraud and Abuse Act violations, attempted extortion, and unfair competition under California Business and Professions Code § 17200.

Motion to Strike 

Automattic and Matt Mullenweg have moved to strike parts of WP Engine’s complaint, citing California’s anti-SLAPP law. They argue that WP Engine’s  “claims fail as a matter of law and must be struck under California’s anti-SLAPP law because they improperly seek to impose liability for commentary and debate on an issue of public interest—namely, WP Engine’s commitment (or lack thereof) to the WordPress community – without any valid basis. WP Engine’s attempt to stifle public discussion of those issues via these claims violates California law and should be stopped here.”

The motion also asserts,  “Matt was speaking and writing in his individual capacity as WordPress’s co-founder, and not as CEO of Automattic. There is no basis to impute his statements to the company. For these and other reasons, WP Engine’s ninth, tenth, and eleventh causes of action should be stricken.”

WP Engine’s defamation claims are based on statements Mullenweg made on public platforms, which his attorneys argue are protected by the First Amendment and California law. 

Mullenweg’s comments about WP Engine’s “parasitic” behavior were part of a broader conversation on the tragedy-of-the-commons theory, explaining the critical importance of meaningful, sustained contributions to the WordPress community through the Five for the Future initiative. Besides, WP Engine does not challenge any of Matt’s statements. 

WP Engine’s trade libel claim fails to plausibly allege another required element: WP Engine has not identified any specific third party who was deterred from conducting business with WP Engine as a result of Matt’s Statements. 

Opposition to WP Engine’s Preliminary Injunction

Automattic and Matt have requested the denial of WP Engine’s motion, arguing that “WP Engine conflates the open source WordPress software with a website located at wordpress.org (“Website”) that is provided by Matt. The Website is distinct from the WordPress open source software platform and both are distinct from Automattic and the WordPress Foundation, a nonprofit public benefit corporation that was organized exclusively for charitable, scientific and educational purposes, not commercial endeavors. WP Engine’s CEO Heather Brunner feigns ignorance and reliance on a false understanding that an educational foundation was responsible for the Website that provides resources for commercial endeavors.”

WP Engine has always had unrestricted access to the open-source WordPress software and plugins, which do not require login credentials. The only resources it cannot access are certain developer tools on WordPress.org, previously used to manage plugin versions. WP Engine quickly restored its lost functionality by hosting its plugins independently on its own website.

WP Engine also seeks to limit competition by asking the Court to prevent Matt from criticizing its actions and to restrict Automattic from offering promotional incentives to consumers. Automattic contends that WP Engine’s purported damages, such as customer losses, result from WP Engine’s service quality rather than any actions by the defendants.

Also “Matt does not and never has had any contracts, agreements, or obligations to provide WP Engine access to the Website. Nor did WP Engine pay any operating costs towards the Website or to access the Website for this convenience.”

After losing access, WP Engine implemented a solution restoring its workflow by linking its plugins to its own servers. This setup has been operational for over a month, making any claimed harm from access denial either nonexistent or resolved.

Since ACF plugin has over two million active installs, so any security vulnerability within ACF would threaten a substantial portion of the WordPress community, the WordPress security team forked that plugin, and named that fork SCF. The public was also notified of the developments.

“WP Engine experienced a loss of income or capital in that intervening period, these losses are the result of its decision to freeride off the Website and Matt’s extensive efforts to support and maintain the Website, all the while knowing it had no contractual agreement entitling it to the continued receipt of those resources. WP Engine gambled, for the sake of profit, on Matt’s continued maintenance and provision of the Website for free. Having lost that bet, it cannot now come to the Court complaining of the consequences.”

If an injunction is considered, the defendants argue that it should only cover access to WordPress software and plugins. WP Engine should also be required to post a bond compensating Matt for any services he might be compelled to provide, as well as Automattic for any lost revenue due to restricted competition. Maintaining WordPress.org involves annual administrative and operational costs estimated at $800,000. If WP Engine is granted ongoing access, a bond of at least $1.6 million should be posted to cover these services for the case’s expected two-year duration.

Automattic has also issued the following public statement through its blog:

“After engaging in conduct that undermines the WordPress community, WP Engine and its private equity owner, Silver Lake, have resorted to making unfounded allegations against the founder and vanguard of the open source software.”

“WordPress open source software remains freely available to all. But WP Engine is not entitled, either legally or morally, to have unfettered access to WordPress.org—a website Matt Mullenweg built for the benefit of a robust community.”

“Preserving and maintaining the resources made available on WordPress.org requires considerable effort, investment, and a shared sense of mission that the plaintiff does not embrace. WP Engine and Silver Lake should not expect to profit off the back of others without carrying some of the weight, and that is all that Matt is asking.”

The court will next hold a hearing on November 26, 2024 and WP Engine has until November 4 to respond to Automattic and Mullenweg’s filings.

by Jyolsna at November 02, 2024 03:32 AM under wp engine

Matt: Disrupt Interview

On Wednesday I had a great chat with Connie Loizos, the editor in chief of TechCrunch, you can view the video here:

Then yesterday Automattic filed its legal responses to the spurious lawfare from WP Engine, Silver Lake, and Quinn Emanuel. It’s a bit long, but if you have time give it a read, it’s the first time we’ve been able to put out our full story.

by Matt at November 02, 2024 12:12 AM under press

November 01, 2024

Matt: GPL Clarification

A quick followup on my prior conversation with Theo.

During that chat, I talked briefly about a trademark infringer that was also distributing nulled plugins. I said “Not illegal. Legal under the GPL. But they weren’t changing the names. They were selling their customers Pro Plugins with the licensing stuff nulled out.”

I want to be clear that my reference to legality and GPL was solely focused on the copying and modifying of the code. That is one of the key freedoms of open source and GPL: the right to copy and modify GPL code.

I was not speaking about their right to charge money for nulled plugins. GPLv2 prohibits that because they aren’t providing physical copies or support. This is very different from reputable web hosts, who provide hosting and support for websites and e-commerce stores.

by Matt at November 01, 2024 05:00 PM under plugins

Do The Woo Community: Friday Shares: This Week’s Must-Reads and Community Highlights, v2

The content highlights recent updates, events, and resources within the WordPress and WooCommerce communities, emphasizing community engagement and upcoming developments.

by BobWP at November 01, 2024 10:30 AM under 1

October 30, 2024

Gravatar: Introducing Native Integrations for Gravatar Mobile SDK

We’re excited to announce the release of native integrations for the Gravatar Mobile SDK, now available for both iOS and Android. These SDKs make it easier than ever to integrate Gravatar’s powerful avatar and profile management features into your mobile applications.

What’s New?

Our platform-specific SDKs leverage native UI frameworks – Compose for Android and Swift UI for iOS – to provide seamless integration with your existing mobile applications. Each SDK is carefully crafted to follow platform-specific best practices while maintaining consistent functionality across ecosystems.

One of the more exciting additions is our new native Avatar Change Flow – a complete, ready-to-use UI component that can be embedded directly into your app. This feature eliminates the need to build your own avatar management system, saving you valuable development time. Users can easily update their Gravatar image through a polished, platform-native interface that handles all the complexity of image selection, cropping, and uploading.

Key Features

Gravatar SDK in Pocket Casts
  • Ready-to-Use UI Components: Display profile views and avatars with pre-built components
  • Efficient Avatar Management: Calculate and download avatar URLs based on email addresses
  • Built-in Image Caching: Optimize performance with automatic image caching
  • Profile Integration: Fetch and display Gravatar profiles directly within your app
  • Avatar Upload Support: Enable users to update their Gravatar images from your app

Platform-Specific Benefits

Android SDK

  • Built with Kotlin and Jetpack Compose, with easy compatibility with the old view system
  • Seamless integration with modern Android development workflows
  • Android-specific optimizations for performance

iOS SDK

  • Written in Swift with native iOS UI frameworks
  • Available via CocoaPods and Swift Package Manager
  • iOS-specific extensions including UIImageView integration

Getting Started

Visit our GitHub repositories to start integrating Gravatar into your mobile apps:

For implementation guides and detailed documentation, visit our developer site.

Security and Privacy

Your users’ privacy and security are our top priority. The SDK implements secure data handling via oAuth and gives users full control over their profile visibility.

Visit our privacy pledge here.

Coming Soon

We’re actively working on expanding the SDK’s capabilities with full profile editing support. This upcoming feature will allow users to manage additional profile fields and user information directly within your app, making it even easier to provide a comprehensive Gravatar integration experience.

We’re committed to improving the developer experience and would love to hear your feedback. Try out the new SDKs and let us know what you think!

by Ronnie Burt at October 30, 2024 03:39 PM under Gravatar Integrations

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:

November 13, 2024 03:00 AM
All times are UTC.