hrishav.dev

01 / case study

alex capece photography

a fast, self-updatable portfolio site for a washington, d.c. documentary photopgrapher, built solo, from a client-provided design, in one week.

Desktop View
Mobile View

01 - problem

alex came to me with no existing site and a clear visual direction already in mind: a full-bleed, single-column scroll of documentary images with editorial captions underneath, minimal navigation, nothing to distract from the photography itself. my job was to take that vision and turn it into a real, fast, maintainable site, while also catching the places where his initial spec needed a second opinion on structure to actually hold up as a working website.

02 - role & process

i handled the build end-to-end: front-end development, converting his source images from png to webp, buying and configuring the domain, and deployment. alex was decisive about the visual direction, so most of my input was structural - where his design needed adjustment to translate cleanly into a responsive, performant layout, i flagged it and we worked through it together. he stayed firm on the core vision, which was the right call; my job was to make sure the site underneath was solid.

03 - solution

because this was a lightweight portfolio rather than a content-heavy site, i made a deliberate call: skip a cms and backend entirely. adding that infrastructure would have meant more moving parts, slower load times, and ongoing maintenance for a site that just needed to be fast and simple.

instead, i built a plain-folder-and-data-file-system. alex adds an image to a folder and updates a simple images.ts file to control what shows, in what order. to make that accessible to a non-developer, i recorded a set of walkthrough videos showing him exactly how to add, remove, reorder, and update images himself, with zero ongoing dependency on me.

Walkthrough: adding an image

04 - result

~95

1 wk

0

the site loads a large, image-heavy portfolio without any perceptible lag, and gives alex full control to update his work without touching a line of code. it's live and serving as his primary portfolio for assignments and inquiries.

hrishav was a delight to work with - extremely responsive, and was able to walk me through the more technical aspects without any issues. he even made a video tutorial to help me manage the back-end of things on my own! From first contacting me through my reddit post, to the final delivery of my portfolio site, hrishav was a consummate professional and helped me build exactky what i wanted. i would absolutely contact him again if i needed to build a different website or upgrade my current one.

alex capece · alexcapece.com

05 - takeaway

not every project needs a cms. sometimes the right technical decision is the one that adds the least - a plain-file content system and a short set of tutorial videos gave alex full independence without adding a single point of backend failure.