Skip to main content
Mohamed Noor
Back to work
Figma to Production

mohamedhnoor.com Production Next.js Website

This site. A production website built from a design reference with a focus on accessibility, responsive behaviour and performance, with the parts of the reference that would have been dishonest deliberately removed.

Role
Sole developer
Period
2026
Stack
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • shadcn/ui
  • Motion
  • Vitest
This site's home page in its dark theme: the headline Websites and Web Applications Built for Your Business, with Start a Project and View My Work buttons, beside a code-editor card listing the four services and the stack, above a row of technology chips.

Measured

  • 100/100

    Lighthouse accessibility

    Mobile preset against a production build, scored on the home page, a case study and the contact form.

  • 0

    axe violations

    Every route in both themes, including the mobile menu open and the contact form showing its errors.

  • 88 ms

    Largest Contentful Paint

    The home page in a real browser at mobile viewport, against a production build on 5 October 2026, with cumulative layout shift at 0. Case studies and the contact page measured 76 ms.

Overview

The website you are reading: a portfolio for a freelance developer, built from a design reference into a production Next.js site. It is also a work sample, so its own accessibility and performance numbers are published with the measurement behind them.

The Problem

A developer with no reviews has to win work on evidence alone, and most portfolios actively work against that. They lead with a generic tagline, rate their own skills with percentage bars, and show screenshots with no account of what was solved. A client cannot tell a capable developer from a template.

The reference design I started from had that problem built in. It carried a client-count statistic and a satisfaction score, neither of which could be true for an account with no completed jobs, and skill bars that are self-assigned by definition.

The Solution

I matched the reference where it was good and departed from it where it would have made the site lie. The palette, the hero composition, the eyebrow-and-heading rhythm and the card language were kept. The invented statistics and the skill percentages came out and were replaced with numbers that carry the measurement behind them.

Because accessibility and performance are services this site sells, they were treated as build gates rather than aspirations.

Key Features

A site a client can read on a phone in a minute, or study in depth before an enquiry.

  • A home page that summarises every section, with a full page behind each
  • Case studies with the measurement behind every number
  • A project index filterable by service and technology
  • A print-optimised resume
  • A contact form with the same validation in the browser and on the server, delivered by email
  • Light and dark themes, generated social images and structured data

Architecture

Next.js App Router with server components throughout. Every public route is statically generated and the public site's only server work is the contact form's Server Action, which re-validates with the same Zod schema the browser used rather than trusting what arrived.

All copy lives in typed content modules with invariants checked at module scope, so a malformed entry fails the build instead of rendering an empty section. Client components are limited to the islands that genuinely need them: the theme toggle, mobile navigation, contact form, project filter, and the marquee's pause control.

  • Static generation for every public route, verified in the build output
  • Security headers including a Content Security Policy, served without middleware so routes stay static
  • Social images generated at build time from the content layer

Engineering Challenges

Most of the difficulty was in keeping promises the site makes about itself.

  • Contrast as a test: every theme token is converted from oklch to sRGB, and the test suite fails if a pair drops below its WCAG threshold
  • A Content Security Policy without middleware, because middleware would have made every route dynamic
  • Motion that never delays the largest contentful paint, and collapses entirely under reduced motion
  • A deploy gate that refuses a production build while any project is still seeded example content

Testing

336 Vitest tests over the logic that can be wrong: validation, content invariants, contrast, metadata and structured data. UI is verified in a real browser instead, with axe run on every route in both themes.

Technology

A deliberately small stack, so the site stays fast and the next developer can read it.

  • Next.js with the App Router, React 19 and the React Compiler
  • TypeScript in strict mode
  • Tailwind CSS v4 and shadcn/ui on Radix
  • Motion, code split and reduced-motion aware
  • react-hook-form, Zod and Resend for the contact form
  • Vitest

My Role

Role: Sole developer. I adapted the design reference, and built the frontend, the content layer, the contact form and its server action, the accessibility and performance work, and the tests.

Outcome

Lighthouse accessibility, best practices and SEO all score 100 on the mobile preset, axe reports no violations on any route in either theme, and layout shift is zero.

Performance measured 88 to 95 on the same preset: a case study reached the 95 target, and the home page and contact form came in below it. The cause is recorded rather than glossed: simulated Slow 4G turns the critical path into seconds of render delay, while the same page reaches its largest contentful paint in under 100 ms in a real browser. Reporting only the flattering half of that would undercut the point of the site.

Need something like this built?

Tell me what you are building. You can send a brief, a Figma file or a short description, and you will get a reply within one business day with a practical way to approach it.