Blueprints

Blueprints define the rules for text generation. They are the core of your pipeline and determine how your data is transformed into text. Each pipeline can have one or many blueprints, and which blueprints are used to render a specific object is determined by the fanout script.

Blueprints are compatible with Cockpit rulesets and are in fact exactly the same. You can use the same rulesets you used in Cockpit, or create new ones.

Ask your customer success agent if you want to import your existing Cockpit rulesets into Studio, it's super easy!

Have a look at the ruleset documentation for more information on how to write rulesets.

Studio vs Cockpit

Blueprints in Studio differ in some small details from Cockpit rulesets. Features that rely on data source analysis, like the Analyze tab or histogram nodes, are not available in Studio. How you add test objects to your blueprint is also different. In Studio, you can add test objects directly inside the blueprint, in the test object manager. Right now test objects are only grabbed from the first data pool you have created.

More to Come

Translation packages and the translate app are not yet available in Studio. We are working on bringing translation packages to Studio soon.