Explora Artículos y Servicios para Todos

How I Built a WordPress Personality Quiz to Turn Visitors into Subscribers
General, Notas Interesantes

How I Built a WordPress Personality Quiz to Turn Visitors into Subscribers

I was looking for a fresh way to grow my email list in WordPress, and personality quizzes caught my attention right away. They’re engaging, fun to take, and feel personal to each visitor. The challenge is that many quiz tools can feel complicated or require… Read More »
The post How I Built a WordPress Personality Quiz to Turn Visitors into Subscribers first appeared on WPBeginner.

How I Built a WordPress Personality Quiz to Turn Visitors into Subscribers Leer entrada »

General, Notas Interesantes

Riad Benguella: Meet Studio Code: I redesigned my WordPress site in a 2 hours

The shoemaker’s children go barefoot or, as we say in French, Les cordonniers sont toujours les plus mal chaussés. That’s been me for years. As a developer working on WordPress, I’ve long neglected the design of my site. This ends today.

We’ve recently released a new tool called Studio Code, think of it as Claude Code but tailored for WordPress. A tool you can install by running npm -g install wp-studio and invoke using studio code locally. Or you can try directly using npx wp-studio code. I took this as an opportunity to see what it’s capable of, and oh boy! I’m mind-blown 🤯

It took me:

1 tiny prompt to pull the site locally

1 main redesign prompt and 3 or 4 follow-up prompts to get everything redesigned and sorted out.

1 last tiny prompt to push the site online

The whole process lasted about a couple of hours during the weekend, while watching yet another Sinner-Alcarazmatch on TV.

(Ok, I’m lying a bit. The push didn’t work the first time because I had discovered a bug that had since been fixed.)

There are a lot of things that made the experience so enjoyable for me. I can see myself switching how I work with WordPress sites entirely to this process:

All it took to get access to all my remote sites was to login to WP.com prompted by the tool itself.

I didn’t have to think much or configure anything. I didn’t have to install any MCP, or provide any specific instructions. It just worked.

I really enjoyed the feeling of freedom it gives you to iterate on your designs, content, and explore wild ideas. It feels like everything is possible, your ideas are the limit.

I really enjoyed the safety net of the local development. I can change anything, break whatever I want, yet it’sstill local and won’t impact my live site until I decide.

I literally just said “push my site back to riad.blog” and that was it.

Nonetheless, the tool still has some rough edges, but we’re shipping early and iterating fast. We want you to test it and please share any feedback you have with us. We have a lot of ideas and you can also bring your own, it’s all Open Source.

I forgot, what do you think about my new design? I wanted something minimal but gives you a small “hacker” feeling. Don’t be too harsh on me.

Riad Benguella: Meet Studio Code: I redesigned my WordPress site in a 2 hours Leer entrada »

Donncha: Media Picker for Immich: Self-Hosted Photos in WordPress
General, Notas Interesantes

Donncha: Media Picker for Immich: Self-Hosted Photos in WordPress

I’ve just released Media Picker for Immich on the WordPress.org plugin directory. It connects WordPress to a self-hosted Immich server so you can browse, search, and insert your photos and videos into posts without copying files around.

Immich

I run Immich at home. It’s where my photos now live. They’re organised, searchable, with facial recognition and AI search. My WordPress uploads directory is where photos used to go, and the two never talked to each other. This plugin fixes that.

How it works

Point the plugin at your Immich server and give it an API key. You can set a site-wide key or let each user configure their own to connect to their own Immich account.

If the site-wide key is blank, each user adds their own key on their profile page. All Immich API calls happen server-side.

Two ways to add media

Once configured, an Immich tab appears in two places.

The first is the Media Library grid. Switch to the Immich view and you can search, filter by person, and either Use or Copy assets into WordPress.

Use creates a virtual attachment. Nothing is copied; WordPress proxies the media from Immich on demand and caches it locally on first request. Your uploads directory stays lean.

Copy downloads the original file into wp-content/uploads/ as a normal attachment.

