Studio Workflow
Studio is where you turn your files into a published module. It's a two-step flow: first the profile (files + metadata), then the variables (configuration).
Step 1 — Profile: upload files & metadata
On the first step you upload your files and describe the module.
Upload files
Provide your Module ZIP, README, and (recommended) UI preview. See Create a Module for what each file is.
Scanning happens here
The moment you submit, your files run through the automated security pipeline — before anything is stored. If the module is rejected, nothing is saved and you get a report explaining why.
Configure metadata
Describe the module so buyers can find and evaluate it:
- Name
- Category (one of the marketplace categories)
- Short description (the card blurb)
- Full description
- Tags (up to 10) and features
- Price (see Monetization)
Draft vs publish requirements
You can save a draft with just a name, module ZIP, and README. To publish, you additionally need a category, a short description, and a price.
Step 2 — Variables: define configuration
The second step is where you make your module configurable without buyers touching code. You define a config schema — the set of variables buyers can adjust (labels, options, toggles, defaults).
CodeSCE renders this schema as a form using the Dynamic Form Engine, which is exactly what buyers use after purchase, and what appears as "Config options" on the module page. See Dynamic Configuration for how it works.
Preview your module
Before finishing, preview the module to confirm the UI renders and your config variables behave as intended — the same sandboxed preview buyers see.
Finish
The variables step gives you two ways to save:
- Save as Draft — keeps the module private while you keep working.
- Save & Finish — publishes the module (subject to the review outcome).
Next step
Curious what happens to your files on upload? Read Security Scanning →.