Skip to content

reference-web-development — Sites Built from a Reference

Role
Solo Designer / Developer
Period
2026 — ongoing
reference-web-development — Sites Built from a Reference

Overview

“Make it like this site” is the most common brief for a new website, and the hardest to hold to: opinions about “like” drift, and the build slowly stops resembling the reference. This service turns the reference into something you can check: a written brief first, a measured comparison at the end.

Result: a new site with its own content and brand that shares the reference’s structure, rhythm and feel, with the match shown in screenshots rather than asserted.


How it works

  1. Brief of the reference. I read the live site once, politely: page structure, section order and heights, colour roles, type scale, spacing, corner radii, breakpoints, which parts move and how. For a whole site I follow its main navigation to cover the distinct page types (home, list, detail). Result: a short document and a token file you can read and correct before anything is built.
  2. Your content and brand. Your text, your photos, your logo, your colours where the reference’s palette does not fit. The brief decides structure and proportions; it never supplies content.
  3. Build. Hand-written HTML/CSS (plus a little JavaScript where behaviour needs it), as a static site, Jekyll, or a theme layer on an existing OpenCart store. Light and dark themes when the reference has them, Ukrainian and English versions when you need both.
  4. Measured check. Screenshots of the reference and the build at desktop and phone widths, compared pixel by pixel on the layout (target: at least 98% of pixels match within tolerance and page heights within a few pixels where the structure is meant to match), plus a keyboard pass and a look at both colour themes. Differences are listed with the reason for each, not hidden.
  5. Hand-over. Source repository, the deployed site, the brief and the design tokens, so the next change does not start from zero.

What you get

  • A written reference brief and a design-token file
  • The built site in your repository and live on your hosting
  • Responsive layout checked at desktop and phone widths, with the comparison screenshots
  • Optional: bilingual UA/EN, light/dark theme, contact or lead form wired to email, Telegram or CRM

Boundaries

  • The reference’s text, photographs, illustrations, logos and fonts are not copied; commercial fonts get a free look-alike.
  • No bypassing of bot protection, and no sign-in, checkout or banking pages as references.
  • A site that is far from the reference on purpose (a different audience, a different brand) is a design job, not a remake, and is quoted as one.

Stack

HTML, CSS, JavaScript, Jekyll, OpenCart, design tokens, Chromium for the visual checks