\r \r

html-deploy-easy\r

\r

Overview\r

\r Use htmlcode.fun when the output can be delivered as one standalone HTML document and speed matters more than full project-hosting features. This skill is designed for agents that need the shortest path from HTML content to a live shareable URL.\r \r Live example and walkthrough:\r

• https://www.htmlcode.fun/s/htmlcode-fun-guide\r \r Bundled script:\r
• scripts/htmlcode_deploy.py for deploy, update, and fetch operations\r \r

Decision rule\r

\r Use this skill when all of the following are true:\r

• The deliverable is a single HTML page.\r
• The page can be self-contained or nearly self-contained.\r
• Fast sharing matters more than custom domains, CI/CD, or multi-file assets.\r \r Do not use this skill when any of the following are true:\r
• The project is a React, Vue, Next, or multi-file frontend app.\r
• The site needs build steps, environment variables, or asset pipelines.\r
• The user specifically needs their own domain bound to the host.\r
• The page is likely to exceed the service limit of about 1 MB HTML payload.\r \r

Core workflow\r

\r

1. Produce one complete HTML document.\r
2. Inline CSS and JS when practical.\r
3. Add quality metadata before deploy:\r
   • \x3Ctitle>\r
   • \x3Cmeta name="description">\r
   • \x3Cmeta name="viewport" content="width=device-width, initial-scale=1.0">\r
   • Open Graph tags when the page will be shared\r
4. Decide whether the page needs a stable short code.\r
   • For one-off pages, deploy without custom code.\r
   • For pages that will be updated in place, set enableCustomCode=true and choose customCode on first deploy.\r
5. Deploy with JSON to POST https://www.htmlcode.fun/api/deploy.\r
6. Save the returned code, url, and qrCode.\r
7. For later edits, update with PATCH https://www.htmlcode.fun/api/deploy/content using the same code.\r
8. If the API returns 429, wait for retryAfterSeconds before retrying.\r \r

Fastest path\r

\r Prefer the bundled script when working from local files.\r \r Deploy a new page:\r \r

python scripts/htmlcode_deploy.py deploy page.html --title "launch-page" --code launch-page\r
```\r
\r
Update an existing short code in place:\r
\r
```bash\r
python scripts/htmlcode_deploy.py update launch-page page.html --title "launch-page-v2"\r
```\r
\r
Fetch deployed content:\r
\r
```bash\r
python scripts/htmlcode_deploy.py get launch-page --output launch-page.html\r
```\r
\r
Use raw API calls only when the agent already has HTML content in memory and does not need a file-based workflow.\r
\r
## Request format\r
\r
Always send JSON.\r
\r
Required fields:\r
- `filename`\r
- `content`\r
\r
Useful optional fields:\r
- `title`\r
- `enableCustomCode`\r
- `customCode`\r
\r
Example deploy payload:\r
\r
```json\r
{\r
  "filename": "index.html",\r
  "title": "launch-page",\r
  "content": "\x3C!doctype html>\x3Chtml>...\x3C/html>",\r
  "enableCustomCode": true,\r
  "customCode": "launch-page"\r
}\r
```\r
\r
Example update payload:\r
\r
```json\r
{\r
  "code": "launch-page",\r
  "content": "\x3C!doctype html>\x3Chtml>...updated...\x3C/html>",\r
  "title": "launch-page-v2",\r
  "filename": "index.html"\r
}\r
```\r
\r
## Best practices for agents\r
\r
- Prefer one larger deploy over many tiny edits because the service enforces a 10 second cooldown after success.\r
- Do not use multipart upload or `-F file`. Read files into memory and send them as JSON `content`.\r
- Keep the page self-contained. Inline CSS, inline lightweight JS, and avoid many external dependencies.\r
- Keep images small. Large base64 assets can quickly hit the payload limit.\r
- If the page will be revised repeatedly, reserve a meaningful `customCode` at the first deploy.\r
- Save returned `code`, `url`, and `qrCode` immediately after deployment.\r
- When receiving `429`, respect `retryAfterSeconds` instead of retrying aggressively.\r
- Treat htmlcode.fun as a fast publication channel, not a full static hosting platform.\r
- Tell the user clearly when the page is better suited for Vercel or Netlify instead.\r
\r
## What this host is good at\r
\r
- Temporary landing pages\r
- Demo pages\r
- Shareable documentation pages\r
- QR-linked event or campaign pages\r
- AI-generated single-file frontends\r
- Stable short-link pages that need quick overwrite updates\r
\r
## What this host is not good at\r
\r
- Multi-page sites with shared assets\r
- Framework builds\r
- Large production frontends\r
- Team workflows with preview environments and rollback\r
- Confirmed custom-domain hosting workflows\r
\r
## Example live page\r
\r
Reference example:\r
- https://www.htmlcode.fun/s/htmlcode-fun-guide\r
\r
Use that page as a model for how to explain advantages, limitations, and deployment guidance in one self-contained HTML document.\r