Omar Chenine
Rank 09WebArchive

Freelance web projects

Client sites built to ship, not to demo.

Restaurant and dental clinic booking sites in Next.js, with a focus on mobile flow and form reliability.

Role
Design and build
Year
Pending
Case study
371 words
Demo
Not available
TypeScriptJavaScriptReactNext.jsTailwindREST API integration

Result: a restaurant site and dental clinic booking sites built in Next.js. Live URLs and screenshots are add public URLs or sanitized screenshots.

Problem

Small businesses need a mobile first site that makes one action easy: book, call, or order. The work is less about novelty and more about form reliability, fast pages, and a flow that survives a phone.

Data

Client requirements are add a short scope note per site. The stack per site is confirm Next.js, Tailwind, and any booking API. No patient or customer data is shown in screenshots.

Approach and why

  • Start with the mobile flow. The booking or contact action is the first screen, not a footer link.
  • Use Next.js with a small component surface and typed props.
  • Keep forms accessible: labels, error text, and a clear success state.
  • Integrate the booking or contact endpoint with a loading and failure state.
  • Check the page on a slow connection and a small viewport.

The goal is a site a client can run, not a design award entry.

Results

SiteStackStatus
Restaurantconfirm stackadd live URL
Dental clinic bookingconfirm stackadd live URL

Evaluation

  • Performance: Lighthouse or Core Web Vitals evidence is add if available.
  • Accessibility: keyboard path through the booking form, labels, and error states.
  • Form reliability: success, validation error, network error, and spam protection.
  • Privacy: no personal data in screenshots or public repositories.

A reviewer should challenge a web project without a URL or a screenshot. They should also ask what was built by the developer and what was client provided.

Limitations

The sites are client work, so public repo access may not be possible. The live URLs are pending. The case study is in the archive because the AI work is the primary story.

Next steps

Add live URLs or sanitized screenshots, a one line scope per site, and performance evidence. Add a short note on the booking API and the failure handling.

Links

  • Live sites: add public URLs
  • Repo: add links where the client allows

Headline metrics

Live sites
Pending

Add public URLs or screenshots

Case study length

371 / 500