About This Website

This website came together quickly, but not casually.

From the first planning conversation to a live deployment, the project took shape over the course of a few days. What made the process interesting was the sequence of decisions that shaped it, as much as the speed itself.

Before there were layouts or code, there was a conversation.

Starting With the Story

The goal was to create a durable home on the internet, a place where my work, experiments, and ideas could live, accumulate, and change over time.

That meant avoiding the feel of a traditional developer portfolio, or a personal brand page dressed up as one.

Before writing code or designing layouts, I spent time in conversation with an AI assistant, working through questions like:

  • What themes actually define my work?
  • What patterns exist across my career?
  • What story connects the different systems I've worked inside?

That conversation became the raw material for the site.

Rather than starting with visuals or structure, the process began with the narrative foundation the site would rest on.

Out of that process, a simple positioning statement emerged:

Elliot Peter is a builder working across systems, AI-assisted workflows, and creative technology.

That line became the anchor for everything that followed.

Designing the Right Direction

Once the story was clear, the next step was to translate that narrative into a website.

The first version came together quickly. It followed a restrained, editorial design direction, built around typography and structured sections that explained my work and approach.

Then it was rejected.

The issue was not technical, the site worked. It was that the design created the wrong impression. It felt too static, too text-heavy, and too forgettable.

A second revision pushed the design in a darker direction and simplified the structure. That version also failed to land.

At that point, I chose to abandon that direction and step back. The site was functional, but it did not feel right, and that judgment mattered.

Two new design directions followed. One of them, internally called "Cinematic Systems," became the foundation for the final version of the site.

The shift was subtle, but important. The site moved toward:

  • a stronger first impression
  • more visual presence
  • less explanatory text
  • a clearer tone and point of view

Once that direction was clear, the rest of the build moved quickly.

Building and Deploying

Once the concept was in place, the technical side of the project was relatively straightforward.

The site was built on a simple, modern stack:

  • Next.js
  • TypeScript
  • Tailwind CSS
  • Vercel hosting
  • CircleCI for deployment automation

From the beginning, the priority was a site that could go live quickly, stay easy to maintain, and remain flexible enough to evolve over time.

The final steps happened quickly:

  • the repository was committed
  • the deployment pipeline was wired
  • CI/CD issues were resolved
  • domain routing and canonical URLs were verified
  • the site went live

Within days of the original planning conversation, elliot-peter.dev was live.

Why This Process Matters

This website serves as more than a web project. It is also a record of a process I want to keep exploring.

At a high level, the process is simple:

  1. Start with conversation
  2. Extract the narrative
  3. Define positioning
  4. Build quickly
  5. Review honestly
  6. Reject weak directions
  7. Reset when necessary
  8. Deploy once the concept is right

The website itself is the artifact.

The more interesting experiment is the process itself, how human judgment, AI collaboration, and modern tools can combine very quickly to turn an idea into something real.

Version 1

This page describes the first version of the site.

Over time, both the website and this explanation will evolve. New projects, experiments, and ideas will be added, and the narrative will evolve with the work itself.

This page remains open-ended.

It marks the first entry in what will likely become a much longer story.

The Final Step

Once the site was live, one final step remained: writing this page.

Every project benefits from reflection. Capturing what worked, what changed, and how decisions were made turns a fast build into something more meaningful.

This page closes the loop.

The project began with a conversation.

It continued through narrative, design, iteration, and deployment.

For now, it concludes with the story of how the site itself came to be.