■ Guided site building · no filler

This isn’t an article
It’s afollow-it-and-shipprocess

You didn’t come here to read, you came to build. Pick a scenario and work through it: every step has instructions, a copy-paste script and a checklist. Stuck? Go to the feedback site. This site has no comment section, on purpose.

新手起步

第一次建站?我带你从第一步走

Pick a scenario,跟着步骤一步步做——每步都有说明、一键脚本和自查清单,不用自己踩坑。

从 AI 变现站起步(7 步)→
老手开干

闭着眼都会?直接挑要做的

21 个场景、99 步可执行清单,挑你要的那块;或直奔工具箱与文档,不绕路。

21Scenarios
99Actionable steps
0Backend / database
¥50Total cost per year

Pick a scenario

Each scenario is a complete path, from buying a server to earning from it. Pick wrong and you lose nothing — the early steps are shared.

How this site works

Plain HTML plus JSON, no backend. Change the JSON and the page changes.

1 · Everything lives in JSON

Scenarios, steps, FAQs and promo links are separate JSON files. Edit text without touching HTML, and without breaking the layout.

config.jsonsteps.jsonfaq.json

2 · Every step is self-checked

Each step ends with a checklist, so you can confirm it yourself instead of asking. Progress is stored locally in the browser.

localStorageTick to finish

3 · Stuck? Go to the feedback site

The FAQ is local keyword matching and only covers the common questions. Really stuck? The feedback site is where people answer.

No commentsOne place to talk

What the 21 scenarios give you (at a glance)

For anyone who wants the conclusion first. The early scenarios share their opening steps — buy a server, install a panel, fill in the JSON — and only differ in what you build at the end. 21 scenarios, 99 steps.

AI Content Monetisation Site (7 steps · about 2 hours)

Plain HTML driven by JSON, earning through platform invite codes and affiliate commissions: no backend, no database, no maintenance.

  • Time: about 2 hours · difficulty: Medium
  • 7 steps, each with a script and a checklist
Open the AI Content Monetisation Site guide →

Server Monitoring Dashboard (5 steps · about 1.5 hours)

A collector script plus phone alerts — you know the moment something breaks, instead of finding out later.

  • Time: about 1.5 hours · difficulty: Advanced
  • 5 steps, each with a script and a checklist
Open the Server Monitoring Dashboard guide →

Link Directory / Short-Link Site (4 steps · about 1 hours)

A front-end-only directory of your favourite tools, with ad slots you can monetise.

  • Time: about 1 hours · difficulty: Easy
  • 4 steps, each with a script and a checklist
Open the Link Directory / Short-Link Site guide →

AI News Aggregator Site (5 steps · about 2 hours)

Reuse a public AI news feed to build your own AI daily page: auto-updating, near-zero maintenance, and a funnel you can monetise.

  • Time: about 2 hours · difficulty: Medium
  • 5 steps, each with a script and a checklist
Open the AI News Aggregator Site guide →

Personal Tech Blog / Content Site (5 steps · about 2.5 hours)

A static writing site: write in Markdown, generate pages automatically, ship RSS and third-party comments.

  • Time: about 2.5 hours · difficulty: Medium
  • 5 steps, each with a script and a checklist
Open the Personal Tech Blog / Content Site guide →

Self-hosted Image Hosting / Object Storage (5 steps · about 1.5 hours)

Object storage plus direct-link management: your images, your rules, and a natural affiliate angle.

  • Time: about 1.5 hours · difficulty: Advanced
  • 5 steps, each with a script and a checklist
Open the Self-hosted Image Hosting / Object Storage guide →

Email Newsletter Site (5 steps · about 2 hours)

RSS-to-email automation plus a landing page: turn readers into a list you own, and monetise it over time.

  • Time: about 2 hours · difficulty: Advanced
  • 5 steps, each with a script and a checklist
Open the Email Newsletter Site guide →

SEO Toolbox Site (5 steps · about 2 hours)

Sitemap generation, robots checking, dead-link probing — small front-end-only tools that pull traffic and are fun to build.

  • Time: about 2 hours · difficulty: Medium
  • 5 steps, each with a script and a checklist
Open the SEO Toolbox Site guide →

AI Chatbot Page (5 steps · about 2 hours)

Wire an LLM API into a chat page that answers questions on your site around the clock.

  • Time: about 2 hours · difficulty: Medium
  • 5 steps, each with a script and a checklist
Open the AI Chatbot Page guide →

High-conversion Landing Page (5 steps · about 1.5 hours)

One page, one CTA, instrumented end to end: turn "someone looked" into "someone clicked".

  • Time: about 1.5 hours · difficulty: Easy
  • 5 steps, each with a script and a checklist
Open the High-conversion Landing Page guide →

Documentation / Knowledge Base Site (5 steps · about 2 hours)

Write docs in VitePress: sidebar, full-text search and static output with one command — works for products and tutorials alike.

  • Time: about 2 hours · difficulty: Medium
  • 5 steps, each with a script and a checklist
Open the Documentation / Knowledge Base Site guide →

Personal Resume / Portfolio Site (4 steps · about 1 hours)

One page that says who you are and what you've built: work cards, PDF export, a contact entry — useful when you're taking on work.

  • Time: about 1 hours · difficulty: Easy
  • 4 steps, each with a script and a checklist
