Restaurant Operations Demo

The problem

A kitchen team needs one clear view of incoming work, its current state, and the load at each stage.

Role and contribution

Designed and built as a portfolio demonstration of frontend, API, database, validation, and container delivery skills.

The solution

A Next.js interface uses Sanity as its structured content backend, keeping operational content editable and presentation concerns separate.

Technical decisions

• Use three explicit states instead of a configurable workflow.
• Model structured content in Sanity.
• Keep content queries separate from presentation components.

Challenges

• Designing a clear content model.
• Keeping loading and error states useful.
• Maintaining consistent structured content across views.

What I learned

A narrow vertical slice can demonstrate architecture more honestly than a wide but simulated product.