M Ming’s Daily
Home / Wizard

Site wizard: pick a scenario, follow the steps, go live

Every step carries instructions, a copy-paste script and a checklist: pick a scenario, then follow the steps from buying a server and filling in the data through to launch and monetisation. Do a step, tick a step. Stuck? Go to the feedback site — the main site keeps no comment section.

■ Overview · all scenarios

21 scenarios, 99 steps · outline

Here is the outline of every scenario. Each has its own page, with the full walkthrough, scripts and checklists — click a title to open it. Generated by scripts/seo-prerender.js from data/en/steps.json.

AI Content Monetisation Site guide (7 steps): Buy a server and point the domain at it → Install a hosting panel → Create the site and upload the files

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

  1. AI Content Monetisation Site guide (7 steps): Buy a server and point the domain at it → Install a hosting panel → Create the site and upload the files — Pick a plan, order it, point the domain at the IP
  2. Step 2 · Install a hosting panel — One command, then wait 5–10 minutes
  3. Step 3 · Create the site and upload the files — Add a site in the panel, then upload the HTML and JSON
  4. Step 4 · Fill in the JSON data sources — Content, promo links and the FAQ all go into JSON
  5. Step 5 · The AI helper module + the automation scripts — FAQ keyword matching, plus the copy-paste scripts, both in place
  6. Step 6 · Configure the monetisation links — Join affiliate programmes and turn traffic into money
  7. Step 7 · Launch + SEO + monitoring — HTTPS, submit for indexing, analytics, routine backups

Server Monitoring Dashboard guide (5 steps): Get a server and install a hosting panel → Deploy the collection script → Configure alerting (chat webhook / email)

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

  1. Server Monitoring Dashboard guide (5 steps): Get a server and install a hosting panel → Deploy the collection script → Configure alerting (chat webhook / email) — A 2-core / 2 GB box with a control panel on it
  2. Step 2 · Deploy the collection script — Collect CPU / memory / disk / processes into JSON
  3. Step 3 · Configure alerting (chat webhook / email) — Push threshold breaches to your phone instead of staring at a screen
  4. Step 4 · Schedule it and make it survive a reboot — Collect once a minute; come back automatically after a restart
  5. Step 5 · Dashboard + backup strategy — Turn the JSON into charts, and back up the config

AI News Aggregator Site guide (5 steps): Pick the feed and understand where the data comes from → Fetch the data and land it in JSON → Render the list on the front end

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

  1. AI News Aggregator Site guide (5 steps): Pick the feed and understand where the data comes from → Fetch the data and land it in JSON → Render the list on the front end — Use an existing public AI news API; learn the latest / by-date / list endpoints
  2. Step 2 · Fetch the data and land it in JSON — A scheduled fetch script writes the feed into a local daily.json
  3. Step 3 · Render the list on the front end — Fetch the local JSON, render cards, add date filtering
  4. Step 4 · Schedule updates + aggregate more sources — A daily scheduled task pulls the feed; add your own RSS when you want more
  5. Step 5 · Launch + SEO + monetise the traffic — Upload, add HTTPS and a sitemap; treat the aggregator as a funnel to affiliate offers

Personal Tech Blog / Content Site guide (5 steps): Pick your writing setup (hand-written vs generator) → Set up the local writing workflow → Auto-generate index, archive and tag pages

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

  1. Personal Tech Blog / Content Site guide (5 steps): Pick your writing setup (hand-written vs generator) → Set up the local writing workflow → Auto-generate index, archive and tag pages — Choose first: raw HTML / static generator (Hugo, VitePress) / hosted platform
  2. Step 2 · Set up the local writing workflow — Directory conventions + front matter + images + categories and tags
  3. Step 3 · Auto-generate index, archive and tag pages — One command builds lists, categories, tags and RSS
  4. Step 4 · Add RSS + third-party comments — Keep readers: RSS feed + backend-free comments (Giscus and friends)
  5. Step 5 · Deploy + SEO + distribution — Ship it, enable HTTPS, get indexed, turn readers into an asset

