Xandrov StudioAtlas of shipped systems
← The territory/ V. Brand & Web/ № 16 — xandrov.com
Dossier № 16 / 19 — Brand & Web — Live production site

xandrov.com

Nothing between the editor and production.

File
№ 16 / 19
Territory
Brand & Web
Classification
Live production site
Status
Live in production
§ 01 Context

Xandrov Labs' studio site serves as the front door — a single page that introduces the consultancy and its work. The brief required a site that loads instantly, never breaks, and costs nothing to run. These constraints rule out frameworks altogether. The result had to prove a studio principle: nothing between the editor and production. What you edit is what the user sees.

The site is published as-is: no build step, no deployment pipeline, no compilation. The host takes the folder and publishes it verbatim. This constraint forces clarity in the code.

§ 02 The problem

Conventional web development assumes a build step. You write code, compile it, deploy it. But a studio site has different requirements: it must load instantly, never break unexpectedly, and cost nothing to run. These constraints don't advocate for frameworks — they argue against them. JavaScript frameworks come with dependencies, complexity, and runtime overhead. A single-page consultancy site doesn't need React, Vue, or Next. The simplest possible approach — hand-written HTML, CSS, and JavaScript — meets the performance and reliability target.

§ 03 The approach

The entire site lives in one folder: a self-contained index.html file plus assets. There is no build step; the host publishes the folder as-is. The page is structured as a scrollytelling narrative — an interactive blueprint of the studio as a machine. It functions as both diagnostic intake (understanding what a prospect needs) and method walkthrough (showing how the studio works).

All interaction and motion is written in vanilla JavaScript, without dependencies or a framework. The code responds to scroll position to drive the narrative, triggering sections into view as the user scrolls. The site includes reduced-motion support for users who have requested it and graceful fallbacks for users with JavaScript disabled. The markup and styles are hand-written — each element is directly readable in the page source. Nothing is compiled, transpiled, or generated. What exists in the folder is what the browser renders. The result is a site that loads in milliseconds and will never break due to a missing dependency.

Nothing between the editor and production.

§ 04 Decisions that mattered
D1
No framework, no build
The site eschews JavaScript frameworks. The deploy is the file — the host publishes the folder verbatim, with no build step or compilation.
D2
Vanilla JavaScript with fallbacks
All interaction is vanilla JavaScript, without dependencies. The site includes reduced-motion support and graceful fallbacks for users with JavaScript disabled.
D3
Hand-written markup
The HTML, CSS, and JavaScript are hand-written. Every line exists in the source; nothing is generated, compiled, or hidden.
D4
Scrollytelling driven by scroll
The page uses scroll position as the primary interaction driver. Sections reveal themselves as the user reads, controlled by vanilla JavaScript.
D5
Self-contained folder deployment
A single folder holds everything: index.html plus assets. The host publishes the folder as-is, with no dependencies, environment variables, or external services.
§ 05 Where it stands

The site is live in production at xandrov.com. It serves as the studio's primary web property. The hand-built, no-dependency approach meets the initial brief on every measure: it loads instantly, has never broken, and costs nothing to operate. The page stands as an argument for simplicity — a working model of what happens when you remove abstraction.

HTML / CSSVanilla JSZero build

LIVE — xandrov.com ↗

§ 06 — Sanitization record

No client data, credentials, or internal communications appear in this case study. The site is public and authored by Xandrov Labs; there is no sensitive information to redact. The source code and markup are visible to any browser inspector. The case study describes the architecture exactly as deployed.

Have a system like this worth building?

Fixed scope, quoted after one working session, first output inside two weeks. Read by a person within one working day.