social-media-engagement-website — HTML 后台模板

SHA-256: 25c92ffd0cad8865ca51c3b40788a65b16e293da5cfdc9b669dcdfe3339012e0

2026-10-15T16:43:55.060Z

# Social Media Engagement Website

One place to see engagement across Instagram and YouTube — daily figures on a
dashboard — plus a generator for draft post captions and descriptions to copy
out by hand.

Read-only by design. Nothing is ever published to either platform from here.

## Live

https://social-media-engagement-website.vercel.app

Sample data throughout. See **Status** above.

## Status: design template only

This repo currently contains **the frontend template and nothing else**. Be
clear about what that means:

- Every number on the dashboard is invented and hard-coded into the HTML.
- The chart is a static SVG with pre-computed coordinates.
- The drafts are canned strings. Nothing is generated.
- Date ranges, the account filter and the length slider do nothing but show a
  toast saying so.
- There is no backend, no database, no API client and no scheduled job.

Two things genuinely work: the tone and platform switches on the drafts page,
and copy-to-clipboard.

## Running it

No build step, no dependencies, no package manager.

```sh
./serve.sh          # http://localhost:8090
./serve.sh 3000     # or pick your own port
```

That is just `python3 -m http.server` pointed at `site/`. Any static file
server will do.

## Layout

```
site/index.html         landing page
site/dashboard.html     stat tiles, 14-day chart, platform split, recent posts
site/drafts.html        tone and platform switcher over canned drafts
site/assets/site.css    design tokens and components
site/assets/app.js      demo behaviour only; talks to nothing
serve.sh                local static server
vercel.json             serves site/ as the output directory
```

## Deploying

Import the repo on Vercel. Framework preset **Other**; no build command. The
`vercel.json` in the root points the output at `site/`, so leave Root Directory
empty.

## Deliberately absent

- **No framework.** The stack is an open question, and scaffolding Next or Vite
  would settle it by accident. Static files are cheap to throw away.
- **No credentials, ever.** When platform access arrives it will read from
  environment variables. No token, key or secret belongs in this repo.

## Design

The visual direction is one of three that were explored — high-contrast paper
and ink, 2px rules with hard offset shadows, Bricolage Grotesque over Archivo.
Colours for the two platforms were checked for colour-blind separation rather
than picked by eye.

## Working notes

Day-to-day context — current state, the decision log, session logs — is kept
alongside this repo but outside version control, so the public history stays
code-only.

## Licence

MIT — see [LICENSE](LICENSE). Use it, change it, ship it, sell it; no
attribution required beyond keeping the copyright notice. It comes with no
warranty, which matters here more than usual: this is a template with invented
data, not a working product.