Rootline Web Co.Rootline Web Co. home
Case study · Pinterest marketing · Florida
In build · Her revision round

She wanted tropical. She also doesn’t like anything literal.

Kandace runs Pinterest marketing on her own out of Florida. She found me on Messenger, signed the same day, and asked for something bright, airy and tropical. Then she told me she doesn’t like things that are literal. No palm clip art. No beach photos. Good. Those were never going to be the interesting version anyway.

0.2 mleaf litter
Where this stands

Built, and in her hands

The page is built and she has been watching it come together on a private link the whole way. I’m waiting on her finished first revision round, and then it launches on her own domain.

The pictures here are from the build as it stood before her revision round. The real thing goes in when it’s live.

0.6 mtopsoil
The deal

One page, and how much fits in one page

A single landing page, buttons going out to the tools she already uses, one revision round. No form, no checkout, no second page. That’s what she bought and I’m not going to pretend it was a bigger job than it was.

What a page like that lives or dies on is whether it feels like a place instead of a flyer. Twelve sections on one scroll can very easily turn into a document, and a document isn’t going to convince anybody that the person selling design attention has any.

1.2 mthe root zone
The brief

Tropical without the tropics

Search any site in this space and you get the same three moves: a beach, a laptop on a beach, and a font that’s trying very hard. Kandace ruling out literal imagery took all of that off the table in one sentence.

So the warmth had to come from somewhere structural. Her own brand board already had the answer on it: Moroccan lattice. I pulled two motifs off it, a fretwork and a stepped strapwork, and used each one four different ways so no two panels next to each other are wearing the same pattern.

Everything decorative on that page is drawn: the lattice, the starburst, the monogram, the color fields, the marks. Nothing bought, nothing stock, nothing that turns up on somebody else’s site next month.

1.9 mhardpan
Color

Thirteen panels, and two colors that didn’t make it

Her navy is the ground everything else stands on, and the brighter colors take turns on top of it. I mapped all thirteen panels so neighbors never repeat: paper, mint, warm paper, pale blush, paper, pale mint, and so on down, with the chapter breaks and the closing panel in the navy.

Her amber and her coral are two of the prettiest colors she owns and neither one is a panel. Her navy lands at 3.2 to 1 on the amber and 3.4 to 1 on the coral, and AA wants 4.5. Pretty isn’t a good enough reason to make somebody squint, so they show up as accents instead of backgrounds.

2.6 msubsoil
Layout

Four section shapes on rotation

One shape repeated twelve times is a document. Four on rotation is a page you keep scrolling.

  1. 01

    Lead and body

    Heading left, the content carrying the right. The plainest one, used sparingly.

  2. 02

    Mirrored

    The same shape flipped, so two sections in a row never sit the same way.

  3. 03

    Oversized statement

    One line at display size doing the whole job, with nothing else on the panel.

  4. 04

    Full bleed showcase

    The content runs edge to edge and the heading tucks into it.

The Packages section before and after: two package cards stacked in a column on the left, four packages across in one row on the right with The Setup outlined
Packages, before and after. Two cards in a column became four across in one row, with The Setup outlined.
The Why Pinterest section before and after: a plain three-row list on the left, three panels each topped with a different brand color on the right
Why Pinterest, before and after. A plain list became three panels, each topped with one of her brighter colors.

There’s a rule under the decoration too: it never stacks. A lattice band and a frond don’t share a corner, and anything translucent gets an opaque silhouette of itself painted underneath in the panel’s own color, so the pattern behind it can’t read straight through.

3.4 mclay
On a phone

The parts people actually get wrong

Her four packages are a sideways swipe on a phone, one per screen with the next one peeking in from the edge and a cue that says so. No card borders, no boxes. Four price cards stacked vertically is four chances to stop scrolling.

The sections pin on a phone too, not just on desktop. The usual way to do that is to give up on anything taller than the screen, because a tall section pinned to the top hides its own last line. So the tall ones get a negative offset measured at runtime and hold at the bottom of the screen instead. Same effect, nothing cut off.

One photo of her on the entire site, and it’s in the About section. The hero does its work with type, color and lattice. A face in a hero is the easiest decision available and it almost never earns the space.

Four phone screens from the page: the navigation, the pin examples that scroll sideways, the About panel with her photo in an arch, and the closing panel with the book a call button
On a phone: the nav, the pin examples that swipe sideways, the About panel and the closing call. Before her revision round.
4.2 mparent material
How I work

You get to watch it happen

As soon as there’s a version up, you get the link. I’d rather you see it grow than hand you a finished thing and hope.

While I’m still finding the direction, I leave the commentary wide open. Tell me it isn’t landing, tell me why, tell me halfway through a section. That part isn’t a revision round and it doesn’t count as one.

Once the direction is locked, it closes, and we move to the set rounds. That’s not me getting precious about feedback. It’s the only way the site stops moving long enough to actually get finished.

Six versions of the landing page opening side by side, from a plain heading and photo to the version with the lattice, the arch around her photo and the underlined words
Six passes at the opening, from the plain first version to the lattice, the arch and the underlined words. All before her revision round.
5.1 mthe deep
What she owns

All of it, in her name

The code lives in her GitHub. The host is her Cloudflare account. The editor is connected to her repo, so when she changes a word it publishes itself without coming back through me. I’m a collaborator on her stuff, not a landlord of it.

Three typefaces, all self hosted as files in her project, so the page isn’t phoning a font service on every visit. It costs her nothing a month and it will keep costing her nothing a month.

6.0 mbedrock
By the numbers

One landing page, counted

Measured against the built page, not a mockup.

  • 0Stock photos. Every mark on the page is drawn.
  • 1Photo of her on the whole site, and it's in the About section, not the hero.
  • 13Color panels, mapped so no two neighbors match.
  • 2Lattice motifs off her own brand board, applied four ways each.
  • 4Section shapes, alternating, so the page never reads like a document.
  • 3Typefaces, self hosted, so nothing calls out to Google for a font.
  • $0What the stack costs her a month. Everything on free plans, in her name.
  • 1Page. That was the deal, and it's the whole point of this one.
6.9 mgroundwater
What happens next

Her round, her content, her domain

Her first revision round is with her now, along with the final copy and photos. When that comes back I build off it, and then it goes live on her own domain instead of the preview link.

I’ll come back and update this at launch, and again at thirty to sixty days with whatever actually happened.

Your website should be yours.

One page or twenty, it gets built for your brand and handed over in your name.