The owner edits
Spreadsheet
Everything the owner writes, job openings included. An importer checks every row with zod before it can ship.
Client work4 May 2026 to 30 Aug 2026Web
A heritage beef noodle restaurant, online in six languages. The owner keeps it current from a spreadsheet, the till system owns the menu, and every build writes 130 static pages.
A departure board flips the words beef noodle soup through the site's six languages.
Site locales
One noodle, three spellings: 面麵麺. The Chinese and Japanese boards share 牛肉 and flip only the last character.
No runtime CMS. Production is static files built from git.
The owner keeps the site current without calling me. A spreadsheet holds what the owner writes and the till system holds the menu, prices and photos, while git keeps the code and design. Every build turns them into static pages in all six languages.
The owner edits
Everything the owner writes, job openings included. An importer checks every row with zod before it can ship.
Source of truth
A headless browser reads the till's public ordering page. The first full refresh brought in 54 items and 49 HD photos.
Every build
A bad row fails validation instead of shipping.
Output
130static pages per build, in six languages
Review
A GitHub Action opens a labelled pull request for every content change, so each one is a reviewable diff.
Job openings
The owner posts in a Careers tab and opens a bookmarked build hook. The change is live about 2 minutes later.
Branches
Prices are rows keyed by item and branch, so refreshing one branch never touches another's.
Client work4 May 2026 to 30 Aug 2026
A statically generated Next.js site in six languages for a heritage beef noodle restaurant, with a menu pulled from the restaurant's till system and content the owner edits in a spreadsheet.
Built with an AI pair programmer, then reviewed and tested by me. The tests and decision records below are how I hold that work to account.
A heritage beef noodle brand from Penang needed a real website in six languages, and in August 2026 it opened a second outlet in Kuala Lumpur. Three requirements shaped everything. The owner is not technical and had to keep the menu, prices and job openings current without calling me. Hosting had to cost nothing beyond the domain. And the site could make no claim the business cannot back up, which in Malaysia especially means halal wording without a certificate. It also had to look like this restaurant and nobody else.
A Next.js 16 App Router site in React 19 and TypeScript, generated entirely at build time: 16 page routes in six locales, 130 static pages per build as of June 2026. next-intl handles locale-prefixed routing with English slugs (/ms/menu) and hreflang. The English message file has 974 leaf keys, and a test makes sure every locale has all of them.
Content has three sources, each owning different facts: the restaurant's till system owns the menu, prices and photos, a Google Sheet owns what the owner writes, and git owns the code and design. Seven public forms run as server actions, with email through Resend and newsletters through MailerLite, and each starts with a honeypot and an in-memory per-IP limit of 5 requests per 60 seconds. Every route sends CSP, HSTS and the usual security headers. The site runs on Netlify's free tier, because Vercel's free tier forbids commercial use.
The visual system went through four reversals: a serif editorial look, a dark direction that was built and then reverted, a bold grotesk system from a design handoff, and finally a single typeface for readability. Because the token names stayed stable, each change cascaded through every page without rewrites. I built this with an AI pair programmer; every change went through tests and my review.
The trigger was a real bug: one price lived in two data files and drifted apart, and adding a single menu item touched seven files. A headless CMS would have fixed that at the cost of a monthly bill and another service to run. Instead, a build-time importer reads the Sheet's published CSV tabs, validates every row with zod, regenerates the typed data files, and a GitHub Action opens a labelled pull request. Production stays static files in git, a bad row fails validation instead of shipping, and every content change is a reviewable diff.
The owner posts openings in a Careers tab of the same Sheet, then opens a bookmarked build hook. A standalone importer runs before next build. If the Sheet is unset, unreachable or malformed, it warns, keeps the committed careers data and exits 0. A runtime fetch would have put Google on every request, and running the full content importer at build could have overwritten the till system's menu data. The change is live about 2 minutes after the hook, and the same data drives JobPosting structured data.
The first decision record required a "halal-friendly" badge with a certification-pending disclaimer. The client judged any halal wording misleading without a certificate, and I agreed: a disclaimer does not undo an implied claim. The wording came out of components, data, SEO metadata and all six locales, and the only dietary framing left is pork-free and lard-free. Bringing any of it back requires a new decision record.
Three production incidents came from values pasted into the hosting dashboard. A value pasted with quotes failed zod's email check, so every form answered "unavailable"; the loader now trims whitespace and strips wrapping quotes. The schema required all five per-purpose recipient addresses, so one typo disabled every form; they now fall back to one contact address. A WhatsApp number in local format with a leading zero passed a digits-only check but made a dead wa.me link on every page; the pattern now rejects a leading zero and names the expected format, so the build fails loudly. A separate guard stops a production build without SITE_URL, which would otherwise poison canonical URLs, hreflang and the sitemap. Each incident became a rule that fails at build time instead of in front of a customer.
When the Kuala Lumpur outlet opened, its till system prices had not been captured, and showing Penang prices under KL would have been wrong. A pricesPending flag drives an explicit note on the menu page that KL prices may differ, and because prices merge per branch, the later KL refresh will not touch Penang rows. The photo viewer is the native <dialog> element, which brings Escape handling, focus containment and a backdrop with no new dependency. Photos were re-encoded to strip EXIF and GPS data before publishing.
There are 35 Vitest tests in 8 files, counted in source: 30 test cases, plus one i18n parity test run against each of the five non-English locales. They cover the honeypot and rate limiter, the form schemas, the structured-data builders, the newsletter action and smoke renders. A task only counts as done when typecheck, lint and a full six-locale build pass and the pages have been checked at 360, 390 and 768 px.
One gap I know about: the agent instruction files drifted from the decision log. One still says the halal badge is mandatory, and another still cites Vercel. The append-only log stayed authoritative, but nothing tested the other files against it.
The site is live at teowkee.com in 6 languages. The menu comes from the till system, 54 items with 49 HD photos, and the owner publishes job openings without me. Hosting costs nothing beyond the domain. The project took 45 commits on main and 21 decision records between May and August 2026, and the Kuala Lumpur outlet went in as data rather than as a redesign.
What shipped, and when.
Started: six-language site for a heritage restaurant
Owner edits content in a spreadsheet, imported at build
Full redesign shipped
The till system becomes the source of truth for the menu
Structured data for search on every page
7 of the 21 decision records, 1 of them superseded and kept on the list. Open one to read its context and consequence.
Decision record ADR-013 from 6 May 2026. Status: accepted.
Decision record ADR-017 from 16 June 2026. Status: accepted.
Decision record ADR-019 from 20 June 2026. Status: accepted.
Decision record ADR-020 from 20 June 2026. Status: accepted.
Decision record ADR-021 from 21 June 2026. Status: accepted.
Sampled 16 Nov 2026, 02:51 UTC. Failures are shown as they were read.
Teowkee site status
Not sampled yet
Source: teowkee.com
Paste a job description. You get a verdict, the evidence that matches it with citations, and what the sources do not show.
Open to senior AI and software engineering roles: on site or hybrid in Sydney, or remote for Australian and US teams.
Email meBook 15 minCVTeowkee site status
200 in 228 ms
Answered with HTTP 200 after following any redirects.
Source: teowkee.com