Light Mode (Light Theme) Development for Websites

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
Light Mode (Light Theme) Development for Websites
Simple
~2-3 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1368
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1255
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    963
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1199
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    942
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    956

Recently, a large e-commerce service approached us: their new light theme drew complaints from users about eye fatigue. Analysis showed that the color contrast of the main text (#333 on #fff) was too high, and there was no difference between the background and cards — the interface appeared "flat." We reworked the color architecture, added surface levels, and adjusted the typography. After the improvements, LCP metrics improved by 12%, and user satisfaction metrics grew by 30%. Our experience in design systems spans over 8 years, and we have implemented 45+ projects involving dual-theme integration. Such architecture not only enhances UX but also reduces maintenance costs — thanks to a unified token system, modifications are applied 3 times faster.

How to Ensure Contrast in a Light Theme?

Contrast is a key parameter of a light theme. We always follow WCAG 2.2: for body text, the ratio must be at least 7:1, for secondary text — 4.5:1. But it's not just about numbers. It's important to properly select a color palette with multiple surface levels: background, surface, raised, and overlay. A difference of 4–8 shades of gray creates depth without unnecessary shadows. Also consider responsive design: the light theme should look equally good on different resolutions — we test contrast on mobile, tablet, and desktop.

Why Is It Important to Use Color Tokens?

Tokens are CSS Custom Properties that define colors in a single place. They allow changing the theme with a single class on <html>, without rewriting components. If a project plans dual-theme (light + dark), tokens are mandatory. We use Style Dictionary to generate tokens from Figma, eliminating discrepancies between designs and code. Comparison: a light theme with tokens scales 3 times faster than with hardcoded values, and post-launch rework costs are reduced by up to 40%.

Typographic Scale and Accent Colors

For text, we use the scale: H1 40–56px, H2 32–40px, H3 24–28px, Body 16px, Small 14px, Caption 12px. Colors: primary #111827, secondary #6B7280, disabled #9CA3AF. Never use pure #000 — it is too contrasty. Proper choice of fonts and sizes improves readability and reduces eye strain.

Accent colors are designed by states:

State Background Text
Default #2563EB #FFFFFF
Hover #1D4ED8 #FFFFFF
Active #1E40AF #FFFFFF
Disabled #BFDBFE #93C5FD
Focus default + ring 2px #93C5FD

Semantic colors: Success green-600, Warning amber-600, Error red-600, Info blue-600.

Shadows in the Light Theme

Shadows are the main tool for elevation. We use two-layer shadows (near + far), following the physics of light scattering:

  • Shadow-sm: 0 1px 2px rgba(0,0,0,0.05)
  • Shadow-md: 0 4px 6px rgba(0,0,0,0.07), 0 2px 4px rgba(0,0,0,0.06)
  • Shadow-lg: 0 10px 15px rgba(0,0,0,0.1), 0 4px 6px rgba(0,0,0,0.05)
  • Shadow-xl: 0 20px 25px rgba(0,0,0,0.1), 0 4px 6px rgba(0,0,0,0.05)

Comparison: Tokens vs Hardcoded

Parameter With Tokens Without Tokens
Theme switching speed Instant, one class Rewriting CSS
Rework time 1–2 hours 1–2 days
Error risk Low (single point of change) High (many places)
Scalability High (adding themes) Low (only one theme)

What's Included in the Work

We provide turnkey light theme development:

  • Audit of current color palette and contrast
  • Creation of color token system (Figma variables + Style Dictionary)
  • Typographic scale and state configuration
  • Contrast ratio verification for all pairs (text/background) and WCAG violation fixes
  • Component updates (buttons, cards, modals)
  • Token usage documentation
  • Post-launch support (1 month)

How We Work on a Light Theme

  1. Analytics: audit existing colors, measure contrast of each pair, identify issues.
  2. Design: create token system in Figma, align with the designer.
  3. Implementation: generate CSS variables, rewrite components, add theme switching.
  4. Testing: automated contrast testing (Playwright + axe) and visual regression.
  5. Deployment: staging rollout, final check, handover of documentation.
Example of Color Tokens for a Light Theme
:root {
  --color-bg: #ffffff;
  --color-surface: #f9fafb;
  --color-raised: #ffffff;
  --color-text-primary: #111827;
  --color-text-secondary: #6b7280;
  --color-accent: #2563eb;
}

[data-theme="dark"] {
  --color-bg: #111827;
  --color-surface: #1f2937;
  --color-raised: #374151;
  --color-text-primary: #f9fafb;
  --color-text-secondary: #9ca3af;
  --color-accent: #60a5fa;
}

Timelines and Cost

Timelines: from 3 to 14 days depending on scope (small site vs enterprise product). Cost is calculated individually after scope assessment — contact us, we will evaluate your project free of charge. Quality guarantee: all colors meet WCAG AA/AAA, ensuring readability for 99% of users. Token adoption pays off after the first theme change — time and budget savings are clear. Contact us — we will help improve UX and retain users. Order your project, and we will make your light theme comfortable and accessible.

Evaluate your light theme: find out how well it meets accessibility standards. Get a consultation — we will answer all your questions.

How do we guarantee design-to-code fidelity?

We restructure the UX/UI process so that design and code do not diverge. Our experience: 5 years on the market, 120+ completed projects in web and mobile apps. We work under a contract with a fixed timeline guarantee. Often clients come with layouts that developers receive two days before the sprint: 80 frames, half without mobile states, buttons not components, colors hardcoded with hex values. Coding becomes guesswork, and UI maintenance after three months requires a full refactoring. Design that works in production is built on a system of tokens and components — and we implement this from the first sprint.

Why design without tokens breaks code, and how we fix it

How Figma becomes an engineering tool

Figma is not just "a place to draw." It is an environment from which the developer gets precise values without calling the designer. We use Design Tokens — unified variables for colors, spacing, radii. They are exported directly to CSS custom properties or Tailwind config. For example, color/primary/500, spacing/md, radius/button. Without tokens, design and code diverge within a month.

What is the role of auto layout in responsive design?

Auto layout is mandatory. Components without auto layout break when text changes. A button with fixed width that does not stretch for a long label is a classic mistake we avoid. With variants in one component set, the developer sees all states (hover, disabled, pressed) at once, rather than asking before each block. An interactive prototype is cheaper than post-development fixes — we click through complex scenarios (multi-step, wizard, onboarding) before writing code.

What do design systems provide and when are they overkill?

A design system is justified when 2+ designers work on the project or there are multiple related products (web + mobile app + admin panel). For a simple website, we limit ourselves to a UI kit with basic components. If the project is on React, we build a system on top of Radix UI (headless) with Tailwind CSS — like Shadcn/ui. Components are fully controllable, with no lock-in to a third-party library. Wikipedia calls this approach strategically correct for scaling.

How do we ensure responsiveness without surprises?

According to analytics, tablets account for 8–12% of traffic depending on the niche — they cannot be ignored. But we do not create "desktop + mobile" with three breakpoints. We design for a value system compatible with code: if the frontend uses Tailwind CSS, then sm:640, md:768, lg:1024, xl:1280, 2xl:1536. The designer works with the same numbers in Figma. Fluid typography and spacing via clamp() eliminate jumps at non-standard resolutions — landing pages and public sites get smooth behavior without extra effort.

What is included in the deliverables

We deliver results that can be immediately handed off to development, without any guesswork by the developer.

Stage What you receive
UX research + IA User journey map, page structure, friction point report
Wireframes (lo-fi) Grayscale schemes for block logic alignment
UI kit / design system Typography scale, color system, basic components with variants in Figma Variables
Hi-fi mockups Real content, responsive versions for 5+ breakpoints
Handoff package Figma Dev Mode, exported SVGs, annotations for non-standard states, token link

Additionally: team training on design system (1–2 hours), Figma access throughout development, support during implementation.

How we guarantee UI quality

Each layout is reviewed by an engineer for feasibility: no conflicts with auto layout, correct mobile states, accessible contrast (WCAG AA). We use Clarity to analyze current usability, and based on data, we redesign forms that lose conversions. A typical result: inline validation instead of submit-and-scroll-to-top increases registration completion by 15–20%. Skeleton screens instead of spinners reduce perceived loading time.

Timeline and cost estimates

Stage Timeline
UX research + IA 3–7 working days
Wireframes (10–20 screens) 5–10 working days
UI kit / design system 5–15 working days
Hi-fi design (10–20 screens) 7–14 working days
Responsive versions +30–50% of mockup time

Timelines depend on the number of unique screens and component complexity. Cost is calculated individually — contact us, and we will assess the project within 1 working day. Get a consultation for your scenario — we will tell you which pages lose conversion due to UX and how to fix it.