LIVE
PORTFOLIO / CASE STUDY

Turning a portfolio from a profile page into a story about how someone thinks and builds

Mohamed Hassan Nehlawi’s portfolio does not begin with a technology list or end with a long résumé. The experience is built to answer three questions quickly: who he is, what he built, and how he works when a problem becomes bigger than one screen.

Mohamed Hassan Nehlawi portfolio homepage
TYPE
Personal portfolio and web experience
SCOPE
Identity · Content · Frontend · Responsive
FOCUS
Full-stack · Product · Data
STATUS
Live / Netlify
01 / THE QUESTION

The problem was not how to put a résumé on the internet

The real question was how someone meeting Mohamed for the first time could understand, within seconds, what he builds, where his experience sits, and what makes his way of working different. That meant treating the portfolio as a content product with an opening, proof, process, context, and a deliberate ending.

02 / THE STRUCTURE

The story is built in five layers, and every layer answers one question

01

Identity

Who are you and what do you build?

02

Proof

Which projects make the claims credible?

03

Process

How do you work when the problem becomes complex?

04

Context

Which experiences shaped that approach?

05

Conversation

What should the visitor do next?

03 / THE STORY

The interface tells that journey as the visitor scrolls

One browser object stays in place while the screen, narrative, and light-dark tone change chapter by chapter. Motion supports the story order instead of becoming a separate performance.

01 / FIRST IMPRESSION

Instead of a CV on the web, the first screen explains how the work is built

The opening does not try to say everything. It establishes the person, the scope across interface, backend, and data, then gives one direct path into the work.

Personal identity · Full-stack · Product · Data
Portfolio homepage hero
04 / THE CRAFT

Small decisions make the portfolio feel made for a person rather than generated from a template

Headline scale, spacing, browser framing, theme transitions, concise copy, and the dominance of email at the end are all intentional. Even the experience section does more than list names and dates: every chapter explains what it changed in the way the work is approached.

  • Clear visual hierarchy
  • Responsive without losing the story
  • RTL/LTR support
  • Reduced Motion support
  • Dimensioned media to reduce CLS
  • One direct final CTA
Portfolio how-I-work section
05 / THE RESULT

The site never needs to say “I am good” — the work is allowed to explain that

Visitors see the product, understand the thinking, get the context, and arrive at a direct contact point. That is the difference between a portfolio that stores information and one that builds trust.