UX AGENT

Live wildlife brand Content strategy · UX/UI · WordPress

Greek Mountain Man had grown into a massive website. The story was getting lost inside everything I had added. I cut it back to one focused page and let the work lead.

The goal: Give the photography and field stories room to breathe, make Greek Mountain Man easy to understand, and point people toward the work, the book, and what comes next.

1 pageOne focused brand story
14+ yearsPhotography and field stories
End to endStory through the live build
Years of work → one clear story Greek Mountain Man
Greek Mountain Man wildlife photography website shown as an editorial one-page experience
Visitor questionWho is Greek Mountain Man, and why does the work matter?
Next stepSee the photography, read the stories, follow the next chapter

01 Focus

The project kept growing. The reason to care became harder to see.

Greek Mountain Man started as a place to share my wildlife photography. Then it grew: animal stories, field notes, awards, gear, social posts, a book, workshops, a wildlife map, and every new idea I wanted to chase. Each piece belonged. Together, they made a new visitor work too hard to find the heart of it.

The site had gotten huge because the project had gotten huge. Every new idea became another page, menu item, introduction, or explanation. The photography was still there, but it was no longer leading. Before people could care about the work, they had to understand the whole machine around it.

I gave my own brand the same hard look I give client work. I read the site like a first-time visitor, found the repeated ideas, moved the parts that belonged elsewhere, and walked the full mobile scroll. This was not a formal research project with interviews and heatmaps. It was an honest reset of a site I had built, managed, and let grow too large.

I kept the parts with a pulse: the photographs, the field stories, the animals, the years behind the work, and the things I am building next. Then I turned the site into one focused page instead of a maze of competing destinations.

The question behind the refresh

How much could I remove and still make the person, the photography, and the future of the project easier to understand?

What I reviewed before cutting the site down

I was not hunting for more content. I was looking for repetition, slow starts, and anything that made people carry too much context before the work had a chance to land.

Content inventory

I mapped every gallery, animal story, about section, award, journal entry, gear page, book idea, workshop, map, social link, contact path, and repeated introduction.

First-visit review

I started at the top and pretended I knew nothing about the project. That showed me where the brand took too long to explain itself and where the best work arrived too late.

Mobile scroll audit

A long site feels even longer on a phone. I checked the order, reading length, image crops, carousel controls, tap targets, and how many choices appeared at once.

Maintenance reality

I looked at what I could honestly keep current. A personal site loses trust when every idea has a page but only a few pages still feel alive.

The page still had to serve different kinds of visitors

One clear page still had to work for people arriving with different interests. The answer was not four separate paths. It was one strong story with clear places to go deeper.

Someone arriving for the photography

Wants to see the photographs now, not after a biography, a pitch, or a long setup.

Needs to know: Is the work worth staying for?

Someone staying for the stories

Cares about the animals, the field notes, and the time behind the photographs, not just the final image.

Needs to know: What is the world behind these images?

Someone discovering the larger project

May come for the wildlife map, the book, workshops, field guidance, or a reason to work together.

Needs to know: Where is this work going next?

Someone trying to understand the person

Needs enough of my story and track record to understand why the voice, the field knowledge, and the photographs belong together.

Needs to know: Who is Greek Mountain Man?

02 Structure

I replaced a large website with one deliberate story.

A smaller menu would not fix the same oversized story. I rebuilt the page in the order a new visitor could understand it: the place, the photographs, the animals, the person, the field notes, and what comes next.

01

Where am I?

Start in the Tetons and say plainly what this work is about.

02

Show me the work

Let the photographs earn attention before asking people to read the full story.

03

Why these animals?

Use the moose, bears, wolves, and field notes to show the patience behind the images.

04

Who is behind it?

Bring in my story, experience, awards, and point of view after the work has earned interest.

05

Where can I go next?

End with the journal, gear, map, book, social channels, workshops, and contact without turning the site back into a directory.

Principles that drove the simplification

The new look mattered. The bigger change came from deciding what stayed, what moved, and what no longer needed a page of its own.

One page, one argument

Every section had to move the same story forward. If it could not explain why it belonged, I cut it, combined it, or moved it somewhere else.

Let the photography lead

The interface could add rhythm, but it could not compete with the mountains, the animals, and the field work that give the brand its reason to exist.

