This System Requirements Document (SRD) defines the requirements for the complete redesign and elevation of the Ecolife website (https://ecolife.az) — an international architectural lighting manufacturer.
The project is not a generic website refresh. The redesigned experience must function as a digital flagship and a digital architectural lighting showroom, visually comparable to world-class architecture, lighting, industrial design, and high-end technology brands.
The governing creative principle for the entire project is: light itself is the interface. The website must not merely be about lighting — the visitor must experience light as a visual material throughout the interface. In place of decorative UI, the experience is built from composition, typography, photography, negative space, lighting, depth, geometry, and motion.
The redesign must preserve Ecolife's existing business logic — products, projects, catalog, company credibility, engineering capability, SEO visibility, and brand recognition — while completely reinventing its presentation.
Ecolife is an architectural lighting manufacturer and engineering provider. The digital product is a public, content-led marketing and catalog website with immersive 3D and interactive lighting scenes. Its purpose is to:
The experience is organized as a continuous visual system rather than a stack of unrelated blocks. It begins in darkness; light reveals material, material reveals architecture, architecture reveals products, products reveal engineering, and engineering reveals Ecolife.
The delivery includes actual implemented layouts, components, responsive states, animations, interactions, lighting effects, shaders, 3D scenes, product presentations, navigation, project layouts, and transitions — not only wireframes or design suggestions. Where the existing site relies on a CMS and API for content and catalog data, those systems are preserved and reused rather than unnecessarily rebuilt.
The existing live Ecolife website is an authoritative content source. The following facts are the source-of-truth content to be preserved and carried into the redesign. They must not be replaced with generic category names or invented examples.
Brand and identity
Hero copy
Statistics
Value propositions
Calls to action
Featured projects
Contact
Structure reference (existing site sections)
Navigation reference
Feature reference (existing capabilities)
Domain context
The reference source is applied as
content_source,domain_context,brand_source,structure_reference, andfeature_referencewith authoritative authority. Its content, domain facts, brand, and structure are preserved unless explicitly replaced. Facts not available from the source are marked unverified rather than invented.
A design professional specifying lighting for architectural, commercial, hospitality, retail, or premium residential projects. They browse featured systems, evaluate products editorially and technically, review project case studies for credibility, and expect engineering credibility and premium product quality before initiating a project conversation.
A technical user who needs photometric-level detail. They engage deeply with the engineering/Dialux section, technical drawings, luminaire positioning, beam distribution, lux distribution, product technical data (CRI, light output, color temperature, dimensions, installation type), and the product light simulation to validate specifications.
A business decision-maker (office, restaurant, retail, hospitality, or similar commercial space) seeking lighting solutions. They respond most strongly to the immersive brand experience, company credibility and statistics, featured project portfolio, "Why Ecolife" engineering advantages, and the final project CTA.
The internal team responsible for auditing the existing site and codebase (including CMS, API, and asset structure), defining art direction, building the design system and components, implementing the homepage, products, and projects, perfecting responsive behavior, optimizing performance, ensuring SEO continuity, and polishing the final experience.
Integration and content systems (CMS, API, catalog data sources) are treated as system actors, not personas. Photography is treated as owned/existing asset content, not a persona.
The visual system is defined by architectural minimalism + cinematic lighting + physical materials + digital precision. It must be sophisticated rather than flashy.
Base materials / palette:
Accent strategy:
Light temperature palette:
Rhythm and contrast (not a uniformly dark site):
Buttons remain neutral and architectural, with thin illuminated-line hover treatments rather than saturated fills.
"Light itself is the interface."
The website is not about lighting; it is an experience of light. Light functions as the primary visual material — establishing hierarchy, depth, interaction, transition, focus, emotion, product understanding, and brand identity.
The narrative arc of the experience:
The signature expression is a continuous lighting system that runs through the experience — linear light profiles, illuminated architectural lines, travel of a thin beam along architectural paths, and light transforming between sections (a hero light line becoming the grid line of the next section; a technical drawing line becoming an architectural lighting profile).
Ecolife must never be confused with a generic template or an ordinary LED retailer. The visitor should immediately understand: Ecolife does not simply sell lights — Ecolife designs how spaces are experienced through light.
Interaction model:
Motion direction:
Performance
Accessibility
Responsive Behavior
SEO
Quality and Craft
Preferred stack (used where appropriate and adapted to the existing technology rather than forced):
Frontend Application
Styling & Tokens
3D & Rendering
Motion
Asset Pipeline
Content & Data Layers
Existing Layers
No technologies outside the source material are introduced. The delivery shape is a content-led, 3D/interactive marketing and catalog website; only the layers the accepted product actually requires are included.
| Term | Definition |
|---|---|
| SRD | System Requirements Document — this document. |
| Ecolife | The architectural lighting manufacturer and engineering provider whose website is being redesigned. |
| Digital flagship | The redesigned website acting as the brand's premium online showcase and showroom. |
| Light as interface | The core creative principle in which light is used as the primary visual and interaction material, not merely decoration. |
| Linear LED system | A linear architectural lighting product family (e.g., linear LED profiles, recessed linear systems, magnetic tracks, pendants). |
| CRI | Color Rendering Index — a measure of how accurately a light source renders colors, presented in product technical data. |
| Color temperature (K) | The warmth/coolness of light in Kelvin: 2700K (warm), 3000K (architectural warm white), 4000K (neutral white), 5000K (cool daylight). |
| Dialux | Professional lighting design/calculation software used for photometric planning and project support. |
| Lux distribution | A photometric diagram showing light levels across a space, used in the engineering section. |
| PBR | Physically Based Rendering — material model producing believable metallic, roughness, and emission responses in 3D. |
| GLB / GLTF | 3D model asset formats, compressed with Draco or Meshopt for web delivery. |
| Emission map | A texture that defines which parts of a 3D model emit light. |
| WebP / AVIF | Modern image compression formats used for optimized, fast-loading imagery. |
| Signed-off "case study" | The 01–05 project detail structure (Challenge, Lighting Concept, Engineering Solution, Products Used, Result). |
| Exploded view | An interactive product visualization separating components such as aluminium profile, diffuser, LED module, driver, and mounting component. |
| CMS | Content Management System used to author and manage Ecolife's products, projects, and copy. |
| API | Application programming interface used to serve product, project, and catalog data to the website. |
| Core Web Vitals | Google's user-experience performance metrics that the redesign must target. |
| Reduced motion | An accessibility/OS preference that limits animation, which the site must respect. |
| Sticky scroll scene | A scroll moment where a visual element remains fixed while its content changes. |
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!