JUBELBUILD — DEVELOPER TOOLS
Smart Transformation
From a single DEV codebase to clean FREE and PRO plugin builds — automatically, reliably, every time.
One codebase. Three builds.
JubelBuild's transformation engine reads your DEV plugin, processes every file, and produces three perfectly tailored archives in seconds — without you touching a single line of code manually.
DEV ZIP
Your personal working copy. Header data (Author, Author URI) is injected from your active dataset. Use this for local testing — it stays structurally identical to your source.
FREE ZIP
Your public, wp.org-compliant version. Every [PRO] block is physically removed, the text domain is patched, and Freemius stubs, SDK references and wrapper functions are stripped automatically.
PRO ZIP
Your premium version for paying customers. The full codebase is retained and distributed via Freemius — only the [PRO] markers themselves are cleaned up.
What the engine does
Every time you click Start Build, the transformation engine runs five sequential operations across all files in your plugin.
1 — PRO block removal
Every section wrapped in // [PRO] … // [/PRO] markers is physically deleted from all PHP, JS, CSS, HTML and TXT files in the FREE build — no stub, no comment, no empty line left behind.
2 — Header injection
The Author and Author URI fields in every PHP header are overwritten from your active dataset, and the Stable tag in readme.txt is synced to your target version.
3 — Text-domain patching
The -dev suffix is stripped from the text domain in the header and in all translation calls — so the FREE build loads the right language files without any manual search-and-replace.
4 — Freemius & SDK cleanup
Ghost classes, SDK stubs, wrapper functions and any SDK start/end blocks are removed from the FREE build. Files with freemius in their name are deleted and their require lines removed.
5 — ZIP packaging
Clean, immediately deployable archives are created for all three variants, following a consistent naming convention — only the version number in the header changes between releases.
Tagging your code
The only thing you do in your source code is wrap PRO-only sections with two comment markers. JubelBuild handles everything else.
// [PRO]
function my_premium_feature() {
// This entire block is removed from the FREE build.
// Nothing — not even an empty line — is left behind.
return fs_dynamic_init( [ 'id' => '1234' ] );
}
// [/PRO]
function my_free_feature() {
// This remains in all three builds untouched.
return 'available to everyone';
}PHP files
Use // [PRO] and // [/PRO] on their own lines. Works inside functions, classes, and at file level.
JS & CSS files
The same markers work in JavaScript and CSS — the engine processes all text-based file types in your plugin folder.
Workspace guides
The built-in workspace guide files also support PRO blocks — so your documentation stays accurate in both the FREE and PRO versions.
Safe by design
The transformation engine never modifies your DEV source. It works on an extracted copy inside a temporary build directory and discards it after packaging.
✓ Non-destructive
Your uploaded DEV ZIP is never altered. The engine works on a temporary copy that is deleted after the build completes.
✓ DEV-only input
JubelBuild enforces that only DEV-tagged plugins are accepted. A FREE or PRO build uploaded by mistake is rejected before any processing begins.
✓ Slug validation
The ZIP folder name is validated against your active dataset slug — uploading the wrong plugin to the wrong project is caught immediately.
Ready to transform your plugin?
Set up your dataset, tag your PRO code, upload your DEV ZIP — and JubelBuild does the rest.