Skip to contentSkip to contact
Dennis KhorTeowkee
Recruiter mode

Client work4 May 2026 to 30 Aug 2026Web

Teowkee

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.

  • English: Beef noodle soup
  • Bahasa Malaysia: Mi sup daging
  • 简体中文: 牛肉面
  • 繁體中文: 牛肉麵
  • 日本語: 牛肉麺
  • Bahasa Indonesia: Mi sup daging sapi

Site locales

How the menu gets onto the site

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.

Two sources, one build

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

Spreadsheet

Everything the owner writes, job openings included. An importer checks every row with zod before it can ship.

Source of truth

Till system

  • Menu
  • Prices
  • Photos

A headless browser reads the till's public ordering page. The first full refresh brought in 54 items and 49 HD photos.

Every build

Build

  1. Validate every row
  2. Regenerate typed data
  3. Render six languages

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

Teowkee

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.

Kind
Client work
Platforms
Web
Period
4 May 2026 to 30 Aug 2026
Stack
  • Next.js 16
  • React 19
  • next-intl
  • Tailwind CSS 4
  • zod
  • Vitest
  • Google Sheets
  • GitHub Actions
  • Languages6
  • Static pages130per build
  • Decision records21

The problem

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.

Constraints

  • No runtime CMS. Production is static files built from git.
  • Every user-facing string ships in all six locales: English, Bahasa Malaysia, Simplified Chinese, Traditional Chinese, Japanese and Bahasa Indonesia.
  • No halal wording, no reservations and no in-house ordering. Ordering deep-links to the delivery platforms for each branch.
  • No new third-party service or runtime dependency without a decision record.
  • Mobile-first, checked at 360, 390 and 768 px.

What I built

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.

Decisions that mattered

A Google Sheet as the CMS, typed TypeScript as the artifact

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 till system owns the menu, even over better photos

Menu cards started with 120 px placeholders, and a studio shoot had delivered about 193 unlabelled originals. I wrote a matcher that scores every pair with perceptual hashes (twice the pHash distance plus the dHash distance), auto-stages confident matches, and sends the rest to an HTML review grid for a person to pick. By June 2026, 19 of 47 dishes were on studio photos.

Then the till system became the source of truth for the menu, and keeping studio photos would have meant a second place to maintain every dish. On 20 Jun 2026 the till system refresh replaced all 19 with its own HD images, 49 in total. I traded some photo quality and control for one source of truth and no double entry. The matcher was good work that the product outgrew. Prices are rows keyed by item and branch, so refreshing one branch never touches another's.

A careers importer that cannot break a deploy

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.

No halal wording at all

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.

Hard problems

Reading a menu from a page with no API

The till system's public ordering page has no JSON API, only server-rendered HTML. A script renders the page in headless Chrome over the Chrome DevTools Protocol and saves the DOM and network responses, and a separate extractor reads the menu from them. Listing thumbnails were about 3 KB, so the downloader derives each full-size original's URL from its thumbnail path and re-fetches anything under an HD size threshold. A verify step separates retryable failures, where the URL exists but the file is missing, from gaps on the till system's side, and the orchestrator loops for up to 3 passes. The first full refresh produced 54 menu items and 49 HD photos between 35 KB and 496 KB.

Environment variables that failed quietly

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.

A second outlet without faking its prices

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.

How it is tested

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.

Results

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 I would do next

  • Build the proposed menu-overrides Sheet, so the owner can hide, feature or badge dishes without touching till system data.
  • Capture the KL prices from the till system and retire the pending note.
  • Add a documentation drift test, like the one I later wrote for Rossi Italian, so agent instruction files cannot contradict the decision log.
  • Move to a nonce-based CSP and a shared rate-limit store, since the in-memory limiter is best-effort on serverless.

Milestones

What shipped, and when.

  1. Started: six-language site for a heritage restaurant

  2. Owner edits content in a spreadsheet, imported at build

  3. Full redesign shipped

  4. The till system becomes the source of truth for the menu

  5. Structured data for search on every page

Decisions

7 of the 21 decision records, 1 of them superseded and kept on the list. Open one to read its context and consequence.

  1. Accepted

    Content authored in a Google Sheet, imported at build

    A build-time importer validates the Sheet's published CSV with zod, regenerates typed data files and opens a labelled pull request.
    Context
    A price drifted because two data files owned the same fact, and adding one menu item touched seven files.
    Consequence
    Production stays static files in git, and every content change is a reviewable diff with no CMS to run.

    Decision record ADR-013 from 6 May 2026. Status: accepted.

  2. Superseded

    Match dish photos to the studio shoot by perceptual hash

    Score every pair with pHash and dHash, auto-stage confident matches and send the rest to a human review grid.
    Context
    Menu cards had small placeholders, and the studio shoot delivered about 193 unlabelled originals.
    Consequence
    19 of 47 dishes moved to studio photos. All 19 were replaced when the till system became the source of truth for photos.
  3. Accepted

    Security headers and best-effort anti-spam

    Send CSP, HSTS and related headers on every route, and start every public server action with a honeypot and an in-memory per-IP limit.
    Context
    Seven public forms needed spam protection, and the client preferred not to add an account for a shared rate-limit store.
    Consequence
    No new service is involved. The CSP allows unsafe-inline and the limiter is best-effort on serverless, both written down with an upgrade path.

    Decision record ADR-017 from 16 June 2026. Status: accepted.

  4. Accepted

    No halal wording, only pork-free and lard-free

    Remove all halal wording from components, data, SEO metadata and all six locales.
    Context
    The business holds no halal certificate, and a certification-pending disclaimer still implies a claim.
    Consequence
    It replaces the earlier badge record, and bringing any halal wording back requires a new decision record.

    Decision record ADR-019 from 20 June 2026. Status: accepted.

  5. Accepted

    Host on Netlify's free tier

    Move to Netlify's free tier, remove the Vercel analytics packages and make the production guard recognise either host.
    Context
    Vercel's free tier forbids commercial use, and Cloudflare Pages would need an adapter for Next 16 server actions.
    Consequence
    Hosting costs nothing beyond the domain, and the original Vercel record is superseded.

    Decision record ADR-020 from 20 June 2026. Status: accepted.

  6. Accepted

    The till system is the source of truth for menu, prices and photos

    Read the till system's ordering page, which has no API, in a headless browser, regenerate typed menu data, and store prices as rows keyed by item and branch.
    Context
    Typing prices into the site as well as the till system invites drift, and a second outlet would need its own prices.
    Consequence
    54 items and 49 HD photos come from the till system, and a refresh for one branch never touches another branch's rows.
  7. Accepted

    Careers managed in the Sheet, imported at build

    A standalone importer runs before the build and keeps the committed careers data, exiting 0, when the Sheet is missing or malformed.
    Context
    The owner needed to post job openings without a developer, and a failed import must never block a deploy.
    Consequence
    The owner publishes from a bookmarked build hook in about 2 minutes, and the import cannot overwrite menu data.

    Decision record ADR-021 from 21 June 2026. Status: accepted.

Live status

Sampled 16 Nov 2026, 02:51 UTC. Failures are shown as they were read.

  • Sampling

    Teowkee site status

    Not sampled yet

    Source: teowkee.com

Ask about fit

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 minCV