Drafts, versions, pricing and private products
Complete drafts, publish versions, configure pricing and share private products through Teams.
Drafts and publishing
After the wizard confirms the source, Boilerplate creates a draft. Complete description, category, tags, license, price, discounts, publish settings and preview before saving or verifying. Use the draft stage to make the product understandable before it enters verification. Buyers should be able to tell what the product does, what it contains, what license applies and what version they are buying.
| Option | Meaning |
|---|---|
| Save | Keep the product as a draft and return later. |
| Verify and publish | Send the product through validation and publish when accepted. |
Pricing and discounts
Products can be free or paid. Use free pricing when the goal is adoption, sharing or team distribution. Use paid pricing when the component has commercial value and the seller account is ready to receive revenue. Discounts can be predefined, custom-ranged or disabled.
Product versions
Create versions for bug fixes, dependency updates, new features, rejected versions or changed files. After a product is published, some fields can become restricted, so code, file, description or tag changes may need a new version instead of editing the current publication.
Private products
Private products are shared through Teams instead of public Store listings. Use them for internal, client-only or team-only components. Access is controlled by the owner or team workspace, so users outside the selected team should not see or use the private product.
Version output
A version should contain enough information for a buyer to reproduce what they received: selected files, source reference, version label, dependency snapshot, license, pricing state and verification result. When a later version changes dependencies or files, keep release notes specific so buyers can decide whether to upgrade.