← Back to crafts

Case study

How I built this portfolio

The craft behind this site, one detail at a time: the thinking, the design system and the build.

How I built

this portfolio

A case study in seventeen details

Case study

Contents

A case study in seventeen details

How I built
this portfolio

The craft behind this site, one detail at a time: the thinking, the design system and the build.

Sujoy Kr. Haldar

click a page, or drag it, to turn it

How I built this portfolio

01. Overview

A portfolio is most convincing when it is the work, not a description of it.
Fig. 1. The brief, ticked off
2

Detail 01 · Overview

The brief

Who the site is for, what it has to prove, and the stack and workflow chosen for it.

Before a line was drawn: who this site is for and what it has to prove to them. Three readers, the one hiring given the shortest path; three things to show rather than list; and a small stack, used all the way.

Inside

  1. 01Three readers, one site
  2. 02Three things, shown, not listed
  3. 03The rules it’s built on
  4. 04A small stack, used all the way
Open the detail →
3

How I built this portfolio

02. UX

Decide what the first seconds must say, before deciding how anything moves.
Fig. 2. Ten seconds on the clock
4

Detail 02 · UX

The first ten seconds

What a visitor should feel and do first, the intro's trade-off between delight and time, and the depth the page gains as you scroll.

A portfolio gets about ten seconds. Here they go to who, what, a person and where next, in that order, all started by one flag. Then the page gains depth as you scroll, and the intro plays once a visit, never in the way.

Inside

  1. 01The first ten seconds, frame by frame
  2. 02Who, what, a person, where next
  3. 03Four layers, four speeds
  4. 04Delight against time
Open the detail →
5

How I built this portfolio

03. Design system

Show the system with the real parts, and it can never drift from the site.
Fig. 3. The real parts, laid out
6

Detail 03 · Design system

The design system

Every token, typeface, pencil mark, spring, sound and component on this site, set out the way a Figma file would, but live: each one is the real thing, read from the code.

No pictures of the parts: the parts themselves. Thirteen boards, from the page’s colour tokens to the three ways it can move, each one live, so a change in the code shows here the moment it’s made. The next two details give the reasons.

Inside

  1. 01A Figma file, but live
  2. 02Seven tokens, four more for what’s drawn
  3. 03Springs by job, curves for sequences
  4. 04The parts, live
  5. 05On, off and calm
Open the detail →
7

How I built this portfolio

04. Design system

Keep the accent rare: once everything is highlighted, nothing is.
Fig. 4. One pencil, one ember
8

Detail 04 · Design system

The pencil language

One system for the whole site: tokens and the ember rule, four typefaces with four jobs, and pencil instead of boxes.

The whole site is drawn with one pencil and one ember: seven colour tokens and a rule for the accent, four typefaces with four jobs, and lines drawn by hand instead of boxes, their wobble seeded so a sketch is the same every visit.

Inside

  1. 01Seven tokens and one rule
  2. 02Four typefaces, four jobs
  3. 03Lines drawn by hand
  4. 04A box is four lines
Open the detail →
9

How I built this portfolio

05. Design system

Name springs by their job, and picking one becomes a decision, not more tuning.
Fig. 5. A spring with some give
10

Detail 05 · Design system

How things move

The system's other half: 26 springs sorted into five named for their job, controls that answer alike, and nothing that pops.

The system’s other half is motion. An audit found twenty-six springs and seventeen settings; sorted by what each one does, they came down to five, named for their job. Every control answers your hand alike, and nothing pops.

Inside

  1. 01Twenty-six springs, seventeen settings
  2. 02Five springs, named for their job
  3. 03Three controls, one hand
  4. 04In and out, never on and off
Open the detail →
11

How I built this portfolio

06. Signature

Outlines are shapes, not strokes: to make a font write, uncover the ink.
Fig. 6. Written while you watch
12

Detail 06 · Signature

A signature written by hand

Handwriting generated from a font, the pen that writes it, how it flies to the navbar and becomes a logo that rewrites itself for each page.

The name on the home page writes itself. A handwriting font becomes paths, a moving pen uncovers the ink at the pace of a hand, and the signature flies to the navbar, where it becomes a logo that rewrites itself for each section.