Self-hosted Image Hosting / Object Storage guide (5 steps): Create the bucket + basic settings → Custom domain + CDN → Hotlink protection + cost control

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

  1. Self-hosted Image Hosting / Object Storage guide (5 steps): Create the bucket + basic settings → Custom domain + CDN → Hotlink protection + cost control — Pick a region, public-read / private-write, standard storage
  2. Step 2 · Custom domain + CDN — Your own domain, HTTPS, CDN origin
  3. Step 3 · Hotlink protection + cost control — Referer rules + traffic and size alarms + lifecycle rules
  4. Step 4 · Upload toolchain (drag, get a link) — COSCLI / ossutil on the CLI, or PicGo on the desktop
  5. Step 5 · Wire it into your site + backup + monetise — Serve all images from your host, back it up, keep keys secret, add affiliates

Email Newsletter Site guide (5 steps): Choose a mail provider and get the compliance straight → Landing page + subscribe form → Automate the content (RSS-to-email)

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

  1. Email Newsletter Site guide (5 steps): Choose a mail provider and get the compliance straight → Landing page + subscribe form → Automate the content (RSS-to-email) — A domestic sending service or one abroad; double opt-in is the floor
  2. Step 2 · Landing page + subscribe form — A page where someone can leave an address, with an embedded or hand-written form
  3. Step 3 · Automate the content (RSS-to-email) — Your blog's RSS becomes email, sent on a schedule
  4. Step 4 · Deliverability: stay out of the spam folder — SPF / DKIM / DMARC + domain warm-up + content traps
  5. Step 5 · Growth + monetisation + long-term operation — Funnel traffic in, honour unsubscribes, monetise the list

SEO Toolbox Site guide (5 steps): Pick the tool list: only what runs purely in the browser → Implement the tool pages (input → compute → output) → Give every tool a "next step"

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

  1. SEO Toolbox Site guide (5 steps): Pick the tool list: only what runs purely in the browser → Implement the tool pages (input → compute → output) → Give every tool a "next step" — Sort 'the browser can compute this' from 'needs a server' before building something impossible
  2. Step 2 · Implement the tool pages (input → compute → output) — One generic tools.js skeleton; every new tool is just a handler
  3. Step 3 · Give every tool a "next step" — Right after a result is the conversion window — don't let people finish and leave
  4. Step 4 · Instrument it: turn "used" into measurable conversion — Three stages to track: tool used, result copied, guidance clicked
  5. Step 5 · Launch + indexing observation + iteration cadence — Submit the sitemap, keep an indexing checklist, let the data pick the next tool

AI Chatbot Page guide (5 steps): Pick a model and endpoint; make one call work first → The key never reaches the browser → Build the chat page: streaming + context

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

  1. AI Chatbot Page guide (5 steps): Pick a model and endpoint; make one call work first → The key never reaches the browser → Build the chat page: streaming + context — Use an OpenAI-compatible API; get curl working before you write any page
  2. Step 2 · The key never reaches the browser — Calling from the front end publishes your key — put a proxy in front
  3. Step 3 · Build the chat page: streaming + context — Read the stream with fetch, render token by token, keep only recent turns
  4. Step 4 · Add guardrails: prompt, sensitive content, cost ceiling — Scope the answers, filter the input, set a daily budget
  5. Step 5 · Launch + conversion tracking + monetisation — Instrument real usage; put provider affiliate links at the bottom

High-conversion Landing Page guide (5 steps): Say one thing clearly: who it's for, what they get, why believe you → Page structure: one line of argument, downwards → Instrument it: CTA clicks, scroll depth and source, recorded separately

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

  1. High-conversion Landing Page guide (5 steps): Say one thing clearly: who it's for, what they get, why believe you → Page structure: one line of argument, downwards → Instrument it: CTA clicks, scroll depth and source, recorded separately — Above the fold: audience, outcome, proof
  2. Step 2 · Page structure: one line of argument, downwards — Pain → solution → proof → objections → CTA. No unrelated modules
  3. Step 3 · Instrument it: CTA clicks, scroll depth and source, recorded separately — Without tracking, A/B tests and "optimisation" are guesswork
  4. Step 4 · Run one A/B test: change one variable — Change only the headline, or only the CTA copy, and wait for enough samples
  5. Step 5 · Launch + speed + indexing and weekly review — Fast is part of conversion; and put the page on the indexing watchlist

