Projects
A project is one configurator. It holds a 3D scene, the panel of options your customers use, the logic between those options, and the prices. You build it in Composer and publish it to the products it belongs to.
Most stores end up with one project per product family. A dining table available in three woods and four sizes is one project, not twelve.
Creating one
New project asks for a title and then opens Composer.
There is a checkbox, Also create a product for this configurator. It makes a draft product and links it, which is handy when you are trying things out and do not want to touch your real catalogue yet. If you already have the product, skip it and link that product instead.
The project page
Opening a project from the list gives you everything about it apart from the design itself, which is in Composer. The page is organised into a few cards.
Publishing
Where you link products and publish. Publishing takes the current state of the project and sends it to every linked product, and until you do, changes you save in Composer stay private to you.
A project can be linked to more than one product, which is how you reuse one configurator across a range that shares a design.
You can also unpublish, which removes the configurator from its products and leaves the products themselves untouched.
Storefront settings
How the configurator presents itself on the product page. Canvas height on desktop and on mobile, maximum width, side margins, whether the options panel sits beside the 3D view or below it and how wide it is.
This is also where you choose how configured prices are charged, which is explained in Charging methods, and where you can put a configurator into maintenance mode. Maintenance mode shows your customers a message instead of the configurator, which is what you want if you have spotted a problem and need it off the storefront right now.
Canvas sizing has its own page, since it is the setting people most often want to adjust.
Used by Composer projects
If your project links to any scripts, they are listed here. When a script you use has been published since you last published this project, the app says so, so you know a republish is needed to pick up the newer version.
Pricing catalog
Two lists. Products from your own catalogue that you have linked to options, and the helper products the app created to charge for configured options. Helper products explains what those are and why they exist.
Versions
Every publish keeps a snapshot, so you can look back at what was live at a given time. You can also take a manual backup before a big change, and restore one if a change turns out worse than what it replaced.
Saving and publishing are different
Worth repeating because it catches people out. Save keeps your work in the project. Publish puts it on your storefront. You can save as often as you like without any of it reaching a customer.
Deleting a project
Deleting removes the configurator from its products and cleans up the files it published. Helper products it created are archived rather than deleted, because past orders refer to them and those orders must keep making sense.