The same tab shows up in the “Select or Upload Media” dialog inside the post editor, so you can pull an Immich photo straight into a post without leaving the editor.

A few details worth mentioning

Videos work too. Proxied videos stream with seek support.

Lightbox. Proxied Immich images in posts open a full-resolution lightbox on click.

Local cache. Proxied media is cached to wp-content/cache/immich/ after the first fetch. Optional cleanup with a configurable lifetime.

Your server stays private. Immich only needs to be reachable from WordPress — not from the public internet. Visitors never connect to Immich directly.

When images are copied over, virtually or otherwise, you can insert them into a post like any other image, which also includes adding them to galleries in posts.

Get it

Install it from the WordPress plugin directory or search for “media picker for Immich” in the plugins page in WordPress.

Feedback and bug reports are welcome. Development is done on GitHub here.

#Immich #WordPress #WordPressplugin

Donncha: Media Picker for Immich: Self-Hosted Photos in WordPress Leer entrada »

WordPress.org blog: Celebrating Community at WordCamp Asia 2026
General, Notas Interesantes

WordPress.org blog: Celebrating Community at WordCamp Asia 2026

WordCamp Asia 2026 brought the global WordPress community to Mumbai, India, from April 9–11, gathering contributors, organizers, sponsors, speakers, and attendees at the Jio World Convention Centre for three days of learning, collaboration, and community. With 2,281 attendees, the event reflected the scale of the WordPress community and the strong turnout throughout the event.

The event unfolded across Contributor Day and two conference days, with a program that moved from technical sessions and workshops to hallway conversations, shared meals, and joyful moments of connection across the venue. From first-time attendees to longtime contributors, WordCamp Asia 2026 reflected the breadth of the WordPress ecosystem and the many ways people shaped and sustained it.

WordPress is not a company. It is a shared commitment to keeping the web open.Mary Hubbard, Executive Director, WordPress

Throughout the event, WordCamp Asia 2026 balanced formal programming with the conversations happening around it. Sessions and workshops set the pace, while morning networking, tea breaks, lunch, the family photo, the sponsor’s raffle, and the after party in Jasmine Hall helped make the event feel welcoming, social, and connected.

How WordCamp Asia 2026 Took Shape

Bringing together contribution, practical learning, and forward-looking conversation in one shared program. Across Contributor Day and the conference sessions that followed, attendees moved between hands-on work, technical talks, workshops, and broader discussions about AI, education, enterprise, community growth, and the open web.

The result was a WordCamp that felt expansive without losing its sense of connection. Different rooms with topics as themes, helping different audiences, and different forms of participation all fed into the same larger picture: a community actively building what comes next for WordPress as a feeling that something bigger was happening: not just a schedule being delivered, but a community showing up for one another and for the future of WordPress.

Contributor Day: Building WordPress Together

Contributor Day opened WordCamp Asia 2026 with one of the clearest expressions of what makes the project special: people coming together to move WordPress forward by working on it. More than 1,500 participants joined 38 table leads across more than 20 contribution tables, creating a day that was expansive in scale and grounded in real work. For some, it was a return to familiar teams and longtime collaborators. For others, it was the beginning of their contributor journey.

The day moved between structured learning and hands-on participation. Alongside contributor sessions, attendees joined workshops, visited the Open Source Library, took part in YouthCamp, and attended The Making of a WordPress Release: Conversations with Past Release Squad Members, a featured panel that added depth and perspective to the work of building and sustaining WordPress.

What made Contributor Day stand out was not only the number of people in the room, but the range of ways they could take part. Workshops created space for skill-building. YouthCamp brought younger participants into the experience and widened the event’s reach in a meaningful way. The day felt welcoming, energetic, and full of possibility.

By the end, the impact was already visible across teams. Polyglots contributors suggested more than 7,000 strings and reviewed 3,200 of them. Photo contributors uploaded 76 images. The Test team worked on more than 20 tickets, and 55 contributors joined Training. Those numbers told only part of the story, but they pointed to what Contributor Day continued to do so well: turn a large gathering into shared work that strengthened the project in real time.

