Create a Module

A CodeSCE module is made of up to three files. Before you open Studio, get these ready.

Required files

File	What it is	Required?
Module (ZIP)	Your module's core source code, packaged as a ZIP. This is the private, paid deliverable buyers download after purchase.	Required
README	Public documentation — what the module does, how to integrate it, requirements, and notes. Shown on the module page before purchase.	Required
UI (preview)	A preview of the module used to render the live preview on the module page.	Optional, strongly recommended

Minimum to save

You can save a draft with just a name + module ZIP + README. The UI preview is optional to save, but without it buyers can't see a live preview — and several quality checks (accessibility, responsive layout, image moderation) run against the UI. Include it.

What goes where

• Module ZIP → kept private. Delivered only to buyers, as a per-purchase watermarked ZIP.
• UI → kept private, used to render the sandboxed preview.
• README → public, readable by anyone browsing the module.

Best practices

Modules are reviewed automatically on upload (see Security Scanning). To sail through review and sell well:

• Keep it frontend. Server/backend code is rejected. Ship client-side code only.
• Include a UI preview. It powers the live preview and unlocks the UI-quality checks.
• Write a real README. Explain integration steps, requirements, and configuration. This is your sales pitch and your support doc.
• Ship clean dependencies. Vulnerable packages hurt your score — audit before you zip.
• Avoid copy-paste bulk. High internal duplication flags a module for manual review.
• Make the UI accessible and responsive. Accessibility and layout/responsive checks run against your preview.
• Keep content appropriate. Prohibited content and adult imagery are hard-rejected.
• Fill in metadata. A clear name, category, short description, tags, and feature list help buyers find and trust your module.

Next step

Files ready? Open Studio Workflow →.