Documentation / Knowledge Base Site guide (5 steps): Pick the tool and get an empty site running → Configure nav / sidebar / search → Write the content: one page, one problem

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

  1. Documentation / Knowledge Base Site guide (5 steps): Pick the tool and get an empty site running → Configure nav / sidebar / search → Write the content: one page, one problem — VitePress in three commands, previewing locally
  2. Step 2 · Configure nav / sidebar / search — Order the sidebar by how readers look for things, not by your folder layout
  3. Step 3 · Write the content: one page, one problem — The title states the problem; the body gives steps plus copy-paste snippets
  4. Step 4 · Build + deploy (GitHub Pages / Vercel / your own server) — One command produces static output; push it and it's live
  5. Step 5 · SEO + indexing observation + content iteration — Every page indexable and on the watchlist; add pages based on search terms

Personal Resume / Portfolio Site guide (4 steps): Fix the skeleton: one page, three questions answered → Build the single page: structure + print-friendliness → Launch + custom domain + visit tracking

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.

  1. Personal Resume / Portfolio Site guide (4 steps): Fix the skeleton: one page, three questions answered → Build the single page: structure + print-friendliness → Launch + custom domain + visit tracking — Who I am / what I've built / how to reach me — in that order
  2. Step 2 · Build the single page: structure + print-friendliness — Plain HTML and CSS; @media print gives you the PDF for free
  3. Step 3 · Launch + custom domain + visit tracking — A short domain wins; then see who's looking and where from
  4. Step 4 · Maintenance: quarterly updates + keep old versions — Snapshot every update so links never rot

AI API Relay guide (5 steps): Decide what problem you're solving → Build the forwarding layer: OpenAI-compatible protocol → Key distribution + metering: every key can be capped, queried and stopped

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

  1. AI API Relay guide (5 steps): Decide what problem you're solving → Build the forwarding layer: OpenAI-compatible protocol → Key distribution + metering: every key can be capped, queried and stopped — A relay isn't reselling: is this for you, for a few people, or for sale?
  2. Step 2 · Build the forwarding layer: OpenAI-compatible protocol — A minimal Node + Express implementation, or an open-source gateway
  3. Step 3 · Key distribution + metering: every key can be capped, queried and stopped — A relay without metering is paying for someone else
  4. Step 4 · Access control and logging — Auth, rate limiting and redacted logs — all three
  5. Step 5 · Launch + observation + a monthly cost review — HTTPS, health checks, a usage dashboard, a monthly cost table

RSS Reader / Feed Site guide (4 steps): Pick sources and parse the feeds → Fetch on a schedule, land it, dedupe → Front end: list + filtering + read state

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

  1. RSS Reader / Feed Site guide (4 steps): Pick sources and parse the feeds → Fetch on a schedule, land it, dedupe → Front end: list + filtering + read state — Settle on 10–20 sources, then normalise them into one JSON
  2. Step 2 · Fetch on a schedule, land it, dedupe — Hourly crontab, dedupe by url, keep only the last N items
  3. Step 3 · Front end: list + filtering + read state — Filter by source and keyword; read state lives in localStorage
  4. Step 4 · Launch + indexing observation + long-term maintenance — The page needs to be findable, and the source list needs pruning

Backend-free Form Collection Site guide (4 steps): Choose the submission channel: form service vs cloud function → Write the form: fewer fields converts better → Notifications + spreadsheet + spam control

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

  1. Backend-free Form Collection Site guide (4 steps): Choose the submission channel: form service vs cloud function → Write the form: fewer fields converts better → Notifications + spreadsheet + spam control — Decide where the data goes first, then pick the least work
  2. Step 2 · Write the form: fewer fields converts better — Cap required fields at three; validate on the client with specific errors
  3. Step 3 · Notifications + spreadsheet + spam control — Notify a human on submit, keep the data exportable, block the junk
  4. Step 4 · Launch + conversion tracking + iteration — form_view → form_submit is the funnel; always split it by channel

