Skip to content

Custom ordering layer for a Los Angeles restaurant

Yang's Kitchen

A custom ordering layer on top of Squarespace for a Los Angeles restaurant: hand-written CSS and JavaScript that bend the platform into a working menu and pickup flow.

Year
2019
Role
Front-end development
Category
Custom ordering layer for a Los Angeles restaurant
Yang's Kitchen: Yang's Kitchen: Custom ordering layer for a Los Angeles restaurant

The challenge

A Los Angeles restaurant had committed to Squarespace before finding that the platform could not handle the menu and pickup ordering it needed. Migrating was off the table, so the platform was a fixed constraint.

The approach

A custom CSS and JavaScript layer on top of Squarespace that turns the platform into a real ordering experience without abandoning it.

The outcome

A working ordering flow on Squarespace and a menu layout consistent with the brand, without a pile of third-party plugins.

Under the hood

Field
Restaurant · Los Angeles
Type
Custom ordering layer on Squarespace
Team
front-end developer

01

The real problem

The client had already paid for and learned Squarespace. Telling them to migrate was the easy technical answer and the wrong business answer — it would have meant abandoning their content, retraining their staff, and rebuilding the visual identity that was already shipped. The brief: make the platform do what it cannot natively do, by carefully extending it.

02

Who did what

Custom CSS + JavaScript layer on top of Squarespace. Client owned the platform decision and the content; we wrote the custom code that made the chosen platform actually work for their use case.

Front-end developer
Custom CSS injected via Squarespace code blocks. Custom JavaScript for the menu + pickup-flow widgets.
UX problem-solver
Worked around Squarespace constraints (limited form fields, no native ordering, no payment hooks) by layering on top.
Analytics integrator
GA tracking on the custom ordering flow so the restaurant could see actual conversion data.

03

Architecture

01 — Platform

Squarespace hosted

  • Squarespace

    Platform-hosted CMS

    Owned by client; cannot be modified at the server level

02 — Custom layer

Custom CSS + JS layer (this is the work)

  • Injected CSS

    Code blocks

    Brand-consistent menu + ordering UI

  • Injected JS

    Vanilla, no framework

    Cart state, menu rendering, GA events

  • Form-block bridge

    Squarespace native

    Cart submits via hidden Form Block — works within ToS

04

Challenges

  1. 01

    Squarespace exposes limited customisation hooks — every workaround had to use documented injection points only.

  2. 02

    Custom ordering flow that integrates with their existing payment processor without violating Squarespace ToS.

  3. 03

    Mobile-first menu layout within Squarespace block constraints.

05

Hard problems

  • Working within platform limits

    No backend code access; all logic lives in CSS + injected JS. State held in localStorage; cart submission routes to a Squarespace Form Block under the hood.

  • Brand-consistent menu without Squarespace blocks

    Squarespace menu blocks are limited. Built a custom JSON-driven menu rendered by injected JS that respects brand spacing + typography.

06

Why these technologies

  • Work with Squarespace, not against it

    • Client investment in the platform was non-trivial. Migration cost would have exceeded the value of the new flow.
    • Squarespace ToS allows custom CSS + JS via documented injection points — the bridge stays inside the rules.
  • Vanilla JS over framework

    • Injected scripts compete with Squarespace's own framework. A second framework would double load weight.
    • Vanilla code is auditable in a single file — easy for the next maintainer (likely Squarespace itself).

07

What I learned

  1. 01

    The right technical answer is sometimes "respect the platform the client chose, and make it work" — not "rewrite on the stack you prefer."

  2. 02

    Early-career lesson in scoping engineering decisions to the actual business constraints, not to engineer preferences.

Stack

  • Squarespace
  • CSS
  • JavaScript

Questions about Yang's Kitchen

Who built Yang's Kitchen?

Yang's Kitchen was delivered by Ali Haitham Yosef, founder of a software company in Damascus that carries his name. His role on the project: Front-end development.

What is Yang's Kitchen?

A custom ordering layer on top of Squarespace for a Los Angeles restaurant: hand-written CSS and JavaScript that bend the platform into a working menu and pickup flow.

What technology does Yang's Kitchen use?

Squarespace, CSS, JavaScript.

When was Yang's Kitchen built?

It was built during 2019.

Can you build a system like Yang's Kitchen for my business?

Yes. The company builds ERP systems, point-of-sale systems, mobile apps and websites for clients in Syria, Lebanon, Jordan, Iraq, Turkey and the Gulf states, working remotely. Contact: info@aliyosef.online.