Internal reference
Five of the fifteen section patterns from Dave's rebuild, converted to our colours, our fonts and plain HTML with real CSS classes. Nothing here touches the rest of the site — this page carries its own styles and its own script, and it is not in the menu. The point is to see the patterns behaving on our stack before any of them go near a real page.
The remaining ten blocks are on block library, batch two →
By the numbers
0+
Years in business
0
Case studies published
0weeks
Typical website build
0
Senior people, no juniors
aria-expanded and real
focus states, so it works from the keyboard. Animates on height rather
than a guessed max-height, which means long answers never get clipped.
Uses the house chevron, identical to the service drawers — click only,
no hover, because long answers reflowing under the cursor is a nuisance.
This is the block I would take first: paired with FAQPage schema it is
directly useful for the AI search work, because answer engines lift
question-and-answer pairs more readily than prose.
Questions we actually get asked
The things people ask on a first call, answered the way we would answer them on a first call.
Six to eight weeks for most sites, from the first workshop to going live. The variable is rarely the build — it is how quickly content and photography come together. If you bring the words, it is faster. If you would rather we wrote them, we will build that into the schedule from the start.
No. We host most of the sites we build because it makes support straightforward and we can fix things quickly. But the site is yours, and if you would rather it sat somewhere else we will hand it over properly with everything you need to run it.
Not if the URLs are handled properly. Every address on the old site either stays exactly as it is or redirects to its replacement, and we map that before a single page is built. Rankings usually settle within a few weeks. It is the one part of a rebuild where being careful early saves months later.
We do. Reddishpink is deliberately small and senior — the person you meet at the start is the person writing, shooting or building. Nothing is handed down to a junior once the pitch is over, because there is no junior to hand it to.
Often that is the best arrangement. Some clients use us for the things they have no one for — film, photography, a rebuild — and keep the day-to-day in-house. Others want a senior head in the room once a month. Both work, and neither needs a retainer to start.
site.css puts
overflow:hidden on every <section>, which
silently stops sticky from working. Fixed here with
overflow:clip, scoped to this page. Pinning is switched off
below 760px, where it traps the scroll rather than helping.
How it works
Five stages, in plain language, with someone accountable for each one. You always know what is happening this week and what lands next.
A short, focused start: who we are talking to, what they need to believe, and what the work has to move. Usually half a day.
One route committed to properly — type, colour, tone and motion — rather than four half-explored options dressed up as choice.
Writing, shooting and building run alongside each other, so the schedule stays honest and nothing sits waiting on one handover.
Redirects mapped, analytics wired up before the doors open, and a staged rollout — so day one tells you something useful.
Launch is the middle, not the end. What we learn in the first month is usually worth more than anything agreed in the first week.
.proj grid, and it reads properly as a list rather than a
wall of thumbnails. Worth having alongside the grid rather than instead
of it: this suits a full archive page, the grid suits a shortlist.
Collapses to a stacked layout below 760px. Links point at the real case
studies.
Selected work
A working list rather than a gallery. Quick to scan, quick to load, and it never makes a promise the thumbnail cannot keep.