JustStart.now

Interior Design Website Template

Demo brand: HULVER STUDIO · Interior design studio · 13 routes · Astro 7 + Tailwind 4

Live preview

Interior Design Website Template — the HULVER STUDIO homepage

The demo is a full desktop site. Open it in a new tab ↗

About this interior design website template

A complete site for an interior design studio: thirteen built routes covering four individual project pages, a studio page, contact, privacy and a two-post journal.

Bone and warm taupe carrying a single clay-brown accent, in Faustina against Onest. The whole colour field is the moving thing: each room’s specified scheme resolves up out of a bare grey primer as the page is read. The palette is the loud channel, and it is doing something rather than sitting there.

The signature move is the colour coming up through the coats. Scroll depth within a room is coats laid, and every painted surface is re-composited each frame — resolving from primer-grey mud to the specified swatch by the paint-hiding law, perceived = paint·(1−tⁿ) + substrate·tⁿ. The control is the limewash room: a translucent mineral finish that never fully hides, so the substrate is still visible at the foot of the page exactly as it was at the top.

The 13 pages you get

Home /
The coats set-piece, the studio’s position, the work and the enquiry close.
Work /work/
The portfolio index — how an interiors practice is judged.
Four project pages /work/…
Ashcombe Kitchen, Marlowe Drawing Room, Pell Bedroom, Tarn Cottage. Each a full route with its own specified scheme — and Tarn Cottage’s limewash is the control that never fully covers.
Studio /studio/
Who the studio is and how it works, with the service stages and fee structure. The page that justifies a design fee.
Contact /contact/
A working enquiry form plus live tel: and mailto: paths.
Journal /journal/
A wired content collection — add an .mdx file and it appears here and in the sitemap.
Two worked articles /journal/…
How many coats is two coats, and reading a north-facing room. Both are genuinely useful and both sell the expertise.
Privacy /privacy/
A real legal route.
404 /404
Designed, not default. Keeps the navigation.

What is in the build

  • Painted surfaces re-composited every frame by the real paint-hiding law, resolving from primer grey to the specified colour as coats are laid
  • A declared control: a limewash room whose translucent mineral finish never fully hides the substrate, at any scroll position
  • Four project routes each carrying their own specified scheme, so the mechanic shows four different colours arriving
  • Services, stages and FAQ data as typed arrays, with the fee structure on the studio page
  • Balanced-neutral photography at restrained chroma across sixteen images, so the room photographs never fight the colour system
  • Faustina with Onest, both self-hosted; a working enquiry form plus live tel: and mailto:
  • Vitest and Playwright suites included in the repository

The design decision

Every template in this catalog is loud in exactly one channel and deliberately quiet in the other three. That single rule is what stops 62 different worlds reading as one design system in different paint.

The world
Bone and warm taupe carrying a single clay-brown accent — the whole colour field is the moving thing, each room's specified scheme resolving up out of a bare grey primer as the page is read.
The mechanic
"The Colour Comes Up Through the Coats": scroll depth within a room is coats laid, and every painted surface is re-composited each frame — resolving from primer-grey mud to the specified swatch by the paint-hiding law perceived = paint·(1−tⁿ) + substrate·tⁿ.
Loud channel
Palette
Imagery. Balanced neutral, chroma restrained
Type & palette
Faustina · Onest
#050f48 #efe9df #d9a441
The control case
The limewash room — a translucent mineral finish that never fully hides, so the substrate is still visible at the foot of the page as it was at the top. Drawn, not labelled.

Who it is for

Built for interior design studios, decorators working at the design end, and colour consultants. It suits a practice that specifies schemes and needs clients to understand that specification is the work. For architecture, the architecture-studio build draws sections instead of coats; for a showroom with products, ecommerce.

Under the hood

  • Astro 7 · static output, zero client framework
  • Tailwind 4 · one @theme block holds the palette
  • MDX content collections for the blog
  • GSAP + Lenis for the scroll work, reduced-motion aware
  • Self-hosted woff2 — no Google Fonts request
  • Sitemap, canonicals and per-route meta wired
  • Vitest + Playwright suites in the repository
  • Zero third-party requests · strict CSP-ready

How to get started

  1. 01 Accept the repository invite and clone it.
  2. 02 Run npm install, then npm run dev.
  3. 03 Replace the content in src/data/ with your own — that is where the brand, the copy and every list live.
  4. 04 Swap the images in public/images/ and the palette in the @theme block.
  5. 05 Run npm run build and deploy dist/ anywhere static.

Questions

Do I have to supply paint colours for each project?

A specified colour per surface, which any designer already has in the schedule. That is what makes each project resolve to its own scheme rather than replaying one animation four times.

What is the limewash room for?

It is the honest exception. Limewash is translucent and never fully covers, so the build ships a room where the mechanic visibly does not complete. A studio that specifies mineral finishes will recognise it immediately — and clients learn something from it.

Can I show fees?

The studio page carries the service stages and fee structure already. Interior design is a category where vagueness about fees costs you the enquiry rather than protecting it.

What exactly do I get for free?

Access to a private GitHub repository holding the complete Astro source of this template — every route you see in the preview, the content model, the images and the tests. Updates arrive in that same repository.

How many sites can I build with one licence?

As many as you like, for yourself or for clients. The licence is per buyer, not per project. The one thing you may not do is resell or redistribute the source as a template, theme or starter kit.

Do I need to know Astro?

It helps, but the common case is editing content and colour. Content lives in typed objects under src/data, colour lives in one @theme block, and npm run dev shows the result. Deploying is a static folder — Cloudflare Pages, Netlify and Vercel all take it as-is.

Is anything loaded from a third party?

No. Fonts are self-hosted woff2, there is no analytics, no tag manager, no CDN script and no external CSS. The build ships static HTML under a strict Content-Security-Policy.