We would like to take a moment to sincerely thank everyone who supports Joomla Component Builder (JCB) through Open Collective. Your backing-whether financial, advisory, or simply by standing behind the project-makes a very real difference. It allows us to invest time, care, and long-term thinking into JCB, rather than focusing only on short-term deliverables.

This update is both a thank you and a project progress report.

Over the past development cycle, we've been working on improvements that significantly expand how developers can work with JCB, especially in more advanced, automated, and professional environments. These changes are now available in JCB X.1.4 Beta 6.

Two areas stand out in this release:

JCB now includes a comprehensive CLI command suite that allows developers to interact with Component Builder directly from the terminal. This includes compiling components, synchronizing JCB entities with remote repositories, resetting local state, pushing changes upstream, and optionally installing compiled extensions automatically.

The CLI has been designed to be explicit, predictable, and automation-friendly, making it suitable for CI/CD pipelines, containerized setups, and headless servers-while still being approachable for developers who are new to command-line workflows.

📘 Detailed CLI documentation:
https://github.com/orgs/joomengine/discussions/1013

The Powers system has been extended to allow developers to override or add PHP classes directly into the generated src/ folders of components, modules, and plugins.

This is done through a clear, namespace-based approach that makes placement and overrides intentional and deterministic. It gives advanced users the freedom to take ownership of specific classes or extend generated code in a clean, maintainable way-without relying on post-build scripts or manual copying.

📘 Detailed Power override documentation:
https://github.com/orgs/joomengine/discussions/1012

These changes move JCB closer to a more mature and flexible development platform-one that supports both traditional GUI-driven workflows and modern automation-focused practices. They also reflect a core philosophy of the project: power should be available, but never forced. Developers can adopt these features at their own pace, when and if they need them.

Because this release is still in beta, community testing and feedback are especially important. Stability, memory usage, and real-world edge cases are areas we are actively monitoring and refining.

None of this work happens in isolation. Your support through Open Collective gives us the freedom to:

    Refactor carefully instead of rushing
    Document thoroughly instead of cutting corners
    Experiment responsibly with new ideas
    Maintain continuity in a long-running project

For that, we are deeply grateful.

If you'd like to see the broader announcement and how all of this fits together:

🔗 Full release announcement:
https://github.com/orgs/joomengine/discussions/1014

As always, thank you for your trust, your patience, and your support. We look forward to continuing this journey with you-and to shaping the next phase of JCB together.