Public Service Status Page guide (4 steps): Decide what to publish and how you define status → Data source: probe results into JSON → The page: current state + incident history + 90-day uptime

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

  1. Public Service Status Page guide (4 steps): Decide what to publish and how you define status → Data source: probe results into JSON → The page: current state + incident history + 90-day uptime — List your services, define operational / degraded / down
  2. Step 2 · Data source: probe results into JSON — Probe every minute, write status.json, the page only reads a file
  3. Step 3 · The page: current state + incident history + 90-day uptime — One screen answering: is it fine now, and did it break recently
  4. Step 4 · Launch + alerting + postmortems — Update the page during an incident, write the record afterwards

CDN + HTTPS Acceleration guide (4 steps): Turn on HTTPS: issue the certificate and force the redirect → Add the CDN: acceleration domain + origin config → Cache rules: what to cache, for how long, and how to purge

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

  1. CDN + HTTPS Acceleration guide (4 steps): Turn on HTTPS: issue the certificate and force the redirect → Add the CDN: acceleration domain + origin config → Cache rules: what to cache, for how long, and how to purge — Free certificate + auto-renewal + a site-wide redirect
  2. Step 2 · Add the CDN: acceleration domain + origin config — CNAME to the CDN, point the origin at your server, cache by directory first
  3. Step 3 · Cache rules: what to cache, for how long, and how to purge — Don't cache HTML; cache assets long, with versioned filenames
  4. Step 4 · Acceptance: speed, security headers, indexing unaffected — Compare before and after, and confirm crawlers still get through

Backup and Disaster Recovery guide (4 steps): Inventory what to back up and what you can afford to lose → Automate it: script + scheduled task → Run a restore drill (the most important step)

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

  1. Backup and Disaster Recovery guide (4 steps): Inventory what to back up and what you can afford to lose → Automate it: script + scheduled task → Run a restore drill (the most important step) — Grade everything first: recoverable in an hour / a day / a week
  2. Step 2 · Automate it: script + scheduled task — Archive → ship off-site → log → alert on failure
  3. Step 3 · Run a restore drill (the most important step) — Actually restore onto another machine; time it and write down what broke
  4. Step 4 · Monitoring + cost + periodic cleanup — Backups need watching too, and storage costs need bounding

AI Content Production Site guide (5 steps): Choose topics: things people search for that you can actually answer → Generate: give the AI enough context and structure → Human review: the only gate that decides quality

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

  1. AI Content Production Site guide (5 steps): Choose topics: things people search for that you can actually answer → Generate: give the AI enough context and structure → Human review: the only gate that decides quality — Keywords come from questions you've been asked and from search suggestions
  2. Step 2 · Generate: give the AI enough context and structure — State the role, the reader, the structure and what's forbidden
  3. Step 3 · Human review: the only gate that decides quality — Check the facts, add your own experience, delete the filler
  4. Step 4 · Publish: structure, internal links, crawler-friendly — One topic per page, static and fetchable, linked to each other
  5. Step 5 · Indexing and conversion observation: let data pick the next topic — Keep a watchlist, watch indexing and conversion, cut what isn't working

Backend-free Comments and Community guide (4 steps): Pick an approach: Giscus / Waline / Disqus → Integration: configure Giscus and drop it into the page → Comments are content: let UGC be seen too

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

  1. Backend-free Comments and Community guide (4 steps): Pick an approach: Giscus / Waline / Disqus → Integration: configure Giscus and drop it into the page → Comments are content: let UGC be seen too — Decide by whether you'll run a backend, and who your readers are
  2. Step 2 · Integration: configure Giscus and drop it into the page — Enable Discussions, install the app, paste the parameters
  3. Step 3 · Comments are content: let UGC be seen too — Show comments without letting them steal weight from the main content
  4. Step 4 · Observation: what did comments actually bring? — Track the effect on dwell time and return visits, not the comment count