Conference Sessions Take Shape

Across the conference days, WordCamp Asia 2026 covered a wide range of topics, from technical development and hands-on workshops to business strategy and the open web. Sessions took place across the Foundation, Growth, and Enterprise tracks, with workshops running alongside the main program.

One of the opening sessions was James LePage’s WordPress and AI, which introduced a theme that appeared throughout the conference: how WordPress is responding to changes in AI, publishing, and developer workflows. That topic continued in later sessions focused on AI-driven development, autonomous testing, plugin maintenance, and automation.

Later that morning, a fireside chat with Mary Hubbard and Shilpa Shah shifted the focus toward trust, security, and the longer-term questions shaping open source publishing. Coming early in the program, the conversation gave the conference an important center of gravity, pairing technical change with questions of stewardship, resilience, and what people needed from WordPress as the web continued to evolve. Rather than pulling away from the event’s technical momentum, it deepened it, bringing a human perspective to the pace of change and reminding the audience that progress in open source is not only about what gets built, but about how communities guide, challenge, and sustain that work over time.

From there, the conference widened into a program that balanced developer-focused talks with sessions on the Interactivity API, the HTML API, AI-driven development workflows, education initiatives, observability, automation, and startup strategy. On the final day, those threads continued through talks on WP translation, community building, WordPress Playground, data engineering, enterprise WordPress, and journalism on the open web.

Together, the two conference days made clear that WordCamp Asia 2026 was designed not for one kind of attendee, but for many. Developers, founders, marketers, contributors, organizers, and people finding their place in WordPress for the first time all found something that spoke directly to their work and interests. The breadth of the program was striking, but so was the feeling that these conversations mattered now.

Building What Comes Next

WordCamp Asia 2026 closed with reflections from Mary Hubbard, following an opening announcement from Chenda Ngak that WordCamp India will join the calendar in 2027 as the fourth flagship WordPress event.

Mary’s remarks tied together several threads that had already surfaced throughout the event: India’s long-standing role in the WordPress project, the growth of programs like Campus Connect and WordPress Credits, the energy of YouthCamp, and the significance of WordPress 7.0. One of the clearest ideas in the session was that WordPress is entering a new phase shaped by real-time collaboration, AI infrastructure, and global contributor growth. That framing gave the closing session a strong sense of direction without losing sight of the community work that made it possible.

The session then shifted into a panel discussion about the current state of WordPress and where the project is headed next. Peter Wilson and Sergey Biryukov joined Hubbard on stage, while audience questions brought the conversation back to many of the themes that had shaped the event across all three days. Even from afar, Ma.tt Mullenweg remained part of the discussion, following along remotely and sending written responses during the live Q&A.

Those questions touched on contributor growth, AI, plugins, local communities, product direction, and the long-term health of the open web. What stood out was how often the answers returned to the same core idea: WordPress continues to grow through open discussion, shared responsibility, and the people who keep showing up to build it together.

A Lasting Momentum

Over three days in Mumbai, WordCamp Asia 2026 brought together contribution, learning, and community. From Contributor Day through the closing keynote, the event balanced hands-on work with bigger conversations about publishing, technology, education, and the open web.

The event also created space for many kinds of participation. Some attendees contributed to Core, Training, Polyglots, Photos, and other teams. Others came for the conference program, workshops, or the chance to reconnect with collaborators and meet new people. Across session rooms, tea breaks, shared meals, sponsor hall conversations, and the after party, the community side of the event remained just as important as the formal program.

Thank you to the organizers, volunteers, speakers, sponsors, attendees, and everyone who joined online. WordCamp Asia 2026 was a reminder that WordPress continues to grow through the people who show up to contribute and build together.

There is still more to look forward to this year. The community will gather again at WordCamp Europe 2026 in Kraków, Poland from June 4–6, followed by WordCamp US 2026 in Phoenix, Arizona from August 16–19.

WordPress.org blog: Celebrating Community at WordCamp Asia 2026 Leer entrada »

Gary: Claudaborative Editing 0.4: Twice the fun!
General, Notas Interesantes