Cut repetition, not character

The site could get shorter without losing its voice. I kept the field details and the slower pace. I cut the repeated setup.

Compose mobile intentionally

I reconsidered image crops, type, carousel controls, spacing, card order, and reading length for a phone instead of shrinking the desktop page.

Before the refresh

Every idea wanted its own place.

  • Too many pages, categories, and menu choices had piled up.
  • Photography, biography, writing, awards, gear, offers, and future ideas all fought to lead.
  • The same introduction restarted the story in several places.
  • On a phone, the amount of content became impossible to ignore.
  • Keeping every page current took time away from the work itself.
Refresh direction

Every section continued one story.

  • One page moved from place to photography, wildlife, biography, journal, and what comes next.
  • Big images and a slower pace let the work earn interest before the supporting details arrived.
  • Awards, gear, stats, and future projects became short proof points instead of side roads.
  • Mobile became its own reading experience, not a stack of desktop sections.
  • Fewer moving parts made the site easier to keep alive.

A smaller footprint with a stronger sense of place

One continuous page now connects the Tetons, the photographs, the animal stories, the person behind the camera, and the work still ahead.

Greek Mountain Man one-page wildlife photography website with an editorial hero, portfolio, animal stories, field journal, gear, and future offers

The visual design grew richer while the site structure got smaller. That kept the page from feeling empty or overloaded.

Content strategy One-page structure Editorial UX Responsive design

03 Build

The design stayed connected from content decisions to working code.

I wrote, designed, and built the page as one system. When the story ran long, I could cut it. When a photograph needed room, I could change the layout. When a desktop idea failed on a phone, I could fix it in the code instead of explaining it away.

01

Audit and cut

I listed everything, found repeated setup, separated the portfolio from the wildlife planner, and removed the sections that had stopped earning space.

02

Reframe the story

I set a simple order: place, work, animals, person, journal, then the projects still taking shape.

03

Wireframe the rhythm

The wireframe set the size and order of the big moments: hero, proof, portfolio, story, biography, supporting content, and contact.

04

Define the editorial system

Large serif type, quiet labels, dark field colors, restrained cards, and layered images gave the site character without putting the interface in front of the photographs.

05

Build custom carousel UX

The portfolio and animal stories needed movement without feeling like a stock slider. I built custom controls, image framing, and responsive behavior around the work.

06

Test the long scroll

I tuned section changes, image loading, spacing, type, menu behavior, touch controls, and mobile order until the page held together from the first image to contact.

Representative reconstruction

The wireframe was about pacing, not decoration.

I rebuilt the planning logic in the same clean wireframe style used across these case studies. It shows the decisions that mattered: a strong opening, the work early, proof that does not interrupt, room for the animal stories, and a controlled path to the map, book, workshops, social channels, and contact.

The goal was not to cram everything onto one page. It was to decide what deserved to stop the scroll.

The system behind the page

A one-page site still needs rules. Without them, it becomes a stack of nice-looking sections. I built a repeatable rhythm that could hold different kinds of content without losing the main story.

Editorial hero

The opening brings together place, voice, proof, and two clear paths without turning the first screen into a menu for everything.

Portfolio carousel

The photographs stay large. Controls, captions, sequence, and links stay easy to find and use.

Animal chronicles

Each animal gets a visual sequence, a specific story, and a line from the field without needing a separate long page.

Brand and proof

My story, years in the field, awards, publishing, and experience support the work after people have seen why they matter.

Supporting modules

The journal, gear, book, map, workshops, social channels, and contact use tighter patterns so they support the story instead of starting it over.

Reusable front end

Custom HTML, CSS, and jQuery run the layout, carousels, layered visuals, and responsive details inside WordPress.

Mobile composition

The phone needed its own composition, not a compressed desktop page.

The site is long and image-heavy on purpose. On a phone, I had to control what showed first, how much copy appeared at once, where images cropped, how carousels moved under a thumb, and when each supporting section had earned the next screen.

  • The hero keeps the landscape, title, and opening readable at the same time
  • The menu gets smaller without hiding the main paths
  • The photography and animal stories still work with touch
  • Long stories break into shorter reading moments
  • Offers appear only after the work has earned interest
Greek Mountain Man mobile website shown across two phone screens with the landscape hero and wildlife photography

04 Edit

The hardest part was deciding what no longer deserved its own page.

Cutting a personal project is hard. Every page carries a memory, an idea, or something you still hope to build. The site got better when I stopped asking whether a section was good and started asking whether it helped people understand the whole thing.

Keep large

Photography and field stories

They are the reason the brand exists. They earned size, time, strong images, and room for the writing to slow down.

Compress

Awards, stats, gear, and credentials

They build trust, but they do not need to interrupt the story or become pages of their own.

Combine

About, journal, and future offers

They still matter. They work better as connected chapters after people understand the work.

Separate

The wildlife planning product

The map solves a different problem and needs its own product. The portfolio can introduce it without trying to hold all of it.

The site became shorter because the decisions became clearer.

The site did not get shorter by losing detail. It got shorter by giving detail a place. Big moments carry the emotion. Supporting sections answer practical questions. Future projects arrive after people have a reason to care.

EarlierThe place, voice, photographs, and proof now arrive near the beginning.
QuieterThe menu and interface support the story instead of calling attention to themselves.
SmallerFewer pages and fewer repeated explanations make the brand easier to understand and keep current.

The editing rules I used

These rules keep the site from growing back into the thing I just fixed.

01

Every section earns the next scroll

A section stays only when it gives people a new reason to continue. Repeating the brand in different words is not enough.

02

The work appears before the explanation

Let the photographs earn attention first. My story and credentials then explain the years behind them.

03

One idea does not automatically need one page

A good idea can be a strong section, card, or link. It does not always need another page in the menu.

04

Future work stays visible but proportionate

The map, book, and workshops can stay visible without letting unfinished work take over the site.

05 Outcome

The result was not more website. It was a clearer version of the brand.

I am not claiming a made-up conversion lift or a lab-style before-and-after test. The win is visible in the site itself: fewer pages, a stronger story, a better phone experience, and a site I can actually keep current as Greek Mountain Man keeps changing.

1 page

Core experience

Footprint

The main story now lives in one clear flow instead of asking people to piece it together across a large site.

Clearer

Narrative hierarchy

Story

The place, photographs, animals, person, and future projects now arrive in an order that makes sense.

Stronger

Phone composition

Mobile

The long scroll was rebuilt around image crops, touch, reading length, controls, and pace.

Lighter

Maintenance burden

Ownership

Fewer pages make it easier to keep the site honest, current, and tied to the work that actually exists.

The page no longer asks people to understand every part of the project before they understand me.

The page now starts in the field, shows the work, explains why I keep returning to these animals, and gives enough of my story to make the rest make sense. From there, people can find the map, book, journal, social channels, and future workshops. The site is smaller. The world behind it feels bigger.

FocusedPeople understand the core of Greek Mountain Man before the side projects appear.
EditorialThe photographs and the writing now move as one story instead of two separate systems.
FlexibleNew work has a clear place to go without forcing another full rebuild.

A clearer first impression

People can understand the place, the person, and the point of view without opening five pages or reading a long brand pitch.

A stronger visual rhythm

Large photographs, quiet interface details, and different section pacing keep the long page from turning into the same grid over and over.

A true mobile presentation

The phone keeps the landscape, story, photographs, and controls without dragging every desktop choice along with it.

Room for the project to grow

The map, book, workshops, journal, and new work all have a place without pulling the portfolio back into a scattered site.

My contribution

What I actually did on Greek Mountain Man

Because this is my own brand, I owned both the mess and the fix. I made the content, design, code, and maintenance choices together. This was not a concept piece.

Content inventory and cuts
Brand story and direction
Site structure and one-page flow
Writing and content restructure
Wireframes and page planning
Editorial interface design
Photo selection and visual sequence
Custom portfolio and animal-story carousels
Responsive and mobile layout
Custom HTML, CSS, and jQuery
WordPress front-end build
Carousel controls and touch behavior
Typography, spacing, and section flow
Responsive QA and launch polish
Ongoing ownership and updates
The work in one sentence

I did not make Greek Mountain Man smaller. I removed what made the story harder to hear.

The finished site holds the photographs, field stories, animal encounters, experience, journal, gear, map, book, workshops, and contact inside one focused experience. The method is the same one I bring to client work: know what the page needs to do, cut what gets in the way, build a clear path, and stay close enough to the code that the idea survives.