Back to selected projects

Design + Front-End Development

Dan Ross Portfolio

A custom portfolio designed and built from scratch to feel more personal, use modern front-end techniques, and present my work in a way I can be proud of.

HTML / CSS / JavaScript / Accessibility

Dan Ross portfolio homepage

Project Overview

Building a portfolio that feels like me

I wanted a portfolio I had actually designed and built myself. One that reflected my personality, showed what I can do, and gave me something I would want to keep improving.

Role
Designer and front-end developer
Status
Live and actively maintained
Primary focus
Custom design, modern CSS, and accessibility

The Challenge

Matching the visual concept in code

My first goal was to match the desktop concept as closely as possible, then adapt it for smaller screens without losing the character of the design.

Starting with the look

I started with the desktop composition because the oversized type, structured grid, vintage imagery, and large visual elements were central to the design. I built the site iteratively in the browser and compared each section against the visual concept as it came together.

The color palette and overall attitude draw inspiration from the original The Texas Chain Saw Massacre poster. I especially liked the bold typography and warm 1970s colors. Print texture is used sparingly on the hero circle, project backgrounds, and rainbow graphic.

Key Implementation

Learning modern CSS by using it

Most of my recent layout work had used Bootstrap or Tailwind, so this project gave me a chance to work directly with Grid, Flexbox, relative units, and responsive sizing techniques.

01

CSS Grid

I used Grid for the larger page structure, including the editorial rails, project layouts, and multi-column sections.

02

Flexbox

Flexbox handles smaller alignment and spacing needs such as navigation, link groups, headings, and footer content.

03

Responsive sizing

I worked with rem, viewport units, and clamp() for typography and spacing instead of relying only on fixed pixel values.

04

Purposeful JavaScript

JavaScript is limited to interactions that need it, including the mobile navigation and back-to-top link.

Accessibility

Considered throughout the build

Accessibility was part of the implementation from the beginning, not something I planned to add after the design was finished.

  • Skip link for direct access to the main content
  • Semantic landmarks and heading relationships
  • Keyboard-operable mobile navigation with Escape support
  • Visible focus indicators across interactive elements
  • Reduced-motion preference respected for smooth scrolling
  • Initial automated testing completed with axe
  • Next step: Broader keyboard and screen-reader testing

The Result

A site I'm proud to put my name on

I'm proud of the finished look, but I'm also proud that the project gave me a chance to modernize my approach after years of working within legacy systems.

What I learned

Building without a framework gave me more direct control over the layout and strengthened my experience with Grid, Flexbox, relative units, responsive typography, and accessible interaction patterns.

What comes next

I plan to keep the site current instead of treating it as a one-time project. That includes adding stronger project details, completing more manual accessibility testing, and continuing to refine the responsive experience.

Next case study

Josephson Manufacturing