Inside

  1. 01Turning a font into paths
  2. 02Ink, uncovered by a moving pen
  3. 03A logo that knows where it is
Open the detail →
13

How I built this portfolio

07. Motion

Distance, closeness, property, spring: swap the property and it’s a new interaction.
Fig. 7. Letters that lean in
14

Detail 07 · Motion

Proximity: text that leans toward you

Letters that swell as the cursor passes, and the same idea behind the macOS Dock.

The name on the home page leans toward you: each letter grows bolder as the cursor comes near and settles as it leaves. One small pipeline on motion values, real text for screen readers, and the same idea as the macOS Dock.

Inside

  1. 01The real thing, with the controls out
  2. 02From a cursor to a font weight
  3. 03Two small pieces
  4. 04Proximity is a pattern
Open the detail →
15

How I built this portfolio

08. Interaction

If a site has only a few places to go, show them.
Fig. 8. A pill that opens in place
16

Detail 08 · Interaction

Dynamic islands

Islands instead of a menu: pills that spring, squish and blur open in place, sketched icons, six islands from one kit, and the textbook fix that measured slower.

There’s no menu. A dock of pills stands in for it, and each one morphs open in place: a spring with a little give, a squish, a blur through the middle, and content laid out at its final size from the first frame. Six islands, one kit, and a textbook fix that measured slower.

Inside

  1. 01The island, taken apart
  2. 02One kit, six islands
  3. 03The textbook fix that measured slower
  4. 04Crafts, Writing, the music, the résumé and the settings
Open the detail →
17

How I built this portfolio

09. Transitions

Choreography needs one source of truth: a single phase, not a set of flags.
Fig. 9. Five phases, one at a time
18

Detail 09 · Transitions

A state machine for transitions

Five phases, one string: how every page change here is choreographed, and why loose booleans would break it.

Every page change here is a little film in five phases, held in one string. Each phase has one way to end and cleans up after itself, everything else is read from it, and only idle can start a transition.

Inside

  1. 01One click, five phases
  2. 02Five phases, one string
  3. 03Impossible states, made impossible
  4. 04Small pieces, each with one job
Open the detail →
19

How I built this portfolio

10. Transitions

A sketch made from the real layout can’t go stale.
Fig. 10. Sketched, then inked in
20

Detail 10 · Transitions

Sketching the page before it arrives

The page sinking away, then the next one measured and sketched in pencil before it builds inside the sketch.

Between pages, the old one sinks away and the next is sketched in pencil before it builds inside its sketch. The page describes itself with a few marks and is measured live, and the sketch gets quicker the more often you see it.

Inside

  1. 01Four beats
  2. 02Sinking, not cutting
  3. 03The page describes itself
  4. 04Quicker the fifth time
Open the detail →
21

How I built this portfolio

11. Transitions

When a page opens from a preview of itself, let the preview become the page.
Fig. 11. The thumbnail is the page
22

Detail 11 · Transitions

From thumbnail to page

The resume island's thumbnail carried whole to where the sheet sits, the page sketched in outline round it.

The résumé island holds a living thumbnail of the résumé. Open it and the thumbnail is carried, whole and readable, to where the sheet will sit on a page that doesn’t exist yet; the page is sketched in outline round it and arrives beneath it.

Inside

  1. 01Take off, fly, frame, hand over
  2. 02Landing on a page that doesn’t exist yet
  3. 03A sketch that frames it
  4. 04The grow it replaced
Open the detail →
23

How I built this portfolio

12. Atmosphere

Felt more than seen, and idle when nothing changes.
Fig. 12. Plucked by the music
24

Detail 12 · Atmosphere

The details nobody asked for

Strings plucked by the music, grain that doesn't blink, the scroll ruler with its page index, click targets as big as their rows, and separators that never hang where a line wraps.

Details nobody would miss until they’re gone: strings behind the navbar, plucked by the music and asleep when it stops; grain that doesn’t shimmer; a scroll ruler that knows the page’s sections; and rows you can click anywhere, not just on their words.

Inside

  1. 01Strings plucked by the music
  2. 02Grain that doesn’t blink
  3. 03A scrollbar that knows the page
  4. 04Click the row, not the words
  5. 05A dot that knows where the line breaks
Open the detail →
25

How I built this portfolio

13. Resume