Gary: Claudaborative Editing 0.4: Twice the fun!

I’ve been taking an iterative approach to building Claudaborative Editing: build something to prove that the underlying concept works, then evolve on top of that. The first two iterations were answering a question I had: can an LLM genuinely improve the writing process? Along the way, I found a more important question: can it be done without contributing to the masses of generated slop we see?

Having seen the underlying idea working, I needed to answer the next question: can it be brought into the actual writing environment? Can it be useful, but keep out of the way?

Can you talk to an LLM from within WordPress, and have it talk back? I think I’m onto something, and it’s alot of fun.

Coming to a WordPress Near You

Naturally, the next step was to build a WordPress plugin that provided a straightforward interface to the LLM backend. You still install the tool to run with your local copy of Claude Code, but once it’s running, you can do everything directly from the block editor. The plugin is waiting to be approved for the WordPress.org plugin directory, but you can download it directly from the GitHub repo now.

Tools are easily accessible when you need them, but otherwise stay out of your way. You choose how much input you want the LLM to have in your writing: it can fix things up for you, or you can ask it to just leave notes and you’ll decide how you want to proceed. Personally, I prefer to do the work myself, but everyone can choose their level of comfort.

That said, one of the things I often forget to do when writing a post is to tag it properly. If I do remember, I’m never sure what to tag it with. By the time I get to publishing, I’m impatient just to get it out in the world! So, now there’s a button that’ll give suggestions right before publishing, letting you pick and choose which suggestions to use, and what to drop.

Planning is a Conversation

I always start Claude Code in planning mode, and I wanted that for posts, too. That’s where I started this post, and I can absolutely see myself using this every time I need to write a post. Not to do the writing for me, but to help me organise my thoughts. I opened the Compose mode in the sidebar, I had it summarise the changes that I’ve made in the last 2 weeks, and present a few options for how to collate them. Some I kept, some I dropped.

In a lot of ways, it’s more like a very advanced ELIZA, though rather than just reflecting your words back, it reflects your ideas back in a more structured form.

What’s next

I’ll be honest, I’m really happy with how this has turned out so far! I’d love to hear your feedback as you use it. What would you like to see here? I’ve already noted down a bunch of ideas that came up just while I was writing this post, so there are definitely more things to come!

Go ahead and give it a shot now:

npx claudaborative-editing start

Gary: Claudaborative Editing 0.4: Twice the fun! Leer entrada »

How to Set Min & Max WooCommerce Order Limits (& Stop Overselling)
General, Notas Interesantes

How to Set Min & Max WooCommerce Order Limits (& Stop Overselling)

It’s frustrating when customers place orders in your online store that are too small to be profitable, or so large that they deplete your stock and create shipping nightmares. Setting minimum and maximum order limits in WooCommerce solves this problem. It can help you keep your… Read More »
The post How to Set Min & Max WooCommerce Order Limits (& Stop Overselling) first appeared on WPBeginner.

How to Set Min & Max WooCommerce Order Limits (& Stop Overselling) Leer entrada »

General, Notas Interesantes

Weston Ruter: Adding an MCP Server to the WordPress Core Development Environment

I wanted to hook up Claude Code to be able to interact with my local wordpress-develop core development environment via MCP (Model Context Protocol). I couldn’t find documentation specifically for doing this, so I’m sharing how I did it here.

Assuming you have set up the environment (with Docker) and started it via npm run env:start.

1. Install & Activate the MCP Adapter plugin

The MCP adapter is not currently available as a plugin to install from the plugin directory. You instead have to obtain it from GitHub and install it from the command line. I installed it as a plugin instead of as a Composer package:

cd src/wp-content/plugins
git clone https://github.com/WordPress/mcp-adapter
cd mcp-adapter
composer install

