Back to projects

Dayle Palfreyman

An artist portfolio that disappears behind the art

2025 — Present
Solo Designer & Developer
Live site
Next.js 15Sanity CMSFramer MotionTailwind CSSTypeScript

Ownership

Solo Designer & Developer

Team

Solo / small team

Key Result

95+ Lighthouse

Overview

A portfolio for installation and object-based artist Dayle Palfreyman. The brief: make the art the only thing people see. No navigation clutter, no design ego, no templates. A full-screen immersive gallery with Sanity CMS for complete client independence.

The Challenge

Artist portfolios have a unique tension: the site needs to feel considered and intentional, but it can't compete with the work. Most portfolio templates either look generic or add so much design language that they overshadow what they're showing. Dayle needed a site that felt like walking into a gallery, where the work fills the room and the architecture stays invisible.

Constraints

  • Visual restraint was non-negotiable: the site could not compete with artworks.
  • Client autonomy required robust CMS patterns over one-off hardcoded pages.
  • Accessibility and performance had to hold on media-heavy routes.

Decision Log

Problem

Portfolio templates encourage UI chrome over artwork presence.

Decision

Adopted full-screen, vertically snapping gallery with minimal persistent chrome.

Tradeoff

Less conventional page structure for some users.

Impact

Stronger immersion and clearer artwork-first hierarchy.

Problem

Rich motion can quickly become distracting in art contexts.

Decision

Constrained motion vocabulary to subtle spring-driven transitions.

Tradeoff

Lower novelty and fewer visual flourishes.

Impact

Consistent tone with reduced cognitive interference.

Approach

1. Full-Screen Immersive Gallery

The homepage is a vertically-snapping gallery. Each artwork fills the entire viewport. No thumbnails, no grids, no sidebars. Scroll or use arrow keys to move between pieces. Click to enter the detail view with multiple images, video embeds, and artwork metadata. The interaction model borrows from museum kiosks, not web templates.

2. Motion with Restraint

Every animation uses spring physics (not tween curves) for organic feel. Shared layout animations create seamless transitions between gallery and detail views. But the motion vocabulary is deliberately minimal: fade, slide, scale. Nothing calls attention to itself. The header auto-hides after 3 seconds on desktop. Chrome disappears on artwork detail pages. Reduced motion preferences are fully respected.

3. Accessibility as Foundation

Skip navigation links, ARIA live regions that announce the current artwork to screen readers, proper focus indicators using the accent color, keyboard navigation throughout. Loading skeletons for every route. Alt text includes medium and year, not just title. The gallery has a visible slide counter. These aren't afterthoughts; accessibility was architected from the start.

4. CMS-Driven Independence

Sanity Studio is configured so Dayle can manage artworks, exhibitions, writing, interviews, and site settings without touching code. Dynamic sitemap generation, JSON-LD structured data for artwork and exhibition pages, and canonical URLs are all automated. The site SEO improves every time Dayle adds content.

Outcome

A site that loads fast, ranks well, and puts the art first. Full Lighthouse scores above 95. Dynamic SEO infrastructure means every new artwork is automatically optimized for Google. The client manages everything independently through Sanity.

95+

Lighthouse

100%

Client Independence

WCAG 2.1 AA

Accessibility

Auto-generated sitemaps + JSON-LD

SEO

Learnings

  • Artist portfolios are the ultimate test of design restraint. Every pixel you add competes with the work you're trying to showcase.
  • Spring-based animations feel more natural than tween curves for gallery interactions. The physics of deceleration matches how people expect physical objects to move.
  • Accessibility and good design are the same thing. Skip links, focus indicators, and screen reader support aren't compliance checkboxes. They're design decisions that make the site better for everyone.
  • Automating SEO infrastructure (sitemaps, structured data, canonical URLs) means the site gets better every time the client adds content, without any developer involvement.

Anti-Patterns Avoided

  • ×Autoplay-heavy transitions that distract from images.
  • ×CMS models that require developer intervention for routine updates.
  • ×Accessibility retrofits after visual design lock-in.

Next Iterations

  • Collection-level storytelling templates for exhibition narratives.
  • Media compression pipeline tuning for even faster cold loads.

Need This Type Of Outcome?

I run focused design engineering sprints for product teams.

If your team needs clearer UX, faster implementation, and measurable performance improvements, I can help.

Next project

Spark Dashboard