C. Volodina
Get in touch

ChristinaVolodina

Open to jobs, freelance and B2B

Web developer. Fast, search-friendly, multilingual websites with motion that feels alive.

02 — Role

Webdeveloper

Frontend with a full-stack backbone: Next.js, TypeScript, secure APIs and motion that serves the story.

03 — Multilingual

DE ENUK AR

Sites in German, English, Ukrainian and Arabic, and in any other language: the setup (locale routing, hreflang, RTL support) scales to as many languages as a project needs. I speak German (B1), Ukrainian and Russian. English and Arabic copy is written with AI tools such as Claude and GPT.

How I work

Measure

I check with numbers, not with feelings: Lighthouse, Web Vitals, tests.

Small steps

Every step is small, verified and easy to undo.

Ship

Deploy early, improve in the open, keep main green.

SEO

Built in from the first commit: titles, structure, structured data, hreflang.

Own it

From the first sketch to the live site, one person answers for the result.

Clarity

Clear structure, clear words, clear commit messages.

Care

The details others skip: focus states, empty states, error messages.

Curiosity

New tools get a small experiment first, then a place in a project.

Keep scrolling, fly through ↓

Skills

What I do

Eight skills employers ask for. Hover a tile to see it work. Tap a tile to see it work.

01

Fluid layout

Mobile-first, fluid type and spacing with clamp(), CSS Grid and Flexbox, container-aware components.

02

Frontend

Next.js App Router, React, TypeScript strict, CSS Modules. Server Components first.

03

Motion & WebGL

GSAP, ScrollTrigger, Lenis, WebGL shaders, CSS 3D. Animation that serves the page.

04

SEO & GEO

Technical and on-page SEO, Schema.org, hreflang, sitemaps, Core Web Vitals, AI-search readiness.

05

Multilingual sites

Any language: DE, EN, UK and AR today, more on request. next-intl, locale routing, hreflang and full RTL layouts.

06

Accessibility

Semantic HTML, keyboard and focus states, reduced motion, readable contrast.

07

Backend & security

Service layers and repositories, zod validation, session and secrets handling, security headers, GDPR-minded data. Example: the ServiceOS SaaS.

08

AI-assisted dev

Claude Code and GPT as a pair-programmer: rules, skills, MCP, small verified steps.

Fluid layout, live

Drag the handle or use the slider. Navigation, type and cards reflow by the width of their container.

560px · tablet

Fluid by default

Type scales with clamp() and container units, the grid reorganises on its own.

01Card
02Card
03Card

Team workflow on GitHub

I work the way teams do: branches, pull requests and reviews, not just pushes to main. Issues and project boards for planning.

249 GitHub contributions in the last year, private work included. Status 2026-11-12.

Waiting for review

Fix: keep the name clear of the vertical label

The hero name overlapped the vertical label on narrow screens. Review it: click a line to comment.

82 .title {
83- font-size: 18vw;
84+ font-size: clamp(2.5rem, 15.5vw, 18rem);
85 }
86
87 .scene:first-child {
88+ padding-inline-end: calc(var(--gutter) + 2.5rem);
89 }

Comments stay in your browser. Nothing is sent.

ServiceOS · multi-tenant SaaS · in development

Backend in practice: ServiceOS

ServiceOS is a multi-tenant SaaS with an AI receptionist for online booking, built by our team and still in early development. This is the architecture it follows, and how I think about backends in general.

  1. 01
    UI

    React components never call a provider SDK directly.

  2. 02
    Service layer

    Business logic lives in server-only services. Input is validated with zod.

  3. 03
    Interfaces we own

    Repository, auth and AI contracts that belong to us, not to a vendor.

  4. 04
    Provider adapters

    Today a local and an in-memory adapter, a Supabase adapter planned. Swapping a provider costs one adapter, not a rewrite.

  • Provider-agnostic core
  • Repository pattern
  • zod validation
  • Secrets only in environment variables
  • Session behind one function
  • Audited: no provider SDK in the core

Tools I work with

  • GitHub
  • Vercel
  • Next.js
  • React
  • TypeScript
  • HTML5
  • CSS
  • GSAP
  • Three.js
  • Node.js
  • Git
  • ESLint
  • Playwright
  • Vitest
  • zod
  • GitHub Actions
  • Husky
  • Search Console
  • Lighthouse
  • Claude Code
  • Claude
  • ChatGPT
  • Lenis
  • next-intl

