← Index 02Fragiles CV  ·  Contact
01Shipped work· Case

Fragiles

A hand-coded portfolio site for an artist who makes small installations from things found in nature.

Role
Designer and front-end developer
Context
NHL Stenden, year 1 studio
Year
2025
Built with
HTML, CSS, Eleventy, PHP
Links
Staging site ↗
testing.alfydesign.com
The Fragiles home page
Screens
01

The brief

The artist showed her work on Instagram. She needed a place of her own for it, professional and minimal.

Journey mapping told us why the site exists. An art director comes looking for credentials. A visitor comes for more images, and more about each piece.

02

Content first

We spent the first two to three weeks on research and content, before a single wireframe, because designs stall without real content. The team questioned that rule. It paid off.

Content first, then wireframes.

03

What we decided

3.1

Mobile first

We designed the single column first: fewer factors, fewer mistakes. Tablet and desktop grew out of it, one module at a time.

HomePortfolio
3.2

The work on black

Minimal, as the brief asked: each piece stands on black, with only its title and number.

Detail · Portfolio
3.3

Pieces and shows as data

The pieces and the exhibitions are stored as JSON, and Eleventy builds the pages from that data.

Detail · Exhibitions on the home page

Testing came in waves and ended with an expert round: four reviewers, each with an itemised critique. We refined the design after every round.

What the expert round flagged

  1. —An unclear purpose.
  2. —A template feel.
  3. —Where the contact form sat.
  4. —The portfolio carousel.
  5. —The height of the header on phones.
04

Under the hood

HTMLCSSEleventyJSONPHPWebPAnderson Grotesk
  1. 4.1Hand-coded: thousands of lines of mobile-first HTML and CSS, with no page builder and no framework.
  2. 4.2Plumbing for English and Dutch.
  3. 4.3A PHP contact form with several layers of spam defence.
  4. 4.4Fingerprinted file names, so a browser never shows a stale version.
  5. 4.5SEO metadata on every page.
  6. 4.6Responsive images in WebP, checked with PageSpeed.
05

How we worked

A team of seven. I ran the Notion board, planning backwards from the end goal, with small groups by expertise, freedom inside them and regular check-ins.

7People on the team
2–3Weeks of content before any wireframe
4Expert reviewers
06

What I learned

  1. 6.1A short, team-based project means sacrifices: no logo, and less research of my own.
  2. 6.2I relearned CSS layout from the ground up, tried JavaScript and set up SEO.
  3. 6.3It came out more responsive and accessible than anything I had built before.