Max Ⓦ CapitaineWP 👨‍🚀

@KatieKeithBarn2 Some people think than writing code is the core of the job, and AI is replacing it. But writing code is one small piece of a larger set of skills. Our job is far wider than that. Understanding the need, solving problems, facilitate, ensure quality...

Why do you think young people are so sceptical of AI while older people are embracing it? It’s the opposite of what normally happens with new technologies 🙃 I’m sure that the threat to their future jobs is one factor, but it feels like much more than that.

Nouvelle fonctionnalité sur Modern Fields pour très bientôt : filtrez vos publications grâce à vos meta ! Pas de bloc sur mesure, juste la boucle de requête #WordPress ;)

Essayer c’est l’adopter !

New promising experiment. Relationship Field + Query loop block variant = display selected post directly in the #WordPress block editor, live and without a single line of code. Something even ACF can't provide. The block editor API is truly a wonder for developers 🤩

Just made an first version of the relation field for my plugin @modern_fields using mostly native WordPress components. Search, filter posts, drag'n'drop to reorder… Next : creating a variant of the query loop block to display those posts.

Claudez comme jamais !

@alex_borto C’est de la dinguerie, ça m’a complètement révolutionner les choses.

Loïc a fait un boulot de dingue avec Unblock ! Lancez la démo pour voir ce qu'il y a sous le capot : demo.unblockwp.com

@alex_borto Il nous a tous eu !

Tu m'as eu mon gars, je suis devenu accro ! Prend mon argent. 😝

À surveiller, cette extension va révolutionner notre manière de créer (et prompter) des sites dans #WordPress !

🎉 WP Grid Builder turns 7! To celebrate: 50% OFF all licenses, Lifetime included. One of our biggest discounts of the year. ⏳ Ends May 24 #WordPress #Plugins 👉 wpgridbuilder.com/pricing/

@powl_d Du côté de chez moi on est plutôt entre 28-35 cts le kw/h en ce moment. Donc encore moins cher !

Cas concret : Hendaye → Paris c’est ~800km. Avec mon Taycan : ⚡️ ~24kWh/100 sur autoroute ⚡️ ~192kWh consommés ⚡️ à 0,45€/kWh = ~86€ 🛑 3 arrêts de ~20min Avec une Audi A6 diesel : ⛽️ ~8L/100 sur autoroute ⛽️ ~64L consommés ⛽️ à 2,50€/L sur autoroute = ~160€ 🛑 1 arrêt de ~5min Si j’avais une Tesla Model 3 Long Range propulsion : ⚡️ 15kWh/100 sur autoroute ⚡️ ~120kWh sur le trajet ⚡️ 54€ d’électricité 🛑 2 arrêts de ~30min Donc oui, je “perds” environ 1h sur un trajet de 7h… pour payer quasiment 2x moins cher en énergie. Et encore, le Taycan c’est probablement une des pires voitures électriques en rapport rendement / efficience / prix 😅 Tu mets une Tesla Model 3 sur le même trajet, le delta devient absurde. Et surtout : dans la vraie vie, personne n’enchaîne 7h de route sans pause. Perso j’aurais de toute façon fait : ☕️ une pause café 🍔 une vraie pause repas Donc au final ça m’ajoute surtout une petite pause en plus pour répondre aux notifications, envoyer des mails, check deux trois trucs tranquille… pas la fin du monde

@jdevalk Hope it doesn’t land in core though, or I’ll have to throw away 8 months of work. We asked this for years and it come right when I decided to make a plugin about it (@modern_fields). But objectively, it should be a core feature yes…

I tweeted "how long before we get this for custom fields too?" when Custom Post Type UI landed in Gutenberg 23.1. Here's why custom fields are the half that matters, and what they should look like when Core finally ships them. joost.blog/wordpress-cust…

@wpchannel For sure !

Sage décision selon moi !

Coup de tonnerre sur WordPress 7.0 ! La collaboration temps réelle (RTC) ne sera finalement pas de la partie pour le moment.

@alex_borto Vu 😤 j’ai le sens du timing 🤣😅

Wahou ! Regarde @Maximebj

@pootlepress @jdevalk And the UI I've made is almost the same as presented, (but it's normal because we are using native components).

@Maximebj @jdevalk What’s your plugin?

This was just merged into Gutenberg trunk, and it’s a much bigger deal than it looks 👇 WordPress is getting a native UI to create custom post types. No code. No plugins. Just: Settings → Post Types → Add That might sound small… it’s not. Custom post types go from “developer feature” → “everyday user feature” Which means: • Better structured content from day one • Easier onboarding • Less plugin dependency • A cleaner foundation for AI to understand your site And this is just the start. Post types → taxonomies → …you can probably guess what comes next You can see where this is heading… WordPress is becoming a powerful content modelling system 👀

@pootlepress @jdevalk It's @modern_fields (published the V1.0 only 2 weeks ago). It's basically an ACF but with Gutenberg controls. I've added a UI for CPT like 2 weeks ago. My sense of timing has always been spot on 😅.

@jdevalk @pootlepress Hope not too soon because I’ll throw away 6 month of work with my plugin, but yeah in definitive it would be cool to have everything in core. Oh and SVG support too, if not too much asked.

@pootlepress So... how long before we get this for custom fields too? :)

@retlehs @modern_fields @rootswp And Full Site Editing made Roots obsolete.

@Maximebj @modern_fields “No code” isn’t the vibe of our community (@rootswp)

Using ACF made sense in 2019 but it doesn't mesh with modern WordPress development. I just inherited a site that heavily uses ACF and it's a complete mess. - Use 𝚠𝚘𝚛𝚍𝚙𝚛𝚎𝚜𝚜⁠/⁠𝚋𝚞𝚒𝚕𝚍 with 𝚠𝚘𝚛𝚍𝚙𝚛𝚎𝚜𝚜⁠/⁠𝚌𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜 for modern WordPress settings (𝚋𝚞𝚒𝚕𝚍 is the successor to 𝚜𝚌𝚛𝚒𝚙𝚝𝚜, been using it all week and it's great — no more webpack) - Native blocks are more powerful with a better, modern UX. You can use dynamic server rendered blocks where it makes sense, and WordPress 7.0's PHP block registration can replace most ACF blocks - Use the Block Locking API so clients can't break the layouts you build - Use extended-cpts for CPT/taxonomy management ACF repeaters and flexible layouts aren't the way. InnerBlocks + nested native blocks do this with a better UX. Build some boilerplates using 𝚠𝚘𝚛𝚍𝚙𝚛𝚎𝚜𝚜⁠/⁠𝚌𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜 for settings pages (ACF settings pages look out of place compared to this), native blocks, etc. and let agents use them to produce better interfaces quickly I've been doing this for years on hybrid themes and haven't looked back (not using FSE, it's not the right setup for the designs I work on) "But ACF is faster" — not anymore. Agents close the gap, and reviewing their diffs helps you see what modern WP actually looks like.