Logos are trademarks of their owners, shown only to name the tools I use.

What I haven't done yet, I deliver with AI

If a task needs something new, I learn it with Claude and GPT and deliver it step by step, with every result checked. I know my tools, and I know how to verify what they produce.

  • Tailwind CSS with AI support
  • SQL / PostgreSQL with AI support
  • REST / GraphQL with AI support
  • Docker with AI support
  • Figma handoff with AI support
  • Storybook with AI support
  • State management with AI support
  • Testing Library with AI support

Skills Universe

Every skill, with its proof

A map of what I work with. Pick a cluster, then a skill: it shows the projects and pages where it is proven.

Creative coding

Motion Lab

16 live experiments you can play with: type, cursor physics, shaders, scroll and microinteractions. Every one has real controls.

Move the pointer

Selected work · 8 projects

Projects

Concept sites and my own studio, built end to end: design, motion, content structure, SEO, i18n.

Scroll to explore ↓

See all projects →

01 / 08 · Beauty · Demo

Beauty Studio

Lashes, nails and hair. GSAP and Lenis motion, WhatsApp booking flow, DE / EN / UK.

Next.js 16GSAPnext-intlWebGL

Case study →

SEO

SEO you can inspect

I do SEO as part of the build, not as an afterthought. This page is the proof: everything on the right is read live from this site.

What I do

Lighthouse

Local run on the production build, desktop, 2026-11-15. Not a lab claim for your device, just a real measurement I can repeat. LCP 1.2 s · CLS 0.042

Live from this page

Web Vitals (measured in your browser)

Largest Contentful Paint
measuring…
Layout shift
0.000
First Contentful Paint
measuring…
Time to first byte
measuring…

Checklist, all implemented here

  • Unique title and description per language
  • Canonical URL per language
  • hreflang de, en, uk, ar and x-default
  • Schema.org JSON-LD (Person, WebSite)
  • sitemap.xml and robots.txt
  • Open Graph and Twitter cards
  • llms.txt for AI assistants
  • One H1, logical H2 and H3 hierarchy

AI workflow

I build with Claude, on purpose

AI is part of my daily workflow: I set the architecture, the rules and the taste, and Claude Code does the heavy typing. Small steps, every step checked.

  1. 01
    Rules first

    A CLAUDE.md per project: stack, security checklist, no push without approval, no invented data.

  2. 02
    Map before editing

    Graphify builds a knowledge graph of the codebase, so large changes start from the architecture.

  3. 03
    Skills and MCP

    UI/UX, motion and design-taste skills, plus MCP tools, applied where they fit.

  4. 04
    Verify every step

    Build, lint and a real browser check before anything is committed. Commits only with my OK.

Quality gate

  • ESLintno warnings
  • TypeScript strictno errors
  • Next.js buildproduction build passes
  • Playwright e2e70 of 70 tests pass
  • GitHub Actionsruns on every pull request

Real numbers from the last local run on 2026-11-15, 102 s. Tests cover languages, SEO head, layout overflow, palette, theme, forms and 404.

AI for language

For English and Arabic copy, translations and documentation I use Claude and GPT, then check the result myself. It works well, and the sites you see here are proof.

  • Claude Code
  • Claude
  • ChatGPT
  • GitHub

Built in public

Loads data from github.com only when you click. Live from the public GitHub repository of this site. All commits on GitHub ↗

Statement

I build websites that are fast, multilingual and alive. Every detail is designed, and every animation has to earn its place

Move your cursor

Every surface can respond

A project preview on a water surface

End to end

Design to results, by one person

  1. Step 01

    Design

    I design the layout, type, palette and motion myself, and I test them on real devices before any code is final.

  2. Step 02

    Build

    Next.js, TypeScript and CSS Modules, with i18n, accessibility and SEO built in from the first commit.

  3. Step 03

    Deploy

    Vercel deployments, environment setup, security headers and domains, so the site goes live safely.

  4. Step 04

    Track and improve

    I watch Search Console, Lighthouse and Web Vitals, then adjust titles, content and structure based on the data.

Contact

Contact

Hiring, a freelance project or a collaboration? Write me. The form opens WhatsApp with your message ready to send.

What is this about?

Nothing is stored. Your message opens in WhatsApp.