Publish a template
Share your bot or site for others to deploy: remove private details, add a README, and submit it for review.
Made a bot or site other people could use? Share it as a template, and anyone can deploy their own copy. Our team checks every template before it goes on the Templates page.
1. Make a draft
- Open your dashboard and go to Templates.
- Click Publish a template.
- Pick the server to share, give it a name and category, and describe it.
- Click Make draft.
We copy the server’s files into a private draft. Your server isn’t changed, and nothing is public yet.
These are left out automatically: node_modules, .git, virtual environments (venv, .venv), __pycache__, logs, database files (.db, .sqlite) and private key files. A template can be up to 50 MB and 3,000 files, and single files over 10 MB are left out.
2. Remove your private details
The draft opens with a list of checks at the top. The personal-data check looks through your .env files, config files and code for anything private:
- bot tokens, API keys, passwords and webhook links
- database logins
- email addresses, IP addresses and Discord IDs (such as your server or owner ID)
Click any item to open that file at the right place. Or click Remove them all: every value is blanked but its setting is kept. For example TOKEN=abc123... becomes TOKEN=, so people know to fill it in.
WichtigYou can’t submit a template while this check finds anything. If your code has a token written straight into it, move it into
.envand read it from there instead.
3. Add a README
Your README.md, in the top folder, becomes the template’s page. It’s required. Explain what it does, how to set it up, and which settings to fill in. If you don’t have one, click Create README.md for a starter to fill in.
READMEs use Markdown: headings, lists, tables, code blocks, links and pictures all work. Pictures can be links, or files in the template (for example ).
4. Fill in the page details
On the right of the draft:
| Field | What it’s for |
|---|---|
| Name | Shown on the Templates page. |
| Describe your bot | What it does and its main features, in at least 30 characters. |
| Icon | A square picture, like a profile picture. |
| Banner | A wide picture, such as a screenshot of it working. |
| Custom emoji | Used as the icon and banner until you upload your own. Pick a drawing and a colour. |
| Category and Runtime | How people find it. |
| Start command and Install command | Set on servers it’s deployed to, such as node index.js and npm install. |
| You will need | The settings people must fill in, such as TOKEN. Filled from your .env file. You can mark each as required or optional and add a note. |
Pictures can be PNG, JPG, WebP or GIF: the icon up to 2 MB, the banner up to 5 MB. Click Save details when you’re done.
You can also change the draft’s files below, using the same file manager as the Files tab.
5. Submit it
When every check is green, click Submit for review. It shows as In review until our team has looked at it.
| Status | What it means |
|---|---|
| Draft | Only you can see it. |
| In review | Waiting for our team. To change it, click Take out of review. |
| Declined | It needs changes. The reason is shown on the template, and we email it to you. Fix it and submit again. |
| Live | On the Templates page for everyone. |
HinweisOur team can read every file in your template, and may tidy up small things before approving it.
Change a live template
Open it and click Unpublish to edit. It comes off the Templates page until it’s approved again. Servers people have already deployed it to aren’t affected.
Verified templates
Once a template is live, SmileCorp can mark it Verified after an extra check, and it gets a blue tick. If you unpublish a verified template to change it, it loses the tick until it’s checked again.
You can have up to 10 templates that aren’t live yet at once. Delete (the bin button) removes a template and its files for good.