Open the Personal Resume / Portfolio Site guide →

AI API Relay (5 steps · about 2.5 hours)

OpenAI-compatible forwarding with key distribution and usage metering: wrap an API into something you can sell and cap.

  • Time: about 2.5 hours · difficulty: Advanced
  • 5 steps, each with a script and a checklist
Open the AI API Relay guide →

RSS Reader / Feed Site (4 steps · about 1.5 hours)

Aggregate several RSS feeds into a reader of your own: fetch on a schedule, land it in JSON, render it statically — no backend.

  • Time: about 1.5 hours · difficulty: Medium
  • 4 steps, each with a script and a checklist
Open the RSS Reader / Feed Site guide →

Backend-free Form Collection Site (4 steps · about 1 hours)

Sign-ups, feedback and lead capture through a form service or cloud function — data lands in a spreadsheet, no backend to run.

  • Time: about 1 hours · difficulty: Easy
  • 4 steps, each with a script and a checklist
Open the Backend-free Form Collection Site guide →

Public Service Status Page (4 steps · about 1 hours)

Turn uptime into a public page: OK or down at a glance, with a record you can point users to during an incident.

  • Time: about 1 hours · difficulty: Medium
  • 4 steps, each with a script and a checklist
Open the Public Service Status Page guide →

CDN + HTTPS Acceleration (4 steps · about 1 hours)

Certificate, origin and cache rules configured once: speed and security improve together, and SEO benefits along the way.

  • Time: about 1 hours · difficulty: Medium
  • 4 steps, each with a script and a checklist
Open the CDN + HTTPS Acceleration guide →

Backup and Disaster Recovery (4 steps · about 1.5 hours)

Automated backups, an off-site copy and a restore drill: a real backup is one you have restored from, not one you have zipped.

  • Time: about 1.5 hours · difficulty: Medium
  • 4 steps, each with a script and a checklist
Open the Backup and Disaster Recovery guide →

AI Content Production Site (5 steps · about 2.5 hours)

Topic → AI draft → human review → publish → indexing observation: turn content into a repeatable pipeline.

  • Time: about 2.5 hours · difficulty: Medium
  • 5 steps, each with a script and a checklist
Open the AI Content Production Site guide →

Backend-free Comments and Community (4 steps · about 1 hours)

Giscus or Waline for comments: keep readers on your site, and let the comments themselves accumulate into findable content.

  • Time: about 1 hours · difficulty: Easy
  • 4 steps, each with a script and a checklist
Open the Backend-free Comments and Community guide →

Site Search / Full-text Search (5 steps · about 1.5 hours)

A static site can have its own search: build the index at build time, query it in the browser — no backend, no database.

  • Time: about 1.5 hours · difficulty: Medium
  • 5 steps, each with a script and a checklist
Open the Site Search / Full-text Search guide →
What server specs should I buy, and why not 1 core and 1 GB?
For a personal content site: 2 vCPU, 2 GB of RAM, 3–5 Mbps of bandwidth. Don't take 1 core and 1 GB — a hosting panel alone wants 500 MB+, and running Nginx on top of that leaves nothing to spare. Entry-level VPS plans are the best value, around US$10–15 a year on a promotion.
SSH won’t connect. How do I debug it?
1. Confirm the server IP is right; 2. confirm the SSH port is 22, the default; 3. allow port 22 in the server's firewall; 4. confirm the username is root; 5. paste the password rather than typing it.
The panel’s port 8888 won’t open. What do I do?
The panel's default port is 8888. Allow it in the cloud console's security group or firewall. If you changed the port, run bt default over SSH to see the current address and port.
The site returns 403 Forbidden. What now?
1. Check the root directory has an index.html; 2. check file permissions, they should be 644; 3. panel → site settings → site directory, confirm the run directory is the site root; 4. try turning off the cross-site attack protection (open_basedir).
A JSON mistake gave me a blank page. How do I find it?
JSON is strict: strings need double quotes, no trailing comma after the last item, brackets must balance. Paste the file into a validator such as jsonlint.com. The most common mistake by a wide margin is a comma after the final entry.Reading the Console is the fastest way to spot it.
The HTTPS certificate request failed. What now?
Panel → site → SSL → Let's Encrypt → request. If it fails: 1. confirm the domain resolves and points at this server; 2. confirm port 80 is open; 3. the same domain can only be requested 5 times in 24 hours — try again tomorrow.
My new site still isn’t indexed. Is that normal?
1. Check robots.txt isn’t blocking the crawler; 2. submit the sitemap in the search platform; 3. submit the home page URL by hand; 4. keep the content more than 70% original; 5. wait 1–4 weeks — new sites are slow to index, that’s normal.
How do I join a cloud affiliate programme, and what do they pay?
The main ones are the cloud vendors’ own partner programmes. They usually require identity verification and a registered site, and take 1–3 working days to review. Expect around 15–30% of a new customer’s first order.
How do I back up the site?
Panel → scheduled tasks → back up site → pick the site directory → store it in object storage. Weekly full backups. The JSON files are small, so downloading them by hand now and then works too.

Still stuck? Type a keyword into the AI helper on the wizard page, or go to Feedback and ask. This site has no comment section — that’s deliberate.