A Glimpse Into the Future of JCB
Published on September 2, 2026 by Llewellyn
To everyone who supports the continued development of Joomla Component Builder: thank you. Your support is helping us explore an exciting new chapter for JCB.
We are now using AI-assisted development to accelerate major improvements, including a powerful extension extruder, complete component API generation, and extensive compiler refactoring. The long-term goal is not simply to have AI produce more code, but to use AI to create structured JCB blueprints that the compiler can transform into complete, maintainable Joomla components.
This positions JCB as a development multiplier: a relatively compact blueprint can become an extensive, structurally complete, deployable component. We are also exploring MCP capabilities that could allow developers to build inside JCB conversationally and enable JCB-generated components to include their own MCP integrations.
The work is still experimental, fast-moving, and subject to change—but it offers a genuine glimpse of what JCB may soon become.
Your support gives us the space to research, build, test, and carefully move these advances toward stable releases. We deeply appreciate being able to take this journey with you.
🚀 2
Hi, René. It’s good to hear from you. It’s been a while.
Well, yes, absolutely. For us, this is also the way we see it. JCB remains the expected, predictable model. It remains the stability in our infrastructure. It is the part of our infrastructure where AI is not given free rein, and that’s why we have, as a whole separate organization and repository on GitHub, the place where AI is left loose on our code base.
Because whatever it is doing, we are meticulously and very carefully moving across, ensuring that our core stable release remains exactly that, a cornerstone of predictability, dependability, and stability and, in fact, that it can keep pace with the changing industry and become that multiplier of our efforts, as it has always been, but even more so: keeping up with the AI race without surrendering to it.
I don’t know if that makes sense, but yes, we are definitely on the same page there, and thank you for your support.
Well, yes, absolutely. For us, this is also the way we see it. JCB remains the expected, predictable model. It remains the stability in our infrastructure. It is the part of our infrastructure where AI is not given free rein, and that’s why we have, as a whole separate organization and repository on GitHub, the place where AI is left loose on our code base.
Because whatever it is doing, we are meticulously and very carefully moving across, ensuring that our core stable release remains exactly that, a cornerstone of predictability, dependability, and stability and, in fact, that it can keep pace with the changing industry and become that multiplier of our efforts, as it has always been, but even more so: keeping up with the AI race without surrendering to it.
I don’t know if that makes sense, but yes, we are definitely on the same page there, and thank you for your support.
on
As a long-time JCB user, I hope that JCB won't be patched to the point of becoming unusable. Unfortunately, many good programmers are tempted by pressure from AI-Side to patch their excellent software packages into being unusable.
Wanting more and more can turn into "becoming less and less usable."
JCB, as it is now, is a milestone in the Joomla world, and I hope it stays that way.
Regards, René