Wherever it appears, render the real thing, not a copy of it.
Fig. 13. One sheet, three places
26

Detail 13 · Resume

One markup, three outputs

One resume component as a page, a living thumbnail and a one-page PDF printed from CSS.

The résumé is written once. The same component is the page you read, the living thumbnail in the résumé island and a one-page PDF, sized in container units so it scales like paper, and printed by the browser from CSS.

Inside

  1. 01A document, not a layout
  2. 02Sheet, phone and paper
  3. 03A PDF from CSS
Open the detail →
27

How I built this portfolio

14. Performance

A fix is a guess until the frames say so.
Fig. 14. Smooth enough to count
28

Detail 14 · Performance

Fast, light and accessible

Keeping all this motion smooth: what a frame is and how they were counted, what moves cheaply, layers while things move, and the bytes.

All this motion can’t be the price of entry. What a frame is and how they were counted; only cheap things move, as one transform; a layer while something moves, and only then; the fixes the numbers kept and the ones they sent back; and where the bytes go.

Inside

  1. 01Sixty pictures a second
  2. 02How the frames were counted
  3. 03A layer while it moves
  4. 04What the numbers changed
  5. 05Where the bytes go
Open the detail →
29

How I built this portfolio

15. UX

Switched off, nothing moves, but a hover still answers.
Fig. 15. Off, and the next one with it
30

Detail 15 · UX

Motion you can switch off

A settings island with three switches: a calm version for devices that ask for less motion, everything still for visitors who switch it off, and the hover that stays either way.

Not everyone wants a page that moves. A settings island holds three switches, each saying what it does now; a device asking for less motion gets a calm version, a visitor switching it off gets everything at once, and hover, focus and press stay the same in every mode.

Inside

  1. 01Three switches that explain themselves
  2. 02Calm is not off
  3. 03A hover still answers
  4. 04One place that knows
Open the detail →
31

How I built this portfolio

16. Detailing

If it looks like paper, people handle it like paper: every way it doesn’t behave is a bug.
Fig. 16. Turned, never swapped
32

Detail 16 · Detailing

A book you can leaf through

The case study as a real book: sheets that only ever turn, a page that stays under your finger, corners that peel, the pages you aren’t reading, and the sound of a turn.

This book. Every sheet is always there and only turns, so a page can’t flash; a drag keeps the spot you took hold of under your finger; corners peel to show the page beneath; and the pages you aren’t reading show at its edges.

Inside

  1. 01A page is never swapped mid-turn
  2. 02The page stays under your finger
  3. 03A corner that peels
  4. 04Everything you aren’t reading
Open the detail →
33

How I built this portfolio

17. AI

An agent builds the average by default; the craft is steering it somewhere specific.
Fig. 17. I ask, it builds
34

Detail 17 · AI

Directing an AI agent

How this site was built with an AI coding agent: what I decided, what it did, and how I kept the craft mine.

This site was built with an AI coding agent. The design system is written as rules it reads every time, each repeated correction becomes a rule, everything is checked in the browser, and the deciding stays mine.

Inside

  1. 01A design system the agent reads
  2. 02Every correction becomes a rule
  3. 03Deciding, and saying no
Open the detail →
35

That’s the whole book, for now.

36

Colophon

Set in EB Garamond, Roboto and Caveat, the signature in Tropical Country. Drawn in pencil and built with Next.js, React, Tailwind CSS and Motion, with an AI coding agent at the next desk.

37
  1. 01 The brief
  2. 02 The first ten seconds
  3. 03 The design system
  4. 04 The pencil language
  5. 05 How things move
  6. 06 A signature written by hand
  7. 07 Proximity: text that leans toward you
  8. 08 Dynamic islands
  9. 09 A state machine for transitions
  10. 10 Sketching the page before it arrives
  11. 11 From thumbnail to page
  12. 12 The details nobody asked for
  13. 13 One markup, three outputs
  14. 14 Fast, light and accessible
  15. 15 Motion you can switch off
  16. 16 A book you can leaf through
  17. 17 Directing an AI agent

Case studyclick it to open

Seventeen details, from the first brief to the last spring, each with a live demo you can slow down and the real code behind it. They're in the book above, a spread each, in the order they were built: open it, leaf through, then open any one to go in.