Next, activate the plugin. Naturally, you can also just activate the “MCP Adapter” plugin from the WP admin. You can also activate it via WP-CLI (but from the project root working directory, since you can’t run this command from inside of the mcp-adapter directory:

npm run env:cli — plugin activate mcp-adapter

2. Register the MCP server with Claude

Here’s the command I used to register the wordpress-develop MCP server with Claude:

claude mcp add-json wordpress-develop –scope user ‘{«command»:»npm», «args»:[«–prefix», «~/repos/wordpress-develop/», «run», «env:cli», «–«, «mcp-adapter», «serve», «–server=mcp-adapter-default-server», «–user=admin»]}’

Here’s the JSON with formatting:

{
«command»: «npm»,
«args»: [
«–prefix»,
«~/repos/wordpress-develop/»,
«run»,
«env:cli»,
«–«,
«mcp-adapter»,
«serve»,
«–server=mcp-adapter-default-server»,
«–user=admin»
]
}

You may want to remove –scope user if you just want to register the MCP server for the one project. I tend to re-use the same WP environment for multiple projects (core and plugins), so I think it may make it easier for me to install at the user level instead.

You will also need to change the –prefix arg’s ~/repos/wordpress-develop/ value to correspond to where the repo is actually cloned on your system. I include this arg here so that when I start claude inside of a plugin project (e.g. inside src/wp-content/plugins/performance), it is able to successfully run the npm command in the package.json in the ancestor directory. You can remove this –prefix arg if this is not relevant to you.

Change the user from admin according to your needs.

3. Expose all abilities to MCP

Registered abilities are not exposed to MCP by default. This is a safety measure so that AI agents have to be explicitly allowed to perform potentially sensitive actions. So without any plugins active other than the MCP Adapter, prompting Claude with “discover abilities” results in:

No abilities found. The MCP server connection may be unstable. Try reconnecting again with /mcp.

However, since this is a local development environment, there is no concern about this (for me at least). To opt in all abilities to be exposed to MCP by default, you can use the following plugin code:

add_filter(
‘wp_register_ability_args’,
static function ( array $args, string $ability_id ): array {
if (
// Prevent exposing abilities in MCP except on a local dev environment.
wp_get_environment_type() === ‘local’
&&
// Omit abilities which the MCP Adapter already makes available itself.
! str_starts_with( $ability_id, ‘mcp-adapter/’ )
) {
$args[‘meta’][‘mcp’][‘public’] = true;
}
return $args;
},
10,
2
);

This is also available in a gist to facilitate installation via Git Updater.

Note: This filter does not currently apply if your ability is registered by extending Abstract_Ability in the AI plugin.

At this point, I can now open Claude (or re-connect to the MCP server) and see that it is able to see all (er, most) abilities that are registered on my wordpress-develop env with the same prompt “discover abilities”:

3 WordPress abilities available:

core/get-environment-info — Returns runtime context (PHP, database, WordPress version) with the ability name.

core/get-site-info — Returns site information (all fields or filtered subset)

core/get-user-info — Returns current user profile details

When I prompt “what’s the environment info?” it executes the core/get-environment-info ability via MCP and prints out:

Environment: local

PHP Version: 8.3.26

Database Server: 8.4.8 (MySQL)

WordPress Version: 7.1-alpha-62161-src

Now the environment just needs more abilities! I’ve filed a Performance Lab issue for us at the Core Performance table to work on adding abilities during Contributor Day at WordCamp Asia tomorrow.

Where I’ve shared this:

LinkedIn

Twitter

Bluesky

Threads

Mastodon
The post Adding an MCP Server to the WordPress Core Development Environment appeared first on Weston Ruter.

Weston Ruter: Adding an MCP Server to the WordPress Core Development Environment Leer entrada »

General, Notas Interesantes

Greg Ziółkowski: Research: Architecting Tools for AI Agents at Scale

Loading all available tools into an LLM’s context simultaneously is one of the most consequential architectural mistakes teams make when building AI integrations. The solution isn’t bigger context windows, and it’s progressive tool exposure: dynamically presenting only the tools relevant to each interaction. This post surveys the major patterns for doing so, drawn from production servers,

Greg Ziółkowski: Research: Architecting Tools for AI Agents at Scale Leer entrada »

Scroll al inicio