EN | 中文
Home page review · Cloudflare Pages deploy

Get the review live in 5 minutes.

The whole review (hub, three variants, feedback form) is a single folder of static files — no build step, no server. Drop it on Cloudflare Pages and you've got a sharable URL. Anyone on the team can do this. No git account needed.

01 Get the files

Download this entire project as a zip from the chat (the "Present for download" link), or pull from the repo if it's been committed. You only need these files:

Review Hub.html ← the landing page Variant A - Cinematic.html Variant B - Editorial.html Variant C - Triage.html Feedback Questions.html Deploy Guide.html ← this file (optional) styles.css tweaks-panel.jsx a-app.jsx a-hero-canvas.jsx b-app.jsx c-app.jsx thumbs/ a-thumb.png b-thumb.png c-thumb.png

Put them all in one folder on your desktop. Let's call it silk-home-review/. Make sure Review Hub.html is at the top level — that's the page reviewers land on.

02 Create a new Cloudflare Pages project

  1. Go to dash.cloudflare.com, sign in.
  2. In the left nav, click Workers & Pages.
  3. Click Create → choose the Pages tab → click Upload assets.
  4. Project name: silk-home-review (or whatever you want — this becomes the subdomain).
  5. Click Create project.
Why "Upload assets" not "Connect to Git"

We don't need a git repo for a review deploy. Upload assets takes a folder, publishes it, and you're done. When you make changes, drop the new folder over the top.

03 Upload the folder

  1. Drag the entire silk-home-review/ folder onto the upload zone.
  2. Cloudflare validates the files (takes <30 seconds) and shows a green checkmark.
  3. Click Deploy site.
  4. Wait for the build to complete. There's no actual build — Cloudflare just publishes the files. ~60 seconds.

You'll get a URL like https://silk-home-review.pages.dev. That's the live review.

04 Share with the team

Send the team three things in your message (Slack / WeChat / email):

The feedback form autosaves to each reviewer's browser. When they're done, they hit "Copy as text", paste into whatever response thread you set up (Slack DM, shared doc, email reply).

05 Optional: nicer URL

If you want it on the real domain — e.g. review.project-silk.com — instead of pages.dev:

  1. Open the project in Cloudflare Pages → Custom domains tab.
  2. Click Set up a custom domain.
  3. Enter review.project-silk.com.
  4. If project-silk.com is on Cloudflare DNS already, it's done. If DNS is at GoDaddy, Cloudflare gives you a CNAME to add at GoDaddy. Add it. Wait 5 minutes.

06 Updating the review

When you want to push a fix or a new variant:

  1. Make the change in the project folder.
  2. Go back to Cloudflare Pages → your project → Create deployment → drag the folder again.
  3. Old URL works immediately with the new content. No DNS, no cache hassle.

07 Troubleshooting

If…Then…
Variant pages show blank Make sure all the .jsx files (a-app.jsx, b-app.jsx, c-app.jsx, hero-canvas.jsx, tweaks-panel.jsx) and styles.css are at the root of the upload folder, alongside the HTML files.
Thumbnails missing on hub Confirm thumbs/ folder uploaded with the three PNGs inside.
Fonts look wrong Prototype uses Google Fonts CDN. If you preview from inside China without VPN, fonts may not load. Production site self-hosts these (separate decision).
Want password protection Cloudflare Access → set up an Access policy for the project → require email confirmation. Free tier covers up to 50 users.

08 When the review is done

Once you've synthesized feedback and picked a direction:

Either way, the next round of design work happens in the same Cowork project. Each new variant gets bundled the same way and re-uploaded.