nemo curly: a static shop its owner edits from the browser
A small shop sells curly-hair products through Instagram, and its prices change often. The owner wanted to change prices and add products herself, and the site is fully static: no server, no database, no CMS. I built it unpaid.
The site
nemo-curly.5em.workers.dev is an Arabic, right-to-left catalog for two brands, Skala and Cuella, plus a quiz that suggests a full routine and a three-week care schedule based on hair porosity. Orders go through WhatsApp or a phone call, so there’s no checkout.
The fonts are self-hosted, because some CDNs aren’t reliable from Syria. Apart from a small menu script, the shop’s JavaScript is the quiz, as a single Preact island. Every product description and every piece of hair-care advice is the owner’s text, verbatim. Anything she hasn’t written stays empty.
The panel
She opens /admin, changes a price, a description or a photo, or adds a product, and presses حفظ (save). About 30 seconds later it’s on the site.
There’s no server here either. The panel is a static page that reads its files through the GitHub API: catalog.json, the copy file, and the photos of products and packages, which are bundles of products sold together. On save it writes every change as one commit through the Git Data API: blobs, then a tree, then a commit, then the ref update. A new product’s row, copy and photo land in one commit, so the site builds once instead of three times.
The ref update isn’t forced. If anything lands on the branch while she’s typing, GitHub rejects the update, and the panel loads the latest version and asks her to redo the edit, so her save never silently overwrites another change.
Auth is a fine-grained token she pastes once. It stays in localStorage on her device only, scoped to Contents: Read and write on this one repository. The token is issued from my account, so her edits carry my name in the git log.
Why she can’t break the shop
Three layers:
- The form validates every field before saving and disables حفظ while anything is wrong.
- The build runs the same rules from
catalog-rules.tsagain and fails with a message naming the product and the field. - If the build fails, Cloudflare keeps serving the previous deploy.
So the worst case is an edit that doesn’t show up.
Some things the panel doesn’t edit, on purpose: the English copy, the routine text, the quiz questions, the delivery lines and the design.
What broke
Adding products from the panel shipped on 1 October. The same day, at 17:29, I fixed the tests that pinned the product counts to the launch catalog: 28 masks and 14 Cuella products. Any product she added would have failed them.
At 17:52 she added her first product on her own, a smaller size of the Skala gel, and CI failed. It failed again on her second, third and fourth saves. I found out from GitHub’s CI failure email. The site itself kept updating, because Cloudflare’s build doesn’t run the tests. But a different test pinned the quiz result’s add-ons to exactly three products by name, and every non-mask product she adds goes into that list.
The fix landed at 19:10. That test now runs against the launch catalog, and checks that every non-mask product she added shows up after the three. Four minutes later I went through every test that reads her data and turned what she can cause through normal use into warnings: a product with no description, or with no photo. Failures are kept for what actually breaks the site: types, the catalog rules, and the copy parser changing her words.
She saved nine more times that night: two products, six packages and a rename. CI passed on every save after the fix, ten in a row through the next afternoon.
Known limits
- A new mask reaches the quiz results by itself. Shampoos, conditioners and leave-ins are mapped by slug in the code, so a new one needs a code change.
- Photos she uploads are resized, and their backgrounds aren’t removed.
- Her edits carry my name until she has her own GitHub account.
- The address stays on
workers.dev. That’s her choice.
What I’d change
I’d remove the slug mappings for shampoo, conditioner and leave-in, so a new one joins the quiz without touching the code. And I’d add background removal to the panel itself.
How it shipped
I built it between August and October 2026. Astro 7 with TypeScript and Tailwind 4, deployed as static assets on Cloudflare Workers. The repo is private.