A short series on one tool. The first post says what Org Builder is and why we built it. The next ones show it working on small, generic examples: a few blueprints and property groups moved from one organization to another with the destination’s own values, then a content library and a package’s own instructions. For platform teams who have rebuilt a catalog by hand once and would rather not again. Read them in order.

Introducing Org Builder
Why we built Org Builder, our tool for VCF Automation organizations: catalog services built in one organization have to reach others, and rebuilding them by hand or scripting every API call doesn’t scale. Packages, site files and versioned releases, in brief.