Build the solution · 2 / 4

Put production in a safe order

Require printing, folding and then binding.

YOUR TASK

Make this happen

3 steps

Add print, fold and bind operations: DIGITAL_PRINTING, FOLDING and SADDLE_STITCHING. Wire fold after print and bind after fold.
Keep the working capabilities from the previous lesson and connect the new pieces to the same solution.
Check the complete solution, then inspect any unmet requirements.

THE IDEA BEHIND IT

What this step adds

Add print, fold and bind operations: DIGITAL_PRINTING, FOLDING and SADDLE_STITCHING. Wire fold after print and bind after fold.

Files to work in

main.cococo. Other files are the working baseline. New files include named resource skeletons and TODO guidance. Complete their fields and connect them using the objectives, schema completion and reference guide.

Dependencies form a graph

Operations are top-level so dependencies can cross components. dependsOn names predecessor operation localIds, not array indexes.

Publish checks the whole graph

The platform rejects duplicate IDs, unknown component/operation references, self-reference and cycles. Here the lesson checks this concrete valid sequence against the native resource shape.

Local native resource-shape and lesson checks do not run the product-template domain validator, publish versions, select tenant substrates or create jobs.

Files to change: main.cococo

What you’re building: Build a portable booklet template with a production sequence and customer page-count choice.

This step starts with the earlier solution and one new challenge. Each lesson keeps its own draft.

Read the starter files

main.cococo

product_template "booklet" {
  name = "Customer booklet"
  sku = "BOOKLET-A5"
  components = [{
    localId = "text"
    kind = "TEXT"
    name = "Booklet pages"
    totalPages = 16
  }]
  operations = []
}

Reference: product-templates · authoring schemas · authoring