Xandrov Studio is the build arm of Xandrov Labs — a consulting and build studio focused on systems and implementation. The studio's own website needed to serve as proof of capability: something that felt produced and technical while remaining true to its construction as a single hand-built file. The site presents the studio's archive of shipped systems as an interactive territory, each system plotted as a navigable node. Open any node and you see a full case study with decisions and outcomes. This very page is an example.
A build studio's own site is its strongest proof. But typical portfolio sites are exercises in assertion — they claim outcomes without showing constraint or mechanism. This site needed to show the work honestly: the real decisions, the real trade-offs, the actual stack used. It also needed to remain a single file — no framework overhead, no build pipeline, deployable as static HTML to a subdomain. That meant the interactive map and all case-study data had to live in one index.html file with inline CSS and JavaScript.
The site is a single index.html file — no framework, no build step. All CSS is inlined; all JavaScript executes in the browser. Typography is served from external sources: Fraunces for headers, Newsreader for body, IBM Plex Mono for code samples and citations. The core is an interactive SVG map generated by JavaScript, plotting each system as a node. Clicking a node loads that system's case study from JSON data embedded in the page itself — there is no external API call, no dynamic fetch. Each case study includes context, problem, approach, decisions, outcome, and sanitization note. Responsive layout adapts to mobile and desktop via CSS media queries. The entire site is version-controlled and deploys to static hosting with a subdomain DNS record pointing to the root.
Show the work as a navigable map, not a list — structure is the argument.
The site is live in production at studio.xandrov.com. It serves as both the studio's portfolio and a proof of craft — a single-page site that applies its own principles to its own presentation. Each system in the archive can be navigated independently; each opens a full dossier with decisions visible. The site remains maintainable by hand: adding a new system requires editing the HTML to insert a new JSON block and SVG node, no framework migration or dependency updates required.
The site presents only systems and decisions that the studio elected to make public. Client names and project details were withheld where the work was confidential or remains in active use. No user metrics, financial outcomes, or proprietary implementation details are included. The sanitization note on each case study discloses what was removed and whether withholding it was driven by confidentiality, ongoing use, or strategic discretion.