Skip to content
Back to the blog

· 4 min read

Reworking the 1Zero9 home page: structure first, motion second

We thought the home page needed more animation. Looking closely at a site we admired showed the gap was structure. What we changed in one evening, what we left alone, and what went wrong.

case-study · design · website · claude

The problem

The home page of this site was tidy and said the right things. It also felt flat. The hero was a headline and two paragraphs, with some animated lines that most people would not notice. Below it sat one featured project, and a link to the other nineteen.

Our own diagnosis was that the page was missing motion and interactivity. That turned out to be wrong.

Looking at a site we liked

The reference was HiBob, an HR software company. Their home page feels lively, so we expected to find a lot of animation. There is very little. What it has is this:

  • The product is in the hero. A large screenshot of the app sits under the headline, so you see what they make before you read a word.
  • Dark and light sections alternate. Each scroll feels like a new chapter.
  • Proof gets its own blocks. Big numbers, customer quotes and feature cards each have a section to themselves.

Put beside it, our page had one continuous light surface, no picture of anything we had built above the fold, and one project.

The useful finding was that most of our components were already the same kind: a floating pill navigation, rounded cards, small tags, paired buttons. The gap was how the page was arranged, not what it was built from.

What we kept

The colours, the fonts, the logo, the navigation and the card style all stayed. A new palette was suggested and turned down, which was the right call. A one-person studio does not need a rebrand to fix a layout.

We also left out the parts of the reference that belong to a large company: the wall of customer logos, the review badges, the big menu, a grid of job roles. On a site whose whole pitch is "you deal with one person", they would read as padding.

What we changed

  • A hero with something to look at. The copy went from two paragraphs to one. Beside it, a browser-style frame fades through screenshots of three live sites. It pauses when you hover over it.
  • Two dark bands. One under the hero holds four numbers. One above the footer offers two ways to start: send a brief, or ask what is possible.
  • A carousel of four projects in place of the single featured card. It swipes on a phone and never moves on its own.
  • Numbers we can stand behind. Two are counted from the site's own content when the page loads. One is the size of a directory we built. The fourth is the number of people you deal with, which is one.
  • Small tidy-ups. Contact is now in the header. A button arrow that suggested an outside link was corrected. The footer blurb was rewritten to sound like the rest of the site. A services page that nothing linked to was removed.

Motion, last

With the structure in place, the motion that was left to add was small: sections fade up as they scroll into view, the numbers count up once, and cards lift on hover.

Three rules kept it honest:

  • Reduced motion means none. If a visitor's device asks for less motion, the fades, the count-up and the rotating screenshots are all off.
  • Content never depends on the script. The numbers are in the page as it arrives, so they read correctly before anything runs.
  • Nothing important moves by itself. The hero frame rotates, but the carousel with the detail in it waits for the visitor.

What went wrong

  • It went live without a preview. This site deploys only when a change reaches its main branch, so there was no private copy to look at first. The build and the checks passed, it was merged, and the first time anyone saw the page was on the live address. It looked right. That was luck as much as care, and a preview step is worth adding.
  • The first build failed. One line assumed a list of screenshots always had a first item. The type checker disagreed and stopped the build before anything shipped, which is what it is for.
  • We found parts that had never worked. A scroll-reveal component was already in the code, with no styles and nothing using it. One colour class on the old page did nothing at all. Neither had been noticed, because nothing visibly broke.
  • One project has no screenshot. Its slide in the carousel shows a title on a plain background until we take one.

What it does not do

  • It has been checked at desktop width in the light theme. Phone width and the dark theme were not checked before it went live.
  • One of the four numbers is typed in by hand and will go stale when that directory grows.
  • Only the home page changed. The work, labs and about pages still have the old rhythm.
  • We have not measured anything. Whether more people start a brief is a question for a month from now.

Try it

If your page feels flat, check the structure before you reach for animation. Three questions did most of the work for us. Can a visitor see what you make without scrolling? Does the page change pace anywhere on the way down? Is your proof in its own section, or buried in a paragraph? If the answers are no, moving things around will do more than making things move.