Building What We Couldn’t Find

We did not set out to build a website from scratch. We set out to find one that already felt like us.

For years, we knew what we wanted the Crackers & Cucumbers website to feel like.

We wanted a place where the photographs came first, but where the stories behind them had room to breathe. We wanted something quiet, elegant, image-led, and personal. More like entering a gallery than opening another business website.

That did not seem like an unreasonable request.

Then we started looking.

We tried the large website builders. We browsed template after template—photography portfolios, artist pages, storefronts, blogs, and creative-business websites.

Some were polished. Some were modern. Some were built specifically for photographers.

None of them felt like us.

The photographs always seemed secondary to the template. Stories were reduced to captions. Galleries felt like product grids. Every path eventually seemed to lead toward the same kind of storefront.

We knew we wanted to sell prints eventually, but we did not want the website to begin with a sales pitch.

We wanted people to enter through the work.

We wanted them to wander.

A photograph might lead to a reflection. A reflection might lead to a journal entry. A collection might eventually become a film or a book. Some projects might be complete. Others might still be taking shape.

We were not trying to fit photographs into a website.

We were trying to build a place around them.

Eventually, the question changed.

We stopped asking which template came closest to what we wanted.

We began asking what the website would look like if we built exactly what we had imagined.

That was the beginning.

One blank page.

One line of HTML.

Then another.

Soon there were folders, stylesheets, image paths, navigation menus, broken links, missing files, and more CSS than either of us ever expected to care about.

Every answer seemed to create another question.

Where should the Gallery live?

What is the difference between a Gallery and a Collection?

How large should the logo be?

Why does everything that looks good on a desktop look terrible on a phone?

And underneath all of it was the question that kept returning:

Is this worth it?

There were moments when using another template would have been easier.

There were moments when a nearly-right website seemed more reasonable than another night spent tracking down one incorrect folder path.

But nearly right was the problem that started this.

So we kept going.

Line after line.

Page after page.

Not because we had suddenly become web developers, but because the place we wanted did not exist yet.

If we wanted to enter it, we were going to have to build it.

At this point, there was not much of a gallery.

There were only pieces of one.

A homepage beginning to form. A few photographs. Some rough ideas about collections. A growing pile of code and the stubborn belief that it might eventually become something.

We still did not know exactly how all the pieces would fit together.

But for the first time, we were no longer searching for the website we wanted.

We were building it.

The Story Continues

The first pieces were in place. Next came the moment when the code, photographs, collections, and stories began to feel like parts of the same place.

Read Building Rooms, Not Pages
